12 AToM

Layer 2 VPNs and Ethernet Services
2012 Cisco and/or its affiliates. All rights reserved. SPEDGE v1.04-1
Introduce AToM
Implement AToM
Introduction to AToM
Subset of VPWS:
- MPLS transport
- Point-to-point Layer 2 connections
Provisioning:
- Directed LDP requires unsummarized /32 PE loopback addresses
Forwarding:
- No MAC learning
- All ingress frames transported to the other end
Signaling:
- Setup, maintenance, and teardown of VCs and VC labels
- VCCV
- Directed LDP
MTU considerations:
- Fragmentation in core black-holes traffic
- Same MTU values on ingress and egress
1. Use the xconnect command on ingress PE (port, subinterface, etc.).
2. PE1 starts a directed LDP session to PE2 (if not yet available):
- One LDP session can signal multiple PWs.
3. PE1 allocates the VC label and binds to the VC ID:
- Same VC ID on both ends; VC label unique per PE
4. PE1 sends mapping message (VC FEC TLV, VC label TLV).
5. PE2 receives VC FEC and label TLV and maps to local VC ID.
6. PE2 repeats the process (1 to 4, and then 5 on PE1).
Native service Pseudo-wire Native service
1 2 4
5
3
CE 6
PE1 CE
PE2
FEC
Set of packets handled in the same way on MPLS LSR
Used to bind a VC label to a VC ID
Multiplexing customer data over the same LSP tunnel
DLCI 101 17
FEC: VC 17
17 21
17 22
MPLS
17
17 23
17 DLCI 202
Establishing, maintaining, and tearing down VCs:
- Directed LDP signaling
- Frame Relay must use LMI procedures.
- ATM should use ILMI procedures.
If PE detects an event that affects service, it must withdraw VC label.
Label withdrawal:
DLCI 101 VC label 17
MPLS
DLCI 202
Layer 2 VPN OAM feature
Keepalive protocol to monitor PW data forwarding
AToM VCCV categories:
- Switching modesfor differentiating between control and data traffic
In-band (type 1) uses PID field in the AToM control word to identify VCCV
control packet
Out-of-band (type 2) MPLS router alert label is carried above the VC label
to identify VCCV control packet
- Applicationsin-band keepalive method
MPLS LSP ping
ICMP ping
In-band VCCV:
Local L2 Tunnel Control word with VCCV
VC label
header label specific PID payload
Out-of-band VCCV:
Local L2 Tunnel MPLS Router Optional VCCV
VC label
header label Alert Label control word payload
AToM transport of Frame Relay, Ethernet, and AAL5 does not allow
packets to be fragmented and reassembled.
Ensure that the MTU of all intermediate links between endpoints is
sufficient to carry the largest Layer 2 frame received.
The ingress and egress PE routers must have the same MTU value.
Back-up FRR Label (VC) EXP S TTL 4 bytes
TE for FRR Label (VC) EXP S TTL 4 bytes
Core LDP Label (VC) EXP S TTL 4 bytes
VC directed LDP Label (VC) EXP S TTL 4 bytes
Optional control word 4 bytes
Dot1Q Header (only in Port Mode Xconnect) 4 bytes
Up to 1514
Ethernet PDU bytes
Control word is optional.
Transmitted after the label or labels and before the Layer 2 PDU
Can be used for in-band VCCV
Flag field carries different bits for different Layer 2 protocols:
- Frame Relay: FECN, BECN, DE, C/R
- ATM: AAL5 or cell, EFCI, CLP, C/R
Sequence number 0 indicates that no sequencing is done.
Label (LDP) EXP 0 TTL Tunnel label
Label (VC) EXP 1 TTL VCl label
Control word
0000 Flags Length Sequence Number
(Optional)
Layer 2 PDU
Layer 2 VPN extends VCs over single service provider AS.
Changes in control and data plane code are required for inter-AS span.
PW stitching solution:
- Interconnects PWs in different autonomous systems
- ASBRs are the stitch points
- Interworking of control and data planes at stitch point
(FR, Ethernet, Pseudo- (FR, Ethernet,

HDLC, PPP, ATM) Pseudowire wire Pseudowire HDLC, PPP, ATM)
AS 65001 AS 65002
CE PE ASBR ASBR PE CE
Ethernet frames are transported without preamble, SFD, and FCS.
In Ethernet port mode, all VLAN information is transmitted:
- May be overwritten by the egress PE
Control word is optional.
Ethernet II Encapsulation
<7 octets> <1 octet> <6 octets> <6 octets> <2 octets> <2 octets> <2 octets> <46-1500> <4 octets>
Preamble SFD DA SA TPID TCI EtherType Data FCS
Transported using AToM
OUI
Preamble SFD DA SA TPID TCI Length AA-AA-03 EtherType Data FCS
0x00-00-00
<7 octets> <1 octet> <6 octets> <6 octets> <2 octets> <2 octets> <2 octets> <3 octets> <3 octets> <2 octets> <46-1492> <4 octets>
802.3/802.2/SNAP Encapsulation
Failures 1 and 2 (transit network):
- IGP and MPLS LDP will reconverge.
- With MPLS traffic engineering and FRR enabled, failover to backup tunnel.
- PW will stay up as long as PE1 has available LSP path to PE2.
- PW service layer is not affected.
Failures 3 and 4 (service node or attachment circuit):
- EoMPLS PW will go down.
- Network transport layer reconverge does not help.
Solution: PW redundancy Primary PW
Attachment
PE2 Circuit
Core/Transit Router
PE1
1 2 4
3
CE2
CE1
Backup PW
Dual-homing of one local PE to:
- Two remote PEs
- Two different attachment circuits on the same remote PE
Two PWs: Primary and backup provide redundancy for a single
attachment circuit or node.
Faults on the primary PW cause failover to backup PW.
Case 1: Service node and Case 2:

