ZTE-AN-CFM2-MIB: View SNMP OID List / Download MIB

This MIB defines managed objects of the Connectivity Fault Management module for managing Y.1731.

The management capabilities of CFM. The bit value 1 means the function represented by this bit is supported by this equipment. bit 0: value 1 means supporting zxAnCfm2LMepDmTwoWayFdMsrR1Max, zxAnCfm2LMepDmTwoWayFdMsrR2Max, zxAnCfm2LMepDmTwoWayFdMsrR3Max, zxAnCfm2LMepDmOneWayIfdvMsrR1Max, zxAnCfm2LMepDmOneWayIfdvMsrR2Max and zxAnCfm2LMepDmOneWayIfdvMsrR3Max in zxAnCfm2LocalMepTable. Bits: 'supportLocalMepDmResultBin': 0.

Enable/disable the CFM functions. Enumeration: 'disabled': 2, 'enabled': 1.

Enable/disable TLV ignoring. enabled(1): The TLV of the packet is ignored from the peer side. disabled(2): The TLV of the packet is not ignored from the peer side. Enumeration: 'disabled': 2, 'enabled': 1.

An unused value for zxAnCfm2MdIndex in the zxAnCfm2MdTable, 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.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. zxAnCfm2MdTableNextIndex 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 zxAnCfm2MdFormat 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.

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. Enumeration: 'defMHFnone': 1, 'defMHFexplicit': 3, 'defMHFdefault': 2.

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. Enumeration: 'sendIdManage': 3, 'sendIdNone': 1, 'sendIdChassis': 2, 'sendIdChassisManage': 4.

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

The status of this conceptual row. The supported actions of this conceptual row only include: 'createAndGo' and 'destroy'. To create a row in this table, a manager must set this object to createAndGo(4), and must comply with the multi-variables binding rule described in zxAnCfm2MdEntry. To delete a row in this table, a manager must set this object to destroy(6). To get this object, the agent always returns active(1).

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.19 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 dot1agCfmMaCompEntry 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 zxAnCfm2MdMaNextIndex 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 zxAnCfm2MaFormat object. This name MUST be unique within a maintenance domain.

Interval between CCM (Continuity Check Messages) transmissions to be used by all MEPs in the MA. When set this variable, value 0 is not supported.

Primary SVLAN ID of the MEP.

Primary CVLAN ID of the MEP. Value 0 means the primary CVLAN is not configured.

CCM check timeout coefficient. The CCM check timeout is the result of zxAnCfm2MaCcmTimeoutCoefficient multiplied by zxAnCfm2MaCcmInterval, and then divided by 10.

The status of this conceptual row. The supported actions of this conceptual row only include: 'createAndGo' and 'destroy'. To create a row in this table, a manager must set this object to createAndGo(4), and must comply with the multi-variables binding rule described in zxAnCfm2MaEntry. To delete a row in this table, a manager must set this object to destroy(6). To get this object, the agent always returns active(1).

The Maintenance Association End Point (MEP) table. Each row in the table represents a different MEP. An 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.19). This table uses three indices. The first two indices are the indices of the Maintenance Domain and MA tables, the reason being that an MEP is always related to an MA and Maintenance Domain.

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

The index of the NNI/UNI ports on the device.

The sub-interface of the NNI/UNI ports on the device.

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

The administrative status of the MEP. Enumeration: 'disabled': 2, 'enabled': 1.

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

Enable/disable sending CCM messages. Enumeration: 'disabled': 2, 'enabled': 1.

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

The destination MAC address type of CCM packet. Enumeration: 'unicast': 1, 'multicast': 2.

Enable/disable RDI sending in CCM packet. Enumeration: 'disabled': 2, 'enabled': 1.

Enable/disable trusting the CCM packet from remote MEP with RDI. Enumeration: 'disabled': 2, 'enabled': 1.

The total number of CCM packets transmitted.

Current state of the MEP Fault Notification Generator State Machine.

