SSMSv2 Audits of America’s, AP and EMEA ControlCenter 5.2

1. SSMSv2 Audits of America’s, AP and EMEAControlCenter 5.2 EDS SMC SSMSv2 August 9, 2007

2. Agenda • Review of Objectives • Project Report Cards • Status • Progress • Commonality of Issues across SMC’s

3. SSMSv2 Remote Audits – Summary of Objectives Target Objective for Remote Site Audits • North America SMC’s • South America SMC’s • Asia Pacific SMC • Remote Site Audits • Assess the operational state of CC 5.2 • Update CC 5.2 related Documentation • Determine Upgrade Ability to CC 6.0 for SSMSv3

4. SSMSv2 Onsite Audits – Summary of Objectives Target Objective for Onsite Audits • Poor Performing SMC’s • Highly Secured SMC’s • Onsite Site Audits • Assess the operational use of CC 5.2 • Interviews with Administrators • Assess the operational state of the CC 5.2 • Identify and Analysis of problems with CC 5.2 • Recommendations and Corrective Actions for stability • Update CC 5.2 Documentation • Determine Upgrade Ability to CC 6.0 for SSMSv3

5. Project Status

6. Project Progress

7. Project Summary • Tulsa can not be audited remotely • Security restrictions impeded activity • Additional time required per site • Planned for 10 hours / site, is taking longer • Remote Site Audit Schedule Adjustments • Tulsa requires a new action plan • Reset delivery date for updated documentation • Finalization & Reviews start August 13th • Print and deliver by August 24th • Onsite Audit Schedule Adjustments • Russelsheim delivery of conclusions • Scheduling conflicts (Vacations, other projects) • Planned for August 17th

8. Commonality of Issues across SMC’s Top 10 - Repetitive issues found • Agent and Infrastructure Management • Pro-Active Patch Management • Issues with SSMS Server maintenance • High number of in-active Agents • Managing Solutions Enabler, JAVA & NaviCLI • Monitoring of Active Console Alerts • Managing WLA • Compliance to ControlCenter Support Matrix • Growth of the managed environment • ControlCenter agent placement and policies management

9. Agent and Infrastructure Management

10. Pro-Active Patch Management • Installing Service Packs • Installing and Applying Patches (Hotfixes) Plano Charlotte Toronto Auburn Hills

11. High number of in-active Agents • In-Active Agents need to be managed and kept to a minimum • Critical Agents that impact operations • Storage Agents • FCC Agents • WLA Archiver • Stores • Agents that impact reporting • Host Agents Plano Auburn Hills

12. Issues with SSMS Server maintenance • Server OS configuration changes • MS Auto Update service • MS HF’s applied automatically • Maintaining Anti-Virus applications • Page files configurations • Not meeting MS Recommendations of 1.5x • Non-contiguous Page Files on the same HDD • Boot.ini settings • Multiple /PAE entries • /3GB switch • Changes applicable to Windows 2003 SP1 which impact ControlCenter • Data Execution Prevention • Running the SNMP TRAP listening service

13. Monitoring of Active Console Alerts • Emitter does not forward ALL alerts • Emitter clears any alert in the queue greater then 24-hours old • Repetitive Critical Severity 1 & 2 alerts in the Alert History • Non Emitter forwarded alerts are not being resolved • Daily review of Alerts in the Console is a Best Practice • Emitter does not work well when there is a mixed Leveraged environment with a distributed support center. • Case sited with this issue is Europe where Russelsheim is the CC Center for remote locations around Europe

14. Compliance to ControlCenter Support Matrix • SAN Maintenance and adherence to supported firmware • Equipment dropped from support Plano Charlotte

15. Growth of Managed Environment • Planning for growth • New arrays with changing support requirements • Capacity planning of the infrastructure • Planning for change • Re-allocation of assets • GM moved to its own CC implementation from Auburn Hills & Plano • Commonwealth Bank of Australia – will produce a drastic change to Sydney environment. • GM – will produce a drastic change to Russelsheim environment.

16. Managing Solutions Enabler, NaviCLI & Java • JAVA is being auto updated • FLARE dependencies not being followed • Mixed version of NaviCLI within a CLARiiON managed group • Managing older versions of FLARE with the latest NaviCLI Version • Rules are: • FLARE 24 – NaviCLI 6.24 • FLARE 22 – NaviCLI 6.22 • FLARE 19 and Below – NaviCLI 6.19 • Symmetrix dependencies to Solutions Enabler not being followed • Mixed versions of Solutions Enabler across agent servers • Newer DMX3 being managed with SE versions below 6.3.2 • Specific ControlCenter Hotfixes needed to Monitor, Report and Manage new versions of EMC Arrays

17. ControlCenter agent placement and policies management • Agents on Remote Access Server • Agents added to Store Servers • Host agents installed on the CC Cluster • Not modifying Discovery Policies to accommodate for changes in the managed environment • Globally applying of policies when specific objects need to be monitored.

18. Managing WLA • Additional Archivers installed when not required • Handling Policies • Use of Revolving and Analyst DCP • Applying Policies globally to all managed objects • Not creating object specific templates for detailed analysis • Ignoring WLA Archiver processing alerts

19. How SMC’s are being Managed Plano Charlotte Toronto Auburn Hills

20. Q&A Discussion • SMC’s • Doxford • Washington • Tulsa