RAISECOM-DOT1AG-MIB: View SNMP OID List / Download MIB

This MIB module defines objects to CFM

A MEP has a persistent defect condition. A notification (fault alarm) is sent to the management entity with the OID of the MEP that has detected the fault. Whenever a MEP has a persistent defect, it may or may not generate a Fault Alarm to warn the system administrator of the problem, as controlled by the MEP Fault Notification Generator State Machine and associated Managed Objects. Only the highest-priority defect, as shown in Table 20-1, is reported in the Fault Alarm. If a defect with a higher priority is raised after a Fault Alarm has been issued, another Fault Alarm is issued. The management entity receiving the notification can identify the system from the network source address of the notification, and can identify the MEP reporting the defect by the indices in the OID of the rcDot1agCfmMepHighestPrDefect variable in the notification: rcDot1agCfmMdIndex - Also the index of the MEP's Maintenance Domain table entry (rcDot1agCfmMdTable). rcDot1agCfmMaIndex - Also an index (with the MD table index) of the MEP's Maintenance Association network table entry (rcDot1agCfmMaNetTable), and (with the MD table index and component ID) of the MEP's MA component table entry (rcDot1agCfmMaCompTable). rcDot1agCfmMepIdentifier - MEP Identifier and final index into the MEP table (rcDot1agCfmMepTable).

There is one CFM Stack table per bridge. It permits the retrieval of information about the Maintenance Points configured on any given interface.

The Stack table entry

This object represents the Bridge Port or aggregated port on which MEPs or MHFs might be configured. Upon a restart of the system, the system SHALL, if necessary, change the value of this variable, and rearrange the rcDot1agCfmStackTable, 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 delete all entries in the rcDot1agCfmStackTable with the interface index.

VLAN ID to which the MP is attached, or 0, if none.

MD Level of the Maintenance Point.

Direction in which the MP faces on the Bridge Port

The index of the Maintenance Domain in the rcDot1agCfmMdTable to which the MP is associated, or 0, if none.

The index of the MA in the rcDot1agCfmMaNetTable and rcDot1agCfmMaCompTable to which the MP is associated, or 0, if none.

If an MEP is configured, the MEPID, else 0

MAC address of the MP.

A value indicating the MD Level at which MHFs are to be created, and Sender ID TLV transmission by those MHFs is to be controlled, for each rcDot1agCfmDefaultMdEntry whose rcDot1agCfmDefaultMdLevel object contains the value -1. After this initialization, this object needs to be persistent upon reboot or restart of a device.

A value indicating if the Management entity can create MHFs (MIP Half Function) for the VID, for each rcDot1agCfmDefaultMdEntry whose rcDot1agCfmDefaultMdMhfCreation object contains the value defMHFdefer. Since, in this variable, there is no encompassing Maintenance Domain, the value defMHFdefer is not allowed. After this initialization, this object needs to be persistent upon reboot or restart of a device.

Enumerated value indicating what, if anything, is to be included in the Sender ID TLV (21.5.3) transmitted by MHFs created by the Default Maintenance Domain, for each rcDot1agCfmDefaultMdEntry whose rcDot1agCfmDefaultMdIdPermission object contains the value sendIdDefer. Since, in this variable, there is no encompassing Maintenance Domain, the value sendIdDefer is not allowed. After this initialization, this object needs to be persistent upon reboot or restart of a device.

For each bridge component, the Default MD Level Managed Object controls MHF creation for VIDs that are not attached to a specific Maintenance Association Managed Object, and Sender ID TLV transmission by those MHFs. For each Bridge Port, and for each VLAN ID whose data can pass through that Bridge Port, an entry in this table is used by the algorithm in subclause 22.2.3 only if there is no entry in the Maintenance Association table defining an MA for the same VLAN ID and MD Level as this table's entry, and on which MA an Up MEP is defined. If there exists such an MA, that MA's objects are used by the algorithm in subclause 22.2.3 in place of this table entry's objects. The agent maintains the value of rcDot1agCfmDefaultMdStatus to indicate whether this entry is overridden by an MA. When first initialized, the agent creates this table automatically with entries for all VLAN IDs, with the default values specified for each object. After this initialization, the writable objects in this table need to be persistent upon reboot or restart of a device.