The highest priority defect that has been present since the MEPs Fault Notification Generator State Machine was last in the FNG_RESET state. Enumeration: 'defMacStatus': 2, 'defUnexpectedPeriod': 5, 'defRemoteCcm': 3, 'defUnexpectedMac': 6, 'defErrorCcm': 4, 'defUnexpectedMegLevel': 9, 'none': 255, 'defXconCcm': 8, 'defUnexpectedMepId': 7, 'defRdiCcm': 1, 'defAis': 10.

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)

Enable/disable the ETH-AIS function. Enumeration: 'disabled': 2, 'enabled': 1.

The interval for AISMs and LCKMs transmitted by the MEP. Enumeration: 'oneSecond': 1, 'oneMinute': 2.

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

Whether the MEP is in AIS condition or not. Enumeration: 'notIn': 2, 'in': 1.

MEG level at which the most immediate client layer MIPs and MEPs exist, zxAnCfm2LMepClientMegLevel, must be higher than the MD level. For example, configure client level list values '01 03 05 FF FF FF FF' to an MEP. It means that in the client level list only level 1, level 3 and level 5 take effect. Please notice: the range of this object is 0~7. Each client level in the list must be larger than the MD level of the MEP. '0xff' means client level not configured. The number of these client level is fixed with 7.

The MAC address of the MEP.

The maximum value of the first two-way frame delay measurements range. The minimum value is 0.

The maximum value of the second two-way frame delay measurements range. The minimum value is zxAnCfm2LMepDmTwoWayFdMsrR1Max.

The maximum value of the third two-way frame delay measurements range. The minimum value is zxAnCfm2LMepDmTwoWayFdMsrR2Max. This value is also the minimum value of the fourth two-way frame delay measurements range. The maximum value of the fourth range is plus infinity.

The maximum value of the first one-way inter-frame delay variation measurements range. The minimum value is 0.

The maximum value of the second one-way inter-frame delay variation measurements range. The minimum value is zxAnCfm2LMepDmOneWayIfdvMsrR1Max.

The maximum value of the third one-way inter-frame delay variation measurements range. The minimum value is zxAnCfm2LMepDmOneWayIfdvMsrR2Max. This value is also the minimum value of the fourth one-way inter-frame delay variation measurements range. The maximum value of the fourth range is plus infinity.

The status of this conceptual row. The supported actions of this conceptual row only include: 'createAndGo' and 'destroy'. To create a row in this table, a manager must set this object to createAndGo(4), and must comply with the multi-variables binding rule described in zxAnCfm2LocalMepEntry. To delete a row in this table, a manager must set this object to destroy(6). To get this object, the agent always returns active(1).

This table includes remote MEP configuration. A remote MEP is an MEP, it can use in all the CFM tests. It represents the destination of the test when the test uses MEPID as its destination.

The remote MEP table entry.

The MAC address of the remote MEP.

The administrative status of the remote MEP. Enumeration: 'disabled': 2, 'enabled': 1.

The status of this conceptual row. The supported actions of this conceptual row only include: 'createAndGo' and 'destroy'. To create a row in this table, a manager must set this object to createAndGo(4), and must comply with the multi-variables binding rule described in zxAnCfm2RemoteMepEntry. To delete a row in this table, a manager must set this object to destroy(6). To get this object, the agent always returns active(1).

This table includes MIP configuration. An MIP can be used in all the CFM tests. MIP is a CFM entry, associated with a single Maintenance Domain, and thus with single MD level, it can generate CFM PDUs, but only in response to received CFM PDUs.

