deploying ipv6 services over mpls core architecture guide and

Deploying IPv6 Services Over MPLS Core

Architecture Guide and Case Studies

6PE Architectural Whitepaper with Case Studies

Table of Contents 2

6PE CONTROL AND DATA PLANE CONCEPTS ............................................................................... 3

1.1 Core Control Plane setup ..................................................................................................... 3

1.2 6PE Control Plane setup ...................................................................................................... 4

1.3 Label Stack compilation ...................................................................................................... 5

1.3.1 Label Switch Path Forwarding .................................................................................... 6

IPV6 PROVIDER EDGE(6PE) CONFIGURATION ............................................................................. 7

CE to PE Provisioning and verification ....................................................................................... 8

PE to RR Provisioning and Verification ...................................................................................... 9

PE1 Interface, BGP, OSPF and LDP Configuration ............................................................. 9

Step 1 : Configure related Interface IP addresses as depict in Table 8

matrix. ........................................................................................................................... 9

Step 3: Configure Core links with ISIS and MPLS-LDP ............................................ 11

Route Reflector-1 Configuration ........................................................................................ 11


matrix. ......................................................................................................................... 11

Step 3: Configure ISIS for loopback and LDP for label reachability ....................... 12

Route Reflector-2 Configuration ........................................................................................ 13


matrix. ......................................................................................................................... 13

Step 3: Configure ISIS for loopback and LDP for label reachability ....................... 14

PE2 Interface, BGP, OSPF and LDP Configuration ........................................................... 14


matrix. ......................................................................................................................... 14

Step 3: Configure Core links with ISIS and MPLS-LDP ............................................ 15

Configuration Analysis ........................................................................................................ 15


6PE Control and Data Plane Concepts

This section describes the steps taken to distribute the 6PE routes between the Provider Edge

Router (6PE) systems via the RR (Router Reflector)

1.1 Core Control Plane setup

Figure 1 shows the various steps taken to setup 6PE network in the core part to distribute next

hop reachability using ISIS as IGP and LDP as signanlling protocol in the core by setting up label

switch Paths.

Step 1. The Provider Edge Routers(PE) (PE1-AS100 and PE2-AS100) will be running Multi

Protocol label Switching Protocols (LDP) and ISIS with P routers over BFI (Backbone

facing interfaces). Once ISIS neighborship and LDP sessions are UP between PE

router and P (P2) router. The upstream PE router (PE2-AS100) will advertise

IMPLICIT-NULL (POP) to down stream P router (P2) for the reachability of 2.2.2.2.

Step 2. P2 will receive IMPLICIT-NULL (POP) label from upstream (PE) PE2-AS100 and after

allocating a label (2049) will advertise it to downstream to P1.

Step 3. P1 receives label (2049) from upstream (P2) will allocate label (4335) and will

advertise it to down stream PE (PE1-AS100)

Step 4. PE1-AS100 will install label (4335) against 2.2.2.2 prefix in LFIB

Figure 1: Core Control Plane setup


1.2 6PE Control Plane setup

Figure 2 shows the various steps taken to distribute the IPv6 route 2001:215:2::1from PE2-

AS100 to PE1-AS100 using MP-iBGP over Route Reflector cluster. In this example we are using

OSPFv3 as an example as stated previously, Brocade NetIron supports static, eBGP v6, ISIS v6 in

addition to OSPFv3 as CE to PE protocol.

Step 1. CE to PE will be running IPv6 routing protocol through which IPv6 Prefixes being

advertised for example prefix 2001:215:2::1 is advertised to PE2-AS100 from CE2.

PE2-AS100 receives the IPv6 update via eBGP-v6 session and will allocate BGP

label (19523) to prefix 2001:215:2::1.

Step 2. PE2-AS100 will be running MP-iBGP session with Route reflector cluster RR1-AS100

and RR2-AS100 will set itself as a next hop and will advertise this prefix to Route

reflector cluster RR1 and RR2.

Step 3. Both RR1-AS100 and RR2-AS100 are in the data Path (running MPLS with PEs) will

reflect the routes to route reflector client/non route reflector client without modify

any attribute in BGP prefixes including next hop.

NOTE: Brocade NetIron implementation of 6PE does not support route reflector in

control path (does not run MPLS with PE’s/P’s) (5.4 Release)

Step 4. PE1-AS100 receives the IPv6 update via the MP-iBGP session from RR1-AS100 and

RR2-AS100. Since next-hop-self is the default BGP behaviour in IOS-XR PE2-AS100

will set itself as a nexthop and will advertise it as v4-mapped-v6-address

(::ffff:2.2.2.2) for prefix the 2001:215:2::1. The BGP IPv6 table for the route will

show (794624) as the tags being used for the route (refer to Figure 7) . PE1-AS100

then inserts IPv6 routes from BGP table into Routing.

Step 5. PE1-AS100 will advertise IPv6 prefix learned from PE2-AS100 to CE1

Figure2


1.3 Label Stack compilation

Figure 3 Clearly shows various steps taken by Provider Edge(PE) routers to build label stack for

6PE service.

Figure# Label Stack compilation

Step 1. The IPV6 route (2001:215:2::1) is allocated the BGP label of (794624) by PE2-

AS100 . The BGP next hop is set to PE2AS-100 loopback which is v4-mapped-v6

address (::ffff:2.2.2.2) and advertised to RR1, RR2.

Step 2. RR1, RR2 receives the IPV6 Prefix and looks for the next hop resolution by

performing a label lookup for BGP next hop in MPLS forwarding table. If the next

