1 / 25

Broadband Connectivity Services (BBCS) An Engineering Perspective

Broadband Connectivity Services (BBCS) An Engineering Perspective. Rasti Slosiar, Swisscom-Fixnet AG Head of IP Service Integration. Agenda. BBCS - Service Overview Solution Architecture Protocol Stack IPSS - Swisscom’s MPLS/VPN Network VPN Architecture for BBCS Samples. Agenda.

psharon
Télécharger la présentation

Broadband Connectivity Services (BBCS) An Engineering Perspective

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. Broadband Connectivity Services(BBCS)An Engineering Perspective Rasti Slosiar, Swisscom-Fixnet AG Head of IP Service Integration

  2. Agenda • BBCS - Service Overview • Solution Architecture • Protocol Stack • IPSS - Swisscom’s MPLS/VPN Network • VPN Architecture for BBCS • Samples

  3. Agenda • BBCS - Service Overview • Solution Architecture • Protocol Stack • IPSS - Swisscom’s MPLS/VPN Network • VPN Architecture for BBCS • Samples

  4. BBCS - Service Overview

  5. BBCS - Service OverviewSpeeds & Customer relationships • Today: • 64 kbps up 256 kbps down • 128 kbps up, 512 kbps down • Tomorrow (01.11.2001 pilot phase 1.5 months) • 256 kbps up, 1.024 Mbps down • 352 kbps up, 2.048 Mbps down • ISP owns end-customer: • ISP sales channel • ISP to provide starter kit • ISP to provide customer care • Swisscom owns ISP customer (wholesale model)

  6. AAA (optional) Extranet BBCS - Service Overview User Perspective based on PPP Service Selection ISP X Corporation Tunnel PPP Client ISP Y SSG Cisco 6400 PPP

  7. IPSS BBCS - Service OverviewISP Perspective - L2TP Tunnel Selection • L2TP tunnel is built based on structured username, PPP session “user@isp-a.ch” is multiplexed into L2TP tunnel towards LNS ISP-A.ch ISP-B.ch LNS ISP-A.ch LNS LAC L2TP tunnel PPP session

  8. Area TI BBCS - Service OverviewISP Perspective - Session Balancing (Rel. 3 Basic) Max 1 domain Max 8 LNSes 1 set of rules nationwide (I)SP A Area LU ZH LNS 1 LAC - LU Prio 1 „oneDomain.ch“ Area ZH LNS 2 STE1 Prio 1 „oneDomain.ch“ session balancing POP - ZH IP - Network POP - BE (I)SP A LNS 3 BE Prio 1 „oneDomain.ch“ Area GE LNS 4 STE2 Area BE Prio 1 „oneDomain.ch“ End-Customer to backbone route LNS 5 Backbone to ISP Prio 1 „oneDomain.ch“ session balancing

  9. Area TI BBCS - Service OverviewISP Perspective - Session Balancing (Rel. 3 Premium) Max 3 domains Max 2 priorities/domain Max 8 LNS/domain 1 set of rules nationwide (I)SP A Area LU ZH LNS 1 LAC - LU Prio 1 „cheap.ch“ Area ZH 20 MBit LNS 2 STE1 Prio 1 „cheap.ch“ Prio 2 „expensive.ch“ session balancing POP - ZH IP - Network POP - BE 100 MBit (I)SP A LNS 3 BE Primary route Prio 1 „expensive.ch“ Area GE Secondary route LNS 4 STE2 Area BE Prio 1 „expensive.ch“ End-Customer to backbone route LNS 5 Backbone to ISP Prio 1 „expensive.ch“ session balancing

  10. Agenda • BBCS - Service Overview • Solution Architecture • Protocol Stack • IPSS - Swisscom’s MPLS/VPN Network • VPN Architecture for BBCS • Samples

  11. Solution ArchitectureTopology Overview Layer 3 solution! (no E2E ATM PVCs)

  12. Node switch processor (NSP) 5 Gbps ATM switch and system processor 32K VCCs Node route processor (NRP) 7200 NPE-200 class router 155 Mbps backplane connector NRP2 Dual 7200 NPE-300 class router 622 Mbps backplane connector Node line card (NLC) STM-1, DS-3, and STM-4 ATM Air Exhaust (Rear) NLC NLC NLC NLC NLC NLC NLC NLC PEM A NSP B NSP A NRP NRP NRP NRP NRP NRP NRP NRP NRP PEM B NLC NLC NLC NLC NLC NLC NLC NLC Air Intake (Front) Solution ArchitectureCisco 6400

  13. Agenda • BBCS - Service Overview • Solution Architecture • Protocol Stack • IPSS - Swisscom’s MPLS/VPN Network • VPN Architecture for BBCS • Samples

  14. Protocol StackLayered End-to-End Connectivity

  15. Protocol StackTraffic Carried • Swisscom-Fixnet carries: • PPPoX traffic in the access • L2TP Traffic in the edge and core • Swisscom-Fixnet IP Connectivity for BBCS: • No IP connectivity in Access (PPPoX frames bridged in modem), only “PPPoE” connectivity to select domain • IP Connectivity between LAC NRP Loopbacks and LNS Loopbacks from each ISP (L2TP tunnel endpoints) • Used to establish L2TP tunnel, no other visibility • PC to ISP connectivity via IP within PPP

  16. Protocol StackPPP Negotiation and Tunnel Establishment LAC LNS

  17. Agenda • BBCS - Service Overview • Solution Architecture • Protocol Stack • IPSS - Swisscom’s MPLS/VPN Network • VPN Architecture for BBCS • Samples

  18. Access Access Edge Edge Core Core Core Node Edge Node Access Node CPE IPSS - Swisscom’s MPLS/VPN NetworkNetwork Areas

  19. IPSS - Swisscom’s MPLS/VPN NetworkFacts • Cisco based edge and core • Edge implements Multiprotocol BGP (VPN “Intelligence”) • Alcatel based DSLAM • Some numbers: • 35 edge and core locations • Currently STM-16 2.4 Gbit/s core trunks • 900 DSLAMs • Services supported by IPSS • BBCS • LAN Interconnect • Corporate Network • etc.

  20. Agenda • BBCS - Service Overview • Solution Architecture • Protocol Stack • IPSS - Swisscom’s MPLS/VPN Network • VPN Architecture for BBCS • Samples

  21. VPN DesignRoute colouring for Hub-and-Spoke VPN Connectivity

  22. Agenda • BBCS - Service Overview • Solution Architecture • Protocol Stack • IPSS - Swisscom’s MPLS/VPN Network • VPN Architecture for BBCS • Samples

  23. SamplesRouting Table at Hub CE (NRP) ipc-zhb790-r-lc-01>show ip route ... Gateway of last resort is not set 138.187.0.0/16 is variably subnetted, x subnets, 2 masks B 138.187.22.33/32 [20/0] via 172.16.1.2, 14:32:34 B 138.187.22.42/32 [20/0] via 172.16.1.2, 14:32:34 B 138.187.22.41/32 [20/0] via 172.16.1.2, 14:32:34 B 138.187.22.49/32 [20/0] via 172.16.1.2, 14:32:34 B 138.187.22.57/32 [20/0] via 172.16.1.2, 14:32:34 B 138.187.22.3/32 [20/0] via 172.16.1.2, 14:33:02 B 138.187.22.2/32 [20/0] via 172.16.1.2, 14:33:02 … 216.125.11.0/32 is subnetted, 2 subnets B 216.125.11.244 [20/0] via 172.16.1.2, 14:35:44 B 216.125.11.245 [20/0] via 172.16.1.2, 14:35:44 202.243.130.0/32 is subnetted, 1 subnets B 202.243.130.120 [20/0] via 172.16.1.2, 14:35:44 205.104.103.0/32 is subnetted, 1 subnets B 205.104.103.2 [20/0] via 172.16.1.2, 14:35:44 202.190.192.0/32 is subnetted, 1 subnets B 202.190.192.131 [20/0] via 172.16.1.2, 14:35:44 207.21.32.0/32 is subnetted, 1 subnets B 207.21.32.113 [20/0] via 172.16.1.2, 14:35:44 … NRPs (Hubs) LNS Loopbacks (Spokes)

  24. SamplesRouting Table at Spoke CE (connects to ISP LNS) ip-efg-ch-abc-r-01>show ip route ... Gateway of last resort is not set 205.104.100.0/30 is subnetted, 1 subnets C 205.104.100.60 is directly connected, FastEthernet1/0 138.187.0.0/16 is variably subnetted, x subnets, 2 masks B 138.187.22.33/32 [20/0] via 172.16.19.2, 14:47:49 B 138.187.22.42/32 [20/0] via 172.16.19.2, 14:53:38 B 138.187.22.41/32 [20/0] via 172.16.19.2, 14:53:39 B 138.187.22.49/32 [20/0] via 172.16.19.2, 15:12:11 B 138.187.22.57/32 [20/0] via 172.16.19.2, 15:03:07 B 138.187.22.3/32 [20/0] via 172.16.19.2, 14:41:52 B 138.187.22.2/32 [20/0] via 172.16.19.2, 14:41:52 … 205.104.103.0/32 is subnetted, 1 subnets S 205.104.103.2 [1/0] via 205.104.100.61 … Interface to LNS NRPs (Hubs) ONLY ROUTES! Static Route to LNS

More Related