Beruflich Dokumente
Kultur Dokumente
Document Information
Revision History
Document No.
Date
Description of Changes
76.8600-50133B
24.08.2011
76.8600-50133A
20.12.2010
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
76.8600-50133B
2011 Tellabs.
Document Information
Explanation
AC
Attachment Circuit
ARP
ATM
BE
Best Effort
BRAS
BPDU
BSC
CCM
CDC
Control and DC Power Card (used in Tellabs 8630 access switch and Tellabs 8660
edge switch)
CE
CFM
CLI
CSMA/CD
C-tag
C-VLAN
Customer VLAN
DA
Destination Address
DMM
DMR
DSLAM
E-CCM
ELP
eNB
Evolved NodeB
ETH-DM
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
ETH-LM
FD
Frame Delay
FDV
FIB
FLR
FMC
Fixed-mobile convergence
Tellabs 8600 Managed Edge System
Ethernet Configuration Guide
3
Document Information
FTN
Forwarding equivalence class To Next hop label forwarding entry map (for MPLS)
GE
Gigabit Ethernet
HM
IDU
Indoor Unit
IEEE
IETF
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
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
ILM
IP
Internet Protocol
IRB
L2
OSI Layer 2
L3
OSI Layer 3
LACP
LAG
Link Aggregation
LAN
LAPF
LBM
Loopback Message
LBR
Loopback Reply
LDP
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
LOC
Loss of Continuity
LTE
LTM
Linktrace Message
LTR
Linktrace Reply
MA
Maintenance Association
MAC
MAID
76.8600-50133B
2011 Tellabs.
Document Information
MAN
MD
Maintenance Domain
MDL
ME
Maintenance Entity
MEP
Maintenance Endpoint
MIP
MP
Maintenance Point
MPLS
MSP1+1
MSTP
MTU
76.8600-50133B
2011 Tellabs.
NE
Network Element
Node
In Tellabs 8000 intelligent network manager and CLI refers to network element.
OAM
ODU
P-CCM
PDU
PE
PIM
PM
Performance Monitoring
PRI 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
PWE3
Q-in-Q
Stacked VLAN
QoS
Quality of Service.
RAN
RDI
RMEP
RNC
RSTP
SA
Source Address
SAToP
SCM
Document Information
Single hop
SNAP
SSM
S-tag
STP
S-VLAN
Service VLAN
TDM
TLV
T-PE
TTL
Time-to-Live
VCCV
VLAN
Virtual LAN
VPLS
VPWS
VRF
VRRP
VSI
WAN
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.
76.8600-50133B
2011 Tellabs.
Table of Contents
Table of Contents
Ethernet Overview....................................................................................................... 13
1.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
76.8600-50133B
2011 Tellabs.
Table of Contents
3.2
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
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
76.8600-50133B
2011 Tellabs.
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.
Tellabs 8600 Managed Edge System
CLI Commands Manual (76.8600-50117)
76.8600-50133B
2011 Tellabs.
76.8600-50133B
2011 Tellabs.
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
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.
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
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)
100/1000BASE-X
(fixed interface)
1000BASE-T
(fixed interface)
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
76.8600-50133B
2011 Tellabs.
2 Ethernet Forwarding
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.
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:
76.8600-50133B
2011 Tellabs.
2 Ethernet Forwarding
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.
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.
2 Ethernet Forwarding
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.
76.8600-50133B
2011 Tellabs.
2 Ethernet Forwarding
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.
76.8600-50133B
2011 Tellabs.
2 Ethernet Forwarding
VLAN Operations
Attachment Mode
Frame VLAN
Tagging
Ingress Action
Egress Action
VLAN Access
untagged
NA
tag added1
single tag
none
two tags
none
untagged
NA
add tag
single tag
add tag
two tags
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
1Those
76.8600-50133B
2011 Tellabs.
2 Ethernet Forwarding
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.
2 Ethernet Forwarding
2.1.1
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.
76.8600-50133B
2011 Tellabs.
2 Ethernet Forwarding
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.
2 Ethernet Forwarding
2.2.2
2.2.3
2.2.4
76.8600-50133B
2011 Tellabs.
2 Ethernet Forwarding
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]
[RFC4447]
[RFC4448]
[RFC5085]
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.
2 Ethernet Forwarding
2.3.1
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]
76.8600-50133B
2011 Tellabs.
2 Ethernet Forwarding
2.4
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.
2 Ethernet Forwarding
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
76.8600-50133B
2011 Tellabs.
2 Ethernet Forwarding
2.5
2.5.1
76.8600-50133B
2011 Tellabs.
Command
Description
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])#
2 Ethernet Forwarding
Command
Description
8660:
upe2(config)# interface fe
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])#
Description
8660:
upe1(config)# interface fe
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])#
76.8600-50133B
2011 Tellabs.
2 Ethernet Forwarding
Command
Description
8660:
upe2(config)# interface fe
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])#
76.8600-50133B
2011 Tellabs.
Command
Description
8660:
upe4(config)# interface fe
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])#
2 Ethernet Forwarding
8660:
Attach the pseudowire to the interface.
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
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
76.8600-50133B
2011 Tellabs.
2 Ethernet Forwarding
PE1(cfg-if[fe0/3#svlan#10])# dot1q
svlan ethertype 0x88a8
PE1(cfg-if[fe0/3#svlan#10])# no
shutdown
PE2 configuration:
Command
Description
PE2(cfg-if[fe0/4.100])# no shutdown
76.8600-50133B
2011 Tellabs.
2 Ethernet Forwarding
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
PE3(cfg-if[ge1/1.1)# no shutdown
PE3(cfg-if[ge1/1.2)# no shutdown
76.8600-50133B
2011 Tellabs.
2 Ethernet Forwarding
2.5.2
76.8600-50133B
2011 Tellabs.
Command
Description
NE1(cfg-bridge-inst[VSI-1])#
description MyFirstBridge
NE1(cfg-bridge-inst[VSI-1])#
mac-learning limit 400 alarm 70
clear 60
2 Ethernet Forwarding
2.5.3
Description
NE(config)# bridging-instance
MyBridge44 44
NE(cfg-if[irb44])# no shutdown
76.8600-50133B
2011 Tellabs.
2 Ethernet Forwarding
76.8600-50133B
2011 Tellabs.
NE(cfg-if[irb44.8])# no shutdown
3 Ethernet OAM
3 Ethernet OAM
3.1
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.
Tellabs 8600 Managed Edge System
Ethernet Configuration Guide
38
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
Definition
[Y.1731]
Term
Maintenance
Association (MA)
MEG
Maintenance
Domain (MD)
MEG
Maintenance
Domain Level
(MDL)
MEG Level
Maintenance
Entity (ME)
ME
Maintenance
Endpoint (MEP)
MEP
Maintenance
Domain
Intermediate
Point (MIP)
MIP
Maintenance
Point (MP)
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.
3 Ethernet OAM
The following chapters describe the Ethernet OAM functions supported in the Tellabs 8600 system.
3.1.1
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
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
RMEPs
76.8600-50133B
2011 Tellabs.
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.
Tellabs 8600 Managed Edge System
Ethernet Configuration Guide
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.
3 Ethernet OAM
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.
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
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.
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 R2 IFMs2
IFC2
NE
2K
4K
4K
1K
1K
4K
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
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
16
64
16
64
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
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
3.1.5
3.2
References
[IEEE 802.1ag]
[Y.1731]
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
3.2.1
cfm
cfm
cfm
cfm
md
md
md
md
DOMAIN_0
DOMAIN_0
DOMAIN_0
DOMAIN_0
eth
eth
eth
eth
cfm
cfm
cfm
cfm
md
md
md
md
DOMAIN_1
DOMAIN_1
DOMAIN_1
DOMAIN_1
eth
eth
eth
eth
cfm
cfm
cfm
cfm
md
md
md
md
DOMAIN_2
DOMAIN_2
DOMAIN_2
DOMAIN_2
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.
3 Ethernet OAM
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
router-CE1(config)# interface ge
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
router-CE1(config)# interface ge
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
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
router-CE1(config)# interface ge
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
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
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
3.2.5
Displaying MD
It is possible to display MD information name (briefly), or detailed.
Command
Description
MD :
Level:
MD Name:
MD Name Type:
Maintenance Associations:
DOMAIN_1
1
PROVIDER
String
MA_1D MA_1I MA_1U
Command
Description
Display MD information.
MD
DOMAIN_0
DOMAIN_1
DOMAIN_2
Level
0
1
2
MD Name
OPERATOR
PROVIDER
CUSTOMER
Command
Description
Description
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.
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
Command
Description
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
Description
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
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
Description
Ping 00b0.c79e.5c7c:
46 data bytes
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
3.2.7
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
Command
Description
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
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.
2.
3.
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.
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.
3 Ethernet OAM
3.2.8
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:
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
Command
Description
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.
3 Ethernet OAM
Description
Description
router# show eth cfm mp name lmep714 lm Display Ethernet OAM frame loss performance
monitoring results.
Description
router# show eth cfm mp name lmep714 dm Display Ethernet OAM frame delay performance
monitoring results.
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
76.8600-50133B
2011 Tellabs.
Command
Description
3 Ethernet OAM
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
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:
Tellabs 8600 Managed Edge System
Ethernet Configuration Guide
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 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
router (cfg-if[ge 0/0.2000])#
shutdown
router (cfg-if[ge 0/0.2000])#
0/0.2000
pwe3
no
exit
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
NE5_8630:
Command
Description
Configure RMEP.
router(cfg-if[ge 7/1/0.2000])# qos vlan Define how Ethernet VLAN QoS is decided at
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.
76.8600-50133B
2011 Tellabs.
3 Ethernet OAM
Description
76.8600-50133B
2011 Tellabs.
router(cfg-if[ge 7/1/0.2000])#
label-switching
router(cfg-if[ge 7/1/0.2000])# ip
address 10.10.10.164/24
Configure RMEP.
3 Ethernet OAM
router(cfg-if[ge 7/1/0.2000])# qos vlan Define how Ethernet VLAN QoS is decided at
egress vlan-pri
VLAN granularity.
NE5_8630:
Command
Description
Configure RMEP.
router(cfg-if[ge 7/1/0.2000])# qos vlan Define how Ethernet VLAN QoS is decided at
egress vlan-pri
VLAN granularity.
3.2.9
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.
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:
8x100/1000BASE-X R2 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
76.8600-50133B
2011 Tellabs.
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.
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.
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:
Tellabs 8600 Managed Edge System
Ethernet Configuration Guide
70
76.8600-50133B
2011 Tellabs.
4.2.2
Protocol
Configuration
Application
Hash Calculation
MPLS over
Ethernet
IP over Ethernet
Anything over
Ethernet
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.
The protocols to be used in hash calculation for load balancing. The alternatives are:
1.
2.
Ethernet only: use Ethernet SA and DA, and optionally the Ethernet Type field
3.
4.
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
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.
4.6
Restrictions
Link Aggregation Control Protocol (LACP) is not supported.
LAG does not support VLANs.
4.7
4.7.1
Description
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
76.8600-50133B
2011 Tellabs.
4.7.2
Description
router(cfg-if[ge12/1/4])# no send-ssm
4.7.3
ge12/1/4
eth lag
interface
eth lag
interface
eth lag
76.8600-50133B
2011 Tellabs.
4.7.4
Command
Description
Description
The first joined member of a group cannot be removed from the group.
4.7.5
Description
76.8600-50133B
2011 Tellabs.
4.7.6
76.8600-50133B
2011 Tellabs.
Command
Description
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
4.7.8
76.8600-50133B
2011 Tellabs.
4.7.9
76.8600-50133B
2011 Tellabs.
Command
Description
router(cfg-if[lag5])# ip address
10.10.10.1/24
router(cfg-if[lag5])# no shutdown
4.7.10
Description
router# clear interface statistics lag0 The group-level statistics are cleared. The output
router# show interface lag0
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.
router# show interface ge8/0/0
76.8600-50133B
2011 Tellabs.
76.8600-50133B
2011 Tellabs.
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.
76.8600-50133B
2011 Tellabs.
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.
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.
76.8600-50133B
2011 Tellabs.
5.2.2
76.8600-50133B
2011 Tellabs.
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
up no-signal-detect
rx-both
down pulse
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.
Tellabs 8600 Managed Edge System
Ethernet Configuration Guide
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.
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
Recommended
passive-if-mode up rx-both
May Be Used
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.
76.8600-50133B
2011 Tellabs.
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.
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.
76.8600-50133B
2011 Tellabs.
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.
76.8600-50133B
2011 Tellabs.
5.3
5.3.1
Description
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
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.
Command
Description
5.3.2
Description
router(cfg-elp-prot[elp_example_eth_switched])# passive-if-mode
down pulse
router(cfg-elp-prot[elp_example_eth_switched])# l2-learning-tx-frames
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.
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
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.
Fig. 33 Microwave Radio 1+1 Protection Tellabs 8600 and NSN on Each End
6.2
The following lists some general guidelines and restrictions concerning ELP and MWR1+1
configuration which need to be take into consideration:
Tellabs 8600 Managed Edge System
Ethernet Configuration Guide
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.
6.2.1
76.8600-50133B
2011 Tellabs.
Command
Description
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
6.2.2
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]#
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
router-IDU1(cfg-if[ge6/1/6.100]# ip
address 192.168.2.1/24
router-IDU1(cfg-if[ge6/1/6.100]# no
shutdown
76.8600-50133B
2011 Tellabs.
76.8600-50133B
2011 Tellabs.
Command
Description
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
router-IDU1(cfg-if[ge8/1/6.10]# eth cfm
ma ma_1 mep remote 2 nsn-prot-state-tlv
router-IDU1(cfg-if[ge8/1/6.10]# no
shutdown
6.2.4
router-IDU1(cfg-if[ge6/1/6])# interface
ge 6/1/6.10
router-IDU1(cfg-if[ge6/1/6.10]# eth cfm
ma ma_2 mep local mep_1 1 down ccm send
nsn-prot-state-tlv
router-IDU1(cfg-if[ge6/1/6.10]# eth cfm
ma ma_2 mep remote 2 nsn-prot-state-tlv
router-IDU1(cfg-if[ge6/1/6.10]# no
shutdown
Description
router-IDU1(cfg-if[ge8/1/6]# interface
ge8/1/6.16
router-IDU1(cfg-if[ge8/1/6.16]# pwe3
circuit mwrp_bridge
router-IDU1(cfg-if[ge8/1/6.16]# no
shutdown
76.8600-50133B
2011 Tellabs.
6.2.5
router-IDU1(cfg-if[ge6/1/6]# interface
ge6/1/6.16
router-IDU1(cfg-if[ge6/1/6.16]# pwe3
circuit mwrp_bridge
router-IDU1(cfg-if[ge6/1/6.16]# no
shutdown
6.2.6
Command
Description
76.8600-50133B
2011 Tellabs.
Command
Description
router-IDU1(cfg-if[ge8/1/6.300]# ip
address 192.168.100.1/24
router-IDU1(cfg-if[ge8/1/6.300]# no
shutdown
router-IDU1(cfg-if[ge8/1/6.300]#
interface ge 8/1/6.200
router-IDU1(cfg-if[ge8/1/6.200]# ip
address 192.168.101.1/24
router-IDU1(cfg-if[ge8/1/6.200]# no
shutdown
76.8600-50133B
2011 Tellabs.