76.8600-50133B Ethernet Config

Tellabs 8600 Managed Edge System
Ethernet Configuration Guide

76.8600-50133B
24.08.2011
Document Information
Revision History
Document No.
Date
Description of Changes
76.8600-50133B
24.08.2011
Ethernet MAC switching support added in chapters 2.1 and 2.5.2.

Ethernet pseudowire application example added in chapter 2.2.1.
Internal Ethernet/VLAN bridging data added in chapter 2.2.3.
Ethernet pseudowire virtual circuit connectivity verification support
added in chapter 2.2.4.
Integrated routing and bridging support added in chapters 2.4 and
2.5.3.
[Y.1731] frame loss support added in chapter 3.1.3, 3.1.4, 3.2.1,
3.2.2, 3.2.3, 3.2.4, 3.2.5 and 3.2.6.
[IEEE 802.1ag]/[Y.1731] Ethernet OAM Performance Management:
delay, jitter (DMM/DMR) added in chapters 3.1.3, 3.2.7, 3.2.8 and
3.2.9.
Link Aggregation level statistics examples added in chapter 4.7.10.
[IEEE 802.1ag]/[Y.1731] Ethernet OAM support in ELP interface is
covered in chapters 5 and 3.2.8.
Data on allowed ELP mode combinations added in chapter 5.2.5.
CLI example on Tellabs 8600 network element connected to third
party equipment supporting Ethernet link aggregation added in
chapter 5.3.1.
Microwave radio 1+1 HSBY protection support added in chapter 6.
Support for new products Tellabs 8609 access switch added.
Support for new product Tellabs 8611 access switch added.
76.8600-50133A
20.12.2010
Initial release of the document.
This manual documents the following network elements and the corresponding feature packs or
higher:
Tellabs 8605 access switch
FP1.5
FP1.1
FP1.0
FP1.1
Tellabs 8620 access switch, Tellabs 8630 access switch, Tellabs 8660 edge switch
FP3.1
2011 Tellabs. All rights reserved.

This Tellabs manual is owned by Tellabs or its licensors and protected by U.S. and international copyright laws, conventions and
treaties. Your right to use this manual is subject to limitations and restrictions imposed by applicable licenses and copyright laws.
Unauthorized reproduction, modification, distribution, display or other use of this manual may result in criminal and civil penalties.
The following trademarks and service marks are owned by Tellabs Operations, Inc. or its affiliates in the United States and/or
other countries: TELLABS , TELLABS logo, TELLABS and T symbol , and T symbol .
Any other company or product names may be trademarks of their respective companies.
The specifications and information regarding the products in this manual are subject to change without notice. All statements,
information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind,
express or implied. Users must take full responsibility for their application of any products.
Adobe Reader are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

2
76.8600-50133B
2011 Tellabs.
Terms and Abbreviations

Term
Explanation
AC
Attachment Circuit
ARP
Address Resolution Protocol
ATM
Asynchronous Transfer Mode
BE
Best Effort
BRAS
Broadband Remote Access Server
BPDU
Bridge Protocol Data Unit
BSC
Base Station Controller
CCM
Continuity Check Message
CDC
Control and DC Power Card (used in Tellabs 8630 access switch and Tellabs 8660
edge switch)
CE
Customer Edge device
CFM
Connectivity Fault Management
CLI
Command Line Interface
CSMA/CD
Carrier Sense Multiple Access with Collision Detection
C-tag
Customer VLAN tag (the inner VLAN tag)
C-VLAN
Customer VLAN
DA
Destination Address
DMM
Delay Measurement Message
DMR
Delay Measurement Reply
DSLAM
Digital Subscriber Line Access Multiplexer
E-CCM
Ethernet OAM CCM for IDU-ODU
ELP
Ethernet Link Protection
eNB
Evolved NodeB
ETH-DM
Ethernet OAM Frame Delay Measurement
Ethernet PDU Ethernet frame excluding preamble (7 bytes), start of frame delimiter (1 byte) and
inter-frame gap (12 bytes)
76.8600-50133B
2011 Tellabs.
EtherType
A two-octet field in an Ethernet frame. It is used to indicate which protocol is

encapsulated in the payload of an Ethernet frame.
ETH-LM
Ethernet OAM Frame Loss Measurement
FD
Frame Delay
FDV
Frame Delay Variation
FIB
Forwarding Information Base
FLR
Frame Loss Ratio
FMC
Fixed-mobile convergence
3
FTN
Forwarding equivalence class To Next hop label forwarding entry map (for MPLS)
GE
Gigabit Ethernet
HM
High Speed Module (used in Tellabs 8611 access switch)
IDU
Indoor Unit
IEEE
Institute of Electrical and Electronics Engineers
IETF
Internet Engineering Task Force
IFC
Interface Module Concentrator is the line card baseboard and it can be equipped with
one or two IFMs. Three variants available: IFC1-A, IFC1-B and IFC2-B (used in
Tellabs 8630 access switch and Tellabs 8660 edge switch).
IFDV
Inter-Frame Delay Variation
IFM
Interface Module. A specific term of the module which can be placed on the line
card/baseboard and which consists of the physical interfaces (used in Tellabs 8620
access switch, Tellabs 8630 access switch and Tellabs 8660 edge switch).
IGMP
Internet Group Management Protocol
ILM
Incoming Label Map (for MPLS)
IP
Internet Protocol
IRB
Integrated Routing and Bridging
L2
OSI Layer 2
L3
OSI Layer 3
LACP
Link Aggregation Control Protocol
LAG
Link Aggregation
LAN
Local Area Network
LAPF
Link Access Procedure/Protocol for Frame Mode Services
LBM
Loopback Message
LBR
Loopback Reply
LDP
Label Distribution Protocol (MPLS)
Line card
The line card in the Tellabs 8600 system consists of an Interface Module Concentrator
(IFC) and up to two Interface Modules (IFMs) (used in Tellabs 8630 access switch
and Tellabs 8660 edge switch). In Tellabs 8000 intelligent network manager and
CLI referred to as unit.
LM
Line module (used in Tellabs 8607 access switch, Tellabs 8609 access switch and
Tellabs 8611 access switch)
LMEP
Local Maintenance Endpoint
LOC
Loss of Continuity
LTE
Long Term Evolution
LTM
Linktrace Message
LTR
Linktrace Reply
MA
Maintenance Association
MAC
Media Access Control
MAID
Maintenance Association Identifier

4
76.8600-50133B
2011 Tellabs.
MAN
Metro Area Network
MD
Maintenance Domain
MDL
Maintenance Domain Level
ME
Maintenance Entity
MEP
Maintenance Endpoint
MIP
Maintenance Intermediate Point
MP
Maintenance Point
MPLS
Multiprotocol Label Switching
MSP1+1
Multiplex Section Trail Protection 1+1
MSTP
Multiple Spanning Tree Protocol
MTU
Maximum Transfer/Transmission Unit
Multiple hop Involves multiple packet forwarding decisions

path
76.8600-50133B
2011 Tellabs.
NE
Network Element
Node
In Tellabs 8000 intelligent network manager and CLI refers to network element.
OAM
Operation, Administration and Maintenance
ODU
Out Door Unit
P-CCM
Ethernet OAM CCM for ODU-ODU
PDU
Protocol Data Unit
PE
Provider Edge Network Element
PIM
Protocol Independent Multicast
PM
Performance Monitoring
PRI bits
User Priority field bits
Protecting
interface
This ELP group member interface is selected by default as the passive interface. Note
that in CLI a protecting interface is referred to as a backup interface.
PSN
Packet Switch Network
PWE3
Pseudowire Emulation Edge to Edge. IEFT working group.
Q-in-Q
Stacked VLAN
QoS
Quality of Service.
RAN
Radio Access Network
RDI
Remote Defect Indication
RMEP
Remote Maintenance Endpoint
RNC
Radio Network Controller
RSTP
Rapid Spanning Tree Protocol
SA
Source Address
SAToP
Structure-Agnostic Time Division Multiplexing over Packet
SCM
Switching and Control Module (used in Tellabs 8611 access switch)

5
Single hop
Involves only a single packet forwarding decision
SNAP
Subnetwork Access Protocol
SSM
Synchronization Status Message
S-tag
Service VLAN tag (the outer VLAN tag)
STP
Spanning Tree Protocol
S-VLAN
Service VLAN
TDM
Time Division Multiplexing
TLV
Type Length Value
T-PE
Terminating Provider Edge Network Element (RFC4364)
TTL
Time-to-Live
VCCV
Virtual Circuit Connectivity Verification
VLAN
Virtual LAN
VPLS
Virtual Private LAN Service
VPWS
Virtual Private Wire Service
VRF
VPN Routing and Forwarding (RFC4364)
VRRP
Virtual Router Redundancy Protocol
VSI
Virtual Switching Instance
WAN
Wide Area Network
Working
interface
This ELP group member interface is selected by default as the active interface.
The working interface must be the right-hand side interface of the two interfaces
of an ELP group (in case of Tellabs 8660 edge switch the interface residing on
the right-hand side IFC, in case of Tellabs 8620 access switch the right-hand side
interface on the IFMs, and in case of Tellabs 8630 access switch the lower interface
as IFCs are in horizontal direction). Note that in CLI a working interface is referred
to as primary interface.

6
76.8600-50133B
2011 Tellabs.
Table of Contents
Table of Contents
About This Manual ............................................................................................................ 10

Objectives....................................................................................................................................................................... 10
Audience......................................................................................................................................................................... 10
Related Documentation .................................................................................................................................................. 10
Interface Numbering Conventions ..................................................................................................................................11
Document Conventions .................................................................................................................................................. 12
Documentation Feedback............................................................................................................................................... 12
Ethernet Overview....................................................................................................... 13
1.1
Ethernet Forwarding ................................................................................................... 16

2.1
2.2
2.3
2.4
2.5
Ethernet Interfaces............................................................................................................................................... 14
1.1.1
Ethernet Physical Interfaces ................................................................................................................ 14
1.1.2
Ethernet Logical Interfaces.................................................................................................................. 15
Ethernet Switching .............................................................................................................................................. 16

2.1.1
Application of MAC Switching........................................................................................................... 22
2.1.2
References ........................................................................................................................................... 23
Ethernet Pseudowires .......................................................................................................................................... 23
2.2.1
Application Example of Ethernet Pseudowires ................................................................................... 23
2.2.2
Ethernet Pseudowire Forwarding ........................................................................................................ 24
2.2.3
Internal Ethernet/VLAN Bridging....................................................................................................... 24
2.2.4
Ethernet Pseudowire Virtual Circuit Connectivity Verification .......................................................... 24
2.2.5
References ........................................................................................................................................... 25
Stacked VLANs................................................................................................................................................... 25
2.3.1
Application Example of Stacked VLANs ........................................................................................... 26
2.3.2
References ........................................................................................................................................... 26
Integrated Routing and Bridging ......................................................................................................................... 27
2.4.1
Applications of Integrated Routing and Bridging ............................................................................... 28
Ethernet Forwarding CLI Configuration Examples............................................................................................. 29
2.5.1
Virtual Private Wire Service Layer 2 VPN CLI Examples ................................................................. 29
2.5.2
Ethernet Switching Service CLI Examples ......................................................................................... 35
2.5.3
Integrated Routing and Bridging CLI Examples................................................................................. 36
Ethernet OAM .............................................................................................................. 38

3.1
76.8600-50133B
2011 Tellabs.
Ethernet OAM Overview..................................................................................................................................... 38

7
Table of Contents
3.2
Ethernet Link Aggregation ......................................................................................... 68

4.1
4.2
4.3
4.4
4.5
4.6
4.7
3.1.1
Ethernet OAM Interfaces and Restrictions.......................................................................................... 40
3.1.2
Connectivity Fault Management ......................................................................................................... 40
3.1.3
Performance Monitoring...................................................................................................................... 44
3.1.4
Ethernet OAM Capacity ...................................................................................................................... 47
3.1.5
References ........................................................................................................................................... 48
Ethernet OAM CLI Configuration Examples...................................................................................................... 48
3.2.1
Configuring Local MEP....................................................................................................................... 49
3.2.2
Configuring CCM ................................................................................................................................ 49
3.2.3
Configuring Linktrace.......................................................................................................................... 51
3.2.4
Running Linktrace ............................................................................................................................... 51
3.2.5
Displaying Ethernet OAM Information............................................................................................... 52
3.2.6
Ethernet OAM CFM Ping.................................................................................................................... 54
3.2.7
Configuring QoS Mapping for Ethernet OAM PM ............................................................................. 55
3.2.8
Configuring Ethernet OAM PM - ETH-DM and ETH-LM ................................................................ 58
3.2.9
Ethernet OAM ETH-DM-PING Utility............................................................................................... 66
Introduction ......................................................................................................................................................... 68
4.1.1
Application of Link Aggregation ........................................................................................................ 68
4.1.2
References ........................................................................................................................................... 69
Operation ............................................................................................................................................................. 69
4.2.1
Ethernet Link Aggregation Group ...................................................................................................... 69
4.2.2
Link Aggregation Configuration ......................................................................................................... 71
4.2.3
Bandwidth Allocation.......................................................................................................................... 72
4.2.4
Loopbacks............................................................................................................................................ 73
4.2.5
Synchronization ................................................................................................................................... 73
Faults ................................................................................................................................................................... 73
Statistics............................................................................................................................................................... 73
Dimensioning....................................................................................................................................................... 73
Restrictions .......................................................................................................................................................... 74
Ethernet Link Aggregation CLI Configuration Examples................................................................................... 74
4.7.1
Creating a Link Aggregation Group.................................................................................................... 74
4.7.2
Joining Links to a Link Aggregation Group........................................................................................ 75
4.7.3
Minimizing Traffic Disturbance When Joining a Link........................................................................ 75
4.7.4
Removing Links from a Link Aggregation Group .............................................................................. 76
4.7.5
Removing a Link Aggregation Group ................................................................................................. 76
4.7.6
Configuring Load Balancing Parameters............................................................................................. 77
4.7.7
Configuring Member Link Properties during Membership................................................................. 78
4.7.8
Configuring L2/L3 Properties of a Link Aggregation Group.............................................................. 78
4.7.9
Creating an IP Interface on a Link Aggregation Group ...................................................................... 79
4.7.10
Showing and Clearing of Statistics...................................................................................................... 80
Ethernet Link Protection............................................................................................. 82

5.1
5.2
Introduction and Usage Examples....................................................................................................................... 82

5.1.1
References ........................................................................................................................................... 84
Operation ............................................................................................................................................................. 84
5.2.1
Ethernet Link Protection Group .......................................................................................................... 84
5.2.2
ELP Group Configuration.................................................................................................................... 85

8
76.8600-50133B
2011 Tellabs.
Table of Contents
5.3
5.2.3
Switchover Behavior ........................................................................................................................... 87
5.2.4
MAC Address ...................................................................................................................................... 87
5.2.5
Operational Examples.......................................................................................................................... 88
Ethernet Link Protection CLI Configuration Examples ...................................................................................... 93
5.3.1
Point-to-Point Connection ................................................................................................................... 93
5.3.2
Ethernet Switched Network Connection ............................................................................................. 94
Microwave Radio 1+1 Protection ............................................................................... 96

6.1
6.2
76.8600-50133B
2011 Tellabs.
Microwave Radio 1+1 Protection Overview ....................................................................................................... 96

Configuring Microwave 1+1 Protection in an ELP Group.................................................................................. 98
6.2.1
Create ELP Protection Group .............................................................................................................. 99
6.2.2
Create ODU Management VLAN ..................................................................................................... 100
6.2.3
Create IDU-ODU Monitoring VLAN ............................................................................................... 100
6.2.4
Create ODU-ODU Monitoring VLAN.............................................................................................. 102
6.2.5
Egress Rate Limiter Configuration .................................................................................................... 103
6.2.6
Create Protected User VLANs to ELP Group ................................................................................... 103

9
About This Manual
About This Manual

This chapter discusses the objectives and intended audience of this manual, Tellabs 8600 Managed
Edge System Ethernet Configuration Guide and consists of the following sections:
Objectives
Audience
Related Documentation
Interface Numbering Conventions
Document Conventions
Documentation Feedback
Objectives
This manual provides an overview of the Tellabs 8600 managed edge system Ethernet applications
and instructions on how to configure them using command line interface (CLI) and ASCII textual
commands with a routers console or remote terminal (Telnet).
Audience
This manual is designed for administration personnel for configuring Tellabs 8600 managed edge
system functions with CLI. On the other hand, Tellabs 8000 intelligent network manager provides
access to equal functionality for administration personnel with a graphical user interface. It is
assumed that you have a basic understanding of Ethernet switching and IP routing.
Related Documentation
The document numbering scheme consists of the document ID, indicated by numbers, and the
document revision, indicated by a letter. The references in the Related Documentation table below
are generic and include only the document ID. To make sure the references point to the latest
available document versions, please refer to the relevant product document program on the Tellabs
Portal by navigating to www.portal.tellabs.com > Product Documentation > Data Networking >
Tellabs 8600 Managed Edge System > Technical Documentation.
CLI Commands Manual (76.8600-50117)
Provides commands available to configure, monitor

and maintain the Tellabs 8600 managed edge system
products with CLI.

Tellabs 8605 Access Switch FP1.5
Interface Configuration Guide (76.8615-50147)
Provides an overview of the Tellabs 8605 access

switch interface functions and instructions on how to
configure them with CLI.

10
76.8600-50133B
2011 Tellabs.
About This Manual

Tellabs 8607 Access Switch FP1.1

switch interface functions and instructions on how to
configure them with CLI.

Tellabs 8609 Access Switch FP1.0 and
Tellabs 8611 Access Switch FP1.1 Interface
Configuration Guide (76.8610-50149)

switch and Tellabs 8611 access switch interface
functions and instructions on how to configure them
with CLI.
Tellabs 8600 Managed Edge System FP3.1


switch, Tellabs 8630 access switch and Tellabs 8660
edge switch interface functions and instructions on
how to configure them with CLI.

IP Forwarding and Traffic Management
Configuration Guide (76.8600-50122)
Provides an overview of the Tellabs 8600 managed

edge system IP forwarding and traffic management
and instructions on how to configure them with CLI.

MPLS Applications Configuration Guide
(76.8600-50123)

edge system MPLS applications and instructions on
how to configure them with CLI.

Network Time Protocol Configuration Guide
(76.8600-50126)

edge system network time protocol and instructions
on how to configure it with CLI.

Routing Protocols Configuration Guide
(76.8600-50121)

edge system routing protocols and instructions on how
to configure them with CLI.

Synchronization Configuration Guide
(76.8600-50114)

edge system synchronization and instructions for
configuring it with CLI.

Test and Measurement Configuration Guide
(76.8600-50124)

edge system testing and measurement tools,
connectivity verification and instructions for
configuring them with CLI.
Tellabs 8000 Intelligent Network Manager

Online Help
Provides instructions on how different operations

are performed with Tellabs 8000 intelligent network
manager. Describes also different parameters and
controls of the Tellabs 8000 intelligent network
manager dialogs and windows.
Note that the online help is not available on the portal
but it is incorporated in Tellabs 8000 intelligent
network manager.
Interface Numbering Conventions

To be able to follow more easily the feature descriptions and configuration examples given in this
document, see also the Tellabs 8600 system interface numbering and related figures described in
Tellabs 8600 Managed Edge System CLI Commands Manual.
76.8600-50133B
2011 Tellabs.

11
About This Manual
Document Conventions
This is a note symbol. It emphasizes or supplements information in the document.
This is a caution symbol. It indicates that damage to equipment is possible if the instructions
are not followed.
This is a warning symbol. It indicates that bodily injury is possible if the instructions are not
followed.
Documentation Feedback
Please contact us to suggest improvements or to report errors in our documentation:
Email: fi-documentation@tellabs.com
Fax: +358.9.4131.2430

12
76.8600-50133B
2011 Tellabs.
1 Ethernet Overview
1 Ethernet Overview
Ethernet is one of the most common technologies in various types of networks. Its long
history started from the corporate LAN side and it has spread and it has been used in different
telecommunication applications for years. Today Ethernet has a prominent role in mobile
back-hauling and fixed-mobile convergence (FMC). Its benefits are simplicity, flexibility,
cost-effectiveness both in operational and capital expenditures, and a broad range of products
available.
Ethernet can be applied for different network segments, such as,
Single-hop link between two routers or other network elements.
Multi-hop network segment or operational domain like access.
WAN, and core network.
End-to-end Ethernet service.
Ethernet frames can be carried over almost all physical or data link protocols, such as,
directly over optical fiber and copper cables at various nominal rates of 10 Mbps, 100 Mbps,
1 Gbps, 10 Gbps, or higher,
over multiple physical links using Ethernet Link Aggregation,
over SDH/SONET encapsulated into ATM, PPP, or Frame Relay,
over single or bundled xDSL lines,
over MPLS using pseudowires.
To keep the network operating efficiency, Ethernet service OAM [IEEE802.1ag]/[ITU-T Y.1731]
provides tools for testing, monitoring, measuring, and troubleshooting the network.
The Tellabs 8600 managed edge system supports Ethernet in various ways and on different layers.
This document describes these features including Ethernet pseudowires, OAM functions, Ethernet
layer protections and Ethernet Link Aggregation.
Ethernet features supported by Tellabs 8600 are based on IEEE, IETF, ITU-T, and MEF standards
and technical specifications.
76.8600-50133B
2011 Tellabs.

