IEEE802171-CFM-MIB: View SNMP OID List / Download MIB

Conectivity Fault Management module for managing IEEE 802.1ag

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. 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 dot1agCfmMepHighestPrDefect variable in the notification.

There is one CFM Stack Managed object 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.

Direction in which the MP faces on the Bridge Port

If an MEP is configured, the MEPID, else 0

MAC address of the MP.

The Default MD Level Managed Object controls MHF creation for VIDs that are not attached to a specific Maintenance Association Managed Object. The writable objects in this table need to be persistent upon reboot or restart of a device.

The Default MD Level table entry.

The index to the default MD Level table

This is a VLAN ID monitored by MA.

A value indicating if the Management entity can create MHFs (MIP Half Function) for this VID.

The MD Level at which MHFs are to be created, or -1 if defMHFnone.

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 errored interfaces.

This object is the IfIndex of the interface.

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

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

The MaintenanceDomain table. Each row in the table represents a different maintenance domain. A Maintenace domain is described in 802.1ag (3.22) 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. dot1agCfmMdTableNextIndex 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 dot1agCfmMdNameType 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.24 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.

The transportDomain for the address to which Fault Alarms are to be transmitted. Typical values will be one of (not all inclusive) list: transportDomainUdpIpv4 (from TRANSPORT-ADDRESS-MIB) transportDomainUdpIpv6 (from TRANSPORT-ADDRESS-MIB) snmpIeee802Domain (from SNMP-IEEE802-TM-MIB) The value 'zeroDotZero' indicates 'Fault Alarms are not to be transmitted', in which case the related object of SYNTAX TransportAddress must have a zero-length OCTET STRING as a value.

The transportAddress to which Fault Alarms are to be transmitted to. The type/format of this object is determined by the value of the dot1agCfmMdFaultAlarmDestDomain. If the dot1agCfmMdFaultAlarmDestDomain object has a value of 'zeroDotZero' (indicating 'Fault Alarms are not to be transmitted') then this object should have a value of a zero-length OCTET STRING.

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.

Value to be used as the index of the MA table when the management entity wants to create a new row in the table.

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. 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.17 and 18.2). This table uses two indices, first index is the index of the Maintenance Domain table. 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 dot1agCfmMaTableNextIndex needs to be inspected to find an available index for row-creation 1..4094 -> describes an MA entry associated with a VID 16777217..4294967295 -> describes an MA entry not associated with any VID

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 dot1agCfmMaNameType object.

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

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

The transportDomain for the address to which Fault Alarms are to be transmitted. Typical values will be one of (not all inclusive) list: transportDomainUdpIpv4 (from TRANSPORT-ADDRESS-MIB) transportDomainUdpIpv6 (from TRANSPORT-ADDRESS-MIB) snmpIeee802Domain (from SNMP-IEEE802-TM-MIB) The value 'zeroDotZero' indicates 'Fault Alarms are not to be transmitted', in which case the related object of SYNTAX transportAddress must have a zero-length OCTET STRING as a value.

The transportAddress to which Fault Alarms are to be transmitted to. The type/format of this object is determined by the value of the dot1agCfmMaFaultAlarmDestDomain. If the dot1agCfmMaFaultAlarmDestDomain object has a value of 'zeroDotZero' (indicating 'Fault Alarms are not to be transmitted') then this object should have a value of a zero-length OCTET STRING.

True indicate that the MA is associated with more that one VID. False indicates that the MA is associated with only one VID or no VID. This value should be false for MAs with an index greater than 16777216.

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.

If an MA is associated with multiple VIDs, then this table contains all the VIDs associated with the MA other than the primary VID. The writable objects in this table need to be persistent upon reboot or restart of a device.

The Maintenance Association VLAN table entry.

This is a VLAN ID of the vlan monitored by the MA. VID 0 means that the MA is not associated with any VLAN.

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 (in any bridge) that belong to the same 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.

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.18). 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 Transmit Loopback table. Entries in this table are created/removed at the same time than entries in the MEP table are created/removed. 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 dot1agCfmMepTransmitLbmStatus value to be 'ready'. To do this do this sequence: a. an SNMP GET for both SnmpSetSerialNo and dot1agCfmMepTransmitLbmStatus objects (in same SNMP PDU). b. Check if value for dot1agCfmMepTransmitLbmStatus is 'ready' - if not, wait x seconds, goto step a above. - if yes, save the value of SnmpSetSerialNo and go to step 2) below 2) Change dot1agCfmMepTransmitLbmStatus value from 'ready' to 'notReady' 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 dot1agCfmMepTransmitLbmStatus 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,...). 4) Record the current values of dot1agCfmMepLbrIn, dot1agCfmMepLbrInOutOfOrder, and dot1agCfmMepLbrBadMsdu. 6) Change dot1agCfmMepTransmitLbmStatus value from 'notReady' to 'transmit' to initiate transmission of Loopback messages. 7) Check the value of dot1agCfmMepTransmitLbmResultOK to find out if the operation was sucessfully initiated or not. 8) Monitor the value of dot1agCfmMepTransmitLbmMessages. 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 dot1agCfmMepLbrIn, dot1agCfmMepLbrInOutOfOrder, and dot1agCfmMepLbrBadMsdu to their old values from step 4, above, to get the results of the test. 10) Change the dot1agCfmMepTransmitLbmStatus value back to 'ready' 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. Upon successfully initiating the transmission, the variables dot1agCfmMepTransmitLtmSeqNumber and dot1agCfmMepTransmitLtmEgressIdentifier return the information required to recover the results of the LTM from the dot1agCfmLtrTable.

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.19). MEP Identifier is also known as the MEPID.

