Troubleshooting guide

3. Troubleshooting Functional Failures During Operation
163
target.
3. Due to network congestion, communication with the polling monitoring track target is
unstable.
To investigate the cause of the current unexpected track state, you must follow the methods of
analysis shown in the following table to determine the cause.
Table 3-90: Action to take when the track state is unexpected for AX6700S, AX6600S, or
AX6300S
Table 3-91: Action to take when the track state is unexpected for AX3800S, AX3650S, or
AX3640S
No. Items to check and commands Action
1 Check the track information
• Specify the
<track-object id> parameter
for the
show track-object command, and
display the track information.
If the track information is not displayed, or the track type is
UNSPECIFIED, the track is not set.
If the track operating status is Disable, stop the track in the
configuration.
Check the configuration.
If the track operating status is
Init, the track has stopped
because startup has just finished. Wait until the startup wait
time has elapsed.
If the track operating status is
Aging, system switching is in
progress. The track state immediately before system
switching is retained. Wait until the system switching wait
time has elapsed.
If the track is operating, yet the track type is ICMP, go to
No. 2.
2 Check whether IPv4 communication with the
track target is possible
For the destination address, source address, and
next hop, use the same values as for the track
settings.
• Execute the
ping command.
If the ping destination address and responding address are
different, the address that responded is the subnet broadcast
address of the destination address.
IPv4 ICMP polling monitoring does not operate when the
destination is a broadcast address.
Check the configuration.
If the track has no next hop specified, and there is no
response or response is unstable, check the IPv4 network
communication between the Switch and the track target
device.
If the track has a next hop specified, and there is no response
or the response is unstable, go to No. 3.
3 Check whether IPv4 communication can be made
with the router specified as the next hop
• Execute the
ping command.
If communication with the device specified as the next hop
is unstable, check the IPv4 network communication
between the Switch and the next hop device.
If communication with the device specified as the next hop
is unstable, check the IPv4 network communication
between the next hop device and the track target device.
No. Items to check and commands Action
1 Check the track information
• Specify the
<track-object id> parameter
for the
show track-object command, and
display the track information.
If the information is not displayed, or the track type is
UNSPECIFIED, the track is not set.
If the track operating status is
Disable, stop the track in the
configuration.
Check the configuration.