hop is resolved then RR1, RR2 will reflect the IPV6 route to its client PE1-AS100

Step 3. PE1-AS100 receives the IPv6 Prefix and Label update via an MP-iBGP session from

PE2-AS100. Before installing into Routing Table next hop has to be resolved by

performing a label lookup for BGP next hop in MPLS forwarding table (1050)

Step 4. Once the next hop is resolved Roting Table will install label stack against

(2001:215:2::1) prefix where outer label will be LDP label (4335) and inner VPN

label is the one learned from BGP (794624).


1.3.1 Label Switch Path Forwarding

Various steps taken to forward the labelled packet across the MPLS v4 cloud has described in

this section. Following Figure(6) gives an example of the various labels that get pushed,

swapped and popped in order on the stack as a packet traverse its way from PE1-AS100 for a

end host in destination 2001:215:2::1.

Figure# Label switching path forwarding

Step 1. PE1-AS100 receives an incoming frame destined for a host 2001:215:2::1 from a

CE1.

Step 2. PE1-AS100 (Ingress PE) will impose two labels, VPN (or BGP) label (794624) and

BGP next hop (v4-mapped-v6-address a.k.a PE2-A100) IGP label (1050) (received

by running LDP in the core for next hop reachability) . The packet is then forwarded

to upstream router in the core (P1) .

Step 3. P1 router receives the labelled frame performs look up on the top label (which

happen to be IGP label) swaps it with label (2049) and forwards it to P2.

Step 4. P2 will receive label packet (BGP and IGP Label) from P1 and will POP the top label

and send single label packet with VPN label to PE2-AS100(Label assigned by BGP).

Step 5. PE2-AS100 (egress PE) will perform Label lookup in Routing Tabel which yields

egress interface towards CE2 (CE), PE2-AS100 will dispose the VPN label and will

forward pure IPv6 packet to CE2.


IPv6 Provider Edge (6PE) Configuration

This Section primarily details about the operation and provisioning of 6PE on Various routers

such as Customer Edge(CE), Provider edge(6PE) and Route Reflector(RR) router. IPv6 Routes

directly exchanged between provider edge routers over IPv4 MPLS cloud. Core network in test

scenario is MPLS IPv4 which distributes the IPv6 routes from various CE’s and advertise to

remote 6PE(s) using MP(Multiprotocol)-iBGP session without effecting MPLS IPv4 core

functionality.

Test Setup

Figure# Test Environment for 6PE

The following summarises the test setup that will be used as the basis for the operational

examples:

There is one BGP Autonomous systems, AS 100.

AS 100 has six routers:

1. PE1: 6PE-AS100 acting as the 6PE Edge router.

2. PE2: 6PE-AS100 acting as the 6PE router.

3. P1 and P2 acting as a core routers.

4. RR1 and RR2 are Router reflector cluster to provide redundancy for VPNv6 prefixes.

AS 65001 and AS 65010 are Customer Edge Autonomous system

CE2-AS65010 acting as IPv6 capable customer edge router

RR1 RR2

P1 P2

CE Cloud CE Cloud

AS 100

RR1/RR2-IPv6 Route-Reflector

IPv4 MPLS Core

1.1.1.1 2.2.2.2

PE1

PE2

CE2

CE1


CE1-AS65001 acting as IPv6 capable customer edge router

There will be IPv6 routing protocol (OSPFv3, eBGP v6, Static) running between CE1 <->

PE1 and PE2 <->CE2.

PE1 and PE2 (6PE routers) will be running BGP-v6 session with RR1 and RR2

RR1 and RR2 will be configured as Router reflector cluster for redundancy and will be a

part of data path forwarding.

NOTE: Brocade NetIron implementation of 6PE does not support route reflector in control

path (does not run MPLS with PE’s/P’s) (5.4 Release)

CE to PE Provisioning and verification

CE1 PE1 interface ethernet 2/3

Descripton: CE1-CE link connected to

PE1-PE

ipv6 address 2001:18:2::2/64

ipv6 ospf area 0

ipv6 ospf active

ipv6 router ospf

area 0

interface ethernet 1/3

Descripton: CE1-CE link connected

to PE1-PE

ipv6 address 2001:18:2::1/64

ipv6 ospf area 0

ipv6 ospf active

ipv6 router ospf

area 0

redistribute bgp metric 10

redistribute bgp metric-type type1

NOTE: CE-PE Protocol used in above case is OSPFv3

MPLS/IPv4

Backbone

eth 2/3

eth 1/3

2001:18:2::2/64


PE to RR Provisioning and Verification

Figure# : 6PE Core setup

PE1 P1 P2 PE2 RR1 RR2

PE1 X eth 2/1 x X eth 4/18 eth 2/3

P1 eth 3/1 x eth 3/7 X eth 10/2 eth 2/7

P2 X eth 4/1 x eth 3/3 eth 4/1 eth 1/2

PE2 X x eth 1/5 X eth 2/1 eth 1/2

RR1 eth 2/2 eth 2/1 eth 1/6 eth 1/10 x

RR2 eth 1/1 eth 2/1 eth 1/12 eth 2/2 x

PE1 Interface, BGP, OSPF and LDP Configuration

Step 1 : Configure related Interface IP addresses as depict in Table 8 matrix.

interface loopback 1

Description:Interface used for 6PE peering

ip router isis

ip address 1.1.1.1/32


Description:Connected to P1

enable

ip router isis



Description:Connected to RR1

enable

ip router isis

RR1 RR2

P1 P2 CE Cloud CE Cloud

