JUNIPER-SOAM-PM-MIB Table View

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.