Transcript Effectively Managing IPv6 Transition

Effectively and Efficiently
Managing the Transition
to IPv6
Date: 05/08/06 Version 1.0
IPv6 Transition Agenda
Effectively and Efficiently Managing the Transition to IPv6
• OMB Memorandum, Support & Guidance
• Network Architecture Definitions & Models
• The NASA IPv6 Transition Approach
• The 4 Phases of NASA’s IPv6 Transition project
• Project Formulation & Approval (Phases 1 & 2)
Requirements Gathering & Workflow Analysis
• Phase 3 – Architecture and Design
• Phase 4 - Implementation, Test & Acceptance
• IPv6 Challenges
1
OMB Memorandum 05-22 Instruction
to Agencies
[ Please read the notes section for more detail ]
Effectively and Efficiently Managing the Transition to IPv6
By November 15, 2005
 Identify an IPv6 agency lead
 Complete 1st inventory of IP-aware hardware devices in network
backbone
By February 28, 2006
 Develop a network backbone transition plan for IPv6
 Complete an IPv6 progress report
By June 30, 2006
 Complete 2nd inventory of IP-aware applications and peripherals with
dependencies on network backbone
 Complete an IPv6 transition impact analysis
By June 30, 2008
 Complete network backbone transition to IPv6
2
Available Support to Agencies
for IPv6 Transition
[ Please read the notes section for more detail ]
Effectively and Efficiently Managing the Transition to IPv6

Transition Planning Guidance

Core.gov portal and collaboration space

Address-space acquisition training

Standards/guidelines development

Acquisition guidance
3
[ Please read the notes section for more detail ]
Currently Published IPv6 Guidance
Effectively and Efficiently Managing the Transition to IPv6
Chapter I – Integrating IPv6 into EA
Planning Activities (released)
Chapter II – Developing an IPv6 Transition
Plan (released)
Chapter III – Governance (released)
Chapter IV – Acquisition/Procurement
4
Definitions- LAN/MAN/WAN Model
Wikipedia
Effectively and Efficiently Managing the Transition to IPv6
LAN:
 A Local Area Network (LAN) is a computer network covering a small local
area, like a home, office, or small group of buildings such as a home,
office, or college.
MAN:
 Metropolitan Area Networks (MAN) are large computer networks usually
spanning a campus or a city. They typically use wireless infrastructure or
optical fiber connections to link their sites. For example, a university or
college may have a MAN that joins together many of their LANs. They
could have several WAN links to other universities or the Internet.
WAN:
 A wide area network or WAN is a computer network covering a wide
geographical area, involving a vast array of computers. This is different
from personal area networks, MANs, or LANs that are usually limited to a
room, building or campus.
5
LAN/MAN/WAN Diagram
Network Analysis, Architecture and Design, James D. McCabe
Effectively and Efficiently Managing the Transition to IPv6
WAN
MAN
MAN
LAN
LAN
6
LAN
Definitions- Access/Distribution/Core Model
Network Analysis, Architecture and Design, James D. McCabe
Effectively and Efficiently Managing the Transition to IPv6
Access (aka “Edge”):
 The Access area is closest to the users and their Applications.
The Access area is where most traffic flows are sourced (start)
and sinked (terminate).
Distribution:
 The distribution area area is used to consolidate traffic flows. It
can also source and sink flows, but the flows are usually for
servers or other specialized devices. Few users connect directly
to the Distribution Area.
Core (aka “Backbone”):
 The core of the network is used for bulk transport of traffic.
Traffic flows are not usually sourced or sinked at the core.
External Interfaces & DMZs
 Aggregation points for traffic flows external to that network
7
Access/Distribution/Core Diagram
Network Analysis, Architecture and Design, James D. McCabe
Effectively and Efficiently Managing the Transition to IPv6
Core
Distribution
Distribution
Access
Access
8
Access
NASA IPv6 Project Approach
Effectively and Efficiently Managing the Transition to IPv6
Mandate from the Office of Management and Budget (OMB) for all agencies to
implement IPv6 by June 30, 2008