AS 100

RR1/RR2-IPv6 Route-Reflector IPv4 MPLS Core

1.1.1.1 2.2.2.2

PE1 PE2


Step 2 : Configure BGP Labelled unicast address family with Route Reflector

N

o

t

N

o

t

e

:

N

e

t

i

r

o

n

Implementation(Rel 5.4) does not support bgp next-hop-self by default, we have to turn it on per

neighbor basis.




enable

ip router isis



Descripton: connected to CE1

ipv6 address 2001:18:2::1/64

ipv6 ospf area 0

ipv6 ospf active

**********BGP Config************ router bgp

local-as 100

neighbor 111.111.111.111 remote-as 100

neighbor 111.111.111.111 next-hop-self

neighbor 111.111.111.111 update-source loopback 1




address-family ipv6 unicast

redistribute ospf match internal

redistribute ospf match external1


neighbor 111.111.111.111 activate

neighbor 111.111.111.111 send-label



bgp-redistribute-internal

exit-address-family

Enables iBGP session with

RR1


RR2

Enables IPv6 Labeled unicast for neighbor IP

address (RR1) under IPv6 unicast AF



Redistributes CE-PE protocol routes into BGP under

IPv6 unicast AF


Step 3: Configure Core links with ISIS and MPLS-LDP

Route Reflector-1 Configuration




ip router isis

ip address 111.111.111.111/32


Description:Connected to PE1

enable

ip router isis




enable

ip router isis




enable

ip router isis

ip address 51.10.1.1/30



enable

ip router isis

ip address 53.20.20.1/30

****** ISIS Config******

router isis net 49.0001.0084.45d0.3200.00


exit-address-family

*****MPLS LDP over core links****** router mpls

mpls-interface e2/1

ldp-enable

mpls-interface e4/18

ldp-enable

mpls-interface e2/3

ldp-enable


Step 2 : Configure BGP Labelled unicast address family with Route Reflector Client


local-as 100

cluster-id 222.222.222.222









neighbor 1.1.1.1 route-reflector-client





Note: To implement RR1 and RR2 as part of one Router reflector Cluster , Cluster-id configured

under router bgp must be same on both RR’s.

Step 3: Configure ISIS for loopback and LDP for label reachability


router isis net 49.0001.0085.45e0.8200.00


exit-address-family

*****MPLS LDP over links connecting to 6PE’s ****** router mpls

mpls-interface e2/2

ldp-enable

mpls-interface e1/10

ldp-enable


PE1


PE2

Enables PE1 & PE2 as Route

Reflector clients under IPv6 Unicast

AF


RR2


Route Reflector-2 Configuration




ip router isis

ip address 222.222.222.222/32



enable

ip router isis




enable

ip router isis




enable

ip router isis




enable

ip router isis


Step 2 : Configure BGP Labelled unicast address family with Route Reflector Client


local-as 100

cluster-id 222.222.222.222














Note: To implement RR1 and RR2 as part of one Router reflector Cluster , Cluster-id configured

under router bgp must be same on both RR’s.

Enables PE1 & PE2 as Route

Reflector clients under IPv6 Unicast

AF


PE1


PE2


RR1


Step 3: Configure ISIS for loopback and LDP for label reachability

PE2 Interface, BGP, OSPF and LDP Configuration



router isis net 49.0001.0095.45b0.2200.00


exit-address-family

*****MPLS LDP over links connecting to 6PE’s ****** router mpls

mpls-interface e1/1

ldp-enable

mpls-interface e2/2

ldp-enable



ip router isis




enable

ip router isis




enable

ip router isis

ip address 53.20.20.2/30



enable

ip router isis

ip address 55.8.1.1.1/30


Descripton: Connected to CE2

ipv6 address 2001:28:2::1/64

ipv6 ospf area 0

ipv6 ospf active


Step 2 : Configure BGP Labelled unicast address family with Route Reflector

N

o

t

e

:

N

e

tiNote: NetIron Implementation(Rel 5.4) does not support bgp next-hop-self by default, we have to turn

it on per neighbor basis.

Step 3: Configure Core links with ISIS and MPLS-LDP

Choosen IGP (ISIS) and LDP must be enabled over BFI(Backbone facing Interfaces) on PE routers. We

should also advertise loopback addresses via IGP in the core which provides reachability to establish

iBGP session between PE routers.

Configuration Analysis

This sections describes the various outputs from various show commands and how they relate

between the different routers for 6PE. Each of the relevant routers covered and various tables

such as BGP , RIB and LFIB are examined.

This section has two parts as follows


local-as 100








redistribute ospf match internal







bgp-redistribute-internal

exit-address-family


router isis net 49.0001.0084.45d0.3200.00


exit-address-family

*****MPLS LDP over core links****** router mpls

mpls-interface e2/1

ldp-enable

mpls-interface e1/5

ldp-enable

mpls-interface e3/1

ldp-enable


RR1


RR2





Redistributes CE-PE protocol routes into BGP under

IPv6 unicast AF


1- Control Plane: We will verify if prefixes are installed end to end in BGP->RIB

2- Data Plane: we will verify end to end Label switch path across MPLS v4 core back bone

Control Plane Verification

PE2-AS100 RR1 PE1-AS100

PE2-AS100 This section describes the various show outputs from PE2-AS100 in AS 100.

As discussed PE2-AS100 will receive IPv6 prefixes from CE2-AS200 running OSPFv3 as CE-PE

protocol. The following figures show the various show output commands.

