Configuring IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
Last Updated: August 27, 2012
This module describes how to configure an IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) operation to gather the following performance measurements for Ethernet service:
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see
Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
Restrictions for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731)
Depending on your Cisco software release, SNMP is not supported for reporting threshold events or collecting performance statistics for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) operations.
Continuity Check Message (CCM)-based dual-ended Ethernet frame loss operations are not supported.
In a single-ended Ethernet operation, performance measurement statistics can be retrieved only at the device on which the sender Ethernet Connectivity Fault Management (CFM) Maintenance End Point (MEP) is configured.
Information About IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
The IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) feature supports key operation and maintenance standards that provide for automated end-to-end management and monitoring of Ethernet service by service providers. The ITU-T Y.1731 networking standard defines performance monitoring measurements such as frame delay, frame delay variation, and frame loss ratio to assist with IP SLAs assurance and capacity planning.
Ethernet Frame Delay (ETH-DM: FD), also known as delay, measures the frame latency from the time the first bit of the synthetic frame is transmitted, to the time the last bit of the frame is received. Delay measurement uses synthetic frames because service frames do not carry timestamps.
Ethernet Frame Delay Variation (ETH-DM: FDV), also known as delay variation, measures the difference between the frame latencies as experienced by two separate frames. The two frames can be either consecutive or separated by an exact number of frames, as specified in the configuration. ITU-T Y.1731 defines the following messages to measure Ethernet delay variation:
Delay Measurement Message (DMM)
Delay Measurement Reply (DMR)
One-Way Delay Measurement (1DM)
Ethernet Frame Loss Ratio (ETH-LM: FLR), also known as frame loss, measures the availability of synthetic frames in the network. Availability is defined in terms of the ratio of frames lost to frames sent, or Frame Loss Ratio (FLR). Near End Loss measures ingress frame loss and the Far End Loss measures egress frame loss. Availability is calculated using either the Near End loss numbers or the Far End loss numbers, or both. ITU-T Y.1731 defines the following messages to measure Ethernet frame loss:
Loss Measurement Message (LMM)
Loss Measurement Reply (LMR)
In a single-ended operation, a Maintenance End Point (MEP) on the source device acts as both the sender and receiver. The device sends a synthetic frame from the source to the destination and then, upon receiving back a response frame, the MEP on the source device performs the performance measurement calculations. In this operation, statistics can be retrieved only at the source device.
Dual-ended operations are supported for delay and delay-variation performance measurements only. When you start a dual-ended delay operation, the sender MEP on the source device a synthetic frame to the receiver MEP configured on another (destination) device. In this operation, the receiver MEP performs the measurement calculations. However, the statistics can be retrieved by the MEPs at both ends of the operation. Statistics from the operation are retrieved at the destination device through Cisco extensions to the protocol using Y.1731-defined Vendor-Specific Messages/Replies (VSM/VSR). For VSM/VSR in a dual-ended operation to work, the system clocks at the source and destination devices must be synchronized.
All measurements are performed using a point-to-point model between a given pair of MEPs. One-way measurement values are calculated based on the amount time that elapses between when a frame is sent from the MEP on one device, to the time when the frame is received at the MEP on another device. The accuracy of one-way delay calculations depends on close synchronization of the system clocks at the source and destination devices. Two-way measurement values are based on the time difference between when the source MEP transmits a request frame and when it receives a reply frame from the receiver MEP on the destination device, subtracting the time elapsed at the destination.
How to Configure IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
Configuring a Dual-Ended Ethernet Delay or Delay Variation Operation
Perform the tasks for configuring a dual-ended operation in the order presented.
Note
To remove the MEP configurations in an already-configured dual-ended operation, always remove the MEPs in the reverse order in which they were configured. That is, remove the scheduler first, then the threshold monitoring configuration, and then the sender MEP configuration on the source device before removing the scheduler, proactive threshold monitoring, and receiver MEP configuration on the destination device.
Configuring a Receiver MEP on the Destination Device
Before You Begin
Time synchronization is required between the source and destination devices in order to provide accurate one-way delay (latency) or delay-variation measurements. Configure either Precision Time Protocol (PTP) or Network Time Protocol (NTP) on both the source and destination devices.
(Optional) Configures the length of time during which the performance measurements are conducted and the results stored.
Step 6
distribution {delay |
delay-variation}
one-waynumber-of-binsboundary[,...,boundary]
Example:
Router(config-sla-y1731-delay)# distribution delay-variation one-way 5 5000,10000,15000,20000,-1
(Optional) Specifies measurement type and configures bins for statistics distributions kept.
Step 7
frameoffsetoffset-value
Example:
Router(config-sla-y1731-delay)# frame offset 1
(Optional) Sets the value for calculating delay variation rates.
Step 8
historyintervalintervals-stored
Example:
Router(config-sla-y1731-delay)# history interval 2
(Optional) Sets the number of statistics distributions kept during the lifetime of an IP SLAs Ethernet operation.
Step 9
max-delaymilliseconds
Example:
Router(config-sla-y1731-delay)# max-delay 5000
(Optional) Sets the amount of time an MEP waits for a frame.
Step 10
ownerowner-id
Example:
Router(config-sla-y1731-delay)# owner admin
(Optional) Configures the owner of an IP SLAs operation.
Step 11
end
Example:
Router(config-sla-y1731-delay)# end
Exits to privileged EXEC mode.
What to Do Next
To add proactive threshold conditions and reactive triggering for generating traps, see the "Configuring Proactive Threshold Monitoring" module of the
IP SLAs Configuration Guide.
When you are finished configuring proactive threshold monitoring for this MEP, see the "Scheduling IP SLAs Operations" section to schedule the operation.
Configuring the Sender MEP on the Source Router
Before You Begin
Time synchronization is required between the source and destination devices in order to provide accurate one-way delay (latency) or delay-variation measurements. Configure either Precision Time Protocol (PTP) or Network Time Protocol (NTP) on both the source and destination devices.
The receiver MEP must be configured, including proacive threshold monitoring, and scheduled before you configure the sender MEP.
(Optional) Sets the gap between successive frames.
Step 7
framesizebytes
Example:
Router(config-sla-y1731-delay)# frame size 64
(Optional) Sets the padding size for frames.
Step 8
historyintervalintervals-stored
Example:
Router(config-sla-y1731-delay)# history interval 2
(Optional) Sets the number of statistics distributions kept during the lifetime of an IP SLAs Ethernet operation.
Step 9
ownerowner-id
Example:
Router(config-sla-y1731-delay)# owner admin
(Optional) Configures the owner of an IP SLAs operation.
Step 10
end
Example:
Router(config-sla-y1731-delay)# end
Exits to privileged EXEC mode.
What to Do Next
To add proactive threshold conditions and reactive triggering for generating traps, see the "Configuring Proactive Threshold Monitoring" module of the
IP SLAs Configuration Guide.
When you are finished configuring proactive threshold monitoring for this MEP, see the "Scheduling IP SLAs Operations" section to schedule the operation.
Configuring a Sender MEP for a Single-Ended Ethernet Delay or Delay Variation Operation
Perform this task to configure a sender MEP on the source device.
Before You Begin
Time synchronization is required between the source and destination devices in order to provide accurate one-way delay (latency) or delay-variation measurements. Configure either Precision Time Protocol (PTP) or Network Time Pprotocol (NTP) on both the source and destination devices.
Note
To display information about remote (target) MEPs on destination devices, use the
showethernetcfmmaintenance-pointsremote command.
(Optional) Sets the gap between successive frames.
Step 9
frameoffsetoffset-value
Example:
Router(config-sla-y1731-delay)# frame offset 1
(Optional) Sets value for calculating delay variation values.
Step 10
framesizebytes
Example:
Router(config-sla-y1731-delay)# frame size 32
(Optional) Configures padding size for frames.
Step 11
historyintervalintervals-stored
Example:
Router(config-sla-y1731-delay)# history interval 2
(Optional) Sets the number of statistics distributions kept during the lifetime of an IP SLAs Ethernet operation.
Step 12
max-delaymilliseconds
Example:
Router(config-sla-y1731-delay)# max-delay 5000
(Optional) Sets the amount of time an MEP waits for a frame.
Step 13
ownerowner-id
Example:
Router(config-sla-y1731-delay)# owner admin
(Optional) Configures the owner of an IP SLAs operation.
Step 14
end
Example:
Router(config-sla-y1731-delay)# end
Exits to privileged EXEC mode.
What to Do Next
To add proactive threshold conditions and reactive triggering for generating traps, see the "Configuring Proactive Threshold Monitoring" module of the
IP SLAs Configuration Guide.
When you are finished configuring proactive threshold monitoring for this operation, see the "Scheduling IP SLAs Operations" section to schedule the operation.
Configuring a Sender MEP for a Single-Ended Ethernet Frame Loss Ratio Operation
Note
To display information about remote (target) MEPs on destination devices, use the
showethernetcfmmaintenance-pointsremote command.
Perform this task to configure a sender MEP on the source device.
Before You Begin
Class of Service (CoS)-level monitoring must be enabled on MEPs associated to the Ethernet frame loss operation by using the
monitorlosscounter command on the devices at both ends of the operation. See the
Cisco IOS Carrier Ethernet Command Reference for command information. See the "Configuration Examples for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations" section for configuration information.
Note
Cisco IOS Y.1731 implementation allows monitoring of frame loss for frames on an EVC regardless of the CoS value (any CoS or Aggregate CoS cases). See the "Configuration Examples for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations" section for configuration information.
Router(config)# ip sla reaction-configuration 11 react unavailableDS
(Optional) Configures proactive threshold monitoring for frame loss measurements.
Step 14
ipslaloggingtraps
Example:
Router(config)# ip sla logging traps
(Optional) Enables IP SLAs syslog messages from CISCO-RTTMON-MIB.
Step 15
exit
Example:
Router(config)# exit
Exits to privileged EXEC mode.
What to Do Next
When you are finished configuring this MEP, see the "Scheduling IP SLAs Operations" section to schedule the operation.
Scheduling IP SLAs Operations
Note
All IP SLAs operations to be scheduled must be already configured.
The frequency of all operations scheduled in a multioperation group must be the same.
The list of one or more operation ID numbers to be added to a multioperation group is limited to a maximum of 125 characters in length, including commas (,).
The following sample output shows the configuration, including default values, of a receiver MEP on the responder device for a dual-ended Ethernet delay or delay variation operation:
Router# show ip sla configuration 501
IP SLAs Infrastructure Engine-III
Entry number: 501
Owner: admin
Tag:
Operation timeout (milliseconds): 5000
Ethernet Y1731 Delay Operation
Frame Type: 1DM
Domain: xxx
ReceiveOnly: TRUE
Evc: yyy
Local Mpid: 101
CoS: 3
Max Delay: 5000
Threshold (milliseconds): 5000
.
.
.
Statistics Parameters
Aggregation Period: 900
Frame offset: 1
Distribution Delay One-Way:
Number of Bins 10
Bin Boundaries: 5000,10000,15000,20000,25000,30000,35000,40000,45000,-1
Distribution Delay-Variation One-Way:
Number of Bins 10
Bin Boundaries: 5000,10000,15000,20000,25000,30000,35000,40000,45000,-1
History
Number of intervals: 2
The following sample output shows the configuration, including default values, of the sender MEP for a dual-ended IP SLAs Ethernet delay or delay variation operation:
Example: Sender MEP for a Single-Ended Ethernet Delay Operation
The following sample output shows the configuration, including default values, of the sender MEP for a single-ended IP SLAs Ethernet delay operation:
Router# show ip sla configuration 10
IP SLAs Infrastructure Engine-III
Entry number: 10
Owner:
Tag:
Operation timeout (milliseconds): 5000
Ethernet Y1731 Delay Operation
Frame Type: DMM
Domain: xxx
Vlan: yyy
Target Mpid: 101
Source Mpid: 100
CoS: 4
Max Delay: 5000
Request size (Padding portion): 64
Frame Interval: 1000
Clock: Not In Sync
Threshold (milliseconds): 5000
.
.
.
Statistics Parameters
Aggregation Period: 900
Frame offset: 1
Distribution Delay Two-Way:
Number of Bins 10
Bin Boundaries: 5000,10000,15000,20000,25000,30000,35000,40000,45000,-1
Distribution Delay-Variation Two-Way:
Number of Bins 10
Bin Boundaries: 5000,10000,15000,20000,25000,30000,35000,40000,45000,-1
History
Number of intervals: 2
Example: CoS-Level Monitoring for MEPs in Single-Ended Ethernet Frame Loss Ratio Operation
You must enable CoS-level monitoring for the sender and destination MEPs associated with an IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) frame loss probe. The following sample output shows how to configure probe-monitoring frames on an EVC with CoS 5:
Router-1# show running interface gigabitethernet2/3
interface GigabitEthernet2/3
service instance 101 ethernet evc-sample-1
encapsulation dot1q 777
rewrite ingress tag pop 1 symmetric
xconnect 102.102.102.102 777777 encapsulation mpls
cfm mep domain md-sample mpid 1
monitor loss counter priority 5
The following sample output shows how to configure an MEP for monitoring frame loss for frames on an EVC regardless of the CoS value (any CoS or Aggregate CoS cases).
Router-1# show running interface gigabitethernet2/3
interface GigabitEthernet2/3
service instance 102 ethernet evc-sample-2
encapsulation dot1q 888
rewrite ingress tag pop 1 symmetric
xconnect 102.102.102.102 888888 encapsulation mpls
cfm mep domain md-sample mpid 1
COS 5
monitor loss counter
Example: Sender MEP for a Single-Ended Ethernet Frame Loss Operation
The following output shows the configuration, including default values, of the sender MEP in a basic single-ended IP SLAs Ethernet frame loss ratio operation with a start-time of now:
Router# show ip sla configuration 11
IP SLAs Infrastructure Engine-III
Entry number: 11
Owner:
Tag:
Operation timeout (milliseconds): 5000
Ethernet Y1731 Loss Operation
Frame Type: LMM
Domain: xxx
Vlan: 12
Target Mpid: 34
Source Mpid: 23
CoS: 4
Request size (Padding portion): 0
Frame Interval: 1000
Schedule:
Operation frequency (seconds): 60 (not considered if randomly scheduled)
Next Scheduled Start Time: Start Time already passed
Group Scheduled : FALSE
Randomly Scheduled : FALSE
Life (seconds): 3600
Entry Ageout (seconds): never
Recurring (Starting Everyday): FALSE
Status of entry (SNMP RowStatus): ActiveThreshold (milliseconds): 5000
Statistics Parameters
Aggregation Period: 900
Frame consecutive: 10
Availability algorithm: static-window
History
Number of intervals: 2
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.
Feature Information for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1
Feature Information for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731)
Feature Name
Releases
Feature Information
IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731)
15.1(2)S
This feature provides the capability to gather Ethernet-layer network performance metrics, such as frame delay, frame delay variation, and frame loss ratio (as defined by the ITU-T Y.1737 networking standard), for assisting with IP SLAs assurance and capacity planning .
The following commands were introduced or modified:
aggregateinterval,
availability,
distribution,
ethernety1731delay,
ethernety1731delayreceive,
ethernety1731loss,
frameconsecutive,
frameinterval,
frame offset,
frame size,
history
interval,
ipslareaction-configuration,
max-delay,
owner,
show ipslahistoryinterval.
Y1731 MIB Support through existing IPSLA MIBs
15.2(2)S
Support was added for reporting threshold events and collecting performance statistics for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) operations using SNMP.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.