1. IP re-addressing Implementation Presented by: Bill Furr
All AITR Meeting
Presented by: Bill Furr
June 24, 2008

2. Transformation Messaging Services Desktop Help Desk Security
Mass Desktop Refresh Projects
Network Printer Consolidation and Refresh
Enterprise Desktop Management Systems
$35M Investment
Enterprise Help Desk in Russell and Chesterfield
Counties Field Based Agents and Technicians for
Level 3 Enterprise Help Desk System (Peregrine)
$10M Investment
Enterprise Exchange/Outlook
Enterprise Collaboration Tools
Active Directory, DNS
$25M Investment
Security
Transformation
Mainframe & Servers - IP re-addressing
$270 Million Investment
Reliable, High Performance,
Enterprise-Wide IT Infrastructure
ITIL/VITA myRequests
“People – Processes – Tools”
Enterprise Security Operations Center
Computer Security Incident Response Center
Secure Internet Gateway
$10M Investment
New IBM and Unisys Mainframes in New Data Center
Consolidation and Refresh of Servers
Migration of servers to the Data Center
$50M Investment
Network
Facilities Tier 3 and Tier 2
Voice / Video
New Data Center/Office Building in Chesterfield
New Disaster Recovery Center and Help Desk
in Russell County
$60M Investment
New Commonwealth-wide MPLS Core WAN
LAN upgrades to Local Switches/Routers as Needed
DHCP
$60M Investment
Voice over IP Network Optimized for Voice and Video Traffic
$20M Investment

3. IP re-addressing Introduction
Project Description
IP re-addressing is a component of the server transformation effort that will transition servers from multiple legacy networks to being managed on a single, reliable, and scalable network infrastructure. The IP re-addressing effort will collect application data on server addresses, analyze the data to create IP re-addressing plans, and change IP addresses to move servers from their current network to a new single network.
The new network will provide increased security, automated monitoring, and reduced complexity to maintain and operate the Commonwealth’s IT infrastructure.
Project Objectives
Collect necessary data for IP re-addressing
Change IP addresses of state agencies’ servers

4. Benefits from IP re-addressing
Effectively manage application environments: Agencies will be provided the dependency maps of their environment from the data collection efforts. These maps can be used to document and manage your application environment and show the relationships and interdependencies between applications
Dependency maps will also facilitate common understanding of infrastructure applications and their impact to agency operations to improve our ability to prioritize and manage critical services.
Enables the full benefits of server transformation: Relocation of servers to a single, secure location where they can be centrally monitored and maintained. This will provide increased security and reduce the complexity to maintain and operate the Commonwealth’s IT infrastructure
Provides improved understanding: Allows service delivery and support teams to better understand infrastructure dependencies, allocate resources, and improve focus on critical infrastructure components

5. Data Collection is Necessary for IP re-addressing
We’ve learned from previous data collection efforts and have a process to pre-populate all data requests with previously collected information. This will minimize the level of effort required to complete the data collection
The data will be stored so that it may be leveraged by future initiatives to reduce the time it takes to plan and deploy projects. (For example, IP re-addressing data will be shared with the enterprise architecture group)
Data collection efforts will focus on application dependencies:
Hard coded network references and addresses
Internal/external servers
Client/server relationships
Data will be used to:
Plan and develop IP re-addressing schedule
Create dependency maps between systems
Promote a common understanding between VITA and agencies regarding application dependencies when planning upgrades and changes to the environment
Assist in moving servers to the new MPLS network

6. IP Data will be Collected through Data Collection Tools and a Tailored Survey Questionnaire
Data collection tools - will create an application dependency map of our server environment
Lumeta's IPsonar® - will trace the path of data to provide a comprehensive network topology from an application connectivity perspective
EMC Smarts Application Discovery Manager - will provide an end-to-end map of the relationships and dependencies of applications, servers, and devices
Tailored survey questionnaire – We need to utilize agency resources to validate the collected data. The questionnaire will be modified to eliminate questions where the tool has already provided the data

7. The Data Collection Tools will not Collect any Proprietary and Sensitive Data
Lumeta's IPsonar®
No sensitive data is collected other than network infrastructure information
The information collected by the tool is stored in the appliance which is a hardened Linux platform with access control that requires a configurable user ID and password for access
The interface is web based and data in motion is encrypted using https
EMC Smarts Application Discovery Manager
Collects information about hosts, services, dependencies, usage, demand, tables, and URLs
Does not capture usernames, passwords, transaction details, or other sensitive data