The MIP table entry. When a manager wants to create a remote MEP, it must comply with the multi-variables usage rule that all the mib variables related to same fuction must be in one snmp set operation, the variables have two type: mandatory and optional. Mandatory variables must be in the one snmp set operation. Optional variables may be in the one snmp set operation with the mandatory variables, but must not be used alone. To create an MIP, there are two cases base on the MIP is assigned to a physical port or a logical port, and the mandatory and optional variables for each case are different. To create an MIP assign to physical port: - mandatoty: zxAnCfm2MipRowStatus zxAnCfm2MipIfIndex - optional : zxAnCfm2MipSubIfIndex zxAnCfm2MipIfIndex, zxAnCfm2MipSubIfIndex can not be modified.

The index of the NNI/UNI ports on the device.

The sub-interface of the NNI/UNI ports on the device.

The status of this conceptual row. The supported actions of this conceptual row only include: 'createAndGo' and 'destroy'. To create a row in this table, a manager must set this object to createAndGo(4), and must comply with the multi-variables binding rule described in zxAnCfm2MipEntry. To delete a row in this table, a manager must set this object to destroy(6). To get this object, the agent always returns active(1).

The Maintenance Association End Point (MEP) connectivity operation table stores all the managed objects for sending LBM. 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 zxAnCfm2MepTransLbmEnable value to be disabled. To do this do this sequence: a. an SNMP GET for both snmpSetSerialNo and zxAnCfm2MepTransLbmEnable objects (in same SNMP PDU). b. Check if value for zxAnCfm2MepTransLbmEnable is disabled. - if not, wait x seconds, go to step a above. - if enabled, save the value of snmpSetSerialNo and go to step 2) below 2) Change zxAnCfm2MepTransLbmEnable value from disabled to enabled 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 zxAnCfm2MepTransLbmEnable 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. Setting this MIB object does not set the corresponding LBIactive state machine variable. 3) Setup the different data to be sent (number of messages, optional TLVs,...). 4) Record the current values of zxAnCfm2MepLbrInInOrder, zxAnCfm2MepLbrInOutOfOrder, and zxAnCfm2MepLbrBadMsdu. 5) Check the value of zxAnCfm2MepTransLbmResultOk to find out if the operation was successfully initiated or not. 6) Monitor the value of zxAnCfm2MepTransLbmEnable. When it is reset to false, the last LBM has been transmitted. Wait an additional 5 seconds to ensure that all LBRs have been returned. 7) Compare zxAnCfm2MepLbrInInOrder, zxAnCfm2MepLbrInOutOfOrder, and zxAnCfm2MepLbrBadMsdu to their old values from step 4, above, to get the results of the test.

The Loopback table entry.

Enable/disable the LBM function. Enumeration: 'disabled': 2, 'enabled': 1.

The total number of Loopback messages to be transmitted.

The destination MAC address type of LBM packet. Enumeration: 'unicast': 1, 'multicast': 2.

The application type of LBM. It means to verify bidirectional connectivity of an MEP with an MIP or a peer MEP. Enumeration: 'connectivity': 1.

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

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 zxAnCfm2MepTransLbmDestMepType is 'mepId'.

The MEP type. macAddr(1): The unicast destination MAC address of the target MEP is used for Loopback transmission. mepId(2): The MEP ID of the target MEP is used for Loopback transmission. Enumeration: 'mepId': 2, 'macAddr': 1.

An arbitrary amount of data to be included in the Data TLV, if the Data TLV is selected to be sent. The value 0 means not configured and no data tlv is included in the frame.

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

LMB timeout. If the MEP does not receive LBR in time, the LBR packets may be discarded.

The result of the operation: yes(1): The Loopback Message(s) will be (or has been) sent. no(2): The Loopback Message(s) will not be sent. Enumeration: 'yes': 1, 'no': 2.

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

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

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

The total number of Loopback Replies transmitted.

The maximum latency.

The minimum latency.

The average latency.

This table includes multicast Loopback result. Before start a mulitcast LBM user must first get all the entry of this table, and after the LBM is over, user must get all the entry of this table again, and compare all the entry to get the result of multicast LBM.

The multicast Lookback Reply table entry. All the varibles in this entry is read only.

The mac address of the destination MEP.

