CISCO EXPO CISCO EXPO , , January 2005 January 2005 N.T.U.A Network Management Center N.T.U.A Network Management Center 6PE: 6PE: IPv6 over MPLS IPv6 over MPLS Presented by: Presented by: Andreas Andreas Polyrakis Polyrakis Dimitrios Dimitrios Kalogeras Kalogeras
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
CISCO EXPOCISCO EXPO, , January 2005January 2005
N.T.U.A Network Management CenterN.T.U.A Network Management Center
6PE: 6PE: IPv6 over MPLSIPv6 over MPLS
Presented by:Presented by:Andreas Andreas PolyrakisPolyrakisDimitriosDimitrios KalogerasKalogeras
NTUA NOCNTUA NOC
22
Cisco Expo, 26Cisco Expo, 26--11--20052005
RoadMapRoadMap
n Introduction¨ The Increasing Need for IPv6¨ MPLS & MPLS VPNs Basic¨ 6PE motivation
n The 6PE Approach¨ Applicability & Requirements¨ Label Distribution¨ Packet Switching¨ Router Interactions¨ Configuration Examples
n Advanced Topics: 6PE over CSC¨ The SEEREN case study¨ 6PE Troubleshooting
n Conclusions
NTUA NOCNTUA NOC
33
Cisco Expo, 26Cisco Expo, 26--11--20052005
What is 6PE?What is 6PE?
nA method to provide IPv6 connectivity to your customers without upgrading the entire network to IPv6
n IPv6 is here for quite some time but…¨ NAT extended the life of IPv4¨ Not motivation to deploy IPv6¨ Vendors did not support IPv6
n However, in the past few years…¨ New types of applications (P2P) – NAT is no longer sufficient¨ Enormous increase of internet users – DSL¨ Not only PCs connect to the internet – 3G mobile devices
n IPv6 is now boosted¨ Vendors now support IPv6¨ ISPs deploy IPv6 services
NTUA NOCNTUA NOC
55
Cisco Expo, 26Cisco Expo, 26--11--20052005
IPv6 Provisioning in Existing NetworksIPv6 Provisioning in Existing Networks
n Upgrade the entire network to dual stack ¨ native IPv6 provisioning¨ operational costs and risks (planning, upgrades, lack of
expertise) Ln In pure IPv4 backbones
¨ Connect IPv6 sites (clients, upstream, server farms) though a mesh of GRE tunnelsn Not scalable Ln Big operational costs (OPEX) L
n In IPv4/MPLS backbones¨ Connect IPv6 sites through a mesh of p2p L2 MPLS VPNs
(ATOM or L2 Interworking)n Similar to GRE tunnels, not scalable Ln ATOM: Same media at endpoints Ln L2 Interworking: Many restrictions apply, too L
¨ Upgrade some edge routers to dual stack and use 6PE
NTUA NOCNTUA NOC
66
Cisco Expo, 26Cisco Expo, 26--11--20052005
X
MPLS SimplifiedMPLS Simplified
n Packet Forwarding based on a Labelimposed at the ingress point
Step 3: Step 3: Label Distribution in 6PELabel Distribution in 6PE
n 6PE routers establish MP-BGP sessions ¨ running over IPv4
n IPv6 prefixes are exchanged through MP-BGPn BGP Next Hop field is the IPv4-mapped IPv6 address of
the 6PE router¨ Mapping: X.Y.Z.W è ::FFFF:X.Y.Z.W
n An “Aggregated IPv6 Label” is sent for IPv6 routes¨ This will be used as the “inner” label
Note: Labels are made and exchanged for the ipv4 loopbacks of the PE routers, too (typical MPLS + LDP)
NTUA NOCNTUA NOC
1818
Cisco Expo, 26Cisco Expo, 26--11--20052005
Step 3: Configuration CommandsStep 3: Configuration Commandsn include “sent-label” in the ipv6 address familynMust be done in both directions PEsn In a Mesh of PEs, it must be done with all PEs
Packet Forwarding in 6PEPacket Forwarding in 6PEn MP-BGP exchanges IPv6 Routes & Labelsn On packet arrival at the ingress 6PE:
¨ The IPv4-mapped IPv6 BGP next-hop for the destination address is found
¨ These two labels are pushed:Inner label: The label for the BGP next-hopOuter label: The label for the IPv4 address correspinding to the IPv4-mapped IPv6 address
n Forwarding: Swap exterior labeln Penultimate Hop Popping (PHP)n Last Hop: Packet received with interior
label onlyn Inner label à VPN & egress interfacen The last label is popped, the IP packet is
forwarded to the CE router
MPL
S C
loud
Raif0
6PEif1
Rbif0
Pif1
Rcif0
Pif1
Rdif0
6PEif1
C2CEif1
C1if0
CE
LFIB for A:Local: LdRem: Lci/f: if0
LFIB for A:Local: LcRem: Lbi/f: if0
LFIB for A:Local: Lb Rem: Øi/f: if0
LFIB for A:(empty)
IPv6 Route X: via ::FFFF:A,Label L6
IPv6 Route X:Label L6,i/f: if0
IPv6
IPv6 A
IPLvLc IPv6L6
IPv6L6Lb
IPv6L6
NTUA NOCNTUA NOC
2020
Cisco Expo, 26Cisco Expo, 26--11--20052005
Routing Interactions in 6PERouting Interactions in 6PE
Advanced Topics: Advanced Topics: 6PE over CSC6PE over CSCCarrier-Supporting-Carrier
(CSC)n For ISPs that are VPN
customers of MPLS Backbones
nA VPN with very small virtual routing table (VRF)
nCSC-CEs exchange limited labels with CSC-PE
nMPLS between CSC-CE and CSC-PE
MPLSCloud
CSC-CE
CSC-PE
CSC-PE
CSC-CE
IP
IPLa
CSC-P
CSC-P
IP
IPLvLb
IPLvLc
IPLvLd
IPLv
IP
ISP1
-C
SC P
RO
VID
ER
ISP2
ISP2
NTUA NOCNTUA NOC
2222
Cisco Expo, 26Cisco Expo, 26--11--20052005
Case Study: The SEEREN networkCase Study: The SEEREN network
nSEEREN: South Eastern European Research & Educational Network¨Upstream: GRNET (Greek Research Network)¨Backup Upstream: Roedunet (via GRNET)¨Peers: Serbia & Montoragevo, Bulgaria, Albania,
FYROM, Bosnia & Herzecovinova¨Connectivity: Oteglobe, via a CSC MPLS VPN
6PE verification & troubleshooting6PE verification & troubleshootingathens-2# sh ip bgp neighbor 194.141.252.13BGP neighbor is 194.141.252.13, remote AS 6802, external linkDescription: UNICOM-BOULGARIABGP version 4, remote router ID 194.141.252.13BGP state = Established, up for 2d08hLast read 00:00:25, hold time is 90, keepalive interval is 30 secondsConfigured hold time is 90, keepalive interval is 30 secondsNeighbor capabilities:Route refresh: advertised and received(new)Address family IPv4 Unicast: advertised and receivedAddress family IPv6 Unicast: advertised and receivedipv6 MPLS Label capability: advertised and received
ipv6 MPLS Label capability: advertised and receive… athens-2# sh bgp ipv6 unicast
BGP table version is 26881, local router ID is 194.177.210.40Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal, S StaleOrigin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path*> 2001:648:F080::/42
athens-2# sh ipv6 route 2001:648:F080::/47IPv6 Routing Table - 487 entriesCodes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
B 2001:648:F080::/42 [20/0]via ::FFFF:194.141.252.13, IPv6-mpls
NTUA NOCNTUA NOC
2828
Cisco Expo, 26Cisco Expo, 26--11--20052005
ConclusionsConclusions
n Purpose: Provide native IPv6 services to customers without changing the IPv4 MPLS core network¨ minimal operational cost and risk¨ scalability¨ fits very well into the general MPLS philosophy è Flexibility
n Requirements:¨ P routers : no modification!¨ PE routers : (a) must be dual stack and (b) must support MP-BGP¨ CE routers : just need to be dual stack
n But also recommended to run an IPv6-capable routing protocol with PEn But do not:
¨ Use 6PE when most customers require IPv6. Consider upgrading theentire network to dual stack
¨ Upgrade your entire network to MPLS only just to support 6PE. Use tunnels instead.