8. IP re-addressing Agency Timeline (approximate)1 2 3 4 5 6
Hold plan validation meeting (technical staff)
Change IP addresses on servers
Test applications to ensure they are working properly
Collect IP re-addressing data using data collection tools
Hold data validation meeting (technical staff)
Hold kickoff meeting
2-8 Hours Per Application*
2 Hours
6-9 Weeks*
2 Hours
1 Hour
1-2 Hours* 7
Total Time: 3 Months*
IP addresses successfully changed!
*Depends on the number of agency servers and size of agency

9. IP re-addressing Request for Agency Time (approximate)
Data Validation Meeting (Total time required: 2 hours)
Present data discovered to date (tool output)
Ask questions from tailored survey questionnaire
Answer agency questions and exchange POC information
Plan Validation Meeting (Total time required: 1 hour)
Validate IP re-addressing plan
Review resource groupings created from dependency maps
Align IP re-addressing schedule with agency resources/constraints
Application Testing (Total time required: 2-8 hours per application)
Document comprehensive test cases of application functions
Run test cases and provide test results

10. Service Interruptions will be Minimized
Tools – No interruptions to service
No downtime required for configuration
It takes approximately 4 hours to configure both tools
IP re-addressing process – Minimal interruptions
Interruptions to service will occur at an Application level
Changes will be planned with agency approval and where possible, occur during maintenance windows

11. Planned Schedule for IP re-addressing (DJJ Pilot ~90 days)
Deployment
2008 Timeline
July
August
September
Deploy Tools
Analyze Data
Execute Data Call
Develop Re-IP strategy by Application
Re-IP Servers per strategy
= tentative date ranges

12. Appendix

13. IP re-addressing Transformation Process
Transformation Project Objective
IP re-addressing is a key component of server transformation efforts. A data collection effort is needed to fully understand the current server and application environments before changing IP addresses on state agencies’ servers
PRE-GO LIVE
GO LIVE
POST-GO LIVE
Agency
Validate survey questionnaire
Review/distribute IP re-addressing deployment communications
Approve maintenance/outage windows
IT Partnership team
Hold Kickoff meeting
Deploy data collection tools: Lumeta's IPsonar & EMC Smarts Application Discovery Manager
Hold validation meeting for data collected
Hold validation of re-addressing plan meeting
Schedule maintenance/outage windows
Agency
Conduct testing of systems and applications
IT Partnership team
Change IP addresses on agency servers
Coordinate/conduct testing of systems and applications
Agency
Contact the VITA Help Desk for any technical issues at (866)
Send with functional/other questions about IP re-addressing to
IT Partnership team
Answer questions sent to

14. IP re-addressing Communication Deployment Detailed Activities#
Activity
Timing
Responsible Party
Target Audience 1
Present overview of IP re-addressing deployment at PAC meeting
-90 days
IP re-addressing project manager
AITRs 2
Present overview of IP re-addressing deployment at Manager/Supervisor Conference call
Service delivery managers and supervisors 3
Present overview of IP re-addressing deployment at all-AITR meeting 4
Distribute IP re-addressing Introductory/Kickoff s to agency AITRs, APOCs and technical staff
-85 days
IP re-addressing project manager, TPOCs
AITRs, APOCs, Technical support staff 5
Present Kickoff Presentation at Kickoff Meeting
-80 days
IP re-addressing project manager, AITRs, APOCs
Impacted agency and service delivery personnel 6
Distribute Data Gathering Notification to Agency Technical Support Staff to validate, complete Data Collection Template and send it back to the APOC
-65 days
APOCs
Technical support staff 7
Distribute Technical Data Validation Meeting Invite
-55 days
Completed Activities

15. IP re-addressing Communication Deployment Detailed Activities (cont’d)#
Activity
Timing
Responsible Party
Target Audience 8
Distribute Technical Plan Validation Meeting Invite
-40 days
APOCs
Technical support staff 9
Distribute Application Testing Notifications
-30 days before implemen-
tation 10
Distribute 30 day to agency and Service Delivery personnel at agency receiving IP re-addressing
-30 days
AITR, RIM, District Managers
Impacted agency and service delivery personnel 11
Distribute 15 day to agency and Service Delivery personnel at agency receiving IP re-addressing
-15 days 12
Distribute 1 day to agency and Service Delivery personnel to Inform them the outage window for specific server consolidation
-1 day 13
Distribute Thank You notice
Post deployment 14
Answer questions from Questions Mailbox
Ongoing
IP re-addressing project manager
Various