The total LBR packets received by the MEP from the same remote MEP that responsed the LBR PDUs when received LBM from the local MEP.

The maximum latency.

The minimum latency.

The average latency.

The Maintenance Association End Point (MEP) LinkTrace operation table stores all the managed objects for sending LTM. LTM Managed objects in the MEP table enables the management entity to initiate transmission of LinkTrace messages. It will signal the MEP that it SHOULD transmit some number of LinkTrace messages and detect the detection (or lack thereof) of the corresponding LinkTrace messages. Steps to use entries in this table: 1) Wait for zxAnCfm2MepTransLtmEnable value to be disabled. To do this do this sequence: a. an SNMP GET for both snmpSetSerialNo and zxAnCfm2MepTransLtmEnable objects (in same SNMP PDU). b. Check if value for zxAnCfm2MepTransLtmEnable is disabled. - if not, wait x seconds, go to step a above. - if enabled, save the value of snmpSetSerialNo and go to step 2) below 2) Change zxAnCfm2MepTransLtmEnable value from disabled to enabled 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 zxAnCfm2MepTransLtmEnable 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. Setting this MIB object does not set the corresponding LBIactive state machine variable. 3) Setup the different data to be sent (number of messages, ,...). 4) Check the value of zxAnCfm2MepTransLtmResultOk to find out if the operation was successfully initiated or not. 5) Monitor the value of zxAnCfm2MepTransLtmEnable. When it is reset to false, the last LTM has been transmitted. Wait an additional 5 seconds to ensure that all LTRs have been returned. 6) Read the zxAnCfm2MepLinkTraceReplyTable to get the results of the test.

The LinkTrace table entry. All the varibles writable in the entry can be modified after the MEP entry created, and the variables are reset when the entry is destroyed.

Enable/disable the LTM function. Enumeration: 'disabled': 2, 'enabled': 1.

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 zxAnCfm2MepTransLtmTargetMepType is 'macAddr'.

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 zxAnCfm2MepTransLtmTargetMepType is 'mepId'.

The MEP type. macAddr(1): The unicast destination MAC address of the target MEP is used for LinkTrace transmission. mepId(2): The MEPID of the target MEP is used for LinkTrace transmission. Enumeration: 'mepId': 2, 'macAddr': 1.

The LTM TTL field. The TTL field indicates the number of hops remaining to the LTM. Decremented by 1 by each LTR (Link Trace 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.

The LTM timeout. If the MEP does not receive LTR in time, the LTR packets may be discarded.

The result of the operation: yes(1): The LinkTrace Message(s) will be (or has been) sent. no(2): The LinkTrace Message(s) will not be sent. Enumeration: 'yes': 1, 'no': 2.

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

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

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. zxAnCfm2MepLtrReceiveOrder are assigned sequentially from 1, in the order that the LinkTrace Initiator received the LTRs.

TTL field value for a returned LTR.

Whether a LTM was forwarded by the responding MP. Enumeration: 'notForwarded': 2, 'forwarded': 1.

Whether the forwarded LTM reached a MEP enclosing its MA. Enumeration: 'yes': 1, 'no': 2.

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.

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

MAC address returned in the ingress MAC address field.

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

MAC address returned in the egress MAC address field.

The Maintenance Association End Point (MEP) performance measurement operation table stores all the managed objects for sending DMM. Steps to use entries in this table: 1) Wait for zxAnCfm2MepDmEnable value to be disabled. To do this do this sequence: a. an SNMP GET for both snmpSetSerialNo and zxAnCfm2MepDmEnable objects (in same SNMP PDU). b. Check if value for zxAnCfm2MepDmEnable is disabled. - if not, wait x seconds, go to step a above. - if enabled, save the value of snmpSetSerialNo and go to step 2) below 2) Change zxAnCfm2MepDmEnable value from disabled to enabled 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 zxAnCfm2MepDmEnable and other delay measurement objects (such as zxAnCfm2MepDmPriority,...) (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) Check the value of zxAnCfm2MepDmResultOk to find out if the operation was successfully initiated or not. 4) Monitor the value of zxAnCfm2MepDmEnable. When it is reset to false, the last DMM has been transmitted. 5) Get the results of the test from zxAnCfm2MepDmRltTable.

