ELS Messages for Source Routing Transparent (SRT)
- Level:
- UI-ERROR
- Short Syntax:
- SRT.001 No buf to dup broadcast frame source_mac
-> dest_mac
to port port
, nt network
- Long Syntax:
- SRT.001 No buffer available to duplicate frame from source_mac
to dest_mac
on to port port
, network network
- Description:
- No buffer available to copy a frame in order to send a bridged
frame on multiple interfaces. Bridged packets are sent on
multiple interfaces either for multicast destination addresses,
or in the case of certain static entries. No copy of this frame will
be sent on the specified port and network.
- Cause:
- Severe packet buffer shortage.
- Action:
- Check memory statistics in GWCON to verify packet buffer
level.
- Cause:
- Traffic peak using all available buffers.
- Action:
- This is the problem if this message occurs infrequently.
a bug where buffers are being lost. You can look at this with
DDT. Look at BFRLST, if 0 (NULL) there are still no free buffers.
Then look at NBFREE, if zero there was a slow buffer leak, if non-zero
then there has been a double-free of a buffer freeing the free
list.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.002 Err error_code
setting promsic mode on nt network
- Long Syntax:
- SRT.002 Error code error_code
trying to set promiscuous mode on network network
- Description:
- The Spanning Tree Protocol requested setting this network into
Learning state, but the command to the device failed. The error_code
is a device-specific error code that may indicate what the error is.
- Cause:
- Hardware failure or software bug.
- Action:
- Contact customer service.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.003 Err error_code
add stat ent on nt network
- Long Syntax:
- SRT.003 Error code error_code
trying to add static entries on network network
- Description:
- An attempt to add a set of static entries to the internal database
of a bridging interface having internal filtering failed.
The error_code
is a device-specific error code that may indicate what the error is.
- Cause:
- Hardware failure or software bug.
- Action:
- Contact customer service.
ID_cccc table in mos/src/mos.h. Then look at the appropriate
device handler (or driver) for that ID_cccc error.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.004 No buf for command_name
cmd to net network
- Long Syntax:
- SRT.004 No buffer available for command_name
command to network network
- Description:
- No buffer was available to send a command to the device.
The possible command names are
"D_CNFGSRB" (configure source-routing bridging),
"SRT_ON" (promiscuous on),
"SRT_INFORM" (learn capabilities of device),
"SRT_SET_AGE" (set age for filtering database in device),
"SRT_DECR_AGE" (do ageing pass on filtering database in device),
"SRT_ADD_ENTRY" (add static entry),
"SRT_DEL_ENTRY" (delete entry, from console),
"SRT_SEARCH_ENTRY" (search for particular entry, from console),
and "SRT_LIST_ENTRY" (list contents of learning database in card).
For commands "D_CNFGSRB" and
"SRT_ON" the result will be that the interface
may remain in the wrong state. A failure on "SRT_INFORM" could cause
serious problems. For other commands the
results will be less serious.
- Cause:
- Severe packet buffer shortage.
- Action:
- Check memory statistics in GWCON to verify packet buffer
level.
- Cause:
- Traffic peak using all available buffers.
- Action:
- This is the problem if this message occurs infrequently.
a bug where buffers are being lost. You can look at this with
DDT. Look at BFRLST, if 0 (NULL) there are still no free buffers.
Then look at NBFREE, if zero there was a slow buffer leak, if non-zero
then there has been a double-free of a buffer freeing the free
list.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.005 source_mac
-> dest_mac
send fld, rsn reason_code
, port port
nt network
- Long Syntax:
- SRT.005 Sending Frame from source_mac
to dest_mac
failed, reason reason_code
, on port port
network network
- Description:
- The sending of a packet being forwarded failed. The reason is
the internal error code for the failure.
- Cause:
- Miscellaneous handler error. (Reason code 1.)
- Action:
- Check for error messages from handler for network_name.
- Cause:
- Output queue overflow, or other flow control. (Reason code
2.)
- Action:
- Alleviate congestion.
- Cause:
- Network down. (Reason code 3.)
- Action:
- See why handler thinks network is down.
- Cause:
- Dropped by handler to avoid looping, or bad broadcast.
(Reason code 4.)
- Action:
- Check configuration.
- Cause:
- Host down. (Reason code 5.)
- Action:
- See why handler thinks host is down.
- Level:
- CI-ERROR
- Short Syntax:
- SRT.006 Input q ovf source_mac
-> dest_mac
, dropped, nt network
- Long Syntax:
- SRT.006 Input queue overflow on frame from source_mac
to dest_mac
, packet dropped from network network
- Description:
- The input queue for frames to be forwarded is too long, and
this frame has been dropped to attempt to alleviate the
congestion.
- Cause:
- Bursty traffic may be causing congestion.
- Action:
- Wait for burst to subside.
- Cause:
- Too much traffic for forwarder to forward.
- Action:
- Reconfigure network. Increase speed of router.
- Cause:
- Inadequate buffer resources.
- Action:
- Examine memory statistics in GWCON.
check bridge configuration.
- Level:
- CI-ERROR
- Short Syntax:
- SRT.007 BPDU q ovf frm source_mac
, dropped, nt network
- Long Syntax:
- SRT.007 Bridge Protocol Data Unit input queue overflow on frame from source_mac
, dropped from network network
- Description:
- The input queue for Spanning Tree Protocol Bridge Protocl Data Units
is too long, and this frame has been dropped to attempt to
alleviate the congestion.
- Cause:
- Source node streaming BDPU frames.
- Action:
- Correct behavior of source node.
- Cause:
- Too much traffic for forwarder to forward.
- Action:
- Reconfigure network. Increase speed of router.
- Cause:
- Inadequate buffer resources.
- Action:
- Examine memory statistics in GWCON.
check bridge configuration.
- Level:
- CE-ERROR
- Short Syntax:
- SRT.008 source_mac
-> dest_mac
too big ( reformatted_length
> output_maximum
) for port port
nt network
, dropped
- Long Syntax:
- SRT.008 Frame from source_mac
to dest_mac
is too big (reformatted length reformatted_length
bytes > output maximum size output_maximum
bytes) for port port
network network
, dropped
- Description:
- The specified frame is too large to send on this outgoing port and
network. The reformatted_length is the size of the frame
including MAC headers after any mapping of data link headers.
- Cause:
- Host on network with large maximum frame size sending to host
on network with smaller maximum frame size.
- Action:
- Reconfigure sending host to not send such large frames.
If frame is of a routable protocol supporting fragmentation
(such as IP or ISO) or maximum frame size determination (DNA or
XNS), convert to using routing instead of bridging.
- Cause:
- Host on network with large maximum frame size sending to host
via an intervening network with smaller maximum frame size.
- Action:
- Reconfigure network to use networks with large maximum frame size
(such as FDDI or 802.5) as the backbone networks. Reconfigure
port costs in Spanning Tree Protocol to favor spanning trees via
networks with large maximum frame sizes.
transparent bridging. The main solution is routing, although the
source-routing frame size determination alogrithms may also
be of use here.
- Level:
- UE-ERROR
- Short Syntax:
- SRT.009 source_mac
-> dest_mac
drp, nt network
down
- Long Syntax:
- SRT.009 Frame from source_mac
to dest_mac
dropped, input network network
is down
- Description:
- A frame has been received for bridging on a network that is down.
It will be ignored.
- Cause:
- A BDPU has been sent to the unicast address of the router on
this interface.
- Action:
- Correct action of sending node.
- Cause:
- Internal state inconsistency.
- Level:
- P-TRACE
- Short Syntax:
- SRT.010 source_mac
-> dest_mac
drp, src add flt, port port
nt network
- Long Syntax:
- SRT.010 Frame from source_mac
to dest_mac
dropped, source address filtered, port port
network network
- Description:
- A MAC frame has been received by the hardware, but is being dropped
because the source MAC address is being administratively filtered
by the bridge. The frame will be dropped.
- Cause:
- Receipt of frame whose source MAC address matches the source
filter.
- Level:
- U-TRACE
- Short Syntax:
- SRT.011 source_mac
-> dest_mac
dropped, input port port
nt network
not forwarding
- Long Syntax:
- SRT.011 Frame from source_mac
to dest_mac
dropped, input port port
network network
not in forwarding state
- Description:
- A MAC frame was received on a port that is still only in "learning"
state. Frames are only bridged when the input port is in "forwarding"
state. While the port is still in "learning" state, they are
only processed to learn the source addresses for the filtering
database. The frame will not be bridged.
- Cause:
- Normal part of transition to "forwarding" state.
- Level:
- U-INFO
- Short Syntax:
- SRT.012 source_mac
-> dest_mac
dropped, output port port
nt network
not forwarding
- Long Syntax:
- SRT.012 Frame from source_mac
to dest_mac
dropped, output port port
network network
not in forwarding state
- Description:
- A MAC frame was being bridged, but the destination port was
not in "forwarding" state. It will not be sent on that port.
- Cause:
- Output port still in "learning" state.
- Action:
- None needed, port will transition to "forwarding".
- Cause:
- Static entry in filtering database points to port that is not
in "forwarding" state.
- Level:
- P-TRACE
- Short Syntax:
- SRT.013 source_mac
-> dest_mac
drp, dst same LAN, port port
nt network
- Long Syntax:
- SRT.013 Frame from source_mac
to dest_mac
dropped, destination on same LAN, port port
network network
- Description:
- A MAC frame has been received whose destination address is known to
be on the same side of the bridge as the packet came from. It is
dropped by the filtering logic since it does not need to be bridged.
- Cause:
- Normal local traffic on network.
about a filtering bridge. Sigh.
- Level:
- CI-ERROR
- Short Syntax:
- SRT.014 source_mac
-> dest_mac
drp, dst port port
not enabled, nt network
- Long Syntax:
- SRT.014 Frame from source_mac
to dest_mac
dropped, destination port port
not enabled, network network
- Description:
- A frame being bridged was destined for a port which is not running
transparent bridging, or not in "forwarding" state for transparent
bridging.
- Cause:
- Static entry in filtering database points to port that is not
in "forwarding" state.
- Level:
- P-TRACE
- Short Syntax:
- SRT.015 source_mac
-> dest_mac
brdg port port
nt network
to port port
nt network
- Long Syntax:
- SRT.015 Frame from source_mac
to dest_mac
bridged from port number port
network network
to port number port
network network
- Description:
- A frame is being bridged between these two interfaces. The
destination address was known, so it was sent only to the
correct destination network.
- Level:
- P-TRACE
- Short Syntax:
- SRT.016 source_mac
-> dest_mac
brdg-all port port
nt network
to port port
nt network
- Long Syntax:
- SRT.016 Frame from source_mac
to dest_mac
bridged to all ports from port number port
network network
to port number port
network network
- Description:
- A frame is being transparently bridged to all active transparent
bridging ports. This happens when the frame destination is a
multicast, when the frame destination is not in the learning database,
or when required by static entries in the learning database.
There will be one message for each port the frame is sent on.
- Level:
- U-INFO
- Short Syntax:
- SRT.017 Enabling SRT on port port
nt network
- Long Syntax:
- SRT.017 Enabling SRT on port port
network network
- Description:
- The SRT forwarder is starting the process of enabling bridging
on the specified interface. This starts when the interface
comes up from a self-test.
- Level:
- C-INFO
- Short Syntax:
- SRT.018 SRT startup complete on port port
nt network
- Long Syntax:
- SRT.018 SRT startup complete on port port
network network
- Description:
- The SRT forwarder has completed the process of enabling bridging
on the specified interface. It will now enter "blocking" state.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.019 Unsupp ifc typ type_name
, nt network
- Long Syntax:
- SRT.019 Unsupported interface type type_name
, network network
- Description:
- The SRT forwarder had been enabled on a type of interface it does
not support.
- Cause:
- Enabling SRT on an interface which does not support SRT, such
as ProNET-10.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.020 Can't autocfg brdg addr, lowest port port
nt network
no MAC addr
- Long Syntax:
- SRT.020 Cannot autoconfigure the bridge address, the lowest numbered port port
network network
has no MAC address
- Description:
- The user has configured the bridge to autoconfigure the bridge
address based on the MAC address of the lowest number port.
However, the lowest numbered port is of a type that does not
have a MAC address, such as a serial line.
- Action:
- Assign address to bridge by using SRT config> command
"SET BRIDGE".
- Level:
- U-TRACE
- Class:
- FAKE
- Short Syntax:
- SRT.021 Bridge source_mac
-> dest_mac
, no fwd, nt network
- Long Syntax:
- SRT.021 Bridge frame from source_mac
to dest_mac
, no forwarder, network network
- Description:
- Bridge frame received, but there is no bridging available in
this load. The frame will be ignored.
- Cause:
- Receiving a frame to 802.2 destination SAP 42.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.022 Bridge config with no ports, disabling
- Long Syntax:
- SRT.022 Bridge configured with no ports on it, disabling the bridge
- Description:
- The bridge has been enabled, but there are no ports configured
on that bridge. The bridge will be left disabled.
It takes at least two ports to be a bridge.
- Action:
- Add ports in SRT config> console.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.023 Port port
config on nonexist network number network_number
- Long Syntax:
- SRT.023 Port port
configured on nonexistent network number network_number
- Description:
- The port has been configured to use a network that has not
been configured with the Config> ADD DEVICE command.
This port of the bridge will be disabled.
- Cause:
- Inconsistency between router device configuration and bridge
configuration.
- Action:
- Correct the network number in the bridge configuration, or
add the network in the device configuration.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.024 existent_port_count
ports is < 2, disabling
- Long Syntax:
- SRT.024 existent_port_count
existent ports is less than 2, disabling bridge
- Description:
- Less than two (valid) ports have been configured on the bridge.
There must be at least two ports.
- Cause:
- Less than two ports configured.
- Action:
- Add more ports, or don't try and use bridging.
- Cause:
- Too many ports on non-configured devices.
- Action:
- Resolve configuration conflicts between bridging ports and
devices.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.025 No mem for filt db (req requested_size
, min minimum_size
), disabl
- Long Syntax:
- SRT.025 No memory for filtering databse (desired size requested_size
bytes, absolute minimum size minimum_size
bytes), disabling bridge
- Description:
- There is not enough free memory to allocate even a minimal size
filtering database. The bridge will be disabled.
The bridge starts by trying to allocate
requestd_size bytes, and then tries with progressively smaller
sizes down to minimum_size. The minimum size is enough only
for the registered and static entries.
- Cause:
- Severe shortage of memory.
- Action:
- Reduce routing table sizes in other protocols, use system with
less protocols, expand memory in router.
- Level:
- C-INFO
- Short Syntax:
- SRT.026 source_mac
== dest_mac
, drop, port port
nt network
- Long Syntax:
- SRT.026 Frame from source_mac
to dest_mac
, source same as destination, dropping, from port port
network network
- Description:
- Frames to and from the same address are not bridged by this bridge.
- Level:
- P-TRACE
- Short Syntax:
- SRT.027 Chg state old_state
to new_state
, port port
nt network
- Long Syntax:
- SRT.027 Changing port state from old_state
to new_state
for port port
, network network
- Description:
- The Spanning Tree Protocol has requested this state change for
this port in the SRT bridge. The old_state and new_state are one of:
FORWARDING (Spanning Tree Protocol Forwarding state),
LEARNING (Spanning Tree Protocol Learning state),
LISTENING (Spanning Tree Protocol Listening state),
BLOCKED (Spanning Tree Protocol Blocking state),
CONFIGURING (configuration of port device pending),
POSTCONFIGURING (configuration of port device done),
PRECONFIGURING (port enabled, configuration of port device to start),
and DISABLED (port disabled).
- Level:
- UI_ERROR
- Short Syntax:
- SRT.028 No room for PERM mac_address
in filt database, disabling
- Long Syntax:
- SRT.028 No room for permanent address mac_address
in filtering database, disabling bridge
- Description:
- There is no room for the permanent entry in the filtering
database. The bridge will be disabled.
- Cause:
- Filtering database size too small.
- Action:
- Make filtering database larger.
- Cause:
- Too many permanent entries.
- Action:
- Configure less permanent entries.
- Level:
- UI_ERROR
- Short Syntax:
- SRT.029 No memm for PERM mac_address
, disabling
- Long Syntax:
- SRT.029 No memory for permanent address mac_address
, disabling bridge
- Description:
- There is no room for the permanent entry in an auxilliary
database. The bridge will be disabled.
- Cause:
- Too little free memory.
- Action:
- Make routing databses smaller.
- Action:
- Increase memory size.
- Cause:
- Too many permanent entries.
- Action:
- Configure less permanent entries.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.030 command
Cmd fld to net network
- Long Syntax:
- SRT.030 command
command failed to network network
- Description:
- A command to a network device failed.
The possible command names are "SRT_ON" (promiscuous on),
"SRT_OFF" (promiscuous off),
"SRT_INFORM" (learn capabilities of device),
"SRT_ADD_ENTRY" (add static entry in device),
"SRT_SET_AGE" (set age for filtering database in device),
and "SRT_DECR_AGE" (do ageing pass on filtering database in device).
For commands "SRT_ON" and "SRT_OFF"
the result will be that the interface
may remain in the worong state. A failure on "SRT_INFORM" could cause
serious problems. For other commands the
results will be less serious.
- Cause:
- Hardware failure or software bug.
- Action:
- Contact customer service.
Only calls to srtioctl() with a NULL iorb argument will get a fail,
due to failing to allocate an iorb, producing message SRT.004.
These are only "SRT_ON" and "SRT_OFF."
- Level:
- UI-ERROR
- Short Syntax:
- SRT.031 No buf to dup routing_type
frame source_mac
-> dest_mac
to port port
, nt network
- Long Syntax:
- SRT.031 No buffer available to duplicate routing_type
frame from source_mac
to dest_mac
on to port port
, network network
- Description:
- No buffer available to copy a frame in order to send an All
Routes Explorer (ARE)
or Spanning Tree
Explorer (STE) routing_type
frame on multiple interfaces. ARE frames are sent on all
interfaces which are part of the SRT spanning tree, STE frames are
sent on all interfaces running source-routing.
No copy of this frame will
be sent on the specified port and network.
- Cause:
- Severe packet buffer shortage.
- Action:
- Check memory statistics in GWCON to verify packet buffer
level.
- Cause:
- Traffic peak using all available buffers.
- Action:
- This is the problem if this message occurs infrequently.
a bug where buffers are being lost. You can look at this with
DDT. Look at BFRLST, if 0 (NULL) there are still no free buffers.
Then look at NBFREE, if zero there was a slow buffer leak, if non-zero
then there has been a double-free of a buffer freeing the free
list.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.032 SR source_mac
-> dest_mac
send fld, rsn reason_code
, port port
nt network
- Long Syntax:
- SRT.032 Sending source routed frame from source_mac
to dest_mac
failed, reason reason_code
, on port port
network network
- Description:
- The sending of a source routed frame being forwarded failed.
The reason_code is the internal error code for the failure.
- Cause:
- Miscellaneous handler error. (Reason code 1.)
- Action:
- Check for error messages from handler for network_name.
- Cause:
- Output queue overflow, or other flow control. (Reason code
2.)
- Action:
- Alleviate congestion.
- Cause:
- Network down. (Reason code 3.)
- Action:
- See why handler thinks network is down.
- Cause:
- Dropped by handler to avoid looping, or bad broadcast.
(Reason code 4.)
- Action:
- Check configuration.
- Cause:
- Host down. (Reason code 5.)
- Action:
- See why handler thinks host is down.
- Level:
- C-TRACE
- Short Syntax:
- SRT.033 routing_type
dup RD drop source_mac
-> dest_mac
from port port
, nt network
- Long Syntax:
- SRT.033 routing_type
with duplicate Route Descriptor from source_mac
to dest_mac
from port port
, network network
- Description:
- A source-routed frame having a All Routes Descriptor (ARE)
or Spanning Tree
Explorer (STE) routing_type
in the RIF has a duplicate Routing Descriptor
in the RIF. The frame will be dropped. This is a normal occurrence
for ARE frames when there are any duplicate paths in the
source routing domain. For STE frames, this
indicates that there is an interface that is part of the source-routing
spanning tree that should not be.
- Cause:
- Receiving an ARE/STE from a segment is has already been on.
- Action:
- None needed for ARE, this is normal. For STE, one may want to
correct it's "spanning tree," but this is not essential.
- Level:
- UE-ERROR
- Short Syntax:
- SRT.034 SRF dup LOUT (RIF RIF
) drop source_mac
-> dest_mac
from port port
, nt network
- Long Syntax:
- SRT.034 SRF with duplicate LOUT (RIF RIF
) from source_mac
to dest_mac
from port port
, network network
- Description:
- A source-routed frame of Specifically-routed frame (SRF) type
has a duplicate LOUT (outgoing LAN ID). This is illegal, and
the frame will be dropped.
- Cause:
- Station sending frame with invalid RIF that would go through
the same bridge more than once, thus looping forever.
- Action:
- Find out why station is using this RIF. Either it is using a
hand-configured one that is wrong, or there is a bug in the
discovery algorithm.
- Level:
- UE-ERROR
- Short Syntax:
- SRT.035 ARE max RD (RIF RIF
) drop source_mac
-> dest_mac
from port port
, nt network
- Long Syntax:
- SRT.035 All Routes Explorer exceeds maximum Route Descriptors (RIF RIF
) from source_mac
to dest_mac
from port port
, network network
- Description:
- An All Routes Explorer (ARE) source-routed frame has more Route
Descriptors than this bridge is configured to allow for ARE frames.
The frame will be dropped.
- Cause:
- Upstream bridge has an ARE RD limit inconsistent with this bridge.
- Action:
- Reconfigure all bridges in source-routing domain to have
consistent ARE RD limit.
- Cause:
- Network has too many hops for configured ARE RD limit.
- Action:
- Reconfigure all bridges in source-routing domain to have
ARE RD limit consistent with the diamter of the domain.
already partly modified.
- Level:
- UE-ERROR
- Short Syntax:
- SRT.036 STE max RD (RIF RIF
) drop source_mac
-> dest_mac
from port port
, nt network
- Long Syntax:
- SRT.036 Spanning Tree Explorer exceeds maximum Route Descriptors (RIF RIF
) from source_mac
to dest_mac
from port port
, network network
- Description:
- A Spanning Tree Explorere (STE) source-routed frame has more Route
Descriptors than this bridge is configured to allow for STE frames.
The frame will be dropped.
- Cause:
- Upstream bridge has an STE RD limit inconsistent with this bridge.
- Action:
- Reconfigure all bridges in source-routing domain to have
consistent STE RD limit.
- Cause:
- Network has too many hops for configured STE RD limit.
- Action:
- Reconfigure all bridges in source-routing domain to have
STE RD limit consistent with the diameter of the domain.
already partly modified.
- Level:
- CE-ERROR
- Short Syntax:
- SRT.037 SRF unk LOUT (RIF RIF
) drop source_mac
-> dest_mac
from port port
, nt network
- Long Syntax:
- SRT.037 SRF with unknown LOUT (RIF RIF
) from source_mac
to dest_mac
from port port
, network network
- Description:
- A source-routed frame of Specifically-routed frame (SRF) type
has an outgoing LOUT (LAN ID Out) that does not match that
of any active source-routing interface in the router. It will
be dropped.
- Cause:
- End station using RIF that was discovered before an interface
went down in the router.
- Action:
- None should be needed, the session on the station will fail, and
it will re-initiate route discovery.
- Cause:
- More than one bridge on the incoming segment with the same
bridge number, and this LOUT matches in it.
- Action:
- Reconfigure for legal configuration. All Bridge Numbers must
be unique on a given segment.
- Cause:
- End station using completely invalid RIF.
- Action:
- Find out why station is using this RIF.
- Level:
- P-TRACE
- Short Syntax:
- SRT.038 ARE rcv (RIF RIF
) source_mac
-> dest_mac
from port port
, nt network
- Long Syntax:
- SRT.038 All Routes Explorer received (RIF RIF
) from source_mac
to dest_mac
from port port
, network network
- Description:
- An All Routes Explorer frame has been received on the specified port.
- Level:
- P-TRACE
- Short Syntax:
- SRT.039 ARE sent (RIF RIF
) source_mac
-> dest_mac
to port port
, nt network
- Long Syntax:
- SRT.039 All Routes Explorer sent (RIF RIF
) from source_mac
to dest_mac
to port port
, network network
- Description:
- An All Routes Explorer frame has been sent on the specified port.
- Level:
- P-TRACE
- Short Syntax:
- SRT.040 STE rcv (RIF RIF
) source_mac
-> dest_mac
from port port
, nt network
- Long Syntax:
- SRT.040 Spanning Tree Explorer received (RIF RIF
) from source_mac
to dest_mac
from port port
, network network
- Description:
- A Spanning Tree Explorer frame has been received on the specified port.
- Level:
- P-TRACE
- Short Syntax:
- SRT.041 STE sent (RIF RIF
) source_mac
-> dest_mac
to port port
, nt network
- Long Syntax:
- SRT.041 Spanning Tree Explorer sent (RIF RIF
) from source_mac
to dest_mac
to port port
, network network
- Description:
- A Spanning Tree Explorer frame has been sent on the specified port.
- Level:
- U-INFO
- Short Syntax:
- SRT.042 routing_type
LF lowered ( old_LF
to new_LF
) source_mac
-> dest_mac
from port port
, nt network
- Long Syntax:
- SRT.042 routing_type
Largest Frame size lowered (from old_LF
bytes to new_LF
bytes) from source_mac
to dest_mac
from port port
, network network
- Description:
- A source-routing explorer (ARE or STE in routing_type) has had
the Largest Frame (LF) field lowered in its RIF. This happens
whenever a frame is received from a segment with a smaller
maximum frame size than the one presently encoded in the
LF bits. This is a normal part of the spanning tree protocol
to determine the maximum frame size on all routes.
- Cause:
- It is somewhat abnormal to see this happen on received frames,
and indicates that the endnodes or other bridges on this segment
have different frame sizes configured. However, it is a
prefectly legal configuration.
- Action:
- Make frame size configurations consistent on a given segment.
- Level:
- C-INFO
- Short Syntax:
- SRT.043 routing_type
LF lowered ( old_LF
to new_LF
) source_mac
-> dest_mac
to port port
, nt network
- Long Syntax:
- SRT.043 routing_type
Largest Frame size lowered (from old_LF
bytes to new_LF
bytes) from source_mac
to dest_mac
to port port
, network network
- Description:
- A source-routing explorer (ARE or STE in routing_type) has had
the Largest Frame (LF) field lowered in its RIF. This happens
whenever a frame is sent to a segment with a smaller
maximum frame size than the one presently encoded in the
LF bits. This is a normal part of the spanning tree protocol
to determine the maximum frame size on all routes.
- Level:
- P-TRACE
- Short Syntax:
- SRT.044 SRF rcv (RIF RIF
) source_mac
-> dest_mac
from port port
, nt network
- Long Syntax:
- SRT.044 Specifically-routed frame received (RIF RIF
) from source_mac
to dest_mac
from port port
, network network
- Description:
- A Specifically-routed frame has been received on the
specified port.
- Level:
- P-TRACE
- Short Syntax:
- SRT.045 Send SRF (RIF RIF
) source_mac
-> dest_mac
to port port
, nt network
- Long Syntax:
- SRT.045 Sending Specifically-routed frame (RIF RIF
) from source_mac
to dest_mac
to port port
, network network
- Description:
- A Specifically-routed frame is being sent on the
specified port.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.046 routing_type
rcv source_mac
-> dest_mac
from disabl port port
, nt network
, disc
- Long Syntax:
- SRT.046 routing_type
frame received from source_mac
to dest_mac
on disabled port port
, network network
, discarded
- Description:
- A source-routed frame has been received on the specified
port, but that port is not configured for bridging.
The routing_type is one of SRF (Specifically-routed frame),
STE (Spanning Tree Expolorer), or ARE (All Routes Explorer).
This really should not happen on more than a transient basis,
because ports that are not enabled for bridging should not
be queueing packets to the source-routing forwarder.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.047 routing_type
rcv source_mac
-> dest_mac
from non-SR port port
, nt network
, disc
- Long Syntax:
- SRT.047 routing_type
frame received from source_mac
to dest_mac
on non-source-routing port port
, network network
, discarded
- Description:
- A source-routed frame has been received on the specified
port, but that port is not configured for source-routing bridging.
The routing_type is one of SRF (Specifically-routed frame),
STE (Spanning Tree Expolorer), or ARE (All Routes Explorer).
This really should not happen on more than a transient basis,
because ports that are not enabled for bridging should not
be queueing packets to the source-routing forwarder.
- Level:
- P-TRACE
- Short Syntax:
- SRT.048 STE dropped (RIF RIF
) source_mac
-> dest_mac
from blk port port
, nt network
- Long Syntax:
- SRT.048 Spanning Tree Explorer dropped (RIF RIF
) from source_mac
to dest_mac
from blocked port port
, network network
- Description:
- A Spanning Tree Explorer (STE) frame was dropped, and not
forwarded, because the incoming port
is not part of the spanning tree, or has been configured
not to forward STE frames.
- Cause:
- Normal for STE frames, this is the difference between them and
ARE frames.
- Level:
- P-TRACE
- Short Syntax:
- SRT.049 STE not sent (RIF RIF
) source_mac
-> dest_mac
to blk port port
, nt network
- Long Syntax:
- SRT.049 Spanning Tree Explorer not sent (RIF RIF
) from source_mac
to dest_mac
to blocked port port
, network network
- Description:
- A Spanning Tree Explorer (STE) frame was not sent on the specified port
because it is not part of the spanning tree, or has been configured
not to forward STE frames.
- Cause:
- Normal for STE frames, this is the difference between them and
ARE frames.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.050 err error_string
ena SR on nt network
- Long Syntax:
- SRT.050 Got error_string
error trying to enable source-routing on network network
- Description:
- The bridge tried to enable source-routing bridging on this
interface, but the interface refused the configuration command.
Source-routing will be left disabled on this interface.
- Cause:
- Either bad commands were passed to the interface, or there
is a bug in the interface firmware.
- Action:
- Contact customer service.
- Level:
- UE-ERROR
- Short Syntax:
- SRT.051 SRF source_mac
-> dest_mac
too big ( reformatted_length
> output_maximum
) for port port
nt network
, dropped
- Long Syntax:
- SRT.051 Specifically-routed frame from source_mac
to dest_mac
is too big (reformatted length reformatted_length
> output maximum size output_maximum
) for port port
network network
, dropped
- Description:
- The specified Specifically-routed (source-routed)
frame is too large to send on this outgoing port and
network. The reformatted_length is the size of the frame
including MAC headers after any mapping of data link headers.
- Cause:
- Host not honoring LF bit values from its returned explorer frames.
- Action:
- Fix host.
- Level:
- UE-ERROR
- Short Syntax:
- SRT.052 routing_type
source_mac
-> dest_mac
too big ( reformatted_length
> output_maximum
) for port port
nt network
, dropped
- Long Syntax:
- SRT.052 routing_type
frame from source_mac
to dest_mac
is too big (reformatted length reformatted_length
> output maximum size output_maximum
) for port port
network network
, dropped
- Description:
- The source-routed explorer (ARE or STE routing_type)
frame is too large to send on this outgoing port and
network. The reformatted_length is the size of the frame
including MAC headers after any mapping of data link headers.
- Cause:
- The sending host is putting too much data in its explorer frames.
These should normally be short, since it should not be making
any assumptions about the maximum frame size available.
- Action:
- Correct behavior of sending host.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.053 routing_type
inv RIF len RIF_length
, source_mac
-> dest_mac
port port
, nt network
, disc
- Long Syntax:
- SRT.053 routing_type
with invalid RIF lenth RIF_length
from source_mac
to dest_mac
from port port
, network network
, discarded
- Description:
- A source-routing frame was received with an invalid
RIF length encoded in the Length bits of the RIF.
The routing_type is one of SRF (Specifically-routed frame),
STE (Spanning Tree Expolorer), or ARE (All Routes Explorer).
- Cause:
- Received frame with RIF length less than 2 or not a multiple of
2 in length.
- Action:
- Correct software in sending node.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.054 No mem for hash tab (req requested_size
), disabl
- Long Syntax:
- SRT.054 No memory for hash table (desired size requested_size
bytes), disabling bridge
- Description:
- There is not enough free memory to allocate the
hash table for the filtering database. The bridge will be disabled.
- Cause:
- Severe shortage of memory.
- Action:
- Reduce routing table sizes in other protocols, use system with
less protocols, expand memory in router.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.055 No mem for conv hash tab (req requested_size
), disabl
- Long Syntax:
- SRT.055 No memory for conversion hash table (desired size requested_size
bytes), disabling bridge
- Description:
- There is not enough free memory to allocate the
hash table for the conversion databse. The bridge will be disabled.
- Cause:
- Severe shortage of memory.
- Action:
- Reduce routing table sizes in other protocols, use system with
less protocols, expand memory in router.
- Level:
- CI-ERROR
- Short Syntax:
- SRT.056 Input SR q ovf source_mac
-> dest_mac
, dropped, nt network
- Long Syntax:
- SRT.056 Input source-routing queue overflow on frame from source_mac
to dest_mac
, packet dropped from network network
- Description:
- The input queue for source-routed
frames to be forwarded is too long, and
this frame has been dropped to attempt to alleviate the
congestion.
- Cause:
- Bursty traffic may be causing congestion.
- Action:
- Wait for burst to subside.
- Cause:
- Too much traffic for forwarder to forward.
- Action:
- Reconfigure network. Increase speed of router.
- Cause:
- Inadequate buffer resources.
- Action:
- Examine memory statistics in GWCON.
check bridge configuration.
- Level:
- P-TRACE
- Short Syntax:
- SRT.057 source_mac
-> dest_mac
brdg port port
nt network
to port port
nt network
- Long Syntax:
- SRT.057 Frame from source_mac
to dest_mac
bridged from port number port
network network
to port number port
network network
- Description:
- A frame is being bridged between these two interfaces. The
destination address was known, so it was sent only to the
correct destination network.
- Level:
- CE-ERROR
- Short Syntax:
- SRT.058 TB->SR source_mac
-> dest_mac
too big ( reformatted_length
> output_maximum
) for port port
nt network
, drop
- Long Syntax:
- SRT.058 Transparent frame converted to source-routed frame from source_mac
to dest_mac
is too big (reformatted length reformatted_length
bytes > output maximum size output_maximum
bytes) for port port
network network
, dropped
- Description:
- The specified transparent bridge
frame is too large to send as a source-routed frame
on this outgoing port and
network. The reformatted_length is the size of the frame
including MAC headers and RIF after any mapping of data link headers.
- Cause:
- Host on network with large maximum frame size sending to host
on network with smaller maximum frame size.
- Action:
- Reconfigure sending host to not send such large frames.
If frame is of a routable protocol supporting fragmentation
(such as IP or ISO) or maximum frame size determination (DNA or
XNS), convert to using routing instead of bridging.
- Cause:
- Host on network with large maximum frame size sending to host
via an intervening network with smaller maximum frame size.
- Action:
- Reconfigure network to use networks with large maximum frame size
(such as FDDI or 802.5) as the backbone networks. Reconfigure
port costs in Spanning Tree Protocol to favor spanning trees via
networks with large maximum frame sizes.
transparent bridging. The main solution is routing, although the
source-routing frame size determination alogrithms may also
be of use here.
- Level:
- P-TRACE
- Short Syntax:
- SRT.059 TB->SR source_mac
-> dest_mac
(RIF RIF
) brdg port port
nt network
to port port
nt network
- Long Syntax:
- SRT.059 Transparent frame converted to source-routed frame from source_mac
to dest_mac
(RIF RIF
) bridged from port number port
network network
to port number port
network network
- Description:
- A frame is being conversion bridged between these two interfaces. The
destination address and RIF were known, so it was sent only to the
correct destination network.
- Level:
- P-TRACE
- Short Syntax:
- SRT.060 TB->SR source_mac
-> dest_mac
(RIF RIF
) brdg-all port port
nt network
to port port
nt network
- Long Syntax:
- SRT.060 Transparent frame converted to source-routed frame from source_mac
to dest_mac
(RIF RIF
) bridged to all ports from port number port
network network
to port number port
network network
- Description:
- A frame is being conversion bridged to all active source-routing
ports. This happens when the frame destination is a
multicast or when the frame destination is not in the
source-routing learning database.
There will be one message for each port the frame is sent on.
- Level:
- UE-ERROR
- Short Syntax:
- SRT.061 SRF rcv source_mac
-> dest_mac
(RIF RIF
) to disabl port port
, nt network
, disc
- Long Syntax:
- SRT.061 Specifically routed frame frame received from source_mac
to dest_mac
(RIF RIF
) to disabled port port
, network network
, discarded
- Description:
- A Specifically Routed frame has been received whose RIF would send
it on the specified port, but that port is not configured for bridging.
- Cause:
- End station using invalid RIF. This can happen when the
end station acquires a RIF, and caches it, but in the interim
the bridge has been reconfigured and restarted.
- Level:
- CE-ERROR
- Short Syntax:
- SRT.062 Warning:SR->TB source_mac
-> dest_mac
too big ( reformatted_length
> output_maximum
) from port port
nt network
- Long Syntax:
- SRT.062 Source-routed frame converted to transparent frame from source_mac
to dest_mac
is too big (reformatted length reformatted_length
bytes > output maximum size output_maximum
bytes) from port port
network network
, may get dropped.
- Description:
- The specified source-routed
frame is larger than that is allowed by LF-BIT configuration for the
transparent bridge domain. After mapping to the MAC headers of the
outgoing port, the packet may get dropped if it exceeds the MSDU
limit of the port.
- Cause:
- Source-routing host not honoring maximum frame size that was determined
in source-routing threading process.
- Action:
- Correct behavior of host.
- Cause:
- Host on network with large maximum frame size sending to host
on network with smaller maximum frame size.
- Action:
- Reconfigure sending host to not send such large frames.
If frame is of a routable protocol supporting fragmentation
(such as IP or ISO) or maximum frame size determination (DNA or
XNS), convert to using routing instead of bridging.
- Cause:
- Host on network with large maximum frame size sending to host
via an intervening network with smaller maximum frame size.
- Action:
- Reconfigure network to use networks with large maximum frame size
(such as FDDI or 802.5) as the backbone networks. Reconfigure
port costs in Spanning Tree Protocol to favor spanning trees via
networks with large maximum frame sizes.
transparent bridging. The main solution is routing, although the
source-routing frame size determination alogrithms may also
help here.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.063 No buf to dup routing_type
frame source_mac
-> dest_mac
for SR->TB from port port
nt network
- Long Syntax:
- SRT.063 No buffer available to duplicate routing_type
frame from source_mac
to dest_mac
for source-routing to transparent bridging conversion from port port
network network
- Description:
- No buffer available to copy a frame in order to send
Routes Explorer (ARE) or Spanning Tree
Explorer (STE) routing_type
frame out as a transparent bridged frame in the transparent
bridging domain. No copy of this frame will
be sent into the transparent bridge domain.
- Cause:
- Severe packet buffer shortage.
- Action:
- Check memory statistics in GWCON to verify packet buffer
level.
- Cause:
- Traffic peak using all available buffers.
- Action:
- This is the problem if this message occurs infrequently.
a bug where buffers are being lost. You can look at this with
DDT. Look at BFRLST, if 0 (NULL) there are still no free buffers.
Then look at NBFREE, if zero there was a slow buffer leak, if non-zero
then there has been a double-free of a buffer freeing the free
list.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.064 No mem for conv db (req requested_size
), disabl
- Long Syntax:
- SRT.064 No memory for conversion databse (desired size requested_size
bytes), disabling bridge
- Description:
- There is not enough free memory to allocate even a minimal size
conversion database. The bridge will be disabled.
- Cause:
- Severe shortage of memory.
- Action:
- Reduce routing table sizes in other protocols, use system with
less protocols, expand memory in router.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.065 Can't add stat ent MAC_address
on nt network
- Long Syntax:
- SRT.065 Can not add static entrie for address MAC_address
on network network
- Description:
- An attempt to add a particular static entry to the internal database
of a bridging interface having internal filtering failed.
- Cause:
- Hardware failure or software bug.
- Action:
- Contact customer service.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.066 Can't ena TB on nt network
- Long Syntax:
- SRT.066 Can not enable transparent bridging on network network
- Description:
- The bridge has been configured to enable transparent bridging on
an IEEE 802.5 Token-Ring network that does not have the hardware
to support transparent bridging. Transparent bridging will
not be enabled on this interface.
- Cause:
- Misconfiguration.
- Action:
- Correct configuration.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.067 SRF source_mac
-> dest_mac
(RIF RIF
) fwd to disabl port port
, nt network
, disc
- Long Syntax:
- SRT.067 Specifically routed frame frame from source_mac
to dest_mac
(RIF RIF
) forwarded to disabled port port
, network network
, discarded
- Description:
- A Specifically Routed frame has been sent on a
port, but that port is not configured for bridging. This should
never happen, since prior checks should prevent calling this
code if the port is not configured for bridging.
would be that the code thinks that the bridge is a two-port
bridge, but the destination port for this side of the two-port
bridge is not the correct one. This indicates an internal state
error in determining sri_tportp. The only other possibility is
that the check up at SRT.061 filed to stop the packet.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.068 Eth type table full for ethernet_type
- Long Syntax:
- SRT.068 Ethernet type table full for Ethernet type ethernet_type
- Description:
- There is no space in the Ethernet type registration table for
the specified ethernet_type. This happens when there are too
many hash collisions, and there are not enough overflow buckets.
- Cause:
- Too many added Ethernet type filters.
- Action:
- Do not use as many Ethernet type filters.
the types in use by the router are colliding too much. This
should not happen, and is a serious bug.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.069 SNAP type table full for PID protocol
- Long Syntax:
- SRT.069 Subnetwork Access Protocol table full for Protocol Identifier type protocol
- Description:
- There is no space in the SNAP PID registration table for
the specified protoocl. This happens when there are too
many hash collisions, and there are not enough overflow buckets.
- Cause:
- Too many added SNAP PID filters.
- Action:
- Do not use as many SNAP PID filters.
the types in use by the router are colliding too much. This
should not happen, and is a serious bug.
- Level:
- P-TRACE
- Short Syntax:
- SRT.070 source_mac
-> dest_mac
drp, dst add flt, port port
nt network
- Long Syntax:
- SRT.070 Frame from source_mac
to dest_mac
dropped, destination address filtered, port port
network network
- Description:
- A MAC frame has been received by the hardware, but is being dropped
because the destination MAC address is being administratively filtered
by the bridge. The frame will be dropped.
- Cause:
- Receipt of frame whose destination MAC address matches the exclusive
filter.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.071 SR not supp on port port
, net network
- Long Syntax:
- SRT.071 Source Routing not supported on port port
, net network
- Description:
- Source Routing is configured on the port which is attached to an
underlying network which inherently does not support source routing
type of functionalities. Such networks are Ethernet and FDDI.
Bridge disables source routing on the port.
- Cause:
- User misconfiguration.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.072 Conversion enabled, but not licensed, disabling
- Long Syntax:
- SRT.072 Conversion bridging (Adaptive or SR-TB) enabled, but not licensed, disabling
- Description:
- Conversion bridging has been enabled, but that feature was not
purchased as part of this software load. The conversion bridging
feature will not be enabled.
- Cause:
- Enabling feature that was not purchased.
- Action:
- Buy software with feature.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.073 SRB enabled, but not licensed, disabling
- Long Syntax:
- SRT.073 Source-routing bridging enabled, but not licensed, disabling
- Description:
- Source-routing bridging has been enabled, but that feature was not
purchased as part of this software load. The source-routing bridging
feature will not be enabled.
- Cause:
- Enabling feature that was not purchased.
- Action:
- Buy software with feature.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.074 SRB enabled on int network
, but not licensed, disabling
- Long Syntax:
- SRT.074 Source-routing bridging enabled on int network
, but not licensed, disabling
- Description:
- Source-routing bridging has been enabled, but that feature was not
purchased as part of this software load. The source-routing bridging
feature will not be enabled.
- Cause:
- Enabling feature that was not purchased.
- Action:
- Buy software with feature.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.075 STB enabled on int network
, but not licensed, disabling
- Long Syntax:
- SRT.075 Spanning tree (transparent) bridging enabled on int network
, but not licensed, disabling
- Description:
- Spanning tree (transparent)
bridging has been enabled, but that feature was not
purchased as part of this software load.
The spanning tree (transparent) bridging
feature will not be enabled.
- Cause:
- Enabling feature that was not purchased.
- Action:
- Buy software with feature.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.076 no mem to alloc NB flt
- Long Syntax:
- SRT.076 No memory to allocate a NETBIOS Filter
- Description:
- At least one configured NETBIOS Filter will not be enabled, because
there is not enough memory.
- Cause:
- Insufficient free memory.
- Action:
- Increase memory size.
- Level:
- U-INFO
- Short Syntax:
- SRT.077 input_output
NB flt lst, port port_number
, dlted
- Long Syntax:
- SRT.077 input_output
NETBIOS filter list, for port port_number
, deleted by user. Filter will not be enabled
- Description:
- The user deleted a filter list, which was part of an already
configured filter. The filter will not be enabled.
- Cause:
- User configuration error.
- Action:
- Reconfigure the filter list that was deleted.
- Level:
- U-INFO
- Short Syntax:
- SRT.078 input_output
NB flt configd for port port_number
, port doesnt exist
- Long Syntax:
- SRT.078 input_output
NETBIOS filter for port port_number
is configured, but that port number is not configured
- Description:
- The user configured a NETBIOS filter for a particular port, but that
port number is not configured.
- Cause:
- User configuration error.
- Action:
- Either reconfigure the NETBIOS filter for the correct port number, or
add to the SRT configuration the port number that was configured in
the NETBIOS filter.
- Level:
- C-TRACE
- Short Syntax:
- SRT.079 NB outp pkt fltd source_mac
-> dest_mac
, prt port
, nt network
- Long Syntax:
- SRT.079 NETBIOS Output Packet Filtered - source_mac
-> dest_mac
, port port
, network network
- Description:
- A NETBIOS packet has matched the criteria specified in a NETBIOS Filter
configuration record. The packet is dropped.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.080 no mem to alloc NB cnsl info
- Long Syntax:
- SRT.080 No memory to allocate information for NETBIOS Filter console display
- Description:
- The part of the router that handles NETBIOS console display cannot
allocate enough memory to do the complete display. Some part of the
NETBIOS console display will not be shown from the T 5 process.
- Cause:
- Insufficient free memory.
- Action:
- Increase memory size.
- Level:
- P-TRACE
- Short Syntax:
- SRT.081 NB STE converted to SRF (RIF RIF
) source_mac
-> dest_mac
from port port
- Long Syntax:
- SRT.081 NETBIOS STE converted to SRF (RIF RIF
) source_mac
-> dest_mac
from port port
- Description:
- A NETBIOS STE converted to SRF by NETBIOS Name Caching
- Level:
- P-TRACE
- Short Syntax:
- SRT.082 NB STE not converted, RIF too long
- Long Syntax:
- SRT.082 NETBIO STE not converted, RIF too long
- Description:
- NETBIO STE not converted, RIF too long
- Level:
- P-TRACE
- Short Syntax:
- SRT.083 NB find-name STE filtered (RIF RIF
) source_mac
-> dest_mac
from port port
- Long Syntax:
- SRT.083 NETBIOS find-name STE filtered (RIF RIF
) source_mac
-> dest_mac
from port port
- Description:
- A NETBIOS find-name STE has been filtered
- Level:
- P-TRACE
- Short Syntax:
- SRT.084 Hello BPDU dropped bcuz STP disabled on prt port
, nt network
- Long Syntax:
- SRT.084 Hello BPDU dropped because STP disabled on port port
, network network
- Description:
- A spanning tree Hello BPDU frame was received on a port
that has been disabled for spanning tree participation by
the "disable tree port#" command.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.085 Frame relay Port port
config on non-Frame Relay intf network_number
- Long Syntax:
- SRT.085 Frame relay Port port
configured on non-Frame relay interface network_number
- Description:
- This port uses a Frame Relay network. However,
subsequent to bridge configuration, the device configuration changed
such that the device is no longer configured to be a Frame Relay
device. This could have happened if you changed the data link
support on the device, or re-ordered the device records.
- Cause:
- Inconsistency between router device configuration and bridge
configuration.
- Action:
- Correct the data link support on the device to be of type Frame Relay
and/or correct the network number in the bridge configuration.
- Level:
- UI-ERROR
- Short Syntax:
- SRT.086 Port port
, cir= circuit_name
reg with Frly net network_number
failed, rsn= reason
- Long Syntax:
- SRT.086 Bridge port port
with circuit= circuit_name
registration with Frame relay network network_number
failed, reason= reason
- Description:
- During bridge initialization, associate ports with Frame Relay
register with the Frame Relay interface. During registration,
they let each other know about their existence and exchange some
useful information to keep about each other.
- Cause:
- The reasons for failure are
(1) Not enough memory.
(2) Another bridge port is using this circuit.
(3) The circuit is not known.
- Action:
- (1) Re-evaluate the memory requirement.
(2) Eliminate or reconfigure the overlapping bridge port, which
uses the same circuit.
(3) Configure the circuit in the Frame Relay configuration.
- Level:
- UE-ERROR
- Short Syntax:
- SRT.087 ARE max RD drop source_mac
-> dest_mac
from port port
, nt network
- Long Syntax:
- SRT.087 All Routes Explorer exceeds maximum Route Descriptors from source_mac
to dest_mac
from port port
, network network
- Description:
- An All Routes Explorer (ARE) source-routed frame has more Route
Descriptors than this bridge is configured to allow for ARE frames.
The frame will be dropped.
- Cause:
- Upstream bridge has an ARE RD limit inconsistent with this bridge.
- Action:
- Reconfigure all bridges in source-routing domain to have
consistent ARE RD limit.
- Cause:
- Network has too many hops for configured ARE RD limit.
- Action:
- Reconfigure all bridges in source-routing domain to have
ARE RD limit consistent with the diamter of the domain.
already partly modified.
- Level:
- UE-ERROR
- Short Syntax:
- SRT.088 source_mac
-> dest_mac
drp, port port_number
disabled
- Long Syntax:
- SRT.088 Frame from source_mac
to dest_mac
dropped, port port_number
is disabled
- Description:
- A frame has been received for bridging on a port that is disabled.
It will be ignored.
- Cause:
- A BDPU has been sent to the unicast address of the router on
this interface.
- Action:
- Correct action of sending node.
- Panic
- SRTimem
- Short Syntax:
- SRT: memory allocation failed
- Description:
- The SRT forwarder failed to allocate sufficient memory to hold
its most fundamental tables.
- Cause:
- Insufficient free memory.
- Action:
- Making databases for other protocols smaller.
- Action:
- Increase memory size.
- Fatal
- srtiisrt
- Short Syntax:
- SRT: Invalid i_srt on input
- Description:
- The i_srt flag passed from the handler to forwarder has an
invalid value.
- Cause:
- Software bug.
- Action:
- Take a crash dump and contact customer service.
- Fatal
- srtuimed
- Short Syntax:
- SRT: unknown input media
- Description:
- The input net type is not one of the ones understood by the
SRT bridge (802.3/Ethernet, FDDI, or 802.5).
- Cause:
- Software bug.
- Action:
- Take a crash dump and contact customer service.