Download - Segment Routing: Network Enablement for Application

Cisco Confidential © 2010 Cisco and/or its affiliates. All rights reserved. 1

Segment Routing CCO presentation [email protected]

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2 Strictly Confidential

•  Intro

•  Technology

•  Properties

•  Use Cases

•  Conclusion


Introduction


•  Network enablement for Application –  scalable per-flow resource reservation –  efficient use of resources –  virtualization

•  MPLS optimization –  operation-less –  simple –  entirely automated 50msec FRR


Properties


•  Implicit leverage of all MPLS excellent properties –  standardized and widely supported dataplane –  standardized and widely supported IP control plane (ISIS, OSPF, BGP) –  multi-service capability (VPN4, VPN6, PE6, VPLS, eVPN, PW…)

•  Co-existence with MPLS as currently deployed

•  Incremental deployment

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 7

Application Enabled Routing •  Application to request specifc SLA •  SDN controller does provide path accros the network matching application

SLA

1 0

B

I need a circuit to got to Z with delay = d

bandwidth = b duration = t

SDN controller Cariden

use the segment D > C > G > Z

A

D

C

F

E

G


•  ISIS/OSPF based

•  Entirely automated –  Guarantee Loop Free Alternate –  100% Link & Node protection guaranteed for any topology

100

10

10 10

10


•  Each engineered application flow is mapped on a path

–  millions of paths

•  A path is expressed as an ordered list of segments

•  The network maintains segments –  thousands of segments –  completely independent of application size/frequency

•  Excellent scaling with complete application un-coupling

–  the application state is no longer within the router but within the packet

Millions of Applications

flows

A path is mapped on a

list of segments

The network only maintains

segments No application

state


Technology


•  Data Plane –  MPLS IPv4/IPv6 –  IPv6 (future)

•  Control Plane –  MPLS labels are carry in ISIS or OSPF

– 2 types of Segment Nodal segment (glogal) Adjacency segment (local)


nodal_label = 66

nodal_label = 64 nodal_label = 62 nodal_label = 60

Loop 0: nodal_label = 61 ipv6= 1:1::::61 nodal_label = 63 nodal_label = 65

•  Represents ECMP to a node. •  Configured on interface loopback 0. •  From static label pool •  MUST be unique across the entire network. •  Flooded in ISIS or OSPF domain

1

0

1

0

0

1

2 0

1

2

1 0 2 0

1

2

0

1


Benefits: •  IPv6 loop 0 address are flooded with associated label, no control plane

synchronization required. •  Easy to troubleshoot: 1 label = 1 node •  One protocol => by design, full congruency of Routing and Label table. •  Support ECMP LB.

65

64

66

1

0

1

0

0

1

2 0

1

2

1 0 2 0

1

2

63

62

61

60

NH IPv6 In Label Out Label Out Intf

1:1:::60 60 60 0 & 1

1:1:::61 61 61 0

1:1:::62 62 62 0 & 1

1:1:::63 63 Pop 0

1:1:::64 64 Pop 1

1:1:::66 66 Pop 2

0

1


65

64

66

1

0

1

0

0

1

2 0

1

2

1 0 2 0

1

2

63

62

61

60

0

1

66 Data 66 Data


Adjacency MPLS label •  Node automatically allocates a local label for each adjacency •  Will be flooded in ISIS or OSPF domain

65

64

66

1

0

1

0

0

1

2 0

1

2

1 0 2 0

1

2

63

62

61

60

Interf 0: adj_label = 9000 Interf 1: Adj_label = 9001 Interf 2: Adj_label = 9002

9000

0

1

9001

9002


65

64

66

1

0

1

0

0

1

2 0

1

2

1 0 2 0

1

2

63

62

61

60

9000

0

1

9001

9002

NH IPv6 In Label Out Label Out Intf

1:1:::60 60 60 0 & 1

1:1:::61 61 61 0

1:1:::62 62 62 0 & 1

1:1:::63 63 Pop 0

1:1:::64 64 Pop 1

1:1:::66 66 Pop 2

1:1::65:0 (c) 9000 Pop 0

1:1::65:1 (c) 9001 Pop 1

1:1::65:2 (c) 9002 Pop 2


Explicit path •  will stack labels (ala source routing) •  Could have use 3 nodal-label [65:64:66] •  Adj-label will be required in specific topologies: rings,… •  Simple: no extra protocols •  Scalable: no extra signaling on core routers

65

64

66

1

0

1

0

0

1

2 0

1

2

1 0 2 0

1

2

63

62

61

60

9000

0

1

9001

9002

65 9001 66 Data 9001 66 Data

66 Data

Data


•  Will provide knob to select –  RSVP explicit / dynamic path –  Segment Routing explicit path

•  Traffic into tunnel-te – Reuse existing traffic steering mechanism. PW,L3VPN Static, Dynamic, PBR


SDN Use Cases


SDN controller to learn topology using •  BGP Link State distribution •  XML, OnePK API •  PCE-P •  Others…

65

64

66

1

0

1

0

0

1

