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

Ethernet Ring Protection Switching information. This MIB provides a set of known, standard setting to get the information on protected Vlan entries per ERPS doamin, ERPS rign information, the configration information related to the monitoring entries of the rign entry, ERPS ring stats, ERPS global information, and ERPS notification.

This trap is generated on the following events: - Local SF is received for the ring. - Local Clear SF is received for the ring. - Remote failure is detected on this ring. - Remote failure is cleared on this ring. - Force Switch is issued for a ring (ForcedSwitch). - Manual Switch is issued for a ring (ManualSwitch).

This trap is generated when there is any failure on a ring.

This object provides the text indicating a particular failure condition. 'R-APSPduTxFailure' will be set, when the state machine is unable to transmit an R-APS PDU. 'HwProgramFailure' will be set, when hardware programming for the ring fails. 'BufferAllocFailure' will be set, when there is memory allocation failure issues. 'TimerFailure' will be set, when there is any failure in the timer start.

This table contains the grouping of set of protected vlans. By default a group with GroupId 64 will be created and all vlans will get mapped to it.

This entry contains vlan id and group id related to ERPS domain.

The member Protected VLAN's name.

This is the Protected vlan id which is mapped to this group.

The status of this entry as per standard RowStatus conventions.

The table for creating and configuring the ring entries. Each entry has information about one ring in the switch.

The ring table entry, each entry in this table contains the attributes which define a ring.

The ERPS domain name.

This object identifies the dedicated VLAN Id used by a ring for its R-APS messages communication. It is recommended that the, * R-APS VLANs should be used only for ring R-APS message communication and should not be used for data switching and management purposes. It is recommended that R-APS VLAN is created first through the VLAN configuration before making the ring entry active, in order to avoid any loss of R-APS PDU Tx/Rx. It is not recommended to use the same R-APS VLAN ID for more than one ring.

First port of the two ring ports participating in the ring. Any interface with valid interface ID can be configured as a ring port.

Second port of the two ring ports participating in the ring. Any interface with valid interface ID can be configured as a ring port. On the interconnected node of a sub-ring, this port should be configured as zero.

This object identifies the RPL port of the ring. Valid values for this object are '0', 'IfIndex of extremeErpsRingEast' and 'IfIndex of extremeErpsRingWest'. When a port is configured as a RPL port, that node becomes RPL owner for that ring. Value '0' indicates that none of the ring ports is a RPL port and hence the node is not a RPL owner. In an interconnected node of a sub-ring, the 'extremeErpsRingEast' alone can be chosen as an RPL port when administrator decides to have the interconnected node as the RPL Owner of the sub-ring. Administrator has to ensure that, only one node in a ring is configured as RPL owner.

This object is applicable for the interconnected nodes of a sub-ring. This configuration helps to avoid the possibility of temporary loops getting formed in the sub-ring during the virtual channel recovery. This object should be set to 'true' on only one of the interconnected node of the sub-ring. (If 'extremeErpsRingPortBlockingOnVcRecovery' is configured to be 'true' on both the interconnected node of a sub-ring, then that sub-ring will be temporary cutoff from the rest of network). When this object value is set to 'true', the fsErpsRingEast of this ring node will be blocked in the event of virtual channel recovery. The extremeErpsRingEast of the sub-ring will be unblocked when the RPL port of the sub-ring is blocked and NRRB messages from the RPL Owner is received by this node.

This object identifies the node state of this ring node. If extremeErpsRingRplPort is configured for a ring node, then that ring node becomes 'rplOwner', otherwise the node remains as 'nonRplOwner'. Enumeration: 'interConnectionNode': 3, 'nonRplOwner': 2, 'rplOwner': 1.

This object identifies whether the ring is operating in revertive or nonRevertive manner. In revertive mode of operation, once the failed link recovers, the data path will be switched back from protection path to working path. In nonRevertive mode of operation, once the failed link recovers, one of the recovered link port will remain in blocked state and the data still remains in the protection path. This object can be changed, only when the rowstatus for this ring is not active. Enumeration: 'revertive': 1, 'nonRevertive': 2.

This object indicates the type of monitoring mechanism used for detecting faults of the ring link. Currently 'cfm' is supported as monitoring mechanism. For 'cfm' monitoring mechanism to monitor the ring ports, appropriate down MEPs on the R-APS VLAN of the ring has to be provisioned through extremeErpsRingCfmTable. For sub-rings, a Up & Down MEP on the sub-ring R-APS VLAN needs to be installed on fsErpsRingEast of the interconnecting nodes using the same extremeErpsRingCfmTable.