The Default MD Level table entry.

The bridge component within the system to which the information in this rcDot1agCfmDefaultMdEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) must be equal to 1.

The Primary VID of the VLAN to which this entry's objects apply.

State of this Default MD Level table entry. True if there is no entry in the Maintenance Association table defining an MA for the same VLAN ID and MD Level as this table's entry, and on which MA an Up MEP is defined, else false.

A value indicating the MD Level at which MHFs are to be created, and Sender ID TLV transmission by those MHFs is to be controlled, for the VLAN to which this entry's objects apply. If this object has the value -1, the MD Level for MHF creation for this VLAN is controlled by rcDot1agCfmDefaultMdDefLevel.

A value indicating if the Management entity can create MHFs (MIP Half Function) for this VID at this MD Level. If this object has the value defMHFdefer, MHF creation for this VLAN is controlled by rcDot1agCfmDefaultMdDefMhfCreation. The value of this variable is meaningless if the values of rcDot1agCfmDefaultMdStatus is false.

Enumerated value indicating what, if anything, is to be included in the Sender ID TLV (21.5.3) transmitted by MHFs created by the Default Maintenance Domain. If this object has the value sendIdDefer, Sender ID TLV transmission for this VLAN is controlled by rcDot1agCfmDefaultMdDefIdPermission. The value of this variable is meaningless if the values of rcDot1agCfmDefaultMdStatus is false.

This table defines the association of VIDs into VLANs. There is an entry in this table, for each component of the bridge, for each VID that is: a) a VID belonging to a VLAN associated with more than one VID; and b) not the Primary VLAN of that VID. The entry in this table contains the Primary VID of the VLAN. By default, this table is empty, meaning that every VID is the Primary VID of a single-VID VLAN. VLANs that are associated with only one VID SHOULD NOT have an entry in this table. The writable objects in this table need to be persistent upon reboot or restart of a device.

The VLAN table entry.

The bridge component within the system to which the information in this rcDot1agCfmVlanEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) must be equal to 1.

This is a VLAN ID belonging to a VLAN that is associated with more than one VLAN ID, and this is not the Primary VID of the VLAN.

This is the Primary VLAN ID of the VLAN with which this entry's rcDot1agCfmVlanVid is associated. This value must not equal the value of rcDot1agCfmVlanVid.

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.

The CFM Configuration Error List table provides a list of Interfaces and VIDs that are incorrectly configured.

The Config Error List Table entry

The VLAN ID of the VLAN with interfaces in error.

This object is the IfIndex of the interface. 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 delete any entries in rcDot1agCfmConfigErrorListTable indexed by that InterfaceIndex value.

A vector of Boolean error conditions from 22.2.4, any of which may be true: 0) CFMleak; 1) ConflictingVids; 2) ExcessiveLevels; 3) OverlappedLevels.

This object contains an unused value for rcDot1agCfmMdIndex in the rcDot1agCfmMdTable, or a zero to indicate that none exist.

The Maintenance Domain table. Each row in the table represents a different Maintenance Domain. A Maintenance Domain is described in 802.1ag (3.21) as the network or the part of the network for which faults in connectivity are to be managed. The boundary of a Maintenance Domain is defined by a set of DSAPs, each of which can become a point of connectivity to a service instance.

The Maintenance Domain table entry. This entry is not lost upon reboot. It is backed up by stable storage.

The index to the Maintenance Domain table. rcDot1agCfmMdTableNextIndex needs to be inspected to find an available index for row-creation. Referential integrity is required, i.e., the index needs to be persistent upon a reboot or restart of a device. The index can never be reused for other Maintenance Domain. The index value should keep increasing up to the time that they wrap around. This is to facilitate access control based on OID.

The type (and thereby format) of the Maintenance Domain Name.

