1974 chp10ONLa

1974_chp10ONLa.
fm Page 735 Tuesday, November 14, 2006 10:07 AM

C

H

A

P

T

E

R

S

U

P

P

L

E

M

E

N

T

10

This online supplement of Chapter 10 focuses on more advanced topics regarding Any
Transport over MPLS (AToM). What if the attachment circuits (AC) on the two sides of the
MPLS network have different encapsulation types? How do you interconnect multiple MPLS
networks that are running the AToM service and provide a Layer 2 transport service end to end?
How do you switch two pseudowire segments? To conclude, this chapter looks at what local
switching entails on the provider edge (PE) routers of the MPLS network.

L2VPN Interworking

Up to this point in the book, the ACs on both sides have been the same encapsulation type, which
is also referred to as like-to-like functionality.

L2VPN interworking

is an AToM feature that
allows different encapsulation types at both sides of the AToM network. The interworking
feature then translates one Layer 2 encapsulation to another.
The L2VPN interworking has two possible modes: IP and Ethernet. If the PE is congured for
IP mode, you extract the IP packet from the received frame on the AC and label it before sending
it into the MPLS network, effectively using AToM to transport pure (nonrouted) IP payload
across the MPLS backbone. If the PE is congured for Ethernet mode, you extract the Ethernet
frame from the received frame on the AC (all VLAN headers are removed) and label it before
sending it into the MPLS network.
Table 10-1 lists the L2VPN interworking possibilities for both the IP and Ethernet modes in
Cisco IOS.

Table 10-1

L2VPN Interworking Possibilities

Interworking Encapsulation IP Mode Ethernet Mode

Frame Relay to Ethernet/VLAN Yes Yes
Frame Relay to PPP Yes No
Frame Relay to ATM AAL5 Yes No
Ethernet/VLAN to ATM AAL5 Yes Yes
Ethernet to VLAN Yes Yes
Ethernet to PPP Yes No

Any Transport over MPLS

1974_chp10ONLa.fm Page 736 Tuesday, November 14, 2006 10:07 AM

737

Chapter 10: Any Transport over MPLS

IP Interworking

The benet of L2VPN interworking in IP mode is that you can provide AToM functionality, even
if the encapsulation is different on both sides of the MPLS network. MPLS VPN can carry the IP
trafc across the MPLS network, but MPLS VPN is a service that carries the IP protocol in a point-
to-multipoint fashion, whereas AToM is strictly point-to-point. Furthermore, with MPLS VPN, the
PE and CE router always interact at Layer 3; an IP routing protocol runs between the two routers.
With AToM, however, an IP routing protocol never runs between the PE and CE router. With
AToM, the routing protocol runs between the two CE routers across the pseudowire.
Figure 10-1 shows how the IP packet is transported across the AToM network. The ingress PE
router PE1 strips off the Ethernet encapsulation, takes the IP packet, labels it with the tunnel and
virtual circuit (VC) label, and switches the packets into the MPLS network. The egress PE router
PE2 strips off the VC label, encapsulates the IP packet into PPP, and forwards the frame onto the
correct interface to the CE router.

Figure 10-1

Example of IP Interworking: Ethernet to PPP

Example 10-1 shows you the conguration for the case of Ethernet to PPP interworking. IP
interworking is simply congured by conguring

interworking IP

under the pseudowire-class.

NOTE

IP interworking is also known as routed interworking.

Example 10-1

Ethernet to PPP IP Interworking Example

PE1#

ppp psss seee euuu uddd dooo owww wiii irrr reee e--- -ccc clll laaa asss ssss s ooo onnn neee e
eee ennn nccc caaa appp psss suuu ulll laaa attt tiii iooo onnn n mmm mppp plll lsss s
IP IP IP
Label 23 Label 23
Label 74 Label 88
Control
Word
Control
Word
Ethernet
Header
Label 23
Control
Word
PPP
Header
IP IP
Ethernet

VCID 100
PE1-CE
Loopback 0
10.200.254.1/32 P P
FastEth 9/0/0
Attachment
Circuit (AC)
PE1 PE2
PE2-CE
PPP

VCID 100
Loopback 0
10.200.254.4/32
Serial 4/0/0
Attachment
Circuit (AC)


L2VPN Interworking

738

sss seee eqqq quuu ueee ennn nccc ciii innn nggg g bbb booo ottt thhh h
iii innn nttt teee errr rwww wooo orrr rkkk kiii innn nggg g iii ippp p
!!! !
iii innn nttt teee errr rfff faaa accc ceee e FFF Faaa asss sttt tEEE Ettt thhh heee errr rnnn neee ettt t999 9/// /000 0/// /000 0
nnn nooo o iii ippp p aaa addd dddd drrr reee esss ssss s
xxx xccc cooo onnn nnnn neee eccc cttt t 111 1000 0... .222 2000 0000 0... .222 2555 5444 4... .444 4 111 1000 0000 0 ppp pwww w--- -ccc clll laaa asss ssss s ooo onnn neee e
!!! !

PE2#

sss seee eqqq quuu ueee ennn nccc ciii innn nggg g bbb booo ottt thhh h
!!! !
iii innn nttt teee errr rfff faaa accc ceee e SSS Seee errr riii iaaa alll l444 4/// /000 0/// /000 0
eee ennn nccc caaa appp psss suuu ulll laaa attt tiii iooo onnn n ppp pppp pppp p
!!! !

