This section discusses the following common problems and their potential solutions:
The router does not forward IP packets
Verify that the IP Packet Forwarding statistic is set to REINITIALIZE SYSTEM command.in TCPCON (Protocols > IP). If routing is not enabled, enable IP Packet Forwarding under Protocols in INETCFG and then issue the
A TCP/IP host cannot reach the router on the local network
Verify that the network portion of the IP address and the subnet mask are the same on the router and the host.
Verify that the router and host use the same frame type.
Use PING from the router to verify connectivity to the TCP/IP host and verify that the IP Address Translation table has an entry for the host.
If there is no entry, use MONITOR to check the status of the LAN driver.
Use PING from the router to verify connectivity to the TCP/IP host and check for Echo Requests in TCPCON (Statistics > ICMP).
Use PING from the router to verify connectivity to the TCP/IP host and check for Echo Replies in TCPCON (Statistics > ICMP).
If the value of the Echo Replies statistic is not incrementing, verify that IP is bound to the host's interface with the correct address and mask. Also, verify that the interface driver is loaded with the correct frame type. If necessary, check the IP statistics for errors and perform Step 7 in Section 7.3, Procedure for Troubleshooting.
A TCP/IP host cannot reach a remote host
Verify that the IP address and mask are correct.
Verify that the local TCP/IP host has the local router listed as the default router.
Verify that each router has a routing protocol enabled and that it has not been disabled on the interface.
Starting at the local router, verify that each router has a route to the remote host's network.
Verify that there are no filters capable of blocking IP traffic configured on any routers along the path.
Verify that the remote host has a route to the local host’s network.
Using PING, verify that the remote host can reach each router on the path to the local TCP/IP host.
Starting at the router closest to the remote host, verify that each router has a route to the local TCP/IP host’s network.
The router cannot initiate IP traffic to a remote router through a LAN interface
Verify that IP is bound to the right interface with the correct address and mask.
Check whether the interface driver is loaded with the correct frame type.
Check whether a route exists to the network on which the destination router resides. This can be done through the IP Routing Table window of TCPCON. If the destination router is accessible, also verify that it has a route to the source router's network.
A TCP/IP host cannot reach another host when fault tolerance is disabled and the NIC that was handling the data transfer has gone down
Make sure the NIC is grouped for load balancing and fault tolerance.
Make sure that fault tolerance is enabled for the group.
To verify that NIC is grouped:
Load INETCFG, then select Bindings > TCP/IP > Configure TCP/IP Bind Option.
Make sure that the Group interface for LBFT is set to Yes.
To check that fault tolerance is enabled:
Load INETCFG and select Protocols > TCP/IP.
In the screen that appears, make sure that fault tolerance is enabled.
This could be for the complete system. You still need to verify whether fault tolerance is enabled for the particular Net Group.
Select Fault Tolerance Configuration > Configure Individual Group.
Select the particular Net Group, then check whether fault tolerance is enabled for it; if it is not, set it to Yes.
Load INETCFG, then select Bindings > TCP/IP.
Select the Interface Group for your WAN card.
Select WAN Call Destination, press Insert, then select the WAN card.
Select Static Routing Table, then press Insert.
The Static Routing entry sets up the default route that points to the Internet Service Provider (ISP).
Select Route to Network or Host > Default Route.
Press Esc to save your changes and exit the menus.
For the changes to take effect, reinitialize the system.
Routes are not exchanged on a LAN:
Use INETCFG to verify that the IP Packet Forwarding option is enabled.
Use INETCFG to verify that a routing protocol has been enabled.
Use INETCFG to verify that the routing protocol has not been disabled on an interface.
Use TCPCON to examine the routing table and determine which routes are missing.
Check TCPCON for IP errors.
Check TCPCON for ICMP errors.
If you are using RIP, use INETCFG under Bindings, verify that the RIP Mode option is not set to Send Only or Receive Only.
If the RIP Version option is set to RIPII, verify that the other routers also support RIP II.
Verify that no route filters are configured that would block route information packets for that interface.
If you are using OSPF, verify that the following conditions have been met:
Routers in the area have the same Authentication Type configured.
All routers on the same network have the same Authentication Password configured for the interface to the network.
All routers on the same network have the same Hello Intervals configured for the interface to the network.
The state of each neighbor is either two-way or full in TCPCON (select Protocol Information > OSPF > Neighbors). If it is not, one of the two conditions described next will occur. Refer to the next two paragraphs for an explanation of the corrective actions required.
In TCPCON, there is a router link state advertisement for each router in your area (select Protocol Information > OSPF > Link State Advertisements). If these advertisements are not present, verify that the missing router is active and the correct area ID is configured for the network interface.
In TCPCON, the number of link state advertisements, Area Boundary Routers, and Autonomous System Boundary Routers are the same for each router in your area (select Protocol Information > OSPF > Areas). Verify that the problem routers are active. Bring down any router whose routing database is not synchronized with the databases of its routing neighbors. If the problem persists, reduce the size of your network or add more memory to the router.
Routes are not exchanged on a LAN
Verify that the broadcast address is correct.
RIP routes are not accessible to hosts on OSPF networks
Check the status of the Autonomous System Boundary Router statistic in TCPCON (select Protocol Information > OSPF).
Verify that no filters are configured that would block access to the network.
When you are trying to bind an IP address, if you get an error message stating a conflict for the IP address, set the allow ip address duplicates command to off under SET parameters.
Increase the following using the SET command options:
Load balancing might have been enabled only for the system and not for the particular group. Check whether you have grouped multiple NICs and enabled load balancing for them.
To check that load balancing is enabled at the group level:
Load INETCFG, then select Protocols > TCP/IP.
In the screen that appears, load balancing should enabled. This is for the complete system. You still need to verify whether load balancing is enabled for the particular Net Group.
Select Load Balancing Configuration > Configure Individual Group.
Select the particular Net Group and check whether load balancing is enabled for it. If it is not, set it to Yes.
If the application is binding to the local host (0.0.0.0), the data is always sent through the Primary interface. The Primary interface should be inside the LBFT group for the load to be evenly balanced.
Check whether the interface designated as Primary is within the group or not. If not, either group the Primary interface or make one of the group members Primary.
If the application is not bound to the local host, then the data is always sent through the host where the application is bound. To load balance in this case, make sure that this host is inside the LBFT Group.
To check whether a particular binding is part of the LBFT Group:
Load INETCFG, then select Bindings > TCP/IP.
In the screen that appears, select the Configure TCP/IP Bind option.
Make sure that the group interface for LBFT is set to Yes.
This could happen if the server abended while being configured. This corrupts the sys:\etc\tcpic.cfg file. Delete this file and copy a backup of the previous configuration.
This could happen if more than one interface is using the same driver. If this is the case, never delete any of the bindings. Always disable them if you don't want to use them.