The Maintenance Domain name. The type/format of this object is determined by the value of the rcDot1agCfmMdNameType object. Each Maintenance Domain has unique name amongst all those used or available to a service provider or operator. It facilitates easy identification of administrative responsibility for each Maintenance Domain. Clause 3.23 defines a Maintenance Domain name as the identifier, unique over the domain for which CFM is to protect against accidental concatenation of Service Instances, of a particular Maintenance Domain.

The Maintenance Domain Level.

Enumerated value indicating whether the management entity can create MHFs (MIP Half Function) for this Maintenance Domain. Since, in this variable, there is no encompassing Maintenance Domain, the value defMHFdefer is not allowed.

Enumerated value indicating what, if anything, is to be included in the Sender ID TLV (21.5.3) transmitted by MPs configured in this Maintenance Domain. Since, in this variable, there is no encompassing Maintenance Domain, the value sendIdDefer is not allowed.

Value to be used as the index of the MA table entries, both the rcDot1agCfmMaNetTable and the rcDot1agCfmMaCompTable, for this Maintenance Domain when the management entity wants to create a new row in those tables.

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.

The Maintenance Association table. Each row in the table represents an MA. An MA is a set of MEPs, each configured with a single service instance. This is the part of the complete MA table that is constant across all Bridges in a Maintenance Domain, and across all components of a single Bridge. That part of the MA table that can vary from Bridge component to Bridge component is contained in the rcDot1agCfmMaCompTable. Creation of a Service Instance establishes a connectionless association among the selected DSAPs. Configuring a Maintenance association End Point (MEP) at each of the DSAPs creates a Maintenance Association (MA) to monitor that connectionless connectivity. The MA is identified by a Short MA Name that is unique within the Maintenance Domain and chosen to facilitate easy identification of the Service Instance. Together, the Maintenance Domain Name and the Short MA Name form the Maintenance Association Identifier (MAID) that is carried in CFM Messages to identify incorrect connectivity among Service Instances. A small integer, the Maintenance association End Point Identifier (MEPID), identifies each MEP among those configured on a single MA (802.1ag clauses 3.16 and 18.2). This table uses two indices, first index is the index of the Maintenance Domain table. The second index is the same as the index of the rcDot1agCfmMaCompEntry for the same MA. The writable objects in this table need to be persistent upon reboot or restart of a device.

The MA table entry.

Index of the MA table rcDot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.

The type (and thereby format) of the Maintenance Association Name.

The Short Maintenance Association name. The type/format of this object is determined by the value of the rcDot1agCfmMaNetNameType object. This name must be unique within a maintenance domain.

Interval between CCM transmissions to be used by all MEPs in the MA.

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.

The Maintenance Association table. Each row in the table represents an MA. An MA is a set of MEPs, each configured with a single service instance. This is the part of the complete MA table that is variable across the Bridges in a Maintenance Domain, or across the components of a single Bridge. That part of the MA table that is constant across the Bridges and their components in a Maintenance Domain is contained in the rcDot1agCfmMaNetTable. This table uses three indices, first index is the rcDot1agCfmPbbComponentIdentifier that identifies the component within the Bridge for which the information in the rcDot1agCfmMaCompEntry applies. The second is the index of the Maintenance Domain table. The third index is the same as the index of the rcDot1agCfmMaNetEntry for the same MA. The writable objects in this table need to be persistent upon reboot or restart of a device.

The MA table entry.

The bridge component within the system to which the information in this rcDot1agCfmMaCompEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) must be equal to 1.

The Primary VLAN ID with which the Maintenance Association is associated, or 0 if the MA is not attached to any VID. If the MA is associated with more than one VID, the rcDot1agCfmVlanTable lists them.

Indicates if the Management entity can create MHFs (MIP Half Function) for this MA.

Enumerated value indicating what, if anything, is to be included in the Sender ID TLV (21.5.3) transmitted by MPs configured in this MA.

The number of VIDs associated with the MA.

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.

