riptide 4.0 architecture

1© 2005 Cisco Systems, Inc. All rights reserved.Session NumberPresentation_ID Cisco Confidential

Riptide 4.0Architecture

K. Kollmansberger


• Solution focuses on an end2end solution for video over IP• Added the SFA SDV solution, CRS-1, and 4948 components

• Regional Headends receive content from Satellite and Off-Air antennas

• Rather than building multiple HEs per region, remote R-HEs can provide redundant/backup sources for any DAN

• VoD and SDV/DS/DB traffic are routed through 7600s onto separate interfaces

• Maintained in separate routing instances

• SDV/DS/DB shares physical interfaces with VoIP and HSD• Maintained in separate routing instances and separate logical

interfaces on the ring

Solution Architecture


• The focus of the SAS is on SDV, VoD, and DS/DB over IP

• Specifically SFA SDV solution

• Introduces the CRS and 4948

• SAS covers the following aspects

• Network design for SDV, VoD, and DS/DB over IP

• Source Diversity for centralized ad-insertion

• Path Diversity via static mroutes and multiple OSPF instances

• Path Resiliency via redundant Sups/RPs, PortChannel/ECMP (VoD), IGP-FC/PIM-FC

• Recommended QoS configuration

• IPmc addressing design example

Architecture Status


Agenda

• Network/Lab Overview

• Source Diversity

• Path Diversity

• Path Resiliency

• QoS Design

• IPmc Addressing Example


Network/Lab Overview


RTE - Decrypt

EncryptIRT -

DecryptEncrypt

Optional N-HE1

RTE - Decrypt

EncryptIRT -

DecryptEncrypt

Optional N-HE2

Mux Mux

Current Backbone = Satellite

Future Backbone = IP Core

RTN - ARs

Radio TowerRadio Tower Radio Tower

MuxAd-splice Groom

MuxAd-splice Groom

Mux Ad-splice

Groom

Encrypt EncryptEncrypt

R-HE1 R-HE2 R-HE3

DAN - HRs

DAN - HRs

DAN - HRs

VoD VoD VoDVoD VoD VoD

Hub Hub Hub Hub Hub Hub

SDV Server

QAMQAMQAMQAM

QAMQAMQAMQAM

QAMQAMQAMQAM

HFC HFC HFC

Hub Hub Hub

SDV Server

SDV Server

Complete Network Overview


Focused Network Overview – E2E

RTN - ARs

Radio TowerRadio Tower Radio Tower

MuxAd-splice Groom

MuxAd-splice Groom

Mux Ad-splice

Groom

Encrypt EncryptEncrypt

R-HE1 R-HE2 R-HE3

DAN - HRs

DAN - HRs

DAN - HRs

VoD VoD VoDVoD VoD VoD

Hub Hub Hub Hub Hub Hub

SDV Server

QAMQAMQAMQAM

QAMQAMQAMQAM

QAMQAMQAMQAM

HFC HFC HFC

Hub Hub Hub

SDV Server

SDV Server


RT 4.0 Lab Overview


Source Diversity


Source Diversity – Primary/Secondary HE

DNCSTED

BFS

App Srv

SDV Srv

Encrypt

RTE RTEIRT REC

Radio Tower

R-HE1 R-HE2DNCSTED

BFS

App Srv

SDV Srv

Encrypt

RTE RTEIRT REC

Radio Tower

RTN

VoDVoD

VoDVoD

VoDVoD

VoDVoD

Stat-Mux

Ad-splicer

Stat-Mux

Ad-splicer

• For Source Diversity, multiple HEs are needed

• No need to create duplicate HEs per Region/Division

• Can use remote R-HE for backup source

• RTN is network which provides interconnectivity between HEs/Regions

• CRS-1 and 7600 focus

QAM QAM


Path Diversity


Path Diversity – Single and Subtended Rings

RTN• DAN is the network which provides interconnectivity between Hubs and the R-HE

• Path Diversity is needed to “separate” VoD traffic from SDV/DS/DB traffic from all other (default) traffic

• Separate IGP instances

• One instance for VoD

• Once instance for SDV/DS/DB

• Once instance for all other services (HSD/Business Services/etc.)

• Separate physical interfaces due to different failure requirements

• VoD and all other traffic

• Separate logical interfaces due to different forwarding requirements

• SDV/DS/DB vs VoIP/HSD/Business

• CRS, 7600, 4500, and 4948 focus

10GE/NxGE P2P = VoD

10GE/NxGE P2P = VoD

10Gb Ring – 2 subinterfces

DAN DAN

DAN

Hub

R-HE1 R-HE2

QAMQAM

SDV Srv

SubInt 1 = SDV/DS/DB


QAMQAM

SubInt 2 = Default

SubInt 2 = Default


AR1a Config

The AR1a configuration would look similar to this:router ospf 100 (RTN process)

network x.x.x.x x.x.x.x area 0 (RTN interfaces)

redistribute connected subnet route-map Local_Netcrypts

router ospf 101 (DAN Broadcast process)

network x.x.x.x x.x.x.x area 0 (DAN Broadcast ring interfaces)


