ELS Messages for Spanning Tree Protocol (STP)
- Level:
- C-TRACE
- Short Syntax:
- STP.001 Cfg BPDU rcv frm source_address
bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.001 Configuration BPDU received frm source_address
on bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- A configuration BPDU has been received from the specified MAC
address.
- Cause:
- Another bridge on the same network as this bridge on this port.
case of the IP tunnel it will be an IP address.
- Level:
- C-TRACE
- Short Syntax:
- STP.002 Tcn BPDU rcv frm source_address
bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.002 Toplogy change notification BPDU received frm source_address
on bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- A toplogy change notification BPDU has been received from the
specified MAC address.
- Cause:
- Topology change has been detected at or downstream of the sending
bridge.
- Action:
- None needed, the message should stop when the toplogy change is
acknowledged by the root bridge.
- Level:
- UE-ERROR
- Short Syntax:
- STP.003 Ukn BPDU type BDPU_type
rcv frm source_address
bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.003 Unkown BPDU type BDPU_type
received frm source_address
on bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- An BPDU with an undefined value in the BPDU Type field was received
from the specified host. It will be ignored.
- Cause:
- Programming error at remote bridge.
- Action:
- Correct remote node.
- Cause:
- Data corruption in received packet.
- Action:
- Eliminate source of data corruption.
- Level:
- UE-ERROR
- Short Syntax:
- STP.004 BPDU bd ID Protocol_Identifier
frm source_address
bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.004 BPDU bad protocol identifier Protocol_Identifier
frm source_address
on bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- A configuration BPDU has been received with a Protocol Identifier
that is not 0000. It will be ignored.
- Cause:
- Programming error at remote bridge.
- Action:
- Correct remote node.
- Cause:
- Data corruption in received packet.
- Action:
- Eliminate source of data corruption.
- Level:
- UE-ERROR
- Short Syntax:
- STP.005 BPDU bd ver Protocol_Version_Identifier
frm source_address
bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.005 BPDU bad Version Protocol_Version_Identifier
frm source_address
on bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- A configuration BPDU has been received with a Protocol Version
Identifier that is not 00. It will be ignored.
- Cause:
- Programming error at remote bridge.
- Action:
- Correct remote node.
- Cause:
- Data corruption in received packet.
- Action:
- Eliminate source of data corruption.
- Level:
- UE-ERROR
- Short Syntax:
- STP.006 Cfg BPDU trunc ( length
byt) frm source_address
bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.006 Configuration BPDU tuncated ( length
bytes) frm source_address
on bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- A configuration BPDU has been received which is less than 35
bytes in length. It will be ignored.
- Cause:
- Programming error at remote bridge.
- Action:
- Correct remote node.
- Cause:
- Data corruption in received packet.
- Action:
- Eliminate source of data corruption.
- Level:
- UE-ERROR
- Short Syntax:
- STP.007 Cfg BPDU unk flg flags
frm source_address
bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.007 Configuration BPDU unknown flags flags
frm source_address
on bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- A configuration BPDU has been received which has undefined
bits set in the flags field. It will be ignored.
- Cause:
- Programming error at remote bridge.
- Action:
- Correct remote node.
- Cause:
- Data corruption in received packet.
- Action:
- Eliminate source of data corruption.
- Level:
- UE-ERROR
- Short Syntax:
- STP.008 Tcn BPDU trunc ( length
byt) frm source_address
bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.008 Toplogy change notification BPDU tuncated ( length
bytes) frm source_address
on bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- A topology change notificaton BPDU has been received that is less
than 4 bytes in length. It will be ignored.
- Cause:
- Programming error at remote bridge.
- Action:
- Correct remote node.
- Cause:
- Data corruption in received packet.
- Action:
- Eliminate source of data corruption.
- Level:
- UI-ERROR
- Short Syntax:
- STP.009 No buf for BPDU bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.009 No buffer to send BDPU on bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- No packet buffer was available to construct and send a BDPU
on the specified port.
- 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:
- P-TRACE
- Short Syntax:
- STP.010 Sndg cfg BPDU bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.010 Sending Configuration BPDU on bridge_type
- bridge_instance
port bridge_port
etwork network
- Description:
- A Configuration BPDU will be sent on the specified port.
This is done normally on a periodic basis as part of the
spanning tree protocol.
The flags field in this BPDU is zero, e.g., neither the Topology Change
or the Topology Change Acknowledgement bits are set.
- Level:
- P-TRACE
- Short Syntax:
- STP.011 Sndg Cfg BPDU flgs TC
TCA
bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.011 Sending Configuration BPDU with flags TC
TCA
on bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- A Configuration BPDU will be sent on the specified port.
This is done normally on a periodic basis as part of the
spanning tree protocol. TC will be displayed if the
Topology Change bit is set in the Flags byte of the BPDU,
TCA will be displayed if the Topology Change Acknowledge bit is
set in the flags byte.
- Cause:
- The Topology Change flag is set if this bridge is the root
and it knows that there is a topology change in process. Also,
non-root bridges propogate this bit received in incoming
Configuration BPDUs.
- Action:
- None needed, this flag will be set only for the sum of the
current maximum age and current forward delay parameters (as
propogated by the root bridge).
- Cause:
- The Topology Change Acknowledge flag is set if this bridge has
received a Topology Change Notification BPDU, and this port
is the Designated Bridge on its LAN.
- Action:
- None needed, this flag will only be sent on one BDPU.
- Level:
- P-TRACE
- Short Syntax:
- STP.012 Sndg tcn BPDU bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.012 Sending Topology Change Notification BPDU on bridge_type
- bridge_instance
port bridge_port
etwork network
- Description:
- A Topology Change Notification
BPDU will be sent on the specified port.
These are sent on the root port of non-root ports when they
detect a topology change in the spanning tree.
- Cause:
- A bridge, or an interface on a bridge, has gone up or down in
this spanning tree.
- Action:
- None needed. This state persists only until a topology
change acknowledgement is received, or a timeout that
indicates that the old root bridge is no longer reachable.
- Level:
- UI-ERROR
- Short Syntax:
- STP.013 BPDU snd fld, rsn reason_code
, bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.013 BPDU send failed for reason code reason_code
on bridge_type
- bridge_instance
port bridge_port
etwork network
- Description:
- The attempt to queue a BPDU for transmission on the specified
port failed.
- Cause:
- Miscellaneous handler error. (Reason code 1.)
- Action:
- Check for error messages from handler for network.
- 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:
- U-INFO
- Short Syntax:
- STP.014 Blocking bridge_type
- bridge_instance
port bridge_port
, nt network
, det topol chg
- Long Syntax:
- STP.014 Blocking bridge_type
- bridge_instance
port bridge_port
, network network
, detecting topology change
- Description:
- This port has just been placed in Blocking state. This is
a change in the topology, so this bridge detects a topology change.
This will in turn cause topology change notifications to be sent.
- Cause:
- A bridge, or an interface on a bridge, has gone up or down in
this spanning tree.
- Action:
- None needed. This is normal when there are changes.
- Level:
- U-INFO
- Short Syntax:
- STP.015 Topol chg detected bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.015 Topology change detected on bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- A topology change notification has been received on this port,
and this port is the designated port on its LAN. This causes
the protocol to enter topology change notification state.
The topology change will be acknowledged towards the sender,
and propogated towards the root.
- Cause:
- A bridge, or an interface on a bridge, has gone up or down in
this Spanning Tree.
- Action:
- None needed. This is normal when there are changes.
- Level:
- U-INFO
- Short Syntax:
- STP.016 Select as root bridge_type
- bridge_instance
, det topol chg
- Long Syntax:
- STP.016 Selected as root on bridge_type
- bridge_instance
, detecting topology change
- Description:
- This bridge has just selected itself as the root of the
spanning tree when it previously had not been. This causes
the bridge to enter topology change notification state.
- Cause:
- A bridge, or an interface on a bridge, has gone up or down in
this spanning tree.
- Action:
- None needed. This is normal when there are changes.
- Cause:
- This is the first bridge up, thus it is the root of the tree.
- Level:
- C-INFO
- Short Syntax:
- STP.017 Tply chg ackd bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.017 Topology change acknowledged on bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- A topology change acknowledgement has been detected on the specified
port. This port is the root port of the bridge.
- Cause:
- Bridge on same LAN as our root port has set toplogy change
acknowledgement flag in outgoing Configuration BDPU. This was
in response to a topology change notification that this bridge
originated or propogated.
- Action:
- None needed. This is the normal conclusion of topology change
notification.
- Level:
- C-INFO
- Short Syntax:
- STP.018 Acking tply chg bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.018 Acknowledging topology change on bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- A topology change notification is being acknowledged on the
specified port. This is done when a topology change notification
is received on a port that is the designated port for that LAN.
- Cause:
- Change on bridge topology downstream of this bridge.
- Action:
- None needed. This is a normal port of reconfiguration of the
spanning tree.
- Level:
- C-TRACE
- Short Syntax:
- STP.019 Tplgy chg notif timer expired bridge_type
- bridge_instance
- Long Syntax:
- STP.019 Topology Change Notification timer expired on bridge_type
- bridge_instance
- Description:
- The Topology Change timer expired. This bridge will cease
sending topology change notification BPDU's on its root port.
- Cause:
- This timer expires when the bridge has been in Topology Change
Notification state for the bridge hello timer period.
- Action:
- None needed, this is the normal conclusion of this state.
- Level:
- C-TRACE
- Short Syntax:
- STP.020 Tplgy chg timer expired bridge_type
- bridge_instance
- Long Syntax:
- STP.020 Topology Change timer expired on bridge_type
- bridge_instance
- Description:
- The Topology Change timer expired. This bridge,
which is the root, will cease sending the Topology Change
in its Configuration BPDUs.
- Cause:
- This happens when this root bridge has been in Topology Change
state for the sum of
current maximum age and current forward delay parameters.
- Action:
- None needed, this is the normal conclusion of this state.
- Level:
- U-INFO
- Short Syntax:
- STP.021 Msg age tmr exp bridge_type
- bridge_instance
port bridge_port
, nt network
, try Root
- Long Syntax:
- STP.021 Message age timer expired on bridge_type
- bridge_instance
port bridge_port
, network network
, will try and become root
- Description:
- The message age timer has expired on this port. The bridge
will attempt to become the root. It will become the designated
port on that LAN.
- Cause:
- No Configuration BPDU's being received on this interface.
Either there are no bridges on this LAN, or they are down.
- Level:
- C-TRACE
- Short Syntax:
- STP.022 Hello tmr exp bridge_type
- bridge_instance
- Long Syntax:
- STP.022 Hello timer expired on bridge_type
- bridge_instance
- Description:
- The hello timer has expired on this port. Configuration
BPDUs will be sent on all ports.
- Level:
- C-TRACE
- Short Syntax:
- STP.023 Stop msg age tmr bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.023 Stopping message age timer for bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- Stopping the message age timer on this port because is it the
designated port on its LAN.
- Level:
- U-INFO
- Short Syntax:
- STP.024 Not root bridge_type
- bridge_instance
, stop hello tmr
- Long Syntax:
- STP.024 Not root anymore on bridge_type
- bridge_instance
, stopping hello timer
- Description:
- This bridge has just decided that it is no longer the root
bridge of the spanning tree. The hello timer will also be
cancelled.
- Level:
- C-INFO
- Short Syntax:
- STP.025 Stop tplgy chg age tmr bridge_type
- bridge_instance
- Long Syntax:
- STP.025 Stopping topology change timer for bridge_type
- bridge_instance
- Description:
- Stopping the topology change timer because this bridge is no
longer the root.
- Level:
- U-INFO
- Short Syntax:
- STP.026 Root bridge_type
- bridge_instance
, strt hello tmr
- Long Syntax:
- STP.026 Selected as root on bridge_type
- bridge_instance
, starting hello timer
- Description:
- This bridge has just decided that it is the root
bridge of the spanning tree. The hello timer will be
started.
- Level:
- C-TRACE
- Short Syntax:
- STP.027 Strt msg age tmr bridge_type
- bridge_instance
port bridge_port
, nt network
- Long Syntax:
- STP.027 Starting message age timer for bridge_type
- bridge_instance
port bridge_port
, network network
- Description:
- Starting the message age timer on this port.
- Level:
- U-INFO
- Short Syntax:
- STP.028 Attmpt root bridge_type
- bridge_instance
, strt hello tmr
- Long Syntax:
- STP.028 Attempting to become root on bridge_type
- bridge_instance
, starting hello timer
- Description:
- This bridge is attempting to become the root
bridge of the spanning tree. The hello timer will be
started.
- Level:
- UI-ERROR
- Short Syntax:
- STP.029 Cfg BPDU frm source_address
ign bridge_type
- bridge_instance
, inact port bridge_port
, nt network
- Long Syntax:
- STP.029 Configuration BPDU from source_address
on bridge_type
- bridge_instance
ignored, inactive port bridge_port
, network network
- Description:
- A configuration BPDU has been received from the specified MAC
address, but the port is not participating in the spanning tree
protocol.
- Level:
- UI-ERROR
- Short Syntax:
- STP.030 Tcn BPDU frm source_address
ign bridge_type
- bridge_instance
, inact port bridge_port
, nt network
- Long Syntax:
- STP.030 Topology change notification BPDU from source_address
on bridge_type
- bridge_instance
ignored, inactive port bridge_port
, network network
- Description:
- A topology change notification
BPDU has been received from the specified MAC
address, but the port is not participating in the spanning tree
protocol.
- Level:
- C-INFO
- Short Syntax:
- STP.031 bridge_type
- bridge_instance
desig port bridge_port
, nt network
- Long Syntax:
- STP.031 bridge_type
- bridge_instance
becoming designated port bridge_port
, network network
- Description:
- This bridge is declaring itelf the designated port on the LAN
connected to this port.
not, the designated-ness just gets overwritten by config BPDUs.
- Level:
- UI-ERROR
- Short Syntax:
- STP.032 DROP: bpdu_type
BPDU frm recvd on non-parti port bridge_port
, nt network
- Long Syntax:
- STP.032 DROP: bpdu_type
BPDU frame received on non-participating port bridge_port
, network network
- Description:
- A Source Route Bridge BPDU or IEEE802.1D BPDU has been received,
but the port is not participating in the SRB or IEEE802.1D Spanning
Tree Protocol.
- Fatal
- stpubpdu
- Short Syntax:
- Attempt to send unknown BPDU type
- Description:
- The code attempted to send an unknown type of BPDU.
- Cause:
- Possible software bug.
- Action:
- Get crash dump, contact customer service.