TN-ERPS-MIB

All MIBs › TN-ERPS-MIB

Category: Transition Networks Media Converters

Description: Manages Transition Networks Ethernet ring protection (G.8032) ring instance and node state.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is TN-ERPS-MIB?

TN-ERPS-MIB is a Transition Networks proprietary SNMP MIB for Ethernet Ring Protection Switching per ITU-T G.8032, a protocol that prevents loops and provides sub-50ms failover on Ethernet ring topologies by blocking one designated link until a break is detected. It exposes per-ring configuration including the two ring ports and their associated APS/signal-fail MEPs, ring type, interconnection-node flag, and virtual channel usage. It is used specifically to monitor the software/hardware status of ring resiliency: the module description highlights that a persistent defect condition triggers a fault notification identifying the affected ring instance, so admins watch for these traps and the corresponding state table to know if a ring segment has failed over to its protection path. It depends on the 802.1ag/CFM MEP infrastructure referenced by the port APS/signal-fail MEP objects for defect detection, tying it to standards-based Ethernet OAM. It is deployed on Transition Networks Carrier Ethernet switches forming resilient ring topologies in metro-access and industrial networks. Engineers can download the TN-ERPS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TN-ERPS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Transition Networks Carrier Ethernet ring switch

Monitoring Examples

An operator subscribes to fault notifications keyed by tnErpsInstance and cross-checks the corresponding tnERPSTable/tnERPSEntry's tnERPSPort0/tnERPSPort1 and tnERPSRingType to identify exactly which ring segment raised the alarm. tnERPSPort0SfMep and tnERPSPort1SfMep are polled to see which port detected the signal failure that triggered the ring protection switchover. tnERPSInterconnectednode and tnERPSVirtualChannel reveal whether the affected ring is interconnected with another ring and whether a virtual channel is used, both relevant to correctly interpreting the failover topology.

What Can Be Monitored

ring persistent defect/fault notifications
per-port signal-fail MEP status
active ring port/topology
interconnected-node and virtual-channel status

Imported Objects

From IEEE8021-CFM-MIB

Dot1agCfmMepId

From IF-MIB

InterfaceIndex

From Q-BRIDGE-MIB

VlanId

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Gauge32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
MacAddress
RowStatus
TruthValue

From TN-PROTECTION-MIB

tnProtectionMIB

MODULE-IDENTITY

From TRANSITION-SMI

tnProducts

OBJECT-IDENTITY

OIDs

