Enterasys Security Router X-PeditionTM User Manual page 426

Enterasys security router user's guide
Table of Contents

Advertisement

System Alarms and Events
Table A-6 High Severity Alarms/Events (continued)
Module
Message
T1E1
Receiver has Loss of Frame (Yellow
Alarm).
T1E1
LOF alarm on receiver cleared.
T1E1
Transmitting Remote Alarm (Yellow
Alarm).
T1E1
Transmit Remote Alarm cleared.
SYNC_
The ISR could not be connected
DRIV
SYNC_
Init string parse failure
DRIV
SYNC_
Unrecoverable error
DRIV
SYNC_
OS initialization failure
DRIV
SYNC_
Device not found
DRIV
SNMP
Failed to enable SNMP server
SNMP
Failed to disable SNMP server
PLATF
System reset from <reason>, <warm|cold>
start
PLATF
Failed to initialize sysLog socket
PLATF
Failed to bind to sysLog port 514
ISDN
<BRI c/p>, SPID <spid string> Registered
(CES <1|2)
ISDN
<BRI c/p>, Unsolicited
SME_TERM_REGISTER_ACK
ISDN
<BRI c/p>, Registration Failed, Cause
<number>
ISDN
%s Layer 2 Terminal %d is DOWN
%s Layer 2 Terminal %d is UP
ISDN
%s Outgoing Call to %s %s Timed Out
ISDN
%s Switch Offers call for BUSY channel
%X
A-4 Alarms/Events, System Limits, and Standard ASCII Table
Description
T1/E1 physical port is detecting an OOF alarm.
T1/E1 physical port is not detecting an OOF alarm.
T1/E1 physical port is transmitting a remote alarm.
T1/E1 physical port is not transmitting a remote alarm.
Driver failed to connect the ISR to the BSP, so it will not start.
Driver could not parse the initialization string so it will not start.
XSR has an un-recoverable error.
The operating system failed to initialize the driver properly, so the
XSR cannot start.
XSR could not be found on the PCI bus, so the driver cannot start.
Failure to start SNMP server due to failure in the locking mechanism
or the message queue is full.
Failure to start SNMP server due to failure in the locking mechanism.
Warm or cold start occurs for the following reasons:
• Default config init: dcfg
• Crash reset: crsh
• CLI reset: cli
• SNMP reset: snmp
• Bootrom reset: btrm
• Software checksum invalid: cksm
Cannot create socket for sending syslogs.
Cannot bind to port 514 for sending syslogs.
BRI with a North American switch type successfully registers with the
central office.
BRI with a North American switch type registers with the central
office but fails.
BRI with a North American switch type registers with the central
office and fails. Causes include: 100 - SPID configuration error, 41 -
Network timeout and 1 - Fit timeout
Q921 - LAP-D status, UP is normal operation. Terminal is 1 for PRI.
For BRI it may be 1 or 2. 1 for ETSI and NTT. For North America 1
and 2 if two SPIDs are configured.
For basic-NET3 BRI, XSR was unable to activate the BRI line for an
outgoing call.
Error condition!

Advertisement

Table of Contents
loading

This manual is also suitable for:

X-pedition xsr

Table of Contents