ONEACCESS-ETHOAM-EXT-MIB

TEXTUAL-CONVENTION

Possible EFD states that an interface can reside in. The value can be one of the following: efdDisabled (1) The EFD feature is disabled; efdIdle (2) The EFD feature is enabled, and there is no error condition on the interface; efdTriggered (3) The EFD feature is enabled, and there is an error condition on the interface;

TEXTUAL-CONVENTION

The CFM standard to which the MEP adheres.

TEXTUAL-CONVENTION

The CFM standard to which the MIP adheres.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

This table contains a list of Maintenance domain Intermediate Points. This table manages MIPs which are created by rules specified on the Maintenance Association (MA) and Maintenance Domain (MD) on the local device. MIPs can also be created by rules specified on Default MD Level, which is covered by dot1agCfmDefaultMdTable in IEEE8021-CFM-MIB.

OBJECT-TYPE

An entry containing configuration of a particular MIP. Each row in the table represents a different MIP.

OBJECT-TYPE

This object is the interface index of the interface either a bridge port, or an aggregated IEEE 802.1 link within a bridge port, to which the MIP is attached. Upon a restart of the system, the system SHALL, if necessary, change the value of this variable so that it indexes the entry in the interface table with the same value of ifAlias that it indexed before the system restart. If no such entry exists, then the system SHALL set this variable to 0.

OBJECT-TYPE

The MEG level of the MIP.

OBJECT-TYPE

The VID associated with the MIP.

OBJECT-TYPE

The MIP mode. The possible values are: - modey1731 (1) The MIP functions according to the Y.1731 standard - mode802dot1ag (2) The MIP functions according to the IEEE 802.1ag standard The default value is 'modey1731'.

OBJECT-TYPE

The status of the row. The writable columns in a row can not be changed if the row is active. All columns MUST have a valid value before a row can be activated.

OBJECT-TYPE

The Extended MEP table stores all the managed objects for setting the CFM standard of the MEP (Y1731, dot1ag, or hybrid), for sending LMM/DMM, for enabling transmission of RDI and AIS, for enabling EFD functionality, and for controlling Multicast Loopbacks. It is an extension of the standard MEP table. (AUGMENT - it uses the same indexes as the standard MEP table dot1agCfmMepTable) *LMM Managed objects LMM Managed objects in the extended MEP table enable the management entity to initiate transmission of Frame Loss messages. It will signal the MEP that it should start to transmit Frame Loss messages (LMM) and retrieve the information received from the Frame Loss Responses (LMR). Steps to use entries in this table: 1) Wait for oacEthOamMepLossStatus value to be false. To do this do this sequence: a. an SNMP GET for both SnmpSetSerialNo and oacEthOamMepLossStatus objects (in same SNMP PDU). b. Check if value for oacEthOamMepLossStatus is false. - if not, wait x seconds, go to step a above. - if yes, save the value of SnmpSetSerialNo and go to step 2) below 2) Change oacEthOamMepLossStatus value from false to true to ensure no other management entity will use the service. In order to not disturb a possible other NMS do this by sending an SNMP SET for both SnmpSetSerialNo and oacEthOamMepLossStatus objects (in same SNMP PDU, and make sure SNmpSetSerialNo is the first varBind). For the SnmpSetSerialNo varBind, use the value that you obtained in step 1)a. This ensures that two cooperating NMSes will not step on each others toes. 3) Setup the different data to be sent (destination, priority, interval,...), except do not set oacEthOamMepLossMessagesStart. 4) Set oacEthOamMepLossMessagesStart to true to initiate transmission of Frame Loss messages. 5) Check the value of oacEthOamMepLossResultOK to find out if the operation was successfully initiated or not. 6) The results of the running test can be retrieved from oacEthOamMepLossNbrOfTxFrames, oacEthOamMepLossNbrOfRxFrames, oacEthOamMepLossReplyLoss, oacEthOamMepLossNearEndDrops and oacEthOamMepLossFarEndDrops. 7) If you so desire, you can periodically stop and/or restart transmission of LMM messages by modifying the oacEthOamMepLossMessagesStart accordingly. 8) Change the oacEthOamMepLossStatus value back to false to allow other management entities to use the table. Setting oacEthOamMepLossStatus to false obviously implies that LMMs will no longer be transmitted, and that as such the value of oacEthOamMepLossMessagesStart will be ignored. *DMM Managed objects The DMM Managed objects in the extended MEP table are used in a manner similar to that described for LMM transmission, above. Upon successfully initiating the transmission, the objects oacEthOamMepDelayNbrOfTxFrames, oacEthOamMepDelayNbrOfRxFrames, oacEthOamMepDelayLoss, oacEthOamMepDelayMin, oacEthOamMepDelayMax, oacEthOamMepDelayAvrg, oacEthOamMepDelayJitterNegMax, oacEthOamMepDelayJitterAvrgMax, oacEthOamMepDelayJitterPosMax contain the result of the test. *AIS managed objects The AIS managed objects in the extended MEP table are used in a manner similar to that described for LMM transmission. In short, first all managed objects except oacEthOamMepAisTxEnable must be set, then oacEthOamMepAisTxEnable must be set to true to enable transmission of AIS. Set it to false to disable transmission again. *Multicast Loopbacks The Multicast Loopback managed objects are used as follows. If wanted, the SNMP manager first sets the oacEthOamMepMcastLbmDataTlv payload, or makes sure that the string is empty if no DataTLV is wanted. Next, the SNMP manager must wait for the oacEthOamMepMcastLbmStatus flag to be false. Then, the oacEthOamMepMcastLbmStatus flag must be set to true to initiate transmission of the Multicast LBM. Then the SNMP manager must wait until the MEP Multicast Loopback Initiator State Machine has set this flag back to false, which indicates that the time to wait for loopback replies has expired. Finally, the oacEthOamLbrNotRespTable and oacEthOamExtLbrTable tables can be consulted to evaluate the results. *EFD Managed Objects CFM could be considered as a line protocol for controlling Ethernet interfaces. In case of Loss of Continuity or AIS or RDI reception, the interface can be disabled. This feature is called Ethernet Fault Detection and Propagation, or EFD. It is only available for inward facing MEPs. When the interface, to which the inward facing MEP belongs, is disabled, the MEP stays up and CFM frames are still flowing. When the defect disappears, EFD will bring the MEP's interface up again. EFD can be enabled with the oacEthOamMepEfdEnable managed object. If more than one inward facing MEP is configured for a specific interface, then EFD can only be enabled on one of these MEPs. Once enabled, the EFD state of the interface can be retrieved from the oacEthOamMepEfdState managed object. In case EFD is triggered, object dot1agCfmMepDefects from the IEEE8021-CFM-MIB MIB can be used to further investigate the cause(s) of the EFD trigger.

