TN-ERPS-MIB: View SNMP OID List / Download MIB

VENDOR: TRANSITION ENGINEERING INC.


 Home MIB: TN-ERPS-MIB
Download as:   
SNMPv2-CONF, IF-MIB, SNMPv2-SMI, Q-BRIDGE-MIB, TN-PROTECTION-MIB, TRANSITION-SMI, SNMPv2-TC, IEEE8021-CFM-MIB

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 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
         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).
         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 no-access
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 no-access
This entry represents an Ethernet Ring Protection Switching configuration.
                 tnERPSinstance 1.3.6.1.4.1.868.2.5.109.3.2.1.1.1 unsigned32 no-access
The ID of the ERPS.
                 tnERPSPort0 1.3.6.1.4.1.868.2.5.109.3.2.1.1.2 integer read-only
This will create a Port 0 of the switch in the ring.
                 tnERPSPort1 1.3.6.1.4.1.868.2.5.109.3.2.1.1.3 integer read-only
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
                 tnERPSPort0ApsMep 1.3.6.1.4.1.868.2.5.109.3.2.1.1.4 integer read-only
The Port 0 APS PDU handling MEP.
                 tnERPSPort1ApsMep 1.3.6.1.4.1.868.2.5.109.3.2.1.1.5 integer read-only
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.
                 tnERPSPort0SfMep 1.3.6.1.4.1.868.2.5.109.3.2.1.1.6 integer read-only
The Port 0 Signal Fail reporting MEP.
                 tnERPSPort1SfMep 1.3.6.1.4.1.868.2.5.109.3.2.1.1.7 integer read-only
The Port 1 Signal Fail reporting MEP.
                 tnERPSRingType 1.3.6.1.4.1.868.2.5.109.3.2.1.1.8 integer read-only
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 Enumeration: 'major': 1, 'sub': 2.
                 tnERPSInterconnectednode 1.3.6.1.4.1.868.2.5.109.3.2.1.1.9 truthvalue read-only
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.
                 tnERPSVirtualChannel 1.3.6.1.4.1.868.2.5.109.3.2.1.1.10 truthvalue read-only
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.
                 tnERPSMajorRingID 1.3.6.1.4.1.868.2.5.109.3.2.1.1.11 integer read-only
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.
                 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. Enumeration: 'active': 1, 'notActive': 2.
                 tnERPSRowStatus 1.3.6.1.4.1.868.2.5.109.3.2.1.1.13 rowstatus read-only
The rowstatus of the Ethernet Ring Protection Switch.
         tnERPSConfigTable 1.3.6.1.4.1.868.2.5.109.3.2.2 no-access
This table contains the configuration of Instance Configuration.
             tnERPSConfigEntry 1.3.6.1.4.1.868.2.5.109.3.2.2.1 no-access
This entry represents an ERPS.
                 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 Enumeration: 'down': 0, 'up': 1.
                 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
                 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. Enumeration: 't6min': 6, 't11min': 11, 't9min': 9, 't4min': 4, 't5min': 5, 't7min': 7, 't1min': 1, 't2min': 2, 't3min': 3, 't12min': 12, 't10min': 10, 't8min': 8.
                 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
                 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. Enumeration: 'v1': 1, 'v2': 2.
                 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 no-access
This table contains the configuration of RPL Configuration.
             tnERPSRPLEntry 1.3.6.1.4.1.868.2.5.109.3.2.3.1 no-access
This entry represents an RPL.
                 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. Enumeration: 'owner': 2, 'neighbour': 3, 'none': 1.
                 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. Enumeration: 'none': 1, 'port0': 2, 'port1': 3.
                 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 no-access
This table contains the configuration of Command Configuration.
             tnERPSCommandEntry 1.3.6.1.4.1.868.2.5.109.3.2.4.1 no-access
This entry represents an Command.
                 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. Enumeration: 'forced': 3, 'none': 1, 'manual': 2, 'clear': 4.
                 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. Enumeration: 'none': 1, 'port0': 2, 'port1': 3.
         tnERPSStateTable 1.3.6.1.4.1.868.2.5.109.3.2.5 no-access
This table contains the configuration of EVC control entry.
             tnERPSStateEntry 1.3.6.1.4.1.868.2.5.109.3.2.5.1 no-access
This entry represents an instance State.
                 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. Enumeration: 'forced': 4, 'unknown': 6, 'manual': 3, 'idle': 1, 'protected': 2, 'pending': 5.
                 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. Enumeration: 'ok': 1, 'sf': 2.
                 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. Enumeration: 'ok': 1, 'sf': 2.
                 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.
                 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.
                 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.
                 tnERPSStateWtrRemaining 1.3.6.1.4.1.868.2.5.109.3.2.5.1.7 integer read-only
Remaining WTR timeout in milliseconds
                 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. Enumeration: 'unblock': 1, 'block': 0.
                 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. Enumeration: 'apsReceived': 1, 'noapsReceived': 0.
                 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. Enumeration: 'unblock': 1, 'block': 0.
                 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 Enumeration: 'unblock': 1, 'block': 0.
                 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 no-access
This table contains the configuration of vlan Configuration.
             tnERPSVlanEntry 1.3.6.1.4.1.868.2.5.109.3.2.6.1 no-access
This entry represents an vlan.
                 tnERPSVlanInstance 1.3.6.1.4.1.868.2.5.109.3.2.6.1.1 unsigned32 no-access
The instance of the ERPS vlan.
                 tnERPSVlanId 1.3.6.1.4.1.868.2.5.109.3.2.6.1.2 vlanid read-write
vlan id.
                 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 no-access
This table contains the configuration of Command Configuration.
             tnERPSSubRingCfgEntry 1.3.6.1.4.1.868.2.5.109.3.2.7.1 no-access
This entry represents an sub ring configuration.
                 tnERPSSubRingType 1.3.6.1.4.1.868.2.5.109.3.2.7.1.1 displaystring read-only
erps ring type.
                 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 no-access
This table contains the display of erps statistics.
             tnERPSStatisticsEntry 1.3.6.1.4.1.868.2.5.109.3.2.8.1 no-access
This entry represents an sub ring configuration.
                 tnERPSRAPSPDUReceived 1.3.6.1.4.1.868.2.5.109.3.2.8.1.1 integer read-only
erps R-APS PDU received.
                 tnERPSRAPSPDUDropped 1.3.6.1.4.1.868.2.5.109.3.2.8.1.2 integer read-only
erps R-APS PDU dropped.
                 tnERPSLocalSFOccurred 1.3.6.1.4.1.868.2.5.109.3.2.8.1.3 integer read-only
erps local SF occurred.
                 tnERPSLocalSFCleared 1.3.6.1.4.1.868.2.5.109.3.2.8.1.4 integer read-only
erps local SF cleared.
                 tnERPSRemoteSFReceived 1.3.6.1.4.1.868.2.5.109.3.2.8.1.5 integer read-only
erps remote SF received.
                 tnERPSRemoteFSReceived 1.3.6.1.4.1.868.2.5.109.3.2.8.1.6 integer read-only
erps remote FS received.
                 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