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

Configuring Expand-Over-ServerNet Lines
Expand Configuration and Management Manual — 529522-013
12 - 5
ServerNet Cluster Product
persistence manager starts a new ServerNet cluster monitor process. Because data
traffic does not involve the ServerNet monitor, it could continue during this time.
$ZZSCL must be configured and started before the Expand-over-ServerNet
line-handler processes can be started. For more information on configuring $ZZSCL,
see the ServerNet Cluster Manual.
ServerNet Cluster Product
ServerNet clusters enable multiple Integrity NonStop NS-series servers to work
together and appear to client applications as one large processing entity. ServerNet
clusters extend the ServerNet X and Y fabrics outside the system boundary and allow
the ServerNet protocol to be used for intersystem messaging. For more information on
the ServerNet Cluster product, see the ServerNet Cluster Manual.
Wide Area Network (WAN) Subsystem
You create an Expand-over-ServerNet line-handler process by adding it as a device to
the WAN subsystem. For each node in a ServerNet cluster, you must create one
Expand-over-ServerNet line-handler process for every other node in the cluster. The
WAN subsystem is preconfigured and started during the system load sequence. For
more information on the WAN subsystem, see the WAN Subsystem Configuration and
Management Manual.
X and Y Fabrics
X and Y fabrics are a collection of connected routers and ServerNet links that,
together, provide an interconnection for Integrity NonStop NS-series servers. Each
processor connects to both fabrics. The X fabric and the Y fabric are not connected to
each other; therefore, a ServerNet packet cannot cross from one fabric to the other
and a failure in one fabric does not affect the other fabric.
Note. The Integrity NonStop NS1000 server does not support ServerNet clusters.