Filter
Top Products
3. Troubleshooting Functional Failures in Operation
72
(1) Checking the log and interface
Communication may be interrupted by a line failure (or damage) or a neighboring system failure. Check the log
displayed on this system or the interface up/down status using the show ipv6 interface command. For the
procedure, see "3.6.1 Communication Is Disabled or Is Disconnected."
(2) Identifying the extent of the failure (performed from this system)
If no failure is found on this system, a failure may exist somewhere in the route between this system and the remote
system. The procedure to locate the failure in the route to the remote system and identify the failure range is as follows:
1. Log in to the system.
2. Use the ping ipv6 command to check communication between both parties. For an example of issuing ping
ipv6 and how to interpret the result, see the manual "Configuration Settings."
3. If communication to the other party cannot be verified with the ping command, use ping to check communication
to remote systems starting from the system closest to this system.
4. If the result of the ping ipv6 command shows that the neighboring system has failed, go to "(4)Checking NDP
resolution information with neighboring system." If the result shows that the remote system has failed, go to
"(5)Checking unicast interface information."
(3) Identifying the extent of failure (performed from the customer's terminal equipment)
If login to this system is not possible, follow the procedure below to identify the extent of failure to see the failure
location in the route between the customer's terminal equipment and the other party.
1. Confirm that the customer's terminal equipment has the ping ipv6 function.
2. Use the ping ipv6 function to check communication between the customer's terminal equipment and the remote
system.
3. If communication to the remote system cannot be verified with the ping ipv6 command, use ping ipv6 again
to check communication to systems starting from the system closest to the customer's terminal equipment.
4. After the extent of failure has been identified using the ping ipv6 command log in to this system if it is considered
to have failed and follow the failure analysis flow to check for the failure cause.
(4) Checking NDP resolution information with neighboring system
If communication to a neighboring system is not possible as a result of ping ipv6 execution, address resolution by
NDP may not have been achieved. The procedure for checking the status of address resolution between this system and
the neighboring system is described below.
1. Log in to the system.
2. Use show ipv6 neighbors command to check the status of address resolution with the neighboring system
(presence/absence of NDP entry information).
3. If the address resolution with the neighboring system is achieved (NDP entry information is provided), go to
"(5)Checking unicast interface information."
4. Confirm that the IP network setting on the neighboring system matches that of this system if the address resolution
with the neighboring system is not achieved (NDP entry information is not provided).
(5) Checking unicast interface information
Check the route information acquired by this system if communication is not possible even when the address resolution
with the neighboring system is achieved, or if communication is disabled in the midway to the other party during IPv6
unicast communication, or if the route to the other party is abnormal. Use the following procedure: