# Presentation: 427974

## Current WAN Provisioning, Topology, Layer 2 Routing, Traffic Prioritization, and Failover

- NISN Quarterly Customer Videocon
- September 12, 2005
- Phillip Turner / Scott Henry

## Architecture

-    provides layer 2 transport for premium and standard routed
-    data services and Time Division Multiplex (TDM)
-   Layer 2 ATM Permanent Virtual Circuits (PVC)s provisioned
-    as virtual circuits on optical core
-  Core consists of OC-12s and OC-3s
-   DS3s at non core sites (MAF, DFRC, and Fairmont)
-   Wide Area Network (WAN) architecture is hub and spoke
-    topology.  ARC, MSFC, GSFC are hubs

- 09/12/05

## Architecture (Cont’d)

-     point using Constant Bit Rate (CBR)
-   Single Premium Internet Protocol (PIP) and Standard
-    Internet Protocol (SIP) PVCs are provisioned from each hub
-    site to each spoke site using non real time Variable Bit
-    Rate (VBR)

- 09/12/05

## Traffic Prioritization & Routing

-   Routing preference is configured for BPX to select best route
-    based on bandwidth availability
-  TDM assigned highest class of service (1) for routing
-   PIP assigned class of service (5 & 9) for routing
-   SIP assigned class of service (7 & 11) for routing
-   Under normal operating conditions, PVCs route via their
-     assigned trunk
-   Routing preference based on best route and modeling

- 09/12/05

## Traffic Re-routing During Failures

-   Traffic is re-routed during trunk failures based on bandwidth
-     availability and class of service (priority bumping)
-   One PIP PVC and one SIP PVC from each site will re-route
-     if bandwidth is available
-   If additional bandwidth is available after re-routing 1st PIP
-    and SIP PVC, additional PIP PVCs will re-route
-   Stub sites cannot re-route
-   Re-routing scenarios are simulated with modeling

- 09/12/05

## Provisioning

-   PVC types assigned NRT-VBR or CBR PVC
-   PVCs are assigned Peak Cell Rate (PCR), Sustained Cell
-    Rate (SCR), and Maximum Burst Size (MBS)
-   PCR allows burst to PCR value
-   SCR support provides a sustained rate
-   MBS defines the maximum number of ATM cells
-    supported per burst

- 09/12/05

## Optimization

-   PVCs modified during missions to accommodate increased
-    PIP and SIP requirements
-   Values adjusted as a result of ongoing changing requirements
-   IP accounting used to determine if packet loss occurs
-    requirement PVC increases
-   Notification of significant changes coordinated and changes
-    made by Enterprise Network Management Center (ENMC)

- 09/12/05

## Aggregate Per-Site Capacity & Trunks

- 09/12/05

## Current WAN Sustained Provisioning

- Note: VAFB provisioning included in JPL provisioning

- 09/12/05

## Aggregate Bandwidth Utilization

- Note: VAFB utilization included in JPL utilization percentage

- 09/12/05

## Bandwidth Requirements (Current/Projected) 

| Center/Facility | Aggregate Ingress | Aggregate Egress |
| --- | --- | --- |
| ARC | 516.3 Mbps | 444 Mbps |
| Boulder | 150.5 Mbps | 51.4 Mbps |
| DFRC | 48.1 Mbps | 45.1 Mbps |
| GRC | 88.6 Mbps | 56.4 Mbps |
| GSFC | 658.4 Mbps | 755 Mbps |
| HQ | 127.3 Mbps | 125.3 Mbps |
| JPL | 237.2 Mbps | 113.2 Mbps |
| JSC | 699.2 Mbps | 685.2 Mbps |
| KSC | 625.8 Mbps | 737.8 Mbps |
| LRC | 263.7 Mbps | 409.3 Mbps |
| MAF | 40.1 Mbps | 37.1 Mbps |
| MSFC | 1046.3 Mbps | 934.4 Mbps |
| SSC | 71.5 Mbps | 94.0 Mbps |
| WS | 83.5 Mbps | 96.8 Mbps |

**Current Provisioned Bandwidth on ATM Core**

| Center/Facility | Aggregate Ingress | Aggregate Egress |
| --- | --- | --- |
| ARC | 553.0 Mbps | 534.7 Mbps |
| Boulder | 149.9 Mbps | 46.3 Mbps |
| DFRC | 48.2 Mbps | 45.2 Mbps |
| GRC | 143.1 Mbps | 101.0 Mbps |
| GSFC | 1053.0 Mbps | 1153.3 Mbps |
| HQ | 148.7 Mbps | 138.8 Mbps |
| JPL | 241.3 Mbps | 142.8 Mbps |
| JSC | 850.4 Mbps | 900.9 Mbps |
| KSC | 685.2 Mbps | 786.9 Mbps |
| LRC | 306.1 Mbps | 280.4 Mbps |
| MAF | 33.6 Mbps | 35.2 Mbps |
| MSFC | 1135.8 Mbps | 1079.3 Mbps |
| SSC | 103.8 Mbps | 174.8 Mbps |
| WS | 258.4 Mbps | 191.2 Mbps |

**Current + Projected Bandwidth Requirements**

- 09/12/05

## Contacts

-  Kathy Hatley (NISN)
- _[Kathy.hatley@msfc.nasa.gov](mailto:Kathy.hatley@msfc.nasa.gov)_
- 	256-544-6571
-   Chris Knoell (UNITeS WAN Engineering)
- _[Chris.knoell@msfc.nasa.gov](mailto:Chris.knoell@msfc.nasa.gov)_
- 	256-961-9355
-   Scott Henry (UNITeS WAN Engineering)
- _[Scott.n.henry@msfc.nasa.gov](mailto:Scott.n.henry@msfc.nasa.gov)_
- 	256-961-9344

- 09/12/05