PE1#

sss shhh hooo owww w mmm mppp plll lsss s lll l222 2ttt trrr raaa annn nsss sppp pooo orrr rttt t vvv vccc c 111 1000 0000 0

Local intf Local circuit Dest address VC ID Status
------------- -------------------- --------------- ---------- ----------
Fa9/0/0 Ethernet 10.200.254.4 100 UP

PE1#

sss shhh hooo owww w mmm mppp plll lsss s lll l222 2ttt trrr raaa annn nsss sppp pooo orrr rttt t vvv vccc c 111 1000 0000 0 ddd deee ettt taaa aiii illl l

Local interface: Fa9/0/0 up, line protocol up, Ethernet up
MPLS VC type is IP, interworking type is IP
Destination address: 10.200.254.4, VC ID: 100, VC status: up
Output interface: Et0/0/0, imposed label stack {74 23}
!output omitted for brevity
PE2#

sss shhh hooo owww w mmm mppp plll lsss s lll l222 2ttt trrr raaa annn nsss sppp pooo orrr rttt t vvv vccc c 111 1000 0000 0

------------- ----------------------- --------------- ---------- ----------
Se4/0/0 PPP 10.200.254.1 100 UP

PE2#


Local interface: Se4/0/0 up, line protocol up, PPP up
Preferred path: not configured
Default path: active
Tunnel label: 22, next hop point2point
Output interface: Se5/0, imposed label stack {22 24}

Example 10-1

Ethernet to PPP IP Interworking Example (Continued)


739


This particular example can lead to an interesting problem. On one side of the pseudowire, the AC
is a point-to-point medium (PPP), whereas on the other side, it is a broadcast medium (Ethernet).
This is a problem for some routing protocols, such as Open Shortest Path First (OSPF). Enhanced
Interior Gateway Routing Protocol (EIGRP), however, does not have a problem. The EIGRP hello
packets are broadcasted to the 224.0.0.10 multicast IP address. The two CE routers form an
EIGRP neighborship across the pseudowire without special conguration.
OSPF is unique because it operates differently over point-to-point media than it does over
broadcast media. If the default OSPF conguration is kept, OSPF does not function correctly
across the pseudowire because it behaves in Broadcast mode over the Ethernet AC and in Point-
to-Point mode over the PPP AC. To solve this problem, congure the Ethernet interface so that
OSPF sees it as a point-to-point interface. You can do this with the command

ip ospf network
point-to-point

on the Ethernet interface of the CE router. Example 10-2 shows the con-
guration needed on the CE routers to get OSPF working in the case of Ethernet to PPP IP
interworking.

Example 10-2

Ethernet to PPP IP Interworking: OSPF

PE1-ce#

!!! !
iii innn nttt teee errr rfff faaa accc ceee e FFF Faaa asss sttt tEEE Ettt thhh heee errr rnnn neee ettt t000 0/// /111 1
iii ippp p aaa addd dddd drrr reee esss ssss s 111 1000 0... .111 1000 0000 0... .111 1000 0000 0... .111 1 222 2555 5555 5... .222 2555 5555 5... .222 2555 5555 5... .000 0
iii ippp p ooo osss sppp pfff f nnn neee ettt twww wooo orrr rkkk k ppp pooo oiii innn nttt t--- -ttt tooo o--- -ppp pooo oiii innn nttt t
!!! !
rrr rooo ouuu uttt teee errr r ooo osss sppp pfff f 111 1000 0000 0
lll looo oggg g--- -aaa addd djjj jaaa accc ceee ennn nccc cyyy y--- -ccc chhh haaa annn nggg geee esss s
nnn neee ettt twww wooo orrr rkkk k 111 1000 0... .000 0... .000 0... .000 0 000 0... .222 2555 5555 5... .222 2555 5555 5... .222 2555 5555 5 aaa arrr reee eaaa a 000 0
!!! !

PE2-ce#

!!! !
iii innn nttt teee errr rfff faaa accc ceee e SSS Seee errr riii iaaa alll l000 0/// /000 0
eee ennn nccc caaa appp psss suuu ulll laaa attt tiii iooo onnn n ppp pppp pppp p
!!! !
rrr rooo ouuu uttt teee errr r ooo osss sppp pfff f 111 1000 0000 0
lll looo oggg g--- -aaa addd djjj jaaa accc ceee ennn nccc cyyy y--- -ccc chhh haaa annn nggg geee esss s
nnn neee ettt twww wooo orrr rkkk k 111 1000 0... .000 0... .000 0... .000 0 000 0... .222 2555 5555 5... .222 2555 5555 5... .222 2555 5555 5 aaa arrr reee eaaa a 000 0
!!! !

PE1-ce#

sss shhh hooo owww w iii ippp p ooo osss sppp pfff f iii innn nttt teee errr rfff faaa accc ceee e fff faaa asss sttt tEEE Ettt thhh heee errr rnnn neee ettt t 000 0/// /111 1

FastEthernet0/1 is up, line protocol is up
Internet Address 10.100.100.1/24, Area 0
Process ID 100, Router ID 10.1.1.1, Network Type POINT_TO_POINT, Cost: 1
Transmit Delay is 1 sec, State POINT_TO_POINT,
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
oob-resync timeout 40


