3.
Troubleshooting Functional Failures in Operation
108
5
Execute the
show
vrrpstatus
command
with "statistics" parameter specified to check
the receiving status of ADVERTISEMENT
packets.
•
If "Virtual router <VRID> of <Interface Name> received VRRP packet for
which the advertisement interval is different than the one configured for local
virtual router." is registered in the type log and "<Number of packets> with bad
advertisement interval" of statistics is incremented, confirm that set values of
the ADVERTISEMENT packet sending interval and the settings of the VRRP
operation mode between this system and the remote system are same.
•
If "Virtual router <VRID> of <Interface Name> received VRRP packet that
does not pass the authentication check." is registered in the type log and
"<Number of packets> with authentication failed" of statistics is incremented,
confirm that password settings match between this system and the remote
system.
•
If "Virtual router <VRID> of <Interface Name> received VRRP packet with IP
HopLimit not equal to 255." is registered in the type log and "<Number of
packets> with bad ipv6 hoplimit" of statistics is incremented, confirm that there
is no other router between this system and the remote system.
•
If "Virtual router <VRID> of <Interface Name> received VRRP packet for
which the address list does not match the locally configured list for the virtual
router." is registered in the type log and "<Number of packets> with bad ipv6
address list" of statistics in incremented, confirm that the settings of the virtual
IP address and VRRP operation mode are same.
•
If "Virtual router <VRID> of <Interface Name> received VRRP packet that
does not pass the authentication check." is registered in the type log and
"<Number of packets> with bad authentication type" of statistics is
incremented, check to see if the authentication password has been set on this
system and the remote system.
•
If "Virtual router <VRID> of <Interface Name> received VRRP packet that
length less than the length of the VRRP header." is registered in the type log and
"<Number of packets> with packet length error" of statistics is incremented,
confirm that settings of the VRRP operation mode between this system and the
remote system are same.
•
When "VRRP packet received with unsupported version number." is registered
in the type log and "<Number of packets> with invalid type" of statics is
incremented, confirm that settings of the VRRP operation mode between this
system and the remote system are same.
If the ADVERTISEMENT packet is normally received, check the remote system.
Go to No. 6 if the ADVERTISEMENT packet is not received.
6
Check the statistical information of the
physical port to which the remote system
constituting the same virtual router is
connected using the
show interfaces
command.
Also, check the CPU usage using the
show
cpu
command.
If "Input rate" and "Output rate" are excessive on the physical port to which the
remote system is connected and the line traffic is high or the CPU usage checked
by the
show cpu
command is high, take the following actions:
•
If the line loops, review the use of STP or physical network configuration to
eliminate the loop.
•
Execute configuration command
vrrp timers advertise
to set up
rather long sending intervals for sending the ADVERTISEMENT packets.
•
Execute configuration command
vrrp preempt delay
to set the automatic
switch back suppressing time.
Go to No. 7 if the traffic of the physical port is low.
7
Confirm that discarding ADVERTISEMENT
packets is not set in the filter setting.
If such filtering setting exists, change the filtering setting so that the
ADVERTISEMENT packets are not discarded.
If this is not the case, check for the operation of the remote system constituting the
same virtual router.
8
If a failure monitoring interface has been set
up, check for its status.
If another virtual router is defined on the interface on which a failure monitoring
interface is set up, confirm that the failure monitoring interface of that virtual
router is not the interface of this virtual router. Otherwise, delete the setting of
either failure interface.
Go to No. 9 if the failure monitoring interface described above is not set up.
No.
Troubleshooting Steps and Command
Action
Summary of Contents for IP8800/S2400 Series
Page 10: ......
Page 26: ......
Page 62: ......
Page 72: ......
Page 190: ......
Page 198: ......
Page 215: ...153 6 Line Test 6 1 Testing Line ...
Page 220: ......
Page 227: ...165 Appendix Appendix A Contents of show tech support Command Display ...
Page 248: ......