List of MEPIDs that belong to this MA. Clause 12.14.6.1.3 specifies that a list of MEPIDs in all bridges in that MA, but since SNMP SMI does not allow to state in a MIB that an object in a table is an array, the information has to be stored in another table with two indices, being the first index, the index of the table that contains the list or array. For all bridges in which the same MAID {rcDot1agCfmMdFormat, rcDot1agCfmMdName, rcDot1agCfmMaNetFormat, and rcDot1agCfmMaNetName} is configured, the same set of rcDot1agCfmMaMepListIdentifiers must be configured in the bridges' rcDot1agCfmMaMepListTables. This allows each MEP to determine whether or not it is receiving CCMs from all of the other MEPs in the MA. For example, if one were creating a new MA whose MAID were {charString, 'Dom1', charString, 'MA1'}, that had 2 MEPs, whose MEPIDs were 1 and 3, one could, in Bridge A: 1. Get a new MD index d from rcDot1agCfmMdTableNextIndex. 2. Create the Maintenance Domain {charString, 'Dom1'}. 3. Get a new MA index a from rcDot1agCfmMdMaNextIndex [d]. 4. Create the Maintenance Association {charString, 'MA1'}. 5. Create a new rcDot1agCfmMaMepListEntry for each of the MEPs in the MA: [d, a, 1] and [d, a, 3]. 6. Create one of the new MEPs, say [d, a, 1]. Then, in Bridge B: 7. Do all of these steps 1-6, except for using the other MEPID for the new MEP in Step 6, in this example, MEPID 3. Note that, when creating the MA, MEP List Table, and MEP entries in the second bridge, the indices 'd' and 'a' identifying the MAID {charString, 'Dom1', charString, 'MA1'} may have different values than those in the first Bridge.

The known MEPS table entry.

MEPID

The status of the row. Read SNMPv2-TC (RFC1903) for an explanation of the possible values this object can take.

The Maintenance Association End Point (MEP) table. Each row in the table represents a different MEP. A MEP is an actively managed CFM entity, associated with a specific DSAP of a Service Instance, which can generate and receive CFM PDUs and track any responses. It is an end point of a single Maintenance Association, and is an endpoint of a separate Maintenance Entity for each of the other MEPs in the same Maintenance Association (802.1ag clause 3.17). This table uses three indices. The first two indices are the indices of the Maintenance Domain and MA tables, the reason being that a MEP is always related to an MA and Maintenance Domain. The MEP table also stores all the managed objects for sending LBM and LTM. *LBM Managed objects LBM Managed objects in the MEP table enables the management entity to initiate transmission of Loopback messages. It will signal the MEP that it should transmit some number of Loopback messages and detect the detection (or lack thereof) of the corresponding Loopback messages. Steps to use entries in this table: 1) Wait for rcDot1agCfmMepTransmitLbmStatus value to be true. To do this do this sequence: a. an SNMP GET for both SnmpSetSerialNo and rcDot1agCfmMepTransmitLbmStatus objects (in same SNMP PDU). b. Check if value for rcDot1agCfmMepTransmitLbmStatus is true. - 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 rcDot1agCfmMepTransmitLbmStatus value from true to false 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 rcDot1agCfmMepTransmitLbmStatus 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 (number of messages, optional TLVs,...), except do not set rcDot1agCfmMepTransmitLbmMessages. 4) Record the current values of rcDot1agCfmMepLbrIn, rcDot1agCfmMepLbrInOutOfOrder, and rcDot1agCfmMepLbrBadMsdu. 6) Set rcDot1agCfmMepTransmitLbmMessages to a non-zero value to initiate transmission of Loopback messages. 7) Check the value of rcDot1agCfmMepTransmitLbmResultOK to find out if the operation was successfully initiated or not. 8) Monitor the value of rcDot1agCfmMepTransmitLbmMessages. When it reaches 0, the last LBM has been transmitted. Wait an additional 5 seconds to ensure that all LBRs have been returned. 9) Compare rcDot1agCfmMepLbrIn, rcDot1agCfmMepLbrInOutOfOrder, and rcDot1agCfmMepLbrBadMsdu to their old values from step 4, above, to get the results of the test. 10) Change the rcDot1agCfmMepTransmitLbmStatus value back to true to allow other management entities to use the table. *LTM Managed objects The LTM Managed objects in the MEP table are used in a manner similar to that described for LBM transmission, above, except transmission is initiated by writing a value to the rcDot1agCfmMepTransmitLtmFlags object. Upon successfully initiating the transmission, the variables rcDot1agCfmMepTransmitLtmSeqNumber and rcDot1agCfmMepTransmitLtmEgressIdentifier return the information required to recover the results of the LTM from the rcDot1agCfmLtrTable.