13
1 Ethernet Overview
1.1
1.1.1
Ethernet Interfaces
Ethernet Physical Interfaces
The notations used in the rows of the supported Ethernet physical interfaces tables are explained
in the following table.
X
The interface module (IFM), line module (LM), high speed module
(HM) or fixed Ethernet interface is supported by the network element.
IFC1, IFC2
The interface module (IFM ) when used in the mentioned interface

module concentrator (IFC) is supported by the network element.
Not supported by the network element.
Tellabs 8620 access switch, Tellabs 8630 access switch and Tellabs 8660 edge switch support the
following Ethernet interface modules:
Interface Module (IFM)
Tellabs 8620
access switch
Tellabs 8630
access switch
Tellabs 8660
edge switch
8x10/100BASE-TX
IFC1
IFC1
8x100BASE-X
IFC1
IFC1
2x1000BASE-X
IFC1
IFC1
8x1000BASE-X
IFC1
IFC1
2+6x10/100/1000BASECOMBO
IFC1
IFC1
8x10/100/1000BASE-TX R2
IFC2
IFC2
8x100/1000BASE-X R2
IFC2
IFC2
1x10GBASE-R R2
IFC2
IFC2
Tellabs 8605 access switch, Tellabs 8607 access switch, Tellabs 8609 access switch and Tellabs
8611 access switch support the following Ethernet interfaces:
Fixed Interface,
Line Module (LM)
or High Speed
Module (HM)
Tellabs 8605
access switch
Tellabs 8607
access switch
Tellabs 8609
access switch
Tellabs
8611 access
switch
10/100BASE-TX
(fixed interface)
10/100/1000BASETX (fixed interface)
100/1000BASE-X
(fixed interface)
1000BASE-T
(fixed interface)

14
76.8600-50133B
2011 Tellabs.
1 Ethernet Overview
1.1.2
Fixed Interface,
Line Module (LM)
or High Speed
Module (HM)
Tellabs 8605
access switch
Tellabs 8607
access switch
Tellabs 8609
access switch
Tellabs
8611 access
switch
8x10/100BASE-TX
LM
4x10/100/1000BASETX HM
4x100/1000BASE-X
HM
Ethernet Logical Interfaces

Logical Ethernet interfaces in Ethernet physical interfaces:
Ethernet
VLAN/Ethernet
Ethernet/MPLS
VLAN/Ethernet/MPLS
Stacked VLAN for pseudowire use
Attachment circuits for Ethernet PWE3 in multiservice interface modules (1xchSTM-1/chOC-3 MS,
2xchSTM-1/chOC-3 MS and 24xchE1/chT1 MS IFMs):
Ethernet/LAPF_SNAP/FR/P12s
VLAN/Ethernet/LAPF_SNAP/FR/P12s
Ethernet/MLPPP and Ethernet/PPP (24xchE1/chT1 MS IFM only)
Attachment circuits for Ethernet PWE3 in multiservice interfaces in Tellabs 8605 access switch and
line modules in Tellabs 8609 access switch and Tellabs 8611 access switch:
Ethernet/MLPPP and Ethernet/PPP on fixed chE1/chT1 interfaces and 8xchE1/chT1 LMs
76.8600-50133B
2011 Tellabs.

15
2 Ethernet Forwarding
Ethernet forwarding can be divided into point-to-point and multipoint connectivity depending
on the network or service topology, see Fig. 1.
In a point-to-point connection, all the frames received from a certain attachment circuit (e.g. VLAN
or port) are transferred to a common destination regardless of the header fields. A common way to
implement a point-to-point Ethernet service is to use MPLS-based pseudowires or stacked VLAN
(Q-in-Q) encapsulation.
Fig. 1 Ethernet Point-to-Point Services
In multipoint topologies, Ethernet switching is needed to look up the headers and decide the
outgoing egress interface. Unicast frames with known destination MAC addresses are forwarded to
a target egress interface, while frames with an unknown MAC destination address are flooded to all
interfaces, except to the incoming, of the used VLAN or other broadcast domain. Typically switches
are learning the Ethernet forwarding table entries from the MAC source addresses of the received
frames, but static addresses are supported as well.
This chapter describes the Ethernet forwarding features supported by the Tellabs 8600 system.
2.1
Ethernet Switching
In the Tellabs 8630 access switch and Tellabs 8660 edge switch Ethernet MAC switching and
MAC learning are supported as specified in [IEEE 802.1D] and [IEEE 802.1Q]. Local switching
of Ethernet frames is supported. Ethernet MAC switching is only supported in IFC variant IFC2
for individual and ELP protected group ports with the following IFMs; both the ingress and egress
interfaces must be on the IFC2 when Ethernet switching is used:

16
76.8600-50133B
2011 Tellabs.
8x10/100/1000BASE-TX R2 IFM
8x100/1000BASE-X R2 IFM
1x10GBASE-R R2 IFM
MAC switching is supported by Tellabs 8630 access switch and Tellabs 8660 edge switch
only in IFC variant IFC2 with the 8x10/100/1000BASE-TX R2, 8x100/1000BASE-X R2 and
1x10GBASE-R R2 IFMs.
The MAC switching functionality is not supported in IFC1 and Tellabs 8620 access switch.
The MAC switching functionality is not supported by Tellabs 8605 access switch, Tellabs 8607
access switch, Tellabs 8609 access switch and Tellabs 8611 access switch.
Ethernet switching is implemented in Tellabs 8600 as part of the VPLS implementation. This allows
defining multiple instances of logical Ethernet switches in one network element, each operating
with an isolated learning and forwarding domain. Tellabs 8630 access switch and Tellabs 8660 edge
switch will support a virtual Ethernet switch. Virtual in the sense that it is distributed on multiple
IFC2s, and it can have multiple instances. Each instance is called a Virtual Switching Instance
(VSI), an isolated Ethernet switch performing MAC switching between all Ethernet interfaces
connected to it. The interfaces are also called Attachment Circuits (ACs), which is a VPLS term.
ACs can be on port or VLAN level, only on native Ethernet interfaces.
Ethernet MAC switching enables forwarding based on Ethernet MAC address. An attachment
circuit is always connected to a single VSI. One or multiple attachment circuits can be connected to
one VSI. The attachment circuit alternatives are:
VLAN
Ethernet port
Up to 960 VSIs are supported per network element and up to a total of 63 ACs per VSI. VSIs can be
in one IFC2 or distributed to multiple IFC2 cards. ACs must be on IFC2 and R2 IFM. VSIs are
stored on the CDC card and then copied to each IFC2.
Fig. 2 Virtual Switches
If frames are untagged, the VSI is associated to the physical port. The VSI association is per VLAN
for single tagged frames and per outer VLAN (S-VLAN) for double tagged frames. MAC switching
between VLANs in the same port (switching + VLAN rewrite) is supported.
76.8600-50133B
2011 Tellabs.

17
MAC learning is performed independently per VSI. The NE performs MAC learning and ageing,
with Forwarding Information Base (FIB) per VSI. Learning is VLAN agnostic but separate VSIs
can be set up per VLAN if needed. Learnt MAC tables share a pool of about 100K entries across all
VSIs in the NE. As the memory resource is shared with other applications, the actual number varies.
The standard flooding domain behavior on ACs ingress, for broadcast, multicast, unknown MAC is:
Flood everywhere at fixed BE priority. BPDUs are transparently forwarded.
The MAC learning attributes are configurable per VSI. Learning can be enabled or disabled per
VSI. The ageing time can be globally configured for all VSIs with 1s granularity, the default value
is 300s and range from 101000000s. Dynamic MAC addresses are removed when aged out,
an interface is going down and during reset or a power shutdown. Static MAC entries that are
not aged and that take precedence over dynamic entries can be configured per VSI. The static
multicast destination configuration is supported and it will override the flooding behavior of a given
multicast group and cause directing those frames to the configured AC. A total of 16000 static MAC
addresses distributed over all VSIs are configurable.
The MAC learning default values can be returned with the CLI command mac-learning.
The configurable limit and thresholds of MAC addresses learnt is supported per VSI. High
threshold is used for triggering an alarm when the number of entries learned goes above the set
threshold. When Limit is reached, learning is suspended. Clear threshold is used for resuming the
learning and clearing alarm when the number of learned entries goes below the clear threshold. The
learned MAC addresses can be shown per VSI.
A mesh group/split horizon (VPLS terms) refer to a group of interfaces that do not flood to each
other; this makes transport more efficient. The mesh group is a group of VSI interfaces. When a
frame arrives from any of the group members, it is never forwarded (unicast, multicast or flooded)
back to any of the other members.
A subset or all ACs can be placed in a mesh group. An AC can only be a member in a single mesh
group. An AC member in a mesh group is termed grouped AC. An AC that is not a member in a
mesh group is termed individual AC.
Fig. 3 VSI Forwarding

18
76.8600-50133B
2011 Tellabs.
IFC2 based hardware utilizes the outgoing bandwidth from the incoming port when flooding
traffic. Traffic is not actually flooded back to the incoming interface, but the bandwidth is
still used. This may lead to exceeding interface outgoing capacity and hence to dropped
packets on that interface (outgoing direction). This is likely to occur if traffic is uni-directional
(permanently or transiently) or if lots of broadcast or multicast traffic (e.g. streamed TV
channels) is present. In many configurations this is non issue. In cases where this becomes
an issue, ports can be assigned to mesh groups. Assigning each port to a separate mesh
group prevents this behavior while permitting regular forwarding behavior.
Spanning tree (STP/RSTP/MSTP) is not supported. Multicast control protocols like PIM and
IGMP are not supported.
Attachment circuits are defined with the following attributes:
AC interface the actual interface attached (e.g. a port, a VLAN over a port)
VLAN level: An attachment circuit of a single customer VLAN (a.k.a Qualified)
Non-VLAN level: An attachment circuit which is not a single VLAN. (It could consist of multiple
VLANs, untagged or a mix) (a.k.a Unqualified)
Attachment mode: An indicator of the VLAN operations at the ingress and egress of an AC. The
modes are modeled after Tellabs 8800:
VLAN Access The VLAN tag is preserved across the VSI being regarded as part of the
customer data. Typically used for customer facing interfaces.
VLAN Trunk The outer tag is removed when forwarded to the VSI, being regarded as a
service delimiter. This mode it typically used to attach a VLAN on a network interface that
multiplexes multiple VLANs.
Port Frames are forwarded transparently onto the VSI. Tags, if they exist, are not affected.
The attachment mode is configurable per AC and it determines the VLAN operations performed at
the AC interfaces to the VSI. The possible values are VLAN-Access, VLAN-Trunk and Port.
The default value for VLAN ACs: VLAN Access
The default value for non-VLAN ACs: Port
Tags 0x88A8, 0x9100 and 0x9200 are not supported by the VSI.
The following table summarizes the VLAN operations.
76.8600-50133B
2011 Tellabs.

19
VLAN Operations
Attachment Mode
Frame VLAN
Tagging
Ingress Action
Egress Action
VLAN Access
untagged
NA
tag added1
single tag
none
outer tag translated
two tags
none
outer tag translated
untagged
NA
add tag
single tag
strip outer tag
add tag
two tags
strip outer tag
add tag1
untagged
none
none
single tag
none
none
two tags
none
none
VLAN Trunk
Port
The VSI typically has all ACs of the same mode, however mix is also possible. The allowed (+) and
not allowed () and non-applicable (NA) combinations are defined in the following table.
Allowed Combinations
Attachment
Mode
VLAN
Access
VLAN Trunk
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
1
0
1
2
Port
Port
Tags
2
VLAN
Trunk
VLAN Access
0
1
2
At VLAN level, a VLAN configured in Access or Trunk mode is supported:

On an Ethernet port could be single or dual tagged, but only the outer tag is considered
On ELP
At VLAN level, mixes of VLANs are supported:
1Those
operations result from misconfigurations (per recommended mixes table below).

20
76.8600-50133B
2011 Tellabs.
Multiple VLAN IDs can be attached to a VSI in the same Tellabs 8630 access switch and Tellabs
8660 edge switch
Multiple VLANs on one port may be associated to same or different VSIs
A VLAN AC may also contain routed traffic as part of the IRB feature (see chapter 2.4 Integrated
Routing and Bridging)
At non-VLAN level, the supported ACs are:
Ethernet port all traffic, tagged or not
A port AC may also contain routed traffic as part of the IRB feature (see chapter 2.4 Integrated
Routing and Bridging)
ELP interface
Native Ethernet AC port or VLAN level fully supports:
Down MEPs
Up MEPs
MIPs
At VLAN level, the ACs not supported are:
VLAN on LAG
VLAN pseudowire
Q-in-Q inner VLAN
VLANs over other L2 interfaces (e.g. over ATM)
Port based VLANs [IEEE 802.1Q]
Raw pseudowire based VLAN
Protocol type based VLANs
At non-VLAN level, the following are not supported:
LAG interface
Raw mode pseudowire
Non VLAN-level AC over other L2 interfaces (e.g. over ATM)
Ethernet switching QoS
Generally the QoS assignment at ingress and egress to a VSI follow the same principles of point to
point Ethernet pseudowires in the product. The [IEEE 802.1p] PRI field in the VLAN tag is used as
the QoS indication. The outer VLAN tag PRI field can be preserved through switching or it can
be remarked at the egress. As a configuration option, a fixed internal QoS can be assigned to all
frames received on an AC. This setting will override the PRI mapping otherwise performed and
also sets the QoS for ACs that have incoming untagged frames. For double tagged frames the inner
tag PRI is preserved. All flooded packets are forwarded in BE class. Up to seven queues per port
are supported in Ethernet switching.
76.8600-50133B
2011 Tellabs.

21
2.1.1
Application of MAC Switching

In Fig. 4 Ethernet MAC switching is applied in mobile backhaul RAN transport. In the aggregation
site, Tellabs 8630 access switch is forwarding Ethernet frames from VLAN attachment circuits
coming from the cell sites with one or more VSIs. In the controller site, Tellabs 8660 edge switch
can optionally be terminated to Ethernet frames to IP/MPLS routing, use VSI and IRB to enable
multiple interfaces share the same IP subnet, or forward traffic purely in L2.
In Fig. 5 a single VLAN per cell site is supposed to encapsulate all user traffic, e.g. SAToP, ATM,
and also Ethernet services carrying data. This requires IRB.
The figures offer application examples only, MAC switching support in Tellabs 8600 products is
described in chapter 2.1 Ethernet Switching.
Fig. 4 Example of Ethernet Switching Application
In the LTE application the eNBs are directly connected via an X2 interface. Ethernet switching can
be configured to the mobile backhaul network nodes for direct delivery of IP/Ethernet packets
between the eNBs. This provides an alternative to routing the packets at Tellabs 8660 edge switch.
X2 connectivity between eNBs can be provided at L2 by the Tellabs 8660 edge switch VSI.

22
76.8600-50133B
2011 Tellabs.
Fig. 5 Example of LTE Application X2
In this application the L2 test/OAM can be done through a separate Ethernet interface, see Fig. 5.
2.1.2
2.2
2.2.1
References
[IEEE 802.1D]
IEEE Std 802.1D-2004 IEEE Standard for Local and Metropolitan Area
Networks--Media access control (MAC) Bridges
[IEEE 802.1Q]
IEEE Std 802.1Q-1998 IEEE Standard for Local and metropolitan area
networks: Virtual Bridged Local Area Networks
Ethernet Pseudowires
Application Example of Ethernet Pseudowires
Virtual Private Wire Service (VPWS) is a point-to-point service where the attachment circuit from
the CE device is connected to a pseudowire at PE. The pseudowire carries a layer 2 packet over the
MPLS and/or IP backbones to the remote PE where it is connected to the remote CE device via an
attachment circuit. The figure below illustrates the arrangement.
The PE does associations between the attachment circuit and pseudowire and is based on local
information. The association can be done, for instance, between the incoming/outgoing VLAN
ID and the pseudowire ID.
76.8600-50133B
2011 Tellabs.

23
Fig. 6 Virtual Private Wire Service
2.2.2
Ethernet Pseudowire Forwarding

An Ethernet pseudowire allows Ethernet Protocol Data Units (Ethernet PDU, Ethernet frame
excluding preamble (7 bytes), start of frame delimiter (1 byte) and inter-frame gap (12 bytes)) to be
carried over an IP or MPLS network. The pseudowire can be set up via manual configuration or by a
signalling protocol. The Tellabs 8600 system supports LDP as the pseudowire signalling protocol.
An Ethernet pseudowire can operate in raw mode or in tagged mode. In tagged mode, each packet
contains a VLAN tag, which is meaningful to the PEs at the two pseudowire endpoints. The raw
mode packet may have a VLAN tag but it is passed transparently through.
In tagged mode, the VLAN ID can be different at different ends of the pseudowire. However,
when PRI bits are carried transparently through the network element, the same VLAN ID must
be used at both ends.
The exact Ethernet pseudowire encapsulation is as defined in [RFC4448].
2.2.3
Internal Ethernet/VLAN Bridging

It is possible to create a connection between two Ethernet interfaces or two VLAN interfaces in the
same NE by creating an NE internal manual pseudowire. Note that this type of Ethernet bridging is a
pure L2 connection without any [IEEE 802.1D] Ethernet bridging functionality such as flooding etc.
2.2.4
Ethernet Pseudowire Virtual Circuit Connectivity Verification

The Tellabs 8600 system supports virtual circuit connectivity verification (VCCV) for pseudowire
fault detection and diagnostics as per [RFC5085]. The following VCCV type options are supported
for Ethernet pseudowires:
Type 3 - TTL Expiry VCCV
supported in Tellabs 8605 access switch, Tellabs 8609 access switch and Tellabs 8611 access
switch

24
76.8600-50133B
2011 Tellabs.
VCCV type 3 is recommended to be used primarily. For more information on VCCV, refer to the
Tellabs 8600 Managed Edge System Test and Measurement Configuration Guide.
2.2.5
2.3
References
[RFC4379]
RFC4379 (2006-02), Detecting Multi-Protocol Label Switched (MPLS) Data

Plane Failures
[RFC4447]
RFC4447 (2006-04), Pseudowire Setup and Maintenance Using the Label

Distribution Protocol (LDP)
[RFC4448]
RFC4448.txt (2006-04), Encapsulation Methods for Transport of Ethernet over

MPLS networks
[RFC5085]
RFC5085 (2007-12), Pseudowire Virtual Circuit Connectivity Verification

(VCCV): A Control Channel for Pseudowires
Stacked VLANs
The Tellabs 8600 system supports VLAN stacking (Q-in-Q) in Ethernet pseudowire emulation edge
to edge (PWE3) and VLAN bridging applications.
Multiple customer VLANs can be carried by a single service VLAN when using two VLAN tags
in the same frame. The inner VLAN tag is the original customer VLAN tag (C-tag) and the outer
VLAN tag (Service VLAN tag or S-tag) is used for aggregation. The C-tag is transparent for most
Ethernet switches. VLAN stacking simplifies provisioning and improves the scalability of Metro
Ethernet networks. IEEE has standardized VLAN stacking in [IEEE802.1ad].
In the Tellabs 8600 system the service VLAN ID is selected per port basis. IEEE recommends to use
0x88A8 as the EtherType value for the S-tag. In addition, Tellabs 8600 also supports the values of
0x8100, 0x9100, and 0x9200. The User Priority field, or PRI bits, of the S-tag can contain a fixed
per port configurable value, or can be copied from the C-tag PRI bits.
76.8600-50133B
2011 Tellabs.

25
2.3.1
Application Example of Stacked VLANs
Fig. 7 Example of VLAN Stacking in Tellabs 8600 Networks
In the figure above VLAN stacking is shown in a network environment where both MPLS based
forwarding and native Ethernet switching are present. The PE1 device could also be a Tellabs 8609
access switch or Tellabs 8611 access switch.
Network elements CE1 and CE2 offer multiple customer VLANs per physical port towards PE1. All
the C-VLANs belonging to a single customer are aggregated to a single service VLAN (S-VLAN).
S-VLANs are carried over the MPLS and Ethernet networks to PE3. PE3 then strips the S-VLAN
tag and forwards the C-VLANs to the targeted links. A tagged mode Ethernet PWE3 is created
between PE1 and PE2 per S-VLAN. PE1 inserts the S-VLAN tag before sending the frame to the
PWE3. PE2 terminates to the PWE3 and forwards the S-tagged frame to the Ethernet network.
The Ethernet network ignores the embedded C-tag, and forwarding is solely based on the S-tags
and MAC addresses.
In the PE2 to PE1 direction, the S-VLAN tag is removed already in PE2, but the associated
forwarding information is carried in the MPLS PWE3 label.
As shown in the figure above, PE3 bridges C-VLANs to/from the stacked S-VLANs in a native
Ethernet network without MPLS.
2.3.2
References
[IEEE802.1ad]