The Delay Measurement table entry.

The frame delay measurement identifier of the specified MEP. 8 measurements can be simultaneously activated on the MEP.

Enable/disable the DM function. If the value is disable, the DM test can not be started. Enumeration: 'disabled': 2, 'enabled': 1.

The Maintenance association End Point Identifier of another MEP in the same Maintenance Association to which the DM is to be sent. It will be used if DMM destination MAC address type is unicast.

The DM frame size. Enumeration: 'size512': 4, 'size66': 1, 'size128': 2, 'size1280': 6, 'size1024': 5, 'size1518': 7, 'size256': 3.

The application type of the DM. Enumeration: 'singleEnded': 1, 'dualEnded': 2.

The interval at which DMMs are sent by an MEP. Enumeration: 'interval10s': 2, 'interval1s': 1, 'interval100s': 4, 'interval60s': 3.

The duration of DM test. It can be configured when zxAnCfm2MepDmOperType is onDemand.

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

The operation type of the DM. Enumeration: 'proactive': 2, 'onDemand': 1.

The result of the operation: yes(1): The Delay Measurement Message(s) will be (or has been) sent. no(2): The Delay Measurement Message(s) will not be sent. Enumeration: 'yes': 1, 'no': 2.

This table includes multicast or unicast frame delay measurement result.

The delay measurement result table entry.

Remote MEP identifier, which receives frame delay measurement packets and responses delay measurement reply packets.

The timestamp of the time-of-day in UTC at the scheduled starting time of the measurement interval.

The timestamp of the time-of-day in UTC at the scheduled ending time of the measurement interval.

The elapsed time of the delay measurement interval.

The packets of delay measurement sent.

The packets of delay measurement received.

The count of two-way frame delay measurements.

The average two-way frame delay measurements.

The minimum two-way frame delay measurements.

The maximum two-way frame delay measurements.

The count of inter-frame delay variation measurements in the forward direction.

The average one-way inter-frame delay variation measurements in forward direction.

The maximum one-way inter-frame delay variation measurements in forward direction.

The minimum one-way inter-frame delay variation measurements in forward direction.

The count of inter-frame delay variation measurements in the backward direction.

The average one-way inter-frame delay variation measurements in backward direction.

The maximum one-way inter-frame delay variation measurements in backward direction.

The minimum one-way inter-frame delay variation measurements in backward direction.

The count in the first two-way frame delay measurements range which is [0, zxAnCfm2LMepDmTwoWayFdMsrR1Max).

The count in the second two-way frame delay measurements range which is [zxAnCfm2LMepDmTwoWayFdMsrR1Max, zxAnCfm2LMepDmTwoWayFdMsrR2Max).

The count in the third two-way frame delay measurements range which is [zxAnCfm2LMepDmTwoWayFdMsrR2Max, zxAnCfm2LMepDmTwoWayFdMsrR3Max).

The count in the fourth two-way frame delay measurements range which is [zxAnCfm2LMepDmTwoWayFdMsrR3Max, plus infinity).

The count in the first one-way inter-frame delay variation measurements range which is [0, zxAnCfm2LMepDmOneWayIfdvMsrR1Max) in the forward direction.

The count in the second one-way inter-frame delay variation measurements range which is [zxAnCfm2LMepDmOneWayIfdvMsrR1Max, zxAnCfm2LMepDmOneWayIfdvMsrR2Max) in the forward direction.

The count in the third one-way inter-frame delay variation measurements range which is [zxAnCfm2LMepDmOneWayIfdvMsrR2Max, zxAnCfm2LMepDmOneWayIfdvMsrR3Max) in the forward direction.