Figure # Global OSPFv3 table on PE2-AS100 show ipv6 ospf routes 2001:215:2::1 Destination Cost E2Cost Tag Flags Dis

OA 2001:215:2::1/64 2 0 0 00000003 110

Next_Hop_Router Outgoing_Interface Adv_Router

fe80::18:18:2 eth1/2 10.10.10.10

show ipv6 route 2001:215:2::1

Type Codes - B:BGP C:Connected I:ISIS L:Local O:OSPF R:RIP S:Static

BGP Codes - i:iBGP e:eBGP

ISIS Codes - L1:Level-1 L2:Level-2

OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2

STATIC Codes - d:DHCPv6

Type IPv6 Prefix Next Hop Router Interface Dis/Metric Uptime src-vrf

Oi 2001:215:2::1/64 fe80::18:18:2 eth 1/2 110/2 6d21h -

label information: 794624(IN)

show ipv6 route tag

IPv6 Routing Table - 16389 entries:







Oi 2001:215:2::1/64 fe80::18:18:2 eth 1/2 110/2 6d21h -

label information: 794624(IN)

show ipv6 bgp routes 2001:215:2::1/64

Number of BGP Routes matching display condition : 1

Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED

E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH

S:SUPPRESSED F:FILTERED s:STALE

Prefix Next Hop MED LocPrf Weight Status

1 2001:215:2::1/64 fe80::18:18:2 2 100 32768 BL

AS_PATH:

Route is advertised to 2 peers:

111.111.111.111(100) 222.222.222.222(100)

****** Route is redistributed into bgp with default attributes and advertised

to 2 peers next hop to be changed

show ip bgp 6pe neighbors


Total number of BGP Neighbors: 2

1 IP Address: 111.111.111.111, AS: 100 (IBGP), RouterID: 111.111.111.111,

VRF: default-vrf

State: ESTABLISHED, Time: 6d22h36m53s, KeepAliveTime: 60, HoldTime: 180

KeepAliveTimer Expire in 33 seconds, HoldTimer Expire in 135 seconds

Minimal Route Advertisement Interval: 0 seconds

UpdateSource: Loopback 1

NextHopSelf: yes

SoftInboundReconfiguration: yes

RefreshCapability: Received

Address Family : VPNV4 Unicast

SendExtenedCommunity: yes

Messages: Open Update KeepAlive Notification Refresh-Req

Sent : 2 11850 21135 0 0

Received: 2 11537 21386 1 0

Last Update Time: NLRI Withdraw NLRI Withdraw

Tx: 1h0m16s 2d21h35m3s Rx: 6d21h49m4s 6d21h49m4s

Last Connection Reset Reason:Rcv Notification

Notification Sent: Unspecified

Notification Received: Cease/CEASE Message

Neighbor NLRI Negotiation:

Peer Negotiated IPV4 unicast capability

Peer Negotiated VPNv4 unicast capability


Peer configured for IPV4 unicast Routes

Peer configured for VPNv4 unicast Routes


Neighbor ipv6 MPLS Label Capability Negotiation:

Peer Negotiated ipv6 MPLS Label capability

Peer configured for ipv6 MPLS Label capability

Neighbor AS4 Capability Negotiation:

Outbound Policy Group:

ID: 5, Use Count: 104

BFD:Disabled

TCP Connection state: ESTABLISHED, flags:00000044 (0,0)

Maximum segment size: 1460

TTL check: 0, value: 0, rcvd: 64

Byte Sent: 3410463, Received: 3235543

Local host: 1.1.1.1, Local Port: 179

Remote host: 111.111.111.111, Remote Port: 8042

ISentSeq: 1024290837 SendNext: 1027701301 TotUnAck: 0

TotSent: 3410464 ReTrans: 231937 UnAckSeq: 1027701301

IRcvSeq: 1299539177 RcvNext: 1302774721 SendWnd: 64981

TotalRcv: 3235544 DupliRcv: 78234 RcvWnd: 65000

SendQue: 0 RcvQue: 0 CngstWnd: 1479

2 IP Address: 222.222.222.222, AS: 100 (IBGP), RouterID: 222.222.222.222,

VRF: default-vrf

State: ESTABLISHED, Time: 13d3h54m19s, KeepAliveTime: 60, HoldTime: 180

KeepAliveTimer Expire in 19 seconds, HoldTimer Expire in 161 seconds

Minimal Route Advertisement Interval: 0 seconds

UpdateSource: Loopback 1

NextHopSelf: yes

SoftInboundReconfiguration: yes

RefreshCapability: Received

Address Family : VPNV4 Unicast

SendExtenedCommunity: yes

Messages: Open Update KeepAlive Notification Refresh-Req

Sent : 1 14031 21177 0 0

Received: 1 3248 21394 0 0

Last Update Time: NLRI Withdraw NLRI Withdraw

Tx: 1h0m17s 2d21h35m4s Rx: --- ---

Last Connection Reset Reason:Unknown


Notification Sent: Unspecified

Notification Received: Unspecified

Neighbor NLRI Negotiation:


Peer Negotiated VPNv4 unicast capability



Peer configured for VPNv4 unicast Routes


Neighbor ipv6 MPLS Label Capability Negotiation:

Peer Negotiated ipv6 MPLS Label capability

Peer configured for ipv6 MPLS Label capability

Neighbor AS4 Capability Negotiation:

Outbound Policy Group:

ID: 5, Use Count: 104

BFD:Disabled

TCP Connection state: ESTABLISHED, flags:00000044 (0,0)

Maximum segment size: 1460