attachment circuit Attachment circuit
protection protection
Dual-homing of two local PEs to two remote PEs
Four PWs:
- One primary PW
- Three backup PWs
Requires MC-LAG
- Point of attachment nodes run ICCP
- ICCP synchronizes state and forms a redundancy group.
Active PW
Active PoA Active PoA
ICCP
ICCP
CE
Standby AC Standby PoA Standby PoA

Standby PWs (3)
Service instances configured on main interface:
- Also known as EFP
Each EFP matches a predefined VLAN tag-based criteria.
Optional tag manipulation can be configured.
Traffic forwarding is specified.
Features such as QoS policies can be specified.
L3 SubI/F
Routing
EoMPLS PW
VPLS
EoMPLS PW
Bridging
IRB
X EoMPLS PW
IRB
X
Bridging
Multiple Layer 2 frame types Multiple Layer 2 services
Flexible PE
Layer 2 peer-to-peer native

Untagged Ethernet
Single-tagged Layer 2 peer-to-peer over PW
Customer Double-tagged Layer 2 MP native Ethernet
Network 802.1q bridging
802.1ad Layer 2 MP VPLS
Layer 3 routed
Access side: Trunk side:

- Customer Ethernet attachment - Local Layer 2 cross-connect
circuit - Local Layer 2 bridging
- Terminates on an EFP - EoMPLS or VPWS
- VPLS or H-VPLS
- Layer 3 routing
EFPs enable flexible
mapping of frames into Inner VLAN
Outer VLAN
Layer 2 services. tag tag
Mapping is based on VLAN
s-vlan 30
tagging:
802.1Q, 802.1ad c-vlan any
s-vlan 20
Single-tag or double-tag s-vlan 402- 410
Unique or multiple values untagged

(ranges or lists) s-vlan 300, 400
Untagged traffic
default
s-vlan 50
Unclassified traffic (default) c-vlan 50
EVC supports only nonexact matching.
encapsulation dot1q 10 matches any packets with outmost tag
equal to 10:
10
10 200
encapsulation dot1q 10 second 100 matches any packets with

