Expand Configuration and Management Manual (G06.24+)

Troubleshooting
Expand Configuration and Management Manual—523347-008
21-18
WAN Subsystem Problems
Common WAN Subsystem Problems
The following is a list of common WAN subsystem problems:
•
The SNMPCODE, KERNELCODE, or PROGRAM file is not in the correct
subvolume or is not secured for “N” read access (the leftmost character in the file
security string). SNMPCODE and KERNELCODE are download files for the SWAN
concentrator; PROGRAM is a microcode file where the data link control (DLC) task
is located. These files must be in a subvolume authorized for access by the TFTP
servers. The correct subvolume is $SYSTEM.CSSnn. For example, if the current
running SYSnn is SYS00, then the correct subvolume is $SYSTEM.CSS00.
•
The NonStop TCP/IP processes used by the WAN subsystem are not configured
correctly. For example:
•
You must configure a SUBNET object (SCF ADD SUBNET command) for each
connection to a network. The SUBNET object is the point of connection
between the NonStop TCP/IP process and the ServerNet LAN Systems
Access (SLSA) subsystem.
•
Each SUBNET must be associated with the correct Internet Protocol (IP)
address (IPADDRESS attribute) and subnet mask (SUBNETMASK attribute).
•
Each time you add a SUBNET, a route is automatically created. A route
(ROUTE object) is the path a data packet travels to reach its destination. You
must issue an SCF START ROUTE command to create implicit connections to
and from a route.
Refer to the TCP/IPv6 Configuration and Management Manual for complete
information about TCP/IP process configuration.
For detailed information about configuring the WAN subsystem, refer to the WAN
Subsystem Configuration and Management Manual