router ospf 102 (DAN Default process)

network x.x.x.x x.x.x.x area 0 (DAN Default ring interfaces)

redistribute connected subnet route-map No_Broadcast

router ospf 103 (DAN VoD process)

network x.x.x.x x.x.x.x area 0 (DAN VoD mini-ring interfaces)

route-map Local_Netcrypts permit 10

match ip address 1

route-map No_Broadcast deny 10

match ip address 1

route-map No_Broadcast permit 20

access-list 1 permit x.x.x.x x.x.x.x (local Netcrypt subnet)

int te0/0.1

desc Broadcast ring inter-AR interface

ip ospf cost 100

int te1/1

desc VoD mini-ring inter-AR interface

ip ospf cost 100

DAN

R-HE1

Hub

RTN

AR1a AR1b

HR2bHR2a

S1,G1 S2,G1

High OSPF Weight

High OSPF Weight


AR1b ConfigThe AR1b configuration would look similar to this:

router ospf 100 (RTN process)

network x.x.x.x x.x.x.x area 0 (RTN interfaces)


router ospf 101 (DAN Broadcast process)


redistribute ospf 100 subnet route-map Remote_Netcrypts



redistribute connected subnet route-map No_Broadcast



route-map Local_Netcrypts permit 10

match ip address 1

route-map Remote_Netcrypts permit 10

match ip address 2

route-map No_Broadcast deny 10

match ip address 1

route-map No_Broadcast permit 20

access-list 1 permit x.x.x.x x.x.x.x (local Netcrypt subnet)

access-list 2 permit x.x.x.x x.x.x.x (secondary/remote Netcrypt subnet)

int te0/0.1

desc Broadcast ring inter-AR interface

ip ospf cost 100

int te1/1

desc VoD mini-ring inter-AR interface

ip ospf cost 100

DAN

R-HE1

Hub

RTN

AR1a AR1b

HR2bHR2a

• Config differences between AR1a and AR1b are highlighted

• AR1a advertises local sources

• AR1b advertises remote sources

S1,G1 S2,G1

High OSPF Weight

High OSPF Weight


HR2a/HR2b Config

The HR2a/HR2b configuration would look similar to this:router ospf 101 (DAN Broadcast process)




redistribute connected subnet route-map No_QAM



redistribute connected subnet route-map Edge_QAM

route-map No_QAM deny 10

match ip address 1

route-map No_QAM permit 20

route-map Edge_QAM permit 10

match ip address 1

access-list 1 permit x.x.x.x x.x.x.x (local QAM data interface subnet)

Hub

QAMQAM

SDV Srv

QAMQAM


Default

RTN

DAN

R-HE1

SubInt 2 = Default

SubInt 1 = SDV/DS/DBSubInt 1 =

SDV/DS/DB

SubInt 2 = Default

Hub

AR1a AR1b

HR2bHR2a

HR3a HR3b HR1a HR1b

Concentric Ring Design


10GE/NxGE P2P = VoD

RTN

DAN

HE1 HE2 HE3

DAN

SubInt 2 = Default



SubInt 2 = Default


SubInt 2 = Default

Concentric Ring Design w/Subtended Rings


Path Resiliency


Path Resiliency

Enhancements to the “forwarding path” including:

• Supervisor/Route Processor redundancy

• Failover from primary Sup/RP to backup Sup/RP

• EtherChannel port groups

• Load-balancing across multiple L2 ports bundled into a single forwarding instance

• Equal-Cost Multi-Path

• Load-balancing across multiple L3 interfaces between routing peers

• IGP-FC

• Tuning the IGP (e.g. OSPF) to support sub-second convergence

• PIM tuning

• To decrease recovery time/increase service availability


QoS Design


QoS ConfigurationTraffic Type DSCP Marking CoS/Queue Assignment Queue Management

IP Routing CS60b110000

6/8 (6/4 on 4500) Priority/Tail-drop

Interactive Voice EF0b101110

5/8 (5/4 on 4500) Priority/Tail-drop

Streaming Video(SDV/DS/DB/Ad Distribution)

AF410b100010

4/3 Tail-drop

Video/Voice Signaling CS30b011000

4/3 Tail-drop

Interactive video(VoD – High)

AF420b100100

4/3 Tail-drop

Interactive video(VoD – Low)

AF430b100110

3/3 Tail-drop

Network Management CS20b010000

2/2 WRED

Business (CIR) AF210b010010

1/2 WRED

Gaming CS50b101000

7/1 WRED

Business (cB) AF110b001010

7/1 WRED

Data(Internet Access)

CS10b001000

7/1 WRED

Business (eB) AF130b001110

0/1 WRED

Scavenger BE0b001010

0/1 WRED

Suspect BE0b001000

0/1 WRED


Queue Assignment/CoS

Queue assignment

• Priority = 5,6 : Taildrop(5=Voice Bearer, 6=Routing)

• Queue3 = 4,3 : TailDrop : 100% CoS4, 70% CoS3(4=SDV/DS/DB or ½ VoD & Service Control, 3 =½ VoD)