This object is the interface index of the interface eiter a bridge port, or an aggregated IEEE 802.1 link within a bridge port, to which the MEP is attached.

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 in the highest priority value allowed to pass through the bridge port for any of this MEPs VIDs. The management entity can obtain the default valuefor 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.

The transportDomain for the address to which Fault Alarms are to be transmitted. Typical values will be one of (not all inclusive) list: transportDomainUdpIpv4 (from TRANSPORT-ADDRESS-MIB) transportDomainUdpIpv6 (from TRANSPORT-ADDRESS-MIB) snmpIeee802Domain (from SNMP-IEEE802-TM-MIB) The value 'zeroDotZero' indicates 'Fault Alarms are not to be transmitted', in which case the related object of SYNTAX transportAddress must have a zero-length OCTET STRING as a value.

The transportAddress to which Fault Alarms (12.14.7.7) are to be transmitted to. The type/format of this object is determined by the value of dot1agCfmMepFaultAlarmDestDomain. If the dot1agCfmMepFaultAlarmDestDomain object has a value of 'zeroDotZero' (indicating 'Fault Alarms are not specified') then this object should have a value of a zero-length OCTET STRING. If 'Fault Alarms are not specified', the address used is that from the Maintenance Association managed object (12.14.6.1.3:e).

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 re-enabling 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 Boolean flag indicating that some other MEP in this MEP's MA is transmitting the RDI bit.

A Boolean flag (someMACstatusDefect, 20.33.6) indicating that a Port Status TLV (21.5.4) or Interface Status TLV (21.5.5) is indicating an error condition (can trigger DefMACstatus).

A Boolean flag indicating that CCMs are not being received from at least one of the configured remote MEPs.

A Boolean flag indicating that a stream of erroneous CCMs is being received from some MEP in this MEP's MA.

A Boolean flag indicating that a stream of CCMs is being received from a MEP that may be in some other MA.

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.

(optional) 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. Reset to false by the MEP Loopback Initiator State Machine.

The Target MAC Address Field to be transmitted: A unicast destination MAC address. This address will be used if the value of the column dot1agCfmMepTransmitLbmDestIsMepId 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 dot1agCfmMepTransmitLbmDestIsMepId 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 hasbeen) sent. - false The Loopback Message(s) will not be sent.

The Loopback Transaction Identifier (dot1agCfmMepNextLbmTransId) of the first LBM (to be) sent. The value returned is undefined if dot1agCfmMepTransmitLbmResultOK 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 dot1agCfmMepTransmitLtmTargetIsMepId 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 dot1agCfmMepTransmitLtmTargetIsMepId 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 decremented value is returned in the LTR. If 0 on input, the LTM is discarded. If 0 on output, the LTM is not transmitted to the next hop.

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 (dot1agCfmMepLtmNextSeqNumber) of the LTM sent. The value returned is undefined if dot1agCfmMepTransmitLtmResult 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 dot1agCfmMepTransmitLtmResult 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 LinktraceReply 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. dot1agCfmLtrReceiveOrder 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 repsonding MP, as returned ind 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. 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 field of that LTM.

An octet field holding the Next Egress Identifier returned in 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 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 dot1agCfmLtrChassisId 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 dot1agCfmLtrChassisIdSubtype object.

Management Address subtype of the bridge transmitting the LTR, if returned in a Sender ID TLV. The value is meaningless if the dot1agCfmLtrManAddress has a length of 0.

Management Address information of the bridge transmitting the LTR, if returned in the Sender ID TLV. Some limitation to the size of the TLVs carrying a Manaement Address is needed, as there is no bound on the lengths of AddressFamilyNumbers. 31 octets, the maximum length of LldpManAddress, is long enough for currently deployed systems. This MIB module assumes that SNMP (IETF STD 62) is used along with the Management Address to access the management database.

The value returned in the Ingress Action Field of the LTM.

MAC address returned in the ingress MAC address field.

Format of the Ingress Port ID.

Ingress Port ID. The format of this object is determined by the value of the dot1agCfmLtrIngressPortIdSubtype object.

The value returned in the Egress Action Field of the LTM.

MAC address returned in the egress MAC address field.

Format of the egress Port ID.

Egress Port ID. The format of this object is determined by the value of the dot1agCfmLtrEgressPortIdSubtype object.

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. SNMP SMI does not allow to stat 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 dot1agCfmLtrChassisIdSubtype object.

Management Address subtype of the bridge transmitting the CCM.

Management Address information of the bridge transmitting the CCM. Some limitation to the size of the TLVs carrying a Manaement Address is needed, as there is no bound on the lengths of AddressFamilyNumbers. 31 octets, the maximum length of LldpManAddress, is long enough for currently deployed systems. This MIB module assumes that SNMP (IETF STD 62) is used along with the Management Address to access the management database.

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