1 / 56

EMC Ionix ControlCenter 6.1 UB7 Architecture & Deployment Design for Citigroup North America

EMC Ionix ControlCenter 6.1 UB7 Architecture & Deployment Design for Citigroup North America. Date: 28 January 2010 (Updated 17 February 2010) Version: 5.3.1 (Final) Author: John Maloney, EMC Professional Services Jim Stringer, Ionix Engineering. Contents. Architectural Factors

jalila
Download Presentation

EMC Ionix ControlCenter 6.1 UB7 Architecture & Deployment Design for Citigroup North America

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EMC Ionix ControlCenter 6.1 UB7 Architecture & Deployment Design for Citigroup North America Date: 28 January 2010 (Updated 17 February 2010) Version: 5.3.1 (Final) Author: John Maloney, EMC Professional Services Jim Stringer, Ionix Engineering

  2. Contents • Architectural Factors • Design Expectations • Server Requirements • Break Down by Datacenter • 390/111 • Rutherford • Silver Springs • George Town • South West • Mid West • Tampa

  3. Architectural Planning Factors

  4. Architectural Planning Factors • Important factors that drive a ControlCenter Architecture • Hosts • Number of Hosts with a Host Agent • Number of Host entities (Host containers and Virtual Machines) • Total Logical Host Devices • Arrays • Number of arrays • Number of devices/LUN per array • Databases • Number of Database Instances • SAN • Number of switches • Number of ports • Number of fabrics • The facts presented on the following slides represent Citi’s North America Managed Environment • The plan is to have 1 ControlCenter Instance per Datacenter

  5. Architectural Planning Factors Current CC 6.0 Growth/Change for CC 6.1 Hosts Physical Hosts = +1,188 = 8,526 Logical Host Devices =+79,277 = 466,606 VMware ESX = +450 Virtual Machines = +5,400 (Estimated 12 VM per ESX Server) Databases Oracle = +4 = 95 SYBASE = +6 = 395 SQL Server = +6 = 96 SAN Ports = 30,927 Switches = 262 Hosts • Physical hosts = 7,338 • Logical Host Devices = 387,329 • VMware • ESX = 0 • Virtual Machines = 0 Databases • Oracle = 91 • SYBASE = 389 • SQL Server = 90 SAN • Not Discovered

  6. Architectural Planning Factors Current CC 6.0 Growth/Change for CC 6.1 Arrays Symmetrix = +16 = 139 Devices = +35,523 = 329,572 T-Devsincluded in Device # Symmetrix removed = -0 Devices removed = -0 CLARiiON = +38 = 173 Disks = +2,277 HDS = +5 = 36 Centera = +16 = 18 Celerra = +46 = 46 DataMovers = 2 to 4 /per Total Arrays = +132 = 413 Arrays • Symmetrix = 113 • Devices = 254,651 • CLARiiON = 135 • Disks = 9,963 • HDS = 31 • Centera = 2 • Celerra = 0 Total Arrays = 281

  7. Design Expectations

  8. Design Expectations • The following slides provide • information related to each of the architectural factors • Reference to supporting EMC documentation • Citi requirements

  9. Design Expectations for Hosts – per Datacenter Hosts • Maximum Managed Hosts (Installed Host Agents) = 2,050 • Maximum total Host Device Logical Paths = 262,400 • VMware sizing Guidelines apply • Adhere to P&S Guideline P1 – P2 and Technical Notes – Installing Ionix ControlCenter in a VMware Environment • Maximum Host entities in Console = 4,500 • Combination of Host Agents + Host Containers + Virtual Machines • Host Containers and Virtual Machine without a Host Agent do not count as Managed Hosts • Host Containers and Virtual Machine without a Host Agent provide reporting on Storage Allocation only • Citi requirements for Hosts Reporting • Report on storage utilization for all SAN attached physical hosts – requires Host Agent • Host containers and Virtual Machines with agents will report on Allocated SAN Storage only • WLA Performance for selected Hosts on a as-needed basis

  10. Design Expectations for Hosts – per Datacenter VMware • ESX servers will be managed by all installed VMWARE Agents per Datacenter (Redundancy and load balancing) • ESX server discovery will be per each ESX server and not through Virtual Center • Discovery of 50 ESX server per VMware Agent • User account for discovery • Service Account can be a local ESX account or a LDAP Domain Account • Service Account with Read-only rights to browse the DataStore • Adhere to P&S Guideline A24 • Citi requirements for VMware discovery • ESX Servers that are attached to SAN Storage will be discovered • ESX Servers that use NAS Storages will not be discovered • Virtual Machines will not have ControlCenter Agents installed • Unless the VM was identified as a critical server to monitor

  11. Design Expectations for SAN – per Datacenter SAN Discovery Only • Discovery method: • Cisco – SNMP V1/V2/V3 • McData - McData (Brocade) SMI Agent Provider for EOS products 2.7 or later • Core-Edge with 100% Locality to keep with vendor SAN and Fabric limits • Locality provides fabric to fabric isolation • McData Fabrics can not exceed these scalability limits (McData SMI Agent Provider requirement • Maximum Switches per fabric = 18 • Maximum Zones per fabric = 1456 • FC Ports in Switches = 1952 • WWN Zone Members = 1002 • ControlCenter FCC Agent and NAS Agent can not reside on the same host • Both agents use Port 162 to monitor for alerts • Adhere to P&S Guideline A6 – A9 • Citi requirements - SAN Monitoring only

  12. Design Expectations for Symmetrix – per Datacenter Symmetrix Management • Each Symmetrix will need 6 Gatekeepers provisioned from each Symmetrix to each Symmetrix Agent • 6 Gatekeepers to each Symmetrix Agent from each Symmetrix • Dedicated Gatekeepers only • Multi-path Gatekeepers is not supported • HBA Vendor Fan-in / Fan-out ratios must not be exceeded • Minimum version of MRLK Solutions Enabler – 7.1.0.0 or later • Symmetrix Management from a Windows platform will need SE HotFix 1469 applied raising the SE version to 7.1.0.17. Solaris platform will be 7.1.0.0 • Adhere to P&S Guideline A10 - A14 • Citi requirements for Symmetrix Management • No Management Redundancy or load balancing of Symmetrix Agent • SMC (Symmetrix Management Console) will not be installed • Citi will provide redundant Gatekeeper paths for limited Symmetrix Management Server redundancy • Total of 12 dedicated Gatekeepers to each Symmetrix Agent from each Symmetrix using two FC paths (6 Gatekeepers per path, no multi-pathing)

  13. Design Expectations For CLARiiON – per Datacenter CLARiiON Management • CLARiiON Arrays managed by specific CLARiiON Agents • No agent load balancing or redundancy • Not to exceed 12 CLARiiON Arrays per CLARiiON Agent when do WLA data is being collected • Individual CLARiiON Array discovery can vary greatly depending upon array Disk and LUNs configurations. This problem is rarely encountered using a 4 CLARiiON Array to Agent ratio. • If discoveries fail, this ratio will need to be reduced • To collect WLA data from CLARiiONs the number of CLARiiON arrays to CLARiiON agent ratio must not exceed 4 collect WLA data with a 15-minute WLA Daily interval • Minimum version of MRLK Solutions Enabler – 7.1.0.0 or later • CLARiiON management from a Windows platform will need SE HotFix 1469 applied raising the SE version to 7.1.0.17. • NaviCLI 6.28 or 6.29 (HF 4716) or later • No WLA performance data to be collected – Ignore Table 25 • Adhere to P&S Guideline A15 • Citi requirements for CLARiiON Management • No Management Redundancy or load balancing of the CLARiiON Agent • No WLA Performance Data will be collected

  14. Design Expectations for HDS – per Datacenter HDS • HDS Arrays will be discovered with the Storage Agent for HDS • No agent redundancy • HiCommand & HiCommand Tuning Manager 6.0, 6.1 is currently support. • HiCommand & HiCommand Tuning Manager 6.2 will be added Q2 or Q3/2010 timeframe • WLA Performance data will not be collected • To collect HDS Performance Data, HDS Tuning Manager is required • Adhere to Guideline A17 and Tables 28 and 29 to collect HDS performance data • P&S Engineering has authorized Citi to discover up 24k LDEVs or 12 Arrays per HDS Agent with no WLA performance data being collected • Variance to P&S Guideline A17 and Table 28 – 29 has been granted by P&S Engineering – Email from Shouri Mitra dated Sunday, November 02, 2008 8:35 PM • Citi requirements for HDS • No WLA Performance Data will be collected

  15. Design Expectations for other Arrays – per Datacenter NAS (Celerra) • Celerra Arrays managed by specific NAS Agents • No agent load balancing or redundancy • No performance data to be collected – Ignore Table 26 • Adhere to P&S Guideline A16 • Citi requirements for Celerra • No WLA Performance Data will be collected Centera • Centera Arrays will be managed by specific Centera Agents • No agent redundancy • Adhere to P&S Guideline A18

  16. Design Expectations for Databases – per Datacenter Databases • SYBASE, Oracle and SQL Server databases will be discovered using local or proxy discovery • Oracle Agent Local – 50 DB Instances on the Oracle Database Server • Sybase 15 discovery will be through proxy only • Any database running on a 64-bit OS will be through proxy only • Any database running on a Cluster will be through proxy only • Proxy discovery must not exceed the database to agent limit • Common Mapping Agent for Databases – 40 DBs per agent • Oracle Agent – 30 DB Instances on one or more Oracle Database Servers • Database discover requires Solutions Enabler • To continue monitoring of database on servers with ControlCenter 6.0 Agents and Solutions Enabler 6.4.0 will require one or more servers with ControlCenter 6.0 Agents • These servers must be established and activity monitoring the database prior to the ControlCenter 6.1 upgrade • Adhere to P&S Guideline A19 – A20 (CMA) & A23 (Oracle) • Citi requirements for Databases • No WLA performance data will be collected • Discover Databases with local DB Agent when possible • No agent load balancing or redundancy

  17. Design Expectations for WLA – per Datacenter WLA Performance data • Only Symmetrix Arrays with the default WLA Daily interval of 15-minutes • Any interval lower then 10-minutes is not supported • Specific Hosts for diagnostics • Limited set of SAN components. • Up to 1,024 SAN Ports for limited period of time using 15-minute intervals WLA Daily DCP. • For problem investigation/resolution only • Performance Statistics monitor up to 10 switches at a time • No Oracle Databases, CLARiiON arrays, HDS Arrays, Celerra WLA DCP Guidelines • WLA Daily DCP should be set to the intervals defined in the P&S Guidelines Document per Managed Object Agent • No WLA Revolving DCP should be enabled (no longer needed) • WLA Analyst DCP for problem resolution @ 2-minute interval for specific managed objects and enabled from the Performance Manager GUI. • Run for 2 to 4 hour periods • Performance degradation ControlCenter will be experienced during this period WLA Archiver • Adhere to P&S Guideline A22

  18. Design Expectations – per ControlCenter Instance Store Guidelines for Stores running on Virtual Machines • 700 Hosts per Store • 89k Host Logical Paths per Store ControlCenter will be running from SAN storage • Mirrored RAID1 is recommended for best performance • All Raid Protection is supported Java Console • Change JAVA resource to increase the memory (JAVA Heap) to use 1 GB (1024 MB) of physical memory is recommended • Default Java Heap is 512 MB IT Operational Expectations needed: • WINS not configured on any ControlCenter Infrastructure Servers • Data Execution Prevention set to essential Windows file only • Page File set to 1.5 times physical memory installed in server • Console run with Terminal Service in Application Mode • No NIC Teaming is configured, fault tolerant mode only • EMC designated exclusions are in place for Anti-Virus and System Backup

  19. Design Expectations for Solutions Enabler Solutions Enabler installed on Production servers • AIX – 7.1.0.29 • HP – 7.1.0.29 • Solaris – 7.1.0.29 • LINUX – 7.1.0.29 • Windows – 7.1.0.29 MRLK used for Agent Servers (Latest patch on Powerlink) Patch 4717 • AIX – 7.1.0.13 • HP – 7.1.0.13 • Solaris & LINUX– 7.1.0.0 • Windows – 7.1.0.0 patched to Solutions Enabler HF 1469 which will patch SE to 7.1.0.17 • For the Server which will be managing the databases, the compatibility rule is the first three digits (Example: 7.1.0.17 to 7.1.0.x) is all that is required. • At this point in time, there is no Solutions Enabler HotFixes that address a database issues.

  20. Server Requirements

  21. Server Requirements for Infrastructure Servers • ControlCenter Server & Repository • Minimum of SPEC CINT2000 Rate (baseline) = 123 or SPEC CINT2006 Rate (baseline) = 61 - (Required) or higher SPEC # • Physical Servers only • Store(s) • Virtual Machines • 2 vCPU • 2 GB vMemory • StorageScope Server & DSS Repository • Virtual Machines • 2 vCPU • 2 GB vMemory • WLA Archiver • Virtual Machines • 2 vCPU • 2 GB vMemory

  22. Server Requirements for Agent Servers • Multi-Agent Shared Servers for TCP/IP based Agents • Virtual Machines • 2 vCPU • 2 GB vMemory • Symmetrix Agent Dedicated Servers without SMC • Physical Server - Windows • 2x 2.66 GHz Dual-Core • 4 GB Memory (min) • Physical Server - Solaris • 2x 1.5 GHz processors (SunFire v240) • 4 GB Memory (min) • Solaris 10

  23. Server Requirements for Console & PM GUI • Console Servers • Terminal Services (Application Server Mode) • Needs to be locked to 2 sessions maximum with physical server currently provided • Physical Server • 2.66 GHz Dual-Core or higher • 4 GB Memory (min) • Each server will have these components installed • Console with JAVA Heap set to 1024 • Performance Manager GUI Client • Will only support one of the two configuration below: • Configuration #1 - 2 Java consoles • Configuration #2 - 1 Java console and 1 Performance Manger console

  24. Server Setup Requirements for Operating System • Operating System • Windows 2003 Enterprise, 64-bit (recommended, not required) • 64-bit x86 multi-core processor for Physical machines recommended • 2vCPU for Virtual machines recommended • 4 GB physical Memory on Physical Server • 2 GB vMemory on Virtual Machines • Page File set to 1.5 times Physical memory, not split • Data Execution Prevention set to essential Windows file only • No WINS • For Multi-NIC servers, the primary NIC must register with DNS • Primary NIC is set to first in Binding Order • Do not use /3GB switch in boot.ini • ECCADMIN local user account can be disabled after installation, but not deleted after a ControlCenter user is assigned Administrative Privileges

  25. Break Down by Datacenter

  26. Summary This breakdown by Datacenter provides: • Summary of site specific changes • Phase I & Phase II configurations • Scalability information as it applies to each site Phase I • Upgrade from ControlCenter 6.0 to ControlCenter 6.1 UB7 • Changes to the architecture that address scalability and performance • Additional support added: • VMware ESX discovery • Symmetrix Vmax • SAN Discovery • Regional Citi Office CLARiiON discovery • Sybase 15 discovery Phase II • Additional feature functionality • Celerra NAS discovery • Performance Manager Key to reading the following slides to understand Phase I & Phase II differences • Additional Servers and Components as shown in Bold text • Managed object increases as shown in Bold text • Phase II servers and components as shown in Red Bold text

  27. Summary of changes to the existing 6.0 architecture • Server footprint is increasing to support the additional design requirements • The 12-month growth factored into this design: • 390/111 0% • Rutherford 0% • Silver Springs 0% • Georgetown 100% • Roanoke 30% • Columbus 50% • Tampa 0% • Information not provided from Citigroup: • SAN Fabric Logical Configuration • Forecasted database discovery inventory for Georgetown, TX. • VMAX Support for new VMax Arrays • NAS (Celera) Monitoring and Reporting • Implementation of Performance Manager for Symmetrix only • SAN Discovery and Reporting • Remove the Hybrid Store Configuration • EMC Engineering Recommendation • 1 Dedicated VM per Infrastructure to move the exist Store from the Server/Repository • Agent deployment design based on ControlCenter 6.1 Performance and Scalability Guidelines • Decoupling CLARiiON Storage Agents from Database Agents (Multi-use Agent Servers) • Dedicated Database Proxy Agents for ControlCenter 6.1 and n-1 versions (Phase II)

  28. Design Comparison – Current to Proposed – Phase 1 & Phase II Current Environment Proposed Environment (All) Total Servers = 94 (+31) 36 Physical Servers (+4) 59 Virtual Servers (+27) Physical Servers 6 CC Server/Repository 1 CC All-in-1 19 (+3) dedicated FC Agent Servers 3 IP-based Agent Servers 7 (-1) Remote Access Servers Virtual Machines Servers 17 (+7) Stores (move of Hybrid Stores) 6 StorageScope 29 (+13) IP-based Agent Servers 5 (+5) WLA Archiver’s (Dedicated) 2 (+2) WLA Archiver’s (Shared) • Total Servers = 64 • 32 Physical Servers • 32 Virtual Servers • Physical Servers • 6 CC Server/Repository • 1 CC All-in-1 • 16 dedicated FC Agent Servers • 3 IP-based Agent Servers • 8 Remote Access Servers • Virtual Machines Servers • 10 Stores • 6 StorageScope • 16 IP-based Agent Servers • 0 WLA Archiver’s (Dedicated) • 0 WLA Archiver’s (Shared)

  29. ControlCenter 6.1 UB7 Agent Scalability Guidelines

  30. Managed Objects – 2009 Actual

  31. Managed Objects – 2010 Growth

  32. Managed Objects - Added with Control Center 6.1

  33. Managed Objects – 2010 Design Requirements

  34. 17 ECC hosts Increase of +5 Hosts 13 ECC hosts Increase of +4 Hosts ECC 6.1 UB7 Production Deployment at Citigroup 390 Silver Spring GTDC 14 ECC hosts Increase of +6 Hosts Some additional servers stated here are not required at time of Upgrade. These servers are indicated in Red Text on the following site slides. 6ECC hosts Increase of +2 Hosts Tampa 15 ECC hosts Increase of +4 Hosts Rutherford 14 ECC hosts Increase of +5 Hosts 15 ECC hosts Increase of +5 Hosts SWDC MWDC 95 Total (+31) 36 Physical (+4) 59 Virtual (+27)

  35. 390 / 111 Summary Phase I – Upgrade • Infrastructure Servers • Move Store #1 to 1 new VM • Physical Agents Servers • 2 new Windows Servers for VMax Arrays • 1 in 390 Datacenter • 1 in 111 Wall Street Datacenter • Virtual Machine Agents Servers • 1 new Agent VM server for CC 6.0 Oracle and CMA(DB) Agents • Additional CC 6.1 Agents • VMware Agent (2) • CLARiiON Agent (1) • Oracle Agent (1) • Common Mapping Agent (1) • FCC Agent (2) • McData SMI Agent Provider (2) Phase II – Added Features • WLA Performance Manager • 1 VM Server for WLA Archiver • Performance Manager GUI added to Remote Access Server • Remove the Agent Server running the CC 6.0 DB Agents Growth • 12-month growth – 0% Change in Managed Objects • VMax • CLARiiON • VMware • SAN Agent on Production Servers • Upgrade Agents to CC 6.1 UB7 • Upgrade Solutions Enabler (per Slide 19)

  36. Phase I & Phase II ECC Deployment Large Configuration Virtual 390 : Capacity: 2,050 Hosts 262,400 Host Device Logical Paths; 175 arrays; 1,200 DBs; 75 ESX’s 132 switches, 8,448 Ports Physical 6.1 Deployment – Phase I & II 6.0 Deployment - Existing ECC Server 6.1 UB7 Repository SPECint_rate_base2006 - 108 ECC Server 6.0 Repository Store #1 • 2010 Managed Objects • Host Device Logical • Paths 61,493 • Arrays53 • Symmetrix 32 • VMAX2 • CLARiiON15 • HDS 4 • Switches 52/6360 • ESX (SAN) 75 Max • Databases 246 • Sybase 213 • Oracle 20 • SQL Server 13 DSS: StorageScope/DSS ST03: Store #1 ST04: Store #2 ST05: Store #3 • CurrentManaged Objects • Host Device Logical • Paths 61,493 • Arrays 48 • Switches 0 • Symmetrix 32 • VMAX 0 • CLARiiON 12 • HDS 4 • ESX 0 • Databases 246 • Sybase 213 • Oracle 20 • SQL Server 13 DSS: StorageScope/DSS ST04: Store #2 ST05: Store #3 2 vCPU 2 GB vMemory AG01: HDS, CLARiiON, FCC, SMI Agent Provider, VMWARE AG02: CLARiiON, FCC, SMI Agent Provider, VMWARE AG03: CMA (DB), Oracle, FCC, SMI Agent Provider AG04: CMA (DB) (6.0), Oracle (6.0) AG05: WLA AG01: HDS, Oracle AG02: CLARiiON, CMA AG03:No Agents Installed 2 vCPU 2 GB vMemory Symmetrix Agent #1 Symmetrix Agent #2 Symmetrix Agent #1 Symmetrix Agent #2 Symmetrix Agent #5 ** Symmetrix Agent #3 Symmetrix Agent #4 (111 Wall St.) Symmetrix Agent #3 Symmetrix Agent #4 (111 Wall St.) Symmetrix Agent #6 ** (111 Wall St.) ** New VMAX Mgmt and Windows OS Console Remote Access Server Console & Performance, Manager GUI

  37. Architectural Factors (390/111) • The total number of Database Agents shown in this table does not represent the actual number of DG Agents to be deployed. This is for planning only. • As Sybase 15 is discovered, the discovery will be via proxy. • This will require an increase of CMA proxy agent to 6.

  38. Rutherford Summary Phase I – Upgrade • Infrastructure Servers • Move Store #1 to 1 new VM • Physical Agents Servers • No new servers • Virtual Machine Agents Servers • 1 new Agent VM server for CC 6.0 Oracle and CMA(DB) Agents • 1 new Agent VM server for CC 6.1 Oracle and CMA (DB) Agents • Additional CC 6.1 Agents • VMware Agent (2) • Oracle Agent (1) • Common Mapping Agent (1) • FCC Agent (3) • McData SMI Agent Provider (3) Phase II – Added Features • WLA Performance Manager • 1 VM Server for WLA Archiver • Performance Manager GUI added to Remote Access Server • Remove the Agent Server running the CC 6.0 DB Agents Growth • 12-month growth – 0% Change in Managed Objects • VMware • SAN Agent on Production Servers • Upgrade Agents to CC 6.1 UB7 • Upgrade Solutions Enabler (per Slide 19)

  39. RUT : Capacity: 2,050 Hosts 262,400 Host Device Logical Paths; 175 arrays; 1,200 DBs; 75 ESX’s 132 switches, 8,448 Ports Phase I & Phase II ECC Deployment Large Configuration Virtual Physical 6.1 Deployment – Phase I & II 6.0 Deployment - Existing ECC Server 6.1 UB7 Repository SPECint_rate_base2006 - 108 ECC Server Repository Store #1 • 12 Month Forecast • Managed Objects • Host Device Logical • Paths 41,833 • Arrays 57 • Symmetrix 28 • VMAX 0 • CLARiiON 26 • HDS 3 • Switches 47/5228 • ESX (SAN) 75 Max • Databases 166 • Sybase 133 • Oracle 12 • SQL Server 21 DSS: StorageScope/DSS ST03: Store #1 ST04: Store #2 ST05: Store #3 2 vCPU 2 GB vMemory DSS: StorageScope/DS ST04: Store #2 ST05: Store #3 • Current • Managed Objects • Host Device Logical • Paths 41,833 • Arrays 57 • Symmetrix 28 • VMAX 0 • CLARiiON 26 • HDS 3 • Switches 0 • ESX 0 • Databases 166 • Sybase 133 • Oracle 12 • SQL Server 21 AG01:HDS, CLARiiON, FCC, SMI Agent Provider, VMWARE AG02: CLARiiON, FCC, SMI Agent Provider, VMWARE AG03: CLARiiON, FCC, SMI Agent Provider AG04: CMA (DB), Oracle AG05: CMA (DB) (6.0), Oracle (6.0) AG06: WLA AG01 CLARiiON, HDS, Oracle AG02: CLARiiON, Mapping AG03: CLARiiON 2 vCPU 2 GB vMemory Symmetrix Agent Symmetrix Agent Symmetrix Agent Symmetrix Agent Symmetrix Agent Symmetrix Agent Console Remote Access Server Console & Performance, Manager GUI

  40. Architectural Factors (Rutherford) • The total number of Database Agents shown in this table does not represent the actual number of DG Agents to be deployed. This is for planning only. • As Sybase 15 is discovered, the discovery will be via proxy. • This will require an increase of CMA proxy agent to 6.

  41. Silver Springs Summary Phase I – Upgrade • Infrastructure Servers • Move Store #1 to 1 new VM • Physical Agents Servers • No new servers • Virtual Machine Agents Servers • 1 new Agent VM server for CC 6.0 Oracle and CMA (DB) Agents • 1 new Agent VM server for CC 6.1 Oracle and CMA (DB) Agents • Additional CC 6.1 Agents • VMware Agent (2) • Centera Agent (1) • Oracle Agent (1) • Common Mapping Agent (1) • FCC Agent (3) • McData SMI Agent Provider (3) Phase II – Added Features • WLA Performance Manager • 1 VM Server for WLA Archiver • Performance Manager GUI added to Remote Access Server • Remove the Agent Server running the CC 6.0 DB Agents Growth • 12-month growth – 0% Change in Managed Objects • VMware • SAN Agent on Production Servers • Upgrade Agents to CC 6.1 UB7 • Upgrade Solutions Enabler (per Slide 19)

  42. SS: Capacity: 2,050 Hosts 262,400 Host Device Logical Paths; 175 arrays; 1,200 DBs; 75 ESX’s 132 switches, 8,448 Ports Phase I & Phase II ECC Deployment Large Configuration Virtual Physical 6.1 Deployment – Phase I & II 6.0 Deployment - Existing ECC Server 6.1 UB7 Repository SPECint_rate_base2006 - 108 ECC Server Repository Store #1, Centerra DSS: StorageScope/DSS ST04: Store #2 ST05: Store #3 DSS: StorageScope/DSS ST03: Store #1 ST04: Store #2 ST05: Store #3 • Current • Managed Objects • Host Device Logical • Paths 41,833 • Arrays 33 • Symmetrix 14 • CLARiiON 9 • HDS 10 • Switches 0 • ESX 0 • Databases 53 • Sybase 12 • Oracle 9 • SQL Server 32 • 12 Month Forecast • Managed Objects • Host Device Logical • Paths 67,346 • Arrays 33 • Symmetrix 14 • CLARiiON 9 • HDS 10 • Switches 64/8028 • ESX (SAN) 75 Max • Databases 53 • Sybase 12 • Oracle 9 • SQL Server 32 2 vCPU 2 GB vMemory AG01: Centera, CLARiiON, FCC, SMI Agent Provider, VMWARE AG02:HDS, FCC, SMI Agent Provider, VMWARE AG03: CMA (DB), Oracle, FCC, SMI Agent Provider AG04: CMA (DB) (6.0), Oracle (6.0) AG05: WLA AG01: CLARiiON, Oracle AG02: HDS, CMA 2 vCPU 2 GB vMemory Symmetrix Agent Symmetrix Agent Symmetrix Agent Symmetrix Agent Remote Access Server Console & Performance, Manager GUI Console CMA, Oracle

  43. Architectural Factors (Silver Spring) • The total number of Database Agents shown in this table does not represent the actual number of DG Agents to be deployed. This is for planning only. • As Sybase 15 is discovered, the discovery will be via proxy. • This will require an increase of CMA proxy agent to 6.

  44. George Town Summary Phase I – Upgrade • Infrastructure Servers • Physical Server is below P&S SPEC. (P&S Engineering has approved this server) • Move Store #1 to 1 new VM • Physical Agents Servers • No new servers • Virtual Machine Agents Servers • 1 new Agent VM server for CC 6.0 Oracle and CMA (DB) Agents – Missing DB information, this VM may not be needed • Additional CC 6.1 Agents • VMware Agent (1) • CLARiiON Agent (1) • FCC Agent (2) Phase II – Added Features • Additional VM Servers for CC 6.1 Agents (4) • Oracle Agent (1) • Common Mapping Agent (1) • NAS Agent (Celerra) (4) • WLA Performance Manager • 1 VM Server for WLA Archiver • Performance Manager GUI added to Remote Access Server • Remove the Agent Server running the CC 6.0 DB Agents Growth • 12-month growth – 100% • No Database information was provided by Citi Change in Managed Objects • Host Device Logical Paths, VMware • Symmetrix, CLARiiON, Celerra (NAS) • SAN Agent on Production Servers • Upgrade Agents to CC 6.1 UB7 • Upgrade Solutions Enabler (per Slide 19)

  45. GTDC: Capacity: 2,050 Hosts 262,400 Host Device Logical Paths; 175 arrays; 1,200 DBs; 75 ESX’s 132 switches, 8,448 Ports Phase I & Phase II ECC Deployment Large Configuration Virtual Physical 6.1 Deployment – Phase I & II 6.0 Deployment - Existing ECC Server 6.1 UB7 Repository SPECint_rate_base2006 – 56.5 ECC Server Repository Store #1 DSS: StorageScope/DSS ST03: Store #1 ST04: Store #2 2 vCPU 2 GB vMemory • 12 Month Forecast • Managed Objects • Host Device Logical • Paths 20,934 • Arrays 78 • Symmetrix 8 • VMAX 0 • CLARiiON 22 • NAS(Celerra) 46 • Switches 16/2100 • ESX (SAN) 75 max • Databases Data not Available DSS: StorageScope/DSS ST03: Store #2 • Current • Managed Objects • Host Device Logical • Paths 10,467 • Arrays 15 • Symmetrix 4 • CLARiiON 11 • Switches 0 • ESX 0 • Databases Data not Available AG01: CLARiiON,Oracle, FCC, VMWARE AG02: CMA (DB),VMWARE , CLARiiON, FCC, AG03: NAS (Celerra) AG04: CMA (DB) (6.0) , Oracle (6.0) AG05: WLA, NAS (Celerra) AG06: NAS (Celerra) AG07: NAS (Celerra) AG01: CLARiiON, Oracle AG02: Mapping, VMWARE 2 vCPU 2 GB vMemory Symmetrix Agent Symmetrix Agent Symmetrix Agent Symmetrix Agent NOTE: Array increase due to Celerra arrays Remote Access Server Console & Performance, Manager GUI Console

  46. Architectural Factors (GTDC)

  47. South West Summary Phase I – Upgrade • Infrastructure Servers • Move Store #1 to 1 new VM • Add Store #4 to 1 new VM • Physical Agents Servers • 1 new Windows Server for VMax Arrays • Virtual Machine Agents Servers • 1 new Agent VM server for CC 6.0 Oracle and CMA (DB) • Additional CC 6.1 Agents • VMware Agent (2) • CLARiiON Agent (1) • HDS Agent (2) • FCC Agent (3) • McData SMI Agent Provider (3) Phase II – Added Features • WLA Performance Manager • 1 VM Server for WLA Archiver • Performance Manager GUI added to Remote Access Server • Remove the Agent Server running the CC 6.0 DB Agents Growth • 12-month growth – 30% Change in Managed Objects • Host Device Logical Paths, VMware • Symmetrix, CLARiiON, HDS • SAN • Databases Agent on Production Servers • Upgrade Agents to CC 6.1 UB7 • Upgrade Solutions Enabler (per Slide 19)

  48. SWDC: Capacity: 2,050 Hosts 262,400 Host Device Logical Paths; 175 arrays; 1,200 DBs; 75 ESX’s 132 switches, 8,448 Ports Phase I & Phase II ECC Deployment Large Configuration Virtual Physical 6.1 Deployment – Phase I & II 6.0 Deployment - Existing ECC Server 6.1 UB7 Repository SPECint_rate_base2006 - 108 ECC Server Repository Store #1, Centera DSS: StorageScope/DSS ST03: Store #1 ST04: Store #2 ST05: Store #3 ST06: Store #4 (new) DSS: StorageScope/DSS ST04: Store #2 ST05: Store #3 • Current • Managed Objects • Host Device Logical • Paths 166,383 • Arrays 66 • Symmetrix 26 • CLARiiON 28 • HDS 12 • Switches 0 • ESX 0 • Databases 52 • Sybase 20 • Oracle 12 • SQL Server 20 • 12 Month Forecast • Managed Objects • Host Device • Logical Paths 216,298 • Arrays 90 • Symmetrix 34 • VMAX 4 • CLARiiON 36 • HDS 16 • Switches 54/8584 • ESX (SAN) 75 Max • Databases 68 • Sybase 26 • Oracle 16 • SQL Server 26 2 vCPU 2 GB vMemory AG01: HDS, CLARiiON, FCC, SMI Agent Provider, VMWARE AG02:CLARiiON,HDS, FCC, SMI Agent Provider, VMWARE AG03: CLARiiON, HDS CMA (DB), Oracle, FCC, SMI Agent Provider, Centera AG04: CMA (DB) (6.0), Oracle (6.0) AG05: WLA AG01: CLARiiON, Oracle AG02: CLARiiON, HDS, CMA AG03: No Agnents 2 vCPU 2 GB vMemory ** New VMAX Mgmt and Windows OS Symmetrix Agent Symmetrix Agent Symmetrix Agent Symmetrix Agent Symmetrix ** Agent Console CMA, Oracle Console Remote Access Server Console & Performance, Manager GUI

  49. Architectural Factors (SWDC) • The total number of Database Agents shown in this table does not represent the actual number of DG Agents to be deployed. This is for planning only. • As Sybase 15 is discovered, the discovery will be via proxy. • This will require an increase of CMA proxy agent to 6.

  50. Mid West Summary Phase I – Upgrade • Infrastructure Servers • Move Store #1 to 1 new VM • Physical Agents Servers • 1 new Windows Server for VMax Arrays • Virtual Machine Agents Servers • 1 new Agent VM server for CC 6.0 Oracle and CMA (DB) • Additional CC 6.1 Agents • CLARiiON Agent (2) • Oracle Agent (1) • Common Mapping Agent (1) • FCC Agent (2) Phase II – Added Features • WLA Performance Manager • 1 VM Server for WLA Archiver • Performance Manager GUI added to Remote Access Server • Remove the Agent Server running the CC 6.0 DB Agents • Physical Agents Servers • -1 agent server to be decommissioned Growth • 12-month growth – 50% Change in Managed Objects • Host Device Logical Paths, VMware • Symmetrix, CLARiiON, HDS • SAN • Databases Agent on Production Servers • Upgrade Agents to CC 6.1 UB7 • Upgrade Solutions Enabler (per Slide 19)

More Related