Title and Copyright Information |
About This Manual |
Audience |
Organization |
Related Documents |
Reader's Comments |
Conventions |
1 | Technical Overview |
1.1 | The Role of a Cluster Interconnect |
1.2 | Controlling Storage Traffic Across the Cluster Interconnect |
1.3 | Controlling Application Traffic Across the Cluster Interconnect |
1.4 | Controlling Cluster Alias Traffic Across the Cluster Interconnect |
1.5 | Effect of Cluster Size on Cluster Interconnect Traffic |
1.6 | Selecting a Cluster Interconnect |
2 | Hardware Configuration |
2.1 | Configuration Guidelines |
2.2 | Supported LAN Interconnect Configurations |
2.2.1 | Two Cluster Members Directly Connected by a Single Crossover Cable |
2.2.2 | Cluster Using a Single Ethernet Switch |
2.2.3 | Cluster Using Fully Redundant LAN Interconnect Hardware |
2.2.4 | Clustering AlphaServer DS10L Systems |
3 | Software Installation |
3.1 | Preparation |
3.1.1 | Obtain the Device Names of the Network Adapters |
3.1.2 | Obtain IP Names and IP Addresses for Each Member's Cluster Interconnect |
3.2 | Create a Single-Member Cluster |
3.3 | Add Members |
4 | Cluster Administration |
4.1 | Configuring a NetRAIN Virtual Interface for a Cluster LAN Interconnect |
4.2 | Tuning the LAN Interconnect |
4.2.1 | Improving Cluster Interconnect Performance by Setting Its ipmtu Value |
4.3 | Obtaining Network Adapter Configuration Information |
4.4 | Monitoring LAN Interconnect Activity |
4.5 | Migrating from Memory Channel to LAN |
4.6 | Migrating from LAN to Memory Channel |
4.7 | Troubleshooting |
4.7.1 | Booting Member Joins Cluster But Appears to Hang Before Reaching Multi-User Mode |
4.7.2 | Booting Member Hangs While Trying to Join Cluster |
4.7.3 | Booting Member Panics with "ics_broadcast_setup" Message |
4.7.4 | Booting Member Displays "ifconfig ioctl (SIOCIFADD): Function not implemented: nr0" Message |
4.7.5 | Many Broadcast Errors on Booting or Booting New Member Panics Existing Member |
4.7.6 | Cannot Manually Fail Over Devices in a NetRAIN Virtual Interface |
4.7.7 | Applications Unable to Map to Port |
A | Configuring Switches for a Highly Available LAN Interconnect |
A.1 | Link Aggregation |
A.2 | Link Resiliency |
A.3 | Spanning Tree Protocol (STP) |
B | Installation Examples |
B.1 | clu_create Log |
B.2 | clu_add_member Log |
C | Cluster Interconnect /etc/sysconfigtab Attributes Set by clu_create and clu_add_member |
Examples |
B-1 | Sample clu_create Log File |
B-2 | Sample clu_add_member Log File |
Figures |
2-1 | Two Cluster Members Directly Connected by a Single Crossover Cable |
2-2 | Three-Member Cluster Using a Single Ethernet Switch |
2-3 | Recommended Fully Redundant LAN Interconnect Configuration Using Link Aggregation or Link Resiliency |
2-4 | Recommended Fully Redundant LAN Interconnect Configuration Using the Spanning Tree Protocol |
2-5 | Nonrecommended Redundant LAN Interconnect Configuration |
2-6 | Low-End AlphaServer DS10L Cluster |
2-7 | Cluster Including Both AlphaServer DS10L and AlphaServer ES40 Members |
3-1 | Cluster Virtual Network and Physical Communication Channel |
Tables |
1-1 | Comparison of Memory Channel and LAN Interconnect Characteristics |
C-1 | Cluster Interconnect /etc/sysconfigtab Attributes Set by clu_create and clu_add_member |
Index |