Expand Configuration and Management Manual (H06.21+, J06.10+)

Planning for ServerNet Clusters
Expand Configuration and Management Manual — 529522-013
4 - 4
Examples of ServerNet Clusters Coexisting With
ATM or IP
Connection, log onto the system being added, select the Configure a ServerNet
Node action for the System object, and perform the action. A guided procedure is
launched, with online help available to assist you in performing the procedure.
Examples of ServerNet Clusters Coexisting With ATM or IP
•
ServerNet Clusters Connected By ATM or IP Lines
•
ServerNet Clusters Connected By a Single ATM or IP Line (Not Recommended)
•
ServerNet Clusters Using Layered Topology With Connections to Nodes Outside
the Cluster
ServerNet Clusters Connected By ATM or IP Lines
Groups of systems at separate locations can use clustering technology to increase
performance within each location and connect to each other by using ATM or IP lines.
When systems on different ServerNet clusters need to communicate with each other,
the Expand line handlers are invoked at every node along the path between the source
and the destination node (including the source and destination nodes). Thus,
processor use is higher when networked applications transfer information between
systems located on separate ServerNet clusters. To avoid this situation, you can
provide the ATM or IP connectivity within the ServerNet cluster so that communications
between the ServerNet clusters travels over IT or ATM without invoking line handlers to
change technologies. Figure 4-1 on page 4-5 shows two ATM-connected or IP-
connected ServerNet clusters in a fault-tolerant configuration that incurs line hops. To
modify this configuration for inter-ServerNet cluster communications without line hops,
add ATM or IP connections within the ServerNet cluster as well.
Note. The Integrity NonStop NS1000 server does not support ServerNet clusters.