HP-UX IPv6 Transport Administrator Guide HP-UX 11i v3 (5992-6426, May 2013)

B. ping successful? If ping -f inet6 succeeded, return to Flowchart 2. If ping
-f inet6 failed, the problem may exist in the routing table for the problem host.
Continue to C.
C. Execute: netstat -rnf inet6. To display gateway routing information in numerical
form, execute:netstat -rnf inet6
D. Direct route to remote or default route to gateway? If the route exists, go to F. If not,
continue to E to add a new route.
E. Add route entry on local system. Use the route command to add a route entry to
the route table on the local system. Refer to route(1M) for a complete description
of the command. Or if an IPv6 router on the LAN advertises default routes, wait a
few minutes to see if a route advertisement is added to the default router list. Start
again with Flowchart 6.
F. Correct router configured? If your local host has a route to the correct router, then
retry Flowchart 6 from the remote node. If the remote node’s routing is configured
properly, and both the local and remote nodes can connect to their respective
routers, then contact your ISP or network administrator to verify network-to-network
connectivity.
G. Change route entry on local system or router. If the routing information is incorrect,
correct it using route, or verify that the IPv6 router is advertising proper subnet
prefixes. Then retry Flowchart 2 to test network connectivity.
Diagnostic Flowcharts 45