10 Gigabit Ethernet, Metro WDM, MPLS, MPLS Traffic Engineering

Transcription

1 10 Gigabit Ethernet, Metro WDM, MPLS, MPLS Traffic Engineering 29th Speedup Workshop on Distributed Computing and High-Speed Networks Berne University Switzerland March 22-23, 23, _06_2000_c2 1 Walter Dey Consulting Engineer Cisco Systems EMEA wdey@cisco.com _06_2000_c2 2 1

2 Agenda 10 Gigabit Ethernet Metro WDM, UCP (Unified Control Plane) MPLS, MPLS Traffic Engineering 3 10 Gigabit Ethernet _06_2000_c2 4 2

3 Ethernet History 1980 s 10 Mbps Ethernet IEEE Mbps Ethernet IEEE 802.3u Mbps Ethernet IEEE 802.3z, 802.3ab 10/100/1000 Mbps Ethernet Link Aggregation IEEE 802.3ad (March) 10 Gbps IEEE 802.3ae 5 Moving the Decimal Point: 10 GbE Performance and Scalability 10 Gbps 10 Gbps OC-192 Ethernet Gigabit EtherChannel 1 Gbps Gigabit Ethernet Fast EtherChannel 100 Mbps Fast Ethernet LAN applications Metro applications WAN applications 10 GbE IEEE 802.3ae Standard

4 Gigabit Ethernet Layer Diagram Media Access Control (MAC) Full Duplex and/or Half Duplex 802.3z Gigabit Media Independent Interface (GMII) (Optional) 1000BaseX PHY 8B/10B 1000BaseT PCS 802.3ab 1000BaseLX Fiber Optic Xcvr 1000BaseSX Fiber Optic Xcvr 1000BaseCX Copper Xcvr 1000BaseT PMA Single-Mode or Multimode Fiber (10km or 550m) Multimode Fiber (275 m) Shielded Copper Cable Unshielded Twisted Pair 7 GBIC Module Flexibility SX Multimode 275 meters only LX/LH ZX Multimode/ 550 meters/ singlemode 10 km singlemode 70km-100km only Modular transceiver plug and play Multiple suppliers Large volume 250K ports/month Low cost (compared to Ether-NOT technologies, Bob Metcalf!) 8 4

5 OC-192 Optics Size First Generation Third Generation VSR OC-192 Optics Circuitry 9 VSR (Very Short Reach) 12 x 1.25G 12x1.25 OC-192 Framer Mapping 16/10 Link Prot FEC Deskew E/O O/E 12 fiber ribbon, MM, x1.25 Features: 12 Tx + 12 Rx 1.25G (10 data + 2 control) 2 x 12 fiber ribbon (Tx and Rx) Protection Channel (1:10) (XOR of the 10 data channels) Error Detection Channel (CRC s of the other 11 channels) Compatible with OC-192 framer interface (OIF99.102) Link length up to 400m Leverages mature GE technology and CMOS SERDES OIF (Optical Internetworking Forum) Contribution OIF

6 Why 10 Gigabit Ethernet? Aggregates Gigabit Ethernet segments Scales Enterprise and Service Provider LAN backbones Leverages installed base of 250 million Ethernet switch ports Supports all types of traffic and services (data, packetized voice and video, storage) Supports metropolitan and wide area networks Faster and simpler than other alternatives Gigabit Ethernet Standard Status IEEE 802.3ae (Task Force) Project kicked off in March, 1999 Project approval January 2000 First draft September 2000 First ballot March 2001 Completion March,

7 IEEE Goals for 10 Gigabit Ethernet Preserve Ethernet frame format Preserve minimum and maximum frame size of current Ethernet (No Jumbo Frames) Support only full duplex operation Support 10,000 Mbps at MAC interface Define two families of PHYs LAN PHY operating at 10 Gbps WAN PHY operating at a data rate compatible with the payload rate of OC-192c/SDH VC-4-64c Note: Partial list 13 Optical Transceivers for 10 Gigabit Ethernet (802.3ae Task Force, late 2000) 14 7

8 10 Gigabit Ethernet LAN Applications Building A 2 to 40 km Building B 10 Gigabit Ethernet SM fiber 10 GigabitEthernet 100 to 300 m, MM fiber Cost-effective bandwidth for the LAN, Switch-to-Switch Aggregate multiple Gigabit Ethernet segments 10 GigaEtherChannel will enable 20 to 80 Gbps (future) Gigabit Ethernet over WAN Attachment to the optical cloud with WAN physical layer (WAN PHY) Compatibility with the installed base of SONET OC-192 No need for protocol conversion, traffic remains IP/Ethernet 10 GbE WAN PHY (< 300 m) DWDM DWDM WAN transport network DWDM 10 GbE (WAN PHY) (< 300 m) OC-192 SONET or DWDM: 1000 s km SONET framing Service Provider POP San Jose, CA Service Provider POP New York, NY 16 8

