Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Network Assessment

Microsoft, VMware, Storage,IP Network Review Results

Rick Allen

on 25 March 2012

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Network Assessment

Network Assessment Assessment sections Storage by HP
IP by Cisco and Lucent
Microsoft - by Microsoft
VMWare - by VMWare and LogicsOne
Telecom - by Avaya and Lucent Security
Managability Methodology Green - Conformance to leading practices; very few if any discrepancies

Yellow - Overall conformance to leading practice, room for improvement in some areas

Red - One or more areas require significant improvement with a major overall impact on availability goals Storage - Encryption of Data in rest and data in motion not adequate. Security IP - No use of network access control, insecure management protocols, broadcast all wireless network names, no transport encryption on public networks, non compliant wireless protocols, and no Intrusion Detection or Prevention. Microsoft - Several settings not to current best practices due to application limitations.
Use of generic logins such as Nursing, Doctor, and Imaging and password storage not optimally configured. VMware - Security meets leading practices Telecom - Security meets leading practices Resiliency Storage - Minimal data replication, manual administrator actions required for failover, SAN software not current, and core SAN switch past end of life. IP - Failover protocols not configured correctly, failover links not sized correctly, 70 devices currently past final end of life - including the 2 highest impact devices on the network, 83 more reach that milestone in next the 18 months, and 5 major and 40 maintenance versions of out of date network software in use. Wireless antennas autonomous not centrally managed. Microsoft - Domain Controllers not fully redundant, several key components not configured for redundancy, and unsupported versions of Windows are running on at least one domain controller. Manual administrator actions are required to recover from any failure. VMware - High availability failover not configured optimally and management servers runing in non recommended configurations. Telecom - No failover outside of any switch frame, PBX software version at end of support, voicemail server past end of life, call distribution and menuing server past end of life, call distribution and menuing system past final end of life. Capacity Storage - Curently at over 80% of total storage capacity. Extreme growth in VMware has caused a huge spike. Thin Provisioning not implemented, will require a change in capital planning and execution. SAN ports are at capacity excluding the ports in the end of life switch. IP - Extremely over subscribed. Recommended ratios are between 4:1 and 24:1, we are currently configured between 26:1 and 210:1. Switch port capacity is reached in both the Resource Center and Main Computer Rooms. Wireless capacity is constrained by over subscription on the wired network and the age of the wireless antenna's. Microsoft - 5 current Domain Controllers reaching maximum utilization. Need to consider expansion along with upgrades to 64-bit multi- core servers. VMware - Over capacity to provide stable desktops. Using memory and processor capacity defined for High Availability. Links to storage and network are both severely over subscribed. Have disabled load balancing functions within VMware View to ensure network stability. Telecom - Capacity for traditional analog/digital phones is adequate. Ascom wireless phone capacity is nearing the currently licensed limit. IP based phones, which is all future growth, capacity is limited and constrained by IP network issues. Design Storage - Storage design follows best practices for a traditional SAN architecture. Migration to a higher capacity consolidated architecture is recommended to meet growth projections. IP - Several single points of failure within the network. The use of daisy chain design presents both capacity and resiliency issues. Not leveraging network segmentation outside of 3 small areas. Microsoft - No documentation is in place from the implementation of the network and no design has been documented for future growth. VMware - Several single points of failure within the network. Current design not adequate to support current capacity or projected growth. Telecom - Overall design meets industry best practice. Management Management - Tools for management automation are needed for all segments of the assessment. Projects So far 12 projects have been spawned to address these issues. Timelines range from late July until mid year 2012. Most projects are tied to capital funding approvals. Projected Costs: Storage : Approx $700,000
IP: Approx $1,000,000
Microsoft: Approx $75,000
VMware: Approx $700,000
Telecom: Approx $2,000,000
Full transcript