WAN Subsystem Configuration and Management Manual

Adding a SWAN Concentrator
WAN Subsystem Configuration and Management Manual—522463-011
4-31
Configuration Requirements and Recommendations
Configuration Requirements and
Recommendations
•
The WAN manager process is preconfigured by HP manufacturing and is running
in processor 0 with the backup process running in processor 1.
•
HP recommends that you configure the SWAN concentrator across two E4SAs,
FESAs, GESAs, G4SAs or VIO enclosures for improved fault tolerance. (VIO
enclosures are supported in H06.08 and subsequent H-series RVUs.)
•
The SWAN concentrator must be configured to use the same TCP/IP processes as
do the E4SA, FESA, GESA, or G4SA ports to which the SWAN concentrator is
connected.
•
The preferred and alternate TCP/IP processes that one SWAN concentrator is
configured to must be configured with separate TCP/IP SUBNET objects.
•
The SWAN concentrator IP addresses associated with Ethernet path A must be on
the same SUBNET as the preferred TCP/IP process. The SWAN concentrator IP
addresses associated with Ethernet path B must be on the same subnet as the
alternate TCP/IP process.
•
The SWAN concentrator IP addresses associated with Ethernet path A must be on
a different SUBNET than the SWAN concentrator IP addresses associated with
Ethernet path B. (This should always be the case because the preferred and
alternate NonStop TCP/IP processes are configured on different SUBNETs.)
•
One ConMgr process is required in each processor that supports a DEVICE object.
•
The WAN manager process automatically configures WANBoot, TFTP, and the
SNMP trap multiplexer processes. HP does not recommend configuring these
processes separately.
•
Each data communications subsystem object has requirements imposed on its
configuration as a DEVICE object by the data communications subsystem to which
it belongs. You will need to read the manuals listed in Table 2-2 on page 2-2 for
product-specific requirements.
Note. The path A and path B IP addresses must be different. Violation of this rule does
not always prevent successful operation, but many functions will not work properly,
including path switching under failure conditions, latent failure detection, and OSM and
TSM operations such as incident analysis and SWAN CLIP firmware update.