26
IEEE Std 802.1ad-2005 IEEE Standard for Local and metropolitan

area networks: Virtual Bridged Local Area Networks. Amendment
4: Provider Bridges. Amendment to IEEE Std 802.1Q-2005.
76.8600-50133B
2011 Tellabs.
2.4
Integrated Routing and Bridging

In Integrated Routing and Bridging (IRB) a logical Ethernet switch is placed before the IP routing
function. In this way multiple physical Ethernet ports may be connected to a logical IP interface.
The function is needed e.g. in RNC protection cases because the RNC protection model is often
designed as assuming an Ethernet switch layer between the RNC and router. By using IRB there
would be no need for external Ethernet switches.
IP routing functions in the normal way except for the fact that the IP interface is attached to the
Ethernet switch instance instead of a physical port. The Ethernet switch function learns MAC
addresses and switches traffic in the same way as normal Ethernet switches. The logical IP interface
changes location on the basis of the RNC protection function decisions. RNC is able to see the
Tellabs 8600 IP address via both physical ports. In this way the protection functions of the RNC
and Tellabs 8600 are independent.
In the Tellabs 8630 access switch and Tellabs 8660 edge switch IRB is only supported in IFC2 with
the following IFMs:
8x10/100/1000BASE-TX R2 IFM
1x10GBASE-R R2 IFM
IRB combines forwarding of the user data at both Layer 2 (L2) and Layer 3 (L3) through a single
network element. Ingress traffic from a single physical or logical interface is first switched at the
Ethernet layer VSI (MAC switch): Some frames may be forwarded based on that to other L2 switch
interfaces, other frames may be forwarded to a logical Router port of the bridge and then to a
routing function. The router port is also called the IRB interface.
Fig. 8 What Is IRB
From the VSI point of view the router port is just another AC. From the router point of view the
port is just another IP interface. IRB is the logical equivalent of connecting a single port from
VSI with a loop cable to the normal routed port.
The IRB interface is attached to a VSI. Generally, both sides of the IRB interface are fully featured:
The switching side at the VSI to which the IRB is attached and the routing function connected
to the IRB.
76.8600-50133B
2011 Tellabs.

27
Multiple IRB interfaces per VSI are supported. The static MAC address of the IRB interface can
be configured and the MAC address can be shared by multiple VSIs/interfaces. Routing instances
are supported per IRB.
IRB interfaces can be port or VLAN ACs but no attachment modes can be defined per IRB interface
so only a single tag is supported and VLAN IDs must match.
There is no queuing resources associated with the logical IRB interface so no shapers or
schedulers can be associated with the logical IRB interface either.
2.4.1
Applications of Integrated Routing and Bridging

Fig. 9 presents a VRRP application between two protecting Tellabs 8660 edge switch routers. The
Ethernet VSI provides L2 connection to the VRRP master without any need for an external switch.
The virtual IRB interface connects the VSI to the routing instance (VRF). For more details on
VRRP, refer to the Tellabs 8600 Managed Edge System Routing Protocols Configuration Guide.
Fig. 9 VRRP with IRB Application

28
76.8600-50133B
2011 Tellabs.
2.5
Ethernet Forwarding CLI Configuration Examples
2.5.1
Virtual Private Wire Service Layer 2 VPN CLI Examples

There are two ways to set up and maintain the pseudowires; either manually or using the MPLS
Label Distribution Protocol, LDP.
The following chapters show CLI commands needed to configure two PWE3 (Pseudowire
Emulation Edge-to-Edge) tunnels for the network described in the figure below.
Fig. 10 Layer 2 PWE3
Manual Configuration Between NEs

In addition to create the PWE3 circuit itself, the FTN / ILM table must also be configured.
76.8600-50133B
2011 Tellabs.
Command
Description
upe1(config)# pwe3 circuit pwe3Cust1

10000 mpls manual
Create the pseudowire circuit instance with PWE3

ID 10000.
8660:
upe1(config)# interface fe
upe1(cfg-if[fe 5/1/1.86])#
pwe3Cust1
upe1(cfg-if[fe 5/1/1.86])#
upe1(cfg-if[fe 5/1/1.86])#
Attach the pseudowire to the interface.

5/1/1.86
pwe3 circuit
no shutdown
exit

29
upe1(config)# mpls static-ftn

push-and-lookup-for-vc pwe3Cust1
vc-qos af2 10001 171.19.13.2
Add pseudowire label 10001 to the packet and send

it to destination 172.19.13.2 (with the PSN label
based on this destination) and with pseudowire
QoS AF2.
upe1(config)# mpls static-ilm

pop-for-vc pwe3Cust1 10002
Remove pseudowire label 10002.
Command
Description

10000 mpls manual

ID 10000.
8660:
upe2(cfg-if[fe 3/0/4.60])#
pwe3Cust1
upe2(cfg-if[fe 3/0/4.60])#
upe2(cfg-if[fe 3/0/4.60])#

3/0/4.60
pwe3 circuit
no shutdown
exit
upe2(config)# mpls static-ftn

push-and-lookup-for-vc pwe3Cust1
vc-qos af2 10002 171.19.13.1
Add pseudowire label 10002 to the packet and send

it to destination 172.19.13.1 (with the PSN label
based on this destination) and with pseudowire
QoS AF2.
upe2(config)# mpls static-ilm

pop-for-vc pwe3Cust1 10001
Remove pseudowire label 10001 for PWE3

processing.
LDP Signalled Configuration between NEs

When LDP is used, the PWE3 connection is signalled with LDP protocol and so the manual
FTN/ILM table configurations are not needed.
Command
Description
upe1(config)# router ldp

upe1(cfg-ldp)# targeted-peer
171.19.13.2
upe1(cfg-ldp)# exit
Create LDP connection to destination 171.19.13.2

(the LDP protocol automatically creates a
connection to immediate neighbors only).

10003 mpls ldp 171.19.13.2 vc-qos af4
Create the pseudowire circuit instance with

PWE3 ID 10003 and destination 171.19.13.2 with
pseudowire QoS AF4.
8660:
upe1(cfg-if[fe 5/1/1.87])#
pwe3Cust2
upe1(cfg-if[fe 5/1/1.87])#
upe1(cfg-if[fe 5/1/1.87])#

30
Attach the pseudowire to VLAN 87 on interface

5/1/1.87
fe 5/1/1.
pwe3 circuit
no shutdown
exit
76.8600-50133B
2011 Tellabs.
Command
Description
upe2(config)# router ldp

upe2(cfg-ldp)# targeted-peer
171.19.13.1
upe2(cfg-ldp)# exit
Create LDP connection to destination 171.19.13.1

(the LDP protocol automatically creates a
connection to immediate neighbors only).

10003 mpls ldp 171.19.13.1 vc-qos af4

pseudowire QoS AF4.
8660:
upe2(cfg-if[fe 3/0/4.61])#
pwe3Cust2
upe2(cfg-if[fe 3/0/4.61])#
upe2(cfg-if[fe 3/0/4.61])#
Attach the pseudowire to VLAN 61 on interface

3/0/4.61
fe 3/0/4.
pwe3 circuit
no shutdown
exit
Check the LDP protocol PWE3 circuit state. The
state is down until both directions are up (can also
be checked from upe1 node). If more information
is required, use the detail option.
Attachment circuit link state must be up for the
pseudowire circuit state to be up.
upe2(config)# show ldp pwe3
Manual Configuration Inside One NE

It is also possible to bridge Ethernet/VLANs inside one NE with pseudowires. Compared to the
manual configuration, a special bridge action is made to the MPLS FTN table.
76.8600-50133B
2011 Tellabs.
Command
Description

9000 mpls manual

ID 9000.
8660:
upe4(cfg-if[fe 7/0/3.30])#
pwe3Cust4
upe4(cfg-if[fe 7/0/3.30])#
upe4(cfg-if[fe 7/0/3.30])#

7/0/3.30
pwe3 circuit
no shutdown
exit

31
8660:
upe4(config)# interface fe 11/1/0.20
upe4(cfg-if[fe 11/1/0.20])# pwe3
circuit pwe3Cust4
upe4(cfg-if[fe 11/1/0.20])# no shutdown
upe4(cfg-if[fe 11/1/0.20])# exit
upe4(config)# mpls static-ftn bridge
pwe3Cust4 vc-qos af3 fe 7/0/3.30 fe
11/1/0.20
upe4(config)# mpls static-ftn bridge
pwe3Cust4 vc-qos af3 fe 11/1/0.20 fe
7/0/3.30
Bridge interfaces with AF3 QoS to both directions.
Stacked VLAN Configuration

The figure below illustrates an example of DSLAM transport.
Fig. 11 DSLAM Transport
In this example, a DSLAM assigns each customer one VLAN (C-VLAN). The PE1 inserts provider
VLAN tags over these VLANs and tunnels them over a PWE3 tunnel (type Ethernet-VLAN) to the
PE2. The PE2 transmits tunneled packets to BRAS, where each DSLAM is identified by a provider
VLAN and each subscriber within a DSLAM by the customer VLAN. In reverse direction, the PE2
removes the provider VLAN tag before transmitting them to the pseudowire.
PE1 configuration:
Command
Description
PE1(config)# interface fe0/3#svlan#10
Create an interface and select the provider tag 10

to be added to all packets. The actual tag value is
overwritten in this example by PE2.
PE1(config)# pwe3 circuit pwe3Cust5

10014 mpls ldp 171.19.14.2 vc-qos af4

pseudowire QoS AF4.