This object indicates ring port1's current status updated by ERPS control process of this ring. If the status is blocked then: - Data traffic will be blocked on this port. - R-APS messages received on this port will be given to ERPS control process but will not be forwarded. - Similarly R-APS messages received at other member ports of R-APS VLAN will not be forwarded on this port. - Locally regenerated R-APS packets will be transmitted out of this port. If the status is unblocked then: - Data traffic will be unblocked on this port. - R-APS messages received on this port will be given to ERPS control process and will be forwarded to R-APS VLAN member ports. - Similarly R-APS messages received at other member ports of R-APS VLAN can be forwarded on this port. Enumeration: 'unblocked': 2, 'blocked': 1.

This object indicates ring port2's current status updated by ERPS control process of this ring. If the status is blocked then: - Data traffic will be blocked on this port. - R-APS messages received on this port will be given to ERPS control process but will not be forwarded. - Similarly R-APS messages received at other member ports of R-APS VLAN will not be forwarded on this port. - Locally regenerated R-APS packets will be transmitted out of this port. If the status is unblocked then: - Data traffic will be unblocked on this port. - R-APS messages received on this port will be given to ERPS control process and will be forwarded to R-APS VLAN member ports. - Similarly R-APS messages received at other member ports of R-APS VLAN can be forwarded on this port. For sub-rings in interconnected nodes, this object is not valid, and get on this object will always return 'unblocked'. Enumeration: 'unblocked': 2, 'blocked': 1.

This object gives the node state as per the G.8032 state event machine. When ring Row status is not active or when ERPS is disabled in the virtual context, this object will show 'disabled(0)' status. Enumeration: 'disabled': 0, 'idle': 1, 'protection': 2, 'manualswitch': 3, 'forcedswitch': 4, 'pending': 5.

General attributes giving the current status of the ring by specifying the events/status currently present. signalFailOnEast(0) - Signal-failure on Ring Port 1 signalFailOnWest(1) - Signal-failure on Ring Port 2 remoteSignalFailOnEast(2) - Remote-signal-failure received on Ring Port 1 remoteSignalFailOnWest(3) - Remote-signal-failure received on Ring Port 2 rplBlocked(4) - Rpl-blocked waitToRestoreTimerRunning(5) - Wait-to-restore-timer-running holdTimerRunning(6) - Hold-timer-running guardTimerRunning(7) - Guard-timer-running Value 1 of the bit signifies the presence of the event associated with that bit and value zero signifies the absence of that event For example: If a signal failure is received on Ring port 1 and R-APS(SF) is received on port 2, then Bit 1 and 4 will have the value as 1. Signal failure on a port represents Port failure indication received from the monitoring entity. This does not depend on hold off timer status. If signal failure is received on ring port 1 and hold-off timer is started, then both signalFailOnEast and holdTimerRunning will have the value as 1. Bits: 'rplBlocked': 4, 'holdTimerRunning': 6, 'signalFailOnWest': 1, 'remoteSignalFailOnWest': 3, 'signalFailOnEast': 0, 'waitToRestoreTimerRunning': 5, 'remoteSignalFailOnEast': 2, 'guardTimerRunning': 7.

This object identifies the RPL Neighbour port of the ring . Valid values for this object are '0', 'IfIndex of extremeErpsRingEast' and 'IfIndex of extremeErpsRingWest'. When a port is configured as a RPL Neighbour port, that node becomes RPL Neighbour for that ring. [Reference : Section 10.1 of ITU-T G.8032 Y.1344 (03/2010)] Value '0' indicates that none of the ring ports is a RPL Neighbour port and hence the node is not a RPL Neighbour. In an interconnected node of a sub-ring, the 'extremeErpsRingEast' alone can be chosen as an RPL Neighbour port when administrator decides to have the interconnected node as the RPL Neighbour of the sub-ring. Both the RPL owner and RPL Neighbor node cannot be enabled at the same Ethernet Ring Node. Administrator has to ensure that, only one node in a ring is configured as RPL Neighbour ,and the node is adjacent to the RPL .

