- Using Ethernet Operations Administration and Maintenance
- Configuring Ethernet Connectivity Fault Management in a Service Provider Network
- CFM CCM Extensions to Support the NSN Microwave 1+1 Hot Standby Protocol
- Configuring Ethernet CFM for the Cisco ASR 1000 Router
- Configuring Ethernet Virtual Connections on the Cisco ASR 1000 Series Router
- Using the IEEE 802.3ad Link Aggregation MIB
- Configuring IEEE 802.3ad Link Bundling
- ITU-T Y.1731 Performance Monitoring in a Service Provider Network
- ICCP Multichassis VLAN Redundancy
- Trunk EFP Support
- ITU-T G.8032 Ethernet Ring Protection Switching
- Layer 2 Access Control Lists on EVCs
- Configuring MAC Address Limiting on Service Instances Bridge Domains and EVC Port Channels
- Configuring Ethernet Local Management Interface at a Provider Edge
- Using Link Layer Discovery Protocol in Multivendor Networks
- Configuring ITU-T Y.1731 Fault Management Functions in IEEE CFM
- G.8032 and CFM Support for Microwave Adaptive Bandwidth
- Configuring IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
- IPSLA Y1731 On-Demand and Concurrent Operations
- VXLAN-MCLAG Active-Active High Availability Support
- Cisco ASR 1000 VxLAN Support
- Finding Feature Information
- Prerequisites for ITU-T Y.1731 Operations
- Restrictions for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731)
- Configuring IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
- How to Configure IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
- Configuration Examples for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
- Additional References for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
- Feature Information for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
Configuring IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
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:
- Finding Feature Information
- Prerequisites for ITU-T Y.1731 Operations
- Restrictions for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731)
- Configuring IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
Finding Feature Information
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.
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.
Prerequisites for ITU-T Y.1731 Operations
IEEE-compliant Connectivity Fault Management (CFM) must be configured and enabled for Y.1731 performance monitoring to function.
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.
Frame Loss Measurement is not supported on Cisco ME 3600X Series and 3800X Series Ethernet Access Switches.
P2 IMs are to be used for CFM and Y1731
Do not configure rewrite on the EFPs throughout the l2 circuit to avoid losing the cos value.
CFMoXconnect on ASR903 works only if the control-word is switched on. To start DM timestamping, switch on the control-word if the remote end is not switched on.
To avoid errors in RX and TX timestamping, ensure to have Y1731 sender as PTP master, and the Y1731 responder as PTP slave.
Reconfigure IP SLA Y1731 while doing online insertion removal (OIR) of IM or router reload because local MEP is deleted during the course.
Configuring IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
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:
- How to Configure IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
- Configuration Examples for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
- Additional References for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
- Feature Information for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
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
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.
1.
enable
2.
configure
terminal
3.
ip
sla
operation-number
4.
ethernet
y1731
delay
receive
1DM
domain
domain-name {evc
evc-id |
vlan
vlan-id}
cos
cos {mpid
source-mp-id |
mac-address
source-address}
5.
aggregate
interval
seconds
6.
distribution {delay |
delay-variation}
one-way
number-of-bins
boundary[,...,boundary]
7.
frame
offset
offset-value
8.
history
interval
intervals-stored
9.
max-delay
milliseconds
10.
owner
owner-id
11.
end
DETAILED STEPS
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
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.
1.
enable
2.
configure
terminal
3.
ip
sla
operation-number
4.
ethernet
y1731
delay
1DM
domain
domain-name {evc
evc-id |
vlan
vlan-id} {mpid
target-mp-id |
mac-address
target-address}
cos
cos {source {mpid
source-mp-id |
mac-address
source-address}}
5.
aggregate
interval
seconds
6.
frame
interval
milliseconds
7.
frame
size
bytes
8.
history
interval
intervals-stored
9.
owner
owner-id
10.
end
DETAILED STEPS
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.
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.
Note | To display information about remote (target) MEPs on destination devices, use the show ethernet cfm maintenance-points remote command. |
1.
enable
2.
configure
terminal
3.
ip
sla
operation-number
4.
ethernet
y1731
delay {DMM |
DMMv1} [burst]
domain
domain-name {evc
evc-id |
vlan
vlan-id} {mpid
target-mp-id |
mac-address
target-address}
cos
cos {source {mpid
source-mp-id |
mac-address
source-address}}
5.
clock
sync
6.
aggregate
interval
seconds
7.
distribution {delay |
delay-variation}
one-way
number-of-bins
boundary[,...,boundary]
8.
frame
interval
milliseconds
9.
frame
offset
offset-value
10.
frame
size
bytes
11.
history
interval
intervals-stored
12.
max-delay
milliseconds
13.
owner
owner-id
14.
end
DETAILED STEPS
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 show ethernet cfm maintenance-points remote command. |
Perform this task to configure a sender MEP on the source device.
-
Class of Service (CoS)-level monitoring must be enabled on MEPs associated to the Ethernet frame loss operation by using the monitor loss counter 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.
1.
enable
2.
configure
terminal
3.
ip
sla
operation-number
4.
ethernet
y1731
loss {LMM |
SLM} [burst]
domain
domain-name {evc
evc-id |
vlan
vlan-id} {mpid
target-mp-id |
mac-address
target-address}
CoS
CoS {source {mpid
source-mp-id |
mac-address
source-address}}
5.
aggregate
interval
seconds
6.
availability
algorithm {sliding-window |
static-window}
7.
frame
consecutive
value
8.
frame
interval
milliseconds
9.
history
interval
intervals-stored
10.
owner
owner-id
11.
exit
12.
exit
13.
exit
DETAILED STEPS
When you are finished configuring this MEP, see the "Scheduling IP SLAs Operations" section to schedule the operation.
Scheduling IP SLAs Operations
- All IP Service Level Agreements (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 must be limited to a maximum of 125 characters in length, including commas (,).
- ip sla schedule operation-number [life {forever | seconds}] [start-time {[hh:mm:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring]
- ip sla group schedule group-operation-number operation-id-numbers {schedule-period schedule-period-range | schedule-together} [ageout seconds] [frequency group-operation-frequency] [life {forever | seconds}] [start-time {hh:mm [:ss] [month day | day month] | pending | now | after hh:mm [:ss]}]
1.
enable
2.
configure terminal
3.
Enter one of the following commands:
4.
end
5.
show
ip
sla
group
schedule
6.
show
ip
sla
configuration
DETAILED STEPS
Configuration Examples for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
Example: Dual-Ended Ethernet Delay Operation
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:
Device# 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:
Device# show ip sla configuration 500 IP SLAs Infrastructure Engine-III Entry number: 500 Owner: Tag: Operation timeout (milliseconds): 5000 Ethernet Y1731 Delay Operation Frame Type: 1DM Domain: yyy ReceiveOnly: FALSE Evc: xxx Target Mpid: 101 Source Mpid: 100 CoS: 3 Request size (Padding portion): 64 Frame Interval: 1000 Threshold (milliseconds): 5000 . . . Statistics Parameters Aggregation Period: 900 Frame offset: 1 History Number of intervals: 22
Example: Frame Delay and Frame Delay Variation Measurement Configuration
The following sample output shows the performance monitoring session summary:
Device# show ethernet cfm pm session summary Number of Configured Session : 2 Number of Active Session: 2 Number of Inactive Session: 0
The following sample output shows the active performance monitoring session:
Device# show ethernet cfm pm session active Display of Active Session -------------------------------------------------------------------------------- EPM-ID SLA-ID Lvl/Type/ID/Cos/Dir Src-Mac-address Dst-Mac-address -------------------------------------------------------------------------------- 0 10 3/BD-V/10/2/Down d0c2.8216.c9d7 d0c2.8216.27a3 1 11 3/BD-V/10/3/Down d0c2.8216.c9d7 d0c2.8216.27a3 Total number of Active Session: 2
Device# show ethernet cfm pm session db 0 ---------------------------------------------------------------------------- TX Time FWD RX Time FWD TX Time BWD RX Time BWD Frame Delay Sec:nSec Sec:nSec Sec:nSec ---------------------------------------------------------------------------- Session ID: 0 **************************************************************************** 234:526163572 245:305791416 245:306761904 234:527134653 0:593 **************************************************************************** 235:528900628 246:308528744 246:309452848 235:529825333 0:601 **************************************************************************** 236:528882716 247:308511128 247:309450224 236:529822413 0:601 **************************************************************************** 237:526578788 248:306207432 248:307157936 237:527529885 0:593 **************************************************************************** 238:527052156 249:306681064 249:307588016 238:527959717 0:609 **************************************************************************** 239:526625044 250:306254200 250:307091888 239:527463325 0:593 **************************************************************************** 240:528243204 251:307872648 251:308856880 240:529228021 0:585
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: 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
Additional References for IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
Related Documents
Related Topic |
Document Title |
---|---|
Cisco IOS commands |
|
Cisco IOS Carrier Ethernet commands |
|
Cisco IOS IP SLAs commands |
|
Ethernet CFM |
“Configuring Ethernet Connectivity Fault Management in a Service Provider Network” module of the Cisco IOS Carrier Ethernet Configuration Guide |
Network Time Protocol (NTP) |
“Configuring NTP” module of the Cisco IOS Network Management Configuration Guide |
Proactive threshold monitoring for Cisco IOS IP SLAs |
“Configuring Proactive Threshold Monitoring of IP SLAs Operations” module of the Cisco IOS IP SLAs Configuration Guide |
Standards and RFCs
Standard/RFC |
Title |
---|---|
ITU-T Y.1731 |
OAM functions and mechanisms for Ethernet-based networks |
No specific RFCs are supported by the features in this document. |
-- |
MIBs
MIB |
MIBs Link |
---|---|
|
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
Technical Assistance
Description |
Link |
---|---|
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.
Feature Name |
Releases |
Feature Information |
---|---|---|
IP SLA Support for ETH-SLM (Ethernet Synthetic Loss Measurement in Y1731) |
Cisco IOS XE Release 3.8S |
Y.1731 Performance Monitoring (PM) provides a standard Ethernet PM function that includes measurement of Ethernet frame delay, frame delay variation, frame loss, and frame throughput measurements specified by the ITU-T Y-1731 standard and interpreted by the Metro Ethernet Forum (MEF) standards group. In Cisco IOS XE Release 3.8S, support was added for Cisco ASR 900 Series. |
Y1731 MIB Support through existing IPSLA MIBs |
Cisco IOS XE Release 3.8S |
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. |