OBJECT-TYPE

The MEP table entry

OBJECT-TYPE

The standard the MEP is following. The possible values are: - modey1731 (1) The MEP functions according to the Y.1731 standard - mode802dot1ag (2) The MEP functions according to the IEEE 802.1ag standard - modehybrid (3) MEP functions according to the IEEE 802.1ag standard, but also supports the delay and loss functionality of the Y.1731 standard The default mode is 'modehybrid'.

OBJECT-TYPE

The Target MAC Address Field to be transmitted: A unicast destination MAC address. This address will be used if the value of the column oacCfmMepLossDestIsMepId is 'false'.

OBJECT-TYPE

The Maintenance association End Point Identifier of another MEP in the same Maintenance Association to which the LMM is to be sent. This address will be used if the value of the column oacCfmMepLossDestIsMepId is 'true'.

OBJECT-TYPE

True indicates that MEPID of the target MEP is used for FrameLoss transmission. False indicates that unicast destination MAC address of the target MEP is used for FrameLoss transmission.

OBJECT-TYPE

Priority. 3 bit value to be used in the VLAN tag, if present in the transmitted frame.

OBJECT-TYPE

Interval between LMM transmissions.

OBJECT-TYPE

A Boolean flag set to true by the MEP Loopback Initiator State Machine or an MIB manager to indicate that LMM messages are going to be transmitted or are already being transmitted. Reset to false by the MEP Loopback Initiator State Machine or the same MIB manager.

OBJECT-TYPE

A Boolean flag set to true by an MIB manager to start LMM transmission, or set to false by an MIB manager to stop LMM transmission.

OBJECT-TYPE

Indicates the result of the operation: - true The FrameDelay Message(s) will be sent. - false The FrameDelay Message(s) will not be sent.

OBJECT-TYPE

The number of sent LMM frames.

OBJECT-TYPE

The number of received LMR frames.

OBJECT-TYPE

Difference between the number of sent LMMs and the number of received LMRs.

OBJECT-TYPE

Number of in-profile data frames dropped on the interface on which the local MEP is defined, sent by the remote MEP, excluding OAM frames at the MEP's MEG level.

OBJECT-TYPE

Number of in-profile data frames dropped on the interface on which the remote MEP is defined, sent by the local MEP, excluding OAM frames at the MEP's MEG level.

OBJECT-TYPE

The Target MAC Address Field to be transmitted: A unicast destination MAC address. This address will be used if the value of the column oacCfmMepDelayDestIsMepId is 'false'.

OBJECT-TYPE

