TCP/IPv6 Configuration and Management Manual (G06.29+, H06.03+, J06.03+)
HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012
7-1
7
Troubleshooting Tips for NonStop
TCP/IPv6
This section provides some conditions to check if you encounter some problems with
your NonStop TCP/IPv6 configuration. Review these suggestions that might pertain to
your configuration:
Check the adapter configuration and ensure that the SACs are configured with the
correct Access List. Ensure that all processors running a TCP6MON process are
listed in the Access List.
Ensure that you have cleared the system of all DEFINEs and PARAMs before
adding new ones.
Ensure that you add a DEFINE and PARAM to specify a TCP6SAM name before
starting your LISTNER, TELSERV, or other client application. These examples
show the DEFINE and PARAM TACL commands:
ADD DEFINE =TCPIP^PROCESS^NAME, FILE $ZSAM0
PARAM TCPIP^PROCESS^NAME $ZSAM0
Ensure that you set your home terminal for the TCP6MAN process to $ZHOME.
Check your TCP6MAN process creation script to ensure that TERM $ZHOME (and
IN $ZHOME, OUT $ZHOME) are included. You should also add those attributes to
the TCP6SAM, LISTNER, and TELSERV process startup commands.
If you have a large configuration that has many LISTNERs and if you want to use
different TCP6SAM processes for each of them, make sure you delete and add
DEFINEs and PARAMs for the TCP6SAM process that will be associated with
each LISTNER. For an example of deleting the DEFINEs and PARAMs, see the
Considerations in the START MON Command for TCP6MAN on page 8-113.
You must wait for all the TCP6MONs to start before starting TCP6SAM. If your
configuration scripts include a command to start the MONs, ensure that scripts
contain a DELAY command after the START MON command.
When you configure a set of listening processes for round-robin, do not allow their
primary and backup processors to overlap. That is, if you configure primary and
backup listening processes, do so in distinct pairs. For example, if you have four
processors, 0 through 3, and you want to configure primary and backup TELSERV
processes for round-robin distribution, configure a primary and backup TELSERV
Note. Only one TCP6SAM process is needed for all the applications in the system when
LNP is not used; creating more TCP6SAM processes does not provide more bandwidth. If
you use only one TCP6SAM process for all the LISTNERs in the system, you only need to
delete and add the DEFINE for TCPIP^PROCESS^NAME once.