oam-pm session session-name {dmm | slm | twamp-light} {start | stop}
oam
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command allows the operator to start and stop on-demand OAM-PM sessions.
Identifies the session name, up to 32 characters, that the test is associated with.
Specifies the DMM test that is affected by the command.
Specifies the SLM test that is affected by the command.
Specifies the TWAMP-Light test that is affected by the command.
Keyword to manually start the test.
Keyword to manually stop the test.
oam-pm
config
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Commands in this context configure storage parameters (including binning structures), availability/resiliency, and the individual proactive and on-demand tests used to gather performance and statistical data.
bin-group bin-group-number [fd-bin-count fd-bin-count fdr-bin-count fdr-bin-count ifdv-bin-count ifdv-bin-count create]
no bin-group bin-group-number
config>oam-pm
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the parameters for a specific bin group. Bin-group 1 is a default bin group and cannot be modified. If no bin group is assigned to an OAM-PM session, bin-group 1 is assigned by default. The default values for bin-group 1 are fd-bin-count 3 bin 1 lower-bound 5000 bin 2 lower-bound 10000, fdr-bin-count 2 bin 1 lower-bound 5000, and ifdv-bin-count 2 bin 1 lower-bound 5000.
The no form of this command removes the specified bin group.
Specifies the numerical identifier for a bin group. A bin group can only shut down and modified when all of the PM sessions referencing the bin group have been shut down. The bin group description may still be modified for active bin groups.
Specifies the number of frame delay bins that are created.
Specifies the number of frame delay range bins that are created.
Specifies the number of inter-frame delay variation bins that are created.
Creates the specified bin group.
bin-type {fd | fdr | ifdv}
no bin-type
config>oam-pm>bin-group
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command enables the specified delay metric configuration context.
The no form of this command restores the default value.
bin-type fd
Enters the frame delay bin threshold configuration context.
Enters the frame delay range bin threshold configuration context.
Enters the inter-frame delay variation bin threshold configuration context.
bin bin-number
config>oam-pm>bin-group>bin
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the floor threshold for an individual bin.
Specifies the bin to configure.
lower-bound microseconds
no lower-bound
config>oam-pm>bin-group>bin-type>bin
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the lower threshold for an individual bin. The operator does not have to specific a lower threshold for every bin that was previously defined by the bin-count for the specific type. By default, the lower threshold for each bin is the bin-number * 5000 microseconds. Lower thresholds in the previous adjacent bin must be lower than the threshold of the next higher bin threshold; otherwise, an error prevents the bin from entering the active state when the no shutdown command is issued for the bin group. Bin 0 is the result of the difference between 0 and the configured lower-bound of bin 1. The highest bin in the bin-count captures every result above the threshold. Any negative delay metric result is treated as zero and placed in bin 0.
The no form of this command restores the default threshold for the bin.
Specifies the lower threshold for the bin, in microseconds.
delay-event {forward | backward | round-trip} lowest-bin bin-number
threshold raise-threshold [clear clear-threshold]
[no] delay-event {forward | backward | round-trip}
config>oam-pm>bin-group>bin-type
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the bin number, threshold, and direction that are monitored to determine if a delay metric threshold crossing event has occurred or has cleared. It requires a bin number, a rising threshold value and a direction. If the [clear threshold] is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. When a raise threshold is reached, the log event is generated. Each unique threshold can only be raised once for the threshold within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised another is not raised until a measurement interval completes, and the clear threshold has not been exceeded. A clear event is raised under that condition. In general, alarms are generated when there is a state change. The thresholds configured are applied to the count in specified bin and all higher number bins.
The no version of this command removes thresholding for this delay metric. The complete command must be configured to remove the specific threshold.
[no] delay-events
Specifies that the threshold is applied to the forward direction bin.
Specifies that the threshold is applied to the backward direction bin.
Specifies that the threshold is applied to the roundtrip direction bin.
Specifies the number of the bin to which the threshold is applied. This bin and all higher bins monitor the sum total results in these bins to determine if they have reached or crossed the configured threshold.
Specifies the rising numerical value in the range that determines when the event is to be generated, when value reached.
Specifies an optional numerical value in the range threshold used to indicate stateful behavior that allows the operator to configure a lower value than the rising threshold that determines when the clear event should be generated. Clear is generated when the end of measurement interval count is less than or equal to the configured value. If this option is not configured, the behavior is stateless. Zero means no results can existing in the lower bin or any higher.
description description-string
no description
config>oam-pm>bin-group
config>oam-pm>session
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the content in the configuration file.
The no form of this command removes the string from the configuration.
Specifies the description character string. Allowed values are any characters up to 80 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed in double quotes.
[no] shutdown
config>oam-pm>bin-group
config>oam-pm>session>ethernet>dmm
config>oam-pm>session>ethernet>slm
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command activates and deactivates the bin group or test.
When a bin group is active, only the description of the bin group can be modified. The bin group can only be shut down and modified when all references in the various PM sessions or individual tests have been shut down. If an active PM session is referencing the bin group, it generates an error indicating there are a number of active tests referencing the bin group, and it cannot be shut down.
When a test is shut down, no active measurements are made and any outstanding requests are ignored. If the test is started or stopped during a measurement interval, the suspect flag is set to ‟yes” to indicate that the data for the specific data set is in questionable.
The no form of this command activates the bin group or test.
session session-name [test-family {ethernet | ip} [session-type {proactive | on-demand}] create]
no session session-name
config>oam-pm
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the individual session containers that house the test-specific configuration parameters. Since this session context provides only a container abstract to house the individual test functions, it cannot be shut down. Only individual tests sessions within the container may be shut down. No values, parameters, or configuration within this context may be changed if any individual test is active. Changes may only be made when all tests within the context are shut down, with the exception of the description.
The no form of this command removes the session.
Specifies the name of the session container. 32 characters maximum.
Specifies that the test is based on the Ethernet layer.
Specifies that the test is based on the IP layer.
Specifies that the test is always on, with no stop. Tests are proactive by default.
Specifies that the test runs on demand, with an immediate start and no stop, or a stop based on offset.
Creates the session container.
bin-group bin-group-number
no bin-group
config>oam-pm>session
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command links the individual test to the group of bins that map the probe responses.
The no form of this command installs the default bin-group 1 as the bin group for the session.
bin-group 1
Specifies the number of the bin-group that is referenced during this session.
ethernet
config>oam-pm>session
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Commands in this context configure Ethernet-specific source and destination information, priority, and Ethernet test tools on the launch point.
dest-mac ieee-address
no dest-mac
config>oam-pm>session>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command defines the destination MAC address of the peer MEP and sets the destination MAC address in the Layer 2 header to match. This must be a unicast address.
The no form of this command removes the session parameter.
Specifies the Layer 2 unicast MAC address of the destination MEP.
dmm [test-id test-id] [create]
no dmm
config>oam-pm>session>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the test ID to be assigned to the delay test, and creates the container to allow the individual test parameters to be configured.
The no form of this command removes the DMM test function from the PM session.
Specifies the value to be placed in the 4-byte test ID field of the ETH-DMM PDU.
Creates the test.
data-tlv-size octets
no data-tlv-size
config>oam-pm>session>ethernet>dmm
config>oam-pm>session>ethernet>slm
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command is used to add an optional Data TLV to the PDU and increase the frame on the wire by the specified amount. This value is not the total size of the frame on the wire, but rather the size of the additional padding added to the PDU.
The no form of this command removes the optional TLV.
data-tlv-size 0
Specifies the size of the optional Data TLV, in octets.
interval milliseconds
no interval
config>oam-pm>session>ethernet>dmm
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the message period, or probe spacing, for the transmission of DMM frames.
The no form of this command restores the default value.
interval 1000
Specifies the number of milliseconds between the transmission of DMM frames. The default value for the DMM interval is intentionally different from the default value for the SLM interval.
test-duration seconds
no test-duration
config>oam-pm>session>ethernet>dmm
config>oam-pm>session>ethernet>slm
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command defines the length of time the test runs before stopping automatically. This command is only a valid option when a session has been configured with a session-type of on-demand. This is not an option when the session-type is configured as proactive. All tests start immediately following the execution of a no shutdown command.
The test duration value, remaining time, or completed state, is not synchronized with the backup CPM. This means that a failover re-launches any active test without regard to the test-duration timer on the previously active CPM. When the test starts on the newly active CPM, the test-duration is reset to the beginning.
The no form of this command removes a previously configured test-duration and allows the test to execute until manually stopped.
Specifies the interval, in seconds, during which the test continues to execute after the start time.
priority priority
no priority
config>oam-pm>session>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the CoS priority across all tests configured under this session. This CoS value is exposed to the various QoS policies the frame passes through and does not necessarily map directly to the CoS value on the wire.
The no form of this command restores the default value.
0
Specifies the CoS priority value.
slm [test-id test-id] [create]
no slm
config>oam-pm>session>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the test ID to be assigned to the synthetic loss test, and creates the container to allow the individual test parameters to be configured.
The no form of this command removes the SLM test function from the PM session.
Specifies the value to be placed in the 4-byte test ID field of the ETH-SLM PDU.
Creates the test.
flr-threshold percentage
no flr-threshold
config>oam-pm>session>ethernet>slm
config>oam-pm>session>ip>twamp-light>loss-events
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the frame loss threshold that is used to determine whether the delta-t is available or unavailable. An individual delta-t with a frame loss threshold equal to or higher than the configured threshold is marked unavailable. An individual delta-t with a frame loss threshold lower than the configured threshold is marked as available.
The no form of this command reverts to the default value.
flr-threshold 50
Specifies the percentage of the threshold.
loss-events
config>oam-pm>session>ethernet>slm
config>oam-pm>session>ip>twamp-light
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This context enables the context to define the loss events and thresholds that are to be tracked.
avg-flr-event {forward | backward} threshold raise-threshold-percent [clear clear-threshold-percent]
[no] avg-flr-event {forward | backward}
config>oam-pm>session>ethernet>slm>loss-events
config>oam-pm>session>ip>twamp-light>loss-events
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command sets the frame loss ratio threshold configuration that is applied and checked at the end of the measurement interval for the specified direction. This is a percentage based on average frame loss ratio over the entire measurement interval. If [clear clear-threshold-percent] is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. Each unique event can only be raised once within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised, another is not raised until a measurement interval completes and the clear threshold has not been exceeded. A clear event is raised under that condition.
The no version of this command removes the event threshold for frame loss ratio. The direction must be included with the no command.
no avg-flr-event forward
no avg-flr-event backward
Specifies that the threshold is applied to the forward direction value.
Specifies that the threshold is applied to the backward direction value.
Specifies the rising percentage that determines when the event is to be generated.
Specifies an optional value used for stateful behavior that allows the operator to configure a percentage of loss value lower than the rising percentage to indicate when the clear event should be generated.
chli-event {forward | backward | aggregate} threshold raise-threshold [clear clear-threshold]
[no] chli-event {forward | backward | aggregate}
config>oam-pm>session>ethernet>slm>loss-events
config>oam-pm>session>ip>twamp-light>loss-events
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command sets the consecutive high loss interval (CHLI) threshold to be monitored and the associated thresholds using the counter of the specified direction. The aggregate is a function of summing forward and backward. This value is only used as a threshold mechanism and is not part of the stored statistics. If [clear clear-threshold] is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. Each unique event can only be raised once within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised, another is not raised until a measurement interval completes and the clear threshold has not been exceeded. A clear event is raised under that condition.
The no version of this command removes the event threshold for frame loss ratio. The direction must be included with the no command.
no chli-event forward
no chli-event backward
no chli-event aggregate
Specifies that the threshold is applied to the forward direction count.
Specifies that the threshold is applied to the backward direction count.
Specifies that the threshold is applied to the aggregate count (sum of forward and backward).
Specifies a numerical value compared to the CHLI counter that is the rising threshold that determines when the event is to be generated, when the percentage of loss value is reached.
Specifies an optional numerical value compared to the CHLI counter used for stateful behavior that allows the operator to configure a value lower than the rising percentage to indicate when the clear event should be generated.
hli-event {forward | backward | aggregate} threshold raise-threshold [clear clear-threshold]
[no] hli-event {forward | backward | aggregate}
config>oam-pm>session>ethernet>slm>loss-events
config>oam-pm>session>ip>twamp-light>loss-events
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command sets the high loss interval (HLI) threshold to be monitored and the associated thresholds using the counter of the specified direction. The aggregate is a function of summing forward and backward. This value is only used as a threshold mechanism and is not part of the stored statistics. If the [clear clear-threshold] is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. Each unique event can only be raised once within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised, another is not raised until a measurement interval completes and the clear threshold has not been exceeded. A clear event is raised under that condition.
The no version of this command removes the event threshold for frame loss ratio. The direction must be included with the no command.
no hli-event backward
no hli-event aggregate
Specifies that the threshold is applied to the forward direction count.
Specifies that the threshold is applied to the backward direction count.
Specifies that the threshold is applied to the aggregate count (sum of forward and backward).
Specifies the rising threshold that determines when the event is to be generated, when the percentage of loss value is reached.
Specifies an optional value used for stateful behavior that allows the operator to configure a percentage of loss value lower than the rising percentage to indicate when the clear event should be generated.
unavailability-event {forward | backward | aggregate} threshold raise-threshold [clear clear-threshold]
[no] unavailability-event {forward | backward | aggregate}
config>oam-pm>session>ethernet>slm>loss-events
config>oam-pm>session>ip>twamp-light>loss-events
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command sets the threshold to be applied to the overall count of the unavailability indicators, not transitions, per configured direction. This value is compared to the 32 bit unavailability counter specific to the direction which tracks the number of individual delta-ts that have been recorded as unavailable. The aggregate is a function of summing forward and backward. This value is only used as a threshold mechanism and is not part of the stored statistics. If the [clear clear-threshold] is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. Each unique event can only be raised once within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised, another is not raised until a measurement interval completes and the clear threshold has not been exceeded. A clear event is raised under that condition.
The no version of this command removes the event threshold for frame loss ratio. The direction must be included with the no command.
no unavailable-event forward
no unavailable-event backward
no unavailable-event aggregate
Specifies that the threshold is applied to the forward direction count.
Specifies that the threshold is applied to the backward direction count.
Specifies that the threshold is applied to the aggregate count (sum of forward and backward).
Specifies a numerical value compared to the unavailability counter that is the rising threshold that determines when the event is to be generated, when value reached
an optional value used for stateful behavior that allows the operator to configure a percentage of loss value lower than the rising percentage to indicate when the clear event should be generated
undet-availability-event {forward | backward | aggregate} threshold raise-threshold [clear clear-threshold]
[no] undet-availability-event {forward | backward | aggregate}
config>oam-pm>session>ethernet>slm>loss-events
config>oam-pm>session>ip>twamp-light>loss-events
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command sets the threshold to be applied to the overall count of the undetermined availability indicators, not transitions, per configured direction. This value is compared to the 32 bit unavailability counter specific to the direction which tracks the number of individual delta-ts that have been recorded as undetermined available. The aggregate is a function of summing forward and backward. This value is only used as a threshold mechanism and is not part of the stored statistics. If the [clear clear-threshold] is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. Each unique event can only be raised once within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised, another is not raised until a measurement interval completes and the clear threshold has not been exceeded. A clear event is raised under that condition.
The no version of this command removes the event threshold for frame loss ratio. The direction must be included with the no command.
no undetermined-available-event forward
no undetermined-available-event backward
no undetermined-available-event aggregate
Specifies that the threshold is applied to the forward direction count.
Specifies that the threshold is applied to the backward direction count.
Specifies that the threshold is applied to the aggregate count (sum of forward and backward).
Specifies the rising threshold that determines when the event is to be generated, when value reached.
Specifies an optional value used for stateful behavior that allows the operator to configure a percentage of loss value lower than the rising percentage to indicate when the clear event should be generated
undet-availability-event {forward | backward | aggregate} threshold raise-threshold [clear clear-threshold]
[no] undet-availability-event {forward | backward | aggregate}
config>oam-pm>session>ethernet>slm>loss-events
config>oam-pm>session>ip>twamp-light>loss-events
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command sets the threshold to be applied to the overall count of the undetermined unavailability indicators, not transitions, per configured direction. This value is compared to the 32 bit unavailability counter specific to the direction which tracks the number of individual delta-ts that have been recorded as undetermined unavailable. The aggregate is a function of summing forward and backward. This value is only used as a threshold mechanism and is not part of the stored statistics. If the [clear clear-threshold] is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. Each unique event can only be raised once within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised, another is not raised until a measurement interval completes and the clear threshold has not been exceeded. A clear event is raised under that condition.
The no version of this command removes the event threshold for frame loss ratio. The direction must be included with the no command.
no undet-unavailable-event forward
no undet-unavailable-event backward
no undet-unavailable-event aggregate
Specifies that the threshold is applied to the forward direction count.
Specifies that the threshold is applied to the backward direction count.
Specifies that the threshold is applied to the aggregate count (sum of forward and backward).
Specifies the rising threshold that determines when the event is to be generated, when value reached.
Specifies an optional value used for stateful behavior that allows the operator to configure a percentage of loss value lower than the rising percentage to indicate when the clear event should be generated.
timing frames-per-delta-t frames consec-delta-t deltas interval milliseconds chli-threshold threshold
no timing
config>oam-pm>session>ethernet>slm
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures various availability parameters and the probe spacing (interval) for the SLM frames. The maximum size of the availability window must not exceed 10 s (10000 ms).
The no form of this command installs the default values for all timing parameters and uses those values to compute availability and set the SLM frequency. If an SLM test is active, it always has timing parameters, whether default or operator-configured.
timing frames-per-delta-t 10 consec-delta-t 10 interval 100 chli-threshold 5
Specifies the number of frames that define the size of the delta-t. Each delta-t is marked as available or unavailable based on the flr-threshold. The size of the delta-t measurement is the product of the number of frames and the interval.
Specifies the number of consecutive delta-ts that make up the sliding window over which availability and unavailability is determined. Transitions from one state to another occur when the consecutive delta-ts are in a new state.
Specifies the number of milliseconds between the transmission of the SLM frames. The default value for the SLM interval is intentionally different from the default interval for DMM.
Specifies the number of consecutive unavailable delta-ts that cause the CHLI counter to be incremented. A CHLI counter is an indication that the sliding window is available but has crossed a threshold of consecutive unavailable delta-t intervals. A CHLI can only be incremented once during a sliding window and is only incremented during times of availability.
source mep mep-id domain md-index association ma-index
no source
config>oam-pm>session>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the source launch point for Y.1731 parameters that are used by the individual tests within the session. If an MEP matching the configuration does not exist, the session is allowed to become active; however, the frames sent and received as seen under the show>oam-pm>statistics>session session-name command are zero.
The no form of this command removes this session parameter.
Specifies the maintenance association end point identifier of the launch point.
Specifies the maintenance domain (MD) index value of the launch point.
Specifies the maintenance association (MA) index value of the launch point.
meas-interval {5-mins | 15-mins | 1-hour | 1-day} [create]
no meas-interval
config>oam-pm>session
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command establishes the parameters of the individual measurement intervals used by the session. A maximum of three different measurement intervals may be configured under each session.
The no form of this command deletes the specified measurement interval.
Specifies a 5 minute measurement interval duration.
Specifies a 15 minute measurement interval duration.
Specifies a 1 hour measurement interval duration.
Specifies a 1 day measurement interval duration.
Creates the measurement interval.
accounting-policy acct-policy-id
no accounting-policy
config>oam-pm>session>meas-interval
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command assigns a record-type of complete-pm to the specified accounting policy (configured using the config>log>accounting-policy command). This runs the data collection process for completed measurement intervals in memory, file storage, and maintenance functions, moving data from memory to flash. A single accounting policy can be applied to a measurement interval.
The no form of this command removes the accounting policy.
Specifies the accounting policy to be applied to the measurement interval.
boundary-type {clock-aligned | test-relative}
no boundary-type
config>oam-pm>session>meas-interval
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command establishes the alignment of the start of the measurement interval with either the time of day clock or the start of the test.
Test-relative start times launch the measurement interval when the individual test enters the active no shutdown state.
Alignment with the time of day clock always defaults to the representative top of the hour. Clocks aligned at 15-minute measurement intervals divide the hour into four equal sections at 00, 15, 30, and 45. Clocks aligned at 1-hour measurement intervals start at 00. Clocks aligned at 1-day measurement intervals start at midnight. It is typical for the first measurement interval of a clock-aligned test to have the suspect flag set to yes because it is unlikely that the no shutdown command exactly corresponds to the clock-based measurement interval start time. Clock-aligned measurement intervals can include an additional offset. See the clock-offset command option under this context.
The no form of this command restores the default value.
boundary-type clock-aligned
Aligns the start of the measurement interval with the time of day clock.
Aligns the start of the measurement interval with the start of the test.
clock-offset seconds
no clock-offset
config>oam-pm>session>meas-interval
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures an offset between measurement intervals with a boundary-type of clock-aligned and the default time of day clock. The configured offset must be smaller than the size of the measurement interval. As an example, an offset of 300 seconds shifts the start times of the measurement intervals by 5 minutes from their default alignments with respect to the time of day clock.
The no form of this command restores the default value.
clock-offset 0
Specifies the number of seconds to offset a clock-alignment measurement interval from its default.
event-mon
config>oam-pm>session>measurement-interval
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command enables different threshold events on a specific measurement interval. Only one measurement interval with a configured OAM PM session can have events enabled using the no shutdown command.
[no] delay-events
config>oam-pm>session>measurement-interval>event-mon
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This enables the monitoring of all configured delay events.
Configuring this command starts the monitoring of the configured delay events at the start of the next measurement interval. If the command is disabled using the no command, all monitoring of configured delay events, logging, and recording of new events for that session are suspended. Any existing events at the time of the shut down are maintained until the active measurement window in which the removal was performed has completed. The state of this monitoring function can be changed without needing to shut down all the tests in the session.
The no form of this command disables the monitoring of all configured delay events.
[no] loss-events
config>oam-pm>session>measurement-interval>event-mon
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This enables the monitoring of all configured loss events.
Configuring this command starts the monitoring of the configured loss events at the start of the next measurement interval. If the command is disabled using the no command, all monitoring of configured loss events, logging, and recording of new events for that session are suspended. Any existing events at the time of the shut down are maintained until the active measurement window in which the removal was performed has completed. The state of this monitoring function can be changed without needing to shut down all the tests in the session.
The no form of this command disables the monitoring of all configured loss events.
intervals-stored intervals
no intervals-stored
config>oam-pm>session>meas-interval
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the number of completed measurement intervals per session to be stored in volatile system memory. The entire block of memory is allocated for the measurement interval when the test is active (no shutdown) to ensure that memory is available. The numbers increase from 1 to the configured value + 1. The active PM data is stored in interval number 1, and older runs are stored, in order, to the upper most number, with the oldest run being deleted when the number of completed measurement intervals exceeds the configured value + 1. As new test measurement intervals complete for the session, the stored intervals are renumbered to maintain the described order. Care must be taken when setting this value. There must be a balance between completed runs stored in volatile memory and the use of the write-to-flash function of the accounting policy.
The 5-mins and 15-mins measurement intervals share the same (1 to 96) retention pool. In the unlikely event that both intervals are required, the total of both cannot exceed 96. The 1-hour and 1-day measurement intervals use their own ranges. If this command is omitted when configuring the measurement interval, the default values are used.
Specifies the number of stored intervals.