Table A-6 High Severity Alarms/Events (continued)
Module
Message
ISDN
Incoming Call <BRI | Serial card/
port:channel> Connected to <calling no.>
Unknown Call
ISDN
North American BRI Interface %d requires
SPID configuration
ISDN
Call <BRI | Serial card/port:channel>
Connected to <called_no.> Outgoing test
CALL
ISDN
Call <BRI | Serial card/port:channel>
Disconnected from <number> <Outgoing
test CALL | Unknown Call> Cause <passed
from central office>
ISDN
No Channel Available <destination name>
ISDN
_FILE _LINE Out of memory
ISDN
ISDN panic!!
ISDN
_FILE _LINE Out of memory
ISDN
_FILE _LINE Out of memory
ISDN
_FILE _LINE unexpected value
ISDN
Interface BRI, changed state to up
ISDN
Interface BRI, changed state to down
FR
Serial a/b:d.e, started
FR
Serial a/b:d.e, shutting down
FR
Serial a/b:d.e, station UP, DLCI nnnn
FR
Serial a/b:d.e, station DOWN, DLCI nnnn
FR
Serial a/b:d cannot establish LMI, port is
down
FR
Serial a/b:d LMI - port DOWN
FR
Serial a/b:d LMI - port UP
FR
Serial a/b:d.e Config Error Aggregate CIR
nnnn greater than measured speed nnn -
CIR Assist is DISABLED
ETH1_
The device is stuck in reset
DRIV
ETH1_
The device TX/RX is stuck in reset
DRIV
Description
An incoming call connected for test purposes will be disconnected
within 30 seconds.
Configuration error.
A test call is placed from the console.
A test call is disconnected due to the standard ISDN cause. E.g. 16:
normal clearing, 18: user does not answer.
ISDN line was over subscribed.
Unable to allocate memory.
Unable to create ISDN object.
Unable to allocate memory.
Unable to allocate memory.
Unexpected message received.
Port has changed to Up state.
Port has changed to Down state.
Output from the no shutdown command.
The interface has been manually shut down.
The network reports the station is up.
The network reports the station is up.
The network has not been responding for 5 minutes. You should
check the connection.
The LMI is reporting the port is Down.
The network is reporting the port is Up.
The total configured CIR exceeds the speed of the link and cannot
guarantee CIR. Assist will not be operational.
The FastEthernet 2 chip on the motherboard has severe problems -
it cannot come out of reset and the FastEthernet 2 driver/interface
cannot be started. The most likely cause is a hardware failure. When
this alarm occurs, FastEthernet Interface 2 is not available.
The FastEthernet 2 chip on the motherboard has severe problems -
either the transmitter or receiver cannot come out of reset and the
FastEthernet 2 driver/interface cannot be started. The most likely
cause of this alarm is a hardware failure, rendering FastEthernet port
2 unavailable.
System Alarms and Events
XSR User's Guide A-5
Need help?
Do you have a question about the Security Router X-PeditionTM and is the answer not in the manual?
Questions and answers