2.4.1 0000XXXX
This section describes operation messages in which the upper four digits of the message identifier are 0000.
Message ID |
Event Level |
Message text |
---|---|---|
Content and response |
||
00003003 |
E3 |
System restarted due to fatal error detected by software. |
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. |
The switch was restarted for one of the following reasons:
[Action] Use show logging command to check the log. Then, check the cause of the device restart. |
||
00003303 |
E3 |
Received many packets and loaded into the queue to CPU. |
Numerous received packets have accumulated in CPU queues. [Action] None. However, if this message occurs frequently, check the following:
|
||
00003304 |
E3 |
Processed the packets in the queue to CPU. |
Packets that had been accumulating in CPU queues have been processed. [Action] None. |
||
00008601 |
E3 |
NTP lost synchronization with <ip address>. |
Synchronization was lost with the NTP server at <ip address>. <ip address>: IPv4 address of NTP server [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>. |
An invalid packet from the NTP server at <ip address> was detected. <ip address>: IPv4 address of NTP server [Action] Check the NTP server. |
||
00008603 |
E3 |
NTP could not find the server which synchronize with. |
There is no NTP server for which synchronization is possible. [Action] Check the NTP configuration, NTP server operation status, and availability of communication. |