cd fy09 tactical plan review fy09 tactical plan for wide-area networking phil demar 9/25/2008

CD FY09 Tactical Plan Review

FY09 Tactical Plan forWide-Area Networking

Phil DeMar

9/25/2008

FY09 Tactical Plan for Wide Area Networking (doc #2876)

• Relevant Strategic Plan(s):

– Strategic Plan for Wide Area Networking (doc #2811)

– Strategic Plan for Data Movement & Storage (doc #2812)

– Strategic Plan for Scientific Facilities (doc #2788)

– Computing Division Strategic Plan (doc #2784)

• Tactical Plan Leader: Phil DeMar• Organizational Unit home: CD/SCF/DMS/WAN

CD FY09 Tactical Plan Review 2

FY09 Tactical Plan: Strategies

– Network designs or configurations will be kept as simple as requirements allow.

– Network infrastructure capacity will be kept well ahead of current & projected near term requirements.

– High capacity, high density network switch fabric will be deployed to the extent practicable.

– Network infrastructure will be maintained at the forward edge of established network technology

– Reliability of network infrastructure will be maximized. Redundancy will be the cornerstone of reliability.


– Operate the Laboratory’s off-site network facilities at the highest level of reliability & performance

– Enhance and maintain the CMS Tier-1 network

– Enhance & configure Laboratory’s wide-area network & MAN infrastructure

– Facilitate optimal network performance capabilities of the Laboratory wide area systems

– Upgrade the wide-area network infrastructure to meet needs of Laboratory experiments & collaborations

FY09 Tactical Plan: Goals

FY09 Tactical Plan: Goals (II)

– Evaluate, and deploy as appropriate new and advanced wide-area network technologies

– Engage in and publish research investigations

– Harden / complete the Lambda Station project

FY09 Tactical Plan: Objectives

– Facilitate reliable end-to-end data circuit service

– Develop and deploy advanced active & passive network monitoring capabilities over offsite data paths

– Enhance the reliability & monitoring of the MAN

– Upgrade the CMS Tier-1 network with very high performance central 10GE aggregation device

– Provide addtl 10GE offsite network path capabilities

– Upgrade offsite backup path to 10GE

– Initiate deployment of a 2nd offsite network hub in WH

– Deploy redundant supervisor on border routers


V = vital priorityH = high priorityM = medium priority

{H}

{H}

{V}

{H}

{V}

{V}

{V}

{V}

– Increase CMS Tier-1’s off-site bandwidth as needed

– Enhance structured performance analysis methodology

– Guide remote sites in improving data transfer rates

– Develop IPv6 test bed to production quality facility

– Deploy a 10GE network connection with ANL

– Connect to the Global Lambda Integrated Facility

– Participate in tests of network speeds beyond 10Gb/s

FY09 Tactical Plan: Objectives (II)V = highest priorityH = high priorityM = medium priority

{M}

{M}

{M}

{M}

{H}

{H}

{H}

– Refresh FAPL/Gridworks cluster with state-of-the-technology systems

– Develop network-based traffic analysis as initiator of dynamic circuits

– Design next-generation Lambda Station product

FY09 Tactical Plan: Objectives (III)V = highest priorityH = high priorityM = medium priority

{M}

{M}

{M}

FY09 Tactical Plan: Past Action Items

– Wide Area Networks initial review – Matt Crawford; Nov. 7, 2007• Re-evaluate budget cuts associated with storage disk space for flow analysis data

from border router.

» Resolved. Space provided on BlueARC• May need to re-visit the budget for making the backup border router to be fully

configured to match the primary border router

FY09 project– Wide Area Networks mid-year review– Phil DeMar; June 3, 2008

• 15.1: Andrey's effort - reporting against CMS-T1 but not actually getting charged as expected to CMS-T1. Jon and Phil agree this is a problem, needs to be resolved with Mike Smith.

Resolved. New activity for charge-back being set up

• 15.2: WAN Operations, Support, & Maintenance erroneously listed under Site Networking. Mike Smith knows about and will fix

Fixed


Service: Advanced WAN Infrastructure


• Offsite configurations & infrastructure enhancements for WAN data movement

• Goals:

1. Facilitate reliable end-to-end (E2E) data circuit service• Ongoing goal – highest priority

2. Deploy perfSonar-based E2E active monitoring capabilities• New goal – high priority

• Key Metrics:

1. Aggregate off-site bandwidth capacity

2. # of E2E circuits, their uptime & utilization – need to develop E2E monitoring capabilities

3. # of PerfSonar-monitored remote sites• Milestones:

1. Active PerfSonar monitoring to all Tier-2 sites - April ‘09

Service: Network / Performance Improvement


• Support for optimization of offsite data movement

• Goals:

1. Enhance structured performance methodology• Ongoing goal – high priority

2. Coordinate & assist remote sites in improving data transfer rates• Ongoing goal – high priority

• Key Metrics:– Quantified performance improvements for CMS Tier-2 & Tier-3 sites

• Milestones:– Incorporation of content management capability in methodology - April ‘09

Services: (1) Network Operational Support & Maint. (2) Network Operations / MAN


• (1) Operation & support of WAN network infrastructure

• (2) Operation & support of Chicago MAN

• Goals:

1. Facilitate very high performance, highly reliable WAN network service• Ongoing goal – highest priority

2. Provide expeditious troubleshooting support for WAN-related network problems

• Ongoing goal – highest priority

3. Enhance reliability & monitoring capabilities of Chicago MAN• Ongoing goal – high priority

• Key Metrics:

1. Uptime of perimeter routers

2. MAN channel uptime• Milestones:

---

Service: Network-CMS-WAN


• Planning, deployment, & support of CMS Tier-1 network infrastructure

• Goals:

1. Upgrade the Tier-1 infrastructure to be based on a very high performance 10GE aggregation device

• New goal – highest priority

2. Increase CMS onsite & offsite bandwidth capacity to meet the Tier-1’s needs

• Ongoing goal – high priority

• Key Metrics:– Uptime of CMS Tier-1 network devices– Measured data traffic levels, internal & offsite

• Milestones:– Upgrade of CMS Tier-1 network to new core device - September ‘09

Project: Network Upgrades


• Testing & deployment of advanced network technologies• Goals:

1. Upgrade backup offsite path to 10GE• Ongoing goal – highest priority

2. Develop 2nd offsite hub in WH• New goal – high priority

3. Deploy redundant supervisors on border & E2E circuit routers• New goal – high priority

4. Additional 10GE offsite channel capacity, as needed• Ongoing goal – high priority

• Key Milestones:

1. Backup border router upgraded with new supervisor – Nov ‘09

2. 2nd Ciena hub deployed in WH - July ‘09

3. Border & E2E routers upgraded with BXL supervisors – Feb ‘09

• Issues and Risks: 1. Could be delayed, but would seriously impact long term strategic directions

Project: Network Investigations


• Testing & deployment of advanced network technologies• Goals:

1. Develop production-quality IPv6 network test bed• Ongoing goal – medium priority

2. Deploy 10GE network connection to ANL• New goal – medium priority

3. Connect R&D test network to Global Lambda Integrated Facility• Ongoing goal – medium priority

4. Participate in wide-area network technologies beyond 10GE• New goal – medium priority

• Key Milestones:

1. Full-function IPv6 test bed with DHCPv6 - July ‘09

2. 10GE connection between FNAL & ANL R&D LANs - Sept. ’09

3. Attachment to GLIF GOLE – Dec. ’08

• Issues and Risks: 1. Could be delayed, but would impact long term strategic directions

Project: (1) SciDAC Lambda Station (2) Lambda Station FTWatch


• (1) Alternate wide-area network path selection service• (2) Flow-based traffic analysis initiator of Lambda Station services• Goals:

1. Hardened Lambda Station distribution package w/ config tools• Ongoing goal – high priority

2. Develop generic flow record analysis algorithms for FTWatch• New goal – medium priority

3. Design next-generation Lambda Station product• New goal – medium priority

• Key Milestones:

1. Complete Lambda Station project - Early-as-possible ’09

• Issues and Risks: 1. Scripting help (PERL) needed to help finish project2. Funding spend-down for Lambda Station proving to be difficult 3. Ongoing support effort also a concern


FY09 Resource Request, Preliminary Allocation

Level 0 Activity: Wide-Area Networking

• Medium priority projects would be first to be scaled back or deferred– Largely effort expenditures; would try for some forward progress

– 100GE test bed & IPv6 initiatives have R&E leadership aspects

• Network upgrades could also be deferred– Would impact strategic direction on reliability & resilience

– Backup 10GE path already delayed one year and overdue

• Lambda Station effort will end this FY– Can not be deferred, only stopped

• High priority WAN & CMS Tier-1 services remain essential– Must receive required effort, at expense of projects, upgrades, &

technology investigations

Impact of Partial Allocation

cd fy09 tactical plan review fy09 tactical plan for wide-area networking phil demar 9/25/2008

Documents

gbs fy09 tactical plan

tactical plan leader

offsite network hub

ge network connection

high priority

tests of network speeds

strategies network designs

wide area networking