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 BBCS - Service Overview Solution Architecture Protocol Stack IPSS - Swisscom’s MPLS/VPN Network VPN Architecture for BBCS Samples

BBCS - Service Overview

BBCS - Service Overview Speeds & 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)

BBCS - Service Overview User Perspective based on PPP Service Selection ISP X AAA (optional) Corporation Layer 2 Service Selection involves using a PPP client. This client can be integrated into the Microsoft dial-up networking client so that it appears as a familiar application to dial-up networking users. The user types in a username@servicename and a password and hits OK. This initiates the PPP session from the client which is examined at Network Access Server. The servicename is used to index into a profile which contains the information about what to do with the PPP session. Options may include forwarding the PPP session via a L2F or L2TP tunnel, or terminating the PPP session and using proxy Radius authentication for the user. If the user is successfully authenticated, the destination network assigns an IP address for that user. When the user wants to select another service, the PPP session must be torn down and re-initiated to the new destination. In some service provider architectures it is not desirable to tear down the session before selecting another. Tunnel PPP Client ISP Y SSG Extranet Cisco 6400 PPP

BBCS - Service Overview ISP 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 IPSS LNS ISP-A.ch LNS LAC L2TP tunnel PPP session

BBCS - Service Overview ISP Perspective - Session Balancing (Rel BBCS - Service Overview ISP 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“ Area TI session balancing POP - ZH IP - Network POP - BE (I)SP A BE LNS 3 Prio 1 „oneDomain.ch“ Area GE LNS 4 Area BE STE2 Prio 1 „oneDomain.ch“ End-Customer to backbone route LNS 5 Backbone to ISP session balancing Prio 1 „oneDomain.ch“

BBCS - Service Overview ISP Perspective - Session Balancing (Rel BBCS - Service Overview ISP 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“ Area TI session balancing POP - ZH IP - Network POP - BE 100 MBit (I)SP A BE LNS 3 Primary route Prio 1 „expensive.ch“ Area GE Secondary route LNS 4 Area BE STE2 Prio 1 „expensive.ch“ End-Customer to backbone route LNS 5 Backbone to ISP session balancing Prio 1 „expensive.ch“

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

Solution Architecture Topology Overview Layer 3 solution! (no E2E ATM PVCs)

Solution Architecture Cisco 6400 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 NSP A PEM A PEM B Air Exhaust (Rear) Air Intake (Front) NSP B NLC NRP

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

Protocol Stack Layered End-to-End Connectivity

Protocol Stack Traffic 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

Protocol Stack PPP Negotiation and Tunnel Establishment LAC LNS

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

IPSS - Swisscom’s MPLS/VPN Network Network Areas Core Edge Access Core Node Edge Node Access Node CPE After having explained the VPN principle, we are going to look a bit more into the network implementation. IPSS distinguishes 3 areas. The core area, the edge area and the access area. Each area has its own node types. Out of the access area is the customer premises with the CPE, the customer premises equipment. Now we are going to characterise the three areas.

IPSS - Swisscom’s MPLS/VPN Network Facts 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.

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

VPN Design Route colouring for Hub-and-Spoke VPN Connectivity

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

Samples Routing 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)

Samples Routing 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