Enterasys Security Router X-PeditionTM User Manual page 428

System Alarms and Events
Table A-6 High Severity Alarms/Events (continued)
Module Message
ETH1_ The ISR could not be connected
DRIV
ETH1_ Init string parse failure
DRIV
ETH1_ Unrecoverable error
DRIV
ETH1_ OS initialization failure
DRIV
ETH1_ Device not found
DRIV
ETH0_ The device is stuck in reset
DRIV
ETH0_ The ISR could not be connected
DRIV
ETH0_ Init string parse failure
DRIV
ETH0_ OS initialization failure
DRIV
CLI Failed to create session for web access
CLI Failed to create session for console access Failure to start session for the Web.
CLI Failed to create session for telnet access
CLI Failed to create session for telnet access
CLI Failed to enable Telnet server
CLI Failed to enable Telnet server
CLI Failed to enable Telnet server
CLI Failed to enable Telnet server
CLI CLI Config mode released by user
<username>
CLI CLI Config mode released by user
<username>
CLI CLI config mode released by startup-config Configuration mode is released when the startup-config script
A-6 Alarms/Events, System Limits, and Standard ASCII Table
Description
This is internal configuration alarm occurs because the interrupt
service routine (ISR) cannot be connected to the FastEthernet 2
interface/driver, rendering FastEthernet port 2 unavailable.
This internal configuration alarm is due to the driver being unable to
parse its initialization string, rendering FastEthernet port 2
unavailable.
The FastEthernet 2 chip on the motherboard has severe problems -
a catastrophic failure. The most likely cause is a hardware failure.
When this alarm occurs, FastEthernet port 2 is unavailable.
This internal configuration alarm occurs because the operating
system initialization of the driver/interface cannot be completed,
rendering FastEthernet port 2 unavailable.
Most likely this occurs due to a hardware failure - the FastEthernet 2
chip cannot be found on the PCI bus (of the motherboard). When this
occurs, FastEthernet port 2 is unavailable.
The FastEthernet 1 chip on the motherboard has severe problems -
it cannot come out of reset and the FastEthernet 1 driver/interface
cannot be started. The most likely cause is a hardware failure. When
this alarm occurs, FastEthernet port 1 is not available.
This internal configuration alarm occurs because the interrupt
service routine (ISR) cannot be connected to the FastEthernet 1
interface/driver, rendering FastEthernet port 1 unavailable.
This internal configuration alarm occurs because the driver could not
parse its initialization string, rendering FastEthernet port 1
unavailable.
This internal configuration alarm occurs because the operating
system initialization of the driver/interface cannot be completed,
rendering the FastEthernet 1 interface unavailable.
Failure to start session for the Web.
Failure to start session for console.
Failure to start session for Telnet.
Cannot start Telnet server because socket open failed.
Cannot start Telnet server because socket bind failed.
Cannot start Telnet server because socket listen failed.
Failure to enable the Telnet server.
A user exits Configuration mode.
An unknown user exits Configuration mode.
finishes execution.