2.4.1 0000XXXX

This section describes operation messages in which the upper four digits of the message identifier are 0000.

Table 2-4: Operation messages for event location SOFTWARE (0000XXXX)
Message ID	Event Level	Message text
Message ID	Content and response
00003001	E3	System restarted due to abort reset operation.
00003001	The device was restarted because the RESET button was pressed. [Action] None.
00003002	E3	System restarted due to default reset operation.
00003002	The device was restarted because the default switch was pressed. [Action] None.
00003003	E3	System restarted due to fatal error detected by software.
00003003	The software detected a fatal error and restarted the system. [Action] Check the log by executing the show logging command. If another problem is indicated in the log, take appropriate action according to the error message.
00003004	E3	System restarted due to user operation.
00003004	The switch was restarted for one of the following reasons: Executing reload Commands Detect member switch additions, deletions, or state changes in a stacked configuration A SW(Switch processor)part failure is detected in a stacked configuration. Restarting the Network Interface Management Program [Action] Use show logging command to check the log. Then, check the cause of the device restart. The log for each restart source is shown below. If applicable logs are available, take the appropriate action for each log. Detect member switch additions, deletions, or state changes in a stacked configuration Reboot Logging with Event Location = STACK A SW part failure is detected in a stacked configuration. E8 EQUIPMENT 25040201 2101 Hardware restarted because of its failure. Restarting the Network Interface Management Program E7 SOFTWARE 25300000 1001 nimd aborted. R7 SOFTWARE 25300000 1001 nimd restarted.
00003005	E3	System restarted due to fatal error detected by kernel.
00003005	The kernel detected a fatal error and restarted the system. [Action] Check the log by executing the show logging command. If another problem is indicated in the log, take appropriate action according to the error message.
00003006	E3	System restarted due to WDT timeout.
00003006	The device was restarted because of a WDT (watchdog timer) timeout. [Action] Check the log by executing the show logging command. If another problem is indicated in the log, take appropriate action according to the error message.
00003007	E3	System restarted due to hardware error detected by kernel.
00003007	The device was restarted because of a hardware failure. [Action] Replace the Switch.
00003008	E3	System restarted due to hardware error detected.
00003008	The device was restarted because of a hardware failure. [Action] Replace the Switch.
00003101	E7	Memory exhausted. Possibly too many users logged in, or too many sessions(via ftp,http,...) established.
	There is not enough CPU memory. [Action] If many users are logged in, log out all but the most essential users. If there is a lot of use from ftp, disconnect all but the most essential connections. If there is too much access from the network management device, limit the amount of access to the minimum necessary. If the system does not recover after any one of three methods above, the capacity limit of the Switch might not be satisfied. Review the network configuration by referring to Vol.1" "3 Capacity Limits in the Configuration Guide.
	R7	Recovered from memory exhaustion.
	The CPU has recovered from a lack of memory. [Action] None.
00003303	E3	Received many packets and loaded into the queue to CPU.
00003303	Numerous received packets have accumulated in CPU queues. [Action] None. If this message is output frequently, check the following. Check if the switch has received a large quantity of packets for the local device (such as for ping or telnet), in a broadcast, or in a multicast. If there is too much access from the network management device, limit the amount of access to the minimum necessary. The network configuration may be too complex. Revise the network configuration.
00003304	E3	Processed the packets in the queue to CPU.
00003304	Packets that had been accumulating in CPU queues have been processed. [Action] None.
00008601	E3	NTP lost synchronization with <ip address>[ on VRF <vrf id>].
00008601	Synchronization was lost with the NTP server at <ip address>. <ip address>: IPv4 address of NTP server <vrf id> VRF ID [Action] Use the show ntp associations command to check the NTP status. If the non-synchronized state continues, check the NTP configuration, NTP server operation status, and availability of communication.
00008602	E3	NTP detected an invalid packet from <ip address>[ on VRF <vrf id>].
00008602	An invalid packet from the NTP server at <ip address> was detected. <ip address>: IPv4 address of NTP server <vrf id> VRF ID [Action] Check the NTP server.
00008603	E3	NTP could not find the server which synchronize with.
00008603	There is no NTP server for which synchronization is possible. [Action] Check the NTP configuration, NTP server operation status, and availability of communication.