Mandate could be interpreted for Minimalist transition approach:
- The NASA WAN
- NASA Center interfaces to the WAN
- Center Networks & all IP devices based on Business Case
• Mandate could be interpreted for a Moderate transition approach:
-
The NASA WAN
NASA Center interfaces to the WAN
Center Networks & all IP devices based on Business Case
Center Networks & all IP capable devices
• Mandate could be interpreted for an Extreme transition approach:
-
The NASA WAN
NASA Center interfaces to the WAN
Center Networks & all IP devices based on Business Case
Center Networks & all IP capable devices
All IP addressable devices within the control or
purview of NASA
Regardless of the approach chosen, the necessary work has to be
efficiently identified and managed
9
NASA IPv6 Project Life Cycle - 4 Phases
Effectively and Efficiently Managing the Transition to IPv6
Project Formulation and Approval
1
Requirements
Gathering
2
Requirements
And Workflow
Analysis
Implementation,
Test, and
Acceptance
Architecture
And Design
3
10
4
Project Formulation & Approval
Effectively and Efficiently Managing the Transition to IPv6
The 7 steps of the Project Formulation and Approval process
are the sub-steps to complete the first two (1 & 2) phases of
the IPv6 Project Life Cycle.
Project
Formulation
And
Approval
1. Project
Initialization
2. High-Level
Information
3. Stakeholder
Identification
7. Requirements
6. Objectives
4. Project
Seed
11
5. Problem
Statements
Project Formulation & Approval
Effectively and Efficiently Managing the Transition to IPv6
The 7 Project Formulation and Approval steps can be accomplished
with considerable overlap Between them. They do not occur in a
strictly serial fashion
1. Initialization
Select program Executive, Project Manager and Requirements Manager.
They will then develop the full IPv6 team, determine project Identification,
and designate/create the collaboration and data collection points.
2. High-Level Information
Project leadership leads the development project description, scope,
objectives, operating principles, requirements, goals, deadlines to accept
problem statements, and baseline terms/definitions and high-level project
timeline for completion.
3. Stakeholder Identification
Project leadership will lead the selection of project stakeholders to include
executives, financial managers, technical representatives and others as
necessary. Stakeholders will review the project documentation, review
problem statements and make recommendations.
12
Project Formulation & Approval
(Continued)
Effectively and Efficiently Managing the Transition to IPv6
4. Project Seed
It is usually necessary to develop a set of initial problem statements,
objectives and requirements in order to kick off the project and germinate
stakeholder interaction. Project leadership will formulate and provide these
project “Seeds” to the project community.
5. Problem Statements
These are the set of issues, vetted by the stakeholders, to be resolved by
project completion. The Objectives will map to the problem statements and
the project requirements will map to the objectives. Thus the requirements
map a clear line of sight relevancy to the problem statements.
6. Objectives
These provide detailed, specific areas to be addressed in support of project
problem statements. These are reviewed by the stakeholders and the project
community.
7. Requirements
These are the most specific and detailed items to be addressed in support of
the objectives and problem statements. Each requirement must have clear
and achievable metrics.
13
Architecture & Design
Transition Plan
Effectively and Efficiently Managing the Transition to IPv6
All devices will eventually become IPv6 but this
may take decades.
In the meantime, we must transition to some level
by June 30, 2008
Transition Plan Considerations:
• NASA will need to interface/communicate with newly emplaced
NASA and Non-NASA devices that are allocated only IPv6
Addresses.
• NASA will need to communicate with NASA and Non-NASA
devices that continue to operate on the old, IPv4 standards.
• NASA needs to provide transport for devices developed to only
operate in IPv6 mode.
14
Architecture & Design
Transition Plan (continued)
Effectively and Efficiently Managing the Transition to IPv6
NASA Objective:
Establish basic IPv6 capability in network devices
located at NASA peering points, WAN backbone, and
Center LAN backbones. Basic IPv6 capability is
defined here as being able to transport and route in
dual-stack (IPv4 and IPv6) mode, and that all devices
that are configured in dual-stack mode must be able
to interoperate with each other.
DEADLINE: June 30, 2008
15
Architecture & Design
Transition Plan (continued)
Effectively and Efficiently Managing the Transition to IPv6
6 Major Steps to Meet NASA Objective
1.
Define the sets of network devices that constitute NASA
Peering Points, WAN Backbone, and Center LAN Backbones. The
most challenging area will be Center LAN Backbones.
2.
Determine the current level of IPv6 capability for each set of
network devices.
3.
Develop a risk assessments of operating in dual-stack mode
and IPv4 to IPv6 translation.
4.
Upgrade or purchase network devices as necessary to bring
each set up to basic IPv6 capability as described above.
5.
Demonstrate IPv6 routing, transport, and interoperability across
NASA Peering Points, WAN Backbone, and Center LAN
Backbones.
6.
Evaluate the effectiveness and requirements of, and issues
with, IPv4 to IPv6 translation.
16
IPv6 Challenges
Effectively and Efficiently Managing the Transition to IPv6
• Available Budget & Time
• Gathering Accurate Information
• IP addresses that only have local significance and
are not advertised outside their local networks
• Devices with hardwired addresses
• Important architecture devices that are not, and will
never be, IPv6 capable (Security Firewalls for example)
• Variance across the agency in capabilities as budget
becomes available
17
Architecture & Design
“To-Be” Mission Support Backbone (WANR)
Effectively and Efficiently Managing the Transition to IPv6
2.5 Gbps lambda
SONET OC48 (2.5 Gbps)
SONET OC12 (622 Mbps)
SONET OC3 (155 Mbps)
GRC
CIEF
Midwest
JPL
ARC
DC
CIEF
HQ
GSFC
LRC
Core
Lambda Services
DFRC
CIEF
Bay
CIEF
South
Central
JSC
WSC
WSTF
KSC
18
MSFC
CIEF
South
East
SSC
MAF
MAF
CIEF – Carrier Independent
Exchange Facility
DC – District of Columbia
Midwest – Chicago
Bay – San Francisco
South Central – Dallas
South East - Atlanta
Architecture & Design
“As-Is” IP Center Architecture (PIP/SIP)
Effectively and Efficiently Managing the Transition to IPv6
LAN – Local Area Network
WAN – Wide Area Network
Gigabit Ethernet
Fast Ethernet
OC-3
OC-12
As needed
NISN ATM Backbone
Offsite location
ATM
Switch
Addresses from PIP
passed to Public
internet as needed
Public
Internet
SIP Core
Router
PIP Core
Router
Offsite location
(“tail circuit”)
Router
Failover Switch
Peering
Router
Integration
Router
Center LAN
Router
19
Center
Campus
NASA Data
Center
Architecture & Design
“To-Be” IP Center Architecture (PIP/SIP)
Effectively and Efficiently Managing the Transition to IPv6
WANR
Optical Core
Gigabit Ethernet
Fast Ethernet
OC-3
OC-12
As needed
MSPP
MSPP – Multi-Service
Performance Platform
These Key Devices will
be upgraded to IPv6.
All Others will be
based on a
Business Case.
High Performance
Router (HPR)
NetOptics
Fiber Tap
Offsite location
Addresses from PIP
passed to Public
internet as needed
Public
Internet
SIP Core
Router
PIP Core
Router
Offsite location
(“tail circuit”)
Router
Failover Switch
Peering
Router
Integration
Router
Center LAN
Router
20
Center
Campus
NASA Data
Center
Architecture & Design: Potential “To-Be”
IP Network Model Architecture
Effectively and Efficiently Managing the Transition to IPv6
HPR – High
Performance Router
Everything shown in
this Architecture
diagram is either
Optical or will be
upgraded to native
IPv6 in the NASA IPv6
transition plan
HPR – High
MSPP – Multi-Service
Performance
Router Platform
Performance
“To-Be” PIP/SIP Architecture
MSPP – Multi-Service
Performance
Platform
21
Implementation, Test And Acceptance
Effectively and Efficiently Managing the Transition to IPv6
• Phased Implementation plan as time and
budget allow
• Lab and bench testing wherever possible.
• Network testing at most available hours
• Test each segment twice before going live
• Accept only after thorough, documented
testing.
22
Questions ??
Effectively and Efficiently Managing the Transition to IPv6
Dr. John McManus –
NASA Chief Technology Officer (CTO)
NASA Chief Enterprise Architect (CEA)
NASA Deputy Chief Information Officer (DCIO)
ESMD Chief Architect
[email protected]
Phone: 202.358.1802
Ken Griffey –
NASA Deputy Chief Enterprise Architect
NSSC Chief Enterprise Architect
[email protected]
Phone: 228.813.6209
23