The MEP table entry

Integer that is unique among all the MEPs in the same MA. Other definition is: a small integer, unique over a given Maintenance Association, identifying a specific Maintenance association End Point (3.18). MEP Identifier is also known as the MEPID.

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 MEP 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.

The direction in which the MEP faces on the Bridge port.

An integer indicating the Primary VID of the MEP, always one of the VIDs assigned to the MEP's MA. The value 0 indicates that either the Primary VID is that of the MEP's MA, or that the MEP's MA is associated with no VID.

Administrative state of the MEP A Boolean indicating the administrative state of the MEP. True indicates that the MEP is to function normally, and false that it is to cease functioning.

Current state of the MEP Fault Notification Generator State Machine.

If set to true, the MEP will generate CCM messages.

The priority value for CCMs and LTMs transmitted by the MEP. Default Value is the highest priority value allowed to pass through the bridge port for any of this MEPs VIDs. The management entity can obtain the default value for this variable from the priority regeneration table by extracting the highest priority value in this table on this MEPs bridge port. (1 is lowest, then 2, then 0, then 3-7).

MAC address of the MEP.

An integer value specifying the lowest priority defect that is allowed to generate fault alarm.

The time that defects must be present before a Fault Alarm is issued (fngAlarmTime. 20.33.3) (default 2.5s).

The time that defects must be absent before resetting a Fault Alarm (fngResetTime, 20.33.4) (default 10s).

The highest priority defect that has been present since the MEPs Fault Notification Generator State Machine was last in the FNG_RESET state.

A vector of Boolean error conditions from Table 20-1, any of which may be true: DefRDICCM(0) DefMACstatus(1) DefRemoteCCM(2) DefErrorCCM(3) DefXconCCM(4)

The last-received CCM that triggered an DefErrorCCM fault.

The last-received CCM that triggered a DefXconCCM fault.

The total number of out-of-sequence CCMs received from all remote MEPs.

Total number of Continuity Check messages transmitted.

Next sequence number/transaction identifier to be sent in a Loopback message. This sequence number can be zero because it wraps around.

Total number of valid, in-order Loopback Replies received.

The total number of valid, out-of-order Loopback Replies received.

The total number of LBRs received whose mac_service_data_unit did not match (except for the OpCode) that of the corresponding LBM (20.2.3).

Next transaction identifier/sequence number to be sent in a Linktrace message. This sequence number can be zero because it wraps around.

The total number of unexpected LTRs received (20.39.1).

Total number of Loopback Replies transmitted.

A Boolean flag set to true by the bridge port to indicate that another LBM may be transmitted.

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

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

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

The number of Loopback messages to be transmitted.

An arbitrary amount of data to be included in the Data TLV, if the Data TLV is selected to be sent.

Priority. 3 bit value to be used in the VLAN tag, if present in the transmitted frame. The default value is CCM priority.

Drop Enable bit value to be used in the VLAN tag, if present in the transmitted frame. For more information about VLAN Drop Enable, please check IEEE 802.1ad.

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

The Loopback Transaction Identifier (rcDot1agCfmMepNextLbmTransId) of the first LBM (to be) sent. The value returned is undefined if rcDot1agCfmMepTransmitLbmResultOK is false.

A Boolean flag set to true by the bridge port to indicate that another LTM may be transmitted. Reset to false by the MEP Linktrace Initiator State Machine.

The flags field for LTMs transmitted by the MEP. Bits: 'useFDBonly': 0.

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

An indication of the Target MAC Address Field to be transmitted: The Maintenance association End Point Identifier of another MEP in the same Maintenance Association This address will be used if the value of the column rcDot1agCfmMepTransmitLtmTargetIsMepId is 'true'.

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

