HPESP Events
The following are the events related to HPESP.
Event ID: 648 (Severity: Fatal)
|
Message |
<SUB-SYSTEM>: Self-test failed <REASON-STRING> |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
Indicates that x86 self-test failed and the reason is displayed in parenthesis |
Event ID: 649 (Severity: Fatal)
|
Message |
<SUB-SYSTEM>: base configuration transfer failed |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
Indicates that base configuration (via BIOS handshake protocol) has failed. |
Event ID: 650 (Severity: Fatal)
|
Message |
<SUB-SYSTEM>: incompatible BIOS version: <VERSION_STRING> |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
Indicates that BIOS is not compatible with the current switch firmware. |
Event ID: 651 (Severity: Fatal)
|
Message |
<PRODUCT DESR. STR> diagnostics partition is ready |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
Indicates that diagnostics partition has loaded and ready for user interaction. |
Event ID: 652 (Severity: Fatal)
|
Message |
<PRODUCT DESR. STR>: Maximum client-port VLANs count reached |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
Indicates that there is no room available in the security VLAN groups, for this access-controller. At this point the access-controller is not operational. User should delete at least one security VLANs in order to resolve the issue. |
Event ID: 653 (Severity: Fatal)
|
Message |
<SUB-SYSTEM>: Maximum system VLANs count reached |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
Indicates that there is no room available in the system VLAN groups; for this HPESP. At this point the HPESP is not operational. User. should delete at least one VLANs in order to resolve the issue. |
Event ID: 654 (Severity: Fatal)
|
Message |
<PRODUCT DESR. STR>: Reboot system to complete client-port configuration |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
Indicates that the system needs to be rebooted in order for security VLANs to be configured properly. |
Event ID: 655 (Severity: Fatal)
|
Message |
<SUB-SYSTEM>: unable to create VLAN. <REASON-STRING> |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
Indicates that SNMP requests to create a VLAN and to assign the downlink port to it; has failed. |
Event ID: 656
|
Message |
<SUB-SYSTEM>: VLAN <VLAN_ID> is created. |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Information |
|
Description |
Indicates that a VLAN is created and the downlink port of the HPESP is assigned to it as the tagged member. |
Event ID: 657 (Severity: Fatal)
|
Message |
<SUB-SYSTEM>: application initialization failed. |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
Indicates that HPESP initialization failed for the following reasons:. 1. Incompatible HPESPd version. 2. Unable to create VLANs. |
Event ID: 658 (Severity: Fatal)
|
Message |
<SUB-SYSTEM>: Illegal event <EVENT-NAME> at state <STATE-NAME> |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
Used for Debugging. |
Event ID: 659 (Severity: Fatal)
|
Message |
<SUB-SYSTEM>: excessive reboots detected |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
Indicates that the OS has rebooted many times before establishing the. communication to the switch. This shows that x86 watchdog timer. expired unexpectedly. The switch won't bring-up the x86 after issuing this message. |
Event ID: 660 (Severity: Fatal)
|
Message |
<SLOT-ID> removed before shutdown completed |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
Indicates that the HPESP was removed before shutdown process was completed. |
Event ID: 661
|
Message |
<SLOT-ID> is safe for removal |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Information |
|
Description |
Indicates that the HPESP is safe for removal from the chassis. |
Event ID: 662 (Severity: Fatal)
|
Message |
<SUB-SYSTEM>: incompatible application version: <VERSION-STRING> |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
Indicates that application on the HPESP is not compatible with the current switch firmware |
Event ID: 664
|
Message |
<SLOT-ID> is shutting down |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Information |
|
Description |
Indicates that the HPESP application has initiated the shutdown process. |
Event ID: 665
|
Message |
<SLOT-ID> is rebooting |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Information |
|
Description |
Indicates that the x86 is rebooting. |
Event ID: 666
|
Message |
<SLOT-ID> is booting |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Information |
|
Description |
Indicates that the x86 is booting (i.e. loading the x86 OS.) |
Event ID: 667
|
Message |
<SLOT-ID> is ready |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Information |
|
Description |
Indicates that the booting of x86 is completed and the blade is ready. |
Event ID: 668
|
Message |
<SLOT-ID> HPLAP send TLV error condition %s on connection ID %d |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Information |
|
Description |
Indicates that the HPESP application incurred a transmit TLV failure. |
Event ID: 669
|
Message |
VLAN <VLAN_ID> caution <REASON-STRING> |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Information |
|
Description |
Informational warning regarding VLAN configuration. |
Event ID: 670 (Severity: Fatal)
|
Message |
FATAL-ERROR-STRING |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
Indicates to user fatals on read/updating of license |
Event ID: 671
|
Message |
LICENSING-INFO-MESSAGE |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Information |
|
Description |
Indicates to user on status of license update (successful/restored) |
Event ID: 672 (Severity: Warning)
|
Message |
APPLICATION-ERROR-MESSAGE |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Warning |
|
Description |
Indicates unexpected event occurred when accessing module's application data. |
Event ID: 673
|
Message |
<SLOT-ID> flash write aborted; write already in progress. |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Information |
|
Description |
Indicates write to flash aborted due to a write already in progress. |
Event ID: 1500
|
Message |
Start of eventIds used by |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Information |
|
Description |
The reason why the management has start of eventids used by |
Event ID: 1999
|
Message |
Start of eventIds used by 'ESPd code' executing on HPESP modules. Reserving block of 500 starting at 1500. These numbers must be consistent across all builds that the HPESP type modules will be used in. |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Information |
|
Description |
The reason why the management has start of eventids used by |
Event ID: 3761 (Severity: Fatal)
|
Message |
<TYPE STR> CPU board power fault |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
The reason why the management str has power fault on CPU board. |
Event ID: 3762 (Severity: Fatal)
|
Message |
<TYPE STR> mezzanine board power fault |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Fatal |
|
Description |
The reason why the management str has power fault on mezzanine board. |
Event ID: 3763
|
Message |
<TYPE STR> board power fault cleared |
|
Platforms |
KB |
|
Category |
HPESP |
|
Severity |
Information |
|
Description |
The reason why the management str has fault cleared. |
