STP
higherPriorityBridge
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2009 |
Event name |
higherPriorityBridge |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.9 |
Default severity | warning |
Source stream | main |
Message format string |
Bridge $tmnxCustomerBridgeId$ with root bridge $tmnxCustomerRootBridgeId$ has higher priority, for service $svcId$ (customer $custId$) on SAP $sapEncapValue$ |
Cause |
A customer's device has been configured with a bridge priority equal to zero. |
Effect | The SAP that the customer's device is connected through will be blocked. |
Recovery | Remove the customer's device or reconfigure the customer's bridge priority with a value greater than zero. |
newRootBridge
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2007 |
Event name |
newRootBridge |
SNMP notification prefix and OID | TIMETRA-SERV-MIB.tstpTraps.7 |
Default severity | warning |
Source stream |
main |
Message format string | New root elected for service $svcId$ (customer $custId$) due to bridge parameter change |
Cause |
The previous root bridge has been aged out and a new root bridge has been elected. |
Effect | The new root bridge creates a new spanning tree topology which may denote loss of customer access or redundancy. |
Recovery | Check new topology against provisioned topology and determine the severity of connectivity loss. |
newRootSap
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2002 |
Event name |
newRootSap |
SNMP notification prefix and OID | TIMETRA-SERV-MIB.tstpTraps.2 |
Default severity | warning |
Source stream |
main |
Message format string | New root elected for service $svcId$ (customer $custId$) due to SAP $sapEncapValue$ |
Cause |
The previous root bridge has been aged out and a new root bridge has been elected. |
Effect | The new root bridge creates a new spanning tree topology which may denote a loss of customer access or redundancy. |
Recovery | Check new topology against provisioned topology and determine the severity of connectivity loss. |
newRootVcpState
Property name | Value |
---|---|
Application name | STP |
Event ID |
2004 |
Event name | newRootVcpState |
SNMP notification prefix and OID | TIMETRA-SERV-MIB.tstpTraps.4 |
Default severity | warning |
Source stream |
main |
Message format string | New root elected for service $svcId$ (customer $custId$) due to VCP state change |
Cause |
The previous root bridge has been aged out and a new root bridge has been elected. |
Effect | The new root bridge creates a new spanning tree topology which may denote a loss of customer access or redundancy. |
Recovery | Check new topology against provisioned topology and determine the severity of connectivity loss |
pipActiveProtocolChange
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2056 |
Event name |
pipActiveProtocolChange |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.42 |
Default severity | minor |
Source stream | main |
Message format string |
Service $svcId$ (customer $custId$) PIP active protocol changed. |
Cause | The spanning tree protocol on this PIP changed from RSTP to STP or vice versa. |
Effect | N/A |
Recovery | No recovery is necessary. |
receivedTCN
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2006 |
Event name |
receivedTCN |
SNMP notification prefix and OID | TIMETRA-SERV-MIB.tstpTraps.6 |
Default severity | warning |
Source stream |
main |
Message format string | TCN received for service $svcId$ (customer $custId$) on SAP $sapEncapValue$ |
Cause |
A SAP has received a TCN from another bridge. |
Effect |
This bridge will either have its Config bpdu with topology change flag set if it is a root bridge, or it will pass TCN to its root bridge. Eventually the address aging timer for the forwarding database will be made shorter for a short period of time. |
Recovery | No recovery is needed. |
sapActiveProtocolChange
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2050 |
Event name |
sapActiveProtocolChange |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.30 |
Default severity | minor |
Source stream | main |
Message format string |
Service $svcId$ (customer $custId$) SAP $sapPortId$:$sapEncapValue$ active protocol changed to $sapTlsStpOperProtocol$. |
Cause | The spanning tree protocol on this SAP changed from RSTP to STP or vice versa. |
Effect | N/A |
Recovery | No recovery is necessary. |
sapEncapDot1d
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2012 |
Event name |
sapEncapDot1d |
SNMP notification prefix and OID | TIMETRA-SERV-MIB.tstpTraps.12 |
Default severity | minor |
Source stream |
main |
Message format string | Service $svcId$ (customer $custId$) SAP $sapEncapValue$ encapsulation changed to 802.1d, bridged with $tmnxOtherBridgeId$ |
Cause | The SAP STP received a BPDU that was 802.1d encapsulated. |
Effect | The SAP STP's BPDUs will be 802.1d encapsulated. |
Recovery | No recovery is needed. |
sapEncapPVST
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2011 |
Event name |
sapEncapPVST |
SNMP notification prefix and OID | TIMETRA-SERV-MIB.tstpTraps.11 |
Default severity | minor |
Source stream |
main |
Message format string | Service $svcId$ (customer $custId$) SAP $sapEncapValue$ encapsulation changed to PVST, bridged with $tmnxOtherBridgeId$ |
Cause | The SAP STP received a BPDU that was PVST encapsulated. |
Effect | The SAP STP's BPDUs will be PVST encapsulated. |
Recovery | No recovery is needed. |
tmnxNewCistRegionalRootBridge
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2021 |
Event name |
tmnxNewCistRegionalRootBridge |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.33 |
Default severity | warning |
Source stream | main |
Message format string |
New $svcStpRegionalName$root $svcTlsStpCistRegionalRoot$ elected in service $svcId$ |
Cause | A STP selected a new regional root for the CIST. |
Effect | The query will be ignored. |
Recovery |
No recovery is necessary. |
tmnxNewMstiRegionalRootBridge
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2022 |
Event name |
tmnxNewMstiRegionalRootBridge |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.34 |
Default severity | warning |
Source stream | main |
Message format string |
New MSTI regional root $tlsMstiRegionalRoot$ elected in service $svcId$. Msti-InstanceId: $svcMstiInstanceId$ |
Cause | A STP selected a new regional root for the MSTI. |
Effect | The query will be ignored. |
Recovery |
No recovery is necessary. |
tmnxPipStpExcepCondStateChng
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2055 |
Event name |
tmnxPipStpExcepCondStateChng |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.41 |
Default severity | warning |
Source stream | main |
Message format string |
The stp exception condition state for service $svcId$ (customer $custId$) on PIP has changed to $tlsPipStpException$ |
Cause | The STP exception state has changed. |
Effect | N/A |
Recovery | N/A |
tmnxSapStpExcepCondStateChng
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2025 |
Event name |
tmnxSapStpExcepCondStateChng |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.37 |
Default severity | warning |
Source stream | main |
Message format string |
The stp exception condition state for service $svcId$ (customer $custId$) on SAP $sapEncapValue$ has changed to $sapTlsStpException$ |
Cause | A STP exception state has changed. |
Effect | N/A |
Recovery | N/A |
tmnxSdpBndStpExcepCondStateChng
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2026 |
Event name |
tmnxSdpBndStpExcepCondStateChng |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.38 |
Default severity | warning |
Source stream | main |
Message format string |
The Stp Exception condition has changed to $sdpBindTlsStpException$ in service $svcId$ (customer $custId$) on SDP Bind $sdpBindId$ |
Cause | The STP exception condition has changed on an SDP Binding." |
Effect | N/A |
Recovery | N/A |
tmnxStpMeshNotInMstRegion
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2024 |
Event name |
tmnxStpMeshNotInMstRegion |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.36 |
Default severity | warning |
Source stream | main |
Message format string |
A MSTP BPDU from outside the MST region is received on mesh SDP $sdpBindId$ in service $svcId$. The mesh will not become operational! |
Cause | A MSTP BPDU from outside the MST region is received on the mesh SDP. |
Effect | The query will be ignored. |
Recovery |
No recovery is necessary. |
tmnxStpRootGuardViolation
Property name | Value |
---|---|
Application name | STP |
Event ID |
2023 |
Event name | tmnxStpRootGuardViolation |
SNMP notification prefix and OID | TIMETRA-SERV-MIB.tstpTraps.35 |
Default severity | warning |
Source stream |
main |
Message format string | A root-guard violation is detected for service $svcId$ on SAP $sapEncapValue$ |
Cause | A STP detects a root-guard violation. |
Effect | The query will be ignored. |
Recovery |
No recovery is necessary. |
tmnxSvcNewRootSdpBind
Property name | Value |
---|---|
Application name | STP |
Event ID |
2015 |
Event name | tmnxSvcNewRootSdpBind |
SNMP notification prefix and OID | TIMETRA-SERV-MIB.tstpTraps.15 |
Default severity | warning |
Source stream |
main |
Message format string | New root bridge $svcTlsStpDesignatedRoot$ elected for service $svcId$ (customer $custId$) due to SDP Bind $sdpBindId$ |
Cause |
The previous root bridge has been aged out and a new root bridge has been elected. |
Effect | The new root bridge creates a new spanning tree topology which may denote loss of customer access or redundancy. |
Recovery | Check new topology against provisioned topology and determine the severity of connectivity loss. |
tmnxSvcSdpActiveProtocolChange
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2051 |
Event name |
tmnxSvcSdpActiveProtocolChange |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.31 |
Default severity | minor |
Source stream | main |
Message format string |
Service $svcId$ (customer $custId$) SDP Bind $sdpBindId$ active changed to $sdpBindTlsStpOperProtocol$. |
Cause | The spanning tree protocol on an SDP changed from RSTP to STP or vice versa. |
Effect | N/A |
Recovery | No recovery is necessary. |
tmnxSvcSdpBindEncapDot1d
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2020 |
Event name |
tmnxSvcSdpBindEncapDot1d |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.20 |
Default severity | minor |
Source stream | main |
Message format string |
Service $svcId$ (customer $custId$) SDP Bind $sdpBindId$ encapsulation changed to 802.1d, bridged with $tmnxOtherBridgeId$ |
Cause | The SDP Binding STP received a BPDU that was 802.1d encapsulated. |
Effect | The SDP Binding STP's BPDUs will be 802.1d encapsulated. |
Recovery | No recovery is needed. |
tmnxSvcSdpBindEncapPVST
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2019 |
Event name |
tmnxSvcSdpBindEncapPVST |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.19 |
Default severity | minor |
Source stream | main |
Message format string |
Service $svcId$ (customer $custId$) SDP Bind $sdpBindId$ encapsulation changed to PVST, bridged with $tmnxOtherBridgeId$ |
Cause | The SDP Binding STP received a BPDU that was PVST encapsulated. |
Effect | The SDP Binding STP's BPDUs will be PVST encapsulated. |
Recovery | No recovery is needed. |
tmnxSvcSdpBindRcvdHigherBriPrio
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2018 |
Event name |
tmnxSvcSdpBindRcvdHigherBriPrio |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.18 |
Default severity | warning |
Source stream | main |
Message format string |
Bridge $tmnxCustomerBridgeId$ with root bridge $tmnxCustomerRootBridgeId$ has higher priority, for service $svcId$ (customer $custId$) on SDP Bind $sdpBindId$ |
Cause |
A customer's device has been configured with a bridge priority equal to zero. |
Effect | The SDP Binding that the customer's device is connected through will be blocked. |
Recovery | Remove the customer's device or reconfigure the customer's bridge priority with a value greater than zero. |
tmnxSvcSdpBindRcvdTCN
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2017 |
Event name |
tmnxSvcSdpBindRcvdTCN |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.17 |
Default severity | warning |
Source stream | main |
Message format string |
TCN received for service $svcId$ (customer $custId$) on SDP Bind $sdpBindId$ |
Cause | A SDP Binding has received TCN from another bridge. |
Effect | This bridge will either have its Config bpdu with topology change flag set if it is a root bridge, or it will pass TCN to its root bridge. Eventually the address aging timer for the forwarding database will be made shorter for a short period of time. |
Recovery | No recovery is needed. |
tmnxSvcTopoChgSdpBindMajorState
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2014 |
Event name |
tmnxSvcTopoChgSdpBindMajorState |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.14 |
Default severity | warning |
Source stream | main |
Message format string |
Topology change for service $svcId$ (customer $custId$) due to SDP Bind $sdpBindId$ state change from $tmnxOldSdpBindTlsStpPortState$ to $sdpBindTlsStpPortState$ |
Cause |
A SDP Binding has transitioned its state from learning to forwarding or from forwarding to blocking or broken. |
Effect | The spanning tree topology has been modified which may denote loss of customer access or redundancy. |
Recovery | Check new topology against provisioned topology and determine the severity of connectivity loss. |
tmnxSvcTopoChgSdpBindState
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2016 |
Event name |
tmnxSvcTopoChgSdpBindState |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.16 |
Default severity | warning |
Source stream | main |
Message format string |
Topology change for service $svcId$ (customer $custId$) due to SDP Bind $sdpBindId$ state change from $tmnxOldSdpBindTlsStpPortState$ to $sdpBindTlsStpPortState$ |
Cause |
A SDP Binding has transitioned state to blocking or broken from a state other than forwarding. This event complements what is not covered by topologyChangeSapMajorState. |
Effect | The spanning tree topology has been modified which may denote loss of customer access or redundancy. |
Recovery | Check new topology against provisioned topology and determine the severity of connectivity loss. |
topologyChangePipMajorState
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2053 |
Event name |
topologyChangePipMajorState |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.39 |
Default severity | warning |
Source stream | main |
Message format string |
Topology change for service $svcId$ (customer $custId$) due to PIP major state change |
Cause | PIP has transitioned its state from learning to forwarding or from forwarding to blocking or broken. |
Effect | The spanning tree topology has been modified which may denote loss of customer access or redundancy. |
Recovery | Check new topology against provisioned topology and determine the severity of connectivity loss |
topologyChangePipState
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2054 |
Event name |
topologyChangePipState |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.40 |
Default severity | warning |
Source stream | main |
Message format string |
Topology change for service $svcId$ (customer $custId$) due to PIP state change |
Cause | PIP has transitioned state to blocking or broken from a state other than forwarding. This event complements what is not covered by topologyChangePipMajorState. |
Effect | The spanning tree topology has been modified which may denote loss of customer access or redundancy. |
Recovery | Check new topology against provisioned topology and determine severity of connectivity loss. |
topologyChangeSapMajorState
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2001 |
Event name |
topologyChangeSapMajorState |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.1 |
Default severity | warning |
Source stream | main |
Message format string |
Topology change for service $svcId$ (customer $custId$) due to SAP $sapEncapValue$ major state change |
Cause | A SAP has transitioned its state from learning to forwarding or from forwarding to blocking or broken. |
Effect | The spanning tree topology has been modified which may denote loss of customer access or redundancy. |
Recovery | Check new topology against provisioned topology and determine the severity of connectivity loss. |
topologyChangeSapState
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2005 |
Event name |
topologyChangeSapState |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.5 |
Default severity | warning |
Source stream | main |
Message format string |
Topology change for service $svcId$ (customer $custId$) due to SAP $sapEncapValue$ state change |
Cause | A SAP has transitioned state to blocking or broken from a state other than forwarding. This event complements what is not covered by topologyChangeSapMajorState. |
Effect | The spanning tree topology has been modified which may denote a loss of customer access or redundancy. |
Recovery | Check new topology against provisioned topology and determine the severity of connectivity loss. |
topologyChangeVcpState
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2003 |
Event name |
topologyChangeVcpState |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.3 |
Default severity | warning |
Source stream | main |
Message format string |
Topology change for service $svcId$ (customer $custId$) due to VCP state change to $tmnxVcpState$ |
Cause | A VCP has transitioned its state from disabled to forwarding or from forwarding to disabled. |
Effect | The spanning tree topology has been modified which may denote a loss of customer access or redundancy. |
Recovery | Check new topology against provisioned topology and determine the severity of connectivity loss. |
unacknowledgedTCN
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2008 |
Event name |
unacknowledgedTCN |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.8 |
Default severity | warning |
Source stream | main |
Message format string |
TCN sent for service $svcId$ (customer $custId$) to SDP $sdpId$ is unacknowledged |
Cause | A TCN sent towards the root bridge on the root port (SAP) has not been acknowledged within allowed time. |
Effect | A portion of the spanning tree topology may not have been notified that a topology change has taken place. FDB tables on some devices may take significantly longer to represent the new distribution of layer-2 addresses. |
Recovery | Diagnose this device and devices towards the root bridge for STP issues. |
vcpActiveProtocolChange
Property name | Value |
---|---|
Application name |
STP |
Event ID | 2052 |
Event name |
vcpActiveProtocolChange |
SNMP notification prefix and OID |
TIMETRA-SERV-MIB.tstpTraps.32 |
Default severity | minor |
Source stream | main |
Message format string |
Service $svcId$ (customer $custId$)VCP Active protocol changed to $svcTlsStpVcpOperProtocol$. |
Cause | The spanning tree protocol on a VCP changed from RSTP to STP or vice versa. |
Effect | N/A |
Recovery | No recovery is necessary. |