TTL check: 0, value: 0, rcvd: 63

Byte Sent: 7740308, Received: 2711407

Local host: 1.1.1.1, Local Port: 179

Remote host: 222.222.222.222, Remote Port: 8106

ISentSeq: 41280888 SendNext: 49021197 TotUnAck: 0

TotSent: 7740309 ReTrans: 177254 UnAckSeq: 49021197

IRcvSeq: 70756821 RcvNext: 73468229 SendWnd: 65000

TotalRcv: 2711408 DupliRcv: 113426 RcvWnd: 65000

SendQue: 0 RcvQue: 0 CngstWnd: 1460

show ip bgp 6pe neighbors 111.111.111.111 advertised-routes detail

2001:215:2::1/64

Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST E:EBGP I:IBGP L:LOCAL

1 Prefix: 2001:215:2::/64, Status: BL, Age: 7d1h44m35s

NEXT_HOP: ::ffff:2.2.2.2, Learned from Peer: Local Router

In-Label: 794624

LOCAL_PREF: 100, MED: 2, ORIGIN: incomplete, Weight: 32768

AS_PATH:

Adj_RIB_out count: 2, Admin distance 110

show ip bgp 6pe neighbors 111.111.111.111 advertised-routes detail

2001:215:2::1/64


1 Prefix: 2001:215:2::/64, Status: BL, Age: 7d1h44m35s

NEXT_HOP: ::ffff:2.2.2.2, Learned from Peer: Local Router

In-Label: 794624


AS_PATH:


Ipv4 mapped V6/6PE nexthop and advertised to RR1&RR2 making PE2 as next hop

with Outer label /BGP label

Route Reflector (RR1) The Route reflector RR1 will accept the route prefixes from PE2-AS100 over MP-BGP and will install

in the BGP table,since a route is received from its client route reflector will reflect the route to all

route-reflector clients(except to client from which the route is received) and non-clients without

changing any attributes including next-hop in route prefix.

show ipv6 bgp routes 2001:215:2::1/64






Prefix Next Hop MED LocPrf Weight Status

1 2001:215:2::/64 ::ffff:2.2.2.2 2 100 0 BI

AS_PATH:

Last update to IP routing table: 7d1h57m6s

Route is advertised to 1 peer:

1.1.1.1(100)

show ip bgp 6pe neighbors 1.1.1.1 advertised-routes detail 2001:215:2::1/64


1 Prefix: 2001:215:2::/64, Status: BI, Age: 7d1h55m51s

NEXT_HOP: ::ffff:2.2.2.2, Learned from Peer: 2.2.2.2 (100)

Out-Label: 794624


AS_PATH:

ORIGINATOR_ID: 2.2.2.2, CLUSTER_LIST: 222.222.222.222


show mpls route 1.1.1.1

R:RSVP L:LDP S:Static O:Others

Destination Gateway Tnnl Port Label Sig Cost Use

1 1.1.1.1/32 1.1.1.1 tnl124 e2/2 3 L 0 0

Note:Brocade Implementation of 6PE does not support Route Reflector in Control path i.e RR’s must

have MPLS/LDP reachability to the 6PE’s. Unless RR’s have MPLS route to 6PE’s MP-BGP 6PE route

updates will never get advertised to 6PE’s.

PE1-AS 100

show ipv6 bgp routes detail 2001:215:2::1/64





1 Prefix: 2001:215:2::/64, Status: BI, Age: 7d2h54m29s

NEXT_HOP: ::ffff:2.2.2.2, Metric: 1, Learned from Peer:

111.111.111.111 (100)

Out-Label: 794624


AS_PATH:


2 Prefix: 2001:215:2::/64, Status: I, Age: 0h1m54s

NEXT_HOP: ::ffff:2.2.2.2, Metric: 1, Learned from Peer:

222.222.222.222 (100)

Out-Label: 794624


AS_PATH:


Last update to IP routing table: 18h0m36s

Route is not advertised to any peers

***** One selected as best ********

show ipv6 bgp 2001:215:2::1/64


Status codes: s suppressed, d damped, h history, * valid, > best, i internal

Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop MED LocPrf Weight Path

*>i 2001:215:2::/64 ::ffff:2.2.2.2 2 100 0 ?

*i 2001:215:2::/64 ::ffff:2.2.2.2 2 100 0 ?


Last update to IP routing table: 18h28m39s

Route is not advertised to any peers

show ipv6 route 2001:215:2::1/64 debug







Bi 2001:215:2::/64 :: lsp PE1_to_PE2 200/2 18h22m -

label information: 794624(OUT)

Nexthop Entry ID:94038, Paths: 1, Ref_Count:3819/3831

IPv6 fwd route 2001:215:2::/64 (0x11233af0)

RIB:0x11334d4c, next 0x00000000, best 1, NH 0x4d0571af

Type 6, sub 1, paths 1, metric 2, redis:0x00000010

Tag 0, num_as 0, magic 0, notify pim 0, bfd 0

Parent fwd route 2001:215::/32 (0x11276b50)

LP-2#show ipv6 network 2001:215:2::1/64

IPv6 Address Next Hop Interface

1 2001:215:2::/64 :: tnl(531)

Permanent: 1 Action: 0 CamLevel: 1 NohostDropCam:

DontAge: PPCR Flag: 0x00000003 CamAge: NoFreeCam: is_trunk 0

PPCR : 2:2 CIDX: 0x00022536 (L3V6) (IPV6_NETWORK_ENTRY: 0x8bd64)