outmost tag equal to 10 and second outmost tag equal to 100:
10 100
10 100 1000
Longest match defines frame-to-EFP matching.
10
dot1q 10
10 200
Int G3/0/0
dot1q 10
10 100
sec 100
dot1q 10
10 130 sec 128-133
Frame received EFP configuration
EVC provides several VLAN tag rewrite options.
Push:
- Adds one or two VLANs to traffic
- push {dot1q <vlan-id> | dot1q <vlan-id> second-dot1q <vlan-id>}
Pop:
- Removes one or two VLANs from frames
- pop {1|2}
Translate:
- 1-to-1 dot1q <vlan-id>
- 2-to-1 dot1q <vlan-id>
- 1-to-2 dot1q <vlan-id> second-dot1q <vlan-id>
- 2-to-2 dot1q <vlan-id> second-dot1q <vlan-id>
Symmetric keyword allows simplicity and avoids misconfiguration.
Three forwarding options through EFP:
Local connect
- Point-to-point connections between two EFPs on same router
Scalable EoMPLS
- Point-to-point Xconnect between two EFPs on different routers
Bridge domain
- Classical Layer 2 switching domain
- Can be integrated with VPLS or Layer 3 IP address (IRB)
- Split horizon can be configured on the bridge domain.
EFP and subinterfaces can coexist on the same physical interface.
VLAN tag local
significant
L3 SubI/F
Routing
EoMPLS PW
(-H) VPLS
Flexible VLAN EoMPLS PW
tag classification
Bridging
Flexible VLAN
tag rewrite X EoMPLS PW
Flexible IRB
EtherType (.1Q, X
QinQ, .1ad) Bridging Routing and Bridging
Layer 2 or Layer 3
subinterfaces Flexible service mapping and multiplexing. Support all standard-based
(802.1a/QinQ/.1ad) 2 services concurrently on the same port
Layer 2 peer-to-peer local connect and EoMPLS
Layer 2 multipoint local bridging , H-VPLS and VPLS
Regular Layer 3 subinterface, and integrated Layer 2 and Layer 3IRB
AToM Implementation
Prepare MPLS infrastructure:
- PE routers must have a /32 address on their loopbacks.
- PE loopback addresses cannot be summarized in the core.
- MPLS enabled in the core (unless L2TPv3 is used).
- Ensure MTU sizes in the core are large enough.
Enable Layer 2 frame transport on both endpoint PE routers.
Make sure MTU is the same on both endpoint interfaces.
Optionally configure parameters:
- Port or VLAN mode, control word, sequencing, and so on
Optionally configure AToM interworking.
IOS XR
CE1 IOS / IOS XE CE2
MPLS
Cisco IOS XR:

Cisco IOS and IOS XE:
ip cef
mpls ip
mpls label protocol ldp
interface Loopback0
mpls ldp router-id Loopback0 force
ipv4 address 10.1.1.1 255.255.255.255
!
!
interface Loopback0
interface Giga0/0/0/0.40 l2transport
ip address 10.2.2.2 255.255.255.255
encapsulation dot1q 40
!
!
pseudowire-class pw-class2
l2vpn
encapsulation mpls
xconnect group eompls-group
!
p2p eompls-p2p
interface Gi0/0/0.40
interface Gigabit0/0/0/0.40
encapsulation dot1Q 40
neighbor 10.2.2.2 pw-id 123
xconnect 10.1.1.1 123 pw-class pw-class2
Control word is optional in EoMPLS

CE1 PE1 PE2 CE2
MPLS
pseudowire-class pw-class1 pseudowire-class pw-class2

encapsulation mpls encapsulation mpls
control-word control-word
! !
interface Loopback0 interface Loopback0
ip address 10.1.1.1 255.255.255.255 ip address 10.2.2.2 255.255.255.255
! !
interface serial1/0 interface serial1/0
no ip address no ip address
encapsulation ppp/hdlc encapsulation ppp/hdlc
xconnect 10.2.2.2 123 pw-class pw-class1 xconnect 10.1.1.1 123 pw-class pw-class2
Control word is optional in PPP and HDLC over MPLS
The attachment circuits are terminated locally.
There are two types of interworking (any-to-any):
- Ethernet (bridged):
Ethernet frames are extracted from attachment circuit and sent over PW.
VLAN tag is removed.
CEs can run Ethernet, BVI, or RBE.
Use the interworking ip command.
- IP (routed):
IP packets are extracted from attachment circuit and sent over the PW.
Use the interworking ethernet command.
AToM L2TPv3 IP Mode Ethernet
Frame Relay to Ethernet/VLAN Yes Yes Yes Yes
Frame Relay to PPP Yes Yes Yes No
Frame Relay to ATM AAL5 Yes No Yes No
Ethernet/VLAN to ATM AAL5 Yes No Yes Yes
Ethernet to VLAN Yes Yes Yes Yes
CE1 PE1 PE2 CE2
LMI
MPLS
PE1:
frame-relay switching PE2:
!
pseudowire-class atom_fr_vlan pseudowire-class atom_vlan_fr
encapsulation mpls encapsulation mpls
interworking ip interworking ip
! !
interface serioal3/0 interface GigabitEthernet4/0.310
encapsulation frame-relay encapsulation dot1Q 310
clock source internal xconnect 10.1.2.1 210 pw-class atom_vlan_fr
frame-relay lmi-type ansi
frame-relay intf-type dce
!
connect fr-vlan serial3/0 210 l2transport
xconnect 10.1.2.2 210 pw-class atom_fr_vlan
CE1: CE2:
interface serial5/0.210 point-to-point interface GigabitEthernet6/0.310
ip address 172.16.1.1 255.255.255.0 encapsulation dot1Q 310
frame-relay interface-dlci 210 ip address 172.16.1.2 255.255.255.0
Cisco IOS XR:
RP/0/RSP0/CPU0:PE1# show l2vpn xconnect