OID symbolic	OID numeric	Type	Access	Description
tnERPSMIB	1.3.6.1.4.1.868.2.5.109.3
tnERPSMIBNotifications	1.3.6.1.4.1.868.2.5.109.3.1
NTF tnErpsAlarmUp	1.3.6.1.4.1.868.2.5.109.3.1.1			A ERPS has cleared a defect condition. A notification (fault clearance alarm) is sent to the management entity with the OID of the ERPS that has cleared the fault. The management entity receiving the notification can identify the system from the network source address of the notification, and can identify the ERPS reporting the alarm by the indices in the OID of the variables in the notification: tnErpsInstance - Also the index of the ERPS state table entry (tnERPSStateTable).
NTF tnErpsAlarmDown	1.3.6.1.4.1.868.2.5.109.3.1.2			A ERPS has a persistent defect condition. A notification (fault alarm) is sent to the management entity with the OID of the ERPS that has detected the fault. The management entity receiving the notification can identify the system from the network source address of the notification, and can identify the ERPS reporting the defect by the indices in the OID of the variables in the notification: tnErpsInstance - Also the index of the ERPS state table entry (tnERPSStateTable).
tnERPSMgmtObjects	1.3.6.1.4.1.868.2.5.109.3.2
tnERPSTable	1.3.6.1.4.1.868.2.5.109.3.2.1		not-accessible	This table displays and sets current Ethernet Protection Switching configurations.
tnERPSEntry	1.3.6.1.4.1.868.2.5.109.3.2.1.1		not-accessible	This entry represents an Ethernet Ring Protection Switching configuration.
U32 tnERPSinstance	1.3.6.1.4.1.868.2.5.109.3.2.1.1.1	Unsigned32	not-accessible	The ID of the ERPS.
INT tnERPSPort0	1.3.6.1.4.1.868.2.5.109.3.2.1.1.2	INTEGER	read-create	This will create a Port 0 of the switch in the ring.
INT tnERPSPort1	1.3.6.1.4.1.868.2.5.109.3.2.1.1.3	INTEGER	read-create	This will create 'Port 1' of the switch in the Ring. As interconnected sub-ring will have only one ring port, 'Port 1' is configured as '0' for interconnected sub-ring. '0' in this field indicates that no 'Port 1' is associated with this instance
INT tnERPSPort0ApsMep	1.3.6.1.4.1.868.2.5.109.3.2.1.1.4	INTEGER	read-create	The Port 0 APS PDU handling MEP.
INT tnERPSPort1ApsMep	1.3.6.1.4.1.868.2.5.109.3.2.1.1.5	INTEGER	read-create	The Port 1 APS PDU handling MEP. As only one APS MEP is associated with interconnected sub-ring without virtual channel, it is configured as '0' for such ring instances. '0' in this field indicates that no Port 1 APS MEP is associated with this instance.
INT tnERPSPort0SfMep	1.3.6.1.4.1.868.2.5.109.3.2.1.1.6	INTEGER	read-create	The Port 0 Signal Fail reporting MEP.
INT tnERPSPort1SfMep	1.3.6.1.4.1.868.2.5.109.3.2.1.1.7	INTEGER	read-create	The Port 1 Signal Fail reporting MEP.
INT tnERPSRingType	1.3.6.1.4.1.868.2.5.109.3.2.1.1.8	INTEGER	read-create	Type of Protecting ring. It can be either major ring or sub-ring. As per G.8032v2, they are defined as : Major Ring: A Major ring is the Ethernet ring that is connected on two ports to an interconnection node. Sub Ring :A sub-ring is an Ethernet ring which is connected to (an)other Ethernet ring(s) or network(s) through the use of a pair of interconnection nodes. On their own, the sub-ring links do not form a closed loop. A closed connection of traffic may be formed by the sub-ring links and one or more links, that are controlled by (an)other Ethernet ring(s) or network(s), between interconnection nodes
T/F tnERPSInterconnectednode	1.3.6.1.4.1.868.2.5.109.3.2.1.1.9	TruthValue	read-create	Interconnected Node indicates that the ring instance is interconnected. Click on the checkbox to configure this. 'True' indicates it is an interconnected node for this instance. 'False' indicates that the configured instance is not interconnected.
T/F tnERPSVirtualChannel	1.3.6.1.4.1.868.2.5.109.3.2.1.1.10	TruthValue	read-create	Sub-rings can either have virtual channel or not on the interconnected node. 'True' indicates it is a sub-ring with virtual channel. 'False' indicates, sub-ring doesn't have virtual channel.
INT tnERPSMajorRingID	1.3.6.1.4.1.868.2.5.109.3.2.1.1.11	INTEGER	read-create	Major ring group ID for the interconnected sub-ring. It is used to send topology change updates on major ring. If ring is major, this value is same as the protection group ID of this ring.
INT tnERPSAlarm	1.3.6.1.4.1.868.2.5.109.3.2.1.1.12	INTEGER	read-only	There is an active alarm on the ERPS.
ROW tnERPSRowStatus	1.3.6.1.4.1.868.2.5.109.3.2.1.1.13	RowStatus	read-create	The rowstatus of the Ethernet Ring Protection Switch.
tnERPSConfigTable	1.3.6.1.4.1.868.2.5.109.3.2.2		not-accessible	This table contains the configuration of Instance Configuration.
tnERPSConfigEntry	1.3.6.1.4.1.868.2.5.109.3.2.2.1		not-accessible	This entry represents an ERPS.
INT tnERPSConfigStatus	1.3.6.1.4.1.868.2.5.109.3.2.2.1.1	INTEGER	read-only	Red: This ERPS is only created and has not yet been configured - is not active. Green: This ERPS is configured - is active��
INT tnERPSConfigGuardTime	1.3.6.1.4.1.868.2.5.109.3.2.2.1.2	INTEGER	read-write	Guard timeout value to be used to prevent ring nodes from receiving outdated R-APS messages. The period of the guard timer can be configured in 10 ms steps between 10 ms and 2 seconds, with a default value of 500 ms
INT tnERPSConfigWtrTime	1.3.6.1.4.1.868.2.5.109.3.2.2.1.3	INTEGER	read-write	The Wait To Restore timing value to be used in revertive switching. The period of the WTR time can be configured by the operator in 1 minute steps between 1 and 12 minutes with a default value of 5 minutes.
INT tnERPSConfigHoldOffTime	1.3.6.1.4.1.868.2.5.109.3.2.2.1.4	INTEGER	read-write	The timing value to be used to make persistent check on Signal Fail before switching. The range of the hold off timer is 0 to 10 seconds in steps of 100 ms
INT tnERPSConfigVersion	1.3.6.1.4.1.868.2.5.109.3.2.2.1.5	INTEGER	read-write	Select v1 or v2 as the ERPS version to be used. For fields such as Version, OpCode, Flags, and End TLV, the values used are as defined in ITU-T Y.1731 (Version 0x01 is transmitted per the current version of this Recommendation at the time of this publication.) G.8032v1 supported a single ring topology and G.8032v2 supports multiple rings/ladder topology. v1: G.8032 v1 supports a single ring topology. The v1 protocol is robust enough to work for unidirectional failure and multiple link failure scenarios in a ring topology. It allows mechanism to force switch (FS) or manual switch (MS) to take care of field maintenance scenario. v2: G.8032 v2 supports multiple rings/ladder topology. The v2 protocol also introduced other features such as Revertive/ Non-revertive mode after condition, that is causing the switch, is cleared, Administrative commands - Forced Switch (FS), Manual Switch (MS) for blocking a particular ring port, Flush FDB (Filtering database), and support of multiple ERP instances on a single ring.
T/F tnERPSConfigRevertive	1.3.6.1.4.1.868.2.5.109.3.2.2.1.6	TruthValue	read-write	In Revertive mode, after the conditions causing a protection switch has cleared, the traffic channel is restored to the working transport entity, i.e., blocked on the RPL. In Non-Revertive mode, the traffic channel continues to use the RPL, if it is not failed, after a protection switch condition has cleared.
tnERPSRPLTable	1.3.6.1.4.1.868.2.5.109.3.2.3		not-accessible	This table contains the configuration of RPL Configuration.
tnERPSRPLEntry	1.3.6.1.4.1.868.2.5.109.3.2.3.1		not-accessible	This entry represents an RPL.
INT tnERPSRPLRole	1.3.6.1.4.1.868.2.5.109.3.2.3.1.1	INTEGER	read-write	It can be either RPL owner or RPL Neighbour.
INT tnERPSRPLPort	1.3.6.1.4.1.868.2.5.109.3.2.3.1.2	INTEGER	read-write	This allows to select the east port or west port as the RPL block.
T/F tnERPSRPLClear	1.3.6.1.4.1.868.2.5.109.3.2.3.1.3	TruthValue	read-write	If the owner has to be changed, then the clear check box allows to clear the RPL owner for that ERPS ring.
tnERPSCommandTable	1.3.6.1.4.1.868.2.5.109.3.2.4		not-accessible	This table contains the configuration of Command Configuration.
tnERPSCommandEntry	1.3.6.1.4.1.868.2.5.109.3.2.4.1		not-accessible	This entry represents an Command.
INT tnERPSCommand	1.3.6.1.4.1.868.2.5.109.3.2.4.1.1	INTEGER	read-write	Administrative command. A port can be administratively configured to be in either manual switch or forced switch state.
INT tnERPSCommandPort	1.3.6.1.4.1.868.2.5.109.3.2.4.1.2	INTEGER	read-write	Port selection - Port0 or Port1 of the protection Group on which the command is applied.
tnERPSStateTable	1.3.6.1.4.1.868.2.5.109.3.2.5		not-accessible	This table contains the configuration of EVC control entry.
tnERPSStateEntry	1.3.6.1.4.1.868.2.5.109.3.2.5.1		not-accessible	This entry represents an instance State.
INT tnERPSState	1.3.6.1.4.1.868.2.5.109.3.2.5.1.1	INTEGER	read-only	ERPS state according to State Transition Tables in G.8032.
INT tnERPSStatePort0	1.3.6.1.4.1.868.2.5.109.3.2.5.1.2	INTEGER	read-only	OK: State of East port is ok. SF: State of East port is Signal Fail.
INT tnERPSStatePort1	1.3.6.1.4.1.868.2.5.109.3.2.5.1.3	INTEGER	read-only	OK: State of East port is ok. SF: State of East port is Signal Fail.
STR tnERPSStateTxAps	1.3.6.1.4.1.868.2.5.109.3.2.5.1.4	DisplayString	read-only	The transmitted APS according to State Transition Tables in G.8032.
STR tnERPSStatePort0RxAps	1.3.6.1.4.1.868.2.5.109.3.2.5.1.5	DisplayString	read-only	The received APS on Port 0 according to State Transition Tables in G.8032.
STR tnERPSStatePort1RxAps	1.3.6.1.4.1.868.2.5.109.3.2.5.1.6	DisplayString	read-only	The received APS on Port 1 according to State Transition Tables in G.8032.
INT tnERPSStateWtrRemaining	1.3.6.1.4.1.868.2.5.109.3.2.5.1.7	INTEGER	read-only	Remaining WTR timeout in milliseconds
INT tnERPSStateRPLUnBlocked	1.3.6.1.4.1.868.2.5.109.3.2.5.1.8	INTEGER	read-only	APS is received on the working flow.
INT tnERPSStateNoApsReceived	1.3.6.1.4.1.868.2.5.109.3.2.5.1.9	INTEGER	read-only	RAPS PDU is not received from the other end.
INT tnERPSStatePort0Blockstatus	1.3.6.1.4.1.868.2.5.109.3.2.5.1.10	INTEGER	read-only	Block status for Port 0 (Both traffic and R-APS block status). R-APS channel is never blocked on sub-rings without virtual channel.
INT tnERPSStatePort1Blockstatus	1.3.6.1.4.1.868.2.5.109.3.2.5.1.11	INTEGER	read-only	Block status for Port 1 (Both traffic and R-APS block status). R-APS channel is never blocked on sub-rings without virtual channel
T/F tnERPSStateFopAlarm	1.3.6.1.4.1.868.2.5.109.3.2.5.1.12	TruthValue	read-only	Failure of Protocol Defect(FOP) status. If FOP is detected, the red LED lights; otherwise the green LED lights.
tnERPSVlanTable	1.3.6.1.4.1.868.2.5.109.3.2.6		not-accessible	This table contains the configuration of vlan Configuration.
tnERPSVlanEntry	1.3.6.1.4.1.868.2.5.109.3.2.6.1		not-accessible	This entry represents an vlan.
U32 tnERPSVlanInstance	1.3.6.1.4.1.868.2.5.109.3.2.6.1.1	Unsigned32	not-accessible	The instance of the ERPS vlan.
VLA tnERPSVlanId	1.3.6.1.4.1.868.2.5.109.3.2.6.1.2	VlanId	read-write	vlan id.
ROW tnERPSVlanRowStatus	1.3.6.1.4.1.868.2.5.109.3.2.6.1.3	RowStatus	read-write	row status.
tnERPSSubRingCfgTable	1.3.6.1.4.1.868.2.5.109.3.2.7		not-accessible	This table contains the configuration of Command Configuration.
tnERPSSubRingCfgEntry	1.3.6.1.4.1.868.2.5.109.3.2.7.1		not-accessible	This entry represents an sub ring configuration.
STR tnERPSSubRingType	1.3.6.1.4.1.868.2.5.109.3.2.7.1.1	DisplayString	read-only	erps ring type.
T/F tnERPSSubRingTopologyChange	1.3.6.1.4.1.868.2.5.109.3.2.7.1.2	TruthValue	read-write	Clicking this checkbox indicates that the topology changes in the sub-ring are propagated in the major ring.
tnERPSStatisticsTable	1.3.6.1.4.1.868.2.5.109.3.2.8		not-accessible	This table contains the display of erps statistics.
tnERPSStatisticsEntry	1.3.6.1.4.1.868.2.5.109.3.2.8.1		not-accessible	This entry represents an sub ring configuration.
INT tnERPSRAPSPDUReceived	1.3.6.1.4.1.868.2.5.109.3.2.8.1.1	INTEGER	read-only	erps R-APS PDU received.
INT tnERPSRAPSPDUDropped	1.3.6.1.4.1.868.2.5.109.3.2.8.1.2	INTEGER	read-only	erps R-APS PDU dropped.
INT tnERPSLocalSFOccurred	1.3.6.1.4.1.868.2.5.109.3.2.8.1.3	INTEGER	read-only	erps local SF occurred.
INT tnERPSLocalSFCleared	1.3.6.1.4.1.868.2.5.109.3.2.8.1.4	INTEGER	read-only	erps local SF cleared.
INT tnERPSRemoteSFReceived	1.3.6.1.4.1.868.2.5.109.3.2.8.1.5	INTEGER	read-only	erps remote SF received.
INT tnERPSRemoteFSReceived	1.3.6.1.4.1.868.2.5.109.3.2.8.1.6	INTEGER	read-only	erps remote FS received.
INT tnERPSNRMessageSent	1.3.6.1.4.1.868.2.5.109.3.2.8.1.7	INTEGER	read-only	erps NR message sent.
tnERPSMIBConformance	1.3.6.1.4.1.868.2.5.109.3.3

RFC description

Manages Ethernet Ring Protection Switch (ERPS) configurations, monitoring ring state and blocking status on Transition Networks devices.

Start monitoring Transition Networks Carrier Ethernet ring switch (G.8032 ring protection/fault-notification status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download TN-ERPS-MIB

What Is TN-ERPS-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description