all aitr meeting – ip re-addressing 0 ip re-addressing implementation all aitr meeting presented...

1

All AITR Meeting – IP re-addressing

IP re-addressing ImplementationAll AITR Meeting

Presented by: Bill Furr

June 24, 2008

2


Help DeskDesktopMessaging Services

Enterprise Exchange/Outlook EmailEnterprise Collaboration Tools

Active Directory, DNS$25M Investment

Mass Desktop Refresh ProjectsNetwork Printer Consolidation and RefreshEnterprise Desktop Management Systems

$35M Investment

New IBM and Unisys Mainframes in New Data Center Consolidation and Refresh of Servers

Migration of servers to the Data Center$50M Investment

Enterprise Help Desk in Russell and Chesterfield Counties Field Based Agents and Technicians for Level 3 Enterprise Help Desk System (Peregrine)

$10M Investment

New Data Center/Office Building in ChesterfieldNew Disaster Recovery Center and Help Desk

in Russell County$60M Investment

New Commonwealth-wide MPLS Core WANLAN upgrades to Local Switches/Routers as Needed

DHCP$60M Investment

Voice over IP Network Optimized for Voice and Video Traffic

$20M Investment

Enterprise Security Operations CenterComputer Security Incident Response Center

Secure Internet Gateway$10M Investment

Security

NetworkVoice / Video

Mainframe & Servers -IP re-addressing

Facilities Tier 3 and Tier 2

Reliable, High Performance,Enterprise-Wide IT Infrastructure

ITIL/VITA myRequests“People – Processes – Tools”

$270 Million 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

Benefits

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-addressingWe’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)

*Depends on the number of agency servers and size of agency

Hold kickoff meetingHold data validation

meeting (technical staff)

Hold plan validation meeting

(technical staff)

Change IP addresses on

servers

Collect IP re-addressing data using data collection tools

Test applications to ensure they are

working properly

1 2 3 4 65

2 Hours 6-9 Weeks* 1-2 Hours*2-8 Hours

Per Application*

2 Hours 1 Hour

IP addresses successfully changed!

7

Total Time: 3 Months*

9


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

IP re-addressing Request for Agency Time (approximate)

10


Service Interruptions will be MinimizedTools – 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)

= tentative date ranges

Develop Re-IP strategy by Application

Execute Data Call

Analyze Data

Re-IP Servers per strategy

Deploy Tools

July

2008 Timeline

SeptemberDeployment

August

12


Appendix

13


IP re-addressing Transformation Process

PRE-GO LIVEPRE-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

• 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

POST-GO LIVEPOST-GO LIVE

Agency

• Contact the VITA Help Desk for any technical issues at (866) 637-8482

• Send e-mail with functional/other questions about IP re-addressing to [email protected]

IT Partnership team

• Answer questions sent to [email protected]

Agency

• Contact the VITA Help Desk for any technical issues at (866) 637-8482

• Send e-mail with functional/other questions about IP re-addressing to [email protected]

IT Partnership team

• Answer questions sent to [email protected]

GO LIVEGO LIVE

Agency

• Conduct testing of systems and applications

IT Partnership team

• Change IP addresses on agency servers

• Coordinate/conduct testing of systems and applications

Agency

• Conduct testing of systems and applications

IT Partnership team

• Change IP addresses on agency servers

• Coordinate/conduct testing of systems and applications

Transformation Project ObjectiveTransformation Project ObjectiveIP 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

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

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


AITRs

4 Distribute IP re-addressing Introductory/Kickoff emails 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 Email 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 Email Invite


Completed Activities

15


IP re-addressing Communication Deployment Detailed Activities (cont’d)

# Activity Timing Responsible Party

Target Audience

8 Distribute Technical Plan Validation Meeting Email Invite


9 Distribute Application Testing Email Notifications -30 days before implemen-tation

APOCs Technical support staff

10 Distribute 30 day e-mail to agency and Service Delivery personnel at agency receiving IP re-addressing

-30 days AITR, RIM, District Managers


11 Distribute 15 day e-mail to agency and Service Delivery personnel at agency receiving IP re-addressing

-15 days AITR, RIM, District Managers


12 Distribute 1 day e-mail to agency and Service Delivery personnel to Inform them the outage window for specific server consolidation

-1 day AITR, RIM, District Managers


13 Distribute Thank You notice Post deployment

AITR, RIM, District Managers


14 Answer questions from Questions Mailbox Ongoing IP re-addressing project manager

Various

all aitr meeting – ip re-addressing 0 ip re-addressing implementation all aitr meeting presented...

Documents