Verifying 6VPE Operation

Figure 9-10 depicts the distribution of a vpnv6 prefix and label by MP-iBGP in a 6VPE network.

Figure 9-10 Distribution of vpnv6 Prefixes and Labels

6VPE Network

Loopback 0 PE

2001:0DB8:1:1::1/128

_VRF

london-ce VRF cust-one

MP-iBGP Binding

2001:0DB8:1:2::1/128 + RD Next-hop: 10.200.254.4 Label 21

Loopback 0

Loopback 0

Loopback 0 2001:0DB8:1:2::1/128

sydney-ce VRF cust-one

LDP Binding

10.200.254.4/32 Label 19

LDP Binding

10.200.254.4/32 Label 19

LDP Binding

10.200.254.4/32 Label Implicit-null

Figure 9-11 shows the same network depicting the packet forwarding of an IPv6 packet through the 6VPE network.

Figure 9-11 Packet Forwarding Through the 6VPE Network

Label 19

Label 19

Label 21

Label 21

IPv6 Packet

IPv6 Packet

Loopback 0 2001:0DB8:1:1::1/128

london-ce

london paris

new-york

PE Loopback 0 Loopback 0

m sydney sydney-ce

Label 21

IPv6 Packet

Pv6 Packet

Pv6 Packet

VRF cust-one

VRF cust-one

Example 9-33 shows how to check which IPv6 VRFs are running on the PE router. Example 9-33 Verifying IPv6 VRFs

london#show vrf ipv6 cust-one

Name Default RD

Protocols Interfaces

cust-one 1:1

ipv6 Serial2/0

london#show vrf ipv6 detail

VRF cust-one; default RD 1:1; default VPNID <not set>

Interfaces:

Serial2/0

Address family ipv6 (Table ID = 0x1E000001):

Connected addresses are not in global routing table

Export VPN route-target communities

RT:1:1

Import VPN route-target communities

RT:1:1

No import route-map

No export route-map

VRF label distribution protocol: not configured

london#show vrf ipv6 interfaces

Interface VRF Protocol Address

Serial2/0 cust-one up

2001:DB8:2::2

Example 9-34 shows how to check whether BGP is running the capability of vpnv6.

Example 9-34 Verifying MP-BGP for vpnv6 london#show ip bgp neighbors

BGP neighbor is 10.200.254.4, remote AS 1, internal link BGP version 4, remote router ID 10.200.254.4 BGP state = Established, up for 00:29:29

Last read 00:00:39, hold time is 180, keepalive interval is 60 seconds Neighbor capabilities:

Route refresh: advertised and received(new) Address family VPNv6 Unicast: advertised and received

Example 9-35 shows how to check if on the remote PE, the IPv6 VRF prefix made it into the BGP table.

Example 9-35 Verifying vpnv6 Prefixes sydney#show bgp vpnv6 unicast vrf cust-one 2001:DB8:1:2::1/128

