You need to verify that the appropriate routes are configured.
Your server needs routes to send packets to other servers or hosts. The
route determines the path that a packet takes to its destination.
If you are trying to Ping an interface address and do not receive a reply,
you should verify that your routes are configured and available. To communicate
between a local and remote network, whether you are using IPv4 or IPv6 connectivity,
you should have at least these two types of routes configured on the server:
- A direct route (*DIRECT) allows packets to travel between interfaces on
the local network. It is automatically configured and activated by the server
for each interface.
- A default route (*DFTROUTE) allows packets to travel to hosts that are
not directly connected to your network. It provides a path for the packets
to take. A default route identifies a specific node as a next hop to which
the packets travel and then continue their trip to their final destination
on a different network. The packets take the default route whenever there
is no other (more specific) route matching the destination IP address.
Keep in mind that routes are unidirectional. Just because a packet from
a client can get to your system does not mean that your system can send a
packet to the client.
Verify that the appropriate IPv4 or IPv6 routes are configured on your
server.
IPv4 routes
To display information about the IPv4
routes on your server, follow these steps:
- Type NETSTAT or WRKTCPSTS on
the command line to display the Work with Network Status menu, and then select
option 2 on this menu.
- Select option 5 (Display details) for details about a specific route.
- If you do not have a default route configured, you should configure it
now. To configure a default route, follow these steps:
- At the command line, type CFGTCP to access the Configure
TCP/IP menu.
- Select option 2 (Work with TCP/IP Routes).
- Select option 1 (Add) to go to the Add TCP/IP Route (ADDTCPRTE) display.
- For the Route destination prompt, specify *DFTROUTE.
- For the Subnet mask prompt, specify *NONE.
- For the Next hop prompt, specify the appropriate IP address.
As an alternative, you can configure a default route using the New
IPv4 Route wizard in iSeries™ Navigator. See the route information
for iSeries Navigator
for more information.
IPv6 routes
To display information about the IPv6
routes on your server, follow these steps:
- Type NETSTAT or WRKTCPSTS on
the command line to display the Work with Network Status menu, and then select
option 5 on the menu.
- Select option 5 (Display details) for details about a specific route.
For IPv6, the Internet Protocol automatically configures default routes
for each interface on the server. However, if you prefer, you can use the New
IPv6 Route wizard in iSeries Navigator to create new routes
yourself. See the route information for iSeries Navigator for more information.