The LTM TTL field. Default value, if not specified, is 64. The TTL field indicates the number of hops remaining to the LTM. Decremented by 1 by each Linktrace Responder that handles the LTM. The value returned in the LTR is one less than that received in the LTM. If the LTM TTL is 0 or 1, the LTM is not forwarded to the next hop, and if 0, no LTR is generated.

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

The LTM Transaction Identifier (rcDot1agCfmMepLtmNextSeqNumber) of the LTM sent. The value returned is undefined if rcDot1agCfmMepTransmitLtmResult is false.

Identifies the MEP Linktrace Initiator that is originating, or the Linktrace Responder that is forwarding, this LTM. The low-order six octets contain a 48-bit IEEE MAC address unique to the system in which the MEP Linktrace Initiator or Linktrace Responder resides. The high-order two octets contain a value sufficient to uniquely identify the MEP Linktrace Initiator or Linktrace Responder within that system. For most Bridges, the address of any MAC attached to the Bridge will suffice for the low-order six octets, and 0 for the high-order octets. In some situations, e.g., if multiple virtual Bridges utilizing emulated LANs are implemented in a single physical system, the high-order two octets can be used to differentiate among the transmitting entities. The value returned is undefined if rcDot1agCfmMepTransmitLtmResult is false.

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.

This table extends the MEP table and contains a list of Linktrace replies received by a specific MEP in response to a linktrace message. SNMP SMI does not allow to state in a MIB that an object in a table is an array. The solution is to take the index (or indices) of the first table and add one or more indices.

The Linktrace Reply table entry.

Transaction identifier/Sequence number returned by a previous transmit linktrace message command, indicating which LTM's response is going to be returned.

An index to distinguish among multiple LTRs with the same LTR Transaction Identifier field value. rcDot1agCfmLtrReceiveOrder are assigned sequentially from 1, in the order that the Linktrace Initiator received the LTRs.

TTL field value for a returned LTR.

Indicates if a LTM was forwarded by the responding MP, as returned in the 'FwdYes' flag of the flags field.

A boolean value stating whether the forwarded LTM reached a MEP enclosing its MA, as returned in the Terminal MEP flag of the Flags field.

An octet field holding the Last Egress Identifier returned in the LTR Egress Identifier TLV of the LTR. The Last Egress Identifier identifies the MEP Linktrace Initiator that originated, or the Linktrace Responder that forwarded, the LTM to which this LTR is the response. This is the same value as the Egress Identifier TLV of that LTM.

An octet field holding the Next Egress Identifier returned in the LTR Egress Identifier TLV of the LTR. The Next Egress Identifier Identifies the Linktrace Responder that transmitted this LTR, and can forward the LTM to the next hop. This is the same value as the Egress Identifier TLV of the forwarded LTM, if any. If the FwdYes bit of the Flags field is false, the contents of this field are undefined, i.e., any value can be transmitted, and the field is ignored by the receiver.

Value returned in the Relay Action field.

This object specifies the format of the Chassis ID returned in the Sender ID TLV of the LTR, if any. This value is meaningless if the rcDot1agCfmLtrChassisId has a length of 0.

The Chassis ID returned in the Sender ID TLV of the LTR, if any. The format of this object is determined by the value of the rcDot1agCfmLtrChassisIdSubtype object.

The TDomain that identifies the type and format of the related rcDot1agCfmMepDbManAddress object, used to access the SNMP agent of the system transmitting the LTR. Received in the LTR Sender ID TLV from that system. Typical values will be one of (not all inclusive) list: snmpUDPDomain (from SNMPv2-TM, RFC3417) snmpIeee802Domain (from SNMP-IEEE802-TM-MIB, RFC4789) The value 'zeroDotZero' (from RFC2578) indicates 'no management address was present in the LTR', in which case the related object rcDot1agCfmMepDbManAddress must have a zero-length OCTET STRING as a value.

The TAddress that can be used to access the SNMP agent of the system transmitting the CCM, received in the CCM Sender ID TLV from that system. If the related object rcDot1agCfmLtrManAddressDomain contains the value 'zeroDotZero', this object rcDot1agCfmLtrManAddress must have a zero-length OCTET STRING as a value.

