ELS Messages for Basic Rate Integrated Services Digital Network
- Level:
- CE-ERROR
- Short Syntax:
- BRI.001 I_ERR (0x status
) len( msglen
) on rcv dev device name
- Long Syntax:
- BRI.001 Packet received with I_ERR set (status = 0x status
) or bad length( msglen
), on device device name
- Description:
- YDC ISDN: isdny_rx() received a buffer from the driver with the error
flag set or with a length less than the minimum.
- Action:
- Report this event to customer service.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.002 RX bad type (0x type
) on dev device name
- Long Syntax:
- BRI.002 Received an unrecognized packet type (0x type
), on device device name
- Description:
- YDC ISDN: isdny_rx() received a packet with an unrecognized type.
- Action:
- Report this event to customer service.
- Level:
- C-INFO
- Short Syntax:
- BRI.003 ConnID 0x ConnID
Status msg cause (0x cause0
:0x cause1
) message
on dev device name
- Long Syntax:
- BRI.003 ConnID (0x ConnID
) Received a status message from the BRI device: Cause field 0x cause0
:0x cause1
( message
) on device device name
- Description:
- isdny_rx() received a status message from the BRI device.
- Level:
- C-INFO
- Short Syntax:
- BRI.004 ConnID 0x ConnID
message
" displaystring
" (cause 0x cause0
:0x cause1
) on dev device name
- Long Syntax:
- BRI.004 ConnID (0x ConnID
) received a message
( displaystring
) from the BRI device: Cause field 0x cause0
:0x cause1
on device device name
- Description:
- isdny_rx() received an NLS Display Information status message from
the BRI device. This may reflect error conditions at the network
interface.
- Action:
- If the network interface will not come up, contact customer service,
and/or your local service provider.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.005 ConnID 0x ConnID
Bad msg (0x message
) in stt state
, sts 0x status
, len length
, cse(0x cause1
:0x cause2
) dev device name
- Long Syntax:
- BRI.005 ConnID 0x ConnID
received an unexpected message (0x message
) in state state
, status 0x status
, length length
, cause (0x cause1
:0x cause2
) on device device name
- Description:
- isdny_rx() received an unexpected packet in its current state.
- Action:
- Report this event to customer service.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.006 Bad Config dev device name
- Long Syntax:
- BRI.006 The BRI configuration for device device name
is bad.
- Description:
- The configuration of the BRI device is
incomplete, missing, or inconsistent.
- Action:
- Verify that the BRI configuration for this device includes at least
the Local Address.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.007 Download failed (0x dlstat
), PUD status(0x pudstat
) dev device name
- Long Syntax:
- BRI.007 Download of the BRI device failed with status 0x dlstat
, Power-Up Diagnostics code 0x pudstat
for device device name
.
- Description:
- Either power-up diagnostics results inhibit download, or the
download image itself was corrupted.
- Action:
- Report this event to customer service.
- Level:
- C-INFO
- Short Syntax:
- BRI.008 Download OK, PUD status (0x pudstat
) dev device name
- Long Syntax:
- BRI.008 Download of the BRI device succeeded, Power-Up Diagnostics returned 0x pudstat
for device device name
.
- Description:
- Download of the BRI device completed normally.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.009 Config bad st (0x cfgstat
) dev device name
- Long Syntax:
- BRI.009 The BRI device rejected configuration with the status 0x cfgstat
for device device name
.
- Description:
- Part of the BRI device configuration is inconsistent or missing.
- Action:
- Report this event to customer service.
- Level:
- C-INFO
- Short Syntax:
- BRI.010 Config ok dev device name
- Long Syntax:
- BRI.010 Configuration of the BRI device succeeded for device device name
.
- Description:
- Configuration of the BRI device completed normally.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.011 Board Down DCT flags in (0x idctst
) out (0x odctst
) dev device name
- Long Syntax:
- BRI.011 INIDEV of the BRI device failed, DCT flags for input and output are 0x idctst
and 0x odctst
respectively for device device name
.
- Description:
- The BRI device isn't responding to driver initialization attempts.
- Action:
- Test the device. If this does not correct the problem,
restart the router. Report this error to customer service.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.012 Dead Board dev device name
- Long Syntax:
- BRI.012 The BRI device for device device name
is dead.
- Description:
- The BRI device is not responding at all. A router
restart is required (at minimum).
- Action:
- Verify that the correct slot was specified in the device configuration,
and restart the card. If it still fails, reseat the card in the
router. Lastly, contact customer service and report a hardware
failure.
- Level:
- U-INFO
- Short Syntax:
- BRI.013 Board reset complete dev device name
- Long Syntax:
- BRI.013 The BRI device for device device name
has been reset. Attempting download.
- Description:
- The board crashed. As the first step in recovering, we reset it.
- Action:
- Report this event to customer service.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.014 Unexpected state ( state1
) instead of state2
dev device name
- Long Syntax:
- BRI.014 BRI handler state ( state1
) is different from that expected ( state2
) for internal event on device device name
.
- Description:
- An event occurred in a state that is inconsistent with the
design of the FSM.
- Action:
- Report this event to customer service.
- Level:
- C-INFO
- Short Syntax:
- BRI.015 Chn channel
FSM st state1
ev event
-> state2
dev device name
- Long Syntax:
- BRI.015 Channel channel
FSM transition occurred: old state state1
, event event
, new state state2
on device device name
.
- Description:
- An FSM transition occurred.
- Level:
- U-INFO
- Short Syntax:
- BRI.016 Chn channel
ConnID 0x ConnID
FSM odd stt state1
ev event
-> state2
dev device name
- Long Syntax:
- BRI.016 Channel channel
ConnID 0x ConnID
unusual FSM state transition occurred: old state state1
, event event
, new state state2
on device device name
.
- Description:
- A transition occurred in the BRI handler's channel FSM contrary to
the normal path, because of resource shortages, or synchronization
problem between the device and the router.
- Action:
- Report this event to customer service.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.017 Chn channel
N-CONN-RQ bad iostat 0x status
dev device name
- Long Syntax:
- BRI.017 An N-CONN-RQ I/O request for channel channel
completed with status 0x status
device device name
.
- Description:
- The BRI handler sent an N-CONN-RQ to the device,
but the transfer did not complete successfully.
- Action:
- Report this event to customer service.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.018 No Hchn channel
A-DISC-RQ dev device name
- Long Syntax:
- BRI.018 A client issued a disconnect request for a connection ( channel
) unrecognized by the handler on device device name
.
- Description:
- A client of the BRI handler issued a disconnect request
(isdny_client_DR) for a connection unknown to the handler.
This indicates a serious synchronization problem between the handler
and its client.
- Action:
- Report this event to customer service.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.019 Bd stats cmp sts 0x status
dev device name
- Long Syntax:
- BRI.019 A statistics request to the device was returned with a bad status (0x status
) for device device name
.
- Description:
- The handler for the CNX YDC BRI device regularly issues statistics
requests to the BRI device, and the status on this request was bad.
This may indicate a slight congestion problem on the control queue
between the router and the device, or, if it persists, it may indicate
a problem with the device.
- Action:
- If this problem persists, test the BRI device. If it is
a persistent problem, report the event to customer service.
- Level:
- U-TRACE
- Short Syntax:
- BRI.020 Chn channel
ConnID 0x ConnID
Rxd Dt Pkt ln msglen
bd stt state
dev device name
- Long Syntax:
- BRI.020 Channel channel
ConnID 0x ConnID
: received a Data Packet of length ( msglen
) in wrong state ( state
) from device device name
.
- Description:
- The handler for the CNX YDC BRI device received a data packet for the
indicated channel, but the channel was not in Data Transfer state.
This may delay the establishment of the Serial Link over the connection
for several seconds. This usually indicates a misordering in the
receipt of signalling and data packets from the BRI device.
- Action:
- Report this event to customer service.
- Level:
- P-TRACE
- Short Syntax:
- BRI.021 Chn channel
ConnID 0x ConnID
RxD Pkt ln msglen
dev device name
- Long Syntax:
- BRI.021 Channel channel
ConnID 0x ConnID
received a Data Packet of length ( msglen
) from device device name
.
- Description:
- The handler for the CNX YDC BRI device received a data packet for the
indicated channel in Data Transfer state.
- Level:
- U-TRACE
- Short Syntax:
- BRI.022 ConnID 0x ConnID
Rxd msgtype
Pkt ln msglen
bd stt state
dev device name
- Long Syntax:
- BRI.022 ConnID 0x ConnID
received a msgtype
Packet of length ( msglen
) in wrong state ( state
) from device device name
.
- Description:
- The handler for the CNX YDC BRI device received a control packet for the
indicated channel, but the channel was not in the appropriate state.
- Action:
- Report this event to customer service.
- Level:
- C-TRACE
- Short Syntax:
- BRI.023 ConnID 0x ConnID
Rxd N_STAT_IN ln msglen
cause 0x cause1
:0x cause2
dev device name
- Long Syntax:
- BRI.023 ConnID 0x ConnID
received a N_STAT_IN message of length ( msglen
) cause 0x cause1
:0x cause2
from device device name
.
- Description:
- The handler for the CNX YDC BRI device received a Status Indication
for the indicated connection.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.024 Start Rq bd st (0x startstatus
) dev device name
- Long Syntax:
- BRI.024 The BRI device rejected a N_START_RQ with the status 0x startstatus
for device device name
.
- Description:
- The BRI device is not in a consistent state with the handler.
- Action:
- Report this event to customer service.
- Level:
- C-INFO
- Short Syntax:
- BRI.025 Start ok dev device name
- Long Syntax:
- BRI.025 Start of the BRI device succeeded for device device name
.
- Description:
- Start of the BRI device completed normally.
- Level:
- C-INFO
- Short Syntax:
- BRI.026 Hndlr inidev() st state
dev device name
- Long Syntax:
- BRI.026 Handler inidev() from state state
for device device name
.
- Description:
- Initialization of the BRI device by the device handler.
- Level:
- C-INFO
- Short Syntax:
- BRI.027 Hndlr N_START_RQ dev device name
- Long Syntax:
- BRI.027 Handler sent N_START_RQ for device device name
.
- Description:
- N_START_RQ sent to the BRI device.
- Level:
- C-INFO
- Short Syntax:
- BRI.028 Can't N_START_RQ DCT i/o flg (0x istatus
:0x ostatus
) dev device name
- Long Syntax:
- BRI.028 Either the device status (0x istatus
:0x ostatus
) or the lack of a buffer prevented an N_START_RQ to the BRI CNX YDC port for device device name
.
- Description:
- The handler has to send an N_START_RQ to initiate transfers, but can't.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.029 Brd Crsh -- rstrng: dev device name
- Long Syntax:
- BRI.029 Device software crash, attempting restart dev device name
- Description:
- The BRI CNX YDC board software has crashed (LOG_EXIT).
- Action:
- Report this event to customer service.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.030 Tx Frm too long ( frame
> configsize
) dev device name
- Long Syntax:
- BRI.030 The size of the frame ( frame
) passed to the BRI handler for transmission exceeded the maximum size configured ( configsize
-- less one) device device name
- Description:
- The BRI CNX YDC card restricts the transmit size to
be one less than the maximum configured, and discards any
frames that exceed this length. Check the encapsulator
packet size. It should be smaller than the BRI frame size
less one and less any encapsulator headers.
- Level:
- U-INFO
- Short Syntax:
- BRI.031 Cll rfsd frm FromAddress
: FromSubAddress
to ToAddress
: ToSubAddress
on dev device name
- Long Syntax:
- BRI.031 Incoming Call Refused from FromAddress
: FromSubAddress
to ToAddress
: ToSubAddress
on device device name
- Description:
- An N_CONN_IND was received from the BRI device, but no registered
client chose to accept it.
- Action:
- Check the reported address against those configured. It may be that
the remote router's configuration is in error, or that some device
on the BRI network is calling the wrong number.
- Level:
- C-INFO
- Short Syntax:
- BRI.032 Chn Channel
ConnID 0x ConnID
Cll Txcmp on dev device name
- Long Syntax:
- BRI.032 Channel Channel
ConnID 0x ConnID
: transfer of N_CONN_RQ to BRI device completed on device device name
- Description:
- A connection has been successfully initiated.
- Level:
- C-INFO
- Short Syntax:
- BRI.033 Chn Channel
ConnID 0x ConnID
FSM st state1
ev event
-> state2
dev device name
- Long Syntax:
- BRI.033 Channel Channel
ConnID 0x ConnID
FSM transition: old state state1
, event event
, new state state2
on device device name
.
- Description:
- An FSM transition occurred.
- Level:
- U-INFO
- Short Syntax:
- BRI.034 Chn UN, ConnID UNAS, callout rfsd (no chnl/destrsp) dev device name
- Long Syntax:
- BRI.034 Channel (unassigned), ConnID (unassigned), call out refused (no channel available, or destination not responding) on device device name
.
- Description:
- Connection setup failed, either because no spare channel was available,
or the destination has refused (retry-count) previous calls within
the timeout period. In the latter case, a subsequent attempt will
proceed once the timeout has expired.
- Action:
- Verify that the address configured for the dial circuits is correct,
and that at least one of the two channels (locally and at the
destination) is currently unassigned.
- Level:
- U-INFO
- Short Syntax:
- BRI.035 Inv Chn (0x Channel
) ConnID 0x ConnID
ev message
dev device name
- Long Syntax:
- BRI.035 Invalid Channel (0x Channel
) ConnID 0x ConnID
in message message
on device device name
.
- Description:
- The channel type in a message received from the device was
invalid. The message was ignored or rejected.
- Action:
- This may indicate that the ISDN switch to which the device
is connected is trying to initialize connections on channels that the
software cannot recognize. One instance of note may be the
unassigned value (reported as 0xFF, but actually 0x0), which, if
it persists, may prevent any connections. Contact customer
service.
happen", so the firmware and the interface between the software and
the firmware can't deal with it (the router has no way to indicate
which channel to use for an inbound connection).
- Level:
- ALWAYS
- Short Syntax:
- BRI.036 Bad drct Tx prot Protocol
, remap to dial circuit on dev device name
- Long Syntax:
- BRI.036 Some forwarder ( Protocol
) has attempted to transmit directly over the BRI device device name
- Description:
- Transmits over the BRI device are only supposed to be done via an
associated dial circuit, which will do an appropriate encapsulation.
This event was caused by a mistake in the configuration of the
forwarders. No forwarder should be configured to use the BRI device.
To bound the number of these messages, they will be logged only a
fraction of the actual events.
- Cause:
- A forwarder (IP, IPX, etc) address was assigned to the BRI
device.
- Action:
- Delete the address, and (probably) re-assign it to a dial circuit
(which is itself mapped to the BRI device).
- Cause:
- The bridge or other forwarder has been configured to use the BRI
device.
- Action:
- Remove the BRI device as a port used by the bridge or forwarder.
- Level:
- UE-ERROR
- Short Syntax:
- BRI.037 Stat Rq bd st (0x startstatus
) dev device name
- Long Syntax:
- BRI.037 The BRI device rejected a N_STAT_RQ (parameter download) with the status 0x startstatus
for device device name
.
- Description:
- The BRI device failed to accept the configuration parameters
sent down by the router and initialize properly.
- Action:
- Report this event to customer service.
- Level:
- C-INFO
- Short Syntax:
- BRI.038 Parameter download ok dev device name
- Long Syntax:
- BRI.038 Parameter download for the BRI device succeeded for device device name
.
- Description:
- The BRI device accepted and initialized correctly with the configuration
parameters passed down from the router.
- Level:
- C-INFO
- Short Syntax:
- BRI.039 Hndlr N_STAT_RQ dev device name
- Long Syntax:
- BRI.039 Handler sent N_STAT_RQ for device device name
.
- Description:
- N_STAT_RQ sent to the BRI device.
- Level:
- C-INFO
- Short Syntax:
- BRI.040 Can't N_STAT_RQ DCT i/o flg (0x istatus
:0x ostatus
) dev device name
- Long Syntax:
- BRI.040 Either the device status (0x istatus
:0x ostatus
) or the lack of a buffer prevented an N_STAT_RQ to the BRI CNX port for device device name
.
- Description:
- The handler has to send an N_STAT_RQ for configuration parameter
download, but can't.
- Level:
- U-INFO
- Short Syntax:
- BRI.041 Too many non-resp, will try later dev device name
- Long Syntax:
- BRI.041 Too many non-responses, will try later on device device name
,.
- Description:
- The destination has refused (retry-count) previous calls within
the timeout period. A subsequent attempt will
proceed once the timeout has expired.
- Action:
- Verify that the address configured for the dial circuits is correct,
and that at least one of the two channels (locally and at the
destination) is currently unassigned.
- Panic
- isdnym
- Short Syntax:
- YDC ISDN: mem alloc fld
- Description:
- The YDC BRI device handler failed to allocate sufficient memory
during the initialization phase.
- Action:
- Contact customer service.
- Level:
- C-INFO
- Short Syntax:
- BRI.042 CBRI_Event
index index
state chan_state
- Long Syntax:
- BRI.042 CBRI_Event
index index
state chan_state
- Description:
- This is an informative ELS trace that prints out what Event is
occurring (i.e. a ConnInd, ConnCnf, DiscReq, DiscInd etc.....)
and also the index and channel state that we advance to.
- Level:
- C-INFO
- Short Syntax:
- BRI.043 BRI_event
index index
, physchan chn_no
- Long Syntax:
- BRI.043 BRI_event
index index
, physchan value given to us by the switch chn_no
- Description:
- An informative ELS trace that prints out what Event is occurring
(i.e. a ConnInd, ConnCnf, DiscReq, DiscInd etc.....) and also what
index and physchan we obtain from the switch BEFORE it is assigned
to pChan->physchan.
- Level:
- U-INFO
- Short Syntax:
- BRI.044 unusual_info_msg
- Long Syntax:
- BRI.044 unusual_info_msg
- Description:
- The message passed in 'unusual_info_msg' is printed. unusual_info_msg
covers a range of unusual messages that occur in the course of call
establishment.
- Action:
- If any of these messages repeatedly occur, contact customer service.
- Level:
- C-INFO
- Short Syntax:
- BRI.045 normal_info_msg
- Long Syntax:
- BRI.045 normal_info_msg
- Description:
- The message passed in 'normal_info_msg' is printed. normal_info_msg
covers a range of normal messages that occur in the course of success-
ful call establishment.
- Level:
- C-INFO
- Short Syntax:
- BRI.046 BRI_event
index index
, dialing ph# [ dial_addr
]
- Long Syntax:
- BRI.046 BRI_event
index index
, dialing ph# [ dial_addr
]
- Description:
- An informative ELS trace that prints out what Event is occurring
(i.e. a ConnInd, ConnCnf, DiscReq, DiscInd etc.....) and also what
index along with the dialing address and subaddress.
- Level:
- U-INFO
- Short Syntax:
- BRI.047 BRI_Event
Tossing DialNext occurring in chan_state
state
- Long Syntax:
- BRI.047 BRI_Event
Tossing DialNext occurring in chan_state
state
- Description:
- This is to indicate to the user that we are in a state other than
Call_Init, while trying to dial the next number.
- Level:
- C-INFO
- Short Syntax:
- BRI.048 str1
passed_str
str2
- Long Syntax:
- BRI.048 str1
passed_str
str2
- Description:
- This is used to prevent various other MISC Common-Info type of
ELS traces.