ELS Messages for Frame Relay Network Interface (FR)
- Level:
- C-INFO
- Short Syntax:
- FR.001 Frame received, PVC = circuit
protocol = protocol
nt network ID
- Long Syntax:
- FR.001 Frame received, PVC = circuit
protocol type = protocol
, on network network ID
- Description:
- A LAPD frame had been received on the FR interface.
- Level:
- C-INFO
- Short Syntax:
- FR.002 Frame transmitted PVC = circuit
protocol = protocol
dev device name
- Long Syntax:
- FR.002 Frame transmitted PVC = circuit
protocol type = protocol
, on device device name
- Description:
- A LAPD frame had been transmitted on the FR interface.
- Level:
- UE-ERROR
- Short Syntax:
- FR.003 Received data on invalid circuit, PVC = circuit
on nt network ID
- Long Syntax:
- FR.003 Data received on invalid or nonconfigured circuit, PVC = circuit
on network network ID
- Description:
- Data has been received on a circuit not configured or learned dynamically but not yet active on network.
- Cause:
- Network mis-configuration or mis-timing.
- Level:
- C-INFO
- Short Syntax:
- FR.004 Circuit outbound congestion PVC = circuit
dev device name
- Long Syntax:
- FR.004 Circuit outbound congestion PVC = circuit
, on device device name
- Description:
- The circuit is now experiencing congestion in the outbound direction.
- Level:
- C-INFO
- Short Syntax:
- FR.005 Circuit outbound uncongested PVC = circuit
dev device name
- Long Syntax:
- FR.005 Circuit outbound uncongested PVC = circuit
, on device device name
- Description:
- The circuit is now not experiencing congestion in the outbound direction.
- Level:
- C-INFO
- Short Syntax:
- FR.006 Circuit active PVC = circuit
dev device name
- Long Syntax:
- FR.006 Circuit enters active state PVC = circuit
, on device device name
- Description:
- The circuit enters the active state.
- Level:
- C-INFO
- Short Syntax:
- FR.007 Orphan circuit joins net PVC = circuit
dev device name
- Long Syntax:
- FR.007 An orphan circuit not statically configured has joined the network PVC = circuit
, on device device name
- Description:
- The LMI signalled present and active a circuit
which had not been statically configured.
- Level:
- C-INFO
- Short Syntax:
- FR.008 Circuit inactive PVC = circuit
dev device name
- Long Syntax:
- FR.008 Circuit enters inactive state PVC = circuit
, on device device name
- Description:
- The circuit enters the inactive state.
- Cause:
- The remote end-point on the circuit either is down or
is disabled.
network remote site and network administrator.
- Level:
- C-INFO
- Short Syntax:
- FR.009 Circuit unavailable PVC = circuit
dev device name
- Long Syntax:
- FR.009 Circuit is unavailable PVC = circuit
, on device device name
- Description:
- The circuit is no longer available on the network.
- Cause:
- The remote end-point on the circuit either is down or
is disabled.
network remote site and network administrator.
- Level:
- C-INFO
- Short Syntax:
- FR.010 Circuit available PVC = circuit
dev device name
- Long Syntax:
- FR.010 Circuit is available PVC = circuit
, on device device name
- Description:
- The circuit is now available on the network.
- Level:
- C-INFO
- Short Syntax:
- FR.011 LMI seq exchange requested rcv seq = rcvseq
xmt seq = xmtseq
dev device name
- Long Syntax:
- FR.011 LMI sequence number exchange requested, last received sequence = rcvseq
current transmit sequence = xmtseq
, on device device name
- Description:
- A LMI sequence number exchange has been requested.
- Level:
- C-INFO
- Short Syntax:
- FR.012 LMI Status Enquiry requested dev device name
- Long Syntax:
- FR.012 LMI Status Enquiry requested on device device name
- Description:
- A LMI full Status Enquiry has been requested.
- Level:
- C-INFO
- Short Syntax:
- FR.013 LMI solicited Status Enquiry response received dev device name
- Long Syntax:
- FR.013 LMI solicited Status Enquiry response had been received on device device name
- Description:
- A solicited LMI Status Enquiry response has been received.
- Level:
- C-INFO
- Short Syntax:
- FR.014 DROP: Bridge port not fwding on PVC= circuit
, nt network ID
- Long Syntax:
- FR.014 DROP: Bridge port not forwarding on PVC= circuit
, network network ID
- Description:
- A bridge frame is being discarded as a bridge port is not in
forwarding state.
- Cause:
- It could be that port has just come up and is progressing from
blocking to listening to learning to forwarding state, or that
Spanning Tree Protocol has determined that this port should
stay in blocked state as a backup port.
- Level:
- UE-ERROR
- Short Syntax:
- FR.015 Circuit not found nt network id
circ circ
- Long Syntax:
- FR.015 Circuit can't be found network network id
circuit circ
- Description:
- An outbound frame could not be sent because there was no circuit
defined for the destination DLCI.
- Level:
- C-INFO
- Short Syntax:
- FR.016 Multicast frame transmitted PVC = circuit
protocol = protocol
nt network ID
- Long Syntax:
- FR.016 Multicast frame transmitted PVC = circuit
protocol type = protocol
, on network network ID
- Description:
- A LAPD frame had been transmitted on the FR interface.
- Level:
- C-INFO
- Short Syntax:
- FR.017 Circuit remains outbound congested PVC = circuit
dev device name
- Long Syntax:
- FR.017 Circuit remains congested in the outbound direction PVC = circuit
, on device device name
- Description:
- The circuit is remaining in the outbound congested state toward the network.
- Level:
- UE-ERROR
- Short Syntax:
- FR.018 No memory for internal module module
chid chid
- Long Syntax:
- FR.018 No memory for an internal module module
channel-id chid
- Description:
- Unable to allocate memory required to open the module
displayed in the message.
- Level:
- C-INFO
- Short Syntax:
- FR.019 Orphan circuit ignored PVC = circuit
dev device name
- Long Syntax:
- FR.019 An disallowed orphan circuit not statically configured has been ignored the network PVC = circuit
, on device device name
- Description:
- The LMI signalled present and active a circuit
which had not been statically configured or allowed.
- Level:
- C-INFO
- Short Syntax:
- FR.020 Circuits exceeded, orphan circuit discarded PVC = circuit
dev device name
- Long Syntax:
- FR.020 The total circuits allowed has been exceeded, an orphan circuit has been ignored PVC = circuit
, on device device name
- Description:
- The LMI signalled present and active a circuit
which cannot join the interface, maximum circuits have been exceeded.
- Level:
- C-INFO
- Short Syntax:
- FR.021 No memory for orphan, circuit discarded PVC = circuit
dev device name
- Long Syntax:
- FR.021 No available memory for orphan circuit, the circuit has been ignored PVC = circuit
, on device device name
- Description:
- The LMI signalled present and active a circuit
which cannot join the interface, memory is unavailable.
- Level:
- UE-ERROR
- Short Syntax:
- FR.022 Unsupported LMI IE, type = type
on dev device name
- Long Syntax:
- FR.022 Unsupported LMI information element, type = type
on device device name
- Description:
- An unsupported management information element has been encountered.
- Cause:
- Software out of date, contact customer service.
- Level:
- UE-ERROR
- Short Syntax:
- FR.023 Unsupported LMI message, type = type
dev device name
- Long Syntax:
- FR.023 Unsupported LMI message type, type encountered = type
, on device device name
- Description:
- An unsupported management message has been encountered.
- Cause:
- Software out of date, contact customer service.
- Level:
- C-INFO
- Short Syntax:
- FR.024 Multicast circuit joins net PVC = circuit
, group = group
dev device name
- Long Syntax:
- FR.024 An multicast circuit has joined the network PVC = circuit
, in mulitcast group = group
on device device name
- Description:
- The LMI signalled present and active a multicast circuit.
- Level:
- UE-ERROR
- Short Syntax:
- FR.025 Data type data_type
already in use nt network id
- Long Syntax:
- FR.025 Data type data_type
already in use network network id
- Description:
- This data type connection already exists, so FRVC refused the
connection.
- Level:
- UE-ERROR
- Short Syntax:
- FR.026 Unsupported NLPID, type = type
, PVC = circuit
on nt network ID
- Long Syntax:
- FR.026 Unsupported Network Layer Protocol ID, type = type
from PVC = circuit
on network network ID
- Description:
- An unsupported network layer protocol NLPID has been encountered.
- Cause:
- Software out of date or incompatible, contact customer service.
- Level:
- UE-ERROR
- Short Syntax:
- FR.027 Unsupported ethertype, type = type
, PVC = circuit
on nt network ID
- Long Syntax:
- FR.027 Unsupported ethernet type, type = type
from PVC = circuit
on network network ID
- Description:
- An unsupported Ethernet type has been encountered.
- Cause:
- Software out of date or incompatible, contact customer service.
- Level:
- C-INFO
- Short Syntax:
- FR.028 Unsupported multicast circuit ignored PVC = circuit
, group = group
nt network ID
- Long Syntax:
- FR.028 An unsupported multicast circuit has been ignored, PVC = circuit
, in mulitcast group = group
on network network ID
- Description:
- The LMI signalled present and active a multicast circuit that is not
supported on the interface.
- Level:
- UE-ERROR
- Short Syntax:
- FR.029 Received data on invalid circuit, PVC = circuit
on dev device name
- Long Syntax:
- FR.029 Data received on invalid or nonconfigured circuit, PVC = circuit
on device device name
- Description:
- Data has been received on a circuit not configured or learned dynamically but not yet active on network.
- Cause:
- Network mis-configuration or mis-timing.
- Level:
- C-INFO
- Short Syntax:
- FR.030 LMI seq exchange received rcv seq = rcvseq
xmt seq = xmtseq
dev device name
- Long Syntax:
- FR.030 LMI sequence number exchange received, last received sequence = rcvseq
current transmit sequence = xmtseq
, on device device name
- Description:
- A LMI sequence number exchange has been received.
- Level:
- C-INFO
- Short Syntax:
- FR.031 LMI unsolicited PVC Status Update received dev device name
- Long Syntax:
- FR.031 LMI unsolicited single Status Update had been received on device device name
- Description:
- An LMI unsolicited single status update message has been received.
- Level:
- UE-ERROR
- Short Syntax:
- FR.032 Circuit address length too short dev device name
- Long Syntax:
- FR.032 Circuit address length less than the 2 octet minimum received on device device name
- Description:
- The router encountered a LAPD frame containing less than the 2 octet
minimum address length.
- Level:
- UE-ERROR
- Short Syntax:
- FR.033 Circuit address length too large dev device name
- Long Syntax:
- FR.033 Circuit address length greater than the 2 octet maximum received on device device name
- Description:
- The router encountered a LAPD frame containing greater than the 2
octet maximum address length that it supports. Currently, the router
supports only 2 octet addresses.
- Level:
- UE-ERROR
- Short Syntax:
- FR.034 Circuit status message using reserved address, PVC = circuit
dev device name
- Long Syntax:
- FR.034 Circuit status update message contained a reserved management channel address, PVC = circuit
, on device device name
- Description:
- The LMI status message contained a reserved management channel address.
- Level:
- UE-ERROR
- Short Syntax:
- FR.035 Unsupported control frame, type = type
, PVC = circuit
on dev device name
- Long Syntax:
- FR.035 Unsupported Link Layer control frame encountered, type = type
from PVC = circuit
on device device name
- Description:
- An unsupported link layer control frame encountered.
- Cause:
- Software out of date or incompatible, contact customer service.
- Level:
- UE-ERROR
- Short Syntax:
- FR.036 Unsupported management protocol descriptor, type = type
on dev device name
- Long Syntax:
- FR.036 Unsupported layer management protocol descriptor encountered, type = type
on device device name
- Description:
- An unsupported network layer protocol descriptor has been encountered.
- Cause:
- Software out of date or incompatible, contact customer service.
- Level:
- UE-ERROR
- Short Syntax:
- FR.037 Unsupported management call reference encountered on dev device name
- Long Syntax:
- FR.037 Unsupported layer management call reference encountered on device device name
- Description:
- An unsupported network layer call reference field has been encountered.
- Cause:
- Software out of date or incompatible, contact customer service.
- Level:
- UE-ERROR
- Short Syntax:
- FR.038 No lock shift encountered in ANSI LMI message on dev device name
- Long Syntax:
- FR.038 No lock shift encountered in received ANSI LMI message on device device name
- Description:
- The received ANSI management frame did not include required locking
shift information element.
- Cause:
- Error in network switch management frame, contact site administrator.
- Level:
- UE-ERROR
- Short Syntax:
- FR.039 Incorrect formated information element encountered on dev device name
- Long Syntax:
- FR.039 Incorrect formated information element encountered on device device name
- Description:
- The received management frame information element was incorrectly
formated.
- Cause:
- Error in network switch management frame, contact site administrator.
- Level:
- UE-ERROR
- Short Syntax:
- FR.040 LMI rcv seq number in error seq = rcvseq
expected seq = xmtseq
dev device name
- Long Syntax:
- FR.040 LMI receive sequence number in error, receive sequence = rcvseq
expected sequence = xmtseq
, on device device name
- Description:
- An incorrect LMI receive sequence number has been received.
- Level:
- C-INFO
- Short Syntax:
- FR.041 Circuit leaves net PVC = circuit
dev device name
- Long Syntax:
- FR.041 An circuit has been removed from the network PVC = circuit
, on device device name
- Description:
- The LMI failed to signal the mentioned circuit is last network status
update message. Circuit assumed removed from network.
- Level:
- C-INFO
- Short Syntax:
- FR.042 Circuit inbound congestion PVC = circuit
dev device name
- Long Syntax:
- FR.042 Circuit inbound congestion PVC = circuit
, on device device name
- Description:
- The circuit is now experiencing congestion in the inbound direction.
- Level:
- UE-ERROR
- Short Syntax:
- FR.043 Incorrect formatted addr hdr for LMI packet encountered on dev device name
- Long Syntax:
- FR.043 Incorrect formatted address header for LMI packet encountered on device device name
- Description:
- The address header on received management frame had BECN, FECN, DE or
CR bits set.
- Cause:
- Error in network switch management frame, contact site administrator.
- Level:
- UE-ERROR
- Short Syntax:
- FR.044 Unsolicited LMI LIV received on dev device name
- Long Syntax:
- FR.044 Unsolicited LMI Link Integrity Verification received on device device name
- Description:
- LMI Link Integrity Verification message was received from the network
without the router polling for it.
- Cause:
- Duplicate packet may have been sent. Monitor LMI link and contact
site administrator.
- Level:
- UE-ERROR
- Short Syntax:
- FR.045 Unsolicited LMI FULL STATUS received on dev device name
- Long Syntax:
- FR.045 Unsolicited LMI FULL STATUS response received on device device name
- Description:
- LMI Full Status message was received from the network without the
router polling for it.
- Cause:
- Duplicate packet may have been sent. Monitor LMI link and contact
site administrator.
- Level:
- UE-ERROR
- Short Syntax:
- FR.046 DROP: Bridging not enabled on PVC= circuit
, nt network ID
- Long Syntax:
- FR.046 DROP: Bridging not enabled on PVC= circuit
, network network ID
- Description:
- A frame was received of a bridge type defined in RFC 1490.
However, since bridging has not been enabled on this circuit, frame
is being discarded.
- Cause:
- In a Point-to-Point WAN connection, this indicates that bridging
is enabled on one end point router, and disabled on another.
This is an illegal configuration.
- Action:
- Either enable proper bridging behavior on both ends of the circuit
or disable bridging on the bridge ports connected to this PVC.
In other words, you must enable or disable bridging at both ends
of the circuit.
- Level:
- C-INFO
- Short Syntax:
- FR.047 DROP: Bridge port not fwding on PVC= circuit
dev device name
- Long Syntax:
- FR.047 DROP: Bridge port not forwarding on PVC= circuit
, device device name
- Description:
- A bridge frame is being discarded as a bridge port is not in
forwarding state.
- Cause:
- It could be that port has just come up and is progressing from
blocking to listening to learning to forwarding state, or that
Spanning Tree Protocol has determined that this port should
stay in blocked state as a backup port.
- Level:
- UE-ERROR
- Short Syntax:
- FR.048 DROP: source_mac
-> dest_mac
, Frame to bdg port behav mismatch on PVC= circuit
, nt network ID
- Long Syntax:
- FR.048 DROP: source_mac
-> dest_mac
, Frame to bridge port behavior mismatch on PVC= circuit
, network network ID
- Description:
- A bridged frame has been received and is being discarded due to mismatch
in the frame type versus the bridge port behavior.
- Cause:
- Either a source routed frame was received on a bridge port where
source routing is disabled, or a transparent frame was received on
a bridge port where transparent bridging is disabled.
- Action:
- Enable proper bridging behavior on both ends of the circuit,
or disable bridging on the bridge ports connected to this PVC.
- Level:
- UE-ERROR
- Short Syntax:
- FR.049 Unsupported bdg frame type = type
, PVC = circuit
on nt network ID
- Long Syntax:
- FR.049 Unsupported bridge frame type = type
from PVC = circuit
on network network ID
- Description:
- An unsupported bridge frame type has been encountered.
- Cause:
- Software out of date or incompatible, contact customer service.
- Level:
- UI-ERROR
- Short Syntax:
- FR.050 Unrecgnz outgoing bdg frame type = type
on PVC= circuit
on nt network ID
- Long Syntax:
- FR.050 Unrecognized outgoing bridge frame type = type
on PVC = circuit
on network network ID
- Description:
- An unrecognized outgoing bridge frame type. Bridge has asked the
Frame Relay interface to send out a frame whose type cannot be
translated into encapsulation defined in RFC 1490.
- Cause:
- Software out of date or incompatible, contact customer service.
- Level:
- C-INFO
- Short Syntax:
- FR.051 Transmit frame discarded PVC = circuit
protocol = protocol
dev device name
- Long Syntax:
- FR.051 Transmit frame discarded PVC = circuit
protocol type = protocol
, on device device name
- Description:
- A protocol frame has been discarded because it could not be
queued for transmission.
- Cause:
- There is a buffer shortage, or the Bandwidth Reservation queue
has reached its maximum length.
- Level:
- UE-ERROR
- Short Syntax:
- FR.052 LMI snd seq number in error seq = sndseq
dev device name
- Long Syntax:
- FR.052 LMI send sequence number in error, sequence = sndseq
, on device device name
- Description:
- An LMI send sequence number of 0 has been received.
- Level:
- UE-ERROR
- Short Syntax:
- FR.053 DN bd ln actual_length
claimed_length
, PVC = circuit
nt network id
- Long Syntax:
- FR.053 DECnet packet received with a bad length actual actual_length
claimed claimed_length
on PVC = circuit
, network network id
- Description:
- A DECnet packet was received with a length field that was larger than
the actual length of the packet.
- Level:
- C-INFO
- Short Syntax:
- FR.054 Rqd DLCI required_dlci
unavail nt network id
; cont tst
- Long Syntax:
- FR.054 Required DLCI required_dlci
unavailable on network network id
; continue testing interface
- Description:
- The switch does not offer a Data Link Connection Identifier (DLCI)
with the Required attribute, so the router continues the interface
self-test.
- Level:
- C-INFO
- Short Syntax:
- FR.055 Rqd DLCI required_dlci
rmvd nt network id
; start testing
- Long Syntax:
- FR.055 Required DLCI required_dlci
removed from network network id
; start testing interface
- Description:
- The switch does not offer a Data Link Connection Identifier (DLCI)
with the Required attribute, so the router is testing the interface.
- Level:
- C-INFO
- Short Syntax:
- FR.056 No DLCIs nt network id
; testing
- Long Syntax:
- FR.056 No DLCIs present on network network id
; testing interface
- Description:
- The switch does not offer a Data Link Connection Identifier (DLCI)
and the interface has the NO-PVC attribute set, so the router is
testing the interface.
- Level:
- UE-ERROR
- Short Syntax:
- FR.057 module
mod init fld nt network id
- Long Syntax:
- FR.057 module
module initialisation failed network network id
- Description:
- A CODE module failed to initialise correctly and so will now
be deleted. Look for other messages that indicate the cause
of the failure.
- Level:
- UE-ERROR
- Short Syntax:
- FR.058 FRMGR no more clnt sub-chs available dev device name
- Long Syntax:
- FR.058 FRMGR has no more client sub channels available device device name
- Description:
- The Frame Relay VC Manager (FRMGR) is unable to accept a new
Frame Relay Encapsulator client because it has run out of
available sub channels.
- Level:
- UE-ERROR
- Short Syntax:
- FR.059 No free buffers dev device name
- Long Syntax:
- FR.059 No free buffers device device name
- Description:
- An attempt to allocate a buffer failed.
- Level:
- UE-ERROR
- Short Syntax:
- FR.060 Buf error dev device name
- Long Syntax:
- FR.060 Buffer received with error bit set device device name
- Description:
- A buffer was received by the FRMGR with the error bit set.
- Action:
- Contact customer service.
- Level:
- C-INFO
- Short Syntax:
- FR.061 LMI not initialized yet dev device name
- Long Syntax:
- FR.061 LMI is not initialized yet device device name
- Description:
- The incoming frame is discarded because the LMI has not yet
been initialized.
- Level:
- UI-ERROR
- Short Syntax:
- FR.062 FRMGR has no clients dev device name
- Long Syntax:
- FR.062 FRMGR has no clients device device name
- Description:
- The FRMGR service has no clients to pass the incoming frame
to, so the frame is dropped.
- Level:
- UE-ERROR
- Short Syntax:
- FR.063 FRMGR dev device name
scid scid
receive failed err
- Long Syntax:
- FR.063 FRMGR device device name
sub-channel scid
receive failed err
- Description:
- An upstream module on the given sub-channel id failed to receive
a frame. The error is given and the frame is not sent to that
sub-channel stack.
- Level:
- UE-ERROR
- Short Syntax:
- FR.064 Can't send mcast, no act circs nt network id
- Long Syntax:
- FR.064 Can't send multicast, no active circuits network network id
- Description:
- There are no active circuits to send the requested multicast
frame on. The frame is dropped.
- Level:
- UE-ERROR
- Short Syntax:
- FR.065 Circuit not found nt device name
dev circ
- Long Syntax:
- FR.065 Circuit can't be found device device name
circuit circ
- Description:
- An outbound frame could not be sent because there was no circuit
defined for the destination DLCI.
- Level:
- C-INFO
- Short Syntax:
- FR.066 Circ circ
reg'd with scid scid
dev device name
- Long Syntax:
- FR.066 Circuit circ
registered with scid scid
device device name
- Description:
- The circuit has been registered with the sub-channel identified
in the message.
- Level:
- UE-ERROR
- Short Syntax:
- FR.067 No memory for internal module module
chid chid
- Long Syntax:
- FR.067 No memory for an internal module module
channel-id chid
- Description:
- Unable to allocate memory required to open the module
displayed in the message.
- Level:
- U-TRACE
- Short Syntax:
- FR.068 FRENC frame too short nt network id
prot prot
circ circ
- Long Syntax:
- FR.068 FRENC frame too short network network id
protocol prot
circuit circ
- Description:
- An invalid frame was received by FRENC.
- Level:
- C-INFO
- Short Syntax:
- FR.069 MCast not enabled nt network id
- Long Syntax:
- FR.069 Multicast emulation not enabled network network id
- Description:
- Multicast Emulation is disabled at the FRLANE module.
- Level:
- C-INFO
- Short Syntax:
- FR.070 LANE Grp enabled circ circ
not found nt network id
- Long Syntax:
- FR.070 LANE Group enabled circuit circ
not found network network id
- Description:
- LANE Group has been enabled so this interface will only accept
defined circuits.
- Level:
- UE-ERROR
- Short Syntax:
- FR.071 Circ circ
creation failed nt network id
- Long Syntax:
- FR.071 Circuit circ
creation failed network network id
- Description:
- Circuit creation failed.
- Level:
- C-INFO
- Short Syntax:
- FR.072 Circ circ
already active nt network id
- Long Syntax:
- FR.072 Circuit circ
already active network network id
- Description:
- The circuit was already active and so the circuit UP message
is ignored.
- Level:
- C-INFO
- Short Syntax:
- FR.073 Circ circ
already inactive nt network id
- Long Syntax:
- FR.073 Circuit circ
already inactive network network id
- Description:
- The circuit was already inactive and so the circuit Down
message is ignored.
- Level:
- CE-ERROR
- Short Syntax:
- FR.074 Circuit Down for unknown circ circ
nt network id
- Long Syntax:
- FR.074 Circuit Down for unknown circuit circ
network network id
- Description:
- Received a Circuit Down message for an unknown circuit. The
message is ignored.
- Level:
- UE-ERROR
- Short Syntax:
- FR.075 Data type data_type
already in use nt network id
- Long Syntax:
- FR.075 Data type data_type
already in use network network id
- Description:
- This data type connection already exists, so FRLANE refused the
connection.
- Level:
- C-INFO
- Short Syntax:
- FR.076 FRLANE already up nt network id
- Long Syntax:
- FR.076 FRLANE already up network network id
- Description:
- The FRLANE module is already up, no need to bring up again.
- Level:
- C-INFO
- Short Syntax:
- FR.077 FRLANE already down nt network id
- Long Syntax:
- FR.077 FRLANE already down network network id
- Description:
- The FRLANE module is already down, no need to bring down again.
- Level:
- UE-ERROR
- Short Syntax:
- FR.078 LANE Grp enabled but no circ defined nt network id
- Long Syntax:
- FR.078 LANE Grp enabled but no circuits defined network network id
- Description:
- The LANE Group has been enabled but no circuits have been defined.
This is a configuration error and the user should define some
circuits or else this interface will not be able to be used.
- Level:
- UE-ERROR
- Short Syntax:
- FR.079 Circuit down failed dev device name
circ circ
- Long Syntax:
- FR.079 Circuit down failed device device name
circuit circ
- Description:
- Circuit down processing failed.
- Level:
- UE-ERROR
- Short Syntax:
- FR.080 Delayed reg dev device name
circ circ
- Long Syntax:
- FR.080 Delayed registration for device device name
circuit circ
- Description:
- A Circuit Up was registered by the shown stack but FRMGR
was unable to find a valid data sub-channel for it. Data
for this circuit will be dropped until the stack indicated
in the message comes up.
- Level:
- UE-ERROR
- Short Syntax:
- FR.081 Int not up dev device name
circ circ
- Long Syntax:
- FR.081 Interface not up device device name
circuit circ
- Description:
- The network interface has not come up yet and so the
incoming frame is dropped.
- Level:
- UE-ERROR
- Short Syntax:
- FR.082 Frame disc, LMI stopped, dev device name
- Long Syntax:
- FR.082 Frame discarded, LMI stopped, device device name
- Description:
- A frame was discarded because the switch's LMI has stopped
communicating. This could mean the port is inoperative on
the switch.
- Level:
- UE-ERROR
- Short Syntax:
- FR.083 Can't find circ circ
to reg client, dev device name
- Long Syntax:
- FR.083 Can't find circuit circ
to register client, device device name
- Description:
- A Client of FRMGR tried to register for the displayed circuit
but this circuit was not found to exist withint FRMGR. Check
the configuration to make sure that all circuits are defined
to FRMGR.
- Level:
- UE-ERROR
- Short Syntax:
- FR.084 Circ circ
already reg'd, dev device name
- Long Syntax:
- FR.084 Circuit circ
already registered, device device name
- Description:
- This circuit has already been registered by another client.
- Panic
- frimem
- Short Syntax:
- Frame Relay interface initialization failed, no memory.
- Description:
- The Frame Relay interface failed to allocate sufficient memory to
complete initialization.
- Action:
- Contact customer service.
- Panic
- friprt
- Short Syntax:
- FR: unsupported protocol during initialization
- Description:
- The Frame Relay network handler detected an unsupported protocol
during initialization.
- Action:
- Contact customer service.
- Panic
- frfprt
- Short Syntax:
- FR: unsupported protocol during frame forward
- Description:
- The Frame Relay network handler detected an unsupported protocol
during the protocol frame forward phase.
- Action:
- Contact customer service.