The value returned in the Ingress Action Field of the LTM. The value ingNoTlv(0) indicates that no Reply Ingress TLV was returned in the LTM.

MAC address returned in the ingress MAC address field. If the rcDot1agCfmLtrIngress object contains the value ingNoTlv(0), then the contents of this object are meaningless.

Format of the Ingress Port ID. If the rcDot1agCfmLtrIngress object contains the value ingNoTlv(0), then the contents of this object are meaningless.

Ingress Port ID. The format of this object is determined by the value of the rcDot1agCfmLtrIngressPortIdSubtype object. If the rcDot1agCfmLtrIngress object contains the value ingNoTlv(0), then the contents of this object are meaningless.

The value returned in the Egress Action Field of the LTM. The value egrNoTlv(0) indicates that no Reply Egress TLV was returned in the LTM.

MAC address returned in the egress MAC address field. If the rcDot1agCfmLtrEgress object contains the value egrNoTlv(0), then the contents of this object are meaningless.

Format of the egress Port ID. If the rcDot1agCfmLtrEgress object contains the value egrNoTlv(0), then the contents of this object are meaningless.

Egress Port ID. The format of this object is determined by the value of the rcDot1agCfmLtrEgressPortIdSubtype object. If the rcDot1agCfmLtrEgress object contains the value egrNoTlv(0), then the contents of this object are meaningless.

All Organization specific TLVs returned in the LTR, if any. Includes all octets including and following the TLV Length field of each TLV, concatenated together.

The MEP Database. A database, maintained by every MEP, that maintains received information about other MEPs in the Maintenance Domain. The SMI does not allow to state in a MIB that an object in a table is an array. The solution is to take the index (or indices) of the first table and add one or more indices.

The MEP Database table entry.

Maintenance association End Point Identifier of a remote MEP whose information from the MEP Database is to be returned.

The operational state of the remote MEP IFF State machines.

The time (SysUpTime) at which the IFF Remote MEP state machine last entered either the RMEP_FAILED or RMEP_OK state.

The MAC address of the remote MEP.

State of the RDI bit in the last received CCM (true for RDI=1), or false if none has been received.

An enumerated value of the Port status TLV received in the last CCM from the remote MEP or the default value psNoPortStateTLV indicating either no CCM has been received, or that nor port status TLV was received in the last CCM.

An enumerated value of the Interface status TLV received in the last CCM from the remote MEP or the default value isNoInterfaceStatus TLV indicating either no CCM has been received, or that no interface status TLV was received in the last CCM.

This object specifies the format of the Chassis ID received in the last CCM.

The Chassis ID. The format of this object is determined by the value of the rcDot1agCfmLtrChassisIdSubtype object.

The TDomain that identifies the type and format of the related rcDot1agCfmMepDbManAddress object, used to access the SNMP agent of the system transmitting the CCM. Received in the CCM Sender ID TLV from that system. Typical values will be one of (not all inclusive) list: snmpUDPDomain (from SNMPv2-TM, RFC3417) snmpIeee802Domain (from SNMP-IEEE802-TM-MIB, RFC4789) The value 'zeroDotZero' (from RFC2578) indicates 'no management address was present in the LTR', in which case the related object rcDot1agCfmMepDbManAddress must have a zero-length OCTET STRING as a value.

The TAddress that can be used to access the SNMP agent of the system transmitting the CCM, received in the CCM Sender ID TLV from that system. If the related object rcDot1agCfmMepDbManAddressDomain contains the value 'zeroDotZero', this object rcDot1agCfmMepDbManAddress must have a zero-length OCTET STRING as a value.

The compliance statement for support of the CFM MIB module.

Objects for the Stack group.

Objects for the Default MD Level group.

Objects for the VLAN ID group.

Objects for the CFM Configuration Error List Group.

Objects for the Maintenance Domain Group.

Objects for the MA group.

Objects for the MEP group.

Objects for the MEP group.

Objects for the Notifications group.