BGP routing table entry for [1:1]2001:DB8:1:2::1/128, version 5 Paths: (1 available, best #1, table cust-one) Advertised to update-groups:

Example 9-35 Verifying vpnv6 Prefixes (Continued) 2

65000

2001:DB8:3::1 (FE80::FF:FEC8:5808) from 2001:DB8:3::1 (10.100.103.1) Origin IGP, metric 0, localpref 100, valid, external, best Extended Community: RT:1:1, mpls labels in/out 21/nolabel

Notice that the RD of the vpnv6 prefixes is printed between []. vpnv6 prefixes are shown in the [RD]IPv6-network/mask-length notation. vpnv4 prefixes are printed in the RD:IPv4-network/ mask-length notation. Using the same notation for vpnv6 prefixes might create problems, because the : used between the RD and the prefix is also used in the IPv6 prefix notation.

Example 9-36 shows how to check whether the IPv6 VRF prefix made it into the BGP table on the ingress PE.

Example 9-36 Verifying vpnv6 Prefixes london#show bgp vpnv6 unicast vrf cust-one 2001:DB8:1:2::1/128

BGP routing table entry for [1:1]2001:DB8:1:2::1/128, version 7 Paths: (1 available, best #1, table cust-one) Advertised to update-groups: 1

65000

::FFFF:10.200.254.4 (metric 13) from 10.200.254.4 (10.200.254.4) Origin IGP, metric 0, localpref 100, valid, internal, best Extended Community: RT:1:1, mpls labels in/out nolabel/21

Example 9-37 shows how to verify the routing entries on the CE and PE routers.

Example 9-37 Verifying Routing Entries on the CE and PE Routers london-ce#show ipv6 route 2001:DB8:1:2::1/128

Routing entry for 2001:DB8:1:2::1/128

Known via "bgp 65000", distance 20, metric 0, type external Route count is 1/1, share count 0 Routing paths:

FE80::A8BB:CCFF:FE00:200, Serial2/0 Last updated 00:30:29 ago london#show ipv6 route vrf cust-one 2001:DB8:1:2::1/128

Routing entry for 2001:DB8:1:2::1/128

Known via "bgp 1", distance 200, metric 0, type internal Route count is 1/1, share count 0 Routing paths:

Example 9-37 Verifying Routing Entries on the CE and PE Routers (Continued)

10.200.254.4%Default-IP-Routing-Table indirectly connected MPLS Required Last updated 00:31:17 ago sydney#show ipv6 route vrf cust-one 2001:DB8:1:2::1/128

Routing entry for 2001:DB8:1:2::1/128

Known via "bgp 1", distance 20, metric 0, type external Route count is 1/1, share count 0 Routing paths:

FE80::FF:FEC8:5808, Serial2/0 Last updated 00:33:08 ago

You can verify the data plane by using ping and traceroute from the CE or PE router. Example 9-38 shows the traceroute and the ping from the london CE and PE router to the sydney CE router.

Example 9-38 Traceroute and Ping

london-ce#traceroute ipv6 2001:DB8:1:2::1

Type escape sequence to abort.

Tracing the route to 2001:DB8:1:2::1

1 2001:DB8:2::2 [AS 1] 40 msec 20 msec 20 msec

2 ::FFFF:10.1.2.2 [MPLS: Labels 19/21 Exp 0] 40 msec 40

msec 40 msec

3 ::FFFF:10.3.1.2 [MPLS: Labels 19/21 Exp 0] 48 msec 48

msec 48 msec

4 2001:DB8:3::2 [AS 1] [MPLS: Label 21 Exp 0] 32 msec 32

msec 32 msec

5 2001:DB8:3::1 [AS 1] 40 msec 40 msec 40 msec

london#ping vrf cust-one ipv6 2001:DB8:1:2::1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 2001:DB8:1:2::1, timeout iiiii

is 2 seconds:

Success rate is 100 percent (5/5), round-trip min/avg/max

= 4/6/8 ms

!The traceroute from the ingress PE inside the VPN:

london#traceroute vrf cust-one ipv6 2001:DB8:1:2::1

Type escape sequence to abort.

Tracing the route to 2001:DB8:1:2::1

1 ::FFFF:10.1.2.2 [MPLS: Labels 19/21 Exp 0] 32 msec *

28 msec

2 ::FFFF:10.3.1.2 [MPLS: Labels 19/21 Exp 0] 28 msec 28

msec 28 msec

3 2001:DB8:3::2 [AS 1] [MPLS: Label 21 Exp 0] 28 msec 28

msec 20 msec

4 2001:DB8:3::1 [AS 1] 32 msec 40 msec 40 msec

Example 9-39 shows how to verify the (two) labels for the IPv6 VRF prefix on the ingress PE router.

Example 9-39 Verifying Labels

london#show bgp vpnv6 unicast vrf cust-one labels

Network

Next Hop In label/Out label

Route Distinguisher: 1:1 (cust-one)

2001:DB8:1:

1::1/128

2001:DB8:2::1 22/nolabel

2001:DB8:1:

2::1/128

::FFFF:10.200.254.4

nolabel/21

2001:DB8:2:

:/64 :: 23/nolabel

2001:DB8:3:

:/64 ::FFFF:10.200.254.4

nolabel/22

london#show ipv6 cef vrf cust-one 2001 :DB8:1:2::1/128

2001:DB8:1:2::

1/128

nexthop 10.1

.2.2 Ethernet0/0 label 19 21

london#show ipv6 cef vrf cust-one 2001:DB8:1:2::1/128 detail

2001:DB8:1:2::

1/128, epoch 0

recursive via 10.200.254.4 label 21

nexthop 10

.1.2.2 Ethernet0/0 label 19

Example 9-40 shows how to verify the label for the next hop (10.200.254.4) of the IPv6 VRF prefix on the P routers.

Example 9-40 Verifying the LFIB on P Routers

paris#show mpls forwarding-table 10.200.254.4 detail

Local

Outgoing Prefix Bytes Label

Outgoing

Next

Hop

Label

Label or VC or Tunnel Id Switched

interface

19

19 10.200.254.4/32 17969

Se3/0

point2point

MAC/Encaps=4/8, MRU=1500, Label Stack{19}

0F008847 00013000

No output feature configured

new-york#show mpls forwarding-table 10.200.254.4 detail

Local

Outgoing Prefix Bytes Label

Outgoing

Next

Hop

Label

Label or VC or Tunnel Id Switched

interface

19

Pop Label 10.200.254.4/32 26473

Et0/0

10.2

1.2

MAC/Encaps=14/14, MRU=1504, Label Stack{}

AABBCC000700AABBCC0005008847

No output feature configured

Example 9-41 shows how to verify the incoming VPN label of the IPv6 VRF prefix in the LFIB on the egress PE router.

Example 9-41 Verifying the LFIB on the Egress PE Router

sydney#show mpls forwarding-table vrf cust-one 2001

:DB8:1:2::1/128 detail

Local

Outgoing Prefix Bytes Label

Outgoing

Next Hop

Label

Label or VC or Tunnel Id Switched

interface

21

No Label 2001:DB8:1:2::1/128[V] \

9360

Se2/0

point2point

MAC/Encaps=0/0, MRU=1504, Label Stack{}

VPN route: cust-one

No output feature configured

The outgoing label is No label, which is correct for an IPv6 VRF prefix learned from the CE router.

Micro Expression Master

Micro Expression Master

If You Could Read Everyone Life A Book You Can Have Better Career, Great Relationships And Become Successful. This Book Is One Of The Most Valuable Resources In The World When It Comes To Reading the smallest and tiniest body Language and know what people are thinking about.

Get My Free Ebook


Post a comment