9 UNI PHY Consistent Encoding for seriel LAN PHY and SONET/SDH payload for a WAN PHY 64B/66B encode Low overhead (3%), seriel LAN PHY runs at 10.3 Gbaud WAN PHY solution puts 64B/66B encoded data stream into payload portion of SDH/SONET data stream 17 Metro WDM, UCP (Unified Control Plane) _06_2000_c2 18 9

10 Metro DWDM Evolution λ GE OC 192 OC 48 OC12 OC 3 100M 10M SONET ATM POS DPT λ1 λ32 λ64 Pt-Pt ADM Rings Mesh 19 Metro DWDM Evolution λ GE Mux OC OC 48 OC12 OC 3 100M 10M N SONET ATM POS DPT λ1 λ32 λ64 Pt-Pt ADM Rings Mesh 20 10

11 Metro DWDM Evolution 10 GE Mux OC OC 48 OC12 OC 3 100M 10M N SONET ATM POS DPT Switching λ1 λ32 λ64 λ128 Pt-Pt ADM Rings Mesh 21 Migration to Mesh Architecture Putting the network in optical networking DWDM transmission Mesh topology A-Z provisioning (Sub-) Wavelength switching granularity Open protocols Increasing distance without regeneration IP Terabit Routing IP controlled Optical Core IP Control plane 22 11

12 Existing Control Planes Network Element Standard Body Routing Signaling Available Optical Cross Connect None Proprietary Proprietary Future ATM Switch ATM Forum PNNI PNNI Deployed MPLS IP-LSR IETF Constraint Based LDP/ RSVP Deployed Source: John Drake MPLS Conference 1999 Separate control planes exist for L1/2/3 Limited communication creates isolation Results in an overlay network model 23 Overlay Model (O-UNI, OIF) Edge-LSR LSR ISP Data Control Plane (MPLS) LSR Edge-LSR Optical Service Provider Optical Control Plane (e.g. WaRP or MPLmS) Wavelength Router Wavelength Router Two Administrative Domains Optical Transport Network Internet Service Provider ISP requests circuits via a UNI interface OTN uses its own Control Plane for Provisioning * ISP... Internet Service Provider 24 12

13 Peer Model (GMPLS, IETF) Common Control Plane (MPLmS) Edge-LSR LSR OXC-LSR OXC-LSR LSR Edge-LSR Wavelength Router One Administrative Domain LSRs and OXC-LSR are Peers Common Control Plane for both L3 and OTN (full visibility of the topology at layer 3) reduced number of routing adjacencies 25 GMPLS and UNI 1.0 Comparison GMPLS O-UNI Notes Standards Body Routing Protocol - Intra-Domain Routing Protocol - Inter-Domain Link Management IETF (1) GMPLS based on MPLS- TE supporting peer model. OSPF-TE IS-IS TE O-BGP * Very early drafts only LMP OIF (2) UNI 1.0 provides public UNI focused on overlay N/A (1) N/A (1) * Public NNI to be developed for later standard LMP (1) Focus on IP control of optical networks using IP control plane (2) - Carrier driven; Transport oriented. Focus on provisioning issues. (1) The client network routing protocol is running completely independent of the optical network routing protocol and there is no exchange of routing information at UNI (1) ITU Recommendation G.709, draft 2000 Reachability information only (no topology data) is to cross the PUB-NNI. * Including neighbor discovery, verification etc *Also includes service discovery Signaling Protocol RSVP-TE CR-LDP RSVP-TE CR-LDP Signaling protocols used by UNI are those from RSVP, LDP and GMPLS, with extensions 26 13

14 MPLS, MPLS Traffic Engineering _06_2000_c2 27 MPLS Summary MPLS is IETF standards based MPLS is accepted as a technology and products of production quality are available MPLS is evolving, e.g. Multicast, AToM (foo over MPLS) MPLS is independent of any Datalink (ATM, FR, POS, Ethernet,.) Not primarily implemented for reasons of performance increase Mainly used by Service Providers, but recently also by Enterprise customers 28 14

15 MPLS as Service Enabler VPN Traffic Engineering Sub-50ms Link/Node protection QoS foo over MPLS (Frame Relay, ATM, Ethernet) 29 FR over MPLS FR Cust FR 101 Port Pi 777 Only one direction illustrated E1 y Port Po z E2 FR 202 DLCI In-EdgeLSR In-Port Out-EdgeLSR OutPort Out-DLCI 101 E1 Pi E2 Po

