Juniper ACX2000

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.
Table 95: jnxSoamDmCfgTable
DescriptionObject IDObject
Denotesan 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 (that is, 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.
jnxSoamDmCfgEntry 1jnxSoamDmCfgIndex
Specifies the type of Delay Measurement to
be performed.
•
dmDmm(1)—DMM SOAM PDU generated,
DMR responses received(one-way or
two-way measurements)
•
dm1DmTx(2)—1DMSOAM 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.
jnxSoamDmCfgEntry 2jnxSoamDmCfgType
Copyright © 2017, Juniper Networks, Inc.1192
ACX Series Universal Access Router Configuration Guide