L2VPN Interworking

740

continues

Example 10-3 shows an AToM network with IP interworking between ATM AAL5 encapsulation
on the PE router PE1 and Ethernet VLAN encapsulation on the PE router PE2. Notice that the
MTU on the ATM interface has been changed to 1500 (the default is 4470); otherwise, the
pseudowire VCID 1000 between the two PE routers would not function because of an MTU
mismatch.

Hello due in 00:00:02
Index 2/2, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 10.100.103.2
Suppress hello for 0 neighbor(s)
PE1-ce#

sss shhh hooo owww w iii ippp p ooo osss sppp pfff f nnn neee eiii iggg ghhh hbbb booo orrr r

Neighbor ID Pri State Dead Time Address Interface
10.100.103.2 0 FULL/ - 00:00:39 10.100.100.2 FastEthernet0/1

Example 10-3

Ethernet VLAN to ATM AAL5 IP Interworking

hhh hooo osss sttt tnnn naaa ammm meee e PPP PEEE E111 1--- -ccc ceee e
!!! !
iii innn nttt teee errr rfff faaa accc ceee e AAA ATTT TMMM M222 2/// /000 0... .111 1 ppp pooo oiii innn nttt t--- -ttt tooo o--- -ppp pooo oiii innn nttt t
mmm mttt tuuu u 111 1555 5000 0000 0
nnn nooo o aaa attt tmmm m eee ennn naaa abbb blll leee e--- -iii illl lmmm miii i--- -ttt trrr raaa appp p
ppp pvvv vccc c 111 1000 0/// /111 1000 0000 0
eee ennn nccc caaa appp psss suuu ulll laaa attt tiii iooo onnn n aaa aaaa alll l555 5sss snnn naaa appp p
!!! !
!!! !
!!! !
iii innn nttt teee errr rfff faaa accc ceee e FFF Faaa asss sttt tEEE Ettt thhh heee errr rnnn neee ettt t000 0/// /111 1
!!! !
iii innn nttt teee errr rfff faaa accc ceee e FFF Faaa asss sttt tEEE Ettt thhh heee errr rnnn neee ettt t000 0/// /111 1... .111 1000 0000 0
eee ennn nccc caaa appp psss suuu ulll laaa attt tiii iooo onnn n ddd dooo ottt t111 1QQQ Q 111 1000 0000 0
!!! !
hhh hooo osss sttt tnnn naaa ammm meee e PPP PEEE E111 1
!!! !

Example 10-2

Ethernet to PPP IP Interworking: OSPF (Continued)


741


!!! !
iii innn nttt teee errr rfff faaa accc ceee e AAA ATTT TMMM M888 8/// /000 0/// /000 0
mmm mttt tuuu u 111 1555 5000 0000 0
ppp pvvv vccc c 111 1000 0/// /111 1000 0000 0 lll l222 2ttt trrr raaa annn nsss sppp pooo orrr rttt t
xxx xccc cooo onnn nnnn neee eccc cttt t 111 1000 0... .222 2000 0000 0... .222 2555 5444 4... .444 4 111 1000 0000 0000 0 ppp pwww w--- -ccc clll laaa asss ssss s ooo onnn neee e
!!! !
!!! !
!!! !
iii innn nttt teee errr rfff faaa accc ceee e FFF Faaa asss sttt tEEE Ettt thhh heee errr rnnn neee ettt t444 4/// /111 1/// /000 0... .111 1000 0000 0
!!! !

PE1#

sss shhh hooo owww w mmm mppp plll lsss s lll l222 2ttt trrr raaa annn nsss sppp pooo orrr rttt t vvv vccc c 111 1000 0000 0000 0 ddd deee ettt taaa aiii illl l

Local interface: AT8/0/0 up, line protocol up, ATM AAL5 10/100 up
Tunnel label: 23, next hop 10.200.200.2
!output trimmed for brevity

PE2#

sss shhh hooo owww w mmm mppp plll lsss s lll l222 2ttt trrr raaa annn nsss sppp pooo orrr rttt t vvv vccc c 111 1000 0000 0000 0 ddd deee ettt taaa aiii illl l

Local interface: Fa4/1/0.100 up, line protocol up, Eth VLAN 100 up
PE1#

sss shhh hooo owww w aaa attt tmmm m ppp pvvv vccc c 111 1000 0/// /111 1000 0000 0

ATM8/0/0: VCD: 1, VPI: 10, VCI: 100
UBR, PeakRate: 149760
AAL5-LLC/SNAP, etype:0x0, Flags: 0x10000C20, VCmode: 0x0

Example 10-3

Ethernet VLAN to ATM AAL5 IP Interworking (Continued)


L2VPN Interworking

742

continues

Ethernet Interworking

