Using the following image sample below, create a fictitious Current IT Environment TWP with at least 5 categories / rows of information.

Current IT Environment Category Geography & Description Two data centres to be used, Site A and Site B, with data replication between. Both will act as the Primary, with failover capability to the other DC. Will probably shift "primary" management nodes between sites to ensure DR capability. Topology of DCs Physical Compute Environment x86 nodes comprising of a mix of x3850's (for VM hosts) and x3650's (for management nodes). No Unix. System Director to be used for hardware management. Virtualised Environment Vmware v4.0 or v4.1, with vCentre deployed in HA configuration with heart beat between nodes. Likely to be deployed in a virtual guest. Clusters not spread across DC's due to network connection. 3 vNics per guest (customer, management, backup) Storage Environment V7000 SAN with storage separation for workloads at each site (x4). Separate V7000 or DS3500 for management nodes. Hardware under consideration is IBM TS5760 VTL. Network Environment The network based on Cisco 6509s. At edge will be Nexus 5000 and possibly Nexus 2000s. 5 VLANs setup for each customer +3 VLANs for management, backup, & vMotion. Static IP used, and local DNS services. Some firewalling used for customer isolation and special requirements May use Cisco IPS modules in 6509. Currently used Symantec for AV, but does not cover Linux. Use of Tipping Point (internet based) for IPS/IDS Security Monitoring- SCOM used for MS Exchange, but deemed deficient in many areas. No tooling for capacity planning Incident and problem management uses Remedy. Active Directory used for directory services OSS integrations BSS Integrations WebSphere Portal is the primary customer portal used today. JD Edwards billing system will continue to be used Volumetrics & Traffic Growth Initially start at capacity for 2,000 VMs, 1,000 at each DC. Growth tbo