NEC IP8800/S6700, IP8800/S6600, IP8800/S3600, IP8800/S2400, IP8800/S6300 manual 106

3.Troubleshooting Functional Failures in Operation

No.	Troubleshooting Steps and Command		Action
7	Execute the show logging command and	• If "Virtual router <VRID> of <Interface Name> received VRRP packet for
	the show vrrpstatus command with		which the advertisement interval is different than the one configured for local
	"statistics" parameter specified to check the		virtual router." is registered in the type log and "<Number of packets> with bad
	receiving status of the ADVERTISEMENT		advertisement interval" of statistics is incremented, confirm that set values of
	packets.		the ADVERTISEMENT packet sending interval match between this system and
			the remote system.
		• 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 match between this system and
			the remote system.
		• If "Virtual router <VRID> of <Interface Name> received VRRP packet with IP
			TTL not equal to 255." is registered in the type log and "<Number of packets>
			with bad ip ttl" 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 ip
			address list" of statistics in incremented, confirm that settings of the virtual IP
			address 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 that the authentication password has been set on this
			system and the remote system.
		• If "VRRP packet received with unsupported version number." is shown in the
			type log and statistics information "<Number of packets> with invalid type" is
			incremented, confirm that the VRRP mode between this system and remote
			system is same.
		If the ADVERTISEMENT packet is normally received, check the remote system.
		Go to No. 8 if the ADVERTISEMENT packet is not received.
8	Check the statistical information of the	If "Input rate" and "Output rate" are excessive on the physical port to which the
	physical port to which the remote system	remote system is connected and the line traffic is high or the CPU usage checked
	constituting the same virtual router is	by the show cpu command is high, take the following actions:
	connected using the show interfaces	• If the line loops, review the use of STP or physical network configuration to
	command.		eliminate the loop.
	Also, check the CPU usage using the show	•	Execute configuration command vrrp timers advertise to set up rather
	cpu command.		long sending intervals for sending the ADVERTISEMENT packets.
		•	Execute configuration command vrrp preempt delay to set the automatic
			switchback suppressing time.
		Go to No. 9 if the traffic of the physical port is low.
9	Confirm that discarding ADVERTISEMENT	If such filtering setting exists, change the filtering setting so that the
	packets is not set in the filter setting.	ADVERTISEMENT packets are not discarded.
		If this is not the case, check for the operation of the remote system constituting the
		same virtual router.
10	If a failure monitoring interface has been set	If another virtual router is defined on the interface on which a failure monitoring
	up, check for its status.	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 on one
		of the failure interface.
		Go to No. 11 if the failure monitoring interface described above is not set up.

106