Transcript
Agenda
Protocol Overview IEEE 8023ah (clause 57) IEEE 8021ag ITU Y1731 MEF E-LMI
OAM Inter-Working
Fault Management scenarios
Performance Management
Drivers for Ethernet OAM
OAM benchmarks
Set by TDM and existing WAN technologies
Operational Efficiency Reduce OPEX, avoid truck-rolls Downtime cost
Management Complexity
Large Span Networks
Multiple constituent networks belong to disparate organizations/companies
Problem Taxonomy
Ethernet OAM
Decoder Ring
IEEE 8021ag Connectivity Fault Management (CFM) Also referred as Service OAM
IEEE 8023ah (clause 57) Ethernet Link OAM Also referred as 8023 OAM, Link OAM or Ethernet in the First
Mile (EFM) OAM
ITU-T Y1731 OAM functions and mechanisms for Ethernet-based networks
MEF E-LMI Ethernet Local Management Interface
Ethernet OAM
Building Blocks
BRKOPT-2202_c1 ⓒ 2009 Cisco Systems, Inc All rights reserved Cisco Public
Cisco Carrier Ethernet OAM
Cisco Public
Cisco Carrier Ethernet OAM
Protocol Positioning
ConnectivityCustomer E-LMI Fault Management
AccessCore Access Customer
Business
Business Backbone
Backbone Bridges
Bridges Provider
Provider Bridges
Bridges
MPLS
Residential Residential
OAMEthernet
IP/MPLS
Link OAM
UNI NNI NNI NNI UNI
E-LMIUser to Network Interface (UNI)
Link OAMAny point-point 8023 link
CFMEnd-to-End UNI to UNI
MPLS OAMwithin MPLS cloud
Link OAM (IEEE 8023ah, Clause 57)
Provides mechanisms useful
for “monitoring link operation”,
such as:
OSI Model
Application
Presentation
Session
Transport
Network
Data Link
Physical
LAN Link Monitoring
CSMA/CDLayers
Remote Failure Indication
Remote Loopback Control
Defines an optional OAM sublayer
Intended for single point-to-point IEEE 8023 links
Uses “Slow Protocol”1 frames called OAMPDUs which are never forwarded by MAC clients
Standardized: IEEE 8023ah, clause 57 (now in IEEE 8023-2005)
Higher Layers
LLC
OAM (Optional)
MAC
Physical Layer
(1) No more than 10 frames transmitted in any one-second period
IEEE 8023ah
Key Functions
OAM discovery Discover OAM support and capabilities per device
Link monitoring
basic error definitions for Ethernet so entities can detect failed and degraded connections
Fault signaling
mechanisms for one entity to signal another that it has detected an error
Remote loopback
used to troubleshoot networks, allows one station to put the other station into a state whereby all inbound traffic is immediately reflected back onto the link
IEEE 8023ah
OAM Events
Set of events that may impact link operation
Critical Link events Link faultFault in the Rx direction of local DTE Dying gaspUnrecoverable local failure condition Critical eventUnspecified critical event
Link events Errored Symbol Period Event Errored Frame Event Errored Frame Period Event Errored Frame Seconds Summary Event
IEEE 8023ah
Remote Loopback
Fault localization and link performance testing
Loopback Control OAMPDU is used to control a remote OAM client
Traffic sent from master loopback port is loopback by slave port, except Pause and OAMPDU
OAM
MAC
PHY
OAM
MAC
PHY
Master OAM
Slave OAM
CFM Overview
Family of protocols that provides capabilities to detect, verify, isolate and report end-to-end ethernet connectivity faults
Employs regular Ethernet frames that travel in-band with the customer traffic
Devices that cannot interpret CFM Messages forward them as normal data frames
CFM frames are distinguishable by Ether-Type (0x8902) and dMAC address (for multicast messages)
Standardized by IEEE in late 2007
IEEE std 8021ag-2007
CFM Overview (Cont)
Key CFM mechanisms include:
Nested Maintenance Domains (MDs) that break up the responsibilities for network administration of a given end-toend service
Maintenance Associations (MAs) that monitor service instances under a given MD
Maintenance Points (MPs) that generate and respond to CFM PDUs
Protocols (Continuity Check, Loopback and Linktrace) used for Fault Management activities
CFM Concepts
Maintenance Domain (MD)
Defined by Operational/Contractual Boundaries
eg Customer/Service Provider/Operator
MD may nest and touch, but never intersect
Up to 8 levels of “nesting”: MD Level (07) The higher the level, the broader its reach
MD Name Format: null, MAC address, DNS or string-based
Maintenance Domain Nesting
CFM Concepts
Maintenance Association (MA)
Monitors connectivity of a particular service instance in a given MD
(eg 1 service traversing 4 MDs = 4 MAs)
Defined by a set of Maintenance End Points (MEP) at the edgeof a domain
Identified by MAID == “Short MA” Name + MD Name
Short MA Name Format: Vlan-ID, VPN-ID, integer or string-based
CFM Concepts
Maintenance Point (MP)MEP
Maintenance Association End Point (MEP)
Define the boundaries of a MD
Support the detection of connectivity failures between any pair ofMEPs in an MA
Associated per MA and identified by a MEPID (1-8191)
Can initiate and respond to CFM PDUs
CFM Concepts
Maintenance Point (MP)MIP
MEP
MIP MIP MEP
MEP MEP
MEP MEP MIP MIP MIP MIP MIP MIP MIP
MIP
MIP MIP
Maintenance Domain Intermediate Point (MIP)
Support the discovery of paths among MEPs and location of faultsalong those paths
Can be associated per MD and VLAN / EVC (manually or automatically created)
Can add, check and respond to received CFM PDUs
CFM Concepts
UP / Inward-facing MEP
CFM PDUs generated by the MEP are sent towards the Bridge’s Relay Function and not via the wire connected to the port where the MEP isconfigured
CFM PDUs to be respondedby the MEP are expected toarrive via the Bridge’s Relay Function
Applicable to switches
CFM Concepts
DOWN / Outward-facing MEP
CFM PDUs generated by the MEP are sent via the wire connected to the port wherethe MEP is configured
CFM PDUs to be respondedby the MEP are expected toarrive via the wire connected to the port where the MEP isconfigured
Port MEP special DownMEP at level zero (0) used todetect faults at the link level (rather than service)
Applicable to routers and switches
CFM Concepts
MAs and UP/DOWN MEPs
Applicability of UP/DOWNMEPs in switches:
DOWN MEPs are typicallyused for MAs spanning asingle link
UP MEPs are commonly usedfor MAs with a wider reach
(eg end-to-end, beyond asingle link
CFM Protocols
There are three (3) protocols defined by CFM
Continuity Check Protocol Fault Detection Fault Notification
Loopback Protocol Fault Verification
Linktrace Protocol Fault Isolation
CFM Protocols
Continuity Check Protocol
Used for Fault Detection and Notification
Per-Maintenance Association multicast “heart-beat” messages
Transmitted at a configurable periodic interval by MEPs (33ms, 10ms, 100ms, 1s, 10s, 1m,
10m)
Uni-directional (no response required)
Carries status of port on which MEP is configured
Catalogued by MIPs at the same MD-Level, Terminated by remote MEPs in the same MA
BRKOPT-2202_c1 ⓒ 2009 Cisco Systems, Inc All rights reserved Cisco Public
CFM Protocols
Continuity Check ProtocolFault Detection
Defect Name Detectable Faults
DefXconCCM Reception by a MEP of a CCM with an incorrect MAID (cross connect error)
Reception by a MEP of a CCM with an incorrect transmission interval
DefErrorCCM Reception by a MEP of a CCM with an incorrect MEPID (duplicate mpid error)
Reception by a MEP of its own CCM
Reception by a MEP of a CCM with an MD Level lower than that of the MEP
Inability to receive consecutive CCMs from any one of the other MEPs in its MA
DefRemoteCCM Inability to receive CCMs from any one of the MEPs configured in a static list
Reception by a MEP of a CCM from a MEPs not included in a static list
DefMACstatus Reception by a MEP of a CCM containing a Port Status TLV or Interface Status TLV indicating a failed port
DefRDICCM Reception by a MEP of a CCM with the Remote Defect Indicator (RDI) bit set
CFM Protocols
Loopback Protocol
CE Operator A Operator B CE
Used for Fault VerificationEthernet Ping
MEP can transmit a unicast LBM to a MEP or MIP in the same MA
Receiving MP responds by transforming the LBM into a unicast LBR sent back to the originating MEP
CFM Protocols
Linktrace Protocol
Used for Path Discovery and Fault IsolationEthernet Traceroute
MEP can transmit a multicast message (LTM) in order to discover the MPs and path to a MIP or MEP in the same MA
Each MIP along the path and the terminating MP return a unicast LTR to originating MEP
CFM Protocols
Putting Everything Together
Run Connectivity Check to proactively detect a soft or hard failure
Upon a failure detection, use Loopback to verify it
Upon verification, run Traceroute to isolate it; multiple segment LPs can also be used to isolate the fault
If the isolated fault points to a virtual circuit, then the OAM tools for that technology can be used to further fault isolationeg, for MPLS PW, VCCV and MPLS ping can be used
Troubleshooting: Example
CFM Deployment
Scenario A
CE1 Access 1 Aggregation 1 Aggregation 2 Access 2 CE2
CFM Deployment
Scenario A (Cont)
CE1 Access 1 Aggregation 1 Aggregation 2 Access 2 CE2
Customer Domain
SP Domain
Link Domain
MIP
MEP
CFM Deployment
Scenario B
CE1 Access 1 Aggregation 1 Aggregation 2 Access 2 CE2
CFM Deployment
Scenario B (Cont)
CE1 Access 1 Aggregation 1 Aggregation 2 Access 2 CE2
Customer Domain
OperatorDomain
Link Domain
MIP
MEP
Cisco IOS CFM Implementation
Cisco IOS Details
IEEE 8021ag supported across the CE / CPE, Access and Aggregation product lines
CFM IOS shipping implementation is based on IEEE 8021ag draft 10 (circa 2004)
Procedural and Frame changes prevent interoperability with standard-based CFM implementations
Support for standard IEEE 8021ag-2007 is scheduled for Q3-Q4 CY 2009
Cisco IOS Area Edge Bridge (AEB) feature performs message translation to allow interoperability between draft 10 and standard CFM
All three (3) IEEE 8021ag protocols supported: Continuity Check, Loopback and Linktrace
Cisco IOS CFM Implementation
Cisco IOS Details (Cont)
interface GigabitEthernet2/2 switchport trunk allowed vlan 500 switchport mode trunk
ethernet cfm mip … ethernet cfm mep …
interface GigabitEthernet2/2
ethernet cfm mep …
interface GigabitEthernet2/2500 encapsulation dot1q 500 ip address 1111 25525500
interface GigabitEthernet2/2 service instance 1 ethernet encapsulation dot1q 500
bridge-domain 100
cfm mip …
cfm mep …
Cisco IOS CFM Implementation
Cisco IOS Details (Cont)
interface GigabitEthernet2/2 service instance 1 ethernet encapsulation dot1q 500 xconnect 2222 111 … cfm mip … cfm mep …
l2 vfi blue manual vpn id 100 bridge-domain 10 vlan neighbor 11001 … neighbor 11002 …
cfm mep …
Standard CFM
Cisco CFM Implementation
Implementation
End-to-End CFM on Switchport Example
UNI NNI
Global Configuration
MEP
Manual MIP
BRKOPT-2202_c1 ⓒ 2009 Cisco Systems, Inc All rights reserved Cisco Public 41
Standard CFM
Cisco CFM Implementation
Implementation
End-to-End CFM on Switchport example (Cont)
Global Configuration
MIPs are created on all interfaces that VLAN 500 is allowed, and VLAN 500 is not specifically associated with a Domain/Service
NNI NNI
interface GigabitEthernet2/2 switchport trunk allowed vlan 500 switchport mode trunk
Standard CFM
Cisco CFM Implementation
Implementation
End-to-End CFM on Switchport example (Cont)
ITU-T Y1731 Overview
ITU-T recommendation that provides mechanisms for user-plane OAM functionality in Ethernet networks Covers:
Fault Management mechanisms
Performance Management mechanisms
Standardized by ITU-T SG 13 in May 2006
A new pre-published version dated Feb 2008 after IEEE 8021ag standardization
Frames format (Multicast Address, Ethertype, and common OAM PDU fields ) and base functionality are generally agreed across IEEE 8021ag and Y1731
Comparison with IEEE 8021ag
ITU-T Y1731 Terminology
IEEE 8021ag ITU-T Y1731
ME Maintenance Entity ME Maintenance Entity
MA Maintenance Association MEG ME Group
MAID MA Identifier MEGID MEG Identifier
MD Maintenance Domain -- No such construct available
MD Level MD Level MEG Level MEG Level
MEP MA End Point MEP MEG End Point
MIP MD Intermediate Point MIP MEG Intermediate Point
#NAME?
ITU-T Y1731 Overview
OAM Functions for Fault Management
Ethernet Continuity Check (ETH-CC) (Y1731 adds unicast CCM) Covered by Ethernet Loopback (ETH-LB) (Y1731 adds multicast LBM)
IEEE 8021ag
Ethernet Linktrace (ETH-LT)
Ethernet Remote Defect Indication (ETH-RDI)
Ethernet Alarm Indication Signal (ETH-AIS)
Ethernet Locked Signal (ETH-LCK)
In addition: ETH-TEST, ETH-APS, ETH-MCC, ETH-EXP, ETH-VSP
OAM Functions for Performance Management
Frame Loss Measurement (ETH-LM)
Frame Delay Measurement (ETH-DM)
Ethernet LMI
Overview
Provides protocol and mechanisms used for:
Notification of EVC addition, deletion or status (Active, Not Active, Partially Active) to CE User Network Interface
Communication of UNI and EVC attributes to CE (eg CE-VLAN to EVC map)
UNI-C
Cisco Enhancement CE auto-configuration
Notification of Remote UNI name and status to CE CE
Asymmetric protocol based on
E-LMI
Frame Relay LMI, mainly applicable
to the UNI (UNI-C and UNI-N)
Specification completed by MEF:
http://wwwmetroethernetforum
org/PDFs/Standards/MEF16doc
Ethernet LMI
Periodic Polling and Asynchronous Update
ELMI-CE (UNI-C) ELMI-PE (UNI-N)
Based on polling
procedure invoked
by CE
N391Polling Counter,
polling cycles between
Full Status exchanges
D
N393Status
Counter, number of
consecutive errors
T391Polling Timer
(PT), UNI-C transmits
Status Enq
T392Polling Verification
Timer (PVT), timer by
which UNI-N expects to
be polled
BRKOPT-2202_c1 ⓒ 2009 Cisco Systems, Inc All rights reserved Cisco Public
50
What Is OAM Interworking?
Operator A Operator B
Strict OAM layering should be honored: messages should not cross layers
Customer Bridge
OAM Messages should not leak outside domain
boundaries within a layer
Interworking is event translations & not
necessarily 1:1 message mapping
Edge Router
ATM Switch ATM Switch
Bridge
Bridge
Router
Router
Router
Bridge
switch
switch
Edge Bridge
Customer Bridge
Interworking may be inter-layer and intra-layer
Event Translation inter-
Ethernet Ethernet 10G ATM
over SONET over MPLS Ethernet RFC1483
domains intra-layer
Service OAM
Server Layers feed events into Client Layers
Network Network OAM OAM
Transport Transport Transport Transport
OAM OAM OAM OAM
Interworking Scenarios
Main Examples Supported by Cisco IOS
Interworking Scenarios
CFM to E-LMI
CFM @ Provider Level acts as MEN OAM: provides EVC Status
and Remote UNI Status/Name to E-LMI Interface Status TLV of CC Messages carry remote UNI status Cisco’s Organization-specific TLV of CC Messages carry remote UNI name Status of remote MEP in CCDB indicates EVC State
Interworking Scenarios
8023ah to CFM (CC-based)
Customer
Service Provider
CE
MPLS Aggregation
Ethernet
Ethernet
Access
Access
CE 1 uPE 11 PE-Agg nPE 11 nPE 31 uPE 31 CE 31
Service Layer OAM
CC
Transport Layer OAM
8023ah to CFM I/W
8023ah
Link Layer Defects detected by 8023ah, relayed to CFM on same device
CFM notifies remote devices of localized fault
Two variants: CC based (8023ah on edge of domain) AIS based (8023ah within domain)
Interworking Scenarios
8023ah to CFM (AIS-based)
Customer
Service Provider
CE
MPLS Aggregation
Ethernet
Ethernet
Access
Access
CE 1 uPE 11 nPE 11 PE-Agg nPE 31 uPE 31 CE 31 Service
Layer OAM
AIS AIS
Transport Layer OAM
8023ah to CFM I/W 8023ah
Link Layer Defects detected by 8023ah, relayed to CFM on same device
CFM notifies remote devices of localized fault
Two variants: CC based (8023ah on edge of domain) AIS based (8023ah within domain)
Interworking Scenarios
MPLS PW OAM to E-LMI
Service Layer
OAM
Transport
Layer OAM
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
CE Access Aggregation Aggregation Access CE
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
CE Access Aggregation Aggregation Access CE
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
CFM Continuity Check Messages (CCM)
UPE11#show ethernet cfm maintenance-points remote CCM -------------------------------------------------------------------------------MPID Domain Name MacAddress IfSt PtStDatabase Lvl Domain ID Ingress RDI MA Name Type Id SrvcInst EVC Name Age
3100 PROVIDER_DOMAIN aabbcc000599 Up Up4 PROVIDER_DOMAIN Et0/1100
customer_100_provider Vlan 100 N/A N/A 0s
Total Remote MEPs: 1
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
uPE11# ping ethernet
CFM Loopback Reply (LBR)
UPE11#ping ethernet mpid 3100 domain PROVIDER_DOMAIN vlan 100
Type escape sequence to abort
Sending 5 Ethernet CFM loopback messages to aabbcc000599, timeout is 5 seconds
:!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/5/12 ms
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
uPE11# traceroute ethernet
CFM Linktrace Message (LTM) CFM Linktrace Reply (LTR)
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
uPE11# traceroute ethernet
UPE11#traceroute ethernet mpid 3100 domain PROVIDER_DOMAIN vlan 100Type escape sequence to abort TTL 64 Linktrace Timeout is 5 secondsTracing the route to aabbcc000599 on Domain PROVIDER_DOMAIN, Level 4, vlan 100 Traceroute sent via Ethernet0/1100, path found via MPDB
B = Intermediary Bridge
! = Target Destination
* = Per hop Timeout
MAC Ingress Ingr Action Relay
Action
Hops Host Forwarded Egress Egr Action Previous
Hop
B 1 AGG11 aabbcc000399 Et0/0100 IngOk RlyMPDB
Forwarded Et0/1100 EgrOK aabbcc000299
B 2 AGG31 aabbcc000499 Et0/0100 IngOk RlyMPDB
Forwarded Et0/1100 EgrOK aabbcc000399
! 3 UPE31 aabbcc000599 Et0/0100 IngOk RlyHit:MEP
Not Forwarded aabbcc000499
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
ELMI Status Enquiry message (Full Status report)
ELMI Status message (Full Status report)
Example:
Cisco
enhancements to
ELMI
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
ELMI Status Enquiry message (Full Status report) ELMI Status message (Full Status report)
Network Stable: Remote UNI shows UP
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
CE Configured with the correct C-VLAN (eg vid 100)
CE11(config)#interface gig0/0100CE11(config-subif)#encapsulation dot1Q 100
CE11#show ip interface briefInterface IP-Address OK? Method Status Protocol <snip>GigabitEthernet0/0100 10010010011 YES NVRAM up up
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
CE Configured with the incorrect C-VLAN (eg vid 1300)
CE11(config)#interface gig0/0100CE11(config-subif)#encapsulation dot1Q 1300
Jan 26 00:15:39546: %ETHER_LMI-6-MISMATCHED_VLAN_NOT_CONFIGURED: VLAN 100 not Configured but in VLAN mapping for UNI GigabitEthernet0/0
Jan 26 00:15:39546: %ETHER_LMI-6-MISMATCHED_VLAN_CONFIGURED: VLAN 1300 configured but not in VLAN mapping for UNI GigabitEthernet0/0 Interface
CE11#show ip interface briefInterface IP-Address OK? Method Status Protocol <snip> GigabitEthernet0/0100 10010010011 YES NVRAM down down
Proactive ELMI Action
at CPE
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
CE Access Aggregation Aggregation Access CE
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
UPE11#
*Apr 8 04:33:44911: %E_CFM-3-REMOTE_MEP_DOWN: Remote MEP mpid 3100 vlan 100 MA name customer_100_provider in domain PROVIDER_DOMAIN changed state to down with event code TimeOut
*Apr 8 04:33:44911: %ETHER_SERVICE-6-EVC_STATUS_CHANGED: status of EVC_P2P_100 changed to InActive
*Apr 8 04:33:47587: %E_CFM-3-FAULT_ALARM: A fault has occurred in the network for the local MEP having mpid 1100 vlan 100 for service MA name customer_100_provider with the event code DefRemoteCCM
Error DB UPE11#show ethernt cfm errors
MPID Domain Id Mac Address Type Id Lvl MAName Reason Age
3100 PROVIDER_DOMAIN aabbcc000599 Vlan 100 4 customer_100_provider Lifetime Timer Expired 119s
Cisco-defined alarm
IEEE-defined alarm
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
UPE11#ping ethernet aabbcc000599 domain PROVIDER_DOMAIN vlan 100
Type escape sequence to abort
Sending 5 Ethernet CFM loopback messages to aabbcc000599, timeout is 5 seconds
:
Success rate is 0 percent (0/5)
UPE11#traceroute ethernet aabbcc000599 domain PROVIDER_DOMAIN vlan 100
Type escape sequence to abort TTL 64 Linktrace Timeout is 5 seconds
Tracing the route to aabbcc000599 on Domain PROVIDER_DOMAIN, Level 4, vlan 100
Traceroute sent via Ethernet0/1100, path found via MPDB
B = Intermediary Bridge
! = Target Destination
* = Per hop Timeout
MAC Ingress Ingr Action Relay Action Hops Host Forwarded Egress Egr Action Previous Hop
B 1 * AGG11 aabbcc000399 Et0/0100 Forwarded Et0/1100 EgrOK IngOk RlyMPDB aabbcc000299
*
*
*
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
CE11#
*Apr 8 04:33:44991: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0100, changed state to down
CE11#show ethernet lmi evc detail EVC_P2P_100 EVC Id: EVC_P2P_100 interface Ethernet0/0
Time since Last Full Report: 00:01:13
Ether LMI Link Status: Up
UNI Status: Up
UNI Id: CE11_UNI
CE-VLAN/EVC Map Type: Service Multiplexing with no bundling
VLAN: 100
Network Failure:
EVC Status: Inactive
EVC Type: Point-to-Point
Remote UNI shows
Remote UNI Count: Configured = 1, Active = 0
UNREACHABLE
UNI Id UNI Status Port
-------------------CE31_UNI Unreachable Remote
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
CE Access Aggregation Aggregation Access CE
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
UPE11#
*Apr 8 04:41:54823: %E_CFM-6-REMOTE_MEP_UP: Continuity Check message isreceived from a remote MEP with mpid 3100 vlan 100 MA name customer_100_provider domain PROVIDER_DOMAIN interface status Down event code PortState
*Apr 8 04:41:54823: %ETHER_SERVICE-6-EVC_STATUS_CHANGED: status of EVC_P2P_100 changed to InActive
*Apr 8 04:41:57451: %E_CFM-3-FAULT_ALARM: A fault has occurred in the network for the local MEP having mpid 1100 vlan 100 for service MA name customer_100_provider with the event code DefMACstatus
UPE11#show ethernet cfm maintenance-point remote
MPID Domain Name
Lvl Domain ID
RDI MA Name
MacAddress IfSt PtSt
Ingress
Type Id SrvcInst
Age
EVC Name
3100 PROVIDER_DOMAIN aabbcc000599 Down Up 4 PROVIDER_DOMAIN Et0/1100
customer_100_provider Vlan 100 N/A
N/A 0s
Total Remote MEPs: 1
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
CE11#
*Apr 8 04:41:54907: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0100, changed state to down
CE11#show ethernet lmi evc detail EVC_P2P_100 EVC Id: EVC_P2P_100 interface Ethernet0/0
Time since Last Full Report: 00:01:07
Ether LMI Link Status: Up
UNI Status: Up
UNI Id: CE11_UNI
CE-VLAN/EVC Map Type: Service Multiplexing with no bundling
VLAN: 100
UNI Failure:
EVC Status: Inactive
Remote UNI shows DOWN
EVC Type: Point-to-Point
Remote UNI Count: Configured = 1, Active = 0
UNI Id UNI Status Port
-------------------
CE31_UNI Down Remote
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
CE Access Aggregation Aggregation Access CE
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
CE Access Aggregation Aggregation Access CE
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
Receive Errors detected by CE
CE Access Aggregation Aggregation Access CE
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
CE PE PECE
EoMPLS Pseudowire
Point-to-Point Ethernet Service
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
CE PE PECE
EoMPLS Pseudowire
E-LMI
Directed LDP session
E-LMI
PW OAM
PW OAM
To E-LMI IW
To E-LMI IW
OAM Protocol Positioning
Deploying Carrier Ethernet OAM
Ethernet Layer 2 VPN Services
CE PE PECE
EoMPLS Pseudowire
X
IP SLAs
Performance Management
IP SLAs Embedded Policy Management Scheduling Automation/Policy Alerts/Data Collection
In-band Performance Management Tool for Ethernet Delay, Delay Variation and Packet Loss measurement Built in CFM principles
Automatic Discovery of Probe Endpoints
IP SLA
CFM Integration Highlights
In-band Performance Management Tool for Ethernet
Use native Ethernet frames
IP not required
Built over CFM
Use Ethernet CFM frames to collect statistics
Probes performed in context of a VLAN and a CFM
Maintenance Domain
CFM MEPs define probe endpoints
Automatic Discovery of Probe Endpoints
Rely on CFM Continuity Check Database (CCDB)
to automatically discover Probe Endpoints
EVC and Maintenance Domain based
Support ‘static’ probes and exclusions
IP SLA
Ethernet Probe Types
Probe Type Capability
Echo Probe Per service, ethernet probe Uses CFM LBM/LBR PDUs Measures RTT
Jitter Probe Per service, ethernet probe Uses proprietary CFM messages Measures uni-directional packet loss, jitter and latency
IP SLA
Hierarchical Performance Management
SP Network
Access Core
Customer
Equipment N-PE 1 N-PE 3 U-PE D
CE U-PE A MPLS MPLS CE
Native
Ethernet
CE U-PE B N-PE 2 N-PE 4 U-PE C Native CE
Ethernet
MEP
Probe initiation/end point
Auto-discovers all other MEPs in Domain/VLAN
Customer Domain
Provider Domain
Operator Domain
SLA measurement operations in one domain are transparent to higher/lower domains
Allows for ‘segmented’, ‘composite’ and ‘end-to-end’ measurements
Follows CFM Maintenance Domain Hierarchical Model: Customer, Service Provider, Operator
IP SLA
Probe Endpoint Auto Discovery
Probe endpoints dynamically discovered for given VLAN within a Maintenance Domain
New probes automatically created for newly added endpoints (sites)
Add new site SP Network
Access Core
Customer Equipment C N-PE 1 N-PE 3 U-PE D B
CE U-PE A MPLS MPLS CE
Native
Ethernet
CE U-PE B N-PE 2 N-PE 4 U-PE C Native Ethernet A CE
Probe: VLAN 100 Domain SP1
A MPID AAAA
B MPID BBBB
Only need to configure new site CE for CFM,
C MPID CCCC
No changes to existing sites for SLA measurement
Acronyms
Acronym
AIS Alarm Indication Signal
CCM Continuity Check Message
CCMDB CCM Data Base (see CCM)
CE Customer Edge
CFM Connectivity Fault Management
EFM Ethernet in the First Mile
E-LMI Ethernet LMI (see LMI)
E-OAM Ethernet OAM (see OAM)
EVC Ethernet Virtual Connection
IEEE Institute of Electrical and Electronics Engineers
ITU International Telecommunication Union
LBM Loopback Message
LBR Loopback Reply
LMI Local Management Interface
LTM Linktrace Message
LTR Linktrace Reply
MA Maintenance Association
MAID MA Identifier (see MA)
MD Maintenance Domain
Acronym
MEF Metro Ethernet Forum
MEN Metro Ethernet Network
MEP Maintenance Association End Point
MEPID MEP Identifier (see MEP)
MHF MIP Half Function (see MIP)
MIB Management Information Base
MIP Maintenance Domain Intermediate Point
MP Maintenance Point
OAM Operations, Administration and Maintenance
PDU Protocol Data Unit
PE Provide Edge
RDI Remote Defect Indicator
RFI Remote Failure Indicator
TLV Type, Length, Value
UNI User to Network Interface
UNI-C Customer side of UNI (see UNI)
UNI-N Network side of UNI (see UNI)
VID VLAN Identifier
VLAN Virtual LAN
Acknowledgement
Jose Liste, TME-Cisco Systems