A second form of L2VPN interworking is Ethernet interworking, which is also referred to as
bridged interworking. When the PE router receives Layer 2 frames, it extracts the Ethernet frame,
labels it, and sends it across the MPLS network.
The advantage of using Ethernet interworking is that you can use integrated routing and bridging
(IRB) or routed bridge encapsulation (RBE) on the CE router. One benet of using RBE, for
example, is that the Ethernet connectivity becomes alike when using an Interior Gateway Protocol
(IGP) that would otherwise have problems dealing with a point-to-point interface on one CE and
a multipoint interface on the other CE. Of course, just bridging the Ethernet frames is also a
possibility. Another benet of using Ethernet as the Interworking mode is that it supports the
transport of multiple Layer 3 protocols across the pseudowire, whereas IP interworking does not.
An example in which Ethernet interworking for AToM is desirable is an enterprise network that
has multiple sites interconnected through a service provider that provides the AToM service. For
technical reasons or even pricing reasons, it might not be possible to have Ethernet encapsulation
all the way up to the PE router. In those cases, Ethernet can be encapsulated into ATM, Frame
Relay, and so on to bring it to the PE router.
Example 10-4 shows the conguration of the PE routers in an AToM network in which Ethernet
interworking exists between VLAN and Ethernet. In other words, one PE has a VLAN toward the
CE, whereas the other PE has a plain Ethernet link toward the CE. The two CE routers can
communicate across the AToM network because of the Ethernet interworking that results in the
VLAN (dot1q) header being stripped off from the Ethernet frame before sending the frame across
the AToM network. For the frames in the opposite directionfrom the Ethernet link to the VLAN
linkthe VLAN header is added before the frame is sent toward the CE router or switch. You
congure Ethernet interworking by conguring

interworking ethernet

under the pseudowire-
class.

OAM Cell Emulation: not configured
Interworking Method: IP
Remote Circuit Status = No Alarm, Alarm Type = None

Example 10-4

Ethernet to VLAN Interworking

PE1#

iii innn nttt teee errr rwww wooo orrr rkkk kiii innn nggg g eee ettt thhh heee errr rnnn neee ettt t
!!! !

Example 10-3

Ethernet VLAN to ATM AAL5 IP Interworking (Continued)


743


!!! !

PE2#

!!! !
!!! !

PE1#


Local interface: Fa9/0/0 up, line protocol up, Ethernet up
Create time: 00:08:56, last status change time: 00:08:51
Signaling protocol: LDP, peer 10.200.254.4:0 up
MPLS VC labels: local 23, remote 19
Group ID: local 0, remote 0
MTU: local 1500, remote 1500
Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 94, send 156
byte totals: receive 9174, send 19558
packet drops: receive 0, send 0
PE2#


MPLS VC type is Ethernet, interworking type is Ethernet

Example 10-4

Ethernet to VLAN Interworking (Continued)


L2VPN Interworking

744

continues

Example 10-5 shows the Ethernet interworking between ATM AAL5 and Ethernet VLAN. The
conguration is similar to Example 10-3, except for the


on the PE routers
and the conguration on the CE router with the ATM interface. That CE router PE1-ce is now
using RBE. RBE allows a bridged segment to be terminated on a routed ATM point-to-point
interface. You congure RBE with the command

atm route-bridged ip

on the ATM interface.

Sequencing: receive disabled, send disabled
Sequence number: receive 0, send 0
VC statistics:
packet drops: receive 0, seq error 0, send 0

Example 10-5

Ethernet VLAN to ATM AAL5 Ethernet Interworking with RBE on the CE

!!! !
mmm mttt tuuu u 111 1555 5000 0000 0
aaa attt tmmm m rrr rooo ouuu uttt teee e--- -bbb brrr riii iddd dggg geee eddd d iii ippp p
ppp pvvv vccc c 111 1000 0/// /111 1000 0000 0
!!! !

hostname PE2-ce
!
interface FastEthernet0/1.100
encapsulation dot1Q 100
ip address 10.100.100.2 255.255.255.0
!

hostname PE1
!
pseudowire-class one
encapsulation mpls
!
!
interface ATM8/0/0
mtu 1500
no ip address
pvc 10/100 l2transport
encapsulation aal5snap
xconnect 10.200.254.4 1000 pw-class one
!

Example 10-4

Ethernet to VLAN Interworking (Continued)


745


Example 10-6 shows the Ethernet interworking between ATM AAL5 and Ethernet VLAN again.
The only difference from the previous example is that the CE router PE1-ce is using IRB now. IRB
allows for routing of a protocol between routed interfaces and bridge groups on one router. IRB
creates a Bridge Group Virtual Interface (BVI), which enables the packets to be switched between
the routed and bridged interfaces. The BVI interface is created so that the routed interfaces have
one interface that represents the bridge group on that router.