2 0

1

2

1

0 2 0

1

2

63

62

61

60

9000

0

1

9001

9002

Learn topology

SDN controller


Application Enabled Routing •  Application to request specifc SLA to go from source host to destination host

65

64

66

1

0

1

0

0

1

2 0

1

2

1

0 2 0

1

2

63

62

61

60

9000

0

1

9001

9002

May I have circuit toH with specific SLA

8004

I need to got to Z with Max delay 100ms bandwidth 20Mb

for next 2h.

SDN controller


65

64

66

1

0

1

0

0

1

2 0

1

2

1

0 2 0

1

2

63

62

61

60

9000

0

1

9001

9002 Full

MPLS segment: [8004:66:9001:65] 65 9001 66 Data 9001

8004

PCC (PCE client) on source Host •  Source host support MPLS forwarding. (no LDP, no IGP, no MPLS CP) •  Source host integrates a PCC lite stack with application API/SDK •  SDN controller will provide the segment routing list to the Host

65,9001, 66, 8004 meets SLA. I account the BW.

I encode the path as nodal segment to 65, adj segment to 9001, nodal segment to 66,

Adj segment to 8004

SDN controller


65

64

66

1

0

1

0

0

1

2 0

1

2

1

0 2 0

1

2

63

62

61

60

9000

0

1

9002

New tunnel-te X Explicit path [8004:66:9001:65]

Stear flow metadata Z to tunnel X

9001

65 9001 66 Data 9001

8004

PCC (PCE client) on Edge and Medata between Host and Edge ( SDN UNI) •  SDN Host will create / delete tunnel-te’s on Egde router via PCEP •  Metadata will tag packets to be forwarded using Segment Routing path.

Data

metadata x

SDN controller


65

64

66

1

0

1

0

0

1

2 0

1

2

1

0 2 0

1

2

63

62

61

60

9000

0

1

9001

9002

New tunnel-te X Explicit path [8004:66:9001:65]

Stear flow Z to tunnel X

9001

65 9001 66 Data 9001

8004

PCC (PCE client) on Edge •  SDN controller will create / delete tunnel-te’s on Egde router usin PCE-P •  Will stear flows to the TE tunnel X

•  Prefix= Static / PBR •  Flow= Open Flow

Data

SDN controller


Conclusion


•  Network enablement for Application –  scalable per-flow resource reservation –  efficient use of resources –  virtualization

•  MPLS optimization –  operation-less –  simple –  entirely automated 50msec FRR


[email protected]


router isis 1

net 49.0001.0010.0000.0001.0

address-family ipv4 unicast

metric-style wide

!

interface Loopback0

passive

address-family ipv4 unicast

nodal-sid sid-value 16001

!

!


RP/0/0/CPU0:R1#show mpls forwarding

Tue Mar 12 04:44:05.526 PDT

Local Outgoing Prefix Outgoing Next Hop Bytes

Label Label or ID Interface Switched

------ ----------- ------------------ ------------ --------------- ------------

16001 Aggregate default: Per-VRF Aggr[V] \

default 0

16004 16004 No ID Gi0/0/0/2 14.0.2.4 13010

17004 Pop No ID Gi0/0/0/2 14.0.2.4 0

18002 18002 No ID Gi0/0/0/0 12.0.0.2 0

18002 No ID Gi0/0/0/1 13.0.1.3 0 Anycast node-SID


RP/0/0/CPU0:R1#show isis route 3.0.0.2/32 detail

Tue Mar 12 04:56:44.347 PDT

L1 3.0.0.2/32 [10/115] medium priority

via 13.0.1.3, GigabitEthernet0/0/0/1, R3

via 12.0.0.2, GigabitEthernet0/0/0/0, R2

src R3.00-00, 3.0.0.1, nodal-SID 18002,0x4 PHP-off:1 ext:0 auto:0

src R2.00-00, 2.0.0.1, nodal-SID 18002,0x4 PHP-off:1 ext:0 auto:0

L2 adv [10] native, propagated, nodal-SID 18002,0x4 PHP-off:1 ext:0 auto:0


RP/0/0/CPU0:R1#show cef 3.0.0.2

Tue Mar 12 04:57:31.456 PDT

3.0.0.2/32, version 213, internal 0x4004001 (ptr 0x577cd874) [1], 0x0 (0x57798878), 0x450 (0x57e8e050)

Updated Mar 12 03:46:45.041

local adjacency 12.0.0.2

Prefix Len 32, traffic index 0, precedence n/a, priority 1

via 12.0.0.2, GigabitEthernet0/0/0/0, 3 dependencies, weight 0, class 0 [flags 0x0]

path-idx 0 [0x57d3c280 0x0]

next hop 12.0.0.2

local adjacency

local label 18002 labels imposed {18002}

via 13.0.1.3, GigabitEthernet0/0/0/1, 2 dependencies, weight 0, class 0 [flags 0x0]

path-idx 1 [0x57d3c4a8 0x0]

next hop 13.0.1.3

local adjacency

local label 18002 labels imposed {18002}