32
76.8600-50133B
2011 Tellabs.
PE1(cfg-if[fe0/3#svlan#10])# dot1q
svlan ethertype 0x88a8
Select the provider tag type 0x88a8.
PE1(cfg-if[fe0/3# svlan#10])# pwe3

circuit pwe3Cust5
Do normal PWE3 circuit binding.
PE1(cfg-if[fe0/3#svlan#10])# no
shutdown
Bring up the interface.
PE2 configuration:
Command
Description
PE2(config)# interface fe0/4.100
Create a provider VLAN interface (the provider

tag value 100).
PE2(config)# pwe3 circuit pwe3Cust5

10014 mpls ldp 171.19.14.1 vc-qos af4

pseudowire QoS AF4.
PE2(cfg-if[fe0/4.100])# pwe3 circuit

pwe3Cust5 encapsulation ethernet-vlan
untagged
Bind the PWE3 circuit. The key word

ethernet-vlan untagged activates the ACPWE3
untagging -- otherwise the PWE3 packets would
have a provider tag in the PE1DSLAM link.
PE2(cfg-if[fe0/4.100])# no shutdown
Connecting Port Mode Interface to Tagged Interface

A VLAN interface can be connected to a physical Ethernet interface. In such a configuration
Ethernet encapsulation (instead of Ethernet VLAN encapsulation) must be used. In a typical
application a number of non-VLAN-aware devices are aggregated to a single physical Ethernet
port, each device in its own VLAN.
When untagged traffic from a physical port arrives to a VLAN interface, the correct VLAN tag is
added. When tagged traffic from the physical Ethernet interface arrives to the VLAN interface, the
existing tag is overwritten.
There are two possible methods for the tag processing in VLAN to the physical interface direction.
Either the tag can be kept in all packets, or it can be removed. In a typical case tag removal is
advisable. However, in some cases keeping the tag might be useful, for example, if a switch that
makes use of the tag is connected to the NE.
The figure below is an example of connecting an untagged interface to a tagged interface.
76.8600-50133B
2011 Tellabs.

33
Fig. 12 Connecting Untagged Interface to Tagged Interface
Customer devices CE1 and CE2 are connected to device CE3. CE3 sees CE1 in VLAN 1 and CE2
in VLAN 2, while both CE1 and CE2 only see the untagged Ethernet.
Command
Description
PE1(config)# interface fe0/1

PE1(config)# pwe3 circuit pw-1-3 10013
mpls ldp 171.19.13.3 vc-qos af4

pseudowire QoS AF4.
PE1(cfg-if[fe0/1])# pwe3 circuit pw-1-3 Do normal PWE3 circuit binding.

PE1(cfg-if[fe0/1)# no shutdown
PE2(config)# interface fe1/3


pseudowire QoS AF4.
PE2(cfg-if[fe1/3])# pwe3 circuit pw-2-3 Do normal PWE3 circuit binding.

PE2(cfg-if[fe1/3)# no shutdown

Create the pseudowire circuit instances with PWE3

IDs 10013 and 10015 and destination 171.19.13.1
and 171.19.13.2, respectively, with pseudowire
QoS AF4.
PE3(config)# interface ge1/1.1

PE3(cfg-if[ge1/1.1])# pwe3 circuit
pw-1-3 encapsulation ethernet untagged
Bind PWE3. Select Ethernet encapsulation for

compatibility to the remote end and select the untag
operation for the PE3PE1 direction.
PE3(cfg-if[ge1/1.1)# no shutdown
PE3(config)# interface ge1/1.2

PE3(cfg-if[ge1/1.2])# pwe3 circuit
pw-2-3 encapsulation ethernet untagged
Bind PWE3. Select Ethernet encapsulation for

compatibility to the remote end and select the untag
operation for the PE3PE1 direction.
PE3(cfg-if[ge1/1.2)# no shutdown

34
76.8600-50133B
2011 Tellabs.
2.5.2
Ethernet Switching Service CLI Examples

The figure below illustrates an example of Ethernet switching service.
Fig. 13 Ethernet Switching Service CLI Example
76.8600-50133B
2011 Tellabs.
Command
Description
NE1(config)# bridging mac-learning

expiry-time 400
Set the global MAC aging timer to a non-default

value 400 seconds.
NE1(config)# bridging-instance VSI-1

100
Create a bridging instance with a name VSI-1 and

ID 100.
NE1(cfg-bridge-inst[VSI-1])#
description MyFirstBridge
Add a description MyFirstBridge for the created

bridging instance.
NE1(cfg-bridge-inst[VSI-1])#
mac-learning limit 400 alarm 70
clear 60
Set the MAC learning limit to a valid value with a

non-default threshold for alarm and clear alarm.
The MAC learning default values can be returned
with the CLI command mac-learning.
NE1(config)# interface ge5/0/0

NE1(cfg-if[ge5/0/0])# no shutdown
NE1(cfg-if[ge5/0/0])# bridging
bridging-instance VSI-1 mode port
NE1(config)# interface ge6/0/0
NE1(cfg-if[ge6/0/0])# no shutdown
NE1(cfg-if[ge6/0/0])# bridging
bridging-instance VSI-1 mode port
Bind two interfaces to the created bridging instance

in port mode.

35
NE1(config)# protection elp Group1

NE1(cfg-elp-prot[Group1])# primary ge
5/0/0 backup ge 6/0/0
NE1(cfg-elp-prot[Group1])# passive-ifmode up rx-both
Create an ELP protection group for the interfaces

bound to the created bridging instance.
NE1(config)# interface ge7/0/0.100

NE1(cfg-if[ge7/0/0.100])# no shutdown
NE1(cfg-if[ge7/0/0.100])# bridging
bridging-instance VSI-1 mode
vlan-access
Bind a VLAN interface to the created bridging

instance in vlan-access mode.

Bind two VLAN interfaces to the created bridging
instance in vlan-trunk mode with vpls-qos af4 and
mesh group ID 1.
bridging-instance VSI-1 mode vlan-trunk
vpls-qos af4 mesh-id 1
bridging-instance VSI-1 mode vlan-trunk
vpls-qos af4 mesh-id 1
NE1(config)# bridging mac bridgingThis is an optional step. Add a static MAC on
instance VSI-1 0000.0011.0022 interface an interface already configured in the bridging
ge 7/0/0.100
instance.
2.5.3
Integrated Routing and Bridging CLI Examples

Command
Description
NE(config)# bridging-instance
MyBridge44 44
Create a bridging instance. A user can define any

name and ID for the bridging instance. In this
example the name MyBridge44 and ID 44 are
used.
NE(config)# interface ge13/0/7

NE(cfg-if[ge13/0/7])# bridging
bridging-instance MyBridge44 mode port
NE(cfg-if[ge13/0/7])# no shutdown
Connect the bridging instance to a physical port.
NE(config)# interface irb 44
Create an IRB interface which is connected to the

bridging instance MyBridge44 (ID 44).
NE(cfg-if[irb44])# no shutdown
Bring up the IRB interface.
NE(config)# interface irb 44.8
Create an IRB interface to bridging instance

MyBridge44 with VLAN tag 8.

36
76.8600-50133B
2011 Tellabs.
76.8600-50133B
2011 Tellabs.
NE(cfg-if[irb44.8])# no shutdown
Bring up the IRB interface with the VLAN tag.
NE(cfg-if[irb44.8])# mac address

3456.abcd.9876
This is an optional step. Configure a static MAC

address for the IRB interface.

37
3 Ethernet OAM
3 Ethernet OAM
3.1
Ethernet OAM Overview

Ethernet Operation, Administration and Maintenance (OAM) is a set of functions designed to
monitor network operation in order to detect network faults and measure its performance.
As Ethernet services evolved from Local Area Networks (LANs) to Ethernet Metro Area Networks
(MANs), the support for automated defect detection and performance measurement prompted the
development of standards e.g. [IEEE 802.1ag], [Y.1731] in the area of Ethernet OAM. There are
two main areas of Ethernet OAM functionality:
Fault management
Performance monitoring
The Ethernet OAM figures offer examples of Ethernet OAM maintenance domains and different
applications. Also other Tellabs 8600 products support the set of functions, see chapter
3.1.1 Ethernet OAM Interfaces and Restrictions.
Fig. 14 Ethernet OAM Maintenance Domains
Ethernet OAM requires the definition and provisioning of the following concepts. The terminology
differs between the [IEEE 802.1ag] and [Y.1731] standards as the table below shows; the Tellabs
8600 system uses the [IEEE 802.1ag] terminology.
Maintenance Domains(MDs) - administrative partitions of a network.
Maintenance Domain Level (MDL) - a representation of the domain level hierarchy.
38
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
Maintenance Endpoints (MEPs) - an edge of a maintenance domain. In addition a MEP can be

distinguished as a down or up MEP:
Down MEP is a MEP facing to the line side, that can be configured in a tunneled, routed
and bridged interface.
Up MEP is a MEP facing to the equipment side, that can be configured in a tunneled interface.
Local MEP (LMEP) - A MEP that is defined locally at the NE level.
Remote MEP (RMEP) - A local MEP has a relationship with RMEPs within the same MA.
Maintenance Intermediate Points (MIPs) - maintenance points on bridges or switches within
a maintenance domain.
Maintenance Point (MP) - One of either a MEP or a MIP.
Maintenance Association (MA) - the set of MEPs and MIPs in the same domain, used to verify
the integrity of a single service instance. An MA can be instantiated per physical interface, or
logical (VLAN) interface and per domain level.
Maintenance Association Identifier (MAID) - As defined in [IEEE 802.1ag], an identifier for a
Maintenance Association, unique over the domain that CFM (Connectivity Fault Management)
is to protect against the accidental concatenation of service instances. The MAID has two parts:
the Maintenance Domain name and the short MA name. It is carried by the CCM (Continuity
Check Message) frames.
[IEEE 802.1ag]
Term
Definition
[Y.1731]
Term
Maintenance
Association (MA)
The set of MEPs/MIPs in the same domain, used to verify the

integrity of a single service instance. An MA can be instantiated
per physical interface, or logical (VLAN) interface and per
domain level.
MEG
Maintenance
Domain (MD)
Administrative partitions of a network.
MEG
Maintenance
Domain Level
(MDL)
Representation of the domain level hierarchy. It determines the

MPs that are interested in the contents of the CFM frame and
through which the CFM frame is allowed to pass. Eight MDLs
are supported.
MEG Level
Maintenance
Entity (ME)
An entity in the network that requires management. This entity

can be an entire network between customer devices, or the
Ethernet network within the domain of a single service provider.
It can also be a single Ethernet link.
ME
Maintenance
Endpoint (MEP)
Maintenance Association Endpoint. Provisioned reference point

that can initiate and terminate proactive OAM frames.
MEP
Maintenance
Domain
Intermediate
Point (MIP)
Provisioned reference point that can respond to diagnostic OAM

frames initiated by a MEP.
MIP
Maintenance
Point (MP)
MEP or MIP, instantiated per physical or logical (VLAN)

interface.
A routed interface refers to the case where Ethernet is terminated, including MPLS; a tunneled
interface refers to the PWE3 attachment circuit side.
76.8600-50133B
2011 Tellabs.

39
3 Ethernet OAM
The following chapters describe the Ethernet OAM functions supported in the Tellabs 8600 system.
3.1.1
Ethernet OAM Interfaces and Restrictions

The Ethernet OAM functionality is supported by the following interfaces types:
Tellabs 8630 access switch and Tellabs 8660 edge switch Ethernet physical interfaces
8x10/100/1000BASE-TX R2, 8x100/1000BASE-X R2 and 1x10GBASE-R R2 on IFC2
Tellabs 8605 access switch and Tellabs 8607 access switch Ethernet physical interfaces
Tellabs 8609 access switch and Tellabs 8611 access switch Ethernet physical interfaces
VLAN on supported Ethernet physical interfaces
Ethernet OAM does not support operation on stacked VLAN interfaces.
Ethernet OAM also can operate on tunneled or bridged/routed interfaces (Ethernet
switching/Integrated Routing and Bridging).
Ethernet OAM is supported by Tellabs 8630 access switch and Tellabs 8660 edge switch only
in IFC2 with the 8x10/100/1000BASE-TX R2, 8x100/1000BASE-X R2 and 1x10GBASE-R R2 IFMs.
The Ethernet OAM functionality is not supported in IFC1 and Tellabs 8620 access switch.
The Ethernet OAM functionality is also supported in Tellabs 8605 access switch, Tellabs 8607
access switch, Tellabs 8609 access switch and Tellabs 8611 access switch.
3.1.2
Connectivity Fault Management

Fault management allows operators or service providers to offer Connectivity Fault Management
(CFM). CFM provides tools to monitor and troubleshoot an Ethernet network that is partitioned into
Maintenance Domains. It provides the ability to monitor connections across these domains using the
CFM functions. This area is divided into the following Ethernet OAM functions:
Fault detection is supported through the continuity check function and allows automatic detection of failures and incorrect configurations of the connectivity from endpoint to endpoint, by
periodically sending and monitoring Continuity Check Messages (CCMs).
Fault verification is supported through the loopback (ping) function by sending a Loopback
Message (LBM) and Loopback Reply (LBR). These can be used during a setup phase or inservice, after a fault has been detected between two endpoints.
Fault isolation is also supported through the linktrace function by sending a Linktrace Message
(LTM) and Linktrace Reply (LTR). Under normal operation conditions this function allows the
operator or service provider to determine the path used by service through the network, whereas
under fault conditions it allows tracing the fault location.
Ethernet OAM CFM relies on a functional architecture that consists of hierarchically partitioned
MDs. Each MD can be managed by a particular service provider or operator. Within an MD,
a service provider or operator can manage various services. An MD is assigned a unique domain
level from 0 to 7, which identifies its position in the hierarchy of other MDs. In different network
applications MDs might be nested, but not overlapped. If MDs are nested, the outer MD must
have a higher domain level than the one used in the inner MD. Each MD of a particular level is
associated to an MA.

40
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
Fig. 15 Ethernet OAM Application
Continuity Check Function

At each NE with a locally configured MEP, the continuity check function allows monitoring the
connectivity of the LMEP to all of its peer RMEPs that are members in the same MA. The monitoring
is performed through the exchange of CCMs. A MEP emits CCMs periodically with a multicast
destination address and they are therefore propagated to every other accessible MEP in the MA.
When the continuity check function is activated, each MEP in the MA monitors the stream of CCMs
arriving from each of its peers. Should CCMs from a RMEP stop arriving, a Loss of Continuity
(LOC) alarm is raised against the RMEP.
ETH-AIS is not supported, instead Tellabs 8600 supports ETH-RDI. The Ethernet remote defect
indication (RDI) allows a MEP to communicate to its peer MEPs that a defect condition has been
encountered. ETH-RDI is used only when the ETH-CC transmission is enabled.
Fig. 16 Ethernet OAM Continuity Check Application
RMEPs
76.8600-50133B
2011 Tellabs.

41
3 Ethernet OAM
For a LMEP, remote MEPs may be either configured manually or autodiscovered. RMEP
configuration allows the operator to indicate which MEPs (identified by MEPID) are expected to be
present in a MA. The RMEPs are stored permanently in the NE database. This allows continuity
check monitoring for RMEPs and raising a LOC alarm if connectivity is lost to a RMEP.
Alternatively, the operator may choose to have the system automatically discovering peer MEPs
in the MA. In that mode, when a stream of CCMs is detected from an unknown MEP, it will be
recorded as a new RMEP. The MEPID as well as the MAC address of the RMEP received in the
CCMs will be displayed. Once discovered, LOC monitoring is applied to the remote MEP and it
may be added to the permanent RMEP list at the operators discretion.
Autodiscovered RMEPs that are in LOC for a pre-configured aging time are removed from
the RMEP list.
A mix of configured and autodiscovered RMEPs can exist in the same MA. This can be useful, for
example, when the operator configures the MEPs that are expected, and uses autodiscovery to find
out any unexpected MEPs e.g. due to configuration errors. Note that learning MAC addresses can
be applied for configured MEPs as well, in the case that the operator administers the MEPIDs but
does not know the MAC addresses.
Cross-Connect Errors
CCMs carry also information of the MAID, a field that identifies the MA that they belong to. This
allows detecting network cross-connect errors (also known as mis-merge errors). When physical
interfaces or VLANs are misconnected in the network, CCMs from a foreign MA may leak into
the monitored MA. This condition can be detected by the local MEP as a mismatch in the MAID
field, which would raise the cross-connect alarm.
Continuity Check Related Parameters
MA parameters - some of the parameters that govern CCM behavior are specified per MA since
they must be consistent for all RMEPs. These include:
MA name - the MA identifier which has a few optional formats.
CCM interval - the time period between the transmission of two consecutive CCMs.
MA CCM priority - the QoS at which a MEP member in the MA sends CCMs.
Autodiscovery - an enable/disable attribute activating autodiscovery. The autodiscovery parameter is specified per MA and it indicates whether or not RMEPs belonging to the MA
should be autodiscovered.
RMEP aging time - specifying the LOC condition duration after which an autodiscovered
MEP is deleted.
Emit faults - indicates whether or not to generate LOC alarms on autodiscovered RMEPs.
RMEP parameters - for configured RMEPs:
RMEPID - the MEPID of the RMEP.
MAC address - an optional parameter indicating the expected MAC address of the RMEP.
Local MEP parameters:
CCM transmission enable/disable - a parameter indicating if a given MEP transmits CCMs
to its neighbors.
42
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
Loopback Function
The loopback function is a ping-like request or reply function. The protocol supports generation of
unicast loopback or multicast loopback and response. A unicast loopback (ping) can be used as a
tool for testing connectivity to a specific known MEP or MIP in the network. A multicast loopback
(ping) can be used as a tool to discover all the MEPs in the MA of the initiator, since all the MEPs
present will respond to the multicast ping command.
A LBM session is initiated when a loopback command is performed for a given LMEP. A LBM
session is a sequence of LBM transmissions, followed by the collection of LBR and is completed
with issuing a report on the results.
The completion of a LBM session is followed by a report of the session that includes the following:
Number of received LBRs for each addressed MP.
Round trip delay (minimum, average, maximum).
Counters of Tx, Rx frames and percentage of packet loss.
Error conditions.
Out-of-sequence LBR frames.
Number of duplicate received LBRs.
LBR frames with payload mismatch.
Linktrace Function
The linktrace is an on-demand function that allows tracing the connectivity of a local MEP to
a destination MEP or a MIP of the same domain in the network. An LTM message is sent by the
linktrace initiator towards the target MEP or MIP. Each MIP on the path sends a LTR to the LTM
initiator and forwards the LTM on the data path towards the target destination. Finally the target MEP
or MIP responds, too. Based on all the responses, the linktrace initiator creates an ordered list of
responders which allows the operator to trace the service path in the network. The linktrace is useful
for troubleshooting in case of connectivity problems as it can help localizing the network segment
which has a fault. It can also assist finding unexpected paths in the network, such as forwarding
loops. The linktrace is similar in functionality to IP traceroute but performed on the Ethernet layer.
Fig. 17 Ethernet OAM Linktrace Application

76.8600-50133B
2011 Tellabs.

43
3 Ethernet OAM
Linktrace Related Parameters

MEP - the name of the local MEP to initiate the linktrace.
Linktrace QoS - the QoS at which the linktrace is sent.
MEP/MAC - an identifier of the target destination of the linktrace.
MIP OAM Processing
In addition to MEPs, the Tellabs 8600 system supports the configuration of MIPs. A MIP is
configured on a network element interface positioned on the user data path between MEPs. It is
considered part of the maintenance domain. A MIP takes a less active part in the Ethernet OAM.
MIP does not initiate any Ethernet OAM functions but can react to some messages and transparently
passes through all other messages.
The messages that a MIP reacts to are:
LBM with a destination equal to the MAC address of the MIP. The MIP reacts to that with LBR
just like a MEP.
LBM with a multicast destination address equal to that of a LTM.
LTM. A MIP reacts to a LTM with LTR and may also forward LTM. See section Linktrace Function for details.
A MIP can generally be configured on tunneled interfaces (Ethernet PWE3 attachment circuits).
MIP instances are provisioned at interface level, at the same MD level as a MEP. The only
configurable attribute of a MIP instance is the MIP name.
3.1.3
Performance Monitoring
In addition to the Ethernet service OAM CFM functions that are targeted for troubleshooting
and fault isolation, the Tellabs 8600 system implements another group of functions related to
Performance Monitoring (PM) of Ethernet services. This group of functions is specified in [Y.1731]
for the following performance parameters:
Frame Loss Ratio (FLR)
Frame Delay (FD)
Frame Delay Variation (FDV)
Such measurements enable identification of problems before they escalate, so that users are not
impacted by network defects. [Y.1731] specifies methods for measurements of loss ratio and
methods for delay and delay variation measurement. These methods are intended mainly for
point-to-point services. The PM functions reuse the same Ethernet OAM infrastructure as CFM. The
entities used for CFM such as MAs, MEPs, MIPs are applicable for PM as well. The PM functions
are typically end to end and MIPs do not participate in these functions.

44
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
Ethernet Frame Loss Measurement (ETH-LM)

Ethernet Frame Loss Measurement (ETH-LM) is an OAM function intended to measure frame loss
characteristics between two MEPs by exchanging ETH-LM-specific OAM messages that carry
frame count information. The ETH-LM function operates on a pair of MEPs at a given QoS level.
The ETH-LM is measured only point-to-point using the Loss Measurement Message/Response
(LMM/LMR) single-ended protocol. For each measurement a MEP can act either as an initiator and
responder or as a responder only. The initiator schedules the measurement and collects the results
and the responder is only responding. Most configuration of the ETH-LM function is performed at
the initiator network element; also the responder needs to be activated. There can also be parallel
ETH-LM sessions performed for different QoS settings for the same pair of MEPs. The single ended
ETH-LM protocol specified by [Y.1731] has been implemented.
The Ethernet OAM frames are not counted in user frame counts.
ETH-LM is performed continuously once it has been configured until it is stopped.
ETH-LM Related Parameters
Local MEP (LMEP) and its role: initiator/responder
Remote MEP (RMEP)
ETH-LM period as generated by the initiator - the interval (0.1900 s), the default period is 10 s
ETH-LM priority of the LMM/LMR frames
QoS (the default is BE)
ETH-LM measurement type is an on-demand continuous measurement that runs infinitely until
stopped.
ETH-LM Report
The following performance metrics are collected in 1x current /32x previous 15min and one
current/one previous 24h buckets and reported for a continuous ETH-LM session:
Rx/Tx counters
Rx/Tx loss counters for the near and far end
Ethernet Frame Delay Measurement (ETH-DM)
Ethernet Frame Delay Measurement (ETH-DM) is an OAM function intended to measure delay
characteristics between two MEPs by exchanging ETH-DM-specific OAM messages that carry
timestamps. The ETH-DM function operates on a pair of MEPs at a given QoS level. For each
ETH-DM measurement a MEP is acting as an initiator and responder. The initiator schedules the
measurement and collects the results and the responder is only responding. The configuration of
the ETH-DM function is performed at the initiator side whereas responding to received DMMs
is an automatic MEP action. The pair of MEPs can be part of a point-to-point or multipoint
MA. In the latter case, the same MEP may conduct separate measurements with multiple other
MEPs simultaneously. There can also be parallel ETH-DM sessions performed for different QoS
settings for the same pair of MEPs. The ETH-DM function is designed to measure the following
performance metrics:
76.8600-50133B
2011 Tellabs.

45
3 Ethernet OAM
Round Trip Delay

One Way Delay
Inter-Frame Delay Variation (IFDV)
ETH-DM is supported in two ways, as ETH-DM ping for quick measurements and troubleshooting,
and also as a continuous ETH-DM running constantly in the background.
The parameters are measured separately on each direction of the path between the MEPs. The
performance metrics are calculated statistically over multiple measurements. The ETH-DM function
implements an initiator-responder protocol using DMM-DMR frames. This protocol can be used to
measure all three types of delay metrics.
The accuracy of the ETH-DM one way delay measurement is directly affected by the time
synchronization of the network elements where the two MEPs reside. Refer to Tellabs
8600 Managed Edge System Network Time Protocol Configuration Guide and Tellabs 8600
Managed Edge System Synchronization Configuration Guide for more information on NTP
and synchronization, respectively.
ETH-DM Related Parameters

MEP - the name of the local MEP.
MEP/MAC - an identifier of the peer MEP against which ETH-DM is performed.
QoS - the QoS for which the ETH-DM is performed.
ETH-DM period - the interval (in milliseconds) between two consecutive DMM frames sent.
ETH-DM frame count - the number of DMMs sent.
ETH-DM selection offset - indicates the pairing of frames for IFDV measurement. For example,
if the selection offset is set to 3, IFDV will be calculated based on all pairs of DMRs which are
three frames apart.
Percentile - indicates the percentile by which certain metrics are to be reported. For example, if
set to 95%, the report for a given metrics will indicate the value under which 95% of the measurements fall.
ETH-DM Report
The following performance metrics shall be calculated and reported at the end of the ETH-DM
session:
Near end two way delay (minimum, maximum, average)
Near end one way delay (minimum, maximum, average, percentile)
Far end one way delay (minimum, maximum, average, percentile)
Near end IFDV (maximum, average, percentile)
Far end IFDV (maximum, average, percentile)
ETH-DM-Ping Utility

46
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
The ETH-DM-ping utility can be used for quick delay measurement and should always be used
for [Y.1731] performance monitoring troubleshooting. It can be entered in place of any continuous
ETH-DM measurement session, but not in parallel (i.e. it is not possible to have both a continuous
ETH-DM session and a dm-ping session between a pair of MEPs on the same QoS.) The advantage
of dm-ping is that it relies only on the timestamps to match DMR response to its DMM request, and
thus it will work even if QoS is not mapped properly along the path. Moreover, it will report the
outgoing VLAN priority of the DMM and receiving VLAN priority of the DMR message.
3.1.4
Ethernet OAM Capacity

The maximum numbers of Ethernet OAM instances supported by the Tellabs 8600 system are
provided below:
Tellabs 8660 edge switch
Ethernet R2 IFMs2
IFC2
NE
Local MPs (any combination of

Up/Down MEPs/ MIPs)
2K
4K
4K
CCM sender MEPs
1K
1K
4K
RMEPs (CCM monitored)
512 @ 1/10 ms
1024 @ 1/100 ms or
longer period
512 @ 1/10 ms
1024 @ 1/100 ms
or longer period
4K @ 1/100 ms
ETH-DM
Measurement
Instances
Initiator
256 @ 1/sec
256 @ 1/sec
1K @ 1/sec
Responder
1K @ 1/sec
1K @ 1/sec
2K @ 1/sec
ETH-LM
Measurement
Instances
Initiator
256 @ 1/10 sec
256 @ 1/10 sec
1K @ 1/10 sec
Responder
1K @ 1/10 sec
1K @ 1/10 sec
2K @ 1/10 sec
Ethernet OAM is not supported in IFC1 and Tellabs 8620 access switch.

Port
NE
Local MPs (any combination of Up/Down

MEPs/ MIPs)
16
64
CCM sender MEPs
16
64
RMEPs (CCM monitored)
16 @ 1/10 ms or 1/100 ms
255 @ 1/sec or longer
period
16 @ 1/10 ms or 1/100 ms
255 @ 1/sec or longer
period
Initiator
16 @ 1/sec
16 @ 1/sec
Responder
16 @ 1/sec
16 @ 1/sec
Initiator
32 @ 1/10 sec
32 @ 1/10 sec
Responder
32 @ 1/10 sec
32 @ 1/10 sec
ETH-DM
Measurement
Instances
ETH-LM
Measurement
Instances
2The
Ethernet R2 IFMs are 8x10/100/1000BASE-TX R2, 8x100/1000BASE-X R2 and 1x10GBASE-R R2 IFMs.
76.8600-50133B
2011 Tellabs.

47
3 Ethernet OAM
3.1.5
3.2
References
[IEEE 802.1ag]
IEEE Std 802.1ag-2007 IEEE Standard for Local and metropolitan

area networks: Virtual Bridged Local Area Networks. Amendment 5:
Connectivity Fault Management.
[Y.1731]
ITU Recommendation Y.1731 (2008-02), OAM functions and mechanisms

for Ethernet based networks
Ethernet OAM CLI Configuration Examples

CLI configuration examples of Ethernet OAM fault management and performance monitoring are
described below. The examples focus only on the Ethernet OAM functionality. In conjunction with
the Ethernet OAM configuration, a configuration of Ethernet connectivity (cross-connection and
tunneling) is required and that is not covered in this chapter. Also the figures offer configuration
examples, support in other Tellabs 8600 products is described in chapter 3.1.1 Ethernet OAM
Interfaces and Restrictions.
Fig. 18 Ethernet OAM Network
The Ethernet OAM CFM configuration guidelines are as follows:

Configure a local MEP.
Configure an MD with a defined MD name and level.
Configure an MA by associating with a configured MD.
Bind an MEP to a physical or logical interface and associate it with a configured MA.
Configure CCM.
Configure linktrace.
Display Ethernet OAM provisioning information and status.
Use Ethernet OAM CFM ping to identify a precise fault location along a given MA.
Use Delay and Loss ETH-DM and ETH-LM Measurements for Ethernet OAM.
Use Delay Measurement (ETH-DM) ping for Ethernet OAM PM.
48
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
3.2.1
Configuring Local MEP

An example on how to configure MD, MA and Local MEP (LMEP) is described below. The
example uses the topology shown in Fig. 18 to create an up MEP between CE1 and CE7. The
creation of the bridged down MEP shown in solid green line between CE1 and NE5 is similar
and follows the same steps as outlined below.
The following Maintenance Domain (MD) and Maintenance Area (MA) definitions are used in
configuration examples presented later in this document. Three MDs (of eight maximum possible)
corresponding to three MD levels are defined, and within each three MAs are defined (one for
each respectively: Down-MEP, MIP, Up-MEP)
eth
eth
eth
eth
cfm
cfm
cfm
cfm
md
md
md
md
DOMAIN_0
DOMAIN_0
DOMAIN_0
DOMAIN_0
level 0 md-name string OPERATOR

ma MA_0D short-name string MA_0D
ma MA_0I short-name string MA_0I
ma MA_0U short-name string MA_0U
eth
eth
eth
eth
cfm
cfm
cfm
cfm
md
md
md
md
DOMAIN_1
DOMAIN_1
DOMAIN_1
DOMAIN_1
level 1 md-name string PROVIDER

eth
eth
eth
eth
cfm
cfm
cfm
cfm
md
md
md
md
DOMAIN_2
DOMAIN_2
DOMAIN_2
DOMAIN_2
level 2 md-name string CUSTOMER

Command
Description
router-CE1(config)# eth cfm md DOMAIN_2 Define MD with name DOMAIN_2 and MD level
level 2 md-name string CUSTOMER
ID 2 at node CE1.
The md-name is the Maintenance Domain
keyword used to construct the MA ID that is
signaled over the network. If not specified, the
default value will be the truncated version of the
string type domain name.
router-CE1(config)# eth cfm md DOMAIN_2 Create MA at node CE1.
ma MA_2U
router-CE1(config)# interface ge
Bind LMEP to an interface (physical or logical).
6/0/6.10
In this case a local up MEP (with MEP ID 606) is
router-CE1(cfg-if[ge6/0/6.10])# eth cfm bound to a logical (VLAN) interface ge 6/0/6.10.
Note that MA can be bound to more than one
ma MA_2U mep local lmep606 606 up
interface (physical/logical), or to a domain level
3.2.2
Configuring CCM
The following example shows how to configure the Ethernet OAM CCM function. The CCM
function requires MD and MA and MEP to be configured with the ccm send option. The
CCM function allows the MEPs to be configured with the remote option which is either static
or autodiscover.
76.8600-50133B
2011 Tellabs.

49
3 Ethernet OAM
Configure MEP with CCM Send Option

Command
Description
router-CE1(config)# eth cfm md DOMAIN_1 Provision the [IEEE 802.1ag] maintenance domain.
level 1 md-name string PROVIDER
router-CE1(config)# eth cfm md DOMAIN_1 Define the CCM interval (100 ms in this example).
ma MA_1D ccm interval 100ms
If no value is defined, the default value used is 1s.
The following options are available in the MA
CCM interval CLI command:
10ms CCM interval
100ms CCM interval
1s CCM interval
10s CCM interval
1min CCM interval
Bind LMEP to interface ge 6/05.10 with the ccm
6/0/5.10
send option.
router-CE1(cfg-if[ge6/0/5.10])# eth cfm
ma MA_1D mep local lmep605 605 down ccm
send
Autodiscovery Configuration
Command
Description
6/0/5.10
router-CE1(cfg-if[ge6/0/5.10])# eth
cfm ma MA_1D mep remote autodiscover
aging-timer 120 emit-faults
Enable fault raising when connectivity breaks.

Set RMEP duration before aging it out: the range is
5 .. 43 200, the default value is 5.
Both autodiscovery and static RMEP can be configured simultaneously. The show CLI command
does not show duplicate entries and shows then only static configured RMEP entry (see chapter
3.2.5 Displaying Ethernet OAM Information section Displaying Maintenance Point).
Static Configuration
Command
Description
Define the remote MEP and optionally its MAC
6/0/5.10
address.
router-CE1(cfg-if[ge6/0/5.10])# eth cfm
ma MA_1D mep remote 10 00b0.c79e.5c7c

50
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
3.2.3
Configuring Linktrace
The following example shows how to configure the Ethernet OAM linktrace function. This function
is similar to IP traceroute. It verifies that when a source node initiates a Link Trace Message (LTM),
each intermediate node along the path sends a Link Trace Reply (LTR) back and forwards the LTM
to the destination node. Under normal operating conditions, it allows the operator to determine the
path used by the service through the network. While under fault conditions, it allows the operator
to isolate the fault location without a need to visit the site. The linktrace function requires a MEP,
MDs and MAs to be created first, see chapter 3.2.1 Configuring Local MEP. Within the linktrace
function static bridging is configured on the MIPs to forward Ethernet frames. The MIPs must be
configured on the same MD level as the MEPs are.
The example uses the topology shown in Fig. 18 as follows:
CE1, CE7 MEP
NE5 MIPs
NE5 configuration:
Command
Description
router-NE5(config)# interface
Provision a MIP instance on the same MD level
ge6/0/4.10
as MEP.
router-NE5(cfg-if[ge6/0/4.10])# eth cfm
ma MA_2U mip mip_ge604
router-NE5(config)# interface
Provision a MIP instance on the same MD level
ge6/0/3.10
as MEP.
router-NE5(cfg-if[ge6/0/3.10])# eth cfm
ma MA_2U mip mip_ge603
3.2.4
Running Linktrace
Command
Description
router-CE1# eth traceroute mep lmep606

dst-mac 00b0.c764.fd51
Traceroute a destination MAC address.

Routes can be linktraced for Ethernet MEPs
optionally using the destination MAC address or
destination MEPID.
Enter <ctrl+c> to exit from the command !

Transmitting with max-ttl=32, timeout 10 s
0 initiating 00b0.c764.fd4d
1 00b0.c7d7.11fa, ttl 31, forwarded
2 00b0.c7d7.11fb, ttl 30, forwarded
3 00b0.c764.fd51, ttl 29, terminal-MEP, relay-hit
76.8600-50133B
2011 Tellabs.

51
3 Ethernet OAM
3.2.5
Displaying Ethernet OAM Information
Displaying MD
It is possible to display MD information name (briefly), or detailed.
Command
Description
router-CE1# show eth cfm md name

DOMAIN_1
Display MD information by name.
MD :
Level:
MD Name:
MD Name Type:
Maintenance Associations:
DOMAIN_1
1
PROVIDER
String
MA_1D MA_1I MA_1U
Command
Description
router-CE1# show eth cfm md
Display MD information.
MD
DOMAIN_0
DOMAIN_1
DOMAIN_2
Level
0
1
2
MD Name
OPERATOR
PROVIDER
CUSTOMER
Command
Description
router-CE1# show eth cfm md config
List MD information as per configuration.
eth cfm md DOMAIN_0 level 0

Displaying MA
Command
Description
router-CE1# show eth cfm ma
Display MA information.
MA
MA_0D
MA_1D
MD
DOMAIN_0
DOMAIN_1
CCM
1s
100ms
MA information can be inspected by using a specific MA name. The following CLI command
gives an example.

52
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
Command
Description
router-CE1# show eth cfm ma name MA_1D
Display MA_1D information.
MA :
MD :
CCM:
Short-Name:
Short-Name Type:
Maintenance Points:
MA_1D
DOMAIN_1
100ms
MA_1D
short-name string
ge6/0/5.10 Down MEP
Displaying Maintenance Point

There are different options available to display the Maintenance Point (MP) detailed information.
The Maintenance Point brief information shows selected information in wide list format.
detail: Maintenance Point details
dm: Delay Measurement
interface: Interfaces
lm: Loss Measurement
log: CFM event logs
mep: Maintenance Association Endpoint
mip: Maintenance Domain Intermediate Point
name: Maintenance Point name keyword
rmep: Remote Maintenance Association Endpoint
Command
Description
router-NE1# show eth cfm mp
Display MP information.
The following examples show information displayed using the MP name or interface name. The
result of both show CLI commands is identical:
76.8600-50133B
2011 Tellabs.
Command
Description
router-CE1# show eth cfm mp name

lmep605
List MP information by MP name.

53
3 Ethernet OAM
Name :
Interface :
Level:
Type:
ID:
CCM:
Autodiscovery:
Aging Timer:
Emit-Faults:
MD:
MA:
Maximum Remote MEPs:
QoS:
Sending RDI:
lmep605
ge6/0/5.10
1
down
605
100ms
enabled
120
enabled
DOMAIN_1
MA_1D
16
be
Yes
Remote MEPs:
3.2.6
Type
State
Condition
Act On CCM
00b0.c79e.5c7c Discovered
Up
---
Yes
---
Down
Loc
Yes
Interface
Actual MAC
10
1111
Configured
Ethernet OAM CFM Ping

The following examples show the usage of the Ethernet ping CLI command.
There are different options to select the ping destination:
dst-mac: Destination MAC address
dst-mep: Destination Maintenance Association Endpoint
multicast: Multicast MAC address
multicast-mep: Multicast-MEP MAC address
Other ping options are:
qos: Quality of Service
size: Size of Ethernet packets sent
packets: Number of Ethernet packets to be sent
interval: Interval between probe packets
timeout: Timeout for waiting reply
Command
Description
router-CE1# eth ping mep lmep605

dst-mac 00b0.c79e.5c7c qos be size 100
packets 3 interval 100 timeout 5
Ping a destination MAC address.
Ping 00b0.c79e.5c7c:

54
46 data bytes
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
1 Reply 60 bytes from 00b0.c79e.5c7c, rtt 2.582 ms

Summary:
3 packets transmitted, 3 packets received, 0% packet loss, 0
payload mismatch
rtt min/avg/max=2.018/2.255/2.582 ms
3.2.7
Configuring QoS Mapping for Ethernet OAM PM

The following QoS mapping (unique one-to-one between priority and QoS) is provided as an
example and may be used on the Tellabs 8600 network elements for all configuration examples
presented in this document:
76.8600-50133B
2011 Tellabs.

55
3 Ethernet OAM
Command
Description
router(config)# mgmt-traffic qos cs7
Configure the QoS used for management traffic

(CLI (Telnet, SSH), BMP (including CCN), SNMP,
SFTP and syslog).
router(config)# qos mapping ingress

vlan-pri 7 qos cs7
vlan-pri 6 qos ef
vlan-pri 4 qos af4 drop-precedence low
vlan-pri 0 qos be
Configure mapping from the incoming packet

header QoS bits to the internal QoS classes.
router(config)# qos
cs7 vlan-pri 7
router(config)# qos
ef vlan-pri 6
router(config)# qos
af4 drop-precedence
router(config)# qos
af4 drop-precedence
router(config)# qos
af4 drop-precedence
router(config)# qos
af3 drop-precedence
router(config)# qos
af3 drop-precedence
router(config)# qos
af3 drop-precedence
router(config)# qos
af2 drop-precedence
router(config)# qos
af2 drop-precedence
router(config)# qos
af2 drop-precedence
router(config)# qos
af1 drop-precedence
router(config)# qos
af1 drop-precedence
router(config)# qos
af1 drop-precedence
router(config)# qos
be vlan-pri 0
Configures mapping from internal QoS classes to

the outgoing packet header QoS bits.

56
mapping egress qos

mapping egress qos
mapping egress qos
high vlan-pri 4
mapping egress qos
medium vlan-pri 4
mapping egress qos
low vlan-pri 4
mapping egress qos
high vlan-pri 3
mapping egress qos
medium vlan-pri 3
mapping egress qos
low vlan-pri 3
mapping egress qos
high vlan-pri 2
mapping egress qos
medium vlan-pri 2
mapping egress qos
low vlan-pri 2
mapping egress qos
high vlan-pri 1
mapping egress qos
medium vlan-pri 1
mapping egress qos
low vlan-pri 1
mapping egress qos
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
In the example above the vlan-pri=5 is not used. This is the priority which is also used for
Tellabs 8600 internal PDUs. However, it can still be used in the configuration if all other
QoS related guidelines are followed. Also, as recommended earlier, vlan-pri=7 (QoS=cs7) is
not used for Ethernet OAM measurements.
Notes on Tellabs 8600 Interface Configuration for Y.1731 Ethernet OAM

1.
Use on the port interface:

router(cfg-if[ge 0/0])# qos mapping use ingress traffic ip-dscp
2.
Use on the port interface and in the global mapping:

router(cfg-if[ge 0/0])# qos mapping use egress traffic ip-dscp
layer2-frame
3.
Use on the VLAN interface:

router(cfg-if[ge 0/0.10])# qos vlan egress vlan-pri
4.
It is suggested to always have ip-dscp in addition to vlan-pri, as that ensures that IP DSCP
markings get marked to every packet. Without it internal protocol frames (LDP,OSPF, etc) may
not go to QoS=cs7 as recommended, but rather to some other QoS class. This can cause the
ETH-LM frame count to appear corrupt.
Notes on QoS Mapping Configuration for Y.1731 Ethernet OAM
76.8600-50133B
2011 Tellabs.
1.
Ethernet OAM PM measurements are strictly per QoS. Thus it is important to maintain a unique
one-to-one mapping between VLAN-priority and QoS level on all priorities where PM is used.
This mapping needs to be preserved on the whole path where the PM measurement probes
(DMM/LMM requests and DMR/LMR responses) are travelling. If several VLAN-priorities
are mapped to a common QoS level, or if several QoS levels are mapped to a single VLAN-priority, it is not possible to utilize Ethernet OAM PM measurements on affected QoS levels/priorities.
2.
Ethernet OAM PM is designed to use at maximum seven QoS levels (be, af1, af2, af3, af4, ef,
cs7) per VLAN, and there are eight possible VLAN priority values (0-7), so if all priorities are
mapped, one QoS level will have to carry two priorities and thus this QoS level cannot be
used for PM measurements.
3.
Most internal protocol frames (LDP, OSPF, etc) are using QoS=cs7, which is mapped to VLANpriority=7, and Tellabs does not recommend that this priority class is used for payload frames,
nor should it be used for PM measurements. In addition to this, the CLI command qos mapping use egress traffic ip-dscp layer2-frame should be used on the port interfaces and the CLI
command qos vlan egress vlan-pri should be used on the VLAN interfaces to ensure that internal protocol frames stay on cs7=7 priority.
4.
If port level PM is used (no VLANs), only priority = 0 (typically QoS=be) should be used.
5.
If PWE3 is used, the vc-qos option should not be used. This option causes the outer VLAN
tag to be modified.
6.
Internal pseudowire circuits do not follow the QoS mapping scheme, and thus cannot be used
in the [Y.1731] application.

57
3 Ethernet OAM
3.2.8
Configuring Ethernet OAM PM - ETH-DM and ETH-LM

CLI configuration examples of Ethernet OAM performance monitoring are described below. The
examples focus only on the Ethernet OAM functionality. In conjunction with the Ethernet OAM
configuration, a configuration of Ethernet connectivity (cross-connection and tunneling) is required
and that is not covered in this chapter.
Fig. 19 Ethernet OAM Performance Monitoring
The PM functions reuse the same Ethernet OAM infrastructure as CFM. The entities used for CFM,
such as MAs, MEPs and MIPs, are applicable for PM as well. The PM functions are typically
end-to-end and MIPs do not participate in those functions. While the PM functions need to operate
on any applicable MA, they do not need to be available on all MAs and MEPs simultaneously.
ETH-DM is defined only for a pair of MEPs and for a given priority. However the pair of MEPs
can be part of a multipoint MA. Hence, the same MEP may conduct separate measurements with
multiple other MEPs simultaneously.
ETH-LM is defined only for a pair of MEPs and for a given priority.
Example below illustrates what is involved in a simple ETH-DM and ETH-LM measurement
session configuration on a VLAN(1000) interface at NE5:
Example on the network element QoS configuration can be found in chapter 3.2.7 Configuring
QoS Mapping for Ethernet OAM PM. MD and MA must also be configured, see chapter
3.2.1 Configuring Local MEP for examples.
VLAN(1000) interface at NE5:

58
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
Command
Description
router(cfg-if[ge 7/1/0])# qos mapping

enable
Configure internal QoS to IP/MPLS (and vice

versa) header bit mapping to in use. By default,
qos mapping is enabled.

use ingress traffic ip-dscp
Configure QoS mapping to IP DSCP bits.

Configure QoS mapping to both IP DSCP bits and
use egress traffic ip-dscp layer2-frame Ethernet PRI bits.
router(cfg-if[ge 7/1/4.1000])# eth cfm
ma MA_2U mep local lmep714 1 up ccm
send
Create a local MEP.

ma MA_2U mep remote autodiscover
Discover remote MEPs via CCM.

ma MA_2U mep remote 2
Create a remote MEP (the MAC address is

discovered via CCM autodiscovery).
router(cfg-if[ge 7/1/4.1000])# eth

cfm ma MA_2U mep remote 2 dm qos be
interval 1000
Start an ETH-DM session on be with a 1000ms

interval.

ma MA_2U mep remote 2 lm qos be
Start an ETH-LM session on be with the default

(10 sec) interval.
router(cfg-if[ge 7/1/4.1000])# qos vlan Define how Ethernet VLAN QoS is decided at
egress vlan-pri
VLAN granularity.
The following CLI configuration command has all ETH-DM parameters. Note on some of them:
selection offset - indicates the pairing of frames for IFDV measurement. For example, if the
selection offset is set to 3, IFDV will be calculated based on all pairs of DMRs which are three
frames apart.
low-percentile / hi-percentile - indicates the percentile by which certain metrics are to be reported. For example, if set to 95%, the report for a given metrics will indicate the frame delay
value under which 95% of the measurements fall.
eth cfm ma MA_2U mep remote 2 dm qos be interval 1000
selection-offset 2 low-percentile 80 hi-percentile 95
The following ETH-LM configuration is used on the responder-only interface. Even if the network
element is not actively initiating and recording ETH-LM measurements, it needs to be provisioned
as responder-only if it is to participate in measurements initiated by a remote network element:
eth cfm ma MA_2U mep remote 2 lm qos be passive
76.8600-50133B
2011 Tellabs.

59
3 Ethernet OAM
Examples of Clear CLI Command for LM and DM

Command
Description
router# clear eth cfm mp name lmep714

dm qos be
router# clear eth cfm mp name lmep714
lm qos be
Clear PM at the source, i.e. at the line card where

measurements are gathered and calculated, so it
may take up to a minute (after the counts were
zeroed out) to show new counts on the CLI due
to the ~60 sec CDC PM collection interval (and at
that point they may not be zero any more).
Examples of Show CLI Command for LM and DM

Command
Description
router# show eth cfm mp name lmep714 lm Display Ethernet OAM frame loss performance
monitoring results.
Ethernet OAM [Y.1731] frame loss performance monitoring results:

MEP: lmep714 MA: MA_2U RMEP: 2 QOS: be
Current 24 h
Elapsed time: 68535 secs End time: 05:16:40 Dec 1 2010
PM measurement accuracy of this period compromised: YES
Near End Frames Tx: 1257
Far End Frames Tx: 4112
Far End Frames Rx: 1257 Far End Frames Lost: 0
Near End Frames Rx: 4112 Near End Frames Lost: 0
Current 15 min
History 15 min
Command
Description
router# show eth cfm mp name lmep714 dm Display Ethernet OAM frame delay performance
monitoring results.
Ethernet OAM [Y.1731] frame delay performance monitoring results:

MEP: lmep714 MA: MA_2U RMEP: 2 QOS: be
Current 24 h
Near End Two Way Delay: min/avg/max=3/3/3 microseconds
60
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
Near End One Way Delay: min/avg/max=-40720/63421/453326

microseconds
Far End One Way Delay: min/avg/max=-453323/-63418/40723
microseconds
Near End Frame Delay Variation (One Way): avg/max=109/2966
microseconds
Far End Frame Delay Variation (One Way): avg/max=99/2966
microseconds
Current 15 min
Near End Two Way Delay: min/avg/max=3/3/3 microseconds
Near End One Way Delay: min/avg/max=20869/28748/29811
microseconds
Far End One Way Delay: min/avg/max=-29808/-28745/-20865
microseconds
Near End Frame Delay Variation (One Way): avg/max=16/593
microseconds
Far End Frame Delay Variation (One Way): avg/max=16/594
microseconds
History 15 min
Near End Two Way Delay:
min/avg/max/70perc/90perc=3/3/3/3/3 microseconds
Near End One Way Delay: min/avg/max/70perc/90perc=-19856/17065/16521/-16775/-16536 microseconds
Far End One Way Delay: min/avg/max/70perc/90perc=16518/17069/19860/18026/19622 microseconds
Near End Interframe Delay Variation (One Way):
avg/max/70perc/90perc=22/585/22/98 microseconds
Far End Interframe Delay Variation (One Way):
avg/max/70perc/90perc=23/584/22/98 microseconds
Note that in the example above the two-way delay measurements are accurate, but the one-way delay
measurements are not as the system clocks between the two MEP nodes are not synchronized. The
negative number in one-way DM indicates that the remote node has its clock in the future. Also
note that the function collects 32 bins for a 15-minute PM period and 1 bin for a 24-hour period.
Provisioning CLI Commands for Direct Connection Ethernet Port Based PM
[Y.1731] on direct port based connection involves PM measurements between two Down MEPs
which are configured on port (non-VLAN) interfaces.
CE7_8605:
76.8600-50133B
2011 Tellabs.
Command
Description
router# interface ge 0/1

router(config)# eth cfm ma MA_2D mep
local lmep26 26 down ccm send
Create Down MEP with id=26 in MA belonging to

MD on level 2, CCMs enabled.

remote autodiscover
Discover remote MEPs via CCM

61
3 Ethernet OAM

remote 25 00b0.c7d7.1089
Configure RMEP (the MAC address is optional

because autodiscover is provisioned).

remote 25 dm qos be interval 1000
Start continuous ETH-DM between LMEP=26 and

RMEP=25 (int=1000ms on be).

remote 25 lm qos be interval 10000
Start continuous ETH-LM between LMEP=26 and

router(cfg-if[ge 0/1])# qos mapping

enable

router(cfg-if[ge 0/1])# qos mapping use Configure QoS mapping to IP DSCP bits.
ingress traffic ip-dscp
router(cfg-if[ge 0/1])# qos mapping use Configure QoS mapping to both IP DSCP bits and
egress traffic ip-dscp layer2-frame
Ethernet PRI bits.
NE5_8630:
Command
Description
router# interface ge 7/1/1



remote autodiscover

remote 26 00b0.c765.b54e
Configure RMEP (the MAC address is optional

because autodiscover is provisioned).

remote 26 dm qos be interval 1000


remote 26 lm qos be interval 10000


enable



Provisioning CLI Commands for Tunneled VLAN PWE3 over Routed VLAN Connection
[Y.1731] on PWE3 tunneled connection (VLAN based) carried over a routed connection (VLAN
based) typically involve PM measurements between:
62
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
Two Down MEPs which are configured on routed interfaces (VLAN based)
Two Up MEPs which are configured on tunneled interfaces (VLAN based)
This example shows how the two Up MEPs in Fig. 19 reference points 1 and 4 are setup. It is
assumed that the VLAN PWE3 (PWE3 circuit CE7_to_NE5/NE5_to_CE7) and the routed VLAN
connection between CE7 and NE5 have already been setup. The Down MEPs configuration over the
routed VLAN between Fig. 19 reference points 2 and 3 is not included in the example.
Please, refer to chapter 3.2.1 Configuring Local MEP for MEP configuration and 3.2.7 Configuring
QoS Mapping for Ethernet OAM PM for QoS configuration and notes.
CE7_8605:
Command
Description
router(cfg-if[ge 0/0])# qos mapping

enable

router(cfg-if[ge 0/0])# qos mapping use Configure QoS mapping to IP DSCP bits.
ingress traffic ip-dscp
router(cfg-if[ge 0/0])# qos mapping use Configure QoS mapping to both IP DSCP bits and
egress traffic ip-dscp layer2-frame
Ethernet PRI bits.
router(config)# pwe3 circuit CE7_to_NE5 Specify a PWE3 circuit, i.e. a layer 2 protocol
100 mpls manual
tunneled over MPLS.
router (config)# interface ge
router (cfg-if[ge 0/0.2000])#
circuit CE7_to_NE5
shutdown
0/0.2000
pwe3
no
exit
router(cfg-if[ge 0/0.2000])# eth cfm ma Create Up MEP with id=42 in MA belonging to

MA_2U mep local lmep42 42 up ccm send
router(cfg-if[ge 0/0.2000])# eth cfm ma Discover remote MEPs via CCM.
MA_2U mep remote autodiscover
router(cfg-if[ge 0/0.2000])# eth cfm ma Configure RMEP.
MA_2U mep remote 41
router(cfg-if[ge 0/0.2000])# eth cfm ma Start continuous ETH-DM between LMEP=42 and
MA_2U mep remote 41 dm qos af1 interval RMEP=41 (int=1000ms on af1).
1000
router(cfg-if[ge 0/0.2000])# eth cfm ma Start continuous ETH-LM between LMEP=42 and
MA_2U mep remote 41 lm qos af2 interval RMEP=41 (int=1000ms on af2).
10000
76.8600-50133B
2011 Tellabs.

63
3 Ethernet OAM
router(cfg-if[ge 0/0.2000])# qos vlan

egress vlan-pri
Define how Ethernet VLAN QoS is decided at

VLAN granularity.
router(cfg-if[ge 0/0.2000])# qos vlan

ingress vlan-pri
Define how Ethernet VLAN QoS is decided

at ingress side VLAN granularity; as PWE3 is
configured, Layer 2 QoS is preferred.
NE5_8630:
Command
Description

enable



router(config)# pwe3 circuit NE5_to_CE7 Specify a PWE3 circuit, i.e. a layer 2 protocol
100 mpls manual
tunneled over MPLS.
router (config)# interface ge
7/1/0.2000
router (cfg-if[ge 7/1/0.2000])# pwe3
circuit NE5_to_CE7
router (cfg-if[ge 7/1/0.2000])# no
shutdown
router (cfg-if[ge 7/1/0.2000])# exit

ma MA_2U mep local lmep41 41 up ccm
send
Create Up MEP with id=41 in MA belonging to


ma MA_2U mep remote autodiscover

ma MA_2U mep remote 42
Configure RMEP.

ma MA_2U mep remote 42 dm qos af4

RMEP=42 (on af4).

ma MA_2U mep remote 42 lm qos ef

RMEP=42 (on ef).
egress vlan-pri
VLAN granularity.
router(cfg-if[ge 7/1/0.2000])# qos vlan Define how Ethernet VLAN QoS is decided
ingress vlan-pri
at ingress side VLAN granularity; as PWE3 is
configured, Layer 2 QoS is preferred.

64
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
Provisioning CLI Commands for ELP and Y.1731 PM

Configuration example below shows [Y.1731] PM application provisioning when ELP protection
is used. This is a variant of configuration for the routed VLAN connection and involves PM
measurements between two Down MEPs.
This example shows how the two Down MEPs in Fig. 19 reference points 4 and 5 are setup. It is
assumed that the ELP group (CE1_ELP/NE5_ELP: primary ge 7/1/0 backup ge 5/1/0, primary ge
7/1/0 backup ge 6/1/0) has already been setup.
Please, refer to chapter 3.2.1 Configuring Local MEP for MEP configuration and 3.2.7 Configuring
QoS Mapping for Ethernet OAM PM for QoS configuration and notes.
CE1_8660:
Command
Description

enable



76.8600-50133B
2011 Tellabs.
router(cfg-if[ge 7/1/0.2000])#
label-switching
Enable label switching on interface ge 7/1/0.2000.
router(cfg-if[ge 7/1/0.2000])# ip
address 10.10.10.164/24
Set the IPv4 address of the interface.
router(cfg-if[ge 7/1/0.2000])# mpls

label protocol ldp
Enable LDP on the specified interface.
router(cfg-if[ge 7/1/0.2000])# mpls

label protocol rsvp
Enable RSVP message exchange on the interface.



remote autodiscover

remote 24
Configure RMEP.

remote 24 dm qos af1 interval 1000

RMEP=24 (int=1000ms on af1).

65
3 Ethernet OAM

remote 24 lm qos af2 interval 10000

egress vlan-pri
VLAN granularity.
NE5_8630:
Command
Description

enable

QoS mapping is enabled.


ma MA_1D mep local lmep24 24 down ccm
send


ma MA_1D mep remote autodiscover

ma MA_1D mep remote 23
Configure RMEP.

cfm ma MA_1D mep remote 23 dm qos af1
interval 1000


cfm ma MA_1D mep remote 23 lm qos af2
interval 10000

egress vlan-pri
VLAN granularity.
3.2.9
Ethernet OAM ETH-DM-PING Utility

The ETH-DM-PING utility can be used for quick delay measurement and should always be
used for [Y.1731] PM troubleshooting. It can be entered in place of any continuous ETH-DM
measurement session, but not in parallel (i.e. we cannot have both continuous ETH-DM session
and ETH-DM-PING session between a pair of MEPs on the same QoS.) The advantage of
ETH-DM-PING is that it relies only on the timestamps to match a DMR response to its DMM
request, and thus it will work even if QoS is not mapped properly along the path. Moreover, it will
report the outgoing VLAN priority of the DMM and receiving VLAN priority of the DMR message.

66
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
The ETH-DM-PING utility example below assumes that the local MEP (LMEP) and remote MEP
(RMEP) have been defined, and that DMM probe packets are to be sent at the interval of 1000 ms:
Command
Description
router# eth dm-ping mep lmep055 dst-mep The log for the DMR reply shows the MAC address
56 qos af11 packets 2 interval 1000
of the responding RMEP, delays, and priorities.
In the example output, pri=1/1 tells us that the transmitted DMM probe was sent on the VLAN
priority = 1, and that the received DMR response arrived on VLAN priority = 1 as well.
Enter <ctrl+c> to exit from the command !
DM-Ping 56
1 DMR Reply from 00b0.c7d7.1089, netwd 45 neowd 19674 feowd
-19628 neifdv 0 feifdv 0, pri=1/1
2 DMR Reply from 00b0.c7d7.1089, netwd 45 neowd 19668 feowd
-19622 neifdv 0 feifdv 0, pri=1/1
Summary:
Near End Two Way Delay: min/avg/max = 45 / 45 / 45 microsec
Near End One Way Delay: min/avg/max/90-percentile = 19668 /
19671 / 19674 / 19668 microsec
Far End One Way Delay: min/avg/max/90-percentile = -19628 /
-19625 / -19622 / -19628 microsec
Near End Interframe Delay Variation (One Way): avg/max/90percentile = 0 / 0 / 0 microsec
Far End Interframe Delay Variation (One Way): avg/max/90percentile = 0 / 0 / 0 microsec
Total of 2 DMM frames sent, 2 DMR frames received.
Note that in the example above the two-way delay measurements are accurate, but the one-way delay
measurements are not as the system clocks between the two MEP nodes are not synchronized. The
negative number in one-way DM indicates that the remote node has its clock in the future. Also
note that the function collects 32 bins for a 15-minute PM period and 1 bin for a 24-hour period.
76.8600-50133B
2011 Tellabs.

67
4 Ethernet Link Aggregation

4.1
Introduction
Ethernet Link Aggregation (LAG) [IEEE802.3ad] is a method for bundling Ethernet links so that
they appear to upper layers as one higher-capacity Ethernet link. Traffic is distributed to the member
links by a load balancing algorithm.
In the Tellabs 8630 access switch and Tellabs 8660 edge switch LAG is only supported in IFC2
with the following IFM:
The benefits of Ethernet Link Aggregation include:
Increase of Ethernet link bandwidth beyond the bandwidth of a single physical link.
Increase of bandwidth in incremental steps, e.g. from 100 Mbps to 200 Mbps instead of an orderof-magnitude increase from 100 Mbps to 1000 Mbps.
Interface protection by means of load balancing; if one of the member links fails, load balancing
is automatically re-configured so that the remaining links carry the traffic.
4.1.1
Application of Link Aggregation

Link Aggregation can be used in Ethernet interfaces facing the Metro Ethernet. Fig. 20 illustrates
two applications of LAG. In the first example, the Ethernet interfaces in the Tellabs 8600 network
element are MPLS enabled and carry pseudowires. Link Aggregation provides higher capacity to
the logical interface and interface protection for any kind of pseudowires. In the second example,
the Link Aggregation group is an IP routed interface that provides load sharing and interface
protection for IP routed traffic.

68
76.8600-50133B
2011 Tellabs.
Fig. 20 Link Aggregation Applications
4.1.2
References
[IEEE 802.3ad]
4.2
4.2.1
Link aggregation was formerly defined in the IEEE 802.3ad specification which
has now merged in the main IEEE 802.3 document (chapter 43).
Operation
Ethernet Link Aggregation Group
The Tellabs 8600 system supports Ethernet Link Aggregation in 8x100/1000BASE-X R2 interface
module in Tellabs 8660 edge switch and Tellabs 8630 access switch. The member links of a Link
Aggregation group must be on the same IFM. Within each IFM the links can be joined into groups
in any combination. In particular, the maximum number of members in a group is 8, which means
that all links of one IFM can belong to the same group. The maximum number of groups in one
network element is 32.
In general a single IFM can forward traffic in a typical case of up to 2.5 Gbps of the actual physical
line rate, which corresponds to the maximum bandwidth of a Link Aggregation group. A single
card (IFC) can forward traffic in a typical case of up to 3.5 Gbps of the actual physical line rate.
For more information on adjustable forwarding capacity, refer to Tellabs 8600 Managed Edge
System Interface Configuration Guide.
76.8600-50133B
2011 Tellabs.

69
Fig. 21 Intra-IFM Link Aggregation
Because Link Aggregation groups are restricted to one IFM, they do not provide IFC protection.
This is achieved by using IP or MPLS layer protection as illustrated in Fig. 22. The primary path
and backup paths are forwarded through different link aggregation groups.
Fig. 22 Intra-IFM Link Aggregation Group Protection
After a Link Aggregation group is created, it can otherwise be configured like any Ethernet interface.
The group can have e.g., an IP address and MPLS enabled.
For detailed information about LAG group attributes, refer to chapter 4.2.2 Link Aggregation
Configuration.
For more information about Link Aggregation group statistics and faults for, refer to chapters
4.4 Statistics and 4.3 Faults, respectively.
Load balancing works by first applying a hash calculation algorithm to a set of protocol header fields
of each packet. The choice of fields to be used in the calculation can be configured by the user.
The calculation produces a number called the hash result. The packet is then mapped to one of
the member interfaces of the group by using a table that maps all possible values of the hash result
onto members. All packets that contain the same values of the header fields (e.g. MPLS label), i.e.
belong to the same flow, are thus mapped to the same interface, which guarantees that the ordering
of packets within this flow is preserved. The choices of headers to be used in a hash calculation are:
70
76.8600-50133B
2011 Tellabs.
4.2.2
Protocol
Configuration
Application
Hash Calculation
MPLS over
Ethernet
Pseudowires over LAG interface
MPLS labels + IP DA/SA (if available)

+ optionally IP protocol and L4
destination/source port (if available)
IP over Ethernet
IP routing over LAG interface
IP DA/SA (if available) + optionally IP

protocol and L4 destination/source port (if
available)
Anything over
Ethernet
Ethernet pseudowire endpoint.

Interface between Tellabs 8600 and
customer Ethernet equipment.
MAC DA/SA + optionally Eth Type +

VLAN ID(s) (if available); optionally one
or two VLAN ID(s) only
Link Aggregation Configuration

The most important configuration actions for a Link Aggregation group are group creation, member
addition, member removal, and group deletion.
Members
All members of the group must be full duplex and running the same speed, which can be 100 or
1000 Mbps. This speed is either configured by the user before joining any members, or determined
by the speed of the first joined member if not configured by the user before. After configuring the
required member speed or joining the first member, other members can be added only if they are
running the required speed.
The first joined member has a special role and it cannot be removed from the group until the whole
group is deleted.
An interface cannot be added to a group if there are VLANs defined on that interface. It is not
possible to have VLANs as members of an aggregate, in other words, only physical Ethernet
interfaces can be members of an aggregate.
The member links of an aggregate cannot be part of an Ethernet Link Protection (ELP) group. The
aggregate itself cannot be part of an ELP group either.
Attributes of Group
The following properties of a Link Aggregation group are configurable by the user:
Maximum Transmission Unit. If a group-specific MTU has not been provided by the user, the
aggregate will use the MTU of the first member link that was added to the group
MAC address. If a group-specific MAC address has not been provided by the user, the aggregate
will use the MAC address of the first member link that was added to the group
The number of member links that have to be in up state in order for the group to be considered to
be in up state. If less than the configured number of member links is up, a fault is raised for the
group
76.8600-50133B
2011 Tellabs.

71
The protocols to be used in hash calculation for load balancing. The alternatives are:
1.
multiple protocols, meaning the following:

For IP packets over Ethernet: use the IP SA and DA, and optionally the IP Protocol
field and layer 4 source and destination port fields
For MPLS packets not containing an IP header: use MPLS label(s)
For IP packets over MPLS: use MPLS label(s), IP SA and DA, and optionally the IP
Protocol field and layer 4 source and destination port fields
2.
Ethernet only: use Ethernet SA and DA, and optionally the Ethernet Type field
3.
outer VLAN id only
4.
inner and outer VLAN id
Optional choice of protocol header fields in hash calculation:

for IP headers, whether to use the IP Protocol field
for IP headers, if the IP Protocol field has been chosen, whether to use also the layer 4 source
and destination port fields (if the IP Protocol field has not been chosen, layer 4 fields will
not be used)
in the Ethernet only case, whether to use the Ethernet Type field
Automatic rebalancing of the load balancer in case of persistent uneven load. This functionality
can be enabled or disabled
Line loopback
Equipment loopback
Loopback timeout
The user can execute the following actions on an aggregate:
Forced rebalancing of the load balancer: the network element will reorganize the mapping of
traffic flows into member interfaces, in order to achieve a more even load balancing. As a side
effect this may cause packet misorder within flows during a short period
Query of load balancing result: the user gives the values of some packet header fields as input,
and gets as output the name of the interface into which the load balancer maps packets having
those values
Clearing of group statistics
4.2.3
Bandwidth Allocation
The allocation of the internal bandwidth resources (cell bandwidth) of a network element works
in a particular way in Link Aggregation groups. In the user interface, cell bandwidth is not
allocated directly to the group but the bandwidth allocations are made for the member interfaces
individually, and the group will have the sum of the members cell bandwidths in its use. The
allocated bandwidth of a member remains in use in the group as long as the membership continues,
even if the member may be in down state.
The Active bandwidth shown in the user interface is the smaller of these two:
the total allocated cell bandwidth
the sum of member interface speeds of the members whose link state is up

72
76.8600-50133B
2011 Tellabs.
Thus Active bandwidth is the maximum bandwidth that could currently be received or transmitted
from/to the network through the Link Aggregation group.
4.2.4
Loopbacks
Line and equipment loopbacks and loopback timeout can be configured for a Link Aggregation group
in the same way as for an individual Ethernet interface. At the member interface level, on the other
hand, loopbacks cannot be configured during membership. For more information on loopbacks,
refer to Tellabs 8600 Managed Edge System Test and Measurement Configuration Guide.
4.2.5
Synchronization
The member links of an aggregate can be used as synchronization sources independently of their
membership. However, SSM sending is not supported, because all packets going through LAG
are distributed to member links by hashing, so that it cannot be guaranteed that an SSM PDU is
transmitted through the link whose synchronization status it refers to.
The aggregate itself has no role in synchronization.
4.3
Faults
Two faults are related to a Link Aggregation group:
the Member links down fault is raised if one or more member links are down
the Link down fault is raised if less than the configured minimum number of links are up. This
fault masks the Member links down fault
The interface-specific faults of the member interfaces are not affected by their membership.
4.4
Statistics
The same statistics counters exist for Link Aggregation groups as for individual Ethernet interfaces.
The group-level counters contain the sum of statistics of the current member interfaces starting from
the beginning of their membership in the group, or the latest clearing of the group-level counters.
The statistics of earlier, removed members are not included in the group statistics.
The interface-level statistics of the member interfaces are not affected by their membership. In
particular the group statistics can be cleared without affecting the members interface-level statistics.
Interface-level statistics can be cleared by interface-level commands.
4.5
Dimensioning
Tellabs 8660 edge switch and Tellabs 8630 access switch support up to 32 aggregates, each of which
can have up to 8 members.
76.8600-50133B
2011 Tellabs.

73
4.6
Restrictions
Link Aggregation Control Protocol (LACP) is not supported.
LAG does not support VLANs.
4.7
4.7.1
Ethernet Link Aggregation CLI Configuration Examples

Creating a Link Aggregation Group
Command
Description
router(config)# interface lag 5
Create a Link Aggregation Group.
router(cfg-if[lag5])# eth lag mode

mbr-speed 1000
Define the required speed of member links. Links

of any other speed cannot be joined to the group.
If this CLI command is not given, the speed of the
first joined member defines the required speed: the
next members must have the same speed as the first
one. After joining the first member to the group,
this CLI command has no effect.
router(cfg-if[lag5])# eth lag min-links Define the minimum number of member links that
2
must be up in order for the group to be up.
router(cfg-if[lag5])# eth lag mtu 1400
Define the Ethernet-level Maximum Transmission

Unit (MTU) for the group. If this CLI command
is not given, the MTU of the first joined member
defines the MTU of the group.
router(cfg-if[lag5])# eth lag

mac-address aaaa.bbbb.cccc
Define the MAC address for the group. If this CLI

command is not given, the MAC address of the
first joined member defines the MAC address of
the group.

74
76.8600-50133B
2011 Tellabs.
4.7.2
Joining Links to a Link Aggregation Group

Command
Description
router(cfg-if[ge12/1/4])# no send-ssm
Disable SSM sending for the links that are going

to be joined to the group, if enabled. During their
membership, the member links can still be used as
clock sources individually, but they cannot send
SSM information.
router(cfg-if[lag5])# eth lag member

ge12/1/4
ge12/1/5
ge12/1/6
Join three links to the group.
router(config)# bandwidth-if module

Allocate bandwidth to the member links. The
12/1 limits 100 100 100 100 500 500 500 bandwidth allocation is always done for all
100
interfaces of the interface module at the same
time. The sum of the allocations for the member
links will be the allocated bandwidth of the group.
During their group membership, the load of the
member links is not restricted link by link. In this
example, the member links will not be restricted
to 500 Mbps bandwidth, but the group will be
restricted to 1500 Mbps.
router(config)# interface
router(cfg-if[ge12/1/4])#
admin-status enabled
ge12/1/5
ge12/1/6
4.7.3
ge12/1/4
eth lag
Enable traffic on the member links.
interface
eth lag
interface
eth lag
Minimizing Traffic Disturbance When Joining a Link

The administrative status of a member link can be enabled in the Rx and Tx directions separately. By
making use of this, the traffic disturbance due to the joining of a new member link can be minimized.
Consider a Link Aggregation Group that connects network elements A and B. A new member link is
joined to the group. If the user now starts by enabling both Rx and Tx in, say, A, then A will start
to send some of the traffic to the new member link, although B is not prepared to receive it. This
traffic disturbance will continue until the user enables Rx and Tx in B as well. But if Rx in both
network elements is enabled first and only then Tx, then the traffic disturbance will be limited to the
execution times of HW configuration actions inside the network elements.
76.8600-50133B
2011 Tellabs.

75
4.7.4
Command
Description
A(cfg-if[lag5])# eth lag member

ge12/1/7
A(cfg-if[lag5])# interface ge12/1/7
A(cfg-if[ge12/1/7])# eth lag
admin-status rx-enabled
Join a new link to the group in network element A

and enable the Rx direction.
B(cfg-if[lag12])# eth lag member

ge6/1/1
B(cfg-if[lag12])# interface ge6/1/1
B(cfg-if[ge6/1/1])# eth lag adminstatus rx-enabled
Join a new link to the group in network element

B and enable the Rx direction. Note that the
identifier of the group (in this example lag5 in
network element A and lag12 in network element
B) does not have to be the same in the two network
elements, because it is not visible to the other
element.
A(cfg-if[ge12/1/7])# eth lag

Enable also the Tx direction in network element A.
B(cfg-if[ge6/1/1])# eth lag adminstatus enabled
Enable also the Tx direction in network element B.
Removing Links from a Link Aggregation Group

Command
Description
router(cfg-if[lag5])# no eth lag member Remove a link from a group.

ge12/1/6
The first joined member of a group cannot be removed from the group.
4.7.5
Removing a Link Aggregation Group

Command
Description
router(config)# no int lag5
Remove a Link Aggregation Group. The member

links are released and can be used as normal
Ethernet interfaces. The link-specific MTU and
MAC address that they had before joining the
group are restored.

76
76.8600-50133B
2011 Tellabs.
4.7.6
Configuring Load Balancing Parameters

Load balancing between the member links of a Link Aggregation Group is based on a two-phase
process. In the first phase a hash key is calculated from certain header fields of a packet. In the
second phase a mapping table is used to map the calculated hash key to one of the groups member
links. The packet will then be forwarded to this link.
The user can define which header fields are used in the hash key calculation. The choices are:
Ethernet: The following fields are used:
Optionally also Ethernet Type can be used
VLAN ID: The following fields are used:
Outer VLAN ID
Multi-VLAN ID: The following fields are used:
Outer VLAN ID
Inner VLAN ID, if contained in the frame
Multi-protocol: The following fields are used, if contained in the frame:
MPLS labels (up to 4 labels)
IPv4 Source Address
IPv4 Destination Address
If an IPv4 header is contained, optionally also IP Protocol field can be used
If IP Protocol field is used, there is a further option to use also L4 Destination Port and L4
Source Port
If the above described load balancing process leads to an uneven load balancing, the user can
command the system to rebalance the mapping table. The system does the rebalancing on the
basis of traffic statistics.
The user can also configure the system to do the rebalancing automatically, if it detects a persistent
uneven load.
76.8600-50133B
2011 Tellabs.
Command
Description
router(cfg-if[lag5])# eth lag loadbalance hash-protocols multi-protocol
Define that MPLS labels and IPv4 Source Address

and Destination Address, if they are contained in
the frame, will be used in hash calculation for load
balancing.

load-balance opt-hash-fields
ip-protocol ip-l4-port
Define that in addition to IPv4 Source Address

and Destination Address, also IP Protocol, L4
Destination Port and L4 Source Port fields will be
used in hash calculation for load balancing.

load-balance auto-rebalance
Enable automatic rebalancing on persistent uneven

load.

77
By giving the following command the user can force the system to reconfigure immediately the
mapping table that is used in load balancing. The reconfiguration is based on traffic statistics. The
reconfiguration algorithm is not configurable.
4.7.7
Command
Description

load-balance rebalance
Reconfigure the load balancing.
Configuring Member Link Properties during Membership

The following CLI commands are applicable to the member links of a Link Aggregation Group
individually:
Interface Basic CLI Commands
clear interface statistics
description
show interface
shutdown-if
Interface Ethernet CLI Commands
clock-source-id
eth bandwidth packet-adjustment
eth bandwidth rate-limit
laser
pause-frame
Interface Synchronization CLI Commands
The following Quality of Service CLI commands are applicable to the member links of a Link
Aggregation Group individually, but only the settings of the first joined member affect the group
traffic. If the Quality of Service properties of the other member links are configured during
membership, the settings become effective after the link is removed from the group or the whole
group is removed.
qos mapping enable
service-policer (layer1)
service-shaper (layer1)
rx-qos-queue
tx-qos-queue
4.7.8
Configuring L2/L3 Properties of a Link Aggregation Group

The following CLI commands are applicable to a Link Aggregation Group in the same way as to a
normal Ethernet interface. Refer to Tellabs 8600 Managed Edge System Interface Configuration
Guide for further details:

78
76.8600-50133B
2011 Tellabs.
Interface Basic CLI Commands

clear interface statistics
description
report
show ip interface
show interface
shutdown
Interface Ethernet CLI Commands
dot1q svlan ethertype
encapsulation
loopback
IP Basic CLI Commands
IP Hosting CLI Commands
IP Routing CLI Commands
IP VPN CLI Commands
Layer 2 Tunneling CLI Commands
MPLS Basic CLI Commands
MPLS LDP CLI Commands
MPLS RSVP-TE CLI Commands
Quality of Service CLI Commands
bandwidth-constraint
bc-mode
clear policer statistics
clear queue statistics
qos mapping use
reservable-bandwidth
service-policer
service-shaper
4.7.9
Creating an IP Interface on a Link Aggregation Group

An IP interface can be created on a Link Aggregation group as if on a normal Ethernet interface.
Once created, it can be used in the same way as any IP interface on top of a normal Ethernet interface.
76.8600-50133B
2011 Tellabs.
Command
Description
router(cfg-if[lag5])# ip address
10.10.10.1/24
Give the group an IPv4 address.
router(cfg-if[lag5])# no shutdown
Release the interface from L3 shutdown.

79
4.7.10
Showing and Clearing of Statistics

Command
Description
router# configure terminal

ge8/0/0
ge8/0/1
Create a LAG group and add two GE interfaces

as members.
Note! Activate now the LAG group (e.g. using
CLI commands eth lag admin-status enabled,
ip address, no shutdown) as described in other
chapters. If trying to display statistics when the
LAG group has been created but not activated, the
statistics will show zero.
router# show interface lag0
The output shows the number of packets and octets

that have been transmitted and received through
the LAG group (i.e. the sum of packets and
octets transmitted and received through the group
members) since it was created.
router# show interface ge8/0/0

the GE interface since the interface statistics were
last cleared. The counts may thus be due to traffic
transmitted and received both before and after the
interface was joined to the LAG group.
router# clear interface statistics lag0 The group-level statistics are cleared. The output
of the show interface CLI command shows
the number of packets and octets that have been
transmitted and received through the LAG group
since clearing. Member-level statistics are not
cleared.

the GE interface since the interface statistics were
last cleared. They have not been affected by the
group-level clear CLI command.

ge8/0/2
router(cfg-if[lag0])# quit
router(config)# quit
A member is added in the LAG group. The packet

and octet counts of the member contribute to
group-level statistics starting from the moment
when the member is added.

A member is removed from the LAG group. The
packet and octet counts that were accumulated
router(cfg-if[lag0])# no eth lag member from the member during its membership remain
ge8/0/1
part of the group-level statistics.
router(cfg-if[lag0])# quit
router(config)# quit

80
76.8600-50133B
2011 Tellabs.
76.8600-50133B
2011 Tellabs.
router# clear interface statistics

ge8/0/0
The member-level statistics of a GE interface are

cleared. The output shows the number of packets
and octets that have been transmitted and received
through the GE interface since clearing.
The output shows the number of packets and

octets that have been transmitted and received
through the GE interface since group-level
clearing. Group-level statistics are not affected by
member-level clearing.

81
5 Ethernet Link Protection

5.1
Introduction and Usage Examples

The Tellabs 8600 system supports Ethernet Link Protection (ELP) in Tellabs 8660 edge switch,
Tellabs 8630 access switch and Tellabs 8620 access switch. ELP may be used to protect network
from Ethernet link failures in various network topologies and applications. For example, it may
be used to create a resilient connection between a Tellabs 8600 IP/MPLS network element and an
Ethernet transport network, as illustrated in the figure below.
Fig. 23 ELP for Ethernet Transport Network Interface Protection
When the currently active link is detected to be down, Tellabs 8660 edge switch moves the logical
interface (including IP and MAC addresses) from the currently active physical interface to the
backup physical interface. Since the IP and MAC addresses remain the same, the switchover is
transparent to IP and MPLS layers and traffic starts to flow immediately after the Ethernet transport
network has adapted to the changed topology. To accelerate Ethernet transport network adaptation,
Tellabs 8660 edge switch sends learning frames (gratuitous ARP by using the MAC address of the
ELP group as the source address) which makes the Ethernet switches to quickly update switching
tables.
As another example, Ethernet Link Protection may also be used on user side interfaces, for example
when an Ethernet access network is used to carry traffic from customer sites to the Tellabs 8600
network elements, as illustrated in the figure below.

82
76.8600-50133B
2011 Tellabs.
Fig. 24 ELP for Ethernet Access Network Interface Protection
The user access side Ethernet interfaces of the Tellabs 8600 network elements typically contain
VLAN subinterfaces since the VLAN technology is widely used in Ethernet access networks to
separate different customers traffic. This does not affect ELP protection behavior, but VLAN
subinterfaces are moved along with the logical base interface in case of a protection switchover.
As another example, Ethernet Link Protection may also be used to protect direct connections
between the Tellabs 8600 network elements, as shown in the figure below.
Fig. 25 ELP for Direct Connection Protection

76.8600-50133B
2011 Tellabs.

83
In addition to protecting connections between Tellabs 8600 network elements, Ethernet Link
Protection may be used in cases where a Tellabs 8600 network element is directly connected to a
3rd party network element that supports Ethernet link aggregation [IEEE 802.3ad]. From the 3rd
party network element point of view, the Tellabs 8600 network element looks like a device that also
supports link aggregation but that has only one physical link transmitting at a time.
Ethernet Link Protection does not support LACP, so LACP should be disabled in peer
equipment when an ELP group is connected to a link aggregation group.
5.1.1
References
[IEEE 802.3ad]
5.2
5.2.1
IEEE Std 802.3ad-2005 IEEE Standard for Local and metropolitan area
networks Specific requirements - Part 3: Carrier Sense Multiple Access
with Collision Detection (CSMA/CD) access method and physical layer
specifications Clause 43: Link Aggregation.
Operation
Ethernet Link Protection Group
An Ethernet Link Protection group consists of two Ethernet interfaces that protect each other. One
of the interfaces of an ELP group is always active (sends and receives data frames) and the other
passive (does not send data frames, receiving depends on the selected mode). The active interface is
selected based on the rules discussed in chapter 5.2.3 Switchover Behavior.
An ELP group must be configured according to the following rules:
The interfaces of an ELP group must reside on IFMs that are of the same HW type, e.g. both
IFMs are of type 8x1000BASE-X.
If IFMs are of different HW version, they must support the same feature set.
Currently this causes the following restriction:
8x100BASE-TX IFM versions 1.x and 2.x (or higher) cannot be used in the same ELP group.
The backup interface may not have VLAN subinterfaces or connections at the time of addition to
an ELP group.
Tellabs 8660 edge switch and Tellabs 8630 access switch:
The interfaces of an ELP group must reside on different IFCs.
The interfaces of an ELP group must have the same interface position on their IFCs, e.g. both
are upmost interfaces.
An IFC may have common ELP groups only with another IFC. In practise this means that IFCs
work in pairs protecting each other.

84
76.8600-50133B
2011 Tellabs.
Tellabs 8620 access switch:

The links of the ELP group can reside either in the same or in different IFMs. If the links of the
ELP group are in the same IFM, the primary interface must have a higher interface number than
the backup interface, for instance, ge1/7 for the primary and ge1/6 for the backup interface.
5.2.2
ELP Group Configuration

It is possible to configure the following parameters for an ELP group:
76.8600-50133B
2011 Tellabs.

85
Group ID (only within Tellabs 8000 intelligent network manager) and name. The group ID and
name identify the ELP group within the network element.
Passive interface mode (passive-if-mode) has the following syntax:
[no] passive-if-mode { down [ pulse ] | up{rx-disabled | no-signal-detect | rx-both } }
Passive Interface Mode Options
Option
Description
down
Physically down
up rx-disabled
Physically up with signal detect
up no-signal-detect
Physically up with no signal detect
rx-both
Physically up with receiving enabled on both sides
down pulse
Short link down pulse sent.
The passive mode is selected based on the type of the peer equipment or network (i.e. whether
the links of the ELP group are connected to another ELP group, to an [IEEE 802.3ad]
link aggregation group, to two Ethernet switches or another type of protection/switching
mechanism) and the role of this switch in the protected connection (master, slave or independent
switchover decisions).
When the passive side is set physically up and receiving is enabled on both sides (rx-both), the
equipment transmits by using the active link but receives on both (the passive side refers here
only to the transmission behavior). In this mode, both ends of a protected connection are free to
select the active side independently from each other. This mode is recommended whenever
possible (for example, when connected to an [IEEE 802.3ad] link aggregation group) as it
enables the fastest possible protection switchover. Furthermore, if both ends are ELP capable
devices, they can have similar configurations which simplifies the setup. This mode cannot be
used in those cases when the peer equipment requires that the same side is used for transmission
and receiving and both ends of the protected connection need to agree on the active side, or the
amount of received traffic needs to be limited to the capacity of a single link.
The rx-both mode should not be used when the peer equipment unnecessarily duplicates traffic
to both ports, such as when ELP is connected to an Ethernet switched network without having a
technology that prevents duplication, e.g. [IEEE 802.3ad] link aggregation (Ethernet switching
duplicates multicast, broadcast and flooded unicast messages to every port).
In other modes, one end of the protected connection acts as a master (it selects the active side
when both links are working) and the other end is the slave (it follows the selection made
by the master). The master end is configured to either set the passive side to be physically
down or to send a short link down pulse (available starting from FP2.7) after a switchover and
initialization. The former ensures that both ends up using the same side as the passive side looks
faulty to the peer device and thus it is never selected by the peer if the other one is OK, but
switching is slower because the link must be first physically activated when it is transformed
from passive to active. The latter is faster but may be used only by devices that are known to be
able to follow link down pulses (FP2.7 or higher).
The slave end is configured to keep the passive side physically up. The two modes that set
the passive interface physically up differ in fault reporting behavior. The signal detect on
mode (up rx-disabled) enables reporting of faults that are caused by missing the physical layer
connectivity on the passive side, whereas the signal detect off mode (up no-signal-detect)
disables reporting.
See chapter 5.2.5 Operational Examples further information.
86
76.8600-50133B
2011 Tellabs.
L2 learning frame transmission (enabled or disabled). When enabled, a learning frame is sent
on every logical IP interface (base or VLAN) after a switchover by using the common MAC
address of the interfaces of the ELP group (see chapter 5.2.4 MAC Address for more information)
as the source address. This enables Ethernet switches to update switching tables quickly. The
option should be enabled on ELP groups that are attached to an Ethernet switched network and
disabled on groups that are directly attached to a layer 3 network element, e.g. another Tellabs
8600 IP/MPLS network element. Note that learning frames are not sent for tunneling type of
interfaces.
Working interface. This ELP group member interface is selected by default as the active interface.
The working interface must be the right-hand side interface of the two interfaces of an ELP group
(in case of Tellabs 8660 edge switch the interface residing on the right-hand side IFC, in case of
Tellabs 8620 access switch the right-hand side interface on the IFMs, and in case of Tellabs 8630
access switch the lower interface as IFCs are in horizontal direction). Note that in CLI a working
interface is referred to as primary interface.
Protecting interface. This ELP group member interface is selected by default as the passive interface. Note that in CLI a protecting interface is referred to as a backup interface.
Manual to primary/backup trigger. This function is used to manually trigger switchover. The
target interface is selected active only if the physical link is operationally up.
Force to primary/backup trigger. This function is used to force switchover regardless of the possibly existing fault conditions.
Releasing copied MAC address trigger. See chapter 5.2.4 MAC Address.
Manual switchover is automatically released if the target interface goes down.
5.2.3
Switchover Behavior
Initially (e.g. after network element initialization), if both interfaces are operationally up, the
primary interface is selected active. If only one interface is operationally up, it is selected active
regardless of the primary/backup role.
During normal operation a switchover is triggered by a link down event of the currently active
interface (assuming that the target, i.e. currently passive interface can be operationally set up) or by a
management command, see chapter 5.2.2 ELP Group Configuration. A switchover is non-revertive,
i.e. traffic is not switched back to the previously active interface when it becomes operational again,
unless the currently active interface is detected to be down or the switchover is manually triggered.
A switchover is always performed in less than 200 ms. Note that the transmission of learning frames
may take longer, especially if the interface contains a larger number of VLAN subinterfaces.
5.2.4
MAC Address
By default the MAC address of the primary interface is used as the MAC address of an ELP group.
The MAC address of an ELP group should not, however, be changed in every primary interface
change case, because changing MAC typically causes a break in traffic (peer routers need to update
ARP caches accordingly). For example, it is not desirable to change the MAC address when the
IFM of the primary interface fails, the IFM is sent to repair and a temporary IFM is inserted.
76.8600-50133B
2011 Tellabs.

87
To overcome this problem the MAC address of an ELP group is maintained until the MAC address
of the currently installed primary interface is taken into use with CLI command eth reset
mac-addressor the primary as well as the backup interface are reset simultaneously (in that
case traffic breaks anyway). The former may take place e.g. during a maintenance period. The latter
typically occurs when the whole network element is reset.
Note that an IFM that permanently holds a MAC address that has been copied for an ELP group
must not be used within the same Ethernet broadcast domain with the ELP interfaces since it would
introduce duplicate MAC addresses to the network. To facilitate risk situation detection, the
Duplicate mac address risk fault is set active when an ELP group is using a MAC address that is
not the MAC address of the currently installed primary interface.
5.2.5
Operational Examples
The allowed ELP mode combinations when there is a Tellabs 8600 network element at both ends
are listed in the table below.
Allowed ELP Mode Combinations when Tellabs 8600 Network Element at Both Ends
Recommended
Node 1
Node 2
Description
passive-if-mode up
rx-both
passive-if-mode up
rx-both
Point-to-Point Connection.
The allowed ELP mode combinations when a Tellabs 8600 network element is connected a third
party switch are listed in the table below.
Allowed ELP Mode Combinations when Tellabs 8600 Network Element Connected to Third
Party Switch
Tellabs 8600 Network Element
Third Party Switch
Recommended
passive-if-mode up rx-both
Ethernet Switched Network Connection.

Link aggregation group has been
configured in the equipment.
May Be Used
passive-if-mode down pulse + L2

learning
Ethernet Switched Network Connection.

The equipment reacts to link down and
L2 learning ARP messages.
Point-to-Point Connection
In the example below two Tellabs 8660 edge switches are connected by two parallel GE links as
shown in the figure below.

88
76.8600-50133B
2011 Tellabs.
Fig. 26 Point-to-Point ELP Example
Network element 1 is configured with the following settings:

Primary interface: ge8/1/2
Backup interface: ge6/1/2
Passive interface mode: physically up with receiving enabled (rx-both)
L2 learning frame transmission: disabled (not needed because directly connected)
Primary interface: ge3/0/0
Passive interface transmitter mode: physically up with receiving enabled (rx-both)
L2 learning frame transmission: disabled (not needed because directly connected)
Since both network elements are configured to receive on both links they are free to choose the
active, that is, the transmitting link, independently from each other. Let us assume that NE 1 has
selected the upper link and NE 2 has selected the lower link, as illustrated in Fig. 27.
Fig. 27 Point-to-Point Initial Situation

76.8600-50133B
2011 Tellabs.

89
In the case that the lower link is broken, NE 1 takes no action as it is already transmitting on the
upper link. NE 2 performs a switchover and activates the upper link, because the lower link was the
active one. The situation is as shown in Fig. 28.
Fig. 28 Point-to-Point After Switchover
Assuming the lower link becomes again operational, no action, however, is taken since switchover
behavior is non-revertive.
Ethernet Switched Network Connection
In this example a Tellabs 8660 edge switch is connected to an Ethernet switched transport network
as illustrated in the figure below. The Ethernet switched network may be based, for example on
[IEEE 802.1Q] or IETF VPLS technology.
Fig. 29 Ethernet Switched Network Connection Example

90
76.8600-50133B
2011 Tellabs.

primary interface: ge6/0/0
Passive interface transmitter mode: down-pulse.
L2 learning frame transmission: enabled (needed because attached to an Ethernet switched network)
In the initial situation traffic flows via the ge6/0/0 interface as shown in the figure below.
Fig. 30 Ethernet Switched Network Connection Initial Situation
In case the lower link fails, NE 3 detects the failure, activates the ge5/0/0 interface (enables frame
transmit and receive, enables transmitter and takes the MAC and IP addresses into use). In certain
Ethernet switching technologies (e.g. VPLS) setting interface physically down causes the network
to flush forwarding tables. It also sends a learning frame (with the MAC address of the ELP group
as the source address and the broadcast address as the destination address) on every VLAN. The
learning frames cause the Ethernet switched network to update forwarding tables. The situation is
afterwards as shown in the figure below.
76.8600-50133B
2011 Tellabs.

91
Fig. 31 Ethernet Switched Network Connection After Switchover
Replacing Interface Module

This example discusses how to replace an IFM without a traffic break.
In this example an IFM containing the primary interface of an ELP group fails. First a switchover
takes place, i.e. traffic is directed to the backup (formerly passive) interface. Thus, only a very short
traffic break is experienced. The MAC address of the primary (now broken) interface is still used, as
discussed in chapter 5.2.4 MAC Address. The failed interface may now be removed, sent to repair
and a temporary IFM installed for the meantime.
If the backup interface (currently active) also fails, traffic is switched back to the primary interface.
The MAC address of the original primary interface remains in use even though it is not physically
present.
When the original working IFM returns from repair, the temporary IFM is removed and the original
one installed back. Now the situation is as before the failure. On the other hand, if the original IFM
cannot be repaired or it is not installed back from some other reason, the system may run with the
temporary IFM. Note that in this case the original primary interface must not be installed into the
same Ethernet broadcast domain as the ELP group, because the ELP group still uses its MAC
address. The problem can be avoided by triggering the MAC address of the currently installed
working IFM, e.g. during a maintenance period.
Note that the MAC address problem occurs only when the working IFM is replaced as the MAC
address of an ELP group is by default taken from the primary interface.

92
76.8600-50133B
2011 Tellabs.
5.3
5.3.1
Ethernet Link Protection CLI Configuration Examples

Point-to-Point Connection
This example depicts how ELP is configured to protect a direct connection between two Tellabs
8600 network elements. The network configuration is illustrated in chapter 5.2.5 Operational
Examples section Point-to-Point Connection.
First, network element 1 is configured. The network element 1 connects with interfaces ge8/1/2
and ge6/1/2 to network element 2.
Command
Description
router(config)# protection elp

elp_example_ptop
Create an ELP group elp_example_ptop.
router(cfg-elp-prot[elp_example_ptop])# Add ge8/1/2 as the primary interface and ge6/1/2

primary ge8/1/2 backup ge6/1/2
as the backup interface in the ELP group.
router(cfg-elp-prot[elp_example_ptop])# Configure both network elements to receive also
on the passive side to enable the fastest possible
switchover.
Next the network element 2 is configured. The network element 2 connects with interfaces ge3/0/0
and ge2/0/0 to the network element 1.
Command
Description

elp_example_ptop
Create an ELP group in the same way as for

network element 1.
router(cfg-elp-prot[elp_example_ptop])# Add interface ge3/0/0 as the primary and

primary ge3/0/0 backup ge2/0/0
interface ge2/0/0 as the backup interface in the
elp_example_ptop ELP group.
router(cfg-elp-prot[elp_example_ptop])# Configure both network elements to receive also
on the passive side to enable the fastest possible
switchover.
The following example depicts how a Tellabs 8600 network element is configured when it connects
point-to-point to a third party network element supporting Ethernet link aggregation over two
interfaces.
76.8600-50133B
2011 Tellabs.

93
Command
Description

elp_example_ptop_3partySwitch_without_linkAggregation
Create an ELP group.
router(cfg-elp-prot[elp_example_ptop_3partySwitch_without_linkAggregation])# primary ge3/0/0 backup

ge2/0/0
Add interface ge3/0/0 as the primary and interface

ge2/0/0 as the backup interface in the ELP group.
router(cfg-elp-prot[elp_examConfigure down pulse mode for both network

ple_ptop_3partySwitch_without_linkAgelements.
gregation])# passive-if-mode down pulse
router(cfg-elp-prot[elp_example_ptop_3partySwitch_without_linkAggregation])# l2-learning-tx-frames
5.3.2
Enable learning frames transmission as the Tellabs

8600 network element is connected to an Ethernet
switched network.
The configuration is now ready.
Ethernet Switched Network Connection

This example depicts how ELP is configured to protect a connection between a Tellabs 8600
network element and an Ethernet switched network. The network configuration is explained in
chapter 5.2.5 Operational Examples section Ethernet Switched Network Connection.
Command
Description

elp_example_eth_switched
First create an ELP group.
router(cfg-elp-prot[elp_example_eth_switched])# primary ge6/0/0

backup ge5/0/0
Add ge6/0/0 as the primary interface and ge5/0/0

as the backup interface in the ELP group.
router(cfg-elp-prot[elp_example_eth_switched])# passive-if-mode
down pulse
Network element acts as the master, although it

is up because l2-learning-tx-frames is enabled.
Thus, the passive interface is configured to the
down pulse state.
router(cfg-elp-prot[elp_example_eth_switched])# l2-learning-tx-frames
Enable learning frames transmission as the Tellabs

8600 network element is connected to an Ethernet
switched network.
The configuration is now ready.
Let us assume, for the sake of illustration (e.g. for traffic engineering reasons), that the ge5/0/0
interface should be active instead of interface ge6/0/0 that is selected active by default. The active
interface can be changed by triggering manual switchover.

94
76.8600-50133B
2011 Tellabs.
76.8600-50133B
2011 Tellabs.
Command
Description
router(cfg-elp-prot[elp_example_eth_switched])# protection
manual-switchover elp elp_example_eth_switched ge5/0/0
Select interface ge5/0/0 as the active interface.

Note: This CLI command should be given only
to the master network element, i.e. the network
element that sets the passive interface mode down.
That is true in this case (even though not explicitly
configured) because setting the passive interface
mode down is the default behavior.

95
6 Microwave Radio 1+1 Protection

6.1
Microwave Radio 1+1 Protection Overview

Tellabs 8660 edge switch and Tellabs 8630 access switch can interoperate with the Nokia Siemens
Flexi Packet Microwave system to provide equipment protection for microwave radio equipment.
At both ends of the radio link hop router/switch device acting as an In Door Unit (IDU) is connected
directly via GE interfaces to two microwave radio devices acting as working and protecting Out
Door Units (ODUs). The working and protecting ODUs are typically connected to the same physical
antenna and they are configured to use the same radio channel parametrization. The radio path itself
is not protected in this application. Depending on the protection status one ODU is active and the
other one is passive at the both ends. Two IDU topologies are supported:
Both IDUs are Tellabs 8630 access switch or Tellabs 8660 edge switch devices.
First IDU is Tellabs 8660 edge switch or Tellabs 8660 edge switch and the second IDU is NSN
Flexi Packet Hub Ethernet switch or equivalent.
Both topologies operate in a similar fashion from the protection point of view. However, the
configuration of the ODU management connections is different.
Microwave radio 1+1 protected systems have the following properties:
All the services like IPv4 routing and MPLS supported over ELP prior to FP3.1 are supported also
with 1+1 microwave radio protection. Ethernet switching and IRB are not supported. Protected
user plane traffic is typically placed to VLAN to enable traffic management capabilities in ODU.
The feature is supported only with 8x10/100/1000BASE-TX R2 IFM on IFC2.
Bandwidth over the radio path is typically 50..350 Mbits while ODU is connected via GE link to
IDU. Therefore bandwidth rate limiter may need in IDU GE egress interface if the traffic is very
bursty not to exceed ODUs packet buffering.

96
76.8600-50133B
2011 Tellabs.
The protection utilizes the existing Ethernet Link Protection (ELP) feature with some extensions.
Ethernet interfaces connected to working and protecting ODUs form an ELP group.
In the egress direction the ELP group replicates the traffic sent to the ELP group to both Ethernet interfaces. In the ingress direction the ELP group merges all the frames from both Ethernet
interfaces. ODU is responsible to drop traffic on the passive side.
As an extension to ELP, it is possible to configure unprotected VLANs to both working and protecting Ethernet interfaces in the ELP group. Unprotected VLANs can be used in the same way
as a regular VLAN in a regular unprotected Ethernet interface. The application requires three
unprotected VLANs per Ethernet interface:
Management VLAN ODUs have IP host for network management purposes. An unprotected VLAN shall be configured to each near-end IDU to reach the ODU IP host. In this
application ODU is always managed via Ethernet interface, not via radio interface even it is
technically possible. VLAN and subnet planning shall ensure this topology.
ODU-IDU monitoring Primary and backup ODU-IDU physical Ethernet links are monitored using ETH OAM CCM monitoring for fast failure detection. Independent Maintenance Associations (E-CCM) are used for both links and dedicated unprotected monitoring
VLAN is associated to Maintenance Associations. The usage of CCM organization specific
TLV (nsn-mwr-tlv) shall be enabled before the CCM session can be up.
ODU-ODU monitoring Primary and backup IDUs monitor mutually their faults and protection states. An Independent Maintenance Association (P-CCM) is used between the
ODUs and dedicated unprotected monitoring VLAN is associated to Maintenance Association. The unprotected VLAN interface is created to both the primary and backup Ethernet
interface in IDU and they are bridged together providing a transparent VLAN-based communication channel for ODU-ODU Maintenance Association.
Fig. 32 Microwave Radio 1+1 Protection Tellabs 8600 Network Element on Both Ends
76.8600-50133B
2011 Tellabs.

97
Fig. 33 Microwave Radio 1+1 Protection Tellabs 8600 and NSN on Each End
6.2
Configuring Microwave 1+1 Protection in an ELP Group

This section provides CLI configuration examples of Microwave Radio 1+1 Protection. The
examples focus only on the configuration of Tellabs 8600 equipment.
Fig. 34 Microwave Radio 1+1 Protection Example
The following lists some general guidelines and restrictions concerning ELP and MWR1+1
configuration which need to be take into consideration:
98
76.8600-50133B
2011 Tellabs.
Microwave Radio Protection can not be configured on the last physical interface the IFM (interface #7).
Manual switch-over operation is not allowed for Microwave Radio Protection. ELP active/passive status information is not relevant because both working and protecting sides are always
active.
The backup interface may not have VLAN sub-interfaces or connections at the time of addition
to an ELP group.
The interfaces of an ELP group must reside on different IFCs.
The interfaces of an ELP group must have the same interface position on their IFCs, e.g. both
are upmost interfaces.
An IFC may have common ELP groups only with one IFC. In practise this means that IFCs work
in pairs protecting each other.
Microwave Radio Protection can not be configured on an IFM, if ELP is already enabled on the
last physical interface of the same IFM.
ELP cannot be configured on the last physical interface (interfce #7) of the IFM if MWRP is
already configured on the same IFM.
Microwave Radio Protection and ELP cannot be configured on the same physical interfaces.
If an interface already belongs to a LAG group, then ELP and Microwave Radio Protection cannot
be configured on that interface.
The maximum number of unprotected VLANs that can be created in a group is 6 even the application requires only 3.
[IEEE 802.1ag] Ethernet OAM monitoring parametrization in MWR1+1 application is driven

by the used ODU device. The following examples recommend typical values but the final
values may vary depending on the ODU product variant and release and need to be verified
with ODU vendor.
6.2.1
Create ELP Protection Group

This example shows how an ELP protection group is created for MWR1+1 protection.
76.8600-50133B
2011 Tellabs.
Command
Description
router-IDU1(config)# protection elp

elp_example
Create first an ELP group.
router-IDU1(cfg-elp-prot[elp_example])#
primary ge8/1/6 backup ge6/1/6 plus
rx-tx-both
router-IDU1(cfg-elp-prot[elp_example])#
unprotected-vlans 10 16 100
Add interface ge8/1/6 as the primary and interface

ge6/1/6 as the backup interface to the ELP group.
The ELP group is configured to transmit and
receive mode.
VLANID values used for three unprotected VLANs
are allocated for primary and backup side using a
single CLI command.

99
6.2.2
Create ODU Management VLAN

This example shows how ODU management VLAN is configured. Both near-end ODUs are
managed via unprotected VLAN in primary and backup interfaces. ODUs shall be configured to
different sub-nets. Note that different sub-netting scheme is used in Tellabs 8600Tellabs 8600 and
Tellabs 86003rd party topologies.
6.2.3
Command
Description
router-IDU1> enable
router-IDU1# config terminal
router-IDU1(config)# interface ge 8/1/6
router-IDU1(cfg-if[ge8/1/6]# interface
ge 8/1/6.100
router-IDU1(cfg-if[ge8/1/6.100]#
Create ODU management VLAN to the

primary interface of the ELP group by issuing a
sub-interface configuration mode command. The
VLANID used in this CLI command shall be
configured as unprotected in the previous step.
The command in this example creates a VLAN
with the VLAN identifier value of 100 (assuming a
VLAN with this VLAN tag value does not already
exist on the main interface) and puts the command
prompt into the VLAN sub-interface configuration
mode. If a VLAN with a given VLAN identifier
already exists, the sub-interface configuration
mode is entered. The VLAN sub-interface can be
configured now.
router-IDU1(cfg-if[ge8/1/6.100]# ip
address 192.168.1.1/24
router-IDU1(cfg-if[ge8/1/6.100]# no
shutdown
Configure IP address for management VLAN for

the primary interface of the ELP group. Primary
ODU is configured to this sub-net as well.
Activate the interface with no shutdown command.

ge 6/1/6.100
Create ODU management VLAN to backup

interface of the ELP group. VLANID used in this
command shall be configured as unprotected in the
previous step.
address 192.168.2.1/24
shutdown
Configure management VLAN IP address for the

backup interface of the ELP group. Secondary
ODU is configured to this sub-net as well.
Activate the interface with no shutdown CLI
command.
Create IDU-ODU Monitoring VLAN

This example shows how [IEEE 802.1ag] Ethernet OAM CCM monitoring is configured.
Configuration shall be fully in-line with ODU configuration to get CCM connection up.

100
76.8600-50133B
2011 Tellabs.
76.8600-50133B
2011 Tellabs.
Command
Description
router-IDU1(config)# eth cfm md

domain_1 level 0 md-name none
Configure maintenance domain parameters for the

ELP group. This configuration is common for both
primary and secondary E-CCM connection.
Define at node IDU1 maintenance domain (MD)
with name (domain_1) and maintenance domain
level (MD level) ID (0). md-name is the
Maintenance Domain keyword used to construct
the MA ID that is signaled over the network. For
interoperability reasons it is recommended to use
MD level=0 and MD name=none.

domain_1 ma ma_1 short-name integer
1105 ccm interval 10ms
Configure maintenance associations for monitoring

VLAN (E-CCM) in the primary interface. Define
the maintenance association name, short name
and CCM interval. In Microwave 1+1 Protection
application 10ms is the only available option. For
interoperability reasons it is recommended to use 4
digit integer as short-name, different than backup
one.
router-IDU1(cfg-if[ge8/1/6])# interface
ge 8/1/6.10
router-IDU1(cfg-if[ge8/1/6.10]# eth cfm
ma ma_1 mep local mep_1 1 down ccm send
nsn-prot-state-tlv
ma ma_1 mep remote 2 nsn-prot-state-tlv
shutdown
Create monitoring VLAN to the primary interface

of the ELP group by issuing a sub-interface
configuration mode command. the VLANID
used in this CLI command shall be configured
as unprotected under the ELP group. For
interoperability reasons it is recommended to use
VLANID range [1..15].
Configure maintenance association endpoint for
primary monitoring VLAN. Bind a local down
MEP to VLAN 10 on ge 8/1/6 interface and enable
nsn-prot-state-tlv. For interoperability reasons it is
recommended to configure local MEP=1.
Bind a remote MEP to VLAN 10 on ge 8/1/6
interface and enable nsn-prot-state-tlv. For
interoperability reasons it is recommended to
configure remote MEP id=2
command.

101
6.2.4

domain_1 ma ma_2 short-name integer
1106 ccm interval 10ms
Configure maintenance associations for monitoring

VLAN (E-CCM) in backup interface. Defines
the maintenance association name, short name
and CCM interval. In Microwave 1+1 Protection
application 10ms is the only available option. For
interoperability reasons it is recommended to use 4
digit integer as short-name, different than primary
one.
router-IDU1(cfg-if[ge6/1/6])# interface
ge 6/1/6.10
ma ma_2 mep local mep_1 1 down ccm send
nsn-prot-state-tlv
ma ma_2 mep remote 2 nsn-prot-state-tlv
shutdown
Create monitoring VLAN to backup interface of the

ELP group by issuing a sub-interface configuration
mode command. VLANID used in this command
shall be configured as unprotected under ELP
group. It is recommended to use VLAID range
[1..15].
Configure maintenance association end point for
backup monitoring VLAN. Bind a local down
MEP to VLAN 10 on ge 6/1/6 interface and enable
nsn-prot-state-tlv. For interoperability reasons it is
recommended to configure local MEP=1.
Bind a remote MEP to VLAN 10 on ge 6/1/6
interface and enable nsn-prot-state-tlv. For
interoperability reasons it is recommended to
configure remote MEP id=2
Activate the interface with no shutdown command.
Create ODU-ODU Monitoring VLAN

This example shows how the ODU-ODU monitoring VLAN connection needed between a primary
and secondary ODU is configured. Note that no Ethernet OAM configuration is done for this
VLAN on IDU side.
Command
Description
router-IDU1(config)# pwe3 circuit

mwrp_bridge 1000 mpls manual
Create the pseudowire circuit instance mwrp_bridge

with id 1000.
ge8/1/6.16
router-IDU1(cfg-if[ge8/1/6.16]# pwe3
circuit mwrp_bridge
shutdown
Configure VLAN with VLAN identifier value 16 as

the ODU-ODU monitoring VLAN to the Ethernet
interface in the primary interface of the ELP group.
The VLANID used in this CLI command shall be
configured as unprotected under the ELP group.
For interoperability reasons it is recommended to
use VLANID range [16..50].
command.

102
76.8600-50133B
2011 Tellabs.
6.2.5
ge6/1/6.16
router-IDU1(cfg-if[ge6/1/6.16]# pwe3
circuit mwrp_bridge
shutdown
Configure VLAN with VLAN identifier value 16 as

the ODU-ODU monitoring VLAN to the Ethernet
interface in the backup interface of the ELP group.
The VLANID used in this CLI command shall be
configured as unprotected under the ELP group.
For interoperability reasons it is recommended to
use VLANID range [16..50].
command.
router-IDU1(config)# mpls static-ftn

bridge mwrp_bridge ge8/1/6.16
ge6/1/6.16
router-IDU1(config)# mpls static-ftn
bridge mwrp_bridge ge6/1/6.16
ge8/1/6.16
Set the bridge between the created VLANs in the

primary and secondary interface in both directions
of the first PWE3 circuit created.
Egress Rate Limiter Configuration

If the traffic is very bursty, it may be needed to enable an egress rate limiter in the Tellabs 8600
egress interface to avoid packet drops in the ODU packet buffer. This example shows how the rate
limiter is configured to primary interface ge8/1/6 and backup interface ge 6/1/6.
6.2.6
Command
Description
router-IDU1(config)# eth bandwidth

rate-limit module 8/1 limits max max
max max max max 350 max
Set the limiter for all interfaces on the IFM using

the same CLI command.
router-IDU1(config)# eth bandwidth

rate-limit module 6/1 limits max max
max max max max 350 max
Set the limiter for all interfaces on the IFM using

the same CLI command.
Create Protected User VLANs to ELP Group

This example shows how two protected user VLANs are configured to an ELP group. These VLANs
are used as MPLS and IP trunks for user end-to-end traffic.
76.8600-50133B
2011 Tellabs.

103
Command
Description

ge 8/1/6.200
interface ge 8/1/6.300
Create two user VLANIDs 200 and 300 to the

primary interface of the ELP group. When VLAN
is configured to the primary interface, it will be
protected.
address 192.168.100.1/24
shutdown
Configure VLAN IP address for VALID=200.

command.
interface ge 8/1/6.200
address 192.168.101.1/24
shutdown
Configure VLAN IP address for VALID=200.

command.

104
76.8600-50133B
2011 Tellabs.

76.8600-50133B Ethernet Config

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

76.8600-50133B Ethernet Config

Încărcat de

Drepturi de autor:

Formate disponibile

Tellabs 8600 Managed Edge System

Ethernet Configuration Guide

Ethernet MAC switching support added in chapters 2.1 and 2.5.2.

Initial release of the document.

Tellabs 8607 access switch

Tellabs 8609 access switch

Tellabs 8611 access switch

2011 Tellabs. All rights reserved.

Tellabs 8600 Managed Edge System

Terms and Abbreviations

Address Resolution Protocol

Asynchronous Transfer Mode

Broadband Remote Access Server

Bridge Protocol Data Unit

Base Station Controller

Continuity Check Message

Customer Edge device

Connectivity Fault Management

Command Line Interface

Carrier Sense Multiple Access with Collision Detection

Customer VLAN tag (the inner VLAN tag)

Delay Measurement Message

Delay Measurement Reply

Digital Subscriber Line Access Multiplexer

Ethernet OAM CCM for IDU-ODU

Ethernet Link Protection

Ethernet OAM Frame Delay Measurement

A two-octet field in an Ethernet frame. It is used to indicate which protocol is

Ethernet OAM Frame Loss Measurement

Frame Delay Variation

Forwarding Information Base

Frame Loss Ratio

High Speed Module (used in Tellabs 8611 access switch)

Institute of Electrical and Electronics Engineers

Internet Engineering Task Force

Inter-Frame Delay Variation

Internet Group Management Protocol

Incoming Label Map (for MPLS)

Integrated Routing and Bridging

Link Aggregation Control Protocol

Local Area Network

Link Access Procedure/Protocol for Frame Mode Services

Label Distribution Protocol (MPLS)

Local Maintenance Endpoint

Long Term Evolution

Media Access Control

Maintenance Association Identifier

Tellabs 8600 Managed Edge System

Metro Area Network

Maintenance Domain Level

Maintenance Intermediate Point

Multiprotocol Label Switching

Multiplex Section Trail Protection 1+1

Multiple Spanning Tree Protocol

Maximum Transfer/Transmission Unit

Multiple hop Involves multiple packet forwarding decisions

Operation, Administration and Maintenance

Out Door Unit

Ethernet OAM CCM for ODU-ODU

Protocol Data Unit

Provider Edge Network Element

Protocol Independent Multicast

User Priority field bits