PPCR : 2:1 CIDX: 0x00022536 (L3V6) (IPV6_NETWORK_ENTRY: 0x8bd64)

pram_index_programmed: ppcr[0] 0x000390f1 ppcr[1] 0x00029c41

ecmp_pram_count: 0 parent: 0 use_index: 0

IPV6-nh-Pram 0: 0x35dc3010, ref_count 3819

n_paths = 1, type = NON_ECMP, is_default = 0, vrf_index = 0

path[0]: FORWARD, out_intf tnl(531), nh 51.1.1.2, out_port 2/1, label 794624,

is_trunk 1

Pram info: alloc_count 1 use_count 1

pram[0]: idx 0, pram_idx[0] 0x000390f1, pram_idx[1] 0x00029c41

Using IPv6 route:

B 2001:215:2::/64 :: tnl(531)

LP-2#show mpls tunnel 531

Name vif-index e-port e-label lsp#/xc# nht index usage sts

PE1_to_PE2 531 2/1 4450 2542 1 104 UP

LP-2#dm pram me/1 0x390f1 ip-vpn

PRAM 0x390f1 255[00001162:010c2000:00000000:00000000]128

127[80010000:00100000:0400000f:08a08200]0

************************PRAM IP VPN entry **********************

DA HIGH 0x0000 Replacement DA (high 2 bytes)

DA LOW 0x00000000 Replacement DA (low 4 bytes)

VLAN_ID 0000 Replacement VLAN ID

MULTICAST_VLAN 0 Set multicast flag in packet header

REPLACE_VLAN_ID 0 Use replacement VLAN ID

TAG 0 Send L2 payload as VLAN tagged pkt

SPA_DISCARD_PKT 0 If 1, allow RPF to discard the packet

REPLACE_DA 0 Use replacement DA

MONITOR 0 Copy packet to MONITOR port


CPU 0 Packet must be copied to CPU

DISCARD INVLD 0 Discard if lookup invalid

DISCARD PACKET 0 Force packet to be discarded

USE FID 1 Use FID from this PRAM entry

USE QOS ID 0 Use QOS ID for rate limiting

INNER VLAN VALID 0 Inner Vlan Valid

QOS ID 0x00 QOS rate limiting ID

VALID 0x000000f Per-port entry valid

FID 0x08a0 Forwarding ID

TRUNK ADJUST 1 Adjust FID based on trunk index

DISABLE QOS OVERRIDE 0 Disable QOS_ID override for CPU-bound pkts

IGNORE SPA MASK 1 IP packets, when src IP processing, will ignore

SPA port mask

PRIORITY_FORCE 0

PRIORITY 0

FWD_COMMAND 2 L3 hardware forwarding command

IGNORE ACLRES 0 Ignore ACL lookup

USE TOS ID 0 Use replacement TOS

TOS ID 0x000 TOS replacement

INNER VLAN ID 0x00000000

PRAM TYPE 1

TRUNK ID 0

NEXTHOP ROUTER INDEX 0x00000001

LOCAL ROUTING 0

INNER LABEL 0xC2000 Inner Label

PUSH OUTER LABEL 1 Push the Outer Label

OUTER LABEL 0x01162 Outer Label

BOGUS LABEL BIT 0 Indicates if this label is

used for single hop acct

MTU_CHECK 0 If 1, enforce mtu check

TNNL_MTU_CHECK_LENGTH 0

show ipv6 ospf redistribute route 2001:215:2::1

Id Prefix Protocol Metric Type Metric

59927 2001:215:2::/64 BGP4+ Type-1 10

Data Plane Verification This section describes the various outputs from various show commands to track end to end data

path and how they relate between the different routers for 6PE. Each of the relevant routers covered

and various tables such as Forwarding and LFIB are examined.

Traffic-sourcePE1-AS100P2P1PE2-AS100Traffic Sink

PE1-AS100 Figure # shows data path forwarding and end to end packet trace


Ingress LC in slot1 on 6PE(PE1-AS100) is programmed to encapsulate IPv6 packet with two labels.

Inner label(BGP label) and the outer label(MPLS label) will be imposed before sending IPv6 packets

on the core (P1)



1 2001:215:2::/64 :: tnl(531)



PPCR : 1:2 CIDX: 0x00022536 (L3V6) (IPV6_NETWORK_ENTRY: 0x96d64)

PPCR : 1:1 CIDX: 0x00022536 (L3V6) (IPV6_NETWORK_ENTRY: 0x96d64)

pram_index_programmed: ppcr[0] 0x0003742b ppcr[1] 0x00028f6b


IPV6-nh-Pram 0: 0x33196010, ref_count 3819

n_paths = 1, type = NON_ECMP, is_default = 0, vrf_index = 0

path[0]: FORWARD, out_intf tnl(531), nh 51.1.1.2, out_port 2/1, label 794624,

is_trunk 1


pram[0]: idx 0, pram_idx[0] 0x0003742b, pram_idx[1] 0x00028f6b

Using IPv6 route:

B 2001:215:2::/64 :: tnl(531)

LP-1#show mpls tunnel 531

Name vif-index e-port e-label lsp#/xc# nht index usage sts

PE1_to_PE2 531 2/1 4450 2542 1 104 UP

LP-1#dm pram me/3 0x28f6b ip-vpn

PRAM 0x28f6b 255[00001162:010c2000:00010000:00000000]128

127[80010000:00100000:04000001:08a08200]0

************************PRAM IP VPN entry **********************


DA LOW 0x00000000 Replacement DA (low 4 bytes)


MULTICAST_VLAN 0 Set multicast flag in packet header