Legend: ST = State, UP = Up, DN = Down, AD = Admin Down, UR = Unresolved,
LU = Local Up, RU = Remote Up, CO = Connected
XConnect Segment 1 Segment 2
Group Name ST Description ST Description ST
---------------------------- --------------------------- -------------------------
eompls-group eompls-p2p UP Gigabit0/0/0/0.30 UP 10.2.2.2 123 UP
--------------------------------------------------------------------------------
PE2#show xconnect all detail

Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP ac Gi0/0/0.40:40(Eth VLAN) UP mpls 10.1.1.1:123 UP
Interworking: none Local VC label 16003
Remote VC label 30005
pw-class: pw-class2
RP/0/RSP0/CPU0:router# show l2vpn xconnect detail
Group eompls-group, XC eompls-p2p, state is up; Interworking none
AC: Gigabit0/0/0/0.30, state is up
Type VLAN
MTU 1500; XC ID 0x5000001; interworking none; MSTi 0
Statistics:
packet totals: send 90
byte totals: send 19056
PW: neighbor 10.2.2.2, PW ID 123, state is up ( established )
PW class pw-class1, XC ID 0x5000001
Encapsulation MPLS, protocol LDP
PW type VLAN, control word enabled, interworking none
PW backup disable delay 0 sec
Sequencing not set
MPLS Local Remote
------------ ------------------------------ ------------------------
Label 30005 16003 Cisco IOS XR
Group ID 0x5000300 0x5000400
Interface Gigabit0/0/0/0.30 Gi0/0/0.40
MTU 1500 1500
Control word enabled enabled
PW type VLAN VLAN
VCCV CV type 0x2 0x2
(LSP ping verification) (LSP ping verification)
VCCV CC type 0x7 0x7
(control word) control word)
(router alert label) (router alert label)
------------ ------------------------------ -----------------------
<output truncated>
PE2# show mpls l2transport vc detail

Local interface: Gi0/0/0.40 up, line protocol up
Destination address: 10.1.1.1, VC ID: 123, VC status: up
Tunnel label: imp-null, next hop point2point
Output interface: PO0/1/0, imposed label stack {16}
Create time: 00:16:44, last status change time: 00:15:45
Signaling protocol: LDP, peer 10.1.1.1:0 up
MPLS VC labels: local 16003, remote 30005
Group ID: local 12, remote 1
MTU: local 1500, remote 1500
Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 56, send 55
byte totals: receive 10181, send 10569
packet drops: receive 0, send 0
EoMPLS is the most common AToM method that supports a host of
features, such as inter-AS operation, redundancy, and EVC
infrastructure.
AToM can be implemented in like-to-like fashion, or in any-to-any by
using AToM interworking.

12 AToM

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

12 AToM

Transféré par

Droits d'auteur :

Formats disponibles

Layer 2 VPNs and Ethernet Services

Native service Pseudo-wire Native service

Back-up FRR Label (VC) EXP S TTL 4 bytes

TE for FRR Label (VC) EXP S TTL 4 bytes

Core LDP Label (VC) EXP S TTL 4 bytes

VC directed LDP Label (VC) EXP S TTL 4 bytes

Optional control word 4 bytes

Dot1Q Header (only in Port Mode Xconnect) 4 bytes

Label (LDP) EXP 0 TTL Tunnel label

Label (VC) EXP 1 TTL VCl label

(FR, Ethernet, Pseudo- (FR, Ethernet,

Preamble SFD DA SA TPID TCI EtherType Data FCS

Transported using AToM

Case 1: Service node and Case 2:

Standby AC Standby PoA Standby PoA

Layer 2 peer-to-peer native

Access side: Trunk side:

Unique or multiple values untagged

encapsulation dot1q 10 second 100 matches any packets with

Frame received EFP configuration

Cisco IOS XR:

Control word is optional in EoMPLS

pseudowire-class pw-class1 pseudowire-class pw-class2

Control word is optional in PPP and HDLC over MPLS

RP/0/RSP0/CPU0:PE1# show l2vpn xconnect

Cisco IOS and IOS XE:

PE2#show xconnect all detail

PE2# show mpls l2transport vc detail

Vous aimerez peut-être aussi