System Events
The following are the events related to system.
Event ID: 61
Message |
----------------------------------------- |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Description |
This log even generates a blank line in the event log. |
Event ID: 62
Message |
SYSTEM went down without saving crash information |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Description |
SYSTEM went down without saving crash information. |
Event ID: 63
Message |
SYSTEM went down: <REASON_STR> |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Description |
SYSTEM went down and the reason why is given. |
Event ID: 64 (Severity: Fatal)
Message |
<CRASH REASON STR> |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Fatal |
Description |
Crash reason will be recorded. |
Event ID: 65 (Severity: Fatal)
Message |
Boot-up selftest failed |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Fatal |
Description |
This message displays if the boot up selftest resulted in a failure. A slot selftest failure message will also be logged for each slot that resulted in a failure. |
Event ID: 66
Message |
system: System Booted |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Description |
This message displays at the conclusion of the boot process. |
Event ID: 75 (Severity: Warning)
Message |
Out of <BUF TYPE> buffers; miss count: <COUNT VAL> |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Event ID: 260
Message |
Mgmt Module <MODULE_ID> Active |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Description |
This log event informs the user that the management module is active. |
Event ID: 261
Message |
Mgmt Module <MODULE_ID> in Standby Mode |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Description |
This log event informs the user that the management module is in standby mode. |
Event ID: 262 (Severity: Warning)
Message |
Mgmt Module <MODULE_ID> Failed - Synchronization Failed |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Warning |
Description |
This log event informs the user that the management module synchronization has failed. |
Event ID: 263
Message |
Mgmt Module <MODULE_ID> Offline (redundancy disabled) |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Description |
This event log notifies the user that the management module was not in standby mode and is now offline. |
Event ID: 264 (Severity: Warning)
Message |
Mgmt Module <MODULE_ID> Failed Selftest |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Warning |
Description |
This event log indicates why the management module failed selftest. |
Event ID: 265 (Severity: Warning)
Message |
Lost Communication with Mgmt Module <MODULE_ID> |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Warning |
Description |
This event log indicates why the management module has lost communication. |
Event ID: 266
Message |
Resetting Mgmt Module <MODULE_ID> |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Description |
This event log indicates why the management module was reset. |
Event ID: 267 (Severity: Warning)
Message |
Mgmt Module <MODULE_ID> - Running different version of SW |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Warning |
Description |
This event log indicates why the management module was running different version of software. |
Event ID: 268 (Severity: Warning)
Message |
Mgmt Module <MODULE_ID> - Failover occurred |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Warning |
Description |
This event log indicates why the failover of the management module occurred. |
Event ID: 269
Message |
Mgmt Module <MODULE_ID> - User initiated switchover occurred |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Description |
This event log indicates why the user initiated switch over of the management module. |
Event ID: 270 (Severity: Warning)
Message |
Mgmt Module <MODULE_ID> - Offline (Incompatible SW versions) |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Warning |
Description |
This event log indicates why the management module has offline incompatible software versions. |
Event ID: 271 (Severity: Warning)
Message |
Other management module is not in standby- shutdown request ignored |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Warning |
Description |
This event log indicates that the second management module is not present or in a state to take over - so blinks all LEDs and logs a message. |
Event ID: 272
Message |
Mgmt Module <MODULE_ID> Offline (shutdown) |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Description |
The reason why the management module has shutdown offline. |
Event ID: 273
Message |
Resetting Mgmt Module <MODULE_ID> - <REASON_STR> |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Description |
The reason why the management module <MODULE_ID> was reset is given. |
Event ID: 542
Message |
Runtime Error Skipped: <ERROR_MSG> |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Description |
Skips runtime error messages that are not being used. |
Event ID: 543
Message |
The command was terminated prematurely because the output exceeded the maximum memory limit. |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Description |
This event log is displayed when the command was terminated prematurely because the output exceeded the maximum memory limit. |
Event ID: 686 (Severity: Fatal)
Message |
<UPGRADE_FAILED_REASON_STR> |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Fatal |
Event ID: 687
Message |
<UPGRADE_PASSED_REASON_STR> |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Event ID: 820 (Severity: Warning)
Message |
A signature is not stored with the current switch software. Please see the 'Software Signing and Verification' section of the Basic Operations Guide for details. |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Event ID: 994 (Severity: Warning)
Message |
<PORTS|MODULE><ID> parity recovery <MEMORY_INDEX> 0x<LOCATION>. |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Description |
Logs the successful repair of certain ASIC memory location that reported a (soft) parity error. Memory Index is the internal ASIC index of the particular memory bank (as there are many). This message is used by HPE Support. |
Event ID: 995 (Severity: Warning)
Message |
<PORTS|MODULE><ID> parity recoveries in previous <INTERVAL_VAL> |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Description |
Logs the number of successful recoveries that occurred during. the interval: 5 minutes; 1 hours; 24 hours. This reduces the number. of system log events when many recoveries happen close in time. |
Event ID: 2681 (Severity: Warning)
Message |
Workaround nic-82566dm occurred. See www.hp.com/networking/device_help/nic_update for details. |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Description |
A NIC is transmitting excessive fragments. Possible Causes: A malfunctioning NIC. Actions:. 1. Check to see if switch is receiving fragments by issuing. "walkmib etherstatsFragments" from the switch CLI. 2. Update the NIC firmware. 3. Update the NIC Driver software. 4. By default; FFI will automatically downgrade the port speed to auto-10/100 if excessive fragments have been etected on the gig port. 5. Check www.procurve.com/device_help/nic_update for more details. |
Event ID: 3001 (Severity: Fatal)
Message |
System reboot due to Power Failure |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Fatal |
Description |
This message displays when the switch goes through a reboot. because of a power failure. |
Event ID: 3002 (Severity: Fatal)
Message |
System reboot due to Switch Reset |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Fatal |
Description |
This message displays when the switch goes through a soft reboot when the user executes the "boot system flash <primary|secondary>" |
Event ID: 3003
Message |
Configuration hash calculation started. |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Description |
This message displays when the hash generation for the running configuration is started |
Event ID: 3004
Message |
Configuration hash calculation finished. |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Description |
This message displays when the hash generation for the running configuration is finished |
Event ID: 3005
Message |
Diagnostic level is set to <SUPPORT|STARNDARD> |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Event ID: 3006
Message |
Reason for system reboot: <REBOOT_REASON_STR> |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Event ID: 3007 (Severity: Warning)
Message |
message buffer allocation has reached <USAGE_PERCENTAGE> |
Platforms |
KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Description |
This event is used to indicate when the message buffer usage reached above threshold limit. |
Event ID: 3008 (Severity: Warning)
Message |
packet buffer allocation has reached <USAGE_PERCENTAGE> |
Platforms |
KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Description |
This event is used to indicate when the packet buffer usage reached above threshold limit. |
Event ID: 3009 (Severity: Warning)
Message |
packet buffer high priority allocation has reached <USAGE_PERCENTAGE> |
Platforms |
KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Description |
This event is used to indicate when the packet high priority buffer usage reached above threshold limit. |
Event ID: 3010 (Severity: Warning)
Message |
packet message buffer high priority allocation has reached <USAGE_PERCENTAGE> |
Platforms |
KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Description |
This event is used to indicate when packet message high priority buffer usage reached above threshold limit. |
Event ID: 3011 (Severity: Warning)
Message |
management message buffer allocation has reached <USAGE_PERCENTAGE> |
Platforms |
KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Description |
This event is used to indicate when the management message buffer usage reached above threshold limit. |
Event ID: 3012 (Severity: Warning)
Message |
oobm packet buffer allocation has reached <USAGE_PERCENTAGE> |
Platforms |
KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Description |
This event is used to indicate when the oobm buffer usage reached above threshold limit. |
Event ID: 3361
Message |
Note: As per RFC 1123- the hostname must contain only letters- numbers and hyphens- and must not start or end with a hyphen. |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Description |
RFC for protocols mandate that component hostname labels may contain only the ASCII letters 'a' through 'z' (in a case-insensitive manner), the digits '0' through '9', and the hyphen (-). The original specification of hostnames in RFC 952 mandated that labels could not start with a digit or with a hyphen and must not end with a hyphen. However; a subsequent specification (RFC 1123) permitted hostname labels start with digits. No other symbols, punctuation characters, or blank spaces are permitted. |
Event ID: 3395 (Severity: Warning)
Message |
<BUFFER_MSG> |
Platforms |
KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Description |
Security Log message |
Event ID: 3396 (Severity: Warning)
Message |
<BUFFER_MSG> |
Platforms |
KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Description |
Security Log message |
Event ID: 3440
Message |
User:'<USER_NAME>':The command: <AAAA_AUTH_SSH_ENABLE_RADIUS> |
Platforms |
KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Description |
User:'user1': The command: 'aaa authentication ssh enable radius' is executed during boot up. |
Event ID: 3441 (Severity: Warning)
Message |
The command log buffer is 80% full. |
Platforms |
KB, WB, WC, YC |
Category |
System |
Severity |
Warning |
Description |
Log message is :The command log buffer is 80% full. |
Event ID: 3442 (Severity: Warning)
Message |
The command log buffer has wrapped; older logs will be overwritten. |
Platforms |
KB, WB, WC, YC |
Category |
System |
Severity |
Warning |
Description |
Log message is : The command log buffer has wrapped; older logs will be overwritten. |
Event ID: 3443 (Severity: Warning)
Message |
The event log buffer is 80% full. |
Platforms |
KB, WB, WC, YC |
Category |
System |
Severity |
Warning |
Description |
Log message is :The event log buffer is 80% full. |
Event ID: 3444
Message |
User:'<USER_NAME>': <COMMAND_LOG_INFO> |
Platforms |
KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Description |
Log messages are: User:'user1': The command logging is enabled. User:'user1': The command logging completed. |
Event ID: 3500
Message |
The supportability information in file <FILENAME> is corrupt and has been removed |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Description |
Informs that some of the crash/boot-history information has been corrupt and removed. |
Event ID: 3801 (Severity: Warning)
Message |
Mgmt Module <MODULE_ID> - Nonstop switching disabled because of SW version mismatch. Warm standby enabled. |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Event ID: 3805
Message |
<LOG STR> |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Description |
This event can be used for any banner related events Currently used for 'banner exec' and 'banner motd' banner exec; The banner exec message is modified. banner motd; Message of the day(MOTD) banner is modified. no banner exec; The banner exec message is disabled. no banner motd; Message of the day(MOTD) banner is disabled. |
Event ID: 3841 (Severity: Fatal)
Message |
<UPGRADE_FAIL_STATUS_MSG> |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Fatal |
Event ID: 3842
Message |
<UPGRADE_PASS_STATUS_MSG> |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Event ID: 4180 (Severity: Warning)
Message |
Auto reset value changed from <OLD_VALUE> to <NEW_VALUE>: <MESSAGE_STR> |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Warning |
Event ID: 4753
Message |
Event log buffer has wrapped; older logs will be overwritten. |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Event ID: 5011
Message |
Switch is in preview mode. |
Platforms |
KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Event ID: 5041
Message |
Active configuration backup has failed on enabling preview mode. |
Platforms |
KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Event ID: 5042
Message |
Restoring backup configuration to active configuration has failed on disabling preview mode. Active configuration has been erased. |
Platforms |
KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Event ID: 5352
Message |
One or more tunnels with unsupported tunnel ID- greater than <MAX_TUNNEL>- have been deleted from the configuration. |
Platforms |
KA |
Category |
System |
Severity |
Information |
Description |
This event is used to indicate the deletion of one or more invalid Tunnel IDs after downgrade to a version that does not support tunnek IDs greater than value specified in <MAX_TUNNEL>. |
Event ID: 5353
Message |
Exit Hibernation Mode. |
Platforms |
KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Description |
system: System reboot due to exiting Hibernation Mode. This message appears when the switch goes through a reboot because hibernation mode is being exited. |
Event ID: 5561
Message |
The tcp-push-preserve feature was disabled. This is a change to default configuration. |
Platforms |
K, KA, KB, WB, WC, YC |
Category |
System |
Severity |
Information |
Description |
This event is used to indicate that there is a default value change for "tcp-push-preserve" command from enable to disable on upgrade. |
Event ID: 5575
Message |
copp: Threshold exceeded for traffic class <CLASS_NAME>. Packets are being dropped. |
Platforms |
KB, WC |
Category |
System |
Severity |
Information |
Description |
This message displays when the rate at which a particular class of traffic is received at the switch exceeds the configured limit. |
Event ID: 5576
Message |
copp: Threshold exceeded for user defined copp - <ID>. Packets are being dropped. |
Platforms |
KB, WC |
Category |
System |
Severity |
Information |
Description |
This message displays when the rate at which a particular class of traffic is received at the switch exceeds the configured limit. |
Event ID: 5577
Message |
MM <MODULE_ID> elected as Active-MM based on preferred-amm configuration |
Platforms |
KB |
Category |
System |
Severity |
Information |
Event ID: 5579
Message |
Port <PORT> with fault-finder broadcast-storm configuration cannot be added to a trunk. |
Platforms |
K, KA, KB, RA, WB, WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Description |
This event is used to indicate that fault-finder broadcast-storm is not allowed on a trunk port. |
Event ID: 5580 (Severity: Warning)
Message |
Fault-finder broadcast-storm configuration is removed as it is configured on a VSF port <PORT_NAME>. |
Platforms |
KB, WC |
Category |
System |
Severity |
Warning |
Description |
This event is used to indicate that fault-finder broadcast-storm is not allowed on a vsf port. |
Event ID: 5738
Message |
Port <PORT_NAME> with fault-finder multicast-storm configuration cannot be added to a trunk. |
Platforms |
WC, YA, YB, YC |
Category |
System |
Severity |
Information |
Description |
This event is used to indicate fault-finder for multicast-storm is not allowed on a trunk port. |
Event ID: 5741 (Severity: Warning)
Message |
Fault-finder multicast-storm configuration is removed as it is configured on a VSF port <PORT_NUM>. |
Platforms |
WC |
Category |
System |
Severity |
Warning |
Description |
This event is used to indicate that fault-finder multicast-storm is not allowed on a VSF port. |