The count in the fourth one-way inter-frame delay variation measurements range which is [zxAnCfm2LMepDmOneWayIfdvMsrR3Max, plus infinity) in the forward direction.

The count in the first one-way inter-frame delay variation measurements range which is [0, zxAnCfm2LMepDmOneWayIfdvMsrR1Max) in the backward direction.

The count in the second one-way inter-frame delay variation measurements range which is [zxAnCfm2LMepDmOneWayIfdvMsrR1Max, zxAnCfm2LMepDmOneWayIfdvMsrR2Max) in the backward direction.

The count in the third one-way inter-frame delay variation measurements range which is [zxAnCfm2LMepDmOneWayIfdvMsrR2Max, zxAnCfm2LMepDmOneWayIfdvMsrR3Max) in the backward direction.

The count in the fourth one-way inter-frame delay variation measurements range which is [zxAnCfm2LMepDmOneWayIfdvMsrR3Max, plus infinity) in the backward direction.

The Maintenance Association End Point (MEP) performance measurement operation table stores all the managed objects for sending LMM. Steps to use entries in this table: 1) Wait for zxAnCfm2MepLmEnable value to be disabled. To do this do this sequence: a. an SNMP GET for both snmpSetSerialNo and zxAnCfm2MepLmEnable objects (in same SNMP PDU). b. Check if value for zxAnCfm2MepLmEnable is disabled. - if not, wait x seconds, go to step a above. - if enabled, save the value of snmpSetSerialNo and go to step 2) below 2) Change zxAnCfm2MepLmEnable value from disabled to enabled 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 zxAnCfm2MepLmEnable and other frame loss measurement objects (such as zxAnCfm2MepLmPriority,...) (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) Check the value of zxAnCfm2MepLmResultOk to find out if the operation was successfully initiated or not. 4) Monitor the value of zxAnCfm2MepLmEnable. When it is reset to false, the last LMM has been transmitted. 5) Get the results of the test from zxAnCfm2MepLmRltTable.

The Loss Measurement table entry.

The packet loss measurement identifier of the specified MEP, only one on-demand or one proactive LM can be activated simultaneously on the specified MEP.

Enable/disable the LM function. If the value is disable the LM test can not be started. Enumeration: 'disabled': 2, 'enabled': 1.

The Maintenance association End Point Identifier of another MEP in the same Maintenance Association to which the LM is to be sent. This variable will be used if the LMM destination MAC address type is unicast, if not configured the multicast LM will be sent.

The application type of the LM. Enumeration: 'singleEnded': 1, 'dualEnded': 2.

The interval at which LMMs are sent by an MEP. Enumeration: 'interval10s': 2, 'interval1s': 1, 'interval100s': 4, 'interval60s': 3.

The duration of LM. It can be configured when zxAnCfm2MepLmOperType is onDemand.

The priority. 3 bit value to be used in the VLAN tag, if present in the LM frame.

The operation type of the LM. Enumeration: 'proactive': 2, 'onDemand': 1.

The result of the operation: yes(1): The Loss Measurement Message(s) will be (or has been) sent. no(2): The Loss Measurement Message(s) will not be sent. Enumeration: 'yes': 1, 'no': 2.

This table includes multicast or unicast frame loss measurement result.

The loss measurement result table entry.

Remote MEP identifier, which receives frame loss measurement packets and responses loss measurement reply packets.

The timestamp of the time-of-day in UTC at the scheduled starting time of the measurement interval.

The timestamp of the time-of-day in UTC at the scheduled ending time of the measurement interval.

The elapsed time of the measurement interval.

The number of frame loss measurement packets sent.

The number of frame loss measurement packets received.

The number of frame loss measurement packets sent in forward direction.

The number of frame loss measurement packets received in forward direction.

The frame loss ratio in forward direction of the LM.

The number of frame loss measurement packets sent in backward direction.

The number of frame loss measurement packets received in backward direction.