TAG 0 Send L2 payload as VLAN tagged pkt

SPA_DISCARD_PKT 0 If 1, allow RPF to discard the packet








INNER VLAN VALID 0 Inner Vlan Valid


VALID 0x0001001 Per-port entry valid

FID 0x08a0 Forwarding ID


DISABLE QOS OVERRIDE 0 Disable QOS_ID override for CPU-bound pkts

IGNORE SPA MASK 1 IP packets, when src IP processing, will ignore

SPA port mask

PRIORITY_FORCE 0

PRIORITY 0

FWD_COMMAND 2 L3 hardware forwarding command

IGNORE ACLRES 0 Ignore ACL lookup

USE TOS ID 0 Use replacement TOS

TOS ID 0x000 TOS replacement


INNER VLAN ID 0x00000000

PRAM TYPE 1

TRUNK ID 0

NEXTHOP ROUTER INDEX 0x00000001

LOCAL ROUTING 0

INNER LABEL 0xC2000 Inner Label

PUSH OUTER LABEL 1 Push the Outer Label

OUTER LABEL 0x01162 Outer Label



MTU_CHECK 0 If 1, enforce mtu check

TNNL_MTU_CHECK_LENGTH 0

show statistics eth 1/3

PORT 1/3 Counters:

InOctets 105021646 OutOctets 19218

InPkts 207716 OutPkts 23

InBroadcastPkts 0 OutBroadcastPkts 0

InMulticastPkts 32 OutMulticastPkts 6

InUnicastPkts 207684 OutUnicastPkts 17

InDiscards 0 OutDiscards 0

InErrors 0 OutErrors 0

InCollisions 0 OutCollisions 0

OutLateCollisions 0

Alignment 0 FCS 0

InFlowCtrlPkts N/A OutFlowCtrlPkts N/A

GiantPkts 0 ShortPkts 0

InBitsPerSec 48129404 OutBitsPerSec 0

InPktsPerSec 11754 OutPktsPerSec 0

InUtilization 0.50% OutUtilization 0.0%

show mpls statistics 6pe

In-Port(s) Endpt Out-Pkt Tnl Out-Pkt

e1/1 - e1/2 0 0

e1/3 - e1/4 0 115525308

e2/1 - e2/4 0 0

e2/5 - e2/8 0 0

e3/1 - e3/4 0 0

e3/5 - e3/8 0 0

e4/1 - e4/8 0 0

e4/9 - e4/16 0 0

e4/17 - e4/24 0 0

e7/1 - e7/2 0 0

e7/3 - e7/4 0 0

e8/1 - e8/2 0 0

e8/3 - e8/4 0 0

e29/1 0 0

e29/2 0 0

e31/1 0 0

e31/2 0 0

show statistics ethernet 2/1

PORT 2/1 Counters:


InPkts 1281 OutPkts 1564202








OutLateCollisions 0

Alignment 0 FCS 0

InFlowCtrlPkts 0 OutFlowCtrlPkts 0





P1-AS100

show mpls forwarding in-label 4450

Dest-prefix In-lbl Out-lbl Out-intf Sig Next-hop Type

1 2.2.2.2/32 4450 3587 e3/7 R 51.1.1.6

LP-3#show mpls lsp_xc 4450

in-label in-port e-label e-port lsp#/xc# nht-ix seq-no

4450 -- 3587 3/7 2337/1 99 0

4450 -- 5829 2/4 2337/1 97 0 Backup

PPCR 3:1: Counters InPacket: 42416174, InBytes: 22735069264, Rate(kbps): 20529


Pram_info: Alloc Count: 1, Use count 1

0: out_seg idx: 0, PPCR 3:1: Pram idx: 0x00006dcb PPCR 3:2:

Pram idx: 0x000071b8

Event History -

Thu Nov 22 17:27:39 2012 XC Update - No HW Update Needed



Thu Nov 22 17:21:53 2012 XC Add

LP-3#dm pram me/1 0x6dcb mpls

PRAM 0x06dcb 255[00000000:00000e03:00500024:3880e890]128

127[40630003:01000000:0400000f:08c08000]0

************************PRAM MPLS entry **********************

GRE TUNNEL INGRESS 0 GRE Tunnel Ingress

TUNNEL LABEL 0x00e03 Tunnel Label for fwded packets


DA LOW 0x3880e890 Replacement DA (low 4 bytes)

ACTION 0 Router Action - 0 = Transit, 1 = Egress

LABEL OPERATION 0 (swap label)

APPLICATION TYPE 4 Type of MPLS application

PROPAGATE IP-MPLS TTL 0 Propagate TTL between IP and MPLS

PROPAGATE Label TTL 1 Propagate TTL between Labels

NEXTHOP INDEX 0x00000063 Nexthop router index

IGNORE TAG 0 PRAM ignores L2 payload tag

INNER VLAN VALID 0 Inner Vlan ID Valid

INNER VLAN ID 0000 Replacement Inner Vlan ID

REPLACE INNER VLAN 0 Use Replacement Inner VLAN ID

PRAM TYPE 0 PRAM Entry Type

TRUNK ID 2













FID 0x08c0 Forwarding ID


PRIORITY_FORCE 0

PRIORITY 0

IGNORE BLOCK 0 Ignore port or RX VLAN block

GRE TNNL TOS 0x000 GRE Tunnel TOS

Insert RSVP label 0 Insert RSVP label into the frame



ROUTING CONTROL 0x000 Routing control for L2VPN pkt

