TCP/IPv6 Configuration and Management Manual (G06.29+, H06.03+, J06.03+)

Troubleshooting Tips for NonStop TCP/IPv6
HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012
7-2
pair in processors 0 and 1 and another primary and backup TELSERV pair in
processors 2 and 3.

The TCP6SAM process must be in a processor that has a TCP6MON running.
Ensure that all primary and backup TCP6SAM processes are configured in
processors, which contain a running TCP6MON.

If you replace the ZTCP6SRL file while you have the TCP6MAN -- or any
TCP6MONs or TCP6SAMs -- running and a processor stops, you get Error 48:
TCPIPV6: TCP-MON can’t be started after CPU failure. Before
replacing the ZTCP6SRL file you must stop the NonStop TCP/IPv6 environment. If
you receive Error 48 in this circumstance, stop the NonStop TCP/IPv6 subsystem
and then restart it. (See Stopping NonStop TCP/IPv6 on page 6-7.)

If you have TCP6MAN ($ZZTCP) configured as a generic process, ensure that its
STOPMODE attribute is set to SYSMSG. For more information, see Managing
Persistence on page 6-15.

If you are migrating from a NonStop K-series system where you are using multiple
Telserv processes on each 3615 communication controller with ports 23, 2, and 3,
you cannot create the same configuration in NonStop TCP/IPv6 because NonStop
TCP/IPv6 does not allow sharing of ports between processes. However, you can
create a similar configuration in the NonStop TCP/IPv6 environment by enabling
round-robin processing. In this case, on the NonStop S-series system or Integrity
NonStop NS-series system, you create multiple Telserv processes in multiple
processors and enable round-robin filtering in the NonStop TCP/IPv6 environment,
(for round-robin filter-enabling procedures, see Round-Robin Filtering on page 2-6)
then the Telserv processes can share all configured ports. If you configure Telserv
like this, run the process pairs in alternative processor pairs (see Port Collision
Considerations for Listening Processes on page 6-2).

When Telserv is running as a fault-tolerant process pair in the NonStop TCP/IPv6
environment, all Telserv STATIC service and STATIC window information is
captured and retained by the backup Telserv process when the primary Telserv
fails. However, when you run multiple Telserv processes not fault-tolerant process
pairs with round-robin filtering enabled, you can configure the persistence manager
to restart Telserv. In this case, when a failed processor is restarted, the persistence
manager can execute an automatic script to relaunch the Telserv process.
However, the primary Telserv process launched by the persistence manager does
not have the knowledge of the STATIC service and STATIC window information. To
avoid or fix this problem, modify the Telserv startup script that the persistence
manager launches upon processor restart, so that the script reconfigures the
Telserv STATIC service STATIC window.