This MIB module contains the management objects for the management of Ethernet Services Operations, Administration and Maintenance for Performance Monitoring.
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
This object contains the time and date at the time that the notification event is detected, not the time of the notification generation.
This object is used only for notifications. The mechanism to set and keep current the date and time is not specified.
jnxSoamPmNotificationObjThresholdId
1.3.6.1.4.1.2636.3.78.1.5.2
OBJECT IDENTIFIER
The Object Identifier of the object that caused the generation of the notification from the jnxSoamLmThresholdEntry or jnxSoamDmThresholdEntry.
This object is only used for the notification.
jnxSoamPmNotificationObjThresholdConfig
1.3.6.1.4.1.2636.3.78.1.5.3
Unsigned32
The configured threshold value of the object that caused the generation of the notification.
This object is only used for the notification.
jnxSoamPmNotificationObjThresholdValue
1.3.6.1.4.1.2636.3.78.1.5.4
Unsigned32
The measured value of the object at the time of the generation of the Notification, from the jnxSoamLmMeasuredStatsTable, jnxSoamLmCurrentStatsTable, jnxSoamDmMeasuredStatsTable or jnxSoamDmCurrentStatsTable.
This object is only used for the notification.
jnxSoamPmNotificationObjSuspect
1.3.6.1.4.1.2636.3.78.1.5.5
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
The suspect flag for the current Measurement Interval in which the notification was generated from the jnxSoamLmCurrentStatsTable, or jnxSoamDmCurrentStatsTable.
This object is only used for the notification.
The Notification Crossing Type of the object that caused the generation of the notification from the jnxSoamLmThresholdEntry or jnxSoamDmThresholdEntry.
aboveAlarm(1) indicates that the crossing type alarm was an above threshold
setAlarm(2) indicates that the crossing type alarm was a set threshold
clearAlarm(3) indicates that the crossing type alarm was a clear threshold
This object is only used for the notification.
jnxSoamPmNotificationObjDestinationMep
1.3.6.1.4.1.2636.3.78.1.5.7
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The MAC address of the Destination MEP associated the notification found in either the jnxSoamDmCfgTable or jnxSoamLmCfgTable.
This object is only used for the notification.
jnxSoamPmNotificationObjPriority
1.3.6.1.4.1.2636.3.78.1.5.8
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The CoS priority of the associated notification found in either the jnxSoamDmCfgTable or jnxSoamLmCfgTable.
This object is only used for the notification.
jnxSoamPmNotificationTotalFlaps
1.3.6.1.4.1.2636.3.78.1.5.9
Unsigned32
The measured value of total number of flaps occured during the flap trap timer itnerval.
jnxSoamPmNotificationAccTotalFlaps
1.3.6.1.4.1.2636.3.78.1.5.10
Unsigned32
The measured value of total number of accumulated flaps occured during the flap trap timer itnerval.
jnxSoamPmNotificationObjThresholdLastValue
1.3.6.1.4.1.2636.3.78.1.5.11
Unsigned32
The measured value of the object at the time of the generation of the last Notification during the flap trap timer interval.
This object is only used for the notification.
The Current Notification Crossing Type of the object that caused the generation of the notification at the end of timer interval from the jnxSoamLmThresholdEntry or jnxSoamDmThresholdEntry.
aboveAlarm(1) indicates that the crossing type alarm was an above threshold
setAlarm(2) indicates that the crossing type alarm was a set threshold
clearAlarm(3) indicates that the crossing type alarm was a clear threshold
This object is only used for the notification.
jnxSoamPmNotificationObjLastDateAndTime
1.3.6.1.4.1.2636.3.78.1.5.13
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
This object contains the time and date at the time that the last notification event is detected, at the end of flap timer interval and not the time of the first notification generation.
This object is used only for notifications. The mechanism to set and keep current the date and time is not specified.
This table is an extension of the dot1agCfmMepTable and rows are automatically added or deleted from this table based upon row creation and destruction 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.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamPmMepOperNextIndex
1.3.6.1.4.1.2636.3.78.1.1.1.1.1
Dot1afCfmIndexIntegerNextFreeAn integer that may be used as a new Index in a table.
The special value of 0 indicates that no more new entries can be created in the relevant table.
When a MIB is used for configuration, an object with this SYNTAX always contains a legal value (if non-zero) for an index that is not currently used in the relevant table. The Command Generator (Network Management Application) reads this variable and uses the (non-zero) value read when creating a new row with an SNMP SET. When the SET is performed, the Command Responder (agent) MUST determine whether the value is indeed still unused; Two Network Management Applications may attempt to create a row (configuration entry) simultaneously and use the same value. If it is currently unused, the SET succeeds and the Command Responder (agent) changes the value of this object, according to an implementation-specific algorithm. If the value is in use, however, the SET fails. The Network Management Application MUST then re-read this variable to obtain a new usable value.
An OBJECT-TYPE definition using this SYNTAX MUST specify the relevant table for which the object is providing this functionality. · Unsigned32 · hint d
This object 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, i.e., 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 destruction of the dot1agCfmMepTable.
jnxSoamPmMepLmSingleEndedResponder
1.3.6.1.4.1.2636.3.78.1.1.1.1.2
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object specifies whether the Loss Measurement (LMM) single-ended Responder is enabled.
The value 'true' indicates the single-ended Loss Measurement Responder is enabled and if a LMM message is received a LMR will be sent in reply.
The value 'false' indicates the single-ended Loss Measurement Responder is disabled. If a 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
1.3.6.1.4.1.2636.3.78.1.1.1.1.3
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object specifies whether the Synthetic Loss Measurement (SLM) single-ended Responder is enabled. The value 'true' indicates the single-ended SLM Responder is enabled and if a SLM message is received a SLR will be sent in reply. The value 'false' indicates the single-ended SLM Responder is disabled. If a SLM 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.
jnxSoamPmMepDmSingleEndedResponder
1.3.6.1.4.1.2636.3.78.1.1.1.1.4
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object specifies whether the Delay Measurement (DMM) single ended Responder is enabled. The value 'true' indicates the single-ended Delay Measurement Responder is enabled and if a DMM message is received a DMR will be sent in reply. The value 'false' indicates the single-ended Delay Measurement Responder is disabled. If a DMM 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.
This table includes configuration objects and operations for the Frame Loss Measurement function defined in [Y.1731] and [MEF SOAM-PM].
Each row in the table represents a Loss Measurement session for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific LM session on the selected MEP. A Loss Measurement session is created on an existing MEP by first accessing the jnxSoamPmMepOperNextIndex object and using this value as the jnxSoamLmCfgIndex in the row creation.
Some writable objects in this table are only applicable in certain cases (as described under each object), and attempts to write values for them in other cases will be ignored.
The writable objects in this table need to be persistent upon reboot or restart of a device.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamLmCfgIndex
1.3.6.1.4.1.2636.3.78.1.2.1.1.1
Unsigned32 (1..4294967295)
An index to the Loss Measurement Configuration table which indicates the specific measurement session for the MEP.
jnxSoamPmMepOperNextIndex needs to be inspected to find an available index for row-creation.
Referential integrity is necessary, i.e., the index needs to be persistent upon a reboot or restart of a device. The index is never reused for other PM sessions on the same MEP while this session is active. The index value keeps increasing until it wraps to 0. This is to facilitate access control based on a fixed index for an EMS, since the index is not reused.
This object specifies what type of Loss Measurement will be performed.
lmLmm(1) LMM SOAM PDU generated and received LMR responses tracked lmSlm(2) SLM SOAM PDU generated and received SLR responses tracked lmCcm(3) CCM SOAM PDU generated and received CCM PDUs tracked
The lmSlm value is required. The lmLmm and lmCcm values are optional.
The lmCcm loss measurement values are only valid for a point-to-point MEG. Multipoint MEGs may give unreliable loss measurements.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgVersion
1.3.6.1.4.1.2636.3.78.1.2.1.1.3
Unsigned32
Reference: [Y.1731]
This object indicates the version of the PDUs used to perform Loss Measurement.
The value is placed in the Version field of the PDU and indicates that the PDU format used is the format defined in Y.1731 with that version.
The exact PDUs to use are specified by this object in combination with jnxSoamLmCfgType.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgEnabled
1.3.6.1.4.1.2636.3.78.1.2.1.1.4
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: [MEF SOAM-PM] R4, R5, R6, O1, R12, R14
This object specifies whether the Loss Measurement session is enabled.
The value 'true' indicates the Loss Measurement session is enabled and SOAM PDUs are sent and/or measurements are collected when the session is running according to the scheduling objects (start time, stop time, etc.).
The value 'false' indicates the Loss Measurement session is disabled and SOAM PDUs are not sent and/or measurements collected.
For a Loss Measurement session to be removed the row is deleted in order to release internal resources.
This object can written/modified after row creation time.
If the LM session is enabled it resumes after shutdown/restart.
If the LM session is disabled the current Measurement Interval is stopped, if it in process at the time, and all the in process calculations for the partially completed Measurement Interval are finalized.
This object does not affect whether the single-ended Responder is enabled or not, which is enabled or disabled by the jnxSoamPmMepLmSingleEndedResponder and jnxSoamPmMepSlmSingleEndedResponder objects.
jnxSoamLmCfgMeasurementEnable
1.3.6.1.4.1.2636.3.78.1.2.1.1.5
BITS
Reference: [Y.1731]
A vector of bits that indicates the type of SOAM LM counters found in the jnxSoamLmMeasuredStatsTable, jnxSoamLmCurrentStatsTable, jnxSoamLmHistoryStatsTable that are enabled. that are enabled.
A bit set to '1' enables the specific SOAM LM counter. A bit set to '0' disables the SOAM LM counter.
If a particular SOAM LM counter is not supported the BIT value is set to '0'.
Not all SOAM LM counters are supported for all SOAM LM types.
This object can only be written at row creation time and cannot be modified once it has been created.
bForwardTransmitedFrames (0) Enables/disables the jnxSoamLmCurrentStatsForwardTransmittedFrames and jnxSoamLmHistoryStatsForwardTransmittedFrames counters. bForwardReceivedFrames(1) Enables/disables the jnxSoamLmCurrentStatsForwardReceivedFrames and jnxSoamLmHistoryStatsForwardReceivedFrames counters. bForwardMinFlr(2) Enables/disables the jnxSoamLmCurrentStatsForwardMinFlr and jnxSoamLmHistoryStatsForwardMinFlr counters. bForwardMaxFlr(3) Enables/disables the jnxSoamLmCurrentStatsForwardMaxFlr and jnxSoamLmHistoryStatsForwardMaxFlr counters. bForwardAvgFlr(4) Enables/disables the jnxSoamLmCurrentStatsForwardAvgFlr and jnxSoamLmHistoryStatsForwardAvgFlr counters. bBackwardTransmitedFrames(5) Enables/disables the jnxSoamLmCurrentStatsBackwardTransmittedFrames and jnxSoamLmHistoryStatsBackwardTransmittedFrames counters. bBackwardReceivedFrames(6) Enables/disables the jnxSoamLmCurrentStatsBackwardReceivedFrames and jnxSoamLmHistoryStatsBackwardReceivedFrames counters. bBackwardMinFlr(7) Enables/disables the jnxSoamLmCurrentStatsBackwardMinFlr and jnxSoamLmHistoryStatsBackwardMinFlr counters. bBackwardMaxFlr(8) Enables/disables the jnxSoamLmCurrentStatsBackwardMaxFlr and jnxSoamLmHistoryStatsBackwardMaxFlr counters. bBackwardAvgFlr(9) Enables/disables the jnxSoamLmCurrentStatsBackwardAvgFlr and jnxSoamLmHistoryStatsBackwardAvgFlr counters. bSoamPdusSent (10) Enables/disables the jnxSoamLmCurrentStatsSoamPdusSent and jnxSoamLmHistoryStatsSoamPdusSent counters. bSoamPdusReceivedbReceivedMeasurements (11) Enables/disables the jnxSoamLmCurrentStatsSoamPdusReceived and jnxSoamLmHistoryStatsSoamPdusReceived counters. bAvailForwardHighLoss(12) Enables/disables the jnxSoamLmCurrentAvailStatsForwardHighLoss and jnxSoamLmHistoryAvailStatsForwardHighLoss counters. bAvailForwardConsecutiveHighLoss(13) Enables/disables the jnxSoamLmCurrentAvailStatsForwardConsecutiveHighLoss and jnxSoamLmHistoryAvailStatsForwardConsecutiveHighLoss counters. bAvailForwardAvailable(14) Enables/disables the jnxSoamLmCurrentAvailStatsForwardAvailable and jnxSoamLmHistoryAvailStatsForwardAvailable counters. bAvailForwardUnavailable(15) Enables/disables the jnxSoamLmCurrentAvailStatsForwardUnavailable and jnxSoamLmHistoryAvailStatsForwardUnavailable counters. bAvailForwardMinFlr(16) Enables/disables the jnxSoamLmCurrentAvailStatsForwardMinFlr and jnxSoamLmHistoryAvailStatsForwardMinFlr counters. bAvailForwardMaxFlr(17) Enables/disables the jnxSoamLmCurrentAvailStatsForwardMaxFlr and jnxSoamLmHistoryAvailStatsForwardMaxFlr counters. bAvailForwardAvgFlr(18) Enables/disables the jnxSoamLmCurrentAvailStatsForwardAvgFlr and jnxSoamLmHistoryAvailStatsForwardAvgFlr counters. bAvailBackwardHighLoss(19) Enables/disables the jnxSoamLmCurrentAvailStatsBackwardHighLoss and jnxSoamLmHistoryAvailStatsBackwardHighLoss counters. bAvailBackwardConsecutiveHighLoss(20) Enables/disables the jnxSoamLmCurrentAvailStatsBackwardConsecutiveHighLoss and jnxSoamLmHistoryAvailStatsBackwardConsecutiveHighLoss counters. bAvailBackwardAvailable(21) Enables/disables the jnxSoamLmCurrentAvailStatsBackwardAvailable and jnxSoamLmHistoryAvailStatsBackwardAvailable counters. bAvailBackwardUnavailable(22) Enables/disables the jnxSoamLmCurrentAvailStatsBackwardUnavailable and jnxSoamLmHistoryAvailStatsBackwardUnavailable counters. bAvailBackwardMinFlr(23) Enables/disables the jnxSoamLmCurrentAvailStatsBackwardMinFlr and jnxSoamLmHistoryAvailStatsBackwardMinFlr counters. bAvailBackwardMaxFlr(24) Enables/disables the jnxSoamLmCurrentAvailStatsBackwardMaxFlr and jnxSoamLmHistoryAvailStatsBackwardMaxFlr counters. bAvailBackwardAvgFlr(25) Enables/disables the jnxSoamLmCurrentAvailStatsBackwardAvgFlr and jnxSoamLmHistoryAvailStatsBackwardAvgFlr counters. Enables/disables the jnxSoamLmCurrentStatsSoamPdusReceived and jnxSoamLmHistoryStatsSoamPdusReceived counters. bMeasuredStatsForwardMeasuredFlr(26) Enables/disables the jnxSoamLmMeasuredStatsForwardFlr counter. bMeasuredStatsBackwardMeasuredFlr(27) Enables/disables the jnxSoamLmMeasuredStatsBackwardFlr counter. bMeasuredStatsAvailForwardStatus(28) Enables/disables the jnxSoamLmMeasuredStatsAvailForwardStatus counter. bMeasuredStatsAvailBackwardStatus(29) Enables/disables the jnxSoamLmMeasuredStatsAvailBackwardStatus counter.
jnxSoamLmCfgMessagePeriod
1.3.6.1.4.1.2636.3.78.1.2.1.1.6
Integer32 · ms
Reference: [MEF SOAM-PM] R76, R77, D29, D30
This object specifies the interval between Loss Measurement OAM message transmission. For Loss Measurement monitoring applications the default value is 1 sec.
This object is not applicable if jnxSoamLmCfgType is set to lmCcm and is ignored for that Loss Measurement Type.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgPriority
1.3.6.1.4.1.2636.3.78.1.2.1.1.7
IEEE8021PriorityValueAn IEEE 802.1Q user priority value.Reference: 12.13.3.3 (0..7) · Unsigned32 · hint d
This object specifies the Loss Measurement OAM message priority as well as the priority of the service/OAM traffic to be monitored. Only frames of the same Class of Service are counted.
The default value is to be the value which yields the lowest frame loss.
This object is not applicable if jnxSoamLmCfgType is set to lmCcm.
This object can only be written at row creation time and cannot be modified once it has been created.
This object specifies the Loss Measurement frame size between 64 bytes and the maximum transmission unit of the EVC.
The range of frame sizes from 64 through 2000 octets need to be supported, and the range of frame sizes from 2001 through 9600 octets is suggested be supported.
The adjustment to the frame size of the standard frame size is accomplished by the addition of a Data or Test TLV. A Data or Test TLV is only added to the frame if the frame size is greater than 64 bytes.
This object is only valid for the entity transmitting the Loss Measurement frames, type 'lmSlm', and is ignored by the entity receiving frames. It is not applicable for the 'lmCcm' or 'lmLmm' types.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgDataPattern
1.3.6.1.4.1.2636.3.78.1.2.1.1.9
JnxSoamTcDataPatternType1 = zeroPattern2 = onesPatternThis enumeration data type indicates the type of data pattern to be sent in an OAM PDU Data TLV. The valid enumerated values associated with this type are: zeroPattern(1) indicates the Data TLV contains all zeros onesPattern(2) indicates the Data TLV contains all ones · Integer32
This object specifies the LM data pattern included in a Data TLV when the size of the LM frame is determined by the jnxSoamLmFrameSize object and jnxoamLmTestTlvIncluded is 'false'.
If the frame size object does not define the LM frame size or jnxSoamLmTestTlvIncluded is 'true' the value of this object is ignored.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgTestTlvIncluded
1.3.6.1.4.1.2636.3.78.1.2.1.1.10
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: [Y.1731] 9.3
Indicates whether a Test TLV or Data TLV is included when the size of the LM frame is determined by the jnxSoamLmFrameSize object.
A value of 'true' indicates that the Test TLV is to be included. A value of 'false' indicates that the Data TLV is to be included.
If the frame size object does not define the LM frame size the value of this object is ignored.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgTestTlvPattern
1.3.6.1.4.1.2636.3.78.1.2.1.1.11
JnxSoamTcTestPatternType1 = null2 = nullCrc323 = prbs4 = prbsCrc32This enumeration data type indicates the type of test pattern to be sent in an OAM PDU Test TLV. The valid enumerated values associated with this type are: null(1) Null signal without CRC-32 nullCrc32(2) Null signal with CRC-32 prbs(3) PRBS 2^31-1 without CRC-32 prbsCrc32(4) PRBS 2^31-1 with CRC-32Reference: [MEF7.1], Appendix III.2 Enumeration, [Y.1731] 7.7 · Integer32
This object specifies the type of test pattern to be sent in the LM frame Test TLV when the size of LM PDU is determined by the jnxSoamLmFrameSize object and jnxSoamLmTestTlvIncluded is 'true'. If the frame size object does not define the LM frame size or jnxSoamLmTestTlvIncluded is 'false' the value of this object is ignored.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgNumIntervalsStored
1.3.6.1.4.1.2636.3.78.1.2.1.1.12
Unsigned32 (1..1000)
Reference: [MEF SOAM-PM] R21, D8, D9
This object specifies the number of completed Measurement Intervals to store in the history statistic table (jnxSoamLmHistoryStatsTable)
At least 32 completed Measurement Intervals need to be stored. 96 Measurement Intervals are recommended to be stored.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgDestMepId
1.3.6.1.4.1.2636.3.78.1.2.1.1.13
Dot1agCfmMepIdOrZeroMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.
The special value 0 is allowed to indicate special cases, for example that no MEPID is configured.
Whenever an object is defined with this SYNTAX, then the DESCRIPTION clause of such an object MUST specify what the special value of 0 means.Reference: 19.2.1 (0 | 1..8191) · Unsigned32 · hint d
Reference: [MEF SOAM-PM] R70, R104
The Maintenance Association End Point Identifier of another MEP in the same Maintenance Association to which the SOAM LM frame is to be sent.
This address will be used if the value of the column jnxSoamLmDestIsMepId is 'true'. A value of zero means that the destination MEP ID has not been configured.
This object is only valid for the entity transmitting the Loss Measurement frames, types 'lmLmm' and 'lmSlm'. It is not applicable for the 'lmCcm' type.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgDestIsMepId
1.3.6.1.4.1.2636.3.78.1.2.1.1.14
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: [MEF SOAM-PM] R70, R104
A value of 'true' indicates that MEPID of the target MEP is used for SOAM LM frame transmission.
A value of 'false' indicates that the MAC address of the target MEP is used for SOAM LM frame transmission.
This object is only valid for the entity transmitting the Loss Measurement frames, types 'lmLmm' and 'lmSlm'. It is not applicable for the 'lmCcm' type.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgStartTimeType
1.3.6.1.4.1.2636.3.78.1.2.1.1.15
JnxSoamTcOperationTimeType1 = none2 = immediate3 = relative4 = fixedThis enumeration data type indicates the operation type start or end time to indicate when an OAM operation is initiated or stopped. The valid enumerated values associated with this type are: none(1) The operation is never started or is stopped immediately if used to indicate a start time, or the operation never ends if it is used to indicate an end time immediate(2) The operation is to begin immediately relative(3) The operation is to begin at a relative time from the current time or stop a relative time after it has started fixed(4) The operation is to begin/stop at the given UTC time/dateReference: [SOAM-PM] R2, [SOAM-FM] 8.7 · Integer32
Reference: [MEF SOAM-PM] R3, R7, R8, D1
This object specifies the type of start time of the SOAM LM session. The start time can be disabled (none), immediate, relative, or fixed.
The value of 'none' is illegal and a write error will be returned if this value is used.
The value of 'immediate' starts the SOAM LM session when the jnxSoamLmCfgEnabled is true.
The value of 'fixed' starts the SOAM LM session when the jnxSoamLmFixedStartDateAndTime is less than or equal to the current system date and time and jnxSoamLmCfgEnabled is true. This value is used to implement an On-Demand fixed time PM session.
The value of 'relative' starts the SOAM LM session when the current system date and time minus the jnxSoamLmRelativeStartTime is greater than or equal to the system date and time when the jnxSoamLmStartTimeType object was written and jnxSoamLmCfgEnabled is true. This value is used to implement an On-Demand relative time PM session.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgFixedStartDateAndTime
1.3.6.1.4.1.2636.3.78.1.2.1.1.16
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Reference: [MEF SOAM-PM] R9
This object specifies the fixed start date/time for the SOAM Loss Measurement session. This object is used only used if jnxSoamLmStartTimeType is 'fixed' and is ignored otherwise.
The default value is year 0000, month 01, day 01, time 00:00:00.00.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgRelativeStartTime
1.3.6.1.4.1.2636.3.78.1.2.1.1.17
TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32
Reference: [MEF SOAM-PM] R9
This object specifies the relative start time, from the current system time, for the SOAM LM session. This object is used only if jnxSoamLmStartTimeType is 'relative' and is ignored otherwise.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgRepetitionTime
1.3.6.1.4.1.2636.3.78.1.2.1.1.18
Unsigned32 (0..31536000) · seconds
Reference: [MEF SOAM-PM] R18, D3, R19, R20
This object specifies a configurable repetition time between Measurement Intervals in a Loss Measurement session, in seconds.
If the value is 0 (none), there is no time gap between the end of one Measurement Interval and the start of a new Measurement Interval. This is the normal usage case.
If the value is greater than 0 but less than or equal to the measurement interval, an error is returned.
If the value is greater than one Measurement Interval there is time gap between the end of one Measurement Interval and the start of the next Measurement Interval. The repetition time specifies the time between the start of consecutive Measurement Intervals; hence the gap between the end of one Measurement Interval and the start of the next is equal to the difference between the repetition time and the measurement interval. During this gap, no SOAM PDUs are sent for this session and no measurements are made.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgAlignMeasurementIntervals
1.3.6.1.4.1.2636.3.78.1.2.1.1.19
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: [MEF SOAM-PM] D4, D5, D6
This object specifies whether the Measurement Intervals for the Loss Measurement session are aligned with a zero offset to real time.
The value 'true' indicates that each Measurement Interval starts at a time which is aligned to NE time source hour, if the repetition time (or the Measurement Interval, if the repetition time is 0) is a factor of an hour, i.e. 60min/15min = 4. For instance, a Measurement Interval/repetition time of 15 minutes would stop/start the Measurement Interval at 0, 15, 30, and 45 minutes of an hour. A Measurement Interval/Repetition Time of 7 minutes would not align to the hour since 7 minutes is NOT a factor of an hour, i.e. 60min/7min = 8.6. In this case the behavior is the same as if the object is set to 'false'.
The value 'false' indicates that the first Measurement Interval starts at an arbitrary time and each subsequent Measurement Interval starts at a time which is determined by jnxSoamLmCfgRepetitionTime.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgAlignMeasurementOffset
1.3.6.1.4.1.2636.3.78.1.2.1.1.20
Unsigned32 (0..525600) · minutes
Reference: [MEF SOAM-PM] D7
This object specifies the offset in minutes from the time of day value if jnxSoamLmCfgAlignMeasurementIntervals is 'true' and the repetition time is a factor of 60 minutes. If not, the value of this object is ignored.
If the Measurement Interval is 15 minutes and jnxSoamLmCfgAlignMeasurementIntervals is true and if this object was set to 5 minutes, the Measurement Intervals would start at 5, 20, 35, 50 minutes past each hour.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgSessionType
1.3.6.1.4.1.2636.3.78.1.2.1.1.21
OCTET STRING SIZE (1..42)
Reference: [MEF SOAM-PM] R3
This object indicates whether the current session is defined to be 'Proactive' or 'On-Demand'. A value of 'proactive' indicates the current session is 'Proactive'. A value of 'onDemand' indicates the current session is 'On-Demand'.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgSessionStatus
1.3.6.1.4.1.2636.3.78.1.2.1.1.22
OCTET STRING SIZE (1..44)
This object indicates the current status of the LM session. A value of 'active' indicates the current LM session is active, i.e. the current time lies between the start time and the stop time, and
jnxSoamLmCfgEnabled is true. A value of 'notActive' indicates the
current LM session is not active, i.e. it has not started yet, has stopped upon reaching the stop time, or is disabled.
jnxSoamLmCfgHistoryClear
1.3.6.1.4.1.2636.3.78.1.2.1.1.23
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object when written clears the Loss Measurement history Table (jnxSoamLmHistoryStatsTable) - all rows are deleted. When read the value always returns 'false'.
Writing this value does not change the current stat table, nor any of the items in the configuration table. Writing this value during row creation has no effect.
jnxSoamLmCfgRowStatus
1.3.6.1.4.1.2636.3.78.1.2.1.1.24
RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].)
The status column has six defined values:
- `active', which indicates that the conceptual row is available for use by the managed device;
- `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device;
- `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated);
- `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device;
- `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row.
Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management
protocol retrieval operation: `notReady', `notInService' or
`active'. That is, when queried, an existing conceptual row
has only three states: it is either available for use by
the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady').
NOTE WELL
This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'.
Also note that whenever any elements of a row exist, the RowStatus column must also exist.
To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram:
STATE +--------------+-----------+-------------+-------------
| A | B | C | D
| |status col.|status column|
|status column | is | is |status column
ACTION |does not exist| notReady | notInService| is active
--------------+--------------+-----------+-------------+-------------
set status |noError ->D|inconsist- |inconsistent-|inconsistent-
column to | or | entValue| Value| Value
createAndGo |inconsistent- | | |
| Value| | |
--------------+--------------+-----------+-------------+-------------
set status |noError see 1|inconsist- |inconsistent-|inconsistent-
column to | or | entValue| Value| Value
createAndWait |wrongValue | | |
--------------+--------------+-----------+-------------+-------------
set status |inconsistent- |inconsist- |noError |noError
column to | Value| entValue| |
active | | | |
| | or | |
| | | |
| |see 2 ->D|see 8 ->D| ->D
--------------+--------------+-----------+-------------+-------------
set status |inconsistent- |inconsist- |noError |noError ->C
column to | Value| entValue| |
notInService | | | |
| | or | | or
| | | |
| |see 3 ->C| ->C|see 6
--------------+--------------+-----------+-------------+-------------
set status |noError |noError |noError |noError ->A
column to | | | | or
destroy | ->A| ->A| ->A|see 7
--------------+--------------+-----------+-------------+-------------
set any other |see 4 |noError |noError |see 5
column to some| | | |
value | | see 1| ->C| ->D
--------------+--------------+-----------+-------------+-------------
(1) goto B or C, depending on information available to the agent.
(2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D.
(3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C.
(4) at the discretion of the agent, the return value may be either:
inconsistentName: because the agent does not choose to
create such an instance when the corresponding RowStatus instance does not exist, or
inconsistentValue: if the supplied value is
inconsistent with the state of some other MIB object's value, or
noError: because the agent chooses to create the instance.
If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A.
(5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned.
(6) the return value can indicate one of the following errors:
wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or
inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated.
(7) the return value can indicate the following error:
inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated.
(8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue.
NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc.
Conceptual Row Creation
There are four potential interactions when creating a
conceptual row: selecting an instance-identifier which is
not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device.
Interaction 1: Selecting an Instance-Identifier
The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics.
In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.)
Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different.
Finally, the management station could select a pseudo-random number to use as the index. In the event that this index
was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation.
A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used.
Interaction 2: Creating the Conceptual Row
Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions.
Interaction 2a: Creating and Activating the Conceptual Row
The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes:
- a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1.
- the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created.
- the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column.
Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'.
When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information
available to the agent is provided by two sources: the
management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row.
NOTE WELL
Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm.
Interaction 2b: Negotiating the Creation of the Conceptual Row
The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the
columns indicated by its column requirements.) Otherwise,
the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3.
Interaction 3: Initializing non-defaulted Objects
The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes:
- a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column.
- the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column.
- the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column.
If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4.
Interaction 4: Making the Conceptual Row Available
Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'.
NOTE WELL
A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device.
If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row.
Conceptual Row Suspension
When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified).
Conceptual Row Deletion
For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady',
`notInService' or `active'.) If the operation succeeds,
then all instances associated with the conceptual row are immediately removed. · Integer32
The status of the row.
The writable columns in a row cannot be changed if the row is active, except for jnxSoamLmCfgHistoryClear and jnxSoamLmCfgEnabled objects. All columns must have a valid value before a row can be activated.
This object specifies the Measurement Interval for FLR statistics, in minutes. A Measurement Interval of 15 minutes needs to be supported, other intervals may be supported.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgDestMacAddress
1.3.6.1.4.1.2636.3.78.1.2.1.1.26
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
Reference: [MEF SOAM-PM] R70, R104
The Target or Destination MAC Address Field to be transmitted.
If jnxSoamLmCfgType is 'lmCcm', the destination MAC address is always a multicast address indicating the level of the MEG: 01-80-c2-00-00-3y, where y is the level of the MEG. An error is returned if this object is set to any other value.
If jnxSoamLmCfgType is 'lmLmm' or 'lmSlm', the destination address is the unicast address of the destination MEP. An error is returned if this object is set to a multicast address.
This address will be used if the value of the object mefSoamLmDestIsMepId is 'false'.
This object is only valid for the entity transmitting the SOAM LM frames and is ignored by the entity receiving SOAM LM frames.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgStopTimeType
1.3.6.1.4.1.2636.3.78.1.2.1.1.27
JnxSoamTcOperationTimeType1 = none2 = immediate3 = relative4 = fixedThis enumeration data type indicates the operation type start or end time to indicate when an OAM operation is initiated or stopped. The valid enumerated values associated with this type are: none(1) The operation is never started or is stopped immediately if used to indicate a start time, or the operation never ends if it is used to indicate an end time immediate(2) The operation is to begin immediately relative(3) The operation is to begin at a relative time from the current time or stop a relative time after it has started fixed(4) The operation is to begin/stop at the given UTC time/dateReference: [SOAM-PM] R2, [SOAM-FM] 8.7 · Integer32
Reference: [MEF SOAM-PM] R3, R10, D2
This object specifies the type of stop time to terminate the SOAM LM session. The stop time can be forever (none), relative, or fixed.
The value of 'none' indicates that the SOAM LM session never ends once it has started unless it the session is disabled.
The value of 'immediate' is illegal and a write error will be returned if this value is used.
The value of 'fixed' stops the SOAM LM session when the jnxSoamLmFixedStopDateAndTime is less than or equal to the current system date and time. This value is used to implement an On-Demand fixed time PM session.
The value of 'relative' stops the SOAM LM session when the time indicated by jnxSoamLmRelativeStopTime has passed since the session start time as determined by the jnxSoamLmCfgStartTimeType, jnxSoamLmCfgFixedStartDateAndTime and jnxSoamLmCfgRelativeStartTime objects. This value is used to implement an On-Demand relative time PM session.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgFixedStopDateAndTime
1.3.6.1.4.1.2636.3.78.1.2.1.1.28
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Reference: [MEF SOAM-PM] R10, R13
This object specifies the fixed stop date/time for the SOAM Loss Measurement session. This object is used only used if jnxSoamLmStopTimeType is 'fixed' and is ignored otherwise.
The default value is year 0000, month 01, day 01, time 00:00:00.00.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamLmCfgRelativeStopTime
1.3.6.1.4.1.2636.3.78.1.2.1.1.29
TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32
Reference: [MEF SOAM-PM] R11
This object specifies the relative stop time, from the session start time, to stop the SOAM LM session. This object is used only if jnxSoamLmStopTimeType is 'relative' and is ignored otherwise. object can only be written at row creation time 1922 and cannot be modified once it has been created.
jnxSoamLmCfgAvailabilityMeasurementInterval
1.3.6.1.4.1.2636.3.78.1.2.1.1.30
Unsigned32 (1..525600) · minutes
Reference: [MEF SOAM-PM] R16, R17
This object specifies the availability Measurement Interval in minutes. A Measurement Interval of 15 minutes is to be supported, other intervals can be supported. This object can only be written at row creation time and cannot be modified once it has been created.
This object specifies a configurable number of consecutive loss measurement PDUs to be used in evaluating the availability/unavailability status of each availability indicator per MEF 10.2.1. Loss Measurement PDUs (LMMs, CCMs or SLMs) are sent regularly with a period defined by jnxSoamLmCfgMessagePeriod. Therefore, this object, when multiplied by mefSoamLmCfgMessagePeriod, 2050 is equivalent to is equivalent to the Availability parameter of 'delta_t' as specified by MEF 10.2.1.
If the jnxSoamLmCfgType is lmLMM or lmCCM, this object defines the number of LMM or CCM PDUs transmitted during each 'delta_t' period. The Availability flr for a given 'delta_t' can be calculated based on the counters in the last LMM/R or CCM during this 'delta_t' and the last LMM/R or CCM in the previous 'delta_t'.
If the jnxSoamLmCfgType is lmSLM, this object defines the number of SLM PDUs transmitted during each 'delta_t' period. The Availability flr for a given 'delta_t' is calculated based on the number of those SLM PDUs that are lost.
If the jnxSoamLmCfgType is lmLMM or lmCCM, the number range of 1 through 10 must be supported. The number range of 10 through 1000000 may be supported, but is not mandatory.
If the jnxSoamLmCfgType is lmSLM, the number range of 10 through 100 must be supported. The number range of 100 through 1000000 may be supported, but is not mandatory.
This object can only be written at row creation time and cannot be modified once it has been created.
This object specifies a configurable availability threshold to be used in evaluating the availability/unavailability status of an availability indicator per MEF 10.2.1. The availability threshold range of 0.00 (0) through 1.00 (100000) is supported. This parameter is equivalent to the Availability parameter of 'C' as specified by MEF 10.2.1.
Units are in milli-percent, where 1 indicates 0.001 percent.
This object can only be written at row creation time and cannot be modified once it has been created.
This object specifies a configurable number of consecutive availability indicators to be used to determine a change in the availability status as indicated by MEF 10.2.1. This parameter is equivalent to the Availability parameter of 'n' as specified by MEF 10.2.1. The number range of 1 through 10 must be supported. The number range of 1 through 1000 may be supported, but is not mandatory.
This object can only be written at row creation time and cannot be modified once it has been created.
This object specifies a configurable number of consecutive availability indicators to be used for assessing CHLI. This parameter is equivalent to the Resilency parameter of 'p' as specified by MEF 10.2.1.
jnxSoamLmCfgAvailabilityNumConsecutiveHighFlr must be strictly less than jnxSoamLmCfgAvailabilityNumConsecutiveIntervals. If not, the count of high loss intervals over time, jnxSoamLmAvailabilityHighLoss, and the
count of consecutive high loss levels,
jnxSoamLmAvailabilityConsecutiveHighLoss, is disabled.
The number range of 1 through 10 must be supported. The number range of 1 through 1000 may be supported, but is not mandatory.
This object can only be written at row creation time and cannot be modified once it has been created.
This object contains the last measured results for a SOAM Loss Measurement session.
Each row in the table represents a Loss Measurement session for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific LM session on the selected MEP.
Instances of this managed object are created automatically by the SNMP Agent when the Loss Measurement session is running.
Each object in this table applies only if the corresponding bit is set in jnxSoamLmCfgMeasurementEnable.
The objects in this table do not need to be persistent upon reboot or restart of a device.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamLmMeasuredStatsForwardFlr
1.3.6.1.4.1.2636.3.78.1.2.2.1.1
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the last frame loss ratio in the forward direction calculated by this MEP. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmMeasuredStatsBackwardFlr
1.3.6.1.4.1.2636.3.78.1.2.2.1.2
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the last frame loss ratio in the backward direction calculated by this MEP. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmMeasuredStatsAvailForwardStatus
1.3.6.1.4.1.2636.3.78.1.2.2.1.3
JnxSoamTcAvailabilityType1 = available2 = unavailable3 = unknownThis enumeration data type defines the availability of a session, measured by a loss measurement session. The valid enumerated values associated with this type are:
available(1) indicates the MEP is available.
unavailable(2) indicates the MEP is unavailable.
unknown(3) indicates the availability is not known, for
instance because insufficient time has passed to make an availability calculation, the time has been excluded because of a maintenance interval, or because availability measurement is not enabled. · Integer32
Reference: [MEF SOAM-PM] R83
This object indicates the availability status (the outcome of the last known availability indicator) in the forward direction. Note that the status of an availability indicator is not known until the loss for a number of subsequent availability indicators has been calculated (as determined by jnxSoamLmCfgAvailabilityNumConsecutiveIntervals)
jnxSoamLmMeasuredStatsAvailBackwardStatus
1.3.6.1.4.1.2636.3.78.1.2.2.1.4
JnxSoamTcAvailabilityType1 = available2 = unavailable3 = unknownThis enumeration data type defines the availability of a session, measured by a loss measurement session. The valid enumerated values associated with this type are:
available(1) indicates the MEP is available.
unavailable(2) indicates the MEP is unavailable.
unknown(3) indicates the availability is not known, for
instance because insufficient time has passed to make an availability calculation, the time has been excluded because of a maintenance interval, or because availability measurement is not enabled. · Integer32
Reference: [MEF SOAM-PM] R83
This object indicates the availability status (the outcome of the last availability indicator) in the backward direction. Note that the status of an availability indicator is not known until the loss for a number of subsequent availability indicators has been calculated (as determined by jnxSoamLmCfgAvailabilityNumConsecutiveIntervals)
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Reference: [MEF SOAM-PM] R83
This object indicates the time of the last transition between available and unavailable in the forward direction.
If there have been no transitions since the Loss Measurement Session was started, this is set to 0.
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Reference: [MEF SOAM-PM] R83
This object indicates the time of the last transition between available and unavailable in the backward direction.
If there have been no transitions since the Loss Measurement Session was started, this is set to 0.
This table contains the results for the current Measurement Interval in a SOAM Loss Measurement session gathered during the interval indicated by iterator counts.
A row in this table is created automatically by the SNMP Agent when the Loss Measurement session is configured.
Each row in the table represents the current statistics for a Loss Measurement session for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific LM session on the selected MEP. There may be more than one LM session per MEP. The main use case for this is to allow multiple CoS instances to be operating simultaneously for a MEP.
The objects in this table apply regardless of the value of jnxSoamLmCfgType unless otherwise specified in the object description.
Except for jnxSoamLmCurrentStatsIndex, jnxSoamLmCurrentStatsStartTime, jnxSoamLmCurrentStatsElapsedTime and jnxSoamLmCurrentStatsSuspect, each object in this table applies only if the corresponding bit is set in jnxSoamLmCfgMeasurementEnable.
The objects in this table do not need to be persistent upon reboot or restart of a device.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamLmCurrentStatsIndex
1.3.6.1.4.1.2636.3.78.1.2.3.1.1
Unsigned32
The index for the current Measurement Interval for this PM session. This value will become the value for jnxSoamLmHistoryStatsIndex once the Measurement Interval is completed.
Measurement Interval indexes are assigned sequentially by the SNMP Agent. The first Measurement Interval that occurs after the session is started is assigned index 1.
jnxSoamLmCurrentStatsStartTime
1.3.6.1.4.1.2636.3.78.1.2.3.1.2
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Reference: [MEF SOAM-PM] R22, R87, R112
The time that the current Measurement Interval started.
jnxSoamLmCurrentStatsElapsedTime
1.3.6.1.4.1.2636.3.78.1.2.3.1.3
TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32
Reference: [MEF SOAM-PM] R24, R87, R112
The time that the current Measurement Interval has been running, in 0.01 seconds.
jnxSoamLmCurrentStatsSuspect
1.3.6.1.4.1.2636.3.78.1.2.3.1.4
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: [MEF SOAM-PM] R39, R40, R41
Whether the Measurement Interval has been marked as suspect.
The object is set to false at the start of a measurement interval. It is set to true when there is a discontinuity in the performance measurements during the Measurement Interval. Conditions for a discontinuity include, but are not limited to the following:
1 - The local time-of-day clock is adjusted by at least 10 seconds 2 - The conducting of a performance measurement is halted before the current Measurement Interval is completed 3 - A local test, failure, or reconfiguration that disrupts service
jnxSoamLmCurrentStatsForwardTransmittedFrames
1.3.6.1.4.1.2636.3.78.1.2.3.1.5
Gauge32
Reference: [MEF SOAM-PM] R69, R87, R112
This object contains the number of frames transmitted in the forward direction by this MEP.
For a PM Session of types lmLmm and lmCcm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only. For a PM Session of type lmSlm this includes the count of SOAM ETH-SLM frames only.
jnxSoamLmCurrentStatsForwardReceivedFrames
1.3.6.1.4.1.2636.3.78.1.2.3.1.6
Gauge32
Reference: [MEF SOAM-PM] R69, R87, R112
This object contains the number of frames received in the forward direction by this MEP.
For a PM Session of types lmLmm and lmCcm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only.
For a PM Session of types lmSlm this includes the count of SOAM ETH-SLM frames only.
jnxSoamLmCurrentStatsForwardMinFlr
1.3.6.1.4.1.2636.3.78.1.2.3.1.7
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the minimum one-way frame loss ratio in the forward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmCurrentStatsForwardMaxFlr
1.3.6.1.4.1.2636.3.78.1.2.3.1.8
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the maximum one-way frame loss ratio in the forward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmCurrentStatsForwardAvgFlr
1.3.6.1.4.1.2636.3.78.1.2.3.1.9
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the average one-way frame loss ratio in the forward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmCurrentStatsBackwardTransmittedFrames
1.3.6.1.4.1.2636.3.78.1.2.3.1.10
Gauge32
Reference: [MEF SOAM-PM] R69, R87, R112
This object contains the number of frames transmitted in the backward direction by this MEP.
For a PM Session of type lmLmm and lmCcm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only.
For a PM Session of type lmSlm this includes the count of SOAM ETH-SLM frames only.
jnxSoamLmCurrentStatsBackwardReceivedFrames
1.3.6.1.4.1.2636.3.78.1.2.3.1.11
Gauge32
Reference: [MEF SOAM-PM] R69, R87, R112
This object contains the number of frames received in the backward direction by this MEP.
For a PM Session of type lmLmm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only.
For a PM Session of type lmSlm this includes the count of SOAM ETH-SLM frames only.
jnxSoamLmCurrentStatsBackwardMinFlr
1.3.6.1.4.1.2636.3.78.1.2.3.1.12
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the minimum one-way frame loss ratio in the backward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmCurrentStatsBackwardMaxFlr
1.3.6.1.4.1.2636.3.78.1.2.3.1.13
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the maximum one-way frame loss ratio in the backward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmCurrentStatsBackwardAvgFlr
1.3.6.1.4.1.2636.3.78.1.2.3.1.14
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the average one-way frame loss ratio in the backward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmCurrentStatsSoamPdusSent
1.3.6.1.4.1.2636.3.78.1.2.3.1.15
Gauge32
Reference: [MEF SOAM-PM] R69, R87, R112
This object contains the count of the number of SOAM PDUs sent during this Measurement Interval.
This object applies when jnxSoamLmCfgType is lmLmm, lmSlm, or
lmCcm. It indicates the number of LMM, CCM, or SLM SOAM frames transmitted.
jnxSoamLmCurrentStatsSoamPdusReceived
1.3.6.1.4.1.2636.3.78.1.2.3.1.16
Gauge32
Reference: [MEF SOAM-PM] R69, R87, R112
This object contains the count of the number of SOAM PDUs PDUs received in this Measurement Interval.
This object applies when jnxSoamLmCfgType is lmLmm, lmSlm, or
lmCcm. This object indicates the number of LMR, CCM, or SLR SOAM frames received.
This table contains the results for history Measurement Intervals in a SOAM Loss Measurement session.
Rows of this table object are created automatically by the SNMP Agent when the Loss Measurement session is running and a Measurement Interval is completed.
Each row in the table represents the history statistics for a Loss Measurement session Measurement Interval for the defined MEP. This table uses five indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific LM session on the selected MEP. The fifth index index the specific Measurement Interval.
At least 32 completed Measurement Intervals are to be supported. 96 completed Measurement Intervals are recommended to be supported. If there are at least 32 rows in the table and a new Measurement Interval completes and a new row is to be added to the table, the oldest completed Measurement Interval may be deleted (row deletion). If the measurement interval is other than 15 minutes then a minimum of 8 hours of completed Measurement Intervals are to be supported and 24 hours are recommended to be supported.
Except for jnxSoamLmHistoryStatsIndex, jnxSoamLmHistoryStatsEndTime, jnxSoamLmHistoryStatsElapsedTime and jnxSoamLmHistoryStatsSuspect, each object in this table applies only if the corresponding bit is set in jnxSoamLmCfgMeasurementEnable.
The rows and objects in this table are to be persistent upon reboot or restart of a device.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamLmHistoryStatsIndex
1.3.6.1.4.1.2636.3.78.1.2.4.1.1
Unsigned32
The index for the Measurement Interval within this PM session.
Measurement Interval indexes are assigned sequentially by the SNMP Agent. The first Measurement Interval that occurs after the session is started is assigned index 1. Measurement Intervals for FLR (stored in this table) are based on iterator count and are indexed independently of Measurement Intervals for availability
Referential integrity is necessary, i.e., the index needs to be persistent upon a reboot or restart of a device. The index is never reused while this session is active until it wraps to zero. The index value keeps increasing up to that time.
jnxSoamLmHistoryStatsEndTime
1.3.6.1.4.1.2636.3.78.1.2.4.1.2
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Reference: [MEF SOAM-PM] R23, R87, R112
The time that the Measurement Interval ended.
jnxSoamLmHistoryStatsElapsedTime
1.3.6.1.4.1.2636.3.78.1.2.4.1.3
TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32
Reference: [MEF SOAM-PM] R24, R87, R112
The length of time that the Measurement Interval ran for, in 0.01 seconds.
jnxSoamLmHistoryStatsSuspect
1.3.6.1.4.1.2636.3.78.1.2.4.1.4
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: [MEF SOAM-PM] R39, R40, R41, R42
Whether the Measurement Interval has been marked as suspect.
The object is set to true when there is a discontinuity in the performance measurements during the Measurement Interval. Conditions for a discontinuity include, but are not limited to the following:
1 - The local time-of-day clock is adjusted by at least 10 seconds 2 - The conducting of a performance measurement is halted before the current Measurement Interval is completed 3 - A local test, failure, or reconfiguration that disrupts service
jnxSoamLmHistoryStatsForwardTransmittedFrames
1.3.6.1.4.1.2636.3.78.1.2.4.1.5
Gauge32
Reference: [MEF SOAM-PM] R69, R87, R112
This object contains the number of frames transmitted in the forward direction by this MEP.
For a PM Session of types lmLmm and lmCcm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only.
For a PM Session of type lmSlm this includes the count of OAM ETH-SLM frames only.
jnxSoamLmHistoryStatsForwardReceivedFrames
1.3.6.1.4.1.2636.3.78.1.2.4.1.6
Gauge32
Reference: [MEF SOAM-PM] R69, R87, R112
This object contains the number of frames received in the forward direction by this MEP.
For a PM Session of types lmLmm and lmCcm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only.
For a PM Session of type lmSlm this includes the count of OAM ETH-SLM frames only.
jnxSoamLmHistoryStatsForwardMinFlr
1.3.6.1.4.1.2636.3.78.1.2.4.1.7
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the minimum one-way frame loss ratio in the forward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmHistoryStatsForwardMaxFlr
1.3.6.1.4.1.2636.3.78.1.2.4.1.8
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the maximum one-way frame loss ratio in the forward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmHistoryStatsForwardAvgFlr
1.3.6.1.4.1.2636.3.78.1.2.4.1.9
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the average one-way frame loss ratio in the forward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmHistoryStatsBackwardTransmittedFrames
1.3.6.1.4.1.2636.3.78.1.2.4.1.10
Gauge32
Reference: [MEF SOAM-PM] D37
This object contains the number of frames transmitted in the backward direction by this MEP.
For a PM Session of type lmLmm and lmCcm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only.
For a PM Session of types lmSlm this includes the count of SOAM ETH-SLM frames only.
jnxSoamLmHistoryStatsBackwardReceivedFrames
1.3.6.1.4.1.2636.3.78.1.2.4.1.11
Gauge32
Reference: [MEF SOAM-PM] R69, R87, R112
This object contains the number of frames received in the backward direction by this MEP.
For a PM Session of type lmLmm and lmCcm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only.
For a PM Session of types lmSlm this includes the count of SOAM ETH-SLM frames only.
jnxSoamLmHistoryStatsBackwardMinFlr
1.3.6.1.4.1.2636.3.78.1.2.4.1.12
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] R69, R87, R112
This object contains the minimum one-way frame loss ratio in the backward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmHistoryStatsBackwardMaxFlr
1.3.6.1.4.1.2636.3.78.1.2.4.1.13
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the maximum one-way frame loss ratio in the backward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmHistoryStatsBackwardAvgFlr
1.3.6.1.4.1.2636.3.78.1.2.4.1.14
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the average one-way frame loss ratio in the backward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmHistoryStatsSoamPdusSent
1.3.6.1.4.1.2636.3.78.1.2.4.1.15
Gauge32
Reference: [MEF SOAM-PM] R69, R87
This object contains the count of the number of SOAM PDUs sent during this Measurement Interval.
This object applies when jnxSoamLmCfgType is lmLmm, lmSlm, or lmCcm. It indicates the number of LMM, CCM, or SLM SOAM frames transmitted.
jnxSoamLmHistoryStatsSoamPdusReceived
1.3.6.1.4.1.2636.3.78.1.2.4.1.16
Gauge32
Reference: [MEF SOAM-PM] R69, R87
This object contains the count of the number of SOAM PDUs received in this Measurement Interval.
This object applies when jnxSoamLmCfgType is lmLmm, lmSlm, or lmCcm. This object indicates the number of LMR, CCM, or SLR SOAM frames received.
This table contains the list of Loss Measurement configuration threshold values for LM Performance Monitoring. The main purpose of the threshold configuration table is to configure threshold alarm notifications indicating that a specific performance metric is not being met.
Each row in the table represents a Loss Measurement session threshold set for the defined MEP. This table uses five indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific LM session on the selected MEP. The fifth index is the specific threshold set number.
Rows in this table are not created automatically. A row is created in this table to set up a threshold set on a configured MEP that has a configured LM session.
If two managers try to 'create' the same row at the same time, the first creation would succeed, the second creation attempt would result in an error. The second creation attempt would then need to select a new index value to successfully create a new row.
An NE needs to support at least one threshold set for NE SOAM PM compliance. A second threshold set on the NE is desirable. More than two threshold sets can be configured on the NE if supported on the NE.
All the objects in the row have a default value that disables the particular threshold measurement. In order to enable a threshold measurement the particular bit in the jnxSoamLmThresholdCfgEnable object is to be set to '1' and the selected threshold measurement is to have a threshold value configured. Non-configured threshold measurements are disabled by default.
The writable objects in this table need to be persistent upon reboot or restart of a device.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamLmThresholdCfgIndex
1.3.6.1.4.1.2636.3.78.1.2.5.1.1
Unsigned32
The index of the threshold number for the specific LM threshold entry.
An index value of '1' needs to be supported. Other index values can also be supported.
jnxSoamLmThresholdCfgEnable
1.3.6.1.4.1.2636.3.78.1.2.5.1.2
BITS
A vector of bits that indicates the type of SOAM LM thresholds notifications that are enabled.
A bit set to '1' enables the specific SOAM LM threshold notification and when the specific counter is enabled and the threshold is crossed a notification is generated.
A bit set to '0' disables the specific SOAM LM threshold notification.
If a particular SOAM LM threshold is not supported the BIT value is set to '0'.
bJnxSoamLmMeasuredFlrForwardThreshold(0) Enables/disables measured frame loss forward ratio threshold notification. The notification is sent immediately when the jnxSoamLmMeasuredStatsForwardFlr value is greater than or equal to the threshold value. bJnxSoamLmMaxFlrForwardThreshold(1) Enables/disables maximum frame loss forward ratio threshold notification. The notification is sent immediately when the jnxSoamLmCurrentStatsForwardMaxFlr value is greater than or equal to threshold value in a Measurement Interval. bJnxSoamLmAvgFlrForwardThreshold(2) Enables/disables average frame loss forward ratio threshold notification. The notification is sent when at the end of a Measurement Interval if the jnxSoamLmCurrentStatsForwardAvgFlr value is greater than or equal to the threshold value. bJnxSoamLmMeasuredFlrBackwardThreshold(3) Enables/disables measured frame loss backward ratio threshold notification. The notification is sent immediately when the jnxSoamLmMeasuredStatsBackwardFlr value is greater than or equal to the threshold value. bJnxSoamLmMaxFlrBackwardThreshold(4) Enables/disables maximum frame loss backward ratio threshold notification. The notification is sent immediately when the jnxSoamLmCurrentStatsBackwardMaxFlr value is greater than or equal to threshold value in a Measurement Interval. bJnxSoamLmAvgFlrBackwardThreshold(5) Enables/disables average frame loss backward ratio threshold notification. The notification is sent when at the end of a Measurement Interval if the jnxSoamLmCurrentStatsBackwardAvgFlr value is greater than or equal to the threshold value.
jnxSoamLmThresholdCfgAvgFlrForwardThreshold
1.3.6.1.4.1.2636.3.78.1.2.5.1.3
Unsigned32 (0..100000) · milli-percent
This object is used to set the average forward frame loss ratio threshold value that will be used to determine if a threshold notification is generated.
jnxSoamLmThresholdCfgAvgFlrBackwardThreshold
1.3.6.1.4.1.2636.3.78.1.2.5.1.4
Unsigned32 (0..100000) · milli-percent
This object is used to set the average backward frame loss ratio threshold value that will be used to determine if a threshold notification is generated.
jnxSoamLmThresholdCfgRowStatus
1.3.6.1.4.1.2636.3.78.1.2.5.1.5
RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].)
The status column has six defined values:
- `active', which indicates that the conceptual row is available for use by the managed device;
- `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device;
- `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated);
- `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device;
- `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row.
Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management
protocol retrieval operation: `notReady', `notInService' or
`active'. That is, when queried, an existing conceptual row
has only three states: it is either available for use by
the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady').
NOTE WELL
This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'.
Also note that whenever any elements of a row exist, the RowStatus column must also exist.
To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram:
STATE +--------------+-----------+-------------+-------------
| A | B | C | D
| |status col.|status column|
|status column | is | is |status column
ACTION |does not exist| notReady | notInService| is active
--------------+--------------+-----------+-------------+-------------
set status |noError ->D|inconsist- |inconsistent-|inconsistent-
column to | or | entValue| Value| Value
createAndGo |inconsistent- | | |
| Value| | |
--------------+--------------+-----------+-------------+-------------
set status |noError see 1|inconsist- |inconsistent-|inconsistent-
column to | or | entValue| Value| Value
createAndWait |wrongValue | | |
--------------+--------------+-----------+-------------+-------------
set status |inconsistent- |inconsist- |noError |noError
column to | Value| entValue| |
active | | | |
| | or | |
| | | |
| |see 2 ->D|see 8 ->D| ->D
--------------+--------------+-----------+-------------+-------------
set status |inconsistent- |inconsist- |noError |noError ->C
column to | Value| entValue| |
notInService | | | |
| | or | | or
| | | |
| |see 3 ->C| ->C|see 6
--------------+--------------+-----------+-------------+-------------
set status |noError |noError |noError |noError ->A
column to | | | | or
destroy | ->A| ->A| ->A|see 7
--------------+--------------+-----------+-------------+-------------
set any other |see 4 |noError |noError |see 5
column to some| | | |
value | | see 1| ->C| ->D
--------------+--------------+-----------+-------------+-------------
(1) goto B or C, depending on information available to the agent.
(2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D.
(3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C.
(4) at the discretion of the agent, the return value may be either:
inconsistentName: because the agent does not choose to
create such an instance when the corresponding RowStatus instance does not exist, or
inconsistentValue: if the supplied value is
inconsistent with the state of some other MIB object's value, or
noError: because the agent chooses to create the instance.
If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A.
(5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned.
(6) the return value can indicate one of the following errors:
wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or
inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated.
(7) the return value can indicate the following error:
inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated.
(8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue.
NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc.
Conceptual Row Creation
There are four potential interactions when creating a
conceptual row: selecting an instance-identifier which is
not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device.
Interaction 1: Selecting an Instance-Identifier
The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics.
In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.)
Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different.
Finally, the management station could select a pseudo-random number to use as the index. In the event that this index
was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation.
A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used.
Interaction 2: Creating the Conceptual Row
Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions.
Interaction 2a: Creating and Activating the Conceptual Row
The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes:
- a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1.
- the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created.
- the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column.
Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'.
When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information
available to the agent is provided by two sources: the
management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row.
NOTE WELL
Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm.
Interaction 2b: Negotiating the Creation of the Conceptual Row
The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the
columns indicated by its column requirements.) Otherwise,
the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3.
Interaction 3: Initializing non-defaulted Objects
The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes:
- a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column.
- the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column.
- the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column.
If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4.
Interaction 4: Making the Conceptual Row Available
Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'.
NOTE WELL
A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device.
If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row.
Conceptual Row Suspension
When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified).
Conceptual Row Deletion
For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady',
`notInService' or `active'.) If the operation succeeds,
then all instances associated with the conceptual row are immediately removed. · Integer32
The status of the row.
The writable columns in a row cannot be changed if the row is active. All columns are to have a valid value before a row can be activated.
This object contains the current results for a SOAM Loss Measurement session for availability statistics gathered during the interval indicated by jnxSoamLmCfgAvailabilityMeasurementInterval.
Each row in the table represents a Loss Measurement session for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific LM session on the selected MEP.
Instances of this managed object are created automatically by the SNMP Agent when the Loss Measurement session is running.
The objects in this table apply regardless of the value of jnxSoamLmCfgType unless otherwise specified in the object description.
Except for jnxSoamLmCurrentAvailStatsIndex, jnxSoamLmCurrentAvailStatsStartTime, jnxSoamLmCurrentAvailStatsElapsedTime and jnxSoamLmCurrentAvailStatsSuspect, each object in this table applies only if the corresponding bit is set in jnxSoamLmCfgMeasurementEnable.
The objects in this table may be persistent upon reboot or restart of a device.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamLmCurrentAvailStatsIndex
1.3.6.1.4.1.2636.3.78.1.2.6.1.1
Unsigned32
The index for the current availability Measurement Interval for this PM session. This value will become the value for jnxSoamLmHistoryAvailStatsIndex once the Measurement Interval is completed. The duration of the Measurement Interval is specified by jnxSoamLmCfgAvailabilityMeasurementInterval.
Measurement Interval indexes are assigned sequentially by the SNMP Agent. The first Measurement Interval that occurs after the session is started is assigned index 1.
jnxSoamLmCurrentAvailStatsStartTime
1.3.6.1.4.1.2636.3.78.1.2.6.1.2
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Reference: [MEF SOAM-PM] R87, R112
The time that the current Measurement Interval started.
jnxSoamLmCurrentAvailStatsElapsedTime
1.3.6.1.4.1.2636.3.78.1.2.6.1.3
TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32
Reference: [MEF SOAM-PM] R24, R87, R112
The time that the current Measurement Interval has been running, in 0.01 seconds.
jnxSoamLmCurrentAvailStatsSuspect
1.3.6.1.4.1.2636.3.78.1.2.6.1.4
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: [MEF SOAM-PM] R39, R40, R41
Whether the Measurement Interval has been marked as suspect.
The object is set to false at the start of a measurement interval. It is set to true when there is a discontinuity in the performance measurements during the Measurement Interval. Conditions for a discontinuity include, but are not limited to the following:
1 - The local time-of-day clock is adjusted by at least 10 seconds 2 - The conducting of a performance measurement is halted before the current Measurement Interval is completed 3 - A local test, failure, or reconfiguration that disrupts service
jnxSoamLmCurrentAvailStatsForwardHighLoss
1.3.6.1.4.1.2636.3.78.1.2.6.1.5
Unsigned32
Reference: [MEF 10.2.1] 6.9.9; [MEF SOAM-PM] R87
This object is the number of high loss intervals (HLI) over time in the forward direction.
The value starts at 0 and increments for every HLI that occurs. This parameter is equivalent to 'L Sub T' found in MEF 10.2.1.
jnxSoamLmCurrentAvailStatsBackwardHighLoss
1.3.6.1.4.1.2636.3.78.1.2.6.1.6
Unsigned32
Reference: [MEF 10.2.1] 6.9.9; [MEF SOAM-PM] R87
This object is the number of high loss intervals (HLI) over time in the backwards direction.
The value starts at 0 and increments for every HLI that occurs. This parameter is equivalent to 'L Sub T' found in MEF 10.2.1.
This object is the number of consecutive high loss intervals (CHLI) over time in the forward direction.
The value starts at 0 and increments for every HLI that occurs that is determined to fall within a CHLI. This parameter is equivalent to 'B Sub T' found in MEF 10.2.1.
This object is the number of consecutive high loss intervals (CHLI) over time in the backward direction.
The value starts at 0 and increments for every HLI that occurs that is determined to fall within a CHLI. This parameter is equivalent to 'B Sub T' found in MEF 10.2.1.
jnxSoamLmCurrentAvailStatsForwardAvailable
1.3.6.1.4.1.2636.3.78.1.2.6.1.9
Gauge32
Reference: [MEF SOAM-PM] R87; [MEF 10.2.1]
This object contains the number of availability indicators evaluated as available in the forward direction by this MEP during this Measurement Interval.
jnxSoamLmCurrentAvailStatsBackwardAvailable
1.3.6.1.4.1.2636.3.78.1.2.6.1.10
Gauge32
Reference: [MEF SOAM-PM] R87
This object contains the number of availability indicators evaluated as available in the backward direction by this MEP during this Measurement Interval.
jnxSoamLmCurrentAvailStatsForwardUnavailable
1.3.6.1.4.1.2636.3.78.1.2.6.1.11
Gauge32
Reference: [MEF SOAM-PM] R87
This object contains the number of availability indicators evaluated as unavailable in the forward direction by this MEP during this Measurement Interval.
jnxSoamLmCurrentAvailStatsBackwardUnavailable
1.3.6.1.4.1.2636.3.78.1.2.6.1.12
Gauge32
Reference: [MEF SOAM-PM] R87
This object contains the number of availability indicators evaluated as unavailable in the backward direction by this MEP during this Measurement Interval.
jnxSoamLmCurrentAvailStatsForwardMinFlr
1.3.6.1.4.1.2636.3.78.1.2.6.1.13
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the minimum one-way availability flr in the forward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each 'delta_t' time period within the Measurement Interval, as specified in MEF 10.2.1.
The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 2626 0.001 percent.
jnxSoamLmCurrentAvailStatsForwardMaxFlr
1.3.6.1.4.1.2636.3.78.1.2.6.1.14
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the maximum one-way availability flr in the forward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each 'delta_t' time period within the Measurement Interval, as specified in MEF 10.2.1.
The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmCurrentAvailStatsForwardAvgFlr
1.3.6.1.4.1.2636.3.78.1.2.6.1.15
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the average one-way availability flr in the forward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each 'delta_t' time period within the Measurement Interval, as specified in MEF 10.2.1.
The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmCurrentAvailStatsBackwardMinFlr
1.3.6.1.4.1.2636.3.78.1.2.6.1.16
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the minimum one-way availability flr in the backward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each 'delta_t' time period within the Measurement Interval, as specified in MEF 10.2.1.
The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmCurrentAvailStatsBackwardMaxFlr
1.3.6.1.4.1.2636.3.78.1.2.6.1.17
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the maximum one-way availability flr in the backward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each 'delta_t' time period within the Measurement Interval, as specified in MEF 10.2.1.
The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmCurrentAvailStatsBackwardAvgFlr
1.3.6.1.4.1.2636.3.78.1.2.6.1.18
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the average one-way availability flr in the backward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each 'delta_t' time period within the Measurement Interval, as specified in MEF 10.2.1.
The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
This table contains the results for availability history Measurement Intervals in a SOAM Loss Measurement session.
Rows of this table object are created automatically by the SNMP Agent when the Loss Measurement session is running and a Measurement Interval is completed.
Each row in the table represents the history statistics for a Loss Measurement session availability Measurement Interval for the defined MEP. This table uses five indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific LM session on the selected MEP. The fifth index index the specific Measurement Interval.
At least 32 completed Measurement Intervals are to be supported. 96 completed Measurement Intervals are recommended to be supported. If there are at least 32 rows in the table and a new Measurement Interval completes and a new row is to be added to the table, the oldest completed Measurement Interval can be deleted (row deletion). If the availability Measurement Interval is other than 15 minutes then a minimum of 8 hours of completed Measurement Intervals are to be supported and 24 hours are recommended to be supported.
Except for jnxSoamLmHistoryAvailStatsIndex, jnxSoamLmHistoryAvailStatsEndTime, jnxSoamLmHistoryAvailStatsElapsedTime and jnxSoamLmHistoryAvailStatsSuspect, each object in this table applies only if the corresponding bit is set in jnxSoamLmCfgMeasurementEnable.
The rows and objects in this table are to be persistent upon reboot or restart of a device.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamLmHistoryAvailStatsIndex
1.3.6.1.4.1.2636.3.78.1.2.7.1.1
Unsigned32
The index for the availability Measurement Interval within this PM session.
Measurement Interval indexes are assigned sequentially by the SNMP Agent. The first Measurement Interval that occurs after the session is started is assigned index 1. Measurement Intervals for availability (stored in this table) are based on jnxSoamLmCfgAvailabilityMeasurementInterval and are indexed independently of Measurement Intervals for FLR (stored in jnxSoamLmHistoryStatsTable).
Referential integrity is necessary, i.e., the index needs to be persistent upon a reboot or restart of a device. The index is never reused while this session is active until it wraps to zero. The index value keeps increasing up to that time.
jnxSoamLmHistoryAvailStatsEndTime
1.3.6.1.4.1.2636.3.78.1.2.7.1.2
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Reference: [MEF SOAM-PM] R23, R87, R112
The time that the Measurement Interval ended.
jnxSoamLmHistoryAvailStatsElapsedTime
1.3.6.1.4.1.2636.3.78.1.2.7.1.3
TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32
Reference: [MEF SOAM-PM] R24, R87, R112
The length of time that the Measurement Interval ran for, in 0.01 seconds.
jnxSoamLmHistoryAvailStatsSuspect
1.3.6.1.4.1.2636.3.78.1.2.7.1.4
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: [MEF SOAM-PM] R39, R40, R41, R42
Whether the Measurement Interval has been marked as suspect.
The object is set to true when there is a discontinuity in the performance measurements during the Measurement Interval. Conditions for a discontinuity include, but are not limited to the following:
1 - The local time-of-day clock is adjusted by at least 10 seconds 2 - The conducting of a performance measurement is halted before the current Measurement Interval is completed 3 - A local test, failure, or reconfiguration that disrupts service
jnxSoamLmHistoryAvailStatsForwardHighLoss
1.3.6.1.4.1.2636.3.78.1.2.7.1.5
Unsigned32
Reference: [MEF 10.2.1] 6.9.9; [MEF SOAM-PM] R87
This object is the number of high loss intervals (HLI) over time in the forward direction.
The value starts at 0 and increments for every HLI that occurs. This parameter is equivalent to 'L Sub T' found in MEF 10.2.1.
jnxSoamLmHistoryAvailStatsBackwardHighLoss
1.3.6.1.4.1.2636.3.78.1.2.7.1.6
Unsigned32
Reference: [MEF 10.2.1] 6.9.9; [MEF SOAM-PM] R87
This object is the number of high loss intervals (HLI) over time in the backward direction.
The value starts at 0 and increments for every HLI that occurs. This parameter is equivalent to 'L Sub T' found in MEF 10.2.1.
This object is the number of consecutive high loss intervals (CHLI) over time in the forward direction.
The value starts at 0 and increments for every HLI that occurs that is determined to fall within a CHLI. This parameter is equivalent to 'B Sub T' found in MEF 10.2.1.
This object is the number of consecutive high loss intervals (CHLI) over time in the forward direction.
The value starts at 0 and increments for every HLI that occurs that is determined to fall within a CHLI. This parameter is equivalent to 'B Sub T' found in MEF 10.2.1.
jnxSoamLmHistoryAvailStatsForwardAvailable
1.3.6.1.4.1.2636.3.78.1.2.7.1.9
Gauge32
Reference: [MEF SOAM-PM] R87; [MEF 10.2.1]
This object contains the number of availability indicators evaluated as available in the forward direction by this MEP during this Measurement Interval.
jnxSoamLmHistoryAvailStatsBackwardAvailable
1.3.6.1.4.1.2636.3.78.1.2.7.1.10
Gauge32
Reference: [MEF SOAM-PM] R87
This object contains the number of availability indicators evaluated as available in the backward direction by this MEP during this Measurement Interval.
jnxSoamLmHistoryAvailStatsForwardUnavailable
1.3.6.1.4.1.2636.3.78.1.2.7.1.11
Gauge32
Reference: [MEF SOAM-PM] R87
This object contains the number of availability indicators evaluated as unavailable in the forward direction by this MEP during this Measurement Interval.
jnxSoamLmHistoryAvailStatsBackwardUnavailable
1.3.6.1.4.1.2636.3.78.1.2.7.1.12
Gauge32
Reference: [MEF SOAM-PM] R87
This object contains the number of availability indicators evaluated as unavailable in the backward direction by this MEP during this Measurement Interval.
jnxSoamLmHistoryAvailStatsForwardMinFlr
1.3.6.1.4.1.2636.3.78.1.2.7.1.13
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the minimum one-way availability flr in the forward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each 'delta_t' time period within the Measurement Interval, as specified in MEF 10.2.1.
The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmHistoryAvailStatsForwardMaxFlr
1.3.6.1.4.1.2636.3.78.1.2.7.1.14
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the maximum one-way availability flr in the forward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each 'delta_t' time period within the Measurement Interval, as specified in MEF 10.2.1.
The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmHistoryAvailStatsForwardAvgFlr
1.3.6.1.4.1.2636.3.78.1.2.7.1.15
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the average one-way availability flr in the forward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each 'delta_t' time period within the Measurement Interval, as specified in MEF 10.2.1.
The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmHistoryAvailStatsBackwardMinFlr
1.3.6.1.4.1.2636.3.78.1.2.7.1.16
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the minimum one-way availability flr in the backward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each 'delta_t' time period within the Measurement Interval, as specified in MEF 10.2.1.
The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmHistoryAvailStatsBackwardMaxFlr
1.3.6.1.4.1.2636.3.78.1.2.7.1.17
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the maximum one-way availability flr in the backward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each 'delta_t' time period within the Measurement Interval, as specified in MEF 10.2.1.
The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 0.001 percent.
jnxSoamLmHistoryAvailStatsBackwardAvgFlr
1.3.6.1.4.1.2636.3.78.1.2.7.1.18
Unsigned32 (0..100000) · milli-percent
Reference: [MEF SOAM-PM] D37
This object contains the average one-way availability flr in the backward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each 'delta_t' time period within the Measurement Interval, as specified in MEF 10.2.1.
The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00).
Units are in milli-percent, where 1 indicates 3458 0.001 percent.
This table includes configuration objects and operations for the Delay Measurement function.
Each row in the table represents a Delay Measurement session for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific DM session on the selected MEP.
A Delay Measurement session is created on an existing MEP by first accessing the jnxSoamDmOperNextIndex object and using this value as the jnxSoamDmCfgIndex in the row creation.
Some writable objects in this table are only applicable in certain cases (as described under each object), and attempts to write values for them in other cases will be ignored.
The writable objects in this table need to be persistent upon reboot or restart of a device.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamDmCfgIndex
1.3.6.1.4.1.2636.3.78.1.3.1.1.1
Unsigned32 (1..4294967295)
An index to the Delay Measurement Configuration table which indicates the specific measurement session for the MEP.
jnxSoamPmMepOperNextIndex needs to be inspected to find an available index for row-creation.
Referential integrity is necessary, i.e., the index needs to be persistent upon a reboot or restart of a device. The index is never reused for other PM sessions on the same MEP while this session is active. The index value keeps increasing until it wraps to zero. This is to facilitate access control based on a fixed index for an EMS, since the index is not reused.
This object indicates what type of Delay Measurement is to be performed.
dmDmm(1) DMM SOAM PDU generated, DMR responses received (one-way or two-way measurements) dm1DmTx(2) 1DM SOAM PDU generated (one-way measurements are made by the receiver) dm1DmRx(3) 1DM SOAM PDU received and tracked (one-way measurements)
The exact PDUs to use are specified by this object in combination with jnxSoamDmCfgVersion.
The value dmDMM is required. The values dm1DmTx and dm1DmRx are optional.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgVersion
1.3.6.1.4.1.2636.3.78.1.3.1.1.3
Unsigned32
Reference: [Y.1731]
This object indicates the version of the PDUs used to perform Delay Measurement.
Version 0 indicates the PDU formats defined in Y.1731-2008. Version 1 indicates the PDU formats defined in Y.1731-2011.
The exact PDUs to use are specified by this object in combination with jnxSoamDmCfgType.
This object can only be written at row creation time and cannot be
modified once it has been created.
jnxSoamDmCfgEnabled
1.3.6.1.4.1.2636.3.78.1.3.1.1.4
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: [MEF SOAM-PM] R4, R5, R6, O1, R12, R14
This object specifies whether the Delay Measurement session is enabled.
The value 'true' indicates the Delay Measurement session is enabled AND SOAM PDUs are sent and/or measurements are collected when the session is running according to the scheduling objects (start time, stop time, etc.).
The value 'false' indicates the Delay Measurement session is disabled AND SOAM PDUs are not sent and/or measurements collected.
For a Delay Measurement session to be removed the row is deleted in order to release internal resources.
This object can written/modified after row creation time.
If the DM session is enabled it resumes after shutdown/restart.
If the DM session is disabled the current Measurement Interval is stopped, if it in process at the time, and all the in process calculations for the partially completed Measurement Interval are finalized.
This object does not affect whether the single-ended Responder is enabled or not, which is enabled or disabled by the jnxSoamPmMepDmSingleEndedResponder object.
jnxSoamDmCfgMeasurementEnable
1.3.6.1.4.1.2636.3.78.1.3.1.1.5
BITS
Reference: [MEF SOAM-PM]
A vector of bits that indicates the type of SOAM DM counters that are enabled.
A bit set to '1' enables the specific SOAM DM counter.
A bit set to '0' disables the SOAM DM counter.
If a particular SOAM DM counter is not supported the BIT value is set to '0'.
Not all SOAM DM counters are supported for all SOAM DM types.
This object can only be written at row creation time and cannot be modified once it has been created.
bSoamPdusSent(0) Enables/disables the jnxSoamDmCurrentStatsSoamPdusSent and jnxSoamDmHistoryStatsSoamPdusSent counters. bSoamPdusReceived(1) Enables/disables the jnxSoamDmCurrentStatsSoamPdusReceived and jnxSoamDmHistoryStatsSoamPdusReceived counters. bFrameDelayTwoWayBins(2) Enables/disables the jnxSoamDmCurrentStatsBinsEntry counter and the jnxSoamDmHistoryStatsBinsEntry counter when the jnxSoamDmCfgMeasBinType is 'twoWayFrameDelay'. bFrameDelayTwoWayMin(3) Enables/disables the jnxSoamDmCurrentStatsFrameDelayTwoWayMin and jnxSoamDmHistoryStatsFrameDelayTwoWayMin counters. bFrameDelayTwoWayMax(4) Enables/disables the jnxSoamDmCurrentStatsFrameDelayTwoWayMax and jnxSoamDmHistoryStatsFrameDelayTwoWayMax counters. bFrameDelayTwoWayAvg(5) Enables/disables the jnxSoamDmCurrentStatsFrameDelayTwoWayAvg and jnxSoamDmHistoryStatsFrameDelayTwoWayAvg counters. bFrameDelayForwardBins(6) Enables/disables the jnxSoamDmCurrentStatsBinsEntry counter and the jnxSoamDmHistoryStatsBinsEntry counter when the jnxSoamDmCfgMeasBinType is 'forwardFrameDelay'. bFrameDelayForwardMin(7) Enables/disables the jnxSoamDmCurrentStatsFrameDelayForwardMin and jnxSoamDmHistoryStatsFrameDelayForwardMin counters. bFrameDelayForwardMax(8) Enables/disables the jnxSoamDmCurrentStatsFrameDelayForwardMax and jnxSoamDmHistoryStatsFrameDelayForwardMax counters. bFrameDelayForwardAvg(9) Enables/disables the jnxSoamDmCurrentStatsFrameDelayForwardAvg and jnxSoamDmHistoryStatsFrameDelayForwardAvg counters. bFrameDelayBackwardBins(10) Enables/disables the jnxSoamDmCurrentStatsBinsEntry counter and the jnxSoamDmHistoryStatsBinsEntry counter when the jnxSoamDmCfgMeasBinType is 'backwardFrameDelay'. bFrameDelayBackwardMin(11) Enables/disables the jnxSoamDmCurrentStatsFrameDelayBackwardMin and jnxSoamDmHistoryStatsFrameDelayBackwardMin counters. bFrameDelayBackwardMax(12) Enables/disables the jnxSoamDmCurrentStatsFrameDelayBackwardMax and jnxSoamDmHistoryStatsFrameDelayBackwardMax counters. bFrameDelayBackwardAvg(13) Enables/disables the jnxSoamDmCurrentStatsFrameDelayBackwardAvg and jnxSoamDmHistoryStatsFrameDelayBackwardAvg counters. bIfdvForwardBins(14) Enables/disables the jnxSoamDmCurrentStatsBinsEntry counter and the jnxSoamDmHistoryStatsBinsEntry counter when the jnxSoamDmCfgMeasBinType is 'forwardIfdv'. bIfdvForwardMin(15) Enables/disables the jnxSoamDmCurrentStatsIfdvForwardMin and jnxSoamDmHistoryStatsIfdvForwardMin counters. bIfdvForwardMax(16) Enables/disables the jnxSoamDmCurrentStatsIfdvForwardMax and jnxSoamDmHistoryStatsIfdvForwardMax counters. bIfdvForwardAvg(17) Enables/disables the jnxSoamDmCurrentStatsIfdvForwardAvg and jnxSoamDmHistoryStatsIfdvForwardAvg counters. bIfdvBackwardBins(18) Enables/disables the jnxSoamDmCurrentStatsBinsEntry counter and the jnxSoamDmHistoryStatsBinsEntry counter when the jnxSoamDmCfgMeasBinType is 'backwardIfdv'. bIfdvBackwardMin(19) Enables/disables the jnxSoamDmCurrentStatsIfdvBackwardMin and jnxSoamDmHistoryStatsIfdvBackwardMin counters. bIfdvBackwardMax(20) Enables/disables the jnxSoamDmCurrentStatsIfdvBackwardMax and jnxSoamDmHistoryStatsIfdvBackwardMax counters. bIfdvBackwardAvg(21) Enables/disables the jnxSoamDmCurrentStatsIfdvBackwardAvg and jnxSoamDmHistoryStatsIfdvBackwardAvg counters. bIfdvTwoWayBins(22) Enables/disables the jnxSoamDmCurrentStatsBinsEntry counter and the jnxSoamDmHistoryStatsBinsEntry counter when the jnxSoamDmCfgMeasBinType is 'twoWayIfdv'. bIfdvTwoWayMin(23) Enables/disables the jnxSoamDmCurrentStatsIfdvTwoWayMin and jnxSoamDmHistoryStatsIfdvTwoWayMin counters. bIfdvTwoWayMax(24) Enables/disables the jnxSoamDmCurrentStatsIfdvTwoWayMax and jnxSoamDmHistoryStatsIfdvTwoWayMax counters. bIfdvTwoWayAvg(25) Enables/disables the jnxSoamDmCurrentStatsIfdvTwoWayAvg and jnxSoamDmHistoryStatsIfdvTwoWayAvg counters. bFrameDelayRangeForwardBins(26) Enables/disables the jnxSoamDmCurrentStatsBinsEntry counter and the jnxSoamDmHistoryStatsBinsEntry counter when the jnxSoamDmCfgMeasBinType is 'forwardFrameDelayRange'. bFrameDelayRangeForwardMax(27) Enables/disables the jnxSoamDmCurrentStatsFrameDelayRangeForwardMax and jnxSoamDmHistoryStatsFrameDelayRangeForwardMax counters. bFrameDelayRangeForwardAvg(28) Enables/disables the jnxSoamDmCurrentStatsFrameDelayRangeForwardAvg and jnxSoamDmHistoryStatsFrameDelayRangeForwardAvg counters. bFrameDelayRangeBackwardBins(29) Enables/disables the jnxSoamDmCurrentStatsBinsEntry counter and the jnxSoamDmHistoryStatsBinsEntry counter when the jnxSoamDmCfgMeasBinType is 'backwardFrameDelayRange'. bFrameDelayRangeBackwardMax(30) Enables/disables the jnxSoamDmCurrentStatsFrameDelayRangeBackwardMax and jnxSoamDmHistoryStatsFrameDelayRangeBackwardMax counters. bFrameDelayRangeBackwardAvg(31) Enables/disables the jnxSoamDmCurrentStatsFrameDelayRangeBackwardAvg and jnxSoamDmHistoryStatsFrameDelayRangeBackwardAvg counters. bFrameDelayRangeTwoWayBins(32) Enables/disables the jnxSoamDmCurrentStatsBinsEntry counter and the jnxSoamDmHistoryStatsBinsEntry counter when the jnxSoamDmCfgMeasBinType is 'twoWayFrameDelayRange'. bFrameDelayRangeTwoWayMax(33) Enables/disables the jnxSoamDmCurrentStatsFrameDelayRangeTwoWayMax and jnxSoamDmHistoryStatsFrameDelayRangeTwoWayMax counters. bFrameDelayRangeTwoWayAvg(34) Enables/disables the jnxSoamDmCurrentStatsFrameDelayRangeTwoWayAvg and jnxSoamDmHistoryStatsFrameDelayRangeTwoWayAvg counters. bMeasuredStatsFrameDelayTwoWay(35) Enables/disables the jnxSoamDmMeasuredStatsFrameDelayTwoWay counter. bMeasuredStatsFrameDelayForward(36) Enables/disables the jnxSoamDmMeasuredStatsFrameDelayForward counter. bMeasuredStatsFrameDelayBackward(37) Enables/disables the jnxSoamDmMeasuredStatsFrameDelayBackward counter. bMeasuredStatsIfdvTwoWay(38) Enables/disables the jnxSoamDmMeasuredStatsIfdvTwoWay counter. bMeasuredStatsIfdvForward(39) Enables/disables the jnxSoamDmMeasuredStatsIfdvForward counter. bMeasuredStatsIfdvBackward(40) Enables/disables the jnxSoamDmMeasuredStatsIfdvBackward counter.
This object specifies the interval between Delay Measurement OAM message transmission. For Delay Measurement monitoring applications, the default value is 100ms.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgPriority
1.3.6.1.4.1.2636.3.78.1.3.1.1.7
IEEE8021PriorityValueAn IEEE 802.1Q user priority value.Reference: 12.13.3.3 (0..7) · Unsigned32 · hint d
This object specifies the priority of frames with Delay Measurement OAM message information.
The default value is to be the value which yields the lowest frame loss.
This object can only be written at row creation time and cannot be modified once it has been created.
This object specifies the Delay Measurement frame size between 64 bytes and the maximum transmission unit of the EVC.
The range of frame sizes from 64 through 2000 octets need to be supported, and the range of frame sizes from 2001 through 9600 octets is suggested to be supported.
The adjustment to the frame size of the standard frame size is accomplished by the addition of a Data or Test TLV. A Data or Test TLV is only added to the frame if the frame size is greater than 64 bytes.
This object is only valid for the entity transmitting the Delay Measurement frames (dmDmm, dm1DmTx) and is ignored by the entity receiving frames.
In addition, this object is not valid when jnxSoamDmCfgVersion is 0.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgDataPattern
1.3.6.1.4.1.2636.3.78.1.3.1.1.9
JnxSoamTcDataPatternType1 = zeroPattern2 = onesPatternThis enumeration data type indicates the type of data pattern to be sent in an OAM PDU Data TLV. The valid enumerated values associated with this type are: zeroPattern(1) indicates the Data TLV contains all zeros onesPattern(2) indicates the Data TLV contains all ones · Integer32
This object specifies the DM data pattern included in a Data TLV when the size of the DM frame is determined by the jnxSoamDmFrameSize object and jnxSoamDmTestTlvIncluded is 'false'. If the frame size object does not define the DM frame size or
jnxSoamDmTestTlvIncluded is 'true' the value of this object is
ignored.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgTestTlvIncluded
1.3.6.1.4.1.2636.3.78.1.3.1.1.10
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: [Y.1731] 9.3
Indicates whether a Test TLV or Data TLV is included when the size of the DM frame is determined by the jnxSoamDmFrameSize object. A value of 'true' indicates that the Test TLV is to be included. A value of 'false' indicates that the Data TLV is to be included.
If the frame size object does not define the DM frame size the value of this object is ignored.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgTestTlvPattern
1.3.6.1.4.1.2636.3.78.1.3.1.1.11
JnxSoamTcTestPatternType1 = null2 = nullCrc323 = prbs4 = prbsCrc32This enumeration data type indicates the type of test pattern to be sent in an OAM PDU Test TLV. The valid enumerated values associated with this type are: null(1) Null signal without CRC-32 nullCrc32(2) Null signal with CRC-32 prbs(3) PRBS 2^31-1 without CRC-32 prbsCrc32(4) PRBS 2^31-1 with CRC-32Reference: [MEF7.1], Appendix III.2 Enumeration, [Y.1731] 7.7 · Integer32
This object specifies the type of test pattern to be sent in the DM frame Test TLV when the size of DM PDU is determined by the jnxSoamDmFrameSize object and jnxSoamDmTestTlvIncluded is 'true'. If the frame size object does not define the DM frame size or jnxSoamDmTestTlvIncluded is 'false' the value of this object is ignored.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgNumIntervalsStored
1.3.6.1.4.1.2636.3.78.1.3.1.1.12
Unsigned32 (1..1000)
Reference: [MEF SOAM-PM] R21, D8, D9
This object specifies the number of completed Measurement Intervals to store in the history statistic table.
At least 32 completed Measurement Intervals are to be stored. 96 Measurement Intervals are recommended to be stored.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgDestMepId
1.3.6.1.4.1.2636.3.78.1.3.1.1.13
Dot1agCfmMepIdOrZeroMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.
The special value 0 is allowed to indicate special cases, for example that no MEPID is configured.
Whenever an object is defined with this SYNTAX, then the DESCRIPTION clause of such an object MUST specify what the special value of 0 means.Reference: 19.2.1 (0 | 1..8191) · Unsigned32 · hint d
Reference: [MEF SOAM-PM] R55, R89
The Maintenance Association End Point Identifier of another MEP in the same Maintenance Association to which the SOAM DM frame is to be sent.
This address will be used if the value of the column jnxSoamDmDestIsMepId is 'true'. A value of zero means that the destination MEP ID has not been configured.
This object is only valid for the entity transmitting the Delay Measurement frames, types 'dmDmm' and 'dm1DmTx'. It is not applicable for the 'dm1DmRx' type.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgDestIsMepId
1.3.6.1.4.1.2636.3.78.1.3.1.1.14
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: [MEF SOAM-PM] R55, R89
A value of 'true' indicates that MEPID of the target MEP is used for SOAM DM frame transmission.
A value of 'false' indicates that the destination MAC address of the target MEP is used for SOAM DM frame transmission.
This object is only valid for the entity transmitting the Delay Measurement frames, types 'dmDmm' and 'dm1DmTx'. It is not applicable for the 'dm1DmRx type.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgStartTimeType
1.3.6.1.4.1.2636.3.78.1.3.1.1.15
JnxSoamTcOperationTimeType1 = none2 = immediate3 = relative4 = fixedThis enumeration data type indicates the operation type start or end time to indicate when an OAM operation is initiated or stopped. The valid enumerated values associated with this type are: none(1) The operation is never started or is stopped immediately if used to indicate a start time, or the operation never ends if it is used to indicate an end time immediate(2) The operation is to begin immediately relative(3) The operation is to begin at a relative time from the current time or stop a relative time after it has started fixed(4) The operation is to begin/stop at the given UTC time/dateReference: [SOAM-PM] R2, [SOAM-FM] 8.7 · Integer32
Reference: [MEF SOAM-PM] R3, R7, R8, D1
This object specifies the type of start time of the SOAM DM
session. The start time can be disabled (none), immediate, relative, or fixed.
The value of 'none' is illegal and a write error will be returned if this value is used.
The value of 'immediate' starts the SOAM DM session when the jnxSoamDmCfgEnabled is true.
The value of 'fixed' starts the SOAM DM session when the jnxSoamDmFixedStartDateAndTime is less than or equal to the current system date and time and jnxSoamDmCfgEnabled is true. This value is used to implement an On-Demand fixed time PM session.
The value of 'relative' starts the SOAM DM session when the current system date and time minus the jnxSoamDmRelativeStartTime is greater than or equal to the system date and time when the jnxSoamDmStartTimeType object was written and jnxSoamDmCfgEnabled is true. This value is used to implement an On-Demand relative time PM session.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgRepetitionTime
1.3.6.1.4.1.2636.3.78.1.3.1.1.16
Unsigned32 (0..31536000) · seconds
Reference: [MEF SOAM-PM] R18, D3, R19, R20
This object specifies a configurable repetition time between Measurement Intervals in a Delay Measurement session in seconds.
If the value is 0 (none), there is no time gap between the end of one Measurement Interval and the start of a new Measurement Interval. This is the normal usage case.
If the value is greater than one Measurement Interval there is time gap between the end of one Measurement Interval and the start of the next Measurement Interval. The repetition time specifies the time between the start of consecutive Measurement Intervals; hence the gap between the end of one Measurement Interval and the start of the next is equal to the difference between the repetition time and the measurement interval. During this gap, no SOAM PDUs are sent for this session and no measurements are made.
If the value is greater 0 but less than or equal to the measurement interval, an error is returned.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgAlignMeasurementIntervals
1.3.6.1.4.1.2636.3.78.1.3.1.1.17
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: [MEF SOAM-PM] D4, D5, D6
This object specifies whether the Measurement Intervals for the Delay Measurement session are aligned with a zero offset to real time.
The value 'true' indicates that each Measurement Interval starts at a time which is aligned to NE time source hour, if the repetition time (or the Measurement Interval, if the repetition time is 0) is a factor of an hour, i.e. 60min/15min = 4. For instance, a Measurement Interval/Repetition Time of 15 minutes would stop/start the Measurement Interval at 0, 15, 30, and 45 minutes of an hour. A Measurement Interval/Repetition Time of 7 minutes would not align to the hour since 7 minutes is NOT a factor of an hour, i.e. 60min/7min = 8.6. In this case the behavior is the same as if the object is set to 'false'.
The value 'false' indicates that the first Measurement Interval starts at an arbitrary time and each subsequent Measurement Interval starts at a time which is determined by jnxSoamLmCfgRepetitionTime.
This object can only be written at row creation time and cannot be modified once it has been created.
This object specifies the selection offset for Inter-Frame Delay Variation measurements. If this value is set to n, then the IFDV is calculated by taking the difference in frame delay between frame F and frame (F+n).
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgSessionType
1.3.6.1.4.1.2636.3.78.1.3.1.1.19
OCTET STRING SIZE (1..42)
Reference: [MEF SOAM-PM] R3
This object indicates whether the current session is defined to be 'Proactive' or 'On-Demand'. A value of 'proactive' indicates the current session is 'Proactive'. A value of 'onDemand' indicates the current session is 'On-Demand'.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgSessionStatus
1.3.6.1.4.1.2636.3.78.1.3.1.1.20
OCTET STRING SIZE (1..42)
This object indicates the current status of the DM session. A value of 'active' indicates the current DM session is active, i.e. the current time lies between the start time and the stop time, and jnxSoamDmCfgEnabled is true. A value of 'notActive' indicates the current DM session is not active, i.e. it has not started yet, has stopped upon reaching the stop time, or is disabled.
jnxSoamDmCfgHistoryClear
1.3.6.1.4.1.2636.3.78.1.3.1.1.21
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object when written clears the Delay Measurement history tables (jnxSoamDmHistoryStatsTable) - all rows are deleted. When read the value always returns 'false'.
Writing this value does not change the current stat table, nor any of the items in the configuration table.
Writing this object at row creation has no effect.
jnxSoamDmCfgRowStatus
1.3.6.1.4.1.2636.3.78.1.3.1.1.22
RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].)
The status column has six defined values:
- `active', which indicates that the conceptual row is available for use by the managed device;
- `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device;
- `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated);
- `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device;
- `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row.
Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management
protocol retrieval operation: `notReady', `notInService' or
`active'. That is, when queried, an existing conceptual row
has only three states: it is either available for use by
the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady').
NOTE WELL
This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'.
Also note that whenever any elements of a row exist, the RowStatus column must also exist.
To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram:
STATE +--------------+-----------+-------------+-------------
| A | B | C | D
| |status col.|status column|
|status column | is | is |status column
ACTION |does not exist| notReady | notInService| is active
--------------+--------------+-----------+-------------+-------------
set status |noError ->D|inconsist- |inconsistent-|inconsistent-
column to | or | entValue| Value| Value
createAndGo |inconsistent- | | |
| Value| | |
--------------+--------------+-----------+-------------+-------------
set status |noError see 1|inconsist- |inconsistent-|inconsistent-
column to | or | entValue| Value| Value
createAndWait |wrongValue | | |
--------------+--------------+-----------+-------------+-------------
set status |inconsistent- |inconsist- |noError |noError
column to | Value| entValue| |
active | | | |
| | or | |
| | | |
| |see 2 ->D|see 8 ->D| ->D
--------------+--------------+-----------+-------------+-------------
set status |inconsistent- |inconsist- |noError |noError ->C
column to | Value| entValue| |
notInService | | | |
| | or | | or
| | | |
| |see 3 ->C| ->C|see 6
--------------+--------------+-----------+-------------+-------------
set status |noError |noError |noError |noError ->A
column to | | | | or
destroy | ->A| ->A| ->A|see 7
--------------+--------------+-----------+-------------+-------------
set any other |see 4 |noError |noError |see 5
column to some| | | |
value | | see 1| ->C| ->D
--------------+--------------+-----------+-------------+-------------
(1) goto B or C, depending on information available to the agent.
(2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D.
(3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C.
(4) at the discretion of the agent, the return value may be either:
inconsistentName: because the agent does not choose to
create such an instance when the corresponding RowStatus instance does not exist, or
inconsistentValue: if the supplied value is
inconsistent with the state of some other MIB object's value, or
noError: because the agent chooses to create the instance.
If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A.
(5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned.
(6) the return value can indicate one of the following errors:
wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or
inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated.
(7) the return value can indicate the following error:
inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated.
(8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue.
NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc.
Conceptual Row Creation
There are four potential interactions when creating a
conceptual row: selecting an instance-identifier which is
not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device.
Interaction 1: Selecting an Instance-Identifier
The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics.
In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.)
Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different.
Finally, the management station could select a pseudo-random number to use as the index. In the event that this index
was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation.
A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used.
Interaction 2: Creating the Conceptual Row
Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions.
Interaction 2a: Creating and Activating the Conceptual Row
The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes:
- a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1.
- the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created.
- the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column.
Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'.
When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information
available to the agent is provided by two sources: the
management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row.
NOTE WELL
Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm.
Interaction 2b: Negotiating the Creation of the Conceptual Row
The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the
columns indicated by its column requirements.) Otherwise,
the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3.
Interaction 3: Initializing non-defaulted Objects
The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes:
- a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column.
- the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column.
- the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column.
If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4.
Interaction 4: Making the Conceptual Row Available
Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'.
NOTE WELL
A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device.
If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row.
Conceptual Row Suspension
When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified).
Conceptual Row Deletion
For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady',
`notInService' or `active'.) If the operation succeeds,
then all instances associated with the conceptual row are immediately removed. · Integer32
The status of the row.
The writable columns in a row cannot be changed if the row is active, except for jnxSoamDmCfgEnabled and jnxSoamDmCfgHistoryClear objects. All columns are to have a valid value before a row can be activated.
jnxSoamDmCfgMeasurementInterval
1.3.6.1.4.1.2636.3.78.1.3.1.1.23
Unsigned32 (1..1440) · minutes
Reference: [MEF SOAM-PM] R16, R17
This object specifies a Measurement Interval in minutes.
A Measurement Interval 15 minutes needs to be supported, other intervals may be supported.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgDestMacAddress
1.3.6.1.4.1.2636.3.78.1.3.1.1.24
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
Reference: [MEF SOAM-PM] R55, R89
The Target or Destination MAC Address Field to be transmitted.
If mefSoamDmCfgType is 'dmDmm', the destination address is to be the unicast address of the destination MEP. An error is returned if this object is set to a multicast address.
If mefSoamDmCfgType is 'dm1DmTx', the destination address is normally the unicast address of the destination MEP, but can be a multicast address indicating the level of the MEG: 01-80-c2-00-00-3y, where y is the level of the MEG. An error is returned if this object is set to any other multicast address.
If mefSoamDmCfgType is 'dm1DmRx', this object is ignored.
This address will be used if the value of the object mefSoamDmDestIsMepId is 'false'.
This object is only valid for the entity transmitting the SOAM DM frames and is ignored by the entity receiving SOAM DM frames.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgSourceMacAddress
1.3.6.1.4.1.2636.3.78.1.3.1.1.25
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
Reference: [MEF SOAM-PM] R55, R89
The Source MAC Address Field of the received SOAM DM session PDUs.
If mefSoamDmCfgType is dm1DmRx this object indicates the source address of the dm1DmTx DM session.
This object is only valid for mefSoamDmCfgType set to dm1DmRx. It is ignored for mefSoamDmCfgType set to dmDmm or dm1DmTx.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgFixedStartDateAndTime
1.3.6.1.4.1.2636.3.78.1.3.1.1.26
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Reference: [MEF SOAM-PM] R9
This object specifies the fixed start date/time for the SOAM Delay Measurement session. This object is used only used if mefSoamDmStartTimeType is 'fixed' and is ignored otherwise.
The default value is year 0000, month 01, day 01, time 00:00:00.00.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgRelativeStartTime
1.3.6.1.4.1.2636.3.78.1.3.1.1.27
TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32
Reference: [MEF SOAM-PM] R9
This object specifies the relative start time, from the current system time, for the SOAM DM session. This object is used only if mefSoamDmStartTimeType is 'relative' and is ignored otherwise.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgStopTimeType
1.3.6.1.4.1.2636.3.78.1.3.1.1.28
JnxSoamTcOperationTimeType1 = none2 = immediate3 = relative4 = fixedThis enumeration data type indicates the operation type start or end time to indicate when an OAM operation is initiated or stopped. The valid enumerated values associated with this type are: none(1) The operation is never started or is stopped immediately if used to indicate a start time, or the operation never ends if it is used to indicate an end time immediate(2) The operation is to begin immediately relative(3) The operation is to begin at a relative time from the current time or stop a relative time after it has started fixed(4) The operation is to begin/stop at the given UTC time/dateReference: [SOAM-PM] R2, [SOAM-FM] 8.7 · Integer32
Reference: [MEF SOAM-PM] R3, R10, D2
This object specifies the type of stop time to terminate the SOAM DM session. The stop time can be forever (none), relative, or fixed.
The value of 'none' indicates that the SOAM DM session never ends once it has started unless the session is disabled.
The value of 'immediate' is illegal and a write error will be returned if this value is used.
The value of 'fixed' stops the SOAM DM session when the mefSoamDmFixedStopDateAndTime is less than or equal to the current system date. This value is used to implement an On-Demand fixed time PM session.
The value of 'relative' stops the SOAM DM session when the time indicated by mefSoamDmRelativeStopTime has passed since the session start time as determined by the mefSoamDmCfgStartTimeType, mefSoamDmCfgFixedStartDateAndTime and mefSoamDmCfgRelativeStartTime objects. This value is used to implement an On-Demand relative time PM session.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgFixedStopDateAndTime
1.3.6.1.4.1.2636.3.78.1.3.1.1.29
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Reference: [MEF SOAM-PM] R10, R13
This object specifies the fixed stop date/time for the SOAM Delay Measurement session. This object is used only used if mefSoamDmStopTimeType is 'fixed' and is ignored otherwise.
The default value is year 0000, month 01, day 01, time 00:00:00.00.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgRelativeStopTime
1.3.6.1.4.1.2636.3.78.1.3.1.1.30
TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32
Reference: [MEF SOAM-PM] R11
This object specifies the relative stop time, from the session start time, to stop the SOAM DM session. This object is used only if mefSoamDmStopTimeType is 'relative' and is otherwise.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgAlignMeasurementOffset
1.3.6.1.4.1.2636.3.78.1.3.1.1.31
Unsigned32 (0..525600) · minutes
Reference: [MEF SOAM-PM] D7
This object specifies the offset in minutes from the time of day value if mefSoamDmCfgAlignMeasurementIntervals is 'true' and the repetition time is a factor of 60 minutes. If not, the value of this object is ignored.
If the Measurement Interval is 15 minutes and mefSoamDmCfgAlignMeasurementIntervals is true and if this object was set to 5 minutes, the Measurement Intervals would start at 5, 20, 35, 50 minutes past each hour.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgNumMeasBinsPerFrameDelayInterval
1.3.6.1.4.1.2636.3.78.1.3.1.1.32
Unsigned32 (2..100)
Reference: [MEF SOAM-PM] R27, D11, R28, D12
This object specifies the number of measurement bins per Measurement Interval for Frame Delay measurements.
At least 3 bins are to be supported; at least 10 bins are recommended to be supported.
This object can only be written at row creation time and cannot be modified once it has been created.
This object specifies the number of measurement bins per Measurement Interval for Inter-Frame Delay Variation measurements.
The minimum number of measurement bins to be supported is 2. The supported is 10.
This object can only be written at row creation time and cannot be modified once it has been created.
jnxSoamDmCfgNumMeasBinsPerFrameDelayRangeInterval
1.3.6.1.4.1.2636.3.78.1.3.1.1.34
Unsigned32 (2..100)
Reference: [MEF SOAM-PM] R31, D15, R32, D16
This object specifies the number of measurement bins per Measurement Interval for Frame Delay Range measurements.
At least 2 bins are to be supported; at least 10 bins are recommended to be supported.
This object can only be written at row creation time and cannot be modified once it has been created.
This object contains the last measured results for a SOAM Delay Measurement session.
Each row in the table represents a Delay Measurement session for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific DM session on the selected MEP.
Instances of this managed object are created automatically by the SNMP Agent when the Delay Measurement session is running.
Each object in this table applies only if the corresponding bit is set in jnxSoamDmCfgMeasurementEnable.
The objects in this table do not need to be persistent upon reboot or restart of a device.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamDmMeasuredStatsFrameDelayTwoWay
1.3.6.1.4.1.2636.3.78.1.3.2.1.1
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the two-way frame delay calculated by this MEP from the last received SOAM PDU.
This object is undefined is jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmMeasuredStatsFrameDelayForward
1.3.6.1.4.1.2636.3.78.1.3.2.1.2
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the frame delay in the forward direction calculated by this MEP from the last received SOAM PDU. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization.
This object is undefined is jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmMeasuredStatsFrameDelayBackward
1.3.6.1.4.1.2636.3.78.1.3.2.1.3
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the frame delay in the backward direction calculated by this MEP from the last received SOAM PDU. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization.
This object is undefined is jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmMeasuredStatsIfdvTwoWay
1.3.6.1.4.1.2636.3.78.1.3.2.1.4
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the last two-way inter-frame delay interval calculated by this MEP.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmMeasuredStatsIfdvForward
1.3.6.1.4.1.2636.3.78.1.3.2.1.5
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the last one-way inter-frame delay interval in the forward direction calculated by this MEP.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmMeasuredStatsIfdvBackward
1.3.6.1.4.1.2636.3.78.1.3.2.1.6
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the last one-way inter-frame delay interval in the backward direction calculated by this MEP.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
This table contains the results for the current Measurement Interval in a SOAM Delay Measurement session gathered during the interval indicated by iterator count.
A row in this table is created automatically by the SNMP Agent when the Delay Measurement session is configured.
Each row in the table represents the current statistics for a Delay Measurement session for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific DM session on the selected MEP. There can be more than one DM session per MEP.
The objects in this table apply regardless of the value of jnxSoamDmCfgType unless otherwise specified in the object description. Backward and two-way statistic objects are undefined if jnxSoamDmCfgType is dm1DmRx.
Except for jnxSoamDmCurrentStatsIndex, jnxSoamDmCurrentStatsStartTime jnxSoamDmCurrentStatsElapsedTime and jnxSoamDmCurrentStatsSuspect, each object in this table applies only if the corresponding bit is set in jnxSoamDmCfgMeasurementEnable.
The objects in this table do not need to be persistent upon reboot or restart of a device.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamDmCurrentStatsIndex
1.3.6.1.4.1.2636.3.78.1.3.3.1.1
Unsigned32
The index for the current Measurement Interval for this PM session. This value will become the value for jnxSoamDmHistoryStatsIndex once the Measurement Interval is completed.
Measurement Interval indexes are assigned sequentially by the SNMP Agent. The first Measurement Interval that occurs after the session is started is assigned index 1.
jnxSoamDmCurrentStatsStartTime
1.3.6.1.4.1.2636.3.78.1.3.3.1.2
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Reference: [MEF SOAM-PM] R22, R66, R100
The time that the current Measurement Interval started.
jnxSoamDmCurrentStatsElapsedTime
1.3.6.1.4.1.2636.3.78.1.3.3.1.3
TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32
Reference: [MEF SOAM-PM] R24, R66, R100
The time that the current Measurement Interval has been running, in 0.01 seconds.
jnxSoamDmCurrentStatsSuspect
1.3.6.1.4.1.2636.3.78.1.3.3.1.4
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: [MEF SOAM-PM] R39, R40, R41
Whether the Measurement Interval has been marked as suspect.
The object is to be set to false at the start of a measurement interval. It is set to true when there is a discontinuity in the performance measurements during the Measurement Interval. Conditions for a discontinuity include, but are not limited to the following:
1 - The local time-of-day clock is adjusted by at least 10 seconds 2 - The conducting of a performance measurement is halted before the current Measurement Interval is completed 3 - A local test, failure, or reconfiguration that disrupts service
jnxSoamDmCurrentStatsFrameDelayTwoWayMin
1.3.6.1.4.1.2636.3.78.1.3.3.1.5
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the minimum two-way frame delay calculated by this MEP for this Measurement Interval.
This object is undefined is jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsFrameDelayTwoWayMax
1.3.6.1.4.1.2636.3.78.1.3.3.1.6
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the maximum two-way frame delay calculated by this MEP for this Measurement Interval.
This object is undefined is jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsFrameDelayTwoWayAvg
1.3.6.1.4.1.2636.3.78.1.3.3.1.7
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the average two-way frame delay calculated by this MEP for this Measurement Interval.
This object is undefined is jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsFrameDelayForwardMin
1.3.6.1.4.1.2636.3.78.1.3.3.1.8
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R67, R101
This object contains the minimum one-way frame delay in the forward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization.
This object is undefined is jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmCurrentStatsFrameDelayForwardMax
1.3.6.1.4.1.2636.3.78.1.3.3.1.9
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R67, R101
This object contains the maximum one-way frame delay in the forward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization.
This object is undefined is jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmCurrentStatsFrameDelayForwardAvg
1.3.6.1.4.1.2636.3.78.1.3.3.1.10
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R67, R101
This object contains the average one-way frame delay in the forward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization.
This object is undefined is jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmCurrentStatsFrameDelayBackwardMin
1.3.6.1.4.1.2636.3.78.1.3.3.1.11
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R67
This object contains the minimum one-way frame delay in the backward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization.
This object is undefined is jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsFrameDelayBackwardMax
1.3.6.1.4.1.2636.3.78.1.3.3.1.12
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R67
This object contains the maximum one-way frame delay in the backward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization.
This object is undefined is jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsFrameDelayBackwardAvg
1.3.6.1.4.1.2636.3.78.1.3.3.1.13
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R67
This object contains the average one-way frame delay in the backward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization.
This object is undefined is jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsIfdvForwardMin
1.3.6.1.4.1.2636.3.78.1.3.3.1.14
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66, R100
This object contains the minimum one-way inter-frame delay interval in the forward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmCurrentStatsIfdvForwardMax
1.3.6.1.4.1.2636.3.78.1.3.3.1.15
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66, R100
This object contains the maximum one-way inter-frame delay interval in the forward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmCurrentStatsIfdvForwardAvg
1.3.6.1.4.1.2636.3.78.1.3.3.1.16
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66, R100
This object contains the average one-way inter-frame delay interval in the forward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmCurrentStatsIfdvBackwardMin
1.3.6.1.4.1.2636.3.78.1.3.3.1.17
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the minimum one-way inter-frame delay interval in the backward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsIfdvBackwardMax
1.3.6.1.4.1.2636.3.78.1.3.3.1.18
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the maximum one-way inter-frame delay interval in the backward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsIfdvBackwardAvg
1.3.6.1.4.1.2636.3.78.1.3.3.1.19
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the average one-way inter-frame delay interval in the backward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsIfdvTwoWayMin
1.3.6.1.4.1.2636.3.78.1.3.3.1.20
Unsigned32 · microseconds
This object contains the minimum two-way inter-frame delay interval calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType
is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsIfdvTwoWayMax
1.3.6.1.4.1.2636.3.78.1.3.3.1.21
Unsigned32 · microseconds
This object contains the maximum two-way inter-frame delay interval calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsIfdvTwoWayAvg
1.3.6.1.4.1.2636.3.78.1.3.3.1.22
Unsigned32 · microseconds
This object contains the average two-way inter-frame delay interval calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsSoamPdusSent
1.3.6.1.4.1.2636.3.78.1.3.3.1.23
Gauge32
Reference: [MEF SOAM-PM] R66, R100
This object contains the count of the number of SOAM PDUs sent
during this Measurement Interval.
This object applies when jnxSoamDmCfgType is dmDmm or dm1DmTx and
is undefined if jnxSoamDmCfgType is dm1DmRx. It indicates the
number of DMM or 1DM SOAM frames transmitted.
jnxSoamDmCurrentStatsSoamPdusReceived
1.3.6.1.4.1.2636.3.78.1.3.3.1.24
Gauge32
Reference: [MEF SOAM-PM] R66, R100
This object contains the count of the number of SOAM PDUs received in this Measurement Interval.
This object indicates the number of DMR and 1DM SOAM frames
received. This object applies when jnxSoamDmCfgTypeis dmDmm or
dm1DmRx and is undefined if jnxSoamDmCfgTypeis dm1DmTx.
jnxSoamDmCurrentStatsFrameDelayRangeForwardMax
1.3.6.1.4.1.2636.3.78.1.3.3.1.25
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66, R100
This object contains the maximum one-way frame delay range in the forward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmCurrentStatsFrameDelayRangeForwardAvg
1.3.6.1.4.1.2636.3.78.1.3.3.1.26
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66, R100
This object contains the average one-way frame delay range in the forward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmCurrentStatsFrameDelayRangeBackwardMax
1.3.6.1.4.1.2636.3.78.1.3.3.1.27
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the maximum one-way frame delay range in the backward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsFrameDelayRangeBackwardAvg
1.3.6.1.4.1.2636.3.78.1.3.3.1.28
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the average one-way frame delay range in the backward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsFrameDelayRangeTwoWayMax
1.3.6.1.4.1.2636.3.78.1.3.3.1.29
Unsigned32 · microseconds
This object contains the maximum two-way frame delay range calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmCurrentStatsFrameDelayRangeTwoWayAvg
1.3.6.1.4.1.2636.3.78.1.3.3.1.30
Unsigned32 · microseconds
This object contains the average two-way frame delay range calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
This table contains the results for history Measurement Intervals in a SOAM Delay Measurement session.
Rows of this table are created automatically by the SNMP Agent when the Delay Measurement session is running and a Measurement Interval is completed.
Each row in the table represents the Measurement Interval history statistics for a Delay Measurement session for the defined MEP. This table uses five indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific DM session on the selected MEP. The fifth index is the Measurement Interval.
At least 32 completed Measurement Intervals are to be supported. 96 completed Measurement Intervals are recommended to be supported. If there are at least 32 rows in the table and a new Measurement Interval completes and a new row is to be added to the table, the oldest completed Measurement Interval can be deleted (row deletion). If the measurement interval is other than 15 minutes then a minimum of 8 hours of completed Measurement Intervals are to be supported and 24 hours are recommended to be supported.
The objects in this table apply regardless of the value of jnxSoamDmCfgType unless otherwise specified in the object description. Backward and two-way statistic objects are undefined if jnxSoamDmCfgType is dm1DmRx.
Except for jnxSoamDmHistoryStatsIndex, jnxSoamDmHistoryStatsEndTime, jnxSoamDmHistoryStatsElapsedTime and jnxSoamDmHistoryStatsSuspect, each object in this table applies only if the corresponding bit is set in jnxSoamDmCfgMeasurementEnable.
The rows and objects in this table are to be persistent upon reboot or restart of a device.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamDmHistoryStatsIndex
1.3.6.1.4.1.2636.3.78.1.3.4.1.1
Unsigned32
The index for the Measurement Interval within this PM session.
Measurement Interval indexes are assigned sequentially by the SNMP Agent. The first Measurement Interval that occurs after the session is started is assigned index 1.
Referential integrity is necessary, i.e., the index needs to be persistent upon a reboot or restart of a device. The index is never reused while this session is active until it wraps to zero. The index value keeps increasing up to that time.
jnxSoamDmHistoryStatsEndTime
1.3.6.1.4.1.2636.3.78.1.3.4.1.2
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Reference: [MEF SOAM-PM] R23, R66, R100
The time that the Measurement Interval ended.
jnxSoamDmHistoryStatsElapsedTime
1.3.6.1.4.1.2636.3.78.1.3.4.1.3
TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32
Reference: [MEF SOAM-PM] R66, R100
The length of time that the Measurement Interval ran for, in 0.01 seconds.
jnxSoamDmHistoryStatsSuspect
1.3.6.1.4.1.2636.3.78.1.3.4.1.4
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: [MEF SOAM-PM] R39, R40, R41, R42
Whether the Measurement Interval has been marked as suspect.
The object is set to true when there is a discontinuity in the performance measurements during the Measurement Interval. Conditions for a discontinuity include, but are not limited to the following:
1 - The local time-of-day clock is adjusted by at least 10 seconds 2 - The conducting of a performance measurement is halted before the current Measurement Interval is completed 3 - A local test, failure, or reconfiguration that disrupts service
jnxSoamDmHistoryStatsFrameDelayTwoWayMin
1.3.6.1.4.1.2636.3.78.1.3.4.1.5
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the minimum two-way frame delay calculated by this MEP for this Measurement Interval.
This object is undefined is jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsFrameDelayTwoWayMax
1.3.6.1.4.1.2636.3.78.1.3.4.1.6
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the maximum two-way frame delay calculated by this MEP for this Measurement Interval.
This object is undefined is jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsFrameDelayTwoWayAvg
1.3.6.1.4.1.2636.3.78.1.3.4.1.7
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the average two-way frame delay calculated by this MEP for this Measurement Interval.
This object is undefined is jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsFrameDelayForwardMin
1.3.6.1.4.1.2636.3.78.1.3.4.1.8
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66, R100
This object contains the minimum one-way frame delay in the forward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization.
This object is undefined is jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmHistoryStatsFrameDelayForwardMax
1.3.6.1.4.1.2636.3.78.1.3.4.1.9
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66, R100
This object contains the maximum one-way frame delay in the forward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization.
This object is undefined is jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmHistoryStatsFrameDelayForwardAvg
1.3.6.1.4.1.2636.3.78.1.3.4.1.10
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66, R100
This object contains the average one-way frame delay in the forward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization.
This object is undefined is jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmHistoryStatsFrameDelayBackwardMin
1.3.6.1.4.1.2636.3.78.1.3.4.1.11
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the minimum one-way frame delay in the backward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization.
This object is undefined is jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsFrameDelayBackwardMax
1.3.6.1.4.1.2636.3.78.1.3.4.1.12
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the maximum one-way frame delay in the backward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization.
This object is undefined is jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsFrameDelayBackwardAvg
1.3.6.1.4.1.2636.3.78.1.3.4.1.13
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the average one-way frame delay in the backward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization.
This object is undefined is jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsIfdvForwardMin
1.3.6.1.4.1.2636.3.78.1.3.4.1.14
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66, R100
This object contains the minimum one-way inter-frame delay interval in the forward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmHistoryStatsIfdvForwardMax
1.3.6.1.4.1.2636.3.78.1.3.4.1.15
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66, R100
This object contains the maximum one-way inter-frame delay interval in the forward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmHistoryStatsIfdvForwardAvg
1.3.6.1.4.1.2636.3.78.1.3.4.1.16
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66, R100
This object contains the average one-way inter-frame delay interval in the forward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmHistoryStatsIfdvBackwardMin
1.3.6.1.4.1.2636.3.78.1.3.4.1.17
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the minimum one-way inter-frame delay interval in the backward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsIfdvBackwardMax
1.3.6.1.4.1.2636.3.78.1.3.4.1.18
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the maximum one-way inter-frame delay interval in the backward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsIfdvBackwardAvg
1.3.6.1.4.1.2636.3.78.1.3.4.1.19
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the average one-way inter-frame delay interval in the backward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsIfdvTwoWayMin
1.3.6.1.4.1.2636.3.78.1.3.4.1.20
Unsigned32 · microseconds
This object contains the minimum two-way inter-frame delay interval calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsIfdvTwoWayMax
1.3.6.1.4.1.2636.3.78.1.3.4.1.21
Unsigned32 · microseconds
This object contains the maximum two-way inter-frame delay interval calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsIfdvTwoWayAvg
1.3.6.1.4.1.2636.3.78.1.3.4.1.22
Unsigned32 · microseconds
This object contains the average two-way inter-frame delay interval calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsSoamPdusSent
1.3.6.1.4.1.2636.3.78.1.3.4.1.23
Gauge32
Reference: [MEF SOAM-PM] R66, R100
This object contains the count of the number of SOAM PDUs sent during this Measurement Interval.
This object applies when jnxSoamDmCfgType is dmDmm or dm1DmTx and
is undefined if jnxSoamDmCfgType is dm1DmRx. It indicates the
number of DMM or 1DM SOAM frames transmitted.
jnxSoamDmHistoryStatsSoamPdusReceived
1.3.6.1.4.1.2636.3.78.1.3.4.1.24
Gauge32
Reference: [MEF SOAM-PM] R66, R100
This object contains the count of the number of SOAM PDUs received in this Measurement Interval.
This object indicates the number of DMR and 1DM SOAM frames
received. This object applies when jnxSoamDmCfgType is dmDmm or
dm1DmRx and is undefined if jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmHistoryStatsFrameDelayRangeForwardMax
1.3.6.1.4.1.2636.3.78.1.3.4.1.25
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66, R100
This object contains the maximum one-way Frame Delay Range in the forward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmHistoryStatsFrameDelayRangeForwardAvg
1.3.6.1.4.1.2636.3.78.1.3.4.1.26
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66, R100
This object contains the average one-way Frame Delay Range in the forward direction calculated by this MEP for this Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx.
jnxSoamDmHistoryStatsFrameDelayRangeBackwardMax
1.3.6.1.4.1.2636.3.78.1.3.4.1.27
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the maximum one-way Frame Delay Range in the backward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsFrameDelayRangeBackwardAvg
1.3.6.1.4.1.2636.3.78.1.3.4.1.28
Unsigned32 · microseconds
Reference: [MEF SOAM-PM] R66
This object contains the average one-way Frame Delay Range in the backward direction calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsFrameDelayRangeTwoWayMax
1.3.6.1.4.1.2636.3.78.1.3.4.1.29
Unsigned32 · microseconds
This object contains the maximum two-way Frame Delay Range calculated by this MEP for this Measurement Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
jnxSoamDmHistoryStatsFrameDelayRangeTwoWayAvg
1.3.6.1.4.1.2636.3.78.1.3.4.1.30
Unsigned32 · microseconds
This object contains the average two-way Frame Delay Range Interval.
The value of this object is undefined when jnxSoamDmCfgType is dm1DmTx or dm1DmRx.
This table contains the list of Delay Measurement threshold configuration values for DM Performance Monitoring.
The main purpose of the threshold configuration table is to configure threshold alarm notifications indicating that a specific performance metric is not being met.
Each row in the table represents a Delay Measurement session threshold set for the defined MEP. This table uses five indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific DM session on the selected MEP. The fifth index is the specific threshold set number.
Rows in this table are not created automatically. A row is created in this table to set up a threshold set on a configured MEP that has a configured DM session.
An NE needs to support at least one threshold set for NE SOAM PM compliance. A second threshold set on the NE is desirable. More than two threshold sets on the NE can be configured if supported on the NE.
All the objects in the row have a default value that disables the particular threshold measurement. In order to enable a threshold measurement the particular bit in the jnxSoamDmThresholdCfgEnable object is to be set to '1' and the selected threshold measurement is to have a threshold value configured. Non-configured threshold measurements are disabled by default.
The writable objects in this table need to be persistent upon reboot or restart of a device.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamDmThresholdCfgIndex
1.3.6.1.4.1.2636.3.78.1.3.5.1.1
Unsigned32
The index of the threshold number for the specific DM threshold entry.
An index value of '1' is to be supported. Other index values can be supported.
jnxSoamDmThresholdCfgEnable
1.3.6.1.4.1.2636.3.78.1.3.5.1.2
BITS
A vector of bits that indicates the type of SOAM DM threshold notifications that are enabled.
A bit set to '1' enables the specific SOAM DM threshold notification and when the specific counter is enabled and the threshold is crossed a notification is generated.
A bit set to '0' disables the specific SOAM DM threshold notification.
If a particular SOAM DM threshold is not supported the BIT value is set to '0'.
bJnxSoamDmMeasuredFrameDelayTwoWayThreshold(0) Enables/disables measured frame two-way delay threshold notification. The notification is sent immediately when the jnxSoamDmMeasuredStatsFrameDelayTwoWay value is greater than or equal to threshold value. bJnxSoamDmMaxFrameDelayTwoWayThreshold(1) Enables/disables maximum frame two-way delay threshold notification. The notification is sent immediately when the jnxSoamDmCurrentStatsFrameDelayTwoWayMax value is greater than or equal to threshold value in a Measurement Interval. bJnxSoamDmAvgFrameDelayTwoWayThreshold(2) Enables/disables average frame two-way delay threshold notification. The notification is sent when at the end of a Measurement Interval if the jnxSoamDmCurrentStatsFrameDelayTwoWayAvg value is greater than or equal to the threshold value. bJnxSoamDmMeasuredIfdvTwoWayThreshold(3) Enables/disables measured frame IFDV two-way threshold notification. The notification is sent immediately when the jnxSoamDmMeasuredStatsIfdvTwoWay value is greater than or equal to threshold value. bJnxSoamDmMaxIfdvTwoWayThreshold(4) Enables/disables maximum frame IFDV two-way threshold notification. The notification is sent immediately when the jnxSoamDmCurrentStatsIfdvTwoWayMax value is greater than or equal to threshold value in a Measurement Interval. bJnxSoamDmAvgIfdvTwoWayThreshold(5) Enables/disables average frame IFDV two-way threshold notification. The notification is sent when at the end of a Measurement Interval if the jnxSoamDmCurrentStatsIfdvTwoWayAvg value is greater than or equal to the threshold value. bJnxSoamDmMaxFrameDelayRangeTwoWayThreshold(6) Enables/disables maximum Frame Delay Range two-way threshold notification. The notification is sent immediately when the jnxSoamDmCurrentStatsFrameDelayRangeTwoWayMax value is greater than or equal to threshold value in a Measurement Interval. bJnxSoamDmAvgFrameDelayRangeTwoWayThreshold(7) Enables/disables average Frame Delay Range two-way threshold notification. The notification is sent when at the end of a Measurement Interval if the jnxSoamDmCurrentStatsFrameDelayRangeTwoWayAvg value is greater than or equal to the threshold value. bJnxSoamDmMeasuredFrameDelayForwardThreshold(8) Enables/disables measured forward frame delay threshold notification. The notification is sent immediately when the jnxSoamDmMeasuredStatsFrameDelayForward value is greater than or equal to threshold value. bJnxSoamDmMaxFrameDelayForwardThreshold(9) Enables/disables maximum forward frame delay threshold notification. The notification is sent immediately when the jnxSoamDmCurrentStatsFrameDelayForwardMax value is greater than or equal to threshold value in a Measurement Interval. bJnxSoamDmAvgFrameDelayForwardThreshold(10) Enables/disables average forward frame delay threshold notification. The notification is sent when at the end of a Measurement Interval if the jnxSoamDmCurrentStatsFrameDelayForwardAvg value is greater than or equal to the threshold value. bJnxSoamDmMeasuredIfdvForwardThreshold(11) Enables/disables measured frame IFDV forward threshold notification. The notification is sent immediately when the jnxSoamDmMeasuredStatsIfdvForward value is greater than or equal to threshold value. bJnxSoamDmMaxIfdvForwardThreshold(12) Enables/disables maximum frame IFDV forward threshold notification. The notification is sent immediately when the jnxSoamDmCurrentStatsIfdvForwardMax value is greater than or equal to threshold value in a Measurement Interval. bJnxSoamDmAvgIfdvForwardThreshold(13) Enables/disables average frame IFDV forward threshold notification. The notification is sent when at the end of a Measurement Interval if the jnxSoamDmCurrentStatsIfdvForwardAvg value is greater than or equal to the threshold value. bJnxSoamDmMaxFrameDelayRangeForwardThreshold(14) Enables/disables maximum Frame Delay Range forward threshold notification. The notification is sent immediately when the jnxSoamDmCurrentStatsFrameDelayRangeForwardMax value is greater than or equal to threshold value in a Measurement Interval. bJnxSoamDmAvgFrameDelayRangeForwardThreshold(15) Enables/disables average Frame Delay Range forward threshold notification. The notification is sent when at the end of a Measurement Interval if the jnxSoamDmCurrentStatsFrameDelayRangeForwardAvg value is greater than or equal to the threshold value. bJnxSoamDmMeasuredFrameDelayBackwardThreshold(16) Enables/disables measured backward frame delay threshold notification. The notification is sent immediately when the jnxSoamDmMeasuredStatsFrameDelayBackward value is greater than or equal to threshold value. bJnxSoamDmMaxFrameDelayBackwardThreshold(17) Enables/disables maximum backward frame delay threshold notification. The notification is sent immediately when the jnxSoamDmCurrentStatsFrameDelayBackwardMax value is greater than or equal to threshold value in a Measurement Interval. bJnxSoamDmAvgFrameDelayBackwardThreshold(18) Enables/disables average backward frame delay threshold notification. The notification is sent when at the end of a Measurement Interval if the jnxSoamDmCurrentStatsFrameDelayBackwardAvg value is greater than or equal to the threshold value. bJnxSoamDmMeasuredIfdvBackwardThreshold(19) Enables/disables measured frame IFDV backward threshold notification. The notification is sent immediately when the jnxSoamDmMeasuredStatsIfdvBackward value is greater than or equal to threshold value. bJnxSoamDmMaxIfdvBackwardThreshold(20) Enables/disables maximum frame IFDV backward threshold notification. The notification is sent immediately when the jnxSoamDmCurrentStatsIfdvBackwardMax value is greater than or equal to threshold value in a Measurement Interval. bJnxSoamDmAvgIfdvBackwardThreshold(21) Enables/disables average frame IFDV backward threshold notification. The notification is sent when at the end of a Measurement Interval if the jnxSoamDmCurrentStatsIfdvBackwardAvg value is greater than or equal to the threshold value. bJnxSoamDmMaxFrameDelayRangeBackwardThreshold(22) Enables/disables maximum Frame Delay Range backward threshold notification. The notification is sent immediately when the jnxSoamDmCurrentStatsFrameDelayRangeBackwardMax value is greater than or equal to threshold value in a Measurement Interval. bJnxSoamDmAvgFrameDelayRangeBackwardThreshold(23) Enables/disables average Frame Delay Range backward threshold notification. The notification is sent when at the end of a Measurement Interval if the jnxSoamDmCurrentStatsFrameDelayRangeBackwardAvg value is greater than or equal to the threshold value.
jnxSoamDmThresholdCfgAvgFrameDelayTwoWayThreshold
1.3.6.1.4.1.2636.3.78.1.3.5.1.3
Unsigned32 · microseconds
This object is used to set the average two-way delay threshold value that will be used to determine if a threshold notification is generated.
jnxSoamDmThresholdCfgAvgIfdvTwoWayThreshold
1.3.6.1.4.1.2636.3.78.1.3.5.1.4
Unsigned32 · microseconds
This object is used to set the average two-way IFDV threshold value that will be used to determine if a threshold notification is generated.
jnxSoamDmThresholdCfgRowStatus
1.3.6.1.4.1.2636.3.78.1.3.5.1.5
RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].)
The status column has six defined values:
- `active', which indicates that the conceptual row is available for use by the managed device;
- `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device;
- `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated);
- `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device;
- `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row.
Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management
protocol retrieval operation: `notReady', `notInService' or
`active'. That is, when queried, an existing conceptual row
has only three states: it is either available for use by
the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady').
NOTE WELL
This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'.
Also note that whenever any elements of a row exist, the RowStatus column must also exist.
To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram:
STATE +--------------+-----------+-------------+-------------
| A | B | C | D
| |status col.|status column|
|status column | is | is |status column
ACTION |does not exist| notReady | notInService| is active
--------------+--------------+-----------+-------------+-------------
set status |noError ->D|inconsist- |inconsistent-|inconsistent-
column to | or | entValue| Value| Value
createAndGo |inconsistent- | | |
| Value| | |
--------------+--------------+-----------+-------------+-------------
set status |noError see 1|inconsist- |inconsistent-|inconsistent-
column to | or | entValue| Value| Value
createAndWait |wrongValue | | |
--------------+--------------+-----------+-------------+-------------
set status |inconsistent- |inconsist- |noError |noError
column to | Value| entValue| |
active | | | |
| | or | |
| | | |
| |see 2 ->D|see 8 ->D| ->D
--------------+--------------+-----------+-------------+-------------
set status |inconsistent- |inconsist- |noError |noError ->C
column to | Value| entValue| |
notInService | | | |
| | or | | or
| | | |
| |see 3 ->C| ->C|see 6
--------------+--------------+-----------+-------------+-------------
set status |noError |noError |noError |noError ->A
column to | | | | or
destroy | ->A| ->A| ->A|see 7
--------------+--------------+-----------+-------------+-------------
set any other |see 4 |noError |noError |see 5
column to some| | | |
value | | see 1| ->C| ->D
--------------+--------------+-----------+-------------+-------------
(1) goto B or C, depending on information available to the agent.
(2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D.
(3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C.
(4) at the discretion of the agent, the return value may be either:
inconsistentName: because the agent does not choose to
create such an instance when the corresponding RowStatus instance does not exist, or
inconsistentValue: if the supplied value is
inconsistent with the state of some other MIB object's value, or
noError: because the agent chooses to create the instance.
If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A.
(5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned.
(6) the return value can indicate one of the following errors:
wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or
inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated.
(7) the return value can indicate the following error:
inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated.
(8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue.
NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc.
Conceptual Row Creation
There are four potential interactions when creating a
conceptual row: selecting an instance-identifier which is
not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device.
Interaction 1: Selecting an Instance-Identifier
The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics.
In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.)
Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different.
Finally, the management station could select a pseudo-random number to use as the index. In the event that this index
was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation.
A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used.
Interaction 2: Creating the Conceptual Row
Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions.
Interaction 2a: Creating and Activating the Conceptual Row
The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes:
- a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1.
- the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created.
- the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column.
Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'.
When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information
available to the agent is provided by two sources: the
management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row.
NOTE WELL
Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm.
Interaction 2b: Negotiating the Creation of the Conceptual Row
The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the
columns indicated by its column requirements.) Otherwise,
the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3.
Interaction 3: Initializing non-defaulted Objects
The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes:
- a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column.
- the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column.
- the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column.
If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4.
Interaction 4: Making the Conceptual Row Available
Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'.
NOTE WELL
A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device.
If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row.
Conceptual Row Suspension
When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified).
Conceptual Row Deletion
For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady',
`notInService' or `active'.) If the operation succeeds,
then all instances associated with the conceptual row are immediately removed. · Integer32
The status of the row.
The writable columns in a row cannot be changed if the row is active. All columns are to have a valid value before a row can be activated.
This table includes configuration objects for the Delay Measurement bins to collect stats.
Each row in the table is automatically created when the Delay Measurement session is defined for the selected MEP. The number of rows created is based upon three items: the DM type, the number of bins defined for each type, and whether bins are enabled for each type.
The first four indices are the same as used to create the DM session: Maintenance Domain, MaNet, MEP identification, and jnxSoamDmCfgIndex. The fifth index is the type of bin, and the sixth index is the bin number.
For a dmDmm session all nine types of bins can be created. For a dm1DmmTx session no bins are created. For a dm1DmmRx session only types forwardFrameDelay, forwardIfdv, and forwardFrameDelayRange can be created.
The number of bins created for a bin type is based upon: the jnxSoamDmCfgNumMeasBinsPerFrameDelayInterval object, the jnxSoamDmCfgNumMeasBinsPerInterFrameDelayVariationInterval object, the jnxSoamDmCfgNumMeasBinsPerFrameDelayRangeInterval object, and the jnxSoamDmCfgMeasurementEnable object.
For instance, if a dmDmm session with Bins per Frame Delay Interval set to 5, Bins per Frame Delay Variation Interval set to 3, and Frame Delay Range set to 2 (default), all of the appropriate bits set in jnxSoamDmMeasurementCfgEnable, the following number of rows would be created:
For bin types TwoWayFrameDelay(1), forwardFrameDelay(2), and backwardFrameDelay(3) = 5 bins * 3 types = 15 rows
For bin types TwoWayIfdv(4), forwardIfdv(5), backwardIfdv(6) = 3 bins * 3 types = 9 rows.
For bins types twoWayFrameDelayRange(7), forwardFrameDelayRange(8), backwardFrameDelayRange(9) = 2 bins * 3 types = 6 rows.
This gives a total of 30 rows created for the DMM session example.
Each value in the bin defaults to 5000us greater than the previous bin, with the first bin default value set to 0.
For the delay example above (5 bins), the following default values would be written to the bins: bin 1: 0 (range is 0us <= measurement < 5,000us) bin 2: 5000 (range is 5,000us <= measurement < 10,000us) bin 3: 10000 (range is 10,000us <= measurement < 15,000us) bin 4: 15000 (range is 15,000us <= measurement < 20,000us) bin 5: 20000 (range is 20,000us <= measurement < infinity)
For the delay variation example above (3 bins), the following default values would be written to the bins: bin 1: 0 (range is 0us <= measurement < 5,000us) bin 2: 5000 (range is 5,000us <= measurement < 10,000us) bin 3: 10000 (range is 10,000us <= measurement < infinity)
For the frame delay range example above (2 bins), the following default values would be written to the bins: bin 1: 0 (range is 0us <= measurement < 5,000us) bin 2: 5000 (range is 5,000us <= measurement < infinity)
The writable objects in this table need to be persistent upon reboot or restart of a device.
Rows are only created if the corresponding measurement type has been enabled via the jnxSoamDmCfgMeasurementEnable object.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamDmCfgMeasBinType
1.3.6.1.4.1.2636.3.78.1.3.6.1.1
JnxSoamTcDelayMeasurementBinType1 = twoWayFrameDelay2 = forwardFrameDelay3 = backwardFrameDelay4 = twoWayIfdv5 = forwardIfdv6 = backwardIfdv7 = twoWayFrameDelayRange8 = forwardFrameDelayRange9 = backwardFrameDelayRangeThis enumeration data type is used to distinguish between measurement bins for Frame Delay, Frame Delay Range, and Inter-frame Delay variation.
The valid enumerated values associated with this type are:
twoWayFrameDelay(1) indicates a measurement bin for two-way Frame Delay. forwardFrameDelay(2) indicates a measurement bin for one-way Frame Delay in the forward direction. backwardFrameDelay(3) indicates a measurement bin for one-way Frame Delay in the backward direction. twoWayIfdv(4) indicates a measurement bin for two-way Inter-frame Delay Variation. forwardIfdv(5) indicates a measurement bin for one-way Inter-frame Delay Variation in the forward direction. backwardIfdv(6) indicates a measurement bin for one-way Inter-frame Delay Variation in the backward direction. twoWayFrameDelayRange(7) indicates a measurement bin for two-way Frame Delay Range. forwardFrameDelayRange(8) indicates a measurement bin for one-way Frame Delay Range in the forward direction. backwardFrameDelayRange(9) indicates a measurement bin for one-way Frame Delay Range in the backward direction. · Integer32
This object specifies whether the bin number is for Frame Delay or Inter-Frame Delay Variation.
jnxSoamDmCfgMeasBinNumber
1.3.6.1.4.1.2636.3.78.1.3.6.1.2
Unsigned32
This object specifies the bin number for the configured boundary. The first bin has bin number 1.
jnxSoamDmCfgMeasBinLowerBound
1.3.6.1.4.1.2636.3.78.1.3.6.1.3
Unsigned32 · microseconds (us)
Reference: [MEF SOAM-PM] R33, R35, D17
This object specifies the lower boundary for a measurement bin. The upper boundary is defined by the next bin value or infinite for the last bin defined. The measurement boundary for each measurement bin is to be larger than the measurement boundary of the preceding measurement bin. By default, the next bin is set to 5000us larger than the lower bin boundary.
The values in a bin boundary object represents the time range used to segregate delay data into the appropriate statistical data bin. For five bins with default values, each bin has the following time range:
bin 1 = 0, range is 0us <= measurement < 5,000us bin 2 = 5000, range is 5,000us <= measurement < 10,000us bin 3 = 10000, range is 10,000us <= measurement < 15,000us bin 4 = 15000, range is 15,000us <= measurement < 20,000us < infinity
The first bin boundary (jnxSoamDmCfgBinNumber set to 1) always contains the value of 0. Attempting to write a non-zero value to this bin will result in an error.
This table contains the result bins for the current Measurement Interval in a SOAM Delay Measurement session.
Each row in the table represents the current bin statistics for a Delay Measurement session for the defined MEP. This table uses six indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific DM session on the selected MEP. The fifth index indicates bin type and the sixth indicates the specific bin number.
A row in this table is created automatically by the SNMP Agent when the Delay Measurement session is configured and the bin counter value is set to 0.
The objects in this table are ignored if jnxSoamDmCfgType is 1DmTx.
This table applies only if the corresponding bit is set in jnxSoamDmCfgMeasurementEnable.
The objects in this table do not need to be persistent upon reboot or restart of a device.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamDmCurrentStatsBinsCounter
1.3.6.1.4.1.2636.3.78.1.3.7.1.1
Gauge32
Reference: [MEF SOAM-PM] R66, R67, R100, R101
This object contains the count of the number of completed measurements initiated in this Measurement Interval whose value falls within the range specified for this bin (that is, greater than or equal to the measurement boundary for the bin, and (unless the bin is the last bin) less than the measurement boundary for the following bin.
This table contains the result bins for the history Measurement Intervals in a SOAM Delay Measurement session.
Rows of this table are created automatically by the SNMP Agent when the Delay Measurement session is running and a Measurement Interval is completed.
Each row in the table represents the Measurement Interval history statistics for a specific bin in a Delay Measurement session for the defined MEP. This table uses seven indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific DM session on the selected MEP. The fifth index is the Measurement Interval. The sixth index is the specific bin type. The seventh index is the specific bin number.
Rows in this table pertaining to a given Measurement Interval are row in the jnxSoamDmHistoryStatsTable is deleted.
The objects in this table are ignored if jnxSoamDmCfgType is 1DmTx.
This table applies only if the corresponding bit is set in jnxSoamDmCfgMeasurementEnable.
The objects in this table need to be persistent upon reboot or restart of a device.
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.
dot1agCfmMaIndex
Unsigned32 (1..4294967295)
Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation.
dot1agCfmMepIdentifier
Dot1agCfmMepIdMaintenance association Endpoint Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.Reference: 3.132, 19.2.1 (1..8191) · Unsigned32 · hint d
Reference: 3.132, 19.2, 12.14.7
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 Endpoint (3.132).
MEP Identifier is also known as the MEPID.
jnxSoamDmHistoryStatsBinsCounter
1.3.6.1.4.1.2636.3.78.1.3.8.1.1
Gauge32
Reference: [MEF SOAM-PM] R66, R67, R100, R101
This object contains the count of the number of completed measurements initiated in this Measurement Interval whose value falls within the range specified for this bin (that is, greater than or equal to the measurement boundary for the bin, and (unless the bin is the last bin) less than the measurement boundary for the following bin.
Trap details
jnxSoamLmSessionStartStopAlarm
1.3.6.1.4.1.2636.3.78.0.1
An jnxSoamLmSessionStartStopAlarm notification is sent when the state of jnxSoamLmCfgSessionStatus changes.
The management entity that receives the notification can identify the system from the network source address of the notification, and can identify the individual PM session reporting the start/stop by the indices in the OID jnxSoamLmCfgSessionStatus, including dot1agCfmMdIndex, dot1agCfmMaIndex, dot1agCfmMepIdentifier, and jnxSoamLmCfgIndex.
An agent is not to generate more than one jnxSoamLmSessionStartStopAlarm 'notification-event' in a given time interval per LM session as specified by the jnxSoamPmNotificationCfgAlarmInterval. A 'notification-event' is the transmission of a single notification to a list of notification destinations.
If additional operational state changes occur within the jnxSoamPmNotificationCfgAlarmInterval period, then notification generation for these changes are be suppressed by the agent until the current alarm interval expires. At the end of an alarm interval period, one notification-event is generated if any operational state changes occurred since the start of the alarm interval period. In such a case, another alarm interval period is started right away.
jnxSoamLmCfgSessionStatus
1.3.6.1.4.1.2636.3.78.1.2.1.1.22
OCTET STRING SIZE (1..44)
This object indicates the current status of the LM session. A value of 'active' indicates the current LM session is active, i.e. the current time lies between the start time and the stop time, and
jnxSoamLmCfgEnabled is true. A value of 'notActive' indicates the
current LM session is not active, i.e. it has not started yet, has stopped upon reaching the stop time, or is disabled.
jnxSoamPmNotificationObjDateAndTime
1.3.6.1.4.1.2636.3.78.1.5.1
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
This object contains the time and date at the time that the notification event is detected, not the time of the notification generation.
This object is used only for notifications. The mechanism to set and keep current the date and time is not specified.
jnxSoamPmNotificationObjDestinationMep
1.3.6.1.4.1.2636.3.78.1.5.7
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The MAC address of the Destination MEP associated the notification found in either the jnxSoamDmCfgTable or jnxSoamLmCfgTable.
This object is only used for the notification.
jnxSoamDmSessionStartStopAlarm
1.3.6.1.4.1.2636.3.78.0.2
An jnxSoamDmSessionStartStopAlarm notification is sent when the state of jnxSoamDmCfgSessionStatus changes.
The management entity that receives the notification can identify the system from the network source address of the notification, and can identify the individual PM session reporting the start/stop by the indices in the OID jnxSoamDmCfgSessionStatus, including dot1agCfmMdIndex, dot1agCfmMaIndex, dot1agCfmMepIdentifier, and jnxSoamDmCfgIndex.
An agent is not to generate more than one jnxSoamDmSessionStartStopAlarm 'notification-event' in a given time interval per DM session as specified by jnxSoamPmNotificationCfgAlarmInterval. A 'notification-event' is the transmission of a single notification to a list of notification destinations.
If additional operational state changes occur within the jnxSoamPmNotificationCfgAlarmInterval period, then notification generation for these changes are suppressed by the agent until the current alarm interval expires. At the end of an alarm interval period, one notification-event is generated if any operational state changes occurred since the start of the alarm interval period. In such a case, another alarm interval period is started right away.
jnxSoamDmCfgSessionStatus
1.3.6.1.4.1.2636.3.78.1.3.1.1.20
OCTET STRING SIZE (1..42)
This object indicates the current status of the DM session. A value of 'active' indicates the current DM session is active, i.e. the current time lies between the start time and the stop time, and jnxSoamDmCfgEnabled is true. A value of 'notActive' indicates the current DM session is not active, i.e. it has not started yet, has stopped upon reaching the stop time, or is disabled.
jnxSoamPmNotificationObjDateAndTime
1.3.6.1.4.1.2636.3.78.1.5.1
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
This object contains the time and date at the time that the notification event is detected, not the time of the notification generation.
This object is used only for notifications. The mechanism to set and keep current the date and time is not specified.
jnxSoamPmNotificationObjDestinationMep
1.3.6.1.4.1.2636.3.78.1.5.7
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The MAC address of the Destination MEP associated the notification found in either the jnxSoamDmCfgTable or jnxSoamLmCfgTable.
This object is only used for the notification.
jnxSoamPmThresholdCrossingAlarm
1.3.6.1.4.1.2636.3.78.0.3
An jnxSoamPmThresholdCrossingAlarm notification is sent if the following conditions are met for a particular type.
For an aboveAlarm five conditions need to be met:
a) measurement of the parameter is enabled via jnxSoamLmCfgMeasurementEnable for a LM crossing or jnxSoamDmCfgMeasurementEnable for a DM crossing; and
b) the parameter threshold is configured in the jnxSoamLmThresholdCfgTable or jnxSoamDmThresholdCfgTable; and
c) the threshold crossing type of bPmThresholdAboveAlarm is enabled; and
d) the measured value of the parameter exceeds the value configured in the jnxSoamLmThresholdCfgTable for a LM crossing entry or jnxSoamDmThresholdCfgTable for a DM crossing entry for a type of bPmThresholdAboveAlarm; and
e) no previous jnxSoamPmThresholdCrossingAlarm notifications with type aboveAlarm have been sent relating to the same threshold in the jnxSoamLmThresholdCfgTable or jnxSoamDmThresholdCfgTable and the same parameter, during this Measurement Interval.
For a setAlarm five conditions need to be met:
a) measurement of the parameter is enabled via jnxSoamLmCfgMeasurementEnable for a LM crossing or jnxSoamDmCfgMeasurementEnable for a DM crossing; and
b) the parameter threshold is configured in the jnxSoamLmThresholdCfgTable or jnxSoamDmThresholdCfgTable; and
c) the threshold crossing type of bPmThresholdSetClearAlarm is enabled; and
d) the measured value of the parameter exceeds the value configured in the jnxSoamLmThresholdCfgTable for a LM crossing entry or jnxSoamDmThresholdCfgTable for a DM crossing entry for a type of bPmThresholdSetClearAlarm for the Measurement Interval; and
e) the previous measured value did not exceed the value configured in the jnxSoamLmThresholdCfgTable for a LM crossing entry or jnxSoamDmThresholdCfgTable for a DM crossing entry for a type of bPmThresholdSetClearAlarm.
For a clearAlarm five conditions need to be met:
a) measurement of the parameter is enabled via jnxSoamLmCfgMeasurementEnable for a LM crossing or jnxSoamDmCfgMeasurementEnable for a DM crossing; and
b) the parameter threshold is configured in the jnxSoamLmThresholdCfgTable or jnxSoamDmThresholdCfgTable; and
c) the threshold crossing type of bPmThresholdSetClearAlarm is enabled; and
d) the measured value of the parameter did not exceed the value configured in the jnxSoamLmThresholdCfgTable for a LM crossing entry or jnxSoamDmThresholdCfgTable for a DM crossing entry for a type of bPmThresholdSetClearAlarm for the Measurement Interval; and
e) the previous measured value did exceed the value configured in the jnxSoamLmThresholdCfgTable for a LM crossing entry or jnxSoamDmThresholdCfgTable for a DM crossing entry for a type of bPmThresholdSetClearAlarm.
In the case of thresholds applied to a maximum or average measurement counter, the previous measured value is the value of the counter at the end of the preceding Measurement Interval. In the case of thresholds applied to the last measured value, it is the previous measured value.
The management entity that receives the notification can identify the system from the network source address of the notification, and can identify the LM or DM session reporting the threshold crossing by the indices in the jnxSoamPmNotificationCfgThresholdId object, including dot1agCfmMdIndex, dot1agCfmMaIndex, dot1agCfmMepIdentifier, and the jnxSoamLmCfgIndex or jnxSoamDmCfgIndex.
An agent is not to generate more than one jnxSoamLmThresholdCrossingAlarm 'notification-event' of a given type per LM or DM session as specified by jnxSoamPmNotificationCfgAlarmInterval. A 'notification-event' is the transmission of a single notification to a list of notification destinations.
If additional threshold crossing events occur within the jnxSoamPmNotificationCfgAlarmInterval period, then notification generation for these changes are suppressed by the agent until the current alarm interval expires. At the end of an alarm interval period, one notification-event is generated if any threshold crossing events occurred since the start of the alarm interval period. In such a case, another alarm interval period is started right away.
The Notification Crossing Type of the object that caused the generation of the notification from the jnxSoamLmThresholdEntry or jnxSoamDmThresholdEntry.
aboveAlarm(1) indicates that the crossing type alarm was an above threshold
setAlarm(2) indicates that the crossing type alarm was a set threshold
clearAlarm(3) indicates that the crossing type alarm was a clear threshold
This object is only used for the notification.
jnxSoamPmNotificationObjThresholdId
1.3.6.1.4.1.2636.3.78.1.5.2
OBJECT IDENTIFIER
The Object Identifier of the object that caused the generation of the notification from the jnxSoamLmThresholdEntry or jnxSoamDmThresholdEntry.
This object is only used for the notification.
jnxSoamPmNotificationObjThresholdConfig
1.3.6.1.4.1.2636.3.78.1.5.3
Unsigned32
The configured threshold value of the object that caused the generation of the notification.
This object is only used for the notification.
jnxSoamPmNotificationObjThresholdValue
1.3.6.1.4.1.2636.3.78.1.5.4
Unsigned32
The measured value of the object at the time of the generation of the Notification, from the jnxSoamLmMeasuredStatsTable, jnxSoamLmCurrentStatsTable, jnxSoamDmMeasuredStatsTable or jnxSoamDmCurrentStatsTable.
This object is only used for the notification.
jnxSoamPmNotificationObjSuspect
1.3.6.1.4.1.2636.3.78.1.5.5
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
The suspect flag for the current Measurement Interval in which the notification was generated from the jnxSoamLmCurrentStatsTable, or jnxSoamDmCurrentStatsTable.
This object is only used for the notification.
jnxSoamPmNotificationObjDateAndTime
1.3.6.1.4.1.2636.3.78.1.5.1
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
This object contains the time and date at the time that the notification event is detected, not the time of the notification generation.
This object is used only for notifications. The mechanism to set and keep current the date and time is not specified.
jnxSoamPmNotificationObjDestinationMep
1.3.6.1.4.1.2636.3.78.1.5.7
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The MAC address of the Destination MEP associated the notification found in either the jnxSoamDmCfgTable or jnxSoamLmCfgTable.
This object is only used for the notification.
jnxSoamPmThresholdFlapAlarm
1.3.6.1.4.1.2636.3.78.0.4
The jnxSoamPmThresholdFlapAlarm is sent when the CFM Threshold Flap Notification feature is enabled which would dampen the jnxSoamPmThresholdCrossingAlarm sent to NMS. The jnxSoamPmThresholdFlapAlarm gives details about Flaps occured during the time interval. The jnxSoamPmThresholdFlapAlarm is sent for the follwing below conditions
a) Trap is sent if one flap sequence has occured
b) Trap is sent if threshold or timer changes happens. c) Trap is sent when finite iterations counts expires.
jnxSoamPmNotificationObjThresholdId
1.3.6.1.4.1.2636.3.78.1.5.2
OBJECT IDENTIFIER
The Object Identifier of the object that caused the generation of the notification from the jnxSoamLmThresholdEntry or jnxSoamDmThresholdEntry.
This object is only used for the notification.
jnxSoamPmNotificationObjThresholdConfig
1.3.6.1.4.1.2636.3.78.1.5.3
Unsigned32
The configured threshold value of the object that caused the generation of the notification.
This object is only used for the notification.
jnxSoamPmNotificationObjThresholdLastValue
1.3.6.1.4.1.2636.3.78.1.5.11
Unsigned32
The measured value of the object at the time of the generation of the last Notification during the flap trap timer interval.
This object is only used for the notification.
jnxSoamPmNotificationTotalFlaps
1.3.6.1.4.1.2636.3.78.1.5.9
Unsigned32
The measured value of total number of flaps occured during the flap trap timer itnerval.
jnxSoamPmNotificationAccTotalFlaps
1.3.6.1.4.1.2636.3.78.1.5.10
Unsigned32
The measured value of total number of accumulated flaps occured during the flap trap timer itnerval.
The Current Notification Crossing Type of the object that caused the generation of the notification at the end of timer interval from the jnxSoamLmThresholdEntry or jnxSoamDmThresholdEntry.
aboveAlarm(1) indicates that the crossing type alarm was an above threshold
setAlarm(2) indicates that the crossing type alarm was a set threshold
clearAlarm(3) indicates that the crossing type alarm was a clear threshold
This object is only used for the notification.
jnxSoamPmNotificationObjDestinationMep
1.3.6.1.4.1.2636.3.78.1.5.7
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The MAC address of the Destination MEP associated the notification found in either the jnxSoamDmCfgTable or jnxSoamLmCfgTable.
This object is only used for the notification.