2-148
Catalyst Supervisor Engine 32 PISA Cisco IOS System Message Guide, Release 12.2ZY
OL-11469-02
Chapter 2 Messages and Recovery Procedures
IDBMAN Messages
Error Message %HYPERION-5-BUS_SEQ_ERR: Constellation bus Sequence Error. Resetting
Hyperion ASIC.
Explanation
The switch processor has detected a sequence error on the backplane bus. A reset
sequence from the EARL has been called to recover from this error. System traffic should recover
and continue normally.
Recommended Action If traffic recovers, no action is required. If traffic does not recover, copy the
error message exactly as it appears on the console or in the system log. Enter the show platform
hardware hyperion all command to gather data that may help identify the nature of the error. If you
cannot determine the nature of the error from the error message text or from the show platform
hardware hyperion all output, contact your Cisco technical support representative, and provide the
representative with the gathered information.
Error Message %HYPERION-5-HYP_INIT_FAILURE: The Hyperion ASIC initialization failed
Explanation
The Hyperion ASIC initialization was not successful.
Recommended Action The Hyperion ASIC is not operational and is disabled.
Error Message %HYPERION-5-NULL_HYP_OBJECT: The Hyperion device object pointer is set
to NULL
Explanation
The memory location of the Hyperion ASIC device object is invalid.
Recommended Action The Hyperion ASIC operation is disabled, and the device interrupt is now
masked.
IDBMAN Messages
This section contains Interface Descriptor Block Manager (IDBMAN) messages.
IDBMAN-4
Error Message %IDBMAN-4-CONFIG_WRITE_FAIL: FFailed to generate confgiruation for
interface [chars]
Explanation
The system failed to generate a configuration for the specified interface because of a
problem with the file system. The active and standby supervisor engines will have configurations
that do not match.
Recommended Action The standby supervisor engine is reloaded automatically to recover from the
problem. If the standby supervisor engine does not recover, copy the message exactly as it appears
on the console or in the system log. Research and attempt to resolve the issue using the tools and
utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will
supply clarifying information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the