The Maintenance association End Point Identifier of another MEP in the same Maintenance Association to which the DMM is to be sent. This address will be used if the value of the column oacCfmMepLossDestIsMepId is 'true'.

OBJECT-TYPE

True indicates that MEPID of the target MEP is used for FrameDelay transmission. False indicates that unicast destination MAC address of the target MEP is used for FrameDelay transmission.

OBJECT-TYPE

Priority. 3 bit value to be used in the VLAN tag, if present in the transmitted frame.

OBJECT-TYPE

Interval between DMM transmissions.

OBJECT-TYPE

A Boolean flag set to true by the MEP Loopback Initiator State Machine or an MIB manager to indicate that DMM messages are going to be transmitted or are already being transmitted. Reset to false by the MEP Loopback Initiator State Machine or the same MIB manager.

OBJECT-TYPE

Time to wait for a FrameDelay response, before considering it lost, expressed in multiples of 100msec.

OBJECT-TYPE

A Boolean flag set to true by an MIB manager to start DMM transmission, or set to false by an MIB manager to stop DMM transmission.

OBJECT-TYPE

Indicates the result of the operation: - true The FrameLoss Message(s) will be sent. - false The FrameLoss Message(s) will not be sent.

OBJECT-TYPE

The number of sent DMM frames.

OBJECT-TYPE

The number of received DMR frames.

OBJECT-TYPE

Difference between the number of sent DMMs and the number of received DMRs within the delay window (size = 10).

OBJECT-TYPE

The minimum delay that was measured in the Delay test, expressed in milliseconds.

OBJECT-TYPE

The maximum delay that was measured in the Delay test, expressed in milliseconds.

OBJECT-TYPE

The average delay that was measured in the Delay test, expressed in milliseconds.

OBJECT-TYPE

The maximum negative jitter deviation that was measured in the Delay test, expressed in milliseconds.

OBJECT-TYPE

The maximum average jitter that was measured in the Delay test, expressed in milliseconds.

OBJECT-TYPE

The maximum positive jitter deviation that was measured in the Delay test, expressed in milliseconds.

OBJECT-TYPE

Enable the transmission of RDI frames. Since RDI is a bit in the CCM frames, this setting is only taken into account if the transmission of CC messages is enabled.

OBJECT-TYPE

A Boolean flag set to true by the MEP Multicast Loopback Initiator State Machine or an MIB manager to start transmission of a single multicast Loopback message. Reset to false by the MEP Multicast Loopback Initiator State Machine once the timeframe to wait for replies has expired.

OBJECT-TYPE

Indicates the result of the operation: - true The multicast Loopback Message(s) will be (or has been) sent - false The multicast Loopback Message(s) will not be sent.

OBJECT-TYPE

The multicast Loopback Transaction Identifier of the next multicast LBM (to be) sent. This sequence number can be zero because it wraps around. The value returned is undefined if oacEthOamMepMcastLbmResult is false.

OBJECT-TYPE

An arbitrary amount of data to be included in the Data TLV of the Multicast Loopback message. When set to a zero length string, the dataTlv part of the message is omitted.

OBJECT-TYPE

Interval between AIS transmissions.

OBJECT-TYPE

Priority. 3 bit value to be used in the VLAN tag, if present in the transmitted AIS frame.

OBJECT-TYPE

Enable the transmission of AIS frames.

OBJECT-TYPE

Maintenance level on which the AIS frames will be sent.

OBJECT-TYPE

Enables Ethernet Fault Detection & propagation.

OBJECT-TYPE

The EFD state of the interface that this MEP belongs to.

OBJECT-IDENTITY

OBJECT-TYPE

This object enables or disables the CFM feature of the local device. When the object is 'true', CFM feature is enabled. When the object is 'false', CFM feature is disabled.

OBJECT-TYPE

The multicast Loopback reply table, a list of all received replies.

OBJECT-TYPE

An entry containing configuration of a particular LBR. Each row in the table represents a different LBR

OBJECT-TYPE

An index to distinguish among multiple LBRs with the same LBR Transaction Identifier field value. oacEthOamLbrReceiveOrder are assigned sequentially from 1, in the order that the Loopback Initiator received the LBRs.

OBJECT-TYPE

The unicast MAC address of the MEP that replied.

OBJECT-TYPE

If the MEP ID can be resolved, the MEPID, else 0.

OBJECT-TYPE

Table containing a list of all known peer MEPs which have not responded to the multicast Loopback Message.

OBJECT-TYPE

An entry containing configuration of a particular MEP. Each row in the table represents a different MEP`

OBJECT-TYPE

The MEP ID of the known peer MEP that did not reply.

OBJECT-TYPE

The unicast MAC address of the known peer MEP that has not replied.