The frame loss ratio in backward direction of the LM.

The Maintenance Association End Point (MEP) performance measurement operation table stores all the managed objects for sending SLM . Steps to use entries in this table: 1) Wait for zxAnCfm2MepSlmEnable value to be disabled. To do this do this sequence: a. an SNMP GET for both snmpSetSerialNo and zxAnCfm2MepSlmEnable objects (in same SNMP PDU). b. Check if value for zxAnCfm2MepSlmEnable is disabled. - if not, wait x seconds, go to step a above. - if enabled, save the value of snmpSetSerialNo and go to step 2) below 2) Change zxAnCfm2MepSlmEnable value from disabled to enabled 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 zxAnCfm2MepSlmEnable and other synthetic loss measurement objects (such as zxAnCfm2MepSlmPriority, ...) (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) Check the value of zxAnCfm2MepSlmResultOk to find out if the operation was successfully initiated or not. 4) Monitor the value of zxAnCfm2MepSlmEnable. When it is reset to false, the last SLM has been transmitted. 5) Get the results of the test from the zxAnCfm2MepSlmRltTable.

The synthetic loss measurement table entry.

The synthetic frame loss measurement identifier of the specified MEP. 8 measurements can be activated simultaneously on the MEP.

Enable/disable the SLM function. If the value is disable the SLM test can not be started. Enumeration: 'disabled': 2, 'enabled': 1.

The Maintenance Association End Point Identifier of another MEP in the same Maintenance Association to which the SLM is to be sent. This variable will be used if the SLM destination MAC address type is unicast, if 0, the SLM destination MAC address type is multicast.

The application type of the SLM. Enumeration: 'singleEnded': 1, 'dualEnded': 2.

The interval at which SLM is send by an MEP. Unlimited means the test can't stop until the user stops it. Enumeration: 'interval10ms': 1, 'interval100ms': 2, 'unlimited': 255, 'interval1s': 3.

The duration of SLM test.

The priority. 3 bit value to be used in the VLAN tag, if present in the SLM frame.

The packet length of the SLM frame. Enumeration: 'size512': 4, 'size256': 3, 'size64': 1, 'size128': 2, 'size1280': 6, 'size1024': 5, 'size1518': 7.

The operation type of the SLM. Enumeration: 'proactive': 2, 'onDemand': 1.

The result of the operation: yes(1): The Synthetic Loss Measurement Message(s) will be (or has been) sent. no(2): The Synthetic Loss Measurement Message(s) will not be sent. Enumeration: 'yes': 1, 'no': 2.

The synthetic frame loss measurement result table.

The result information of Synthetic Loss Measurement.

Remote MEP identifier, which receives synthetic frame loss measurement packets and responses synthetic frame loss reply packets.

The timestamp of the time-of-day in UTC at the scheduled starting time of the measurement interval.

The timestamp of the time-of-day in UTC at the scheduled ending time of the measurement interval.

The elapsed time of the measurement interval.

The number of synthetic loss measurement packets sent.

The number of synthetic loss measurement packets received.

The number of synthetic loss measurement packets sent in forward direction.

The number of synthetic loss measurement packets received in forward direction.

The packets loss in the latest SLM in forward direction.

The packet loss ratio of the latest SLM in forward direction.

The number of synthetic loss measurement packets sent in backward direction.

The number of synthetic loss measurement packets received in backward direction.

The packets loss of the latest SLM in backward direction.

The packet loss ratio of the latest SLM in backward direction.

The MEP (Maintenance Association End Point) statistics table.

The MEP statistics table entry.

The total number of received CFM packets.

The total number of transmitted CFM packets.

The total number of received out-of-sequence CFM packets.

The total number of received CFM packets that source MAC address is invalid.

The total number of received correct CFM packets.

The total number of received illegal CFM packets.

Clear all the MEP statistics variables. When get this variable, always return 1. Enumeration: 'reset': 1.