• Queue2 = 2,1 : WRED : 75/100% CoS2, 50/100% CoS1 (2=NMS, 1=Business CIR)

• Queue1 = 7,0 : WRED : 75/100% CoS7, 50/75% CoS0(7=Gaming/Business cB/Internet Data, 0=Business eB/Scavenger/Suspect)


Modified 7600 ExampleAR1a-7600#sh queueing interface tenGigabitEthernet 5/1

<deleted>Queueing Mode In Tx direction: mode-cos

<deleted>WRR bandwidth ratios: 100[queue 1] 150[queue 2] 200[queue 3] 0[queue 4] 0[queue 5] 0[queue 6] 0[queue 7]queue-limit ratios: 50[queue 1] 20[queue 2] 15[queue 3] 0[queue 4] 0[queue 5] 0[queue 6] 0[queue 7]

<deleted>queue tail-drop-thresholds--------------------------3 100[1] 70[2] 1[3] 1[4] 1[5] 1[6] 1[7] 1[8]

<deleted>queue random-detect-min-thresholds----------------------------------2 75[1] 50[2] 1[3] 1[4] 1[5] 1[6] 1[7] 1[8]1 75[1] 50[2] 1[3] 1[4] 1[5] 1[6] 1[7] 1[8]

<deleted>queue random-detect-max-thresholds----------------------------------2 100[1] 100[2] 1[3] 1[4] 1[5] 1[6] 1[7] 1[8]1 100[1] 75[2] 1[3] 1[4] 1[5] 1[6] 1[7] 1[8]

<deleted>WRED disabled queues: 4 5 6 7

<deleted>queue thresh cos-map--------------------------------------- 1 1 7 1 2 0 2 1 2 2 2 1 3 1 4 3 2 3 8 1 5 6


IPmc Addressing Example


IPmc Addressing Design

11101111.10000000.00000000.00000000• Bits 1-4 are reserved for Class D assignment (1110)

• Bits 5-9 are lost in the 23-bit MAC to 32-bit IP mapping25 bits of MAC address reserved (Organizationally Unique Identifier : OUI+1) by RFC1112

Which leaves 23-bits for unique IPmc group assignment to allow unique MAC addresses (remaining 0s above)

Because of the high order bit in the 2nd octet being “reserved”, there is an IPmc group overlap with a single IPmc MAC address

224.0.0.0, 224.128.0.0, 225.0.0.0, 225.128.0.0, …, 239.0.0.0, 239.128.0.0

Recommend using a single 1st octet (239) and the address ranges in the 2nd octet supported by a ONE in the first bit (128 to 255)

Two different values can be used in the 1st octet (e.g. 239 & 232) if the address plan defined in the next slide is used; e.g. bit 10 used to distinguish between ASM and SSM

The 1st octet is identified as the Source-Block in this design

http://www.cisco.com/warp/public/732/Tech/multicast/docs/addressallocation.pdf


IPmc Addressing Design

11101111.10000000.00000000.00000000

• Bit 10 used for Class designation; either:

ASM (0) / SSM (1), or

External-AS (0) / Internal-AS (1)

• Bits 11-16 used for Region designation

• Bits 17-21 used for Service-Zone designation

Service Zone 0 is reserved for Class0/Region0 due to:

224.0.0.0-224.0.0.255 (224.0.0/24) Local Network Control Block

224.0.1.0-224.0.1.255 (224.0.1/24) Internetwork Control Block

• Bits 22-32 used for Service designation

MPTS channel groups or SPTS channels


IPmc Addressing ExampleFirst Octet Second Octet Third Octet Fourth Octet

Source BlockClass 0

Region 128-191 Service Zone Program Number

Internal GLOB Start End Start Start End Start End

239 233 128 191 0 0 0 255 0 255

239 233 128 191 0 1 256 511 0 255

239 233 128 191 0 2 512 767 0 255

239 233 128 191 0 3 768 1023 0 255

239 233 128 191 0 4 1024 1279 0 255

239 233 128 191 0 5 1280 1535 0 255

239 233 128 191 0 6 1536 1791 0 255

239 233 128 191 0 7 1792 2047 0 255

239 233 128 191 1 8 0 255 0 255

239 233 128 191 1 9 256 511 0 255

239 233 128 191 1 10 512 767 0 255

239 233 128 191 1 11 768 1023 0 255

239 233 128 191 1 12 1024 1279 0 255

239 233 128 191 1 13 1280 1535 0 255

239 233 128 191 1 14 1536 1791 0 255

239 233 128 191 1 15 1792 2047 0 255

239 233 128 191 2 16 0 255 0 255

239 233 128 191 2 17 256 511 0 255

239 233 128 191 2 18 512 767 0 255

239 233 128 191 2 19 768 1023 0 255

239 233 128 191 2 20 1024 1279 0 255

239 233 128 191 2 21 1280 1535 0 255

239 233 128 191 2 22 1536 1791 0 255

239 233 128 191 2 23 1792 2047 0 255

riptide 4.0 architecture

Documents