TN-ERPS-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for TN-ERPS-MIB.
70
Objects
Active
Status
8
Dependencies
Imported Objects
Objects
70 total| Object Name |
|---|
tnERPSMIB OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.109.3 |
tnERPSMIBNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.109.3.1 |
tnErpsAlarmUpA 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). NOTIFICATION-TYPE .1.3.6.1.4.1.868.2.5.109.3.1.1 |
tnErpsAlarmDownA 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). NOTIFICATION-TYPE .1.3.6.1.4.1.868.2.5.109.3.1.2 |
tnERPSMgmtObjects OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.109.3.2 |
tnERPSTableThis table displays and sets current Ethernet Protection Switching configurations. SEQUENCE OF TnERPSEntry .1.3.6.1.4.1.868.2.5.109.3.2.1 |
tnERPSEntryThis entry represents an Ethernet Ring Protection Switching configuration. TnERPSEntry .1.3.6.1.4.1.868.2.5.109.3.2.1.1 |
tnERPSinstanceThe ID of the ERPS. Unsigned32 .1.3.6.1.4.1.868.2.5.109.3.2.1.1.1 |
tnERPSPort0This will create a Port 0 of the switch in the ring.rw INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.1.1.2 |
tnERPSPort1This 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 instancerw INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.1.1.3 |
tnERPSPort0ApsMepThe Port 0 APS PDU handling MEP.rw INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.1.1.4 |
tnERPSPort1ApsMepThe 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.rw INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.1.1.5 |
tnERPSPort0SfMepThe Port 0 Signal Fail reporting MEP.rw INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.1.1.6 |
tnERPSPort1SfMepThe Port 1 Signal Fail reporting MEP.rw INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.1.1.7 |
tnERPSRingTypeType 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 nodesrw Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.1.1.8 |
tnERPSInterconnectednodeInterconnected 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.109.3.2.1.1.9 |
tnERPSVirtualChannelSub-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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.109.3.2.1.1.10 |
tnERPSMajorRingIDMajor 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.rw INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.1.1.11 |
tnERPSAlarmThere is an active alarm on the ERPS.ro Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.1.1.12 |
tnERPSRowStatusThe rowstatus of the Ethernet Ring Protection Switch.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.109.3.2.1.1.13 |
tnERPSConfigTableThis table contains the configuration of Instance Configuration. SEQUENCE OF TnERPSConfigEntry .1.3.6.1.4.1.868.2.5.109.3.2.2 |
tnERPSConfigEntryThis entry represents an ERPS. TnERPSConfigEntry .1.3.6.1.4.1.868.2.5.109.3.2.2.1 |
tnERPSConfigStatusRed: This ERPS is only created and has not yet been configured - is not active.
Green: This ERPS is configured - is activero Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.2.1.1 |
tnERPSConfigGuardTimeGuard 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 msrw INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.2.1.2 |
tnERPSConfigWtrTimeThe 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.rw Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.2.1.3 |
tnERPSConfigHoldOffTimeThe 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 msrw INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.2.1.4 |
tnERPSConfigVersionSelect 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.rw Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.2.1.5 |
tnERPSConfigRevertiveIn 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.109.3.2.2.1.6 |
tnERPSRPLTableThis table contains the configuration of RPL Configuration. SEQUENCE OF TnERPSRPLEntry .1.3.6.1.4.1.868.2.5.109.3.2.3 |
tnERPSRPLEntryThis entry represents an RPL. TnERPSRPLEntry .1.3.6.1.4.1.868.2.5.109.3.2.3.1 |
tnERPSRPLRoleIt can be either RPL owner or RPL Neighbour.rw Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.3.1.1 |
tnERPSRPLPortThis allows to select the east port or west port as the RPL block.rw Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.3.1.2 |
tnERPSRPLClearIf the owner has to be changed,
then the clear check box allows to clear the RPL owner for that ERPS ring.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.109.3.2.3.1.3 |
tnERPSCommandTableThis table contains the configuration of Command Configuration. SEQUENCE OF TnERPSCommandEntry .1.3.6.1.4.1.868.2.5.109.3.2.4 |
tnERPSCommandEntryThis entry represents an Command. TnERPSCommandEntry .1.3.6.1.4.1.868.2.5.109.3.2.4.1 |
tnERPSCommandAdministrative command.
A port can be administratively configured to be in either manual switch or
forced switch state.rw Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.4.1.1 |
tnERPSCommandPortPort selection - Port0 or Port1 of the protection Group on which the command is applied.rw Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.4.1.2 |
tnERPSStateTableThis table contains the configuration of EVC control entry. SEQUENCE OF TnERPSStateEntry .1.3.6.1.4.1.868.2.5.109.3.2.5 |
tnERPSStateEntryThis entry represents an instance State. TnERPSStateEntry .1.3.6.1.4.1.868.2.5.109.3.2.5.1 |
tnERPSStateERPS state according to State Transition Tables in G.8032.ro Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.5.1.1 |
tnERPSStatePort0OK: State of East port is ok.
SF: State of East port is Signal Fail.ro Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.5.1.2 |
tnERPSStatePort1OK: State of East port is ok.
SF: State of East port is Signal Fail.ro Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.5.1.3 |
tnERPSStateTxApsThe transmitted APS according to State Transition Tables in G.8032.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.109.3.2.5.1.4 |
tnERPSStatePort0RxApsThe received APS on Port 0 according to State Transition Tables in G.8032.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.109.3.2.5.1.5 |
tnERPSStatePort1RxApsThe received APS on Port 1 according to State Transition Tables in G.8032.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.109.3.2.5.1.6 |
tnERPSStateWtrRemainingRemaining WTR timeout in millisecondsro INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.5.1.7 |
tnERPSStateRPLUnBlockedAPS is received on the working flow.ro Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.5.1.8 |
tnERPSStateNoApsReceivedRAPS PDU is not received from the other end.ro Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.5.1.9 |
tnERPSStatePort0BlockstatusBlock status for Port 0 (Both traffic and R-APS block status).
R-APS channel is never blocked on sub-rings without virtual channel.ro Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.5.1.10 |
tnERPSStatePort1BlockstatusBlock status for Port 1 (Both traffic and R-APS block status).
R-APS channel is never blocked on sub-rings without virtual channelro Enumeration .1.3.6.1.4.1.868.2.5.109.3.2.5.1.11 |
tnERPSStateFopAlarmFailure of Protocol Defect(FOP) status.
If FOP is detected, the red LED lights; otherwise the green LED lights.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.109.3.2.5.1.12 |
tnERPSVlanTableThis table contains the configuration of vlan Configuration. SEQUENCE OF TnERPSVlanEntry .1.3.6.1.4.1.868.2.5.109.3.2.6 |
tnERPSVlanEntryThis entry represents an vlan. TnERPSVlanEntry .1.3.6.1.4.1.868.2.5.109.3.2.6.1 |
tnERPSVlanInstanceThe instance of the ERPS vlan. Unsigned32 .1.3.6.1.4.1.868.2.5.109.3.2.6.1.1 |
tnERPSVlanIdvlan id.rw VlanId (Q-BRIDGE-MIB) .1.3.6.1.4.1.868.2.5.109.3.2.6.1.2 |
tnERPSVlanRowStatusrow status.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.109.3.2.6.1.3 |
tnERPSSubRingCfgTableThis table contains the configuration of Command Configuration. SEQUENCE OF TnERPSSubRingCfgEntry .1.3.6.1.4.1.868.2.5.109.3.2.7 |
tnERPSSubRingCfgEntryThis entry represents an sub ring configuration. TnERPSSubRingCfgEntry .1.3.6.1.4.1.868.2.5.109.3.2.7.1 |
tnERPSSubRingTypeerps ring type.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.109.3.2.7.1.1 |
tnERPSSubRingTopologyChangeClicking this checkbox indicates that the topology changes in the sub-ring are propagated in the major ring.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.109.3.2.7.1.2 |
tnERPSStatisticsTableThis table contains the display of erps statistics. SEQUENCE OF TnERPSStatisticsEntry .1.3.6.1.4.1.868.2.5.109.3.2.8 |
tnERPSStatisticsEntryThis entry represents an sub ring configuration. TnERPSStatisticsEntry .1.3.6.1.4.1.868.2.5.109.3.2.8.1 |
tnERPSRAPSPDUReceivederps R-APS PDU received.ro INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.8.1.1 |
tnERPSRAPSPDUDroppederps R-APS PDU dropped.ro INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.8.1.2 |
tnERPSLocalSFOccurrederps local SF occurred.ro INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.8.1.3 |
tnERPSLocalSFClearederps local SF cleared.ro INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.8.1.4 |
tnERPSRemoteSFReceivederps remote SF received.ro INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.8.1.5 |
tnERPSRemoteFSReceivederps remote FS received.ro INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.8.1.6 |
tnERPSNRMessageSenterps NR message sent.ro INTEGER .1.3.6.1.4.1.868.2.5.109.3.2.8.1.7 |
tnERPSMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.109.3.3 |