1 / 28

Riptide 4.0 Architecture

Riptide 4.0 Architecture. K. Kollmansberger. Solution Architecture. 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

platt
Download Presentation

Riptide 4.0 Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Riptide 4.0Architecture K. Kollmansberger

  2. Solution Architecture • 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

  3. Architecture Status • 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

  4. Agenda • Network/Lab Overview • Source Diversity • Path Diversity • Path Resiliency • QoS Design • IPmc Addressing Example

  5. Network/Lab Overview

  6. Complete Network Overview Optional N-HE1 Optional N-HE2 IRT - Decrypt Encrypt IRT - Decrypt Encrypt RTE - Decrypt Encrypt Current Backbone = Satellite Future Backbone = IP Core RTE - Decrypt Encrypt Mux Mux RTN - ARs R-HE1 R-HE2 R-HE3 VoD MuxAd-splice Groom VoD MuxAd-splice Groom Mux Ad-splice Groom VoD VoD VoD VoD Encrypt Encrypt Encrypt Hub Hub Hub Hub Hub Hub DAN - HRs DAN - HRs DAN - HRs Hub Hub Hub QAM QAM QAM SDV Server SDV Server SDV Server QAM QAM QAM QAM QAM QAM QAM QAM QAM HFC HFC HFC

  7. Focused Network Overview – E2E RTN - ARs R-HE1 R-HE2 R-HE3 VoD MuxAd-splice Groom VoD MuxAd-splice Groom Mux Ad-splice Groom VoD VoD VoD VoD Encrypt Encrypt Encrypt Hub Hub Hub Hub Hub Hub DAN - HRs DAN - HRs DAN - HRs Hub Hub Hub QAM QAM QAM SDV Server SDV Server SDV Server QAM QAM QAM QAM QAM QAM QAM QAM QAM HFC HFC HFC

  8. RT 4.0 Lab Overview

  9. Source Diversity

  10. Stat-Mux Stat-Mux Ad-splicer Ad-splicer Source Diversity – Primary/Secondary HE • 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 RTN R-HE1 R-HE2 TED TED DNCS DNCS App Srv SDV Srv App Srv SDV Srv BFS BFS VoD VoD VoD VoD VoD VoD Encrypt Encrypt VoD VoD IRT REC IRT REC RTE RTE RTE RTE QAM QAM

  11. Path Diversity

  12. 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 SubInt 1 = SDV/DS/DB SubInt 2 = Default R-HE1 R-HE2 10Gb Ring – 2 subinterfces DAN DAN 10GE/NxGE P2P = VoD 10GE/NxGE P2P = VoD SubInt 1 = SDV/DS/DB SubInt 2 = Default SDV Srv DAN QAM QAM QAM Hub QAM

  13. 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) redistribute connected subnet route-map Local_Netcrypts 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 AR1a Config High OSPF Weight High OSPF Weight RTN AR1b AR1a S1,G1 S2,G1 R-HE1 DAN HR2a HR2b Hub

  14. The 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) 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) redistribute ospf 100 subnet route-map Remote_Netcrypts 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 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 AR1b Config High OSPF Weight High OSPF Weight RTN AR1b AR1a S1,G1 S2,G1 R-HE1 DAN HR2a HR2b Hub • Config differences between AR1a and AR1b are highlighted • AR1a advertises local sources • AR1b advertises remote sources

  15. The HR2a/HR2b configuration would look similar to this: 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_QAM router ospf 103 (DAN VoD process) network x.x.x.x x.x.x.x area 0 (DAN VoD mini-ring interfaces) 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) HR2a/HR2b Config SDV Srv QAM QAM QAM Hub QAM

  16. Concentric Ring Design RTN AR1b AR1a Default R-HE1 HR3a HR3b DAN HR1a HR1b SubInt 2 = Default SubInt 2 = Default HR2a HR2b SubInt 1 = SDV/DS/DB SubInt 1 = SDV/DS/DB Hub

  17. Concentric Ring Design w/Subtended Rings RTN HE1 HE2 HE3 DAN 10GE/NxGE P2P = VoD SubInt 2 = Default SubInt 2 = Default SubInt 1 = SDV/DS/DB SubInt 1 = SDV/DS/DB SubInt 1 = SDV/DS/DB SubInt 2 = Default DAN

  18. Path Resiliency

  19. 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

  20. QoS Design

  21. QoS Configuration

  22. 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)

  23. Modified 7600 Example AR1a-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

  24. IPmc Addressing Example

  25. 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 mapping • 25 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

  26. 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

  27. IPmc Addressing Example

More Related