Updated: Aug 6, 2019
The goal of the project is to install a global, standardized and robust Wide Area Application toolkit that can optimize Wan traffic.
Scope of the project
- there are 2 datacenters, one in US , one in EMEA
- the WAN is base don MPLS, 1 default and standard provider
- we have to consider about 100 sites worldwide, between 10 and 300 ms latency.
- there is a global QoS policy in place, based on access lists
- most of the WAN traffic will be VDI, Citrix based, using Netscalers
- all the remote sites have the same design and hardware in place
- remote sites have no IT personnel, the implemented system must be completely remotely manageble
Clients will need to be migrated to a full VDI environment that is hosted from the global datacenters. This requires an efficient and optimal usage of network bandwidth. All applications will rely on the availability of the VDI environment.
A global budget has been created for the project. This includes hardware, software costs and consultancy.
- product decision
- technical design
- technical installation plan
- technical test plan
Activities to complete the deliverables
--> product decision
Create shortlist of IT solutions:
- Riverbed Steelhead
- Cisco Waas
- Organize global meetings with internals and suppliers:
Decision on product choice:
- Decision is to go further with Cisco Waas.
One of the big advantages is that Cisco is the only vendor who has a partnership with Citrix to have deep insight in the Citrix technology.
Example product presentation Vendor
The technical design will be created by internal and external ( vendor resources ) engineers. The design must completely describe the technical setup of the solution for the datacenters and the remote branches.
Example technical design
Technical installation plan
The installation plan will be used during the implementation and will describe a step by step approach. This installation plan will have to be approved during the global CAB meetings and will be provided in the change requests.
Also, a roll-back plan needs to be included in case the change fails.
Technical test plan
The Technical test plan needs to include a various number of test ( scripts ) and the expected results. Any deviation or abnormal behaviour should be documented in detail. The outcome of the technial tests will be used to decide on the go ahead or roll back of the change.
A set of documents need to be created and imported into the knowledge databases. These documents will cover the installation of the Waas environments @ the datacenter and the remote branches. The documents will get revision numbers and need to be approved by the internal architects.
Put activities in a locical sequence
- organize global meetings with internals, externals and vendors
- decide upon product
- create technical design
- create technical installation plan
- create documentation
- create technical test plan
- manage service and change requests ( cut-over dates, risk analysis, outage planning )
- execute change
- execute test plan
- setup monitoring
- complete documentation
- intstruct + hand-over to support teams
- review project
Estimate resource requirements
Plan the nescessary resources to complete the project
Central DC installation
- 1 Network architect from the internal team : 5 man days
- 1 Network architect from the external team : 9 man days : 5 to prepare and 4 to execute ( weekend )
- 1 Vendor architect : Cisco expert on Waas : 2 man days during preparation and during execution phase. Some extra support may be needed afterwards.
Remote branch installation
- 1 Network architect from the internal team : 0,5 man day.
The change @ the datacenters need to be performed first. Once the central appnav controllers and embedded waas engines are operational, the branch sites will be added one by one.
Order of execution @ the datacenter :
- Perform physical installation of the equipment
- perform hardware tests
- perform DC routing adjustments ( 4 vlans between core and WAN routers )
- Setup Appnav
- Define policies
Example during execution phase
Use Central Waas Manager to monitor Waas clusters, appnav controllers and remote waas branches.
Instruct support teams and hand-over
A set of documents need to be created for the 1st line troubleshooting procedures :
- procedures in case of announced outages @ branch offices
- procedures in case of unexpected outages @ branch offices
- procedures to identify and troubleshoot user / application specific issues
- service desk workflow procedures to escalate issues to Tier 3
- procedures to create/manage common application affinity optimization rules ( executed by Tier 2 ) - needs CM
- procedure to recover / reinstall of waas appliances ( will be done by Tier 3 - needs CM )
These documents will be used in the training of Tier1 and Tier 2 personnel.
Multiple trainings will be organized for the different service desks in every region.
Tier 3 personnel will get more in depth technical training
Review and Close
A meeting will be organized with all the stakeholders to review the installation, configuration and documentation of all project phases. Upons everyone's agreement, the newly installed service can be moved from transition to service operation ITIL status.