RSVP Label 0 RSVP label for LDP over RSVP frames


PORT 3/1 Counters:


InPkts 9253310782 OutPkts 8010344957







OutLateCollisions 0

Alignment 0 FCS 0







PORT 3/7 Counters:


InPkts 500571363 OutPkts 4265404512







OutLateCollisions 0

Alignment 0 FCS 0






P2-AS100 show statistics ethernet 4/1

PORT 4/1 Counters:



InPkts 4266186730 OutPkts 500576628







OutLateCollisions 0

Alignment 0 FCS 0






show mpls forwarding in-label 3587

Dest-prefix In-lbl Out-lbl Out-intf Sig Next-hop Type

1 2.2.2.2/32 3587 3 e3/3 R 51.2.2.1

LP-4#show mpls lsp_xc 3587

in-label in-port e-label e-port lsp#/xc# nht-ix seq-no

3587 -- 0 3/3 1539/1 2 0 PHP

3587 -- 0 3/1 1539/1 1 0 PHP

Backup

PPCR 4:1: Counters InPacket: 140440535, InBytes: 75276126760,

Rate(kbps): 66087


Pram_info: Alloc Count: 1, Use count 1

0: out_seg idx: 0, PPCR 4:1: Pram idx: 0x000009d0 PPCR 4:2:

Pram idx: 0x000009d0

Event History -




Thu Nov 22 09:43:03 2012 XC Add

LP-4#dm pram me/1 0x9d0 mpls

PRAM 0x009d0 255[00000000:00000000:0052001b:edadc404]128

127[40020003:03000000:0400000f:08508000]0

************************PRAM MPLS entry **********************

GRE TUNNEL INGRESS 0 GRE Tunnel Ingress

TUNNEL LABEL 0x00000 Tunnel Label for fwded packets

DA HIGH 0x001b Replacement DA (high 2 bytes)

DA LOW 0xedadc404 Replacement DA (low 4 bytes)

ACTION 0 Router Action - 0 = Transit, 1 = Egress

LABEL OPERATION 1 (PHP)

APPLICATION TYPE 4 Type of MPLS application

PROPAGATE IP-MPLS TTL 0 Propagate TTL between IP and MPLS

PROPAGATE Label TTL 1 Propagate TTL between Labels

NEXTHOP INDEX 0x00000002 Nexthop router index

IGNORE TAG 0 PRAM ignores L2 payload tag

INNER VLAN VALID 0 Inner Vlan ID Valid

INNER VLAN ID 0000 Replacement Inner Vlan ID

REPLACE INNER VLAN 0 Use Replacement Inner VLAN ID

PRAM TYPE 0 PRAM Entry Type

TRUNK ID 6













FID 0x0850 Forwarding ID


PRIORITY_FORCE 0

PRIORITY 0

IGNORE BLOCK 0 Ignore port or RX VLAN block

GRE TNNL TOS 0x000 GRE Tunnel TOS

Insert RSVP label 0 Insert RSVP label into the frame



ROUTING CONTROL 0x000 Routing control for L2VPN pkt

RSVP Label 0 RSVP label for LDP over RSVP frames


PORT 3/3 Counters:


InPkts 514186618347 OutPkts 337767214331







OutLateCollisions 0

Alignment 0 FCS 0

InFlowCtrlPkts N/A OutFlowCtrlPkts N/A





PE2-AS100


PORT 1/5 Counters:


InPkts 337776614108 OutPkts 514186681382







OutLateCollisions 0

Alignment 0 FCS 0








1 2001:215:2::/64 fe80::76e8:f8ff:fea5:f301 eth 1/2




PPCR : 1:2 CIDX: 0x00012368 (L3V6) (IPV6_NETWORK_ENTRY: 0x4ae4b)

PPCR : 1:1 CIDX: 0x00012368 (L3V6) (IPV6_NETWORK_ENTRY: 0x4ae4b)

pram_index_programmed: ppcr[0] 0x0000378d ppcr[1] 0x000027b8


IPV6-nh-Pram 0: 0x3108f810, ref_count 3758

n_paths = 4, type = ECMP_PHY_VE, is_default = 0, vrf_index = 0

path[0]: FORWARD, out_intf ve 500, nh fe80::76e8:f8ff:fea5:f301, out_port

1/2, is_trunk 0


pram[0]: idx 0, pram_idx[0] 0x0000378d, pram_idx[1] 0x000027b8

Using IPv6 route:

Oi 2001:215:2::/64 fe80::76e8:f8ff:fea5:f301

eth ½

show mpls statistics 6pe

In-Port(s) Endpt Out-Pkt Tnl Out-Pkt

e1/1 - e1/4 0 0

e1/5 - e1/8 151450599 0

e2/1 - e2/2 0 0

e2/3 - e2/4 0 0

e3/1 - e3/4 0 0

e3/5 - e3/8 0 0

e4/1 - e4/24 0 0


PORT 1/2 Counters:


InPkts 72078273750 OutPkts 84062878477







OutLateCollisions 0

Alignment 0 FCS 0







© 2013 Brocade Communications Systems, Inc. All Rights Reserved. MM/13

ADX, AnyIO, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS,

ICX, MLX, MyBrocade, OpenScript, VCS, VDX, and Vyatta are registered

trademarks, and HyperEdge, The Effortless Network, and The On-Demand Data

Center are trademarks of Brocade Communications Systems, Inc., in the United

States and/or in other countries. Other brands, products, or service names

mentioned may be trademarks of their respective owners.

deploying ipv6 services over mpls core architecture guide and

Documents