!!! !
!!! !
!!! !
PE1#sss shhh hooo owww w mmm mppp plll lsss s lll l222 2ttt trrr raaa annn nsss sppp pooo orrr rttt t vvv vccc c 111 1000 0000 0000 0 ddd deee ettt taaa aiii illl l
Local interface: AT8/0/0 up, line protocol up, ATM AAL5 10/100 up
PE2#sss shhh hooo owww w mmm mppp plll lsss s lll l222 2ttt trrr raaa annn nsss sppp pooo orrr rttt t vvv vccc c 111 1000 0000 0000 0 ddd deee ettt taaa aiii illl l
Example 10-6 Ethernet VLAN to ATM AAL5 Ethernet Interworking with IRB on the CE
!!! !
bbb brrr riii iddd dggg geee e iii irrr rbbb b
!!! !
Example 10-5 Ethernet VLAN to ATM AAL5 Ethernet Interworking with RBE on the CE (Continued)
L2VPN Inter-Autonomous Networking 746
L2VPN Inter-Autonomous Networking
So far in this chapter, the MPLS network that has been supporting the AToM service has been one
autonomous system (AS). If the MPLS network that provides AToM is split over two or more
autonomous systems, the following must be true:
The loopback IP prexes (/32 prexes) of the PE routers must be known in the other
autonomous system(s). These loopback IP prexes are used by the xconnect commands.
The targeted Label Distribution Protocol (LDP) session must be set up between the PE
routers.
A label switched path (LSP) must exist between the PE routers.
mmm mttt tuuu u 111 1555 5000 0000 0
bbb brrr riii iddd dggg geee e--- -ggg grrr rooo ouuu uppp p 111 1
ppp pvvv vccc c 111 1000 0/// /111 1000 0000 0
!!! !
!!! !
iii innn nttt teee errr rfff faaa accc ceee e BBB BVVV VIII I111 1
mmm mttt tuuu u 111 1555 5000 0000 0
!!! !
bbb brrr riii iddd dggg geee e 111 1 ppp prrr rooo ottt tooo occc cooo olll l iii ieee eeee eeee e
bbb brrr riii iddd dggg geee e 111 1 rrr rooo ouuu uttt teee e iii ippp p
!!! !
!!! !
iii innn nttt teee errr rfff faaa accc ceee e FFF Faaa asss sttt tEEE Ettt thhh heee errr rnnn neee ettt t000 0/// /111 1... .111 1000 0000 0
!!! !
Example 10-6 Ethernet VLAN to ATM AAL5 Ethernet Interworking with IRB on the CE (Continued)
747 Chapter 10: Any Transport over MPLS
If these requirements are met, AToM can work across different autonomous systems without a
problem. Figure 10-2 shows the requirement for L2VPN Inter-Autonomous Networking. The
link(s) between the autonomous system boundary routers (ASBRs) must carry labeled packets;
otherwise, no end-to-end LSP exists between the PE routers. That also entails that a label
distribution exists between the two ASBRs. This can be either an IGP with LDP, or it can be eBGP
with label distribution for IPv4 prexes.
Figure 10-2 L2VPN Inter-Autonomous Networking: Method 1
You can achieve Inter-Autonomous Networking of AToM networks in another way. You can
connect two autonomous systems by connecting two PE routers, one from each autonomous
system. These two border routers can share one subinterface or VC between them for each
pseudowire they need to transport from one autonomous system to the other. Figure 10-3 shows
this way of interconnecting the AToM service between two autonomous systems.
Targeted LDP Session
LSP
PE
CE CE
LSP
Autonomous System 1 Autonomous System 2
Labeled Packets
PE ASBR ASBR
L2VPN Pseudowire Switching 748 L2VPN Pseudowire Switching
Figure 10-3 L2VPN Inter-Autonomous Networking: Method 2
In this scenario, you do not need an end-to-end LSP between the PE routers or a targeted LDP
session between the PE routers from different autonomous systems. The trafc between the
ASBRs is not labeled trafc as in the previous scenario, but it is the native Layer 2 trafc. The
disadvantage of this solution compared to the previous one is that you might need many interfaces
between the ASBRs (for example, one interface for each High-Level Data Link Control [HDLC]
link transported across autonomous systems) if you have several Layer 2 virtual private networks
(VPNs) shared between the two autonomous systems. The previous solution, however, needed
only one link between the ASBRs that could then carry all labeled packets for all shared
pseudowires between the two autonomous systems. You can alleviate this disadvantage somewhat
if only Ethernet VLANs are shared between the two AToM-enabled autonomous systems. In that
case, one dot1q trunk between the two ASBRs can carry all the shared VLANs between the two
autonomous systems.
L2VPN Pseudowire Switching
A third method for Inter-Autonomous AToM Networking is available. L2VPN Pseudowire
Switching allows connection of two pseudowire segments. The two pseudowire segments are
stitched together and form one pseudowire end to end. Although two pseudowire segments in one
autonomous system can be stitched together by one LSR, the big advantage is the stitching of two
LSP
PE
CE CE
LSP
Autonomous System 1
LSP
LSP
Autonomous System 2
Layer 2 Frames
PE PE-ASBR PE-ASBR
pseudowire segments from different autonomous systems. Look at Figure 10-4, which shows two
autonomous systems with one pseudowire segment. The two pseudowire segments are stitched
together at the ASBR routers, by a third pseudowire segment. The three pseudowire segments
together form one end-to-end pseudowire.
Figure 10-4 L2VPN Pseudowire Switching Between Two Autonomous Systems
The benet of this method of Inter-Autonomous AToM Networking is that the PE addresses from
one autonomous system do not need to be known on all routers in the other autonomous system.
This is normally necessary for creating one pseudowire end to end. The ASBRs need conguration
to stitch the two pseudowires together. They need to have the point-to-point Layer 2 virtual
forwarding instance (VFI) conguration to make this work. Under the VFI conguration, the
ASBRs have the PEs in the same autonomous system and the ASBRs of the other autonomous
system congured as neighbors. The PE routers need only the normal AToM conguration. One
LDP session exists between the two ASBRs as a result of the neighbor statement under the VFI
toward the other ASBR. This creates a third pseudowire segment between the two ASBRs. The
packets are then switched between two pseudowire segments on each ASBR. The AToM frames
are label switched on the link between the ASBRs. The ASBRs must have a label binding for the
loopback IP address of the other ASBR. Therefore, either an IGP with LDP is needed between the
two ASBRs, or eBGP is needed for advertising IPv4 prexes + label.
Targeted LDP
Session
Targeted LDP
Session
PE
CE CE
HDLC
Loopback 0
10.100.1.1/32
Loopback 0
10.100.1.3/32
Loopback 0
10.100.2.1/32
Loopback 0
10.100.2.3/32
VCID 100
HDLC
VCID 100
Pseudowire Segment 1
Pseudowire
Segment 3
Autonomous System 1
Pseudowire Segment 2
Autonomous System 2
PE ASBR1 ASBR2
Targeted LDP
Session
Tunnel Label
VC Label
Control Word
Frame
VC Label
Control Word
Frame
Tunnel Label
VC Label
Control Word
Frame
L2VPN Pseudowire Switching 750
Example 10-7 shows the conguration needed on ASBR1 and how to verify the L2VPN
Pseudowire Switching. In this example, eBGP for IPv4 is congured with the send-label keyword
toward the other ASBR. BGP is advertising the ASBR loopback prex to the other ASBR. The
encapsulation of the AC at each end is HDLC.
Example 10-7 L2VPN Pseudowire Switching
!!! !
hhh hooo osss sttt tnnn naaa ammm meee e AAA ASSS SBBB BRRR R111 1
!!! !
!!! !
lll l222 2 vvv vfff fiii i lll l222 2vvv vppp pnnn n--- -ooo onnn neee e ppp pooo oiii innn nttt t--- -ttt tooo o--- -ppp pooo oiii innn nttt t
nnn neee eiii iggg ghhh hbbb booo orrr r 111 1000 0... .111 1000 0000 0... .222 2... .111 1 111 1000 0000 0 ppp pwww w--- -ccc clll laaa asss ssss s ooo onnn neee e
nnn neee eiii iggg ghhh hbbb booo orrr r 111 1000 0... .111 1000 0000 0... .111 1... .111 1 111 1000 0000 0 ppp pwww w--- -ccc clll laaa asss ssss s ooo onnn neee e
!!! !
!!! !
iii innn nttt teee errr rfff faaa accc ceee e LLL Looo oooo oppp pbbb baaa accc ckkk k000 0
iii ippp p aaa addd dddd drrr reee esss ssss s 111 1000 0... .111 1000 0000 0... .111 1... .333 3 222 2555 5555 5... .222 2555 5555 5... .222 2555 5555 5... .222 2555 5555 5
!!! !
iii innn nttt teee errr rfff faaa accc ceee e SSS Seee errr riii iaaa alll l333 3/// /000 0
ddd deee esss sccc crrr riii ippp pttt tiii iooo onnn n iii innn nttt teee errr rfff faaa accc ceee e ttt tooo o AAA ASSS SBBB BRRR R222 2
iii ippp p aaa addd dddd drrr reee esss ssss s 111 1000 0... .333 3... .111 1... .111 1 222 2555 5555 5... .222 2555 5555 5... .222 2555 5555 5... .000 0
mmm mppp plll lsss s bbb bggg gppp p fff fooo orrr rwww waaa arrr rddd diii innn nggg g
!!! !
rrr rooo ouuu uttt teee errr r bbb bggg gppp p 111 1
nnn neee ettt twww wooo orrr rkkk k 111 1000 0... .111 1000 0000 0... .111 1... .333 3 mmm maaa asss skkk k 222 2555 5555 5... .222 2555 5555 5... .222 2555 5555 5... .222 2555 5555 5
nnn neee eiii iggg ghhh hbbb booo orrr r 111 1000 0... .333 3... .111 1... .222 2 rrr reee emmm mooo ottt teee e--- -aaa asss s 222 2
nnn neee eiii iggg ghhh hbbb booo orrr r 111 1000 0... .333 3... .111 1... .222 2 sss seee ennn nddd d--- -lll laaa abbb beee elll l
!!! !
ASBR1#sss shhh hooo owww w vvv vfff fiii i lll l222 2vvv vppp pnnn n--- -ooo onnn neee e
VFI name: l2vpn-one, type: point-to-point
Neighbors connected via pseudowires:
Router ID Pseudowire ID
10.100.2.1 100
10.100.1.1 100
ASBR1#sss shhh hooo owww w mmm mppp plll lsss s lll l222 2ttt trrr raaa annn nsss sppp pooo orrr rttt t vvv vccc c 111 1000 0000 0
------------- -------------------------- --------------- ---------- ----------
MPLS PW 10.100.2.1:100 10.100.1.1 100 UP
MPLS PW 10.100.1.1:100 10.100.2.1 100 UP
ASBR1#sss shhh hooo owww w mmm mppp plll lsss s lll l222 2ttt trrr raaa annn nsss sppp pooo orrr rttt t vvv vccc c 111 1000 0000 0 ddd deee ettt taaa aiii illl l
Local interface: MPLS PW 10.100.2.1:100 up
L2VPN Pseudowire Switching
continues
Next hop: 10.1.2.1
Output interface: Et0/0, imposed label stack {40 72}
Sequencing: receive transparent, send transparent
Sequencing resync disabled
VC statistics:
Local interface: MPLS PW 10.100.1.1:100 up
Next hop: point2point
Output interface: Se3/0, imposed label stack {35}
Sequencing: receive transparent, send transparent
Sequencing resync disabled
VC statistics:
PE1#sss shhh hooo owww w mmm mppp plll lsss s lll l222 2ttt trrr raaa annn nsss sppp pooo orrr rttt t vvv vccc c 111 1000 0000 0
------------- -------------------------- --------------- ---------- ----------
Se3/0 HDLC 10.100.1.3 100 UP
ASBR1#sss shhh hooo owww w xxx xccc cooo onnn nnnn neee eccc cttt t ppp peee eeee errr r 111 1000 0... .111 1000 0000 0... .222 2... .111 1 vvv vccc ciii iddd d 111 1000 0000 0 ddd deee ettt taaa aiii illl l
Legend: XC ST=Xconnect State, S1=Segment1 State, S2=Segment2 State
UP=Up, DN=Down, AD=Admin Down, IA=Inactive, NH=No Hardware
Example 10-7 L2VPN Pseudowire Switching (Continued)
Local Switching 752
Local Switching
Local switching is a feature whereby the PE router switches the Layer 2 frames without sending
them across the MPLS network. The Layer 2 frames are never labeled, and as such, this feature has
little to do with AToM. It is mentioned here because it might be useful when AToM is deployed.
Imagine that a customer has two sites close to each other, but both sites need an independent
connection to the AToM network. The two sites probably each have one connection to the same PE
router of the service provider. If Layer 2 trafc needs to be switched between the two sites, it is not
necessary to use the MPLS network; the PE router can switch the trafc locally. Figure 10-5 shows
a PE router with local switching.
Figure 10-5 Local Switching on the PE Router
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP mpls 10.100.2.1:100 UP mpls 10.100.1.1:100 UP
Local VC label 73 Local VC label 46
Remote VC label 35 Remote VC label 72
pw-class: one pw-class: one
ASBR2#sss shhh hooo owww w xxx xccc cooo onnn nnnn neee eccc cttt t ppp peee eeee errr r 111 1000 0... .111 1000 0000 0... .111 1... .333 3 vvv vccc ciii iddd d 111 1000 0000 0 ddd deee ettt taaa aiii illl l
Legend: XC ST=Xconnect State, S1=Segment1 State, S2=Segment2 State
UP=Up, DN=Down, AD=Admin Down, IA=Inactive, NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP mpls 10.100.2.3:100 UP mpls 10.100.1.3:100 UP
Local VC label 32 Local VC label 35
Remote VC label 73 Remote VC label 73
pw-class: one pw-class: one
Example 10-7 L2VPN Pseudowire Switching (Continued)
PE PE
CE
CE
Local Switching
P
Frame Relay/
ATM/Ethernet/VLAN
Frame Relay/
ATM/Ethernet/VLAN
The encapsulations that local switching supports are ATM, Frame Relay, and Ethernet. In some
cases, you can even have interworking for local switching, meaning that the encapsulation type is
different for both links on the PE router. Cisco IOS supports the following interworking for local
switching:
ATM to Ethernet
ATM to Frame Relay
You congure Local Switching by using the connect command in Cisco IOS. If the two interfaces
have a different encapsulation type, the interworking can be IP or Ethernet. As seen in some
previous examples of interworking, you might want to congure RBE or IRB on the CE routers
when the Ethernet interworking is done.
ATM-to-ATM Local Switching
Example 10-8 shows a router congured for ATM-to-ATM Local Switching with encapsulation
AAL5.
ATM-to-ATM local switching is also supported for AAL0 (Cell Relay) in VC mode.
ATM-to-Ethernet Local Switching
On a router, you can have Local Switching between ATM and Ethernet VLAN or Ethernet Port
mode. This local interworking is supported in two modes: IP and Ethernet.
Example 10-8 ATM-to-ATM Local Switching
iii innn nttt teee errr rfff faaa accc ceee e aaa attt tmmm m 111 1/// /000 0/// /000 0
ppp pvvv vccc c 000 0/// /111 1000 0000 0 lll l222 2ttt trrr raaa annn nsss sppp pooo orrr rttt t
eee ennn nccc caaa appp psss suuu ulll laaa attt tiii iooo onnn n aaa aaaa alll l555 5
!!! !
iii innn nttt teee errr rfff faaa accc ceee e aaa attt tmmm m 222 2/// /000 0/// /000 0
ppp pvvv vccc c 000 0/// /111 1000 0000 0 lll l222 2ttt trrr raaa annn nsss sppp pooo orrr rttt t
eee ennn nccc caaa appp psss suuu ulll laaa attt tiii iooo onnn n aaa aaaa alll l555 5
!!! !
ccc cooo onnn nnnn neee eccc cttt t aaa attt tmmm m--- -aaa attt tmmm m aaa attt tmmm m 111 1/// /000 0/// /000 0 000 0/// /111 1000 0000 0 aaa attt tmmm m 222 2/// /000 0/// /000 0 000 0/// /111 1000 0000 0
Local Switching 754
ATM to Ethernet VLAN
Example 10-9 shows a router that is congured for local switching between an ATM PVC
interface that is congured for AAL5SNAP encapsulation and an Ethernet VLAN. The connect
command allows local switching between these two interfaces and species the interworking type
as IP mode.
ATM to Ethernet
Example 10-10 shows a router that is congured for local switching between ATM and Ethernet.
The connect command allows local switching between these two interfaces and species the
interworking type as IP mode.
Example 10-9 ATM-to-Ethernet VLAN Local Switching
!
hostname PE2
!
interface ATM0/0/0
no ip address
pvc 10/100 l2transport
encapsulation aal5snap
!
!
interface FastEthernet4/1/0.100
encapsulation dot1Q 100
!
connect atm-eth ATM0/0/0 10/100 FastEthernet4/1/0.100 interworking ip
!
!
PE2#sss shhh hooo owww w ccc cooo onnn nnnn neee eccc cttt tiii iooo onnn n nnn naaa ammm meee e aaa attt tmmm m--- -eee ettt thhh h
Connection: 9 - atm-eth
Current State: UP
Segment 1: ATM0/0/0 AAL5 10/100 up
Segment 2: FastEthernet4/1/0.100 up
Interworking Type: ip
Example 10-10 ATM-to-Ethernet Local Switching
!!! !
!!! !
!!! !
continues
ATM-to-Frame Relay Local Switching
Example 10-11 shows a router that has two interfaces. One is congured for Frame Relay, and the
other is an ATM interface that is congured for AAL5SNAP encapsulation. The connect
command allows local switching between these two interfaces.
!!! !
ccc cooo onnn nnnn neee eccc cttt t aaa attt tmmm m--- -eee ettt thhh h AAA ATTT TMMM M000 0/// /000 0/// /000 0 111 1000 0/// /111 1000 0000 0 FFF Faaa asss sttt tEEE Ettt thhh heee errr rnnn neee ettt t444 4/// /111 1/// /000 0 iii innn nttt teee errr rwww wooo orrr rkkk kiii innn nggg g iii ippp p
!!! !
!!! !
PE2#sss shhh hooo owww w ccc cooo onnn nnnn neee eccc cttt tiii iooo onnn n nnn naaa ammm meee e aaa attt tmmm m--- -eee ettt thhh h
Connection: 10 - atm-eth
Current State: UP
Segment 2: FastEthernet4/1/0 up
Example 10-11 ATM-to-Frame Relay Local Switching
!!! !
iii innn nttt teee errr rfff faaa accc ceee e SSS Seee errr riii iaaa alll l000 0/// /111 1/// /000 0
eee ennn nccc caaa appp psss suuu ulll laaa attt tiii iooo onnn n fff frrr raaa ammm meee e--- -rrr reee elll laaa ayyy y
fff frrr raaa ammm meee e--- -rrr reee elll laaa ayyy y iii innn nttt teee errr rfff faaa accc ceee e--- -ddd dlll lccc ciii i 333 3000 0000 0 sss swww wiii ittt tccc chhh heee eddd d
!!! !
!!! !
!!! !
ccc cooo onnn nnnn neee eccc cttt t aaa attt tmmm m--- -fff frrr r AAA ATTT TMMM M888 8/// /000 0/// /000 0 111 1000 0/// /111 1000 0000 0 SSS Seee errr riii iaaa alll l000 0/// /111 1/// /000 0 333 3000 0000 0 iii innn nttt teee errr rwww wooo orrr rkkk kiii innn nggg g iii ippp p
!!! !
!!! !
PE1#sss shhh hooo owww w ccc cooo onnn nnnn neee eccc cttt tiii iooo onnn n nnn naaa ammm meee e aaa attt tmmm m--- -fff frrr r
Connection: 9 - atm-fr
Current State: UP
Segment 2: Serial0/1/0 300 up
Example 10-10 ATM-to-Ethernet Local Switching (Continued)
Local Switching 756
Frame Relay-to-Frame Relay Local Switching
Example 10-12 shows a PE router that has serial interfaces congured for Frame Relay. The
connect command allows local switching between these two Frame Relay interfaces.
Example 10-12 Frame Relay-to-Frame Relay Local Switching
!
frame-relay switching
!
interface Serial0/1/0
no ip address
encapsulation frame-relay
frame-relay interface-dlci 300 switched
frame-relay intf-type dce
!
interface Serial0/1/1
no ip address
encapsulation frame-relay
frame-relay interface-dlci 400 switched
frame-relay intf-type dce
!
connect fr-fr Serial0/1/0 300 Serial0/1/1 400
!
!
PE1#sss shhh hooo owww w ccc cooo onnn nnnn neee eccc cttt tiii iooo onnn n nnn naaa ammm meee e fff frrr r--- -fff frrr r
11 fr-fr Se0/1/0 300 Se0/1/1 400 UP

1974 chp10ONLa

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

1974 chp10ONLa

Diunggah oleh

Hak Cipta:

Format Tersedia

1974_chp10ONLa.

fm Page 735 Tuesday, November 14, 2006 10:07 AM

Anda mungkin juga menyukai