16 AAL5 over MPLS ATM Cust 3/4 Port Pi 7 Only one direction illustrated E1 y Port Po z E2 5/6 vpi/vci In-ELSR In-Port Out-LSR OutPort vpi/vci 3/4 E1 Pi E2 Po 5/6 31 Traffic Engineering: Motivations What is MPLS Traffic Engineering? MPLS TE is an optimization tool Reduce the overall cost of operations by more efficient use of bandwidth resources by preventing a situation where some parts of a service provider network are over-utilized (congested), while other parts under-utilized 32 16

17 Traffic engineering with Layer 2 (e.g. ATM or Frame Relay) R2 R3 R1 PVC for R2 to R3 traffic PVC for R1 to R3 traffic 33 The Overlay Solution (e.g. ATM) L3 L2 L2 L3 L3 L3 L3 L2 L2 L3 L3 L3 L3 L2 L2 Physical L3 L3 L3 Logical Routing at layer 2 (ATM or FR) is used for traffic engineering Layer 3 sees a complete mesh. Routing at layer 3 is trivial (but poor scalability) 34 17

18 MPLS as the MultiService Infrastructure: Layer Collapsing Applications IP ATM SDH WDM Hard Hard Pt-2-Pt QoS QoS Soft Soft Pt-2-Cloud QoS QoS Admission Control Traffic Engineering Fast Restoration Transport IP MPLS WDM 35 IP Traffic engineering with Layer 3 R2 R3 R1 IP routing: destination-based least-cost routing Path for R2 to R3 traffic Path for R1 to R3 traffic under-utilized utilized alternate path 36 18

19 MPLS Traffic Engineering Example R R4 50 R2 R9 R R6 100 R7 Trying to route a trunk from R1 to R9 with bandwidth 75 Mbps 37 MPLS Traffic Engineering Example (cont( cont) R R4 50 R2 R9 R R6 100 R7 Path Computation CSPF computes paths that obey the various constraints and select the best one (shortest metric). Trying to route a trunk from R1 to R9 with bandwidth 75 Mbps R2-R3 link violates constraint (BW 75) so prune it Pick shortest path on remaining topology 38 19

20 MPLS Traffic Engineering Example (cont.)( Path Setup establishes (explicit) routes for traffic trunks. The signaling protocol to establish the path is RSVP (with extension). R2 50 R3 150 R4 75 R9 R R6 25 R7 39 Protection/restoration in IP/MPLS networks Many various protection/restoration schemes exist today: Optical protection Sonet/SDH (link): offering a 50ms convergence time, largely deployed and stable IP (link & node): Convergence = O(sec) MPLS TE Fast Reroute (link & node) 50 msec convergence

21 Path Protection Controlled by the head-end of a trunk Fallback to either (pre)configured or dynamically computed path Once the head-end has detected that the TE LSP has suffered a failure (through the IGP and/or RSVP), the TE LSP is being re signalled following the new path (if any) 41 MPLS TE FRR Link/Node Protection Controlled by the routers at ends of a failed link (know as MPLS TE Fast Reroute). FRR is a local protection mechanism * link protection is configured on a per link basis * the resilience attribute of a trunk allows to control whether link protection could be applied to the trunk which offers a fine granularity Uses nested LSPs (stack of labels) * original LSP nested within link protection LSP 42 21

22 Link protection for R2-R4 link R8 R9 R2 R4 R1 Pop R5 17 R6 R7 22 Setup: Path (R2->R6 >R6->R7->R4) >R4) Labels Established on Resv message 43 Routing prior R2-R4 link failure R8 R9 R4 R1 37 R2 R6 14 R7 Pop R5 Setup: Path (R1->R2 >R2->R4->R9) >R9) Labels Established on Resv message 44 22

23 Link Protection Active R8 R9 R2 R4 R1 R5 R6 R7 On failure of link from R2 -> R4, R2 simply changes outgoing Label Stack from 14 to <17, 14> 45 Link Protection Active R8 Swap 37->14 Push 17 Pop 14 R4 R9 Push 37 R1 R2 R5 R6 Swap 17->22 R7 Pop 22 Label Stack: R1 R2 R6 R7 R4 R None

24 MPLS TE FRR FRR Link protection is available today. FRR Node protection is the next step. Tools to perform TE LSP back-up placement are under study 47 Thank you! _06_2000_c

25 _06_2000_c