All MIBs › TN-ERPS-MIB › tnERPSConfigVersion
tnERPSConfigVersion
Module: TN-ERPS-MIB
OID (symbolic): TN-ERPS-MIB::tnERPSConfigVersion
OID (numeric): 1.3.6.1.4.1.868.2.5.109.3.2.2.1.5
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: 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.
What is tnERPSConfigVersion?
Selects which G.8032 protocol version this ring instance runs: v1(1), which supports only a single ring topology, or v2(2), which adds multi-ring/ladder topology support, revertive/non-revertive mode, forced/manual switch commands, and FDB flush. An admin picks v2 for modern multi-ring deployments and v1 only for compatibility with older single-ring equipment.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.868.2.5.109.3.2.2.1.5 snmpwalk -v2c -c public <target> TN-ERPS-MIB::tnERPSConfigVersion
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.868.2.5.109.3.2.2.1.5.1 snmpget -v2c -c public <target> TN-ERPS-MIB::tnERPSConfigVersion.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.868.2.5.109.3.2.2.1.5.1 i <value>
Start monitoring Transition Networks Carrier Ethernet ring switch (G.8032 ring protection/fault-notification status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TN-ERPS-MIB::tnERPSConfigVersion OID value, configure state conditions and alerts, and monitor any Transition Networks Carrier Ethernet ring switch (G.8032 ring protection/fault-notification status) from a single console.
OID Breakdown
Upper-level ancestors (10 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.868 | transition | TRANSITION-SMI |
| 1.3.6.1.4.1.868.2 | products | TRANSITION-SMI |
| 1.3.6.1.4.1.868.2.5 | tnProducts | TRANSITION-SMI |
| 1.3.6.1.4.1.868.2.5.109 | tnProtectionMIB | TN-PROTECTION-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.868.2.5.109.3 | tnERPSMIB | TN-ERPS-MIB |
| 1.3.6.1.4.1.868.2.5.109.3.2 | tnERPSMgmtObjects | TN-ERPS-MIB |
| 1.3.6.1.4.1.868.2.5.109.3.2.2 | tnERPSConfigTable | TN-ERPS-MIB |
| 1.3.6.1.4.1.868.2.5.109.3.2.2.1 | tnERPSConfigEntry | TN-ERPS-MIB |
| 1.3.6.1.4.1.868.2.5.109.3.2.2.1.5 | tnERPSConfigVersion | TN-ERPS-MIB |