This object specifies the type of protection being provided by this ring instance. The following two protection switching types are possible: portBased - Port Based Protection This ring applies the protection switching mechanism for all traffic that pass through its ring ports. Hence when ERP control process decides to block or unblock a ring port, all data traffic that passes through that port gets affected. serviceBased - Service Based Protection. This ring applies the protection switching mechanism only for the set of vlans mapped to this ring instance. Hence when ERP control process decides to block or unblock a ring port, only the data traffic of the vlans that are mapped to this ring instance and that passes through that port gets affected. All ring nodes in a single ring instance must be configured with the same protection type. In a single virtual context one ring can run in port based protection mode and another ring can run in service based protection mode. It is not recommended to configure a port as ring port in a port based ring instance as well as in a service based ring instance. It is not recommended to configure a port as ring port in multiple port based ring instance. The ring protection type can be modified only when the row status of the ring entry in not in service. Enumeration: 'portBased': 1, 'serviceBased': 2.

Connectivity Fault Management group 1

Connectivity Fault Management group 2

The status of this entry as per standard RowStatus conventions.

This table contains statistics information for each of the ring present in the system. Entries in this table are created implicitly by the creation of entries in the extreneErpsRingTable.

There is one entry in this table for each entry in the extremeErpsRingTable. Each entry contains the statistics for both ring ports. For a sub-ring in an interconnected node, Port 2 statistics represent the statistics of the UP MEP installed on extremeErpsRingEast.

This object indicates the number of valid R-APS PDUs sent on the extremeErpsRingEast of the ring. R-APS PDUs include all types like R-APS(SF), R-APS(NR) & R-APS (NR, RB).

This object indicates the number of valid R-APS PDUs sent on the extremeErpsRingWest of the ring. R-APS PDUs include all types like R-APS(SF), R-APS(NR) & R-APS (NR, RB).

This object indicates the number of valid R-APS PDUs received on the extremeErpsRingEast of the ring. R-APS PDUs include all types like R-APS(SF), R-APS(NR) & R-APS (NR, RB).

This object indicates the number of valid R-APS PDUs received on the extremeErpsRingWest of the ring. R-APS PDUs include all types like R-APS(SF), R-APS(NR) & R-APS (NR, RB).

This object indicates the number of R-APS PDUs discarded on the extremeErpsRingEast of the ring. R-APS PDUs include all types like R-APS(SF), R-APS(NR) & R-APS (NR, RB). R-APS PDUs with invalid RAPS header information(wrong request/state) will be discarded.

This object indicates the number of R-APS PDUs discarded on the extremeErpsRingWest of the ring. R-APS PDUs include all types like R-APS(SF), R-APS(NR) & R-APS (NR, RB). R-APS PDUs with invalid RAPS header information(wrong request/state) will be discarded.

This object indicates the number times the extremeErpsRingEast is blocked. A port might be blocked because of local failure, or because of link configured as RPL, or if Force/Manual switch is configured

This object indicates the number times the extremeErpsRingWest is blocked. A port might be blocked because of local failure, or because of link configured as RPL, or if Force/Manual switch is configured

This object indicates the number times the extremeErpsRingEast is unblocked. A port might be unblocked because of recovery from local failure, or if the link is configured as RPL link and there is any other failure in the network, or if Force/Manual switch configuration is removed.

This object indicates the number times the extremeErpsRingWest is unblocked. A port might be unblocked because of recovery from local failure, or if the link is configured as RPL link and there is any other failure in the network, or if Force/Manual switch configuration is removed.

This object indicates the number of times the extremeErpsRingEast failed because of local SF condition.

This object indicates the number of times the extremeErpsRingWest failed because of local SF condition.

This object indicates the number of times the extremeErpsRingEast recovered from a failure (local clear SF condition).

This object indicates the number of times the extremeErpsRingWest recovered from a failure (local clear SF condition).

This object indicates if ERPS is enabled globally on the switch.

This object indicates if Display Config Warnings is enabled globally on the switch.

This object indicates if Multicast Add Ring Ports is enabled globally on the switch.

This object indicates if Multicast Send IGMP and MLD Query is enabled globally on the switch.

This object indicates if Multicast Temporary Flooding is enabled globally on the switch.

This object indicates the duration of Multicast Temporary Flooding on the switch.

This object indicates the Number of ERPS instances is configured globally on the switch.

The core compliance statement for all ERPS implementations.

The core compliance statement for all ERPS implementations.

Conformance group for ERPS Protected Vlan Entry.

Conformance group for ERPS Ring Entry.

Conformance group for ERPS Ring Cfm Entry.

Conformance group for ERPS Ring Stats Entry.

Conformance group for ERPS global information.

Conformance group for ERPS notification.

Conformance group for ERPS Protected Vlan Entry.

Conformance group for ERPS Ring Entry.