Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Managed Objects for jnxSoamPmMepTable

    The jnxSoamPmMepTable, whose object identifier is {jnxSoamPmMep 1}, contains the jnxSoamPmMepEntry that retrieves details related to Ethernet performance monitoring of maintenance endpoints (MEPs). Each jnxSoamPmMepEntry, whose object identifier is {jnxSoamPmMepTable 1}, contains the objects listed in the following table. The jnxSoamPmMepTable is an extension of the dot1agCfmMepTable and rows are automatically added or deleted from this table based upon row creation and deletion of the dot1agCfmMepTable. This table represents the local MEP PM configuration table. The primary purpose of this table is provide local parameters for the SOAM PM function found in [Y.1731] and [MEF SOAM-PM] and instantiated at a MEP.

    Table 1: jnxSoamPmMepTable

    Object

    Object ID

    Description

    jnxSoamPmMepOperNextIndex

    jnxSoamPmMepEntry 1

    Contains an unused value for a PM session number on a MEP that can be used for either LM or DM sessions, or a zero to indicate that none exist. This value needs to be read in order to find an available index for row-creation of a PM session on a MEP and then used when a row is created. This value is automatically updated by the SNMP Agent after the row is created.

    Referential integrity is necessary (the index needs to be persistent upon a reboot or restart of a device). The index is never to be reused for other PM sessions on the same MEP while this session is active, or until it wraps to zero. The index value keeps increasing up to that time. This is to facilitate access control based on a fixed index for an EMS, since the index is not reused.

    This object is an extension of the dot1agCfmMepTable and the object is automatically added or deleted based upon row creation and removal of the dot1agCfmMepTable.

    jnxSoamPmMepLmSingleEndedResponder

    jnxSoamPmMepEntry 2

    Specifies whether the Loss Measurement (LMM) single-ended responder is enabled.

    The value of true indicates the single-ended Loss Measurement Responder is enabled and if an LMM message is received, an LMR will be sent in reply. The value of false indicates the single-ended Loss Measurement Responder is disabled. If an LMM message is received no response will be sent and the message will be discarded.

    This object needs to be persistent upon reboot or restart of a device. A MEP can be both a single-ended Responder and Controller simultaneously.

    jnxSoamPmMepSlmSingleEndedResponder

    jnxSoamPmMepEntry 3

    Specifies whether the Synthetic Loss Measurement (SLM) single-ended Responder is enabled.

    The value of true indicates the single-ended SLM Responder is enabled and if an SLM message is received, an SLR is sent in reply. The value of false indicates the single-ended SLM Responder is disabled. If an SLM message is received, a response is not sent and the message is discarded.

    This object needs to be persistent upon reboot or restart of a device.

    A MEP can be both a single-ended Responder and Controller simultaneously.

    jnxSoamPmMepDmSingleEndedResponder

    jnxSoamPmMibObjects 4

    This object specifies whether the Delay Measurement (DMM) single-ended Responder is enabled.

    The value of true indicates the single-ended Delay Measurement Responder is enabled and if a DMM message is received a DMR is sent in reply. The value of false indicates the single-ended Delay Measurement Responder is disabled. If a DMM message is received, no response is sent and the message is discarded.

    This object needs to be persistent upon reboot or restart of a device. A MEP can be both a single-ended Responder and Controller simultaneously.

    Modified: 2017-09-13