TCP/IPv6 Configuration and Management Manual (G06.24+)

Manage the NonStop TCP/IPv6 Subsystem
HP NonStop TCP/IPv6 Configuration and Management Manual—524523-008
6-5
QIO Management Considerations
Configuration Guidelines
These are guidelines to use when configuring NonStop TCP/IPv6 with Ethernet
failover:
•
When selecting the LIF pair for the failover SUBNET pair, you should select LIFs
on different adapters.
•
When using Fast Ethernet adapters and Gigabit Ethernet adapters connected
directly to Ethernet switches, the failover recovery time can be impacted by the
spanning tree feature used in a switch.
•
When using multiple failover pairs on the same network subnet and adding static
routes, it is best to add a copy of each route to one SUBNET in each failover pair.
This increases the availability of the routes should both SUBNETs comprising a
failover pair become unavailable. It also allows NonStop TCP/IPv6 to distribute
outbound connections over the failover pairs when the source IP address is not
selected by the application. In this case, static routes need to be added to both
SUBNETs of the pair if both LIFs are to participate.
•
Ethernet failover might not function when directly connected to a firewall that uses
Ethernet address (MAC) to IP address filtering. This problem can be overcome by
adding a router between the LIFs and the firewall.
•
When configuring multiple shared-IP failover pairs, the reserved IP address cannot
be shared between pairs.
•
If you use IP alias addresses, they must be added to both SUBNETs of a failover
pair to preserve their availability during a failure. Also, alias IP addresses can only
be shared between SUBNETs configured as a failover pair.
•
When a pair of LIFs has been configured for Ethernet failover, separating them for
use on distinct SUBNETs requires a manual deletion of the SUBNET objects to
disassociate them. The LIFs can then be used in the non-failover configuration
(that is, one LIF per SUBNET).
To configure your NonStop TCP/IPv6 environment for Ethernet failover, you must use
both the ADD SUBNET and ALTER SUBNET commands. See the ADD SUBNET
Command for TCP6MAN on page 8-26 and ALTER SUBNET Command for TCP6MAN
on page 8-49.
QIO Management Considerations
The QIO subsystem has been enhanced as of G06.17 to allow you to have more
control over certain aspects of memory management. You can now configure QIO to
run in the Kseg2 memory segment and you can also control where QIO runs in the flat
memory segment. Configuring QIO to run in Kseg2 can improve performance for
NonStop TCP/IPv6, but also imposes constraints that affect all QIO clients (including
Parallel Library TCP/IP). As discussed in the QIO Configuration and Management
Manual, you must consider these constraints as well as a variety of other factors
before changing the default QIO configuration.