CommandCentral 5.2 RU3 Hardware and Software Compatibility List

Transcription

1 CommandCentral 5.2 RU3 Hardware and Software Compatibility List Fri Feb Documentation version CommandCentral Storage System and OS Requirements Switches Storage Devices HBAs Miscellaneous Devices Software Compatibility Unified Agent Agentless SAN device vendor hardware and software information frequently changes. It is strongly recommended that you download the latest version of this document from the Symantec Web site: TechNotes referenced in this document are available at: Copyright 2012 Symantec Corporation. All rights reserved. Symantec, the Symantec logo, Veritas, CommandCentral, NetBackup, SANPoint, SANPoint Control, and Storage Foundation are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. 1

2 CommandCentral Storage - System and OS Requirements Component OS* System+ Management Server Standard Agent Push Install Utility Browser Support Microsoft Windows 2000 (SP3 or later) Server, Advanced Server, Datacenter Server Microsoft Windows 2003 Server: Standard Edition, Datacenter Edition (32- and 64-), Enterprise Edition (32- and 64-), Web Edition Microsoft Windows 2008 R2 Server: Standard Edition, Datacenter Edition, Enterprise Edition, Web Edition (32 and 64-) Microsoft Windows 2008 Server: Standard Edition, Datacenter Edition, Enterprise Edition, Web Edition (32 and 64-) Solaris 8, 9,10 *2&*8 VMware Windows Guest OS - Windows 2003 server (32- and 64 -), Windows 2008 server (32- and 64-) HP-UX 11i v1 (11.11) HP-UX 11i v2 (11.23) HP-UX 11i v (11.23 PI) HP-UX 11i v3 (11.31 PI) *5 HP-UX 11i v3 (11.31) *5 IBM AIX 5.2 *3 IBM AIX 5.3 *7 IBM AIX 6.1 *7 IBM AIX 7.1 TL1 SP1 Red Hat Linux Advanced Server 3.0 (32-) Red Hat Linux Advanced Server 4.0 (32) Red Hat Linux Enterprise Server 3.0 (32-) Red Hat Linux Enterprise Server 4.0 (32-,64-) Red Hat Linux Enterprise Server 5.0 (32-, 64-) *6 Red Hat Linux Enterprise Server 6.0 (32-, 64-) *6 Solaris 8, 9,10 *2 Suse Linux Enterprise Server 10 (32-, 64-) *5&*6 Suse Linux Enterprise Server 9 (32-, 64-) *5&*6 1GHz Quad processor + 8GB RAM (16GB for CommandCentral Storage + Storage Change Manager) Pentium-based servers: Pentium 4 64-: Xeon/Opteron 1GHz Quad processor + 8GB RAM (16GB for CommandCentral Storage + Storage Change Manager) Pentium-based servers: Pentium 4 64-: Xeon/Opteron 1 GHz + 8GB RAM (16GB for CommandCentral Storage + Storage Change Manager) 1 GHz (x86 processor) or 1.4 GHz (x64 processor) 64-: Xeon/Opteron 1GHz Quad processor + 8GB RAM (16GB for CommandCentral Storage + Storage Change Manager) Pentium-based servers: Pentium 4 64-: Xeon/Opteron 1GHz UltraSPARC IIIi dual processors + 8GB RAM (16GB for CommandCentral Storage + Storage Change Manager) ESX server 3.5 or later, Guest OS should have a minimum of 2 processors + 8GB RAM (16GB for CommandCentral Storage + Storage Change Manager) PA-RISC 2.0 and PCI HBA based systems: Superdome, V Class, N Class, L Class, 400/500, rp-series + 16/512MB RAM Itanium 2 based systems: Integrity servers + 16/512MB RAM PA-RISC 2.0 and PCI HBA based systems: Superdome, V Class, N Class, L Class, 400/500, rp-series + 16/512MB RAM PA-RISC 2.0 and PCI HBA based systems: Superdome, rp-series + 16/512MB RAM Itanium 2 based systems: Integrity servers + 16/512MB RAM Pseries + 16/512MB RAM P5 5xx + 16/512MB RAM P5 5xx + 16/512MB RAM P5 5xx + 16/512MB RAM 433 MHz Intel x86 equivalent + 256/512MB RAM 433 MHz Intel x86 equivalent + 256/512MB RAM 433 MHz Intel x86 equivalent + 256/512MB RAM 433 MHz Intel x86 equivalent + 256/512MB RAM 433 MHz Intel x86 equivalent + 256/512MB RAM 433 MHz Intel x86 equivalent + 256/512MB RAM Ultra 5 or higher, including SPARC clone equivalents from Fujitsu + 256/512MB RAM *1 433 MHz Intel x86 equivalent + 256/512MB RAM 433 MHz Intel x86 equivalent + 256/512MB RAM Windows 2000 (SP3 or later) Server, Advanced Server, Datacenter Server 733 MHz Pentium /512MB RAM 1 Windows 2003 Server: Standard Edition, Datacenter Edition (32 and 64-), Enterprise Edition (32 and 64-), Web Edition Windows 2008 Server: Standard Edition, Datacenter Edition, Enterprise Edition, Web Edition (32 and 64-) *5 Windows 2000 (SP3 or later) Server, Advanced Server, Datacenter Server Windows 2003 Server: Standard Edition, Datacenter Edition (32 and 64-), Enterprise Edition (32 and 64-), Web Edition Windows 2008 Server: Standard Edition, Datacenter Edition, Enterprise Edition, Web Edition (32 and 64-) 733 MHz + 256/512MB RAM 1 Pentium-based servers: Pentium 4 64-: Xeon/Opteron 1 GHz + 512MB RAM 1 GHz (x86 processor) or 1.4 GHz (x64 processor) 64-: Xeon/Opteron 733 MHz Pentium MB RAM 733 MHz + 512MB RAM Pentium-based servers: Pentium : Xeon/Opteron 1 GHz + 512MB RAM 1 GHz (x86 processor) or 1.4 GHz (x64 processor) 64-: Xeon/Opteron Solaris Mozilla 1.7 Windows Microsoft Internet Explorer 6.x, 7.x Mozilla Firefox 1.07, 1.5, x or 3.0 2

3 Control Host Solaris 9, 10 Windows server 2000 (SP3 or Later) editions include: Server, Advanced Server, and Datacenter Server Windows server 2003 editions include: 32-: Standard,Datacenter, Enterprise, and Web; 64- (Xeon/Opteron): Datacenter and Enterprise Windows server 2008 editions include (32- and 64-): Standard, Datacenter, Enterprise, and Web SPARC MB RAM 733MHz + 512MB RAM 733MHz + 512MB RAM 1GHZ + 512MB RAM Minimum recommended configuration. Memory requirement is in addition to what is already being consumed by other applications on the system. *1 For Memory Requirements for CommandCentral Storage managed hosts, the first number is without Array Management, the second is with Array Management. *2 CommandCentral Storage package is not recommended to be installed on non-global zones on the Solaris OS platform. *3 CommandCentral Storage requires ML7 or later for AIX 5.2 and ML3 or later for AIX 5.3. *5 NetApp Unified Storage Discovery capabilities are not supported on Red Hat Linux Enterprise Server 5.0, Suse Linux Enterprise Server 9 & 10, HPUX 11i v3 and VMware ESX platforms. *6 CommandCentral Managed Host is not supported and will fail to install if SE Linux is enabled on Linux systems. *7 For AIX hosts with LPARs, Virtual devices are not supported. *8 SUN T-series servers are not recommended. * Refer to Release Notes to verify appropriate patch levels CommandCentral Enterprise Reporter System and OS requirements : 1GHz Quad processor + 12GB RAM Pentium-based servers for Windows 2003 SP2/Windows 2008 SP1 32- servers 1GHz UltraSPARC IIIi dual processors + 12GB RAM for Solaris 9, Solaris 10 servers 3

4 CommandCentral Storage - Switches Switch Access Gateway 200E Model Firmware Ancillary SW OS Platform Features SNMP MIB 5.3, 6.1, 6.2, 6.4.x Brocade Integrated SMI Agent DCFM , , , Monitoring Alerting -- Not supported Notes Access Gateway discovery is supported via Brocade DCFM 10.4.x Integrated SMI Agent. Discovery of Access Gateway via Brocade Host-Based SMI Agent is not supported. Other compatible models like, 300, 5100, 4012, 4016, 4018, 4020, 4024, 4424, 5424, 5450, 5460, 5470, 5480, 8000, which supports Access Gateway should get discovered by CCS but we have not qualified them in-house. CommandCentral 5.2 has SMI-S only configuration option for Brocade. Discovery of switches using Brocade API was removed from the CommandCentral 5.1 onwards as Brocade has EOLed these API interfaces. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from API to SMI-S. Users need to remove the old API configuration from the CommandCentral Console and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. Brocade DCX Backbone 6.0.1a, 6.1.0c, 6.1.0f, 6.1.0j, 6.1.1, 6.1.1d, 6.1.2b, 6.2.0, 6.2.0g, 6.2.1b, 6.2.2, 6.2.2a, 6.3.0b, 6.3.0c, 6.3.1, 6.3.1c, 6.4.0b, 6.4.0c, 6.4.1, 6.4.1b, 7.0.0a, 7.0.0b Minimum version of FOS firmware for Proxy switch is 5.3.1a, 6.x is the recommended version (SMI-S requirement). For the Brocade SMIS Agent v and above, the minimum Proxy switch firmware is FOS 6.x. Use the Brocade SMIS Agent b for Proxy switch with 5.3.1a or firmware. Always pick the highest version of firmware in the Fabric for the proxy switch. Users may need to upgrade switch firmware while they move from API mehod of discovery to SMIS discovery method. Install SMI-S agent(s) on Windows or Solaris hosts Proxy switches are configured using the SMI-S agent GUI Proxy switches must have user credentials with "admin" permission CommandCentral discovers these Brocade switches, as well as their role in the fabric (principal/subordinate), total/free ports, port status, objects connected to each port, zoning information, and more. ~MPR supports basic Discovery. No monitoring support Performance monitoring is not supported with SNMP V3. Fabric OS v6.4.0x is supported with SMI-S agent Please refer to the Documentation for supported Switch Firmware and Models with Brocade DCFM 10.4.x Integrated SMI Agent. Brocade Virtual Switch Discovery is supported only with DCFM / BNA. 4

5 CommandCentral Storage - Switches Switch SilkWorm Model Firmware Ancillary SW OS Platform Features SNMP MIB 4.4.0b, d, e, a, b, 5.0.3, 5.0.4, 5.0.5c, 5.0.5d, 5.0.5f Monitoring Alerting Notes CommandCentral 5.2 has SMI-S only configuration option for Brocade. Discovery of switches using Brocade API was removed from the CommandCentral 5.1 onwards as Brocade has EOLed these API interfaces. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from API to SMI-S. Users need to remove the old API configuration from the CommandCentral Console and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. Minimum version of FOS firmware for Proxy switch is 5.3.1a, 6.x is the recommended version (SMI-S requirement). For the Brocade SMIS Agent v and above, the minimum Proxy switch firmware is FOS 6.x. Use the Brocade SMIS Agent b for Proxy switch with 5.3.1a or firmware. Always pick the highest version of firmware in the Fabric for the proxy switch. Users may need to upgrade switch firmware while they move from API mehod of discovery to SMIS discovery method. Install SMI-S agent(s) on Windows or Solaris hosts Proxy switches are configured using the SMI-S agent GUI Proxy switches must have user credentials with "admin" permission CommandCentral discovers these Brocade switches, as well as their role in the fabric (principal/subordinate), total/free ports, port status, objects connected to each port, zoning information, and more. ~MPR supports basic Discovery. No monitoring support Performance monitoring is not supported with SNMP V3. Please refer to the Documentation for supported Switch Firmware and Models with Brocade DCFM 10.4.x Integrated SMI Agent. SilkWorm 200E 5.0.1, 5.0.3, 5.0.5c, 5.0.5d, 5.0.5f, 5.1.0, 5.1.0a, 5.1.0d, 5.2.0a, 5.2.1b, 5.3.0, 5.3.1a, 5.3.1b, 5.3.2, 6.0.0, 6.0.1a, 6.1.0, 6.1.0c, 6.1.0f, 6.1.0j, 6.1.1, 6.1.1d, 6.1.2b, 6.2.0, 6.2.0g, 6.2.1b, 6.2.2, 6.2.2a 5

6 CommandCentral Storage - Switches Switch SilkWorm SilkWorm Silkworm 300 Model Firmware Ancillary SW OS Platform Features SNMP MIB 2.6.1, 2.6.1a, b, c 2.6.2a, b, c, d 4.4.0b, d, e 5.0.1a, b, 5.0.3, 5.0.4, 5.0.5c, 5.0.5d, 5.0.5f, 5.1.0, 5.1.0a, 5.1.0d, 5.2.0a, 5.2.1b, 5.3.0, 5.3.1a, 5.3.1b, a, 6.1.0c, 6.1.0f, 6.1.0j, 6.1.1, 6.1.1d, 6.1.2b, 6.2.0, 6.2.0g, 6.2.1b, 6.2.2, 6.2.2a, 6.3.0b, 6.3.0c, 6.3.1, 6.3.1c, 6.4.0b, 6.4.0c, 6.4.1, 6.4.1b, 7.0.0a, 7.0.0b Monitoring Alerting Notes CommandCentral 5.2 has SMI-S only configuration option for Brocade. Discovery of switches using Brocade API was removed from the CommandCentral 5.1 onwards as Brocade has EOLed these API interfaces. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from API to SMI-S. Users need to remove the old API configuration from the CommandCentral Console and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. Minimum version of FOS firmware for Proxy switch is 5.3.1a, 6.x is the recommended version (SMI-S requirement). For the Brocade SMIS Agent v and above, the minimum Proxy switch firmware is FOS 6.x. Use the Brocade SMIS Agent b for Proxy switch with 5.3.1a or firmware. Always pick the highest version of firmware in the Fabric for the proxy switch. Users may need to upgrade switch firmware while they move from API mehod of discovery to SMIS discovery method. Install SMI-S agent(s) on Windows or Solaris hosts Proxy switches are configured using the SMI-S agent GUI Proxy switches must have user credentials with "admin" permission CommandCentral discovers these Brocade switches, as well as their role in the fabric (principal/subordinate), total/free ports, port status, objects connected to each port, zoning information, and more. ~MPR supports basic Discovery. No monitoring support Performance monitoring is not supported with SNMP V3. Fabric OS v6.4.0x is supported with SMI-S agent Please refer to the Documentation for supported Switch Firmware and Models with Brocade DCFM 10.4.x Integrated SMI Agent. SilkWorm 3200, , 3.1.1, 3.1.1b, d 3.1.2, 3.1.3, 3.1.3b 3.2.0a,

7 CommandCentral Storage - Switches Switch SilkWorm 3250, 3850 Model Firmware Ancillary SW OS Platform Features SNMP MIB 4.4.0b, d, e 5.0.1a, b, 5.0.3, 5.0.4, 5.0.5c, 5.0.5d, 5.0.5f, 5.1.0, 5.1.0a, 5.1.0d, 5.2.0a, 5.2.1b, 5.3.0, 5.3.1a, 5.3.1b, Monitoring Alerting Notes CommandCentral 5.2 has SMI-S only configuration option for Brocade. Discovery of switches using Brocade API was removed from the CommandCentral 5.1 onwards as Brocade has EOLed these API interfaces. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from API to SMI-S. Users need to remove the old API configuration from the CommandCentral Console and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. Minimum version of FOS firmware for Proxy switch is 5.3.1a, 6.x is the recommended version (SMI-S requirement). For the Brocade SMIS Agent v and above, the minimum Proxy switch firmware is FOS 6.x. Use the Brocade SMIS Agent b for Proxy switch with 5.3.1a or firmware. Always pick the highest version of firmware in the Fabric for the proxy switch. Users may need to upgrade switch firmware while they move from API mehod of discovery to SMIS discovery method. Install SMI-S agent(s) on Windows or Solaris hosts Proxy switches are configured using the SMI-S agent GUI Proxy switches must have user credentials with "admin" permission CommandCentral discovers these Brocade switches, as well as their role in the fabric (principal/subordinate), total/free ports, port status, objects connected to each port, zoning information, and more. ~MPR supports basic Discovery. No monitoring support Performance monitoring is not supported with SNMP V3. Please refer to the Documentation for supported Switch Firmware and Models with Brocade DCFM 10.4.x Integrated SMI Agent. SilkWorm b, d, e, a, b, 5.0.3, 5.0.4, 5.0.5c, 5.0.5d, 5.0.5f, 5.1.0, 5.1.0a, 5.1.0d, 5.2.0a, 5.2.1b, 5.3.0, 5.3.1a, 5.3.1b, Brocade SMI provider v b, v , v , v (Refer the Notes section for Proxy switch firmware compatibility with SMI provider) Brocade Integrated SMI Agent DCFM , , , Brocade Network Advisor 11.0, 11.1, Windows 2003,Windows 2000,Windows 2008,Solaris 8,Solaris 9,Solaris 10 Discovery FA MIB 3.0 FE MIB Brocade FC MIB 7

8 CommandCentral Storage - Switches Switch SilkWorm 4100 Model Firmware Ancillary SW OS Platform Features SNMP MIB 4.4.0b, d, e 5.0.1a, b, 5.0.3, 5.0.4, 5.0.5c, 5.0.5d, 5.0.5f, 5.1.0, 5.1.0a, 5.1.0d, 5.2.0a, 5.2.1b, 5.3.0, 5.3.1a, 5.3.1b, 5.3.2, 6.0.0, 6.0.1a, 6.1.0, 6.1.0c, 6.1.0f, 6.1.0j, 6.1.1, 6.1.1d, 6.1.2b, 6.2.0, 6.2.0g, 6.2.1b, 6.2.2, 6.2.2a, 6.3.0b, 6.3.0c, 6.3.1, 6.3.1c, 6.4.0b, 6.4.0c, 6.4.1, 6.4.1b Monitoring Alerting Notes CommandCentral 5.2 has SMI-S only configuration option for Brocade. Discovery of switches using Brocade API was removed from the CommandCentral 5.1 onwards as Brocade has EOLed these API interfaces. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from API to SMI-S. Users need to remove the old API configuration from the CommandCentral Console and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. Minimum version of FOS firmware for Proxy switch is 5.3.1a, 6.x is the recommended version (SMI-S requirement). For the Brocade SMIS Agent v and above, the minimum Proxy switch firmware is FOS 6.x. Use the Brocade SMIS Agent b for Proxy switch with 5.3.1a or firmware. Always pick the highest version of firmware in the Fabric for the proxy switch. Users may need to upgrade switch firmware while they move from API mehod of discovery to SMIS discovery method. Install SMI-S agent(s) on Windows or Solaris hosts Proxy switches are configured using the SMI-S agent GUI Proxy switches must have user credentials with "admin" permission CommandCentral discovers these Brocade switches, as well as their role in the fabric (principal/subordinate), total/free ports, port status, objects connected to each port, zoning information, and more. ~MPR supports basic Discovery. No monitoring support Performance monitoring is not supported with SNMP V3. Fabric OS v6.4.0x is supported with SMI-S agent Please refer to the Documentation for supported Switch Firmware and Models with Brocade DCFM 10.4.x Integrated SMI Agent. SilkWorm c, 5.0.5d, 5.0.5f, 5.1.0, 5.1.0a, 5.1.0d, 5.2.0a, 5.2.1b, 5.3.0, 5.3.1a, 5.3.1b, 5.3.2, 6.0.0, 6.0.1a, 6.1.0, 6.1.0c, 6.1.0f, 6.1.0j, 6.1.1, 6.1.1d, 6.1.2b, 6.2.0, 6.2.0g, 6.2.1b, 6.2.2, 6.2.2a, 6.3.0b, 6.3.0c, 6.3.1, 6.3.1c, 6.4.0b, 6.4.0c, 6.4.1, 6.4.1b 8

9 CommandCentral Storage - Switches Switch Silkworm 4900 Model Firmware Ancillary SW OS Platform Features SNMP MIB 5.1.0, 5.1.0a, 5.1.0d, 5.2.0a, 5.2.1b, 5.3.0, 5.3.1a, 5.3.1b, 5.3.2, 6.0.0, 6.0.1a, 6.1.0, 6.1.0c, 6.1.0f, 6.1.0j, 6.1.1, 6.1.1d, 6.1.2b, 6.2.0, 6.2.0g, 6.2.1b, 6.2.2, 6.2.2a, 6.3.0b, 6.3.0c, 6.3.1, 6.3.1c, 6.4.0b, 6.4.0c, 6.4.1, 6.4.1b Monitoring Alerting Notes CommandCentral 5.2 has SMI-S only configuration option for Brocade. Discovery of switches using Brocade API was removed from the CommandCentral 5.1 onwards as Brocade has EOLed these API interfaces. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from API to SMI-S. Users need to remove the old API configuration from the CommandCentral Console and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. Minimum version of FOS firmware for Proxy switch is 5.3.1a, 6.x is the recommended version (SMI-S requirement). For the Brocade SMIS Agent v and above, the minimum Proxy switch firmware is FOS 6.x. Use the Brocade SMIS Agent b for Proxy switch with 5.3.1a or firmware. Always pick the highest version of firmware in the Fabric for the proxy switch. Users may need to upgrade switch firmware while they move from API mehod of discovery to SMIS discovery method. Install SMI-S agent(s) on Windows or Solaris hosts Proxy switches are configured using the SMI-S agent GUI Proxy switches must have user credentials with "admin" permission CommandCentral discovers these Brocade switches, as well as their role in the fabric (principal/subordinate), total/free ports, port status, objects connected to each port, zoning information, and more. Fabric and Zoning discovery of switches requires an out-of-band connection. ~MPR supports basic Discovery. No monitoring support Performance monitoring is not supported with SNMP V3. Fabric OS v6.4.0x is supported with SMI-S agent Please refer to the Documentation for supported Switch Firmware and Models with Brocade DCFM 10.4.x Integrated SMI Agent. Silkworm , 5.3.1a, 5.3.1b, 5.3.2, 6.0.0, 6.0.1a, 6.1.0, 6.1.0c, 6.1.0f, 6.1.0j, 6.1.1, 6.1.1d, 6.1.2b, 6.2.0, 6.2.0g, 6.2.1b, 6.2.2, 6.2.2a, 6.3.0b, 6.3.0c, 6.3.1, 6.3.1c, 6.4.0b, 6.4.0c, 6.4.1, 6.4.1b 9

10 CommandCentral Storage - Switches Switch Silkworm 5100 Silkworm 5300 Model Firmware Ancillary SW OS Platform Features SNMP MIB 6.0.1a, 6.1.0c, 6.1.0f, 6.1.0j, 6.1.1, 6.1.1d, 6.1.2b, 6.2.0, 6.2.0g, 6.2.1b, 6.2.2, 6.2.2a, 6.3.0b, 6.3.0c, 6.3.1, 6.3.1c, 6.4.0b, 6.4.0c, 6.4.1, 6.4.1b, 7.0.0a, 7.0.0b Monitoring Alerting Notes CommandCentral 5.2 has SMI-S only configuration option for Brocade. Discovery of switches using Brocade API was removed from the CommandCentral 5.1 onwards as Brocade has EOLed these API interfaces. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from API to SMI-S. Users need to remove the old API configuration from the CommandCentral Console and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. Minimum version of FOS firmware for Proxy switch is 5.3.1a, 6.x is the recommended version (SMI-S requirement). For the Brocade SMIS Agent v and above, the minimum Proxy switch firmware is FOS 6.x. Use the Brocade SMIS Agent b for Proxy switch with 5.3.1a or firmware. Always pick the highest version of firmware in the Fabric for the proxy switch. Users may need to upgrade switch firmware while they move from API mehod of discovery to SMIS discovery method. Install SMI-S agent(s) on Windows or Solaris hosts Proxy switches are configured using the SMI-S agent GUI Proxy switches must have user credentials with "admin" permission CommandCentral discovers these Brocade switches, as well as their role in the fabric (principal/subordinate), total/free ports, port status, objects connected to each port, zoning information, and more. ~MPR supports basic Discovery. No monitoring support Performance monitoring is not supported with SNMP V3. Fabric OS v6.4.0x is supported with SMI-S agent Please refer to the Documentation for supported Switch Firmware and Models with Brocade DCFM 10.4.x Integrated SMI Agent. Brocade Virtual Switch Discovery is supported only with DCFM / BNA. CommandCentral 5.2 has SMI-S only configuration option for Brocade. Discovery of switches using Brocade API was removed from the CommandCentral 5.1 onwards as Brocade has EOLed these API interfaces. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from API to SMI-S. Users need to remove the old API configuration from the CommandCentral Console and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. Minimum version of FOS firmware for Proxy switch is 5.3.1a, 6.x is the recommended version (SMI-S requirement). For the Brocade SMIS Agent v and above, the minimum Proxy switch firmware is FOS 6.x. Use the Brocade SMIS Agent b for Proxy switch with 5.3.1a or firmware. SilkWorm , 2.6.1a, b, c 2.6.2a, b, c, d Always pick the highest version of firmware in the Fabric for the proxy switch. Users may need to upgrade switch firmware while they move from API mehod of discovery to SMIS discovery method. Install SMI-S agent(s) on Windows or Solaris hosts Proxy switches are configured using the SMI-S agent GUI Proxy switches must have user credentials with "admin" permission CommandCentral discovers these Brocade switches, as well as their role in the fabric (principal/subordinate), total/free ports, port status, objects connected to each port, zoning information, and more. ~MPR supports basic Discovery. No monitoring support Performance monitoring is not supported with SNMP V3. Please refer to the Documentation for supported Switch Firmware and Models with Brocade DCFM 10.4.x Integrated SMI Agent. 10

11 CommandCentral Storage - Switches Switch SilkWorm 7500 SilkWorm AP7420 Multiprotocol Router (MPR) Model Firmware Ancillary SW OS Platform Features SNMP MIB 5.1.0, 5.1.0a, 5.1.0d, 5.2.0a, 5.2.1b, 5.3.0, 6.0.0, 6.1.0, 5.3.1a, 5.3.1b, 5.3.2, 6.0.1a, 6.1.0c, 6.1.0f, 6.1.0j, 6.1.1, 6.1.1d, 6.1.2b, 6.2.0, 6.2.0g, 6.2.1b, 6.2.2, 6.2.2a, 6.3.0b, 6.3.0c, 6.3.1, 6.3.1c, 6.4.0b, 6.4.0c, 6.4.1, 6.4.1b 7.3.0c 7.4.x Monitoring Alerting Notes CommandCentral 5.2 has SMI-S only configuration option for Brocade. Discovery of switches using Brocade API was removed from the CommandCentral 5.1 onwards as Brocade has EOLed these API interfaces. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from API to SMI-S. Users need to remove the old API configuration from the CommandCentral Console and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. Minimum version of FOS firmware for Proxy switch is 5.3.1a, 6.x is the recommended version (SMI-S requirement). For the Brocade SMIS Agent v and above, the minimum Proxy switch firmware is FOS 6.x. Use the Brocade SMIS Agent b for Proxy switch with 5.3.1a or firmware. Always pick the highest version of firmware in the Fabric for the proxy switch. Users may need to upgrade switch firmware while they move from API mehod of discovery to SMIS discovery method. Install SMI-S agent(s) on Windows or Solaris hosts Proxy switches are configured using the SMI-S agent GUI Proxy switches must have user credentials with "admin" permission CommandCentral discovers these Brocade switches, as well as their role in the fabric (principal/subordinate), total/free ports, port status, objects connected to each port, zoning information, and more. ~MPR supports basic Discovery. No monitoring support Performance monitoring is not supported with SNMP V3. Fabric OS v6.4.0x is supported with SMI-S agent Please refer to the Documentation for supported Switch Firmware and Models with Brocade DCFM 10.4.x Integrated SMI Agent. CommandCentral 5.2 has SMI-S only configuration option for Brocade. Discovery of switches using Brocade API was removed from the CommandCentral 5.1 onwards as Brocade has EOLed these API interfaces. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from API to SMI-S. Users need to remove the old API configuration from the CommandCentral Console and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. Minimum version of FOS firmware for Proxy switch is 5.3.1a, 6.x is the recommended version (SMI-S requirement). For the Brocade SMIS Agent v and above, the minimum Proxy switch firmware is FOS 6.x. Use the Brocade SMIS Agent b for Proxy switch with 5.3.1a or firmware. Always pick the highest version of firmware in the Fabric for the proxy switch. Users may need to upgrade switch firmware while they move from API mehod of discovery to SMIS discovery method. Install SMI-S agent(s) on Windows or Solaris hosts Proxy switches are configured using the SMI-S agent GUI Proxy switches must have user credentials with "admin" permission CommandCentral discovers these Brocade switches, as well as their role in the fabric (principal/subordinate), total/free ports, port status, objects connected to each port, zoning information, and more. ~MPR supports basic Discovery. No monitoring support Performance monitoring is not supported with SNMP V3. Please refer to the Documentation for supported Switch Firmware and Models with Brocade DCFM 10.4.x Integrated SMI Agent. 11

12 CommandCentral Storage - Switches Switch Brocade and McDATA mixed fabrics (Interoperability) Cisco Brocade and McDATA models MDS 9120 MDS 9124 MDS 9134 MDS 9140 MDS 9216 MDS 9506 MDS 9509 MDS 9513 Model Firmware Ancillary SW OS Platform Features SNMP MIB Brocade FOS Firmware: 5.x McData EOS Firmware: or higher. OSMS Must be enabled on all McData Switches Brocade FOS Firmware: 6.x McData EOS Firmware: or higher. OSMS Must be enabled on all McData Switches 1.3.3c, 1.3.4a, b 2.01b, 2.1.1a, b, 3.0.1, 3.0.3b 3.1.2a, 3.1.3a, c, 3.3.1a, 3.1.1c 1.2, 1.3.4a, b 2.0.1b, 2.1.1a, b 3.0.1, 3.0.3b 3.1.2a, 3.1.3a, c, 3.3.1a, 3.3.1c,4.1(1b) (MDS 9513 only), 4.1(3a), 4.2(7d) (MDS 9513 only), 4.2(4e) (MDS 9513 only), 5.0(4d) (MDS 9513 only) EFCM : 9.7.1,2,3 or 4 Fabric Discovery Method: McData SMIS 2.6.2,2.7.1 Brocade API ( Requires a CCS 5.0MP1RP6 Control Host ) Interopmode : Interopmode 1 DCFM: 10.1.x, Fabric Discovery Method: McData SMIS 2.6.2,2.7.1 Brocade SMIS Brocade SMIS Interoperability Modes: Interopmode 3 (Open Fabric) EFCM : 9.7.1,2,3 or 4 Fabric Discovery Method: McData SMIS 2.6.2,2.7.1 Brocade SMIS Brocade SMIS Interoperability Modes: Interopmode 2 (McData Fabric), Interopmode 3 (Open Fabric) Fabric Discovery Method: DCFM , , , Integrated SMI Agent, Brocade Network advisor 11.0, 11.1, SNMP Windows 2003,Windows 2008,Solaris 9,Solaris 10 Solaris 8,Solaris 9,Solaris 10,Windows 2000,Windows 2003,Windows 2008 Discovery MDS MIB SNMP IF MIB Monitoring Alerting Monitoring is not supported for McData Switches with EFCM Monitoring is not supported for McData Switches with DCFM Monitoring is not supported for McData Switches with EFCM via switch SNMP agent. Notes Note: McData switches need to be discovered via McData SMI-S in Proxy Mode to EFCM. Brocade switches need to be discovered via Brocade API (a CCS 5.0MP1RP6 Control Host). Performance monitoring is not supported with SNMP V3. Note: McData switches need to be discovered via McData SMI-S in Proxy Mode to DCFM. Brocade switches need to be discovered via Brocade SMI Agent. Performance monitoring is not supported with SNMP V3. Note: McData switches need to be discovered via McData SMI-S in Proxy Mode to EFCM. Brocade switches need to be discovered via Brocade SMI Agent. Performance monitoring is not supported with SNMP V3. Please refer to the Documentation for supported Switch Firmware and Models with Brocade DCFM 10.4.x Integrated SMI Agent VSAN, Zone, Port Bundle (Port Channels), Module, and Slot discovery supported. SNMP v3 supported. *Discovery of hard zones supported. 12

13 CommandCentral Storage - Switches Switch EMC(Connectri x) DS-24M2 DS- 32M2 ED-140M Model Firmware Ancillary SW OS Platform Features SNMP MIB , , , , , , , , , , , McDATA SMI-S Agent 2.6.2, (Brocade SMI agent for EOS products) DCFM , , , Brocade Network Advisor 11.0, 11.1, Monitoring Alerting Notes CommandCentral 5.2 has SMI-S only configuration option for Connectrix. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from SWAPI to SMI-S. Users need to remove the old SWAPI configuration from the CommandCentral web GUI and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. For EMC-B series fabrics, the minimum version of FOS firmware for Proxy switch is 5.3.1a, 6.x is the recommended version (SMI-S requirement). For the Brocade SMIS Agent v , the minimum Proxy switch firmware is FOS 6.x. Use the Brocade SMIS Agent b for Proxy switch with 5.3.1a or firmware. Other EMC-B models listed in this document which do not have the minimum firmware version can be used as target switches. Always pick the highest version of firmware in the Fabric for the proxy switch. Users may need to upgrade switch firmware while they move from API mehod of discovery to SMIS discovery method. Install SMI-S agent(s) on Windows or Solaris hosts. Proxy switches are configured using the SMI-S agent GUI. Proxy switches must have user credentials with "admin" permission. For EMC-M series fabrics, the McData SMI Agent and are compatible with EFCM 9.7.1,2,3 or 4 and EFCM 9.6.x It is not recommended to install SMI-S agent on the CommandCentral Management Server. SMI-S agent should be installed preferably on a Windows host. Host on which EFCM is running may be used. One SMI-S agent per EFCM is the recommended scale. Its required to uninstall the SWAPI Bridge Agent. CommandCentral Storage discovers these switches, as well as their role in the fabric (principal/subordinate), total/free ports, port status, objects connected to each port, zoning information, and more. Fabric and Zoning discovery of switches requires an out-of-band connection. Discovery EMC-B series fabrics require installation of a qualified Brocade SMI-S provider configured to the Brocade switch explorer on a CommandCentral Storage host. Discovery of EMC M-series fabrics require installation of a qualified McDATA SMI-S provider configured to the McDATA Switch explorer on a CommandCentral host. McDATA SMI-S provider v2.0 or later versions support zoning discovery in fabric zoning mode only. Global zones and zonesets must be imported to fabric zoning libraries for them to be discovered and managed. Active zones and zoneset must be duplicated into inactive zones and zoneset before they can be managed in direct switch connection mode. Monitoring of switches discovered through McDATA SMI-S provider in proxy mode requires setting "EFCMIPAddress". Monitoring of switches discovered through McDATA SMI-S provider in direct switch connection mode is not supported. Monitoring of switches discovered through McDATA SMI-S provider in DCFM proxy mode is not supported. DS-32B b, d, e, a, b, 5.0.3,

14 CommandCentral Storage - Switches Switch DS-12000B Model Firmware Ancillary SW OS Platform Features SNMP MIB 4.4.0b, d, e, a, b, 5.0.3, 5.0.4, 5.0.5c, 5.0.5d, 5.0.5f Windows 2003,Windows 2000,Windows 2008,Solaris 8,Solaris 9,Solaris 10 Discovery Monitoring Alerting FA MIB 3.0 FA MIB 3.1 Notes CommandCentral 5.2 has SMI-S only configuration option for Connectrix. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from SWAPI to SMI-S. Users need to remove the old SWAPI configuration from the CommandCentral web GUI and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. For EMC-B series fabrics, the minimum version of FOS firmware for Proxy switch is 5.3.1a, 6.x is the recommended version (SMI-S requirement). For the Brocade SMIS Agent v , the minimum Proxy switch firmware is FOS 6.x. Use the Brocade SMIS Agent b for Proxy switch with 5.3.1a or firmware. Other EMC-B models listed in this document which do not have the minimum firmware version can be used as target switches. Always pick the highest version of firmware in the Fabric for the proxy switch. Users may need to upgrade switch firmware while they move from API mehod of discovery to SMIS discovery method. Install SMI-S agent(s) on Windows or Solaris hosts. Proxy switches are configured using the SMI-S agent GUI. Proxy switches must have user credentials with "admin" permission. For EMC-M series fabrics, the McData SMI Agent and are compatible with EFCM 9.7.1,2,3 or 4 and EFCM 9.6.x It is not recommended to install SMI-S agent on the CommandCentral Management Server. SMI-S agent should be installed preferably on a Windows host. Host on which EFCM is running may be used. One SMI-S agent per EFCM is the recommended scale. Its required to uninstall the SWAPI Bridge Agent. CommandCentral Storage discovers these switches, as well as their role in the fabric (principal/subordinate), total/free ports, port status, objects connected to each port, zoning information, and more. Fabric and Zoning discovery of switches requires an out-of-band connection. Discovery of EMC-B series fabrics require installation of a qualified Brocade SMI-S provider configured to the Brocade switch explorer on a CommandCentral Storage host. Discovery of EMC M-series fabrics require installation of a qualified McDATA SMI-S provider configured to the McDATA Switch explorer on a CommandCentral host. McDATA SMI-S provider v2.0 or later versions support zoning discovery fabric zoning mode only. Global zones and zonesets must be imported to fabric zoning libraries for them to be discovered and managed. Active zones and zoneset must be duplicated into inactive zones and zoneset before they can be managed in direct switch connection mode. Monitoring of switches discovered through McDATA SMI-S provider in proxy mode requires setting "EFCMIPAddress". Monitoring of switches discovered through McDATA SMI-S provider in direct switch connection mode is not supported. Monitoring of switches discovered through McDATA SMI-S provider in DCFM proxy mode is not supported. DS-220B, DS- 4900B 5.1.0, 5.1.0a, 5.1.0d, 5.2.0a, 5.2.1b, 5.3.0, 5.3.1a, 5.3.1b, 5.3.2, 6.0.0, 6.0.1a, 6.1.0, 6.1.0c, 6.1.0f, 6.1.0j, 6.1.1, 6.1.1d, 6.1.2b, 6.2.0, 6.2.0g, 6.2.1b, 6.2.2a, 6.3.0b, 6.3.0c, 6.3.1, 6.3.1c, 6.4.0b, 6.4.0c, 6.4.1, 6.4.1b (6.3.x not supported by DS-220B) Brocade SMI provider v b, v , v , v (Refer to the Notes section for Proxy switch firmware compatibility with SMI provider) DCFM , , , Brocade Network Advisor 11.0, 11.1,

15 CommandCentral Storage - Switches Switch DS-8B2, 16B2 ED-48000B Model Firmware Ancillary SW OS Platform Features SNMP MIB 3.1, 3.1.1, 3.1.1b, d 3.1.2, 3.1.3, 3.1.3b 3.2.0a, c, 5.0.5d, 5.0.5f, 5.1.0, 5.1.0a, 5.1.0d, 5.2.0a, 5.2.1b, 5.3.0, 5.3.1a, 5.3.1b, 5.3.2, 6.0.0, 6.0.1a, 6.1.0, 6.1.0c, 6.1.0f, 6.1.0j, 6.1.1, 6.1.1d, 6.1.2b, 6.2.0, 6.2.0g, 6.2.1b, 6.2.2a, 6.3.0b, 6.3.0c, 6.3.1, 6.3.1c, 6.4.0b, 6.4.0c, b Monitoring Alerting Notes CommandCentral 5.2 has SMI-S only configuration option for Connectrix. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from SWAPI to SMI-S. Users need to remove the old SWAPI configuration from the CommandCentral web GUI and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. For EMC-B series fabrics, the minimum version of FOS firmware for Proxy switch is 5.3.1a, 6.x is the recommended version (SMI-S requirement). For the Brocade SMIS Agent v , the minimum Proxy switch firmware is FOS 6.x. Use the Brocade SMIS Agent b for Proxy switch with 5.3.1a or firmware. Other EMC-B models listed in this document which do not have the minimum firmware version can be used as target switches. Always pick the highest version of firmware in the Fabric for the proxy switch. Users may need to upgrade switch firmware while they move from API mehod of discovery to SMIS discovery method. Install SMI-S agent(s) on Windows or Solaris hosts. Proxy switches are configured using the SMI-S agent GUI. Proxy switches must have user credentials with "admin" permission. For EMC-M series fabrics, the McData SMI Agent and are compatible with EFCM 9.7.1,2,3 or 4 and EFCM 9.6.x It is not recommended to install SMI-S agent on the CommandCentral Management Server. SMI-S agent should be installed preferably on a Windows host. Host on which EFCM is running may be used. One SMI-S agent per EFCM is the recommended scale. Its required to uninstall the SWAPI Bridge Agent. CommandCentral Storage discovers these switches, as well as their role in the fabric (principal/subordinate), total/free ports, port status, objects connected to each port, zoning information, and more. Fabric and Zoning discovery of switches requires an out-of-band connection. Discovery of EMC-B series fabrics require installation of a qualified Brocade SMI-S provider configured to the Brocade switch explorer on a CommandCentral Storage host. Discovery of EMC M-series fabrics require installation of a qualified McDATA SMI-S provider configured to the McDATA Switch explorer on a CommandCentral host. McDATA SMI-S provider v2.0 or later versions support zoning discovery in fabric zoning mode only. Global zones and zonesets must be imported to fabric zoning libraries for them to be discovered and managed. Active zones and zoneset must be duplicated into inactive zones and zoneset before they can be managed in direct switch connection mode. Monitoring of switches discovered through McDATA SMI-S provider in proxy mode requires setting "EFCMIPAddress". Monitoring of switches discovered through McDATA SMI-S provider in direct switch connection mode is not supported. Monitoring of switches discovered through McDATA SMI-S provider in DCFM proxy mode is not supported. 15

16 CommandCentral Storage - Switches Switch McDATA ES-3016 ES ES-3216 ES-3232 ED ED-6140 Model Firmware Ancillary SW OS Platform Features SNMP MIB , , , , , , , , , , (6140,6064,323 only), (6140,6064,323 only), (6140,6064,323 only) McDATA SMI-S Agent Compatible with EFCM 9.7.1,2,3 or 4 or EFCM 9.6.x, SMI-S Agent Brocade Integrated SMI Agent DCFM , , , Brocade Network Advisor 11.0, 11.1, Monitoring Alerting Notes CommandCentral 5.2 has SMI-S only configuration option for McData. Discovery of switches using SWAPI is removed from the CommandCentral 5.1 release onwards as Brocade has EOLed these API interfaces. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from SWAPI to SMI-S. Users need to remove the old SWAPI configuration from the CommandCentral web GUI and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. SMI Agent is compatible with EFCM 9.7.1, 9.7.2, 9.7.3, or 9.6.x It is not recommended to install SMI-S agent on the CommandCentral Management Server. SMI-S agent should be installed preferably on a Windows host. Host on which EFCM is running may be used. One SMI-S agent per EFCM is the recommended scale. Its required to uninstall the SWAPI Bridge Agent. Refer to McData SMI-S Agent Users Guide. Chapter 1, page 8 "Memory and CPU recommendations. contains SMIS Memory/CPU/Sizing information and JVM resizing instructions. Monitoring of switches discovered through McDATA SMI-S provider in proxy mode requires setting "EFCMIPAddress". Monitoring of switches discovered through McDATA SMI-S provider in direct switch connection mode is not supported. i10k switches with virtualization is not supported. Monitoring is not supported for i10k switches for firmware 9.x. Monitoring of switches discovered through McDATA SMI-S provider in DCFM proxy mode is not supported. Performance monitoring is not supported with SNMP V3. For the Brocade Integrated SMI Agent DCFM , minimum supported M-EOSc and M-EOSn switch firmware is 9.6.x. Please refer to the Documentation for additional information regarding supported Switch Firmware and Models with Brocade DCFM 10.4.x Integrated SMI Agent. For the Brocade Integrated SMI Agent DCFM , minimum supported M-EOSc and M-EOSn switch firmware is 9.6.x. Please refer to the Documentation for additional information regarding supported Switch Firmware and Models with Brocade DCFM 10.4.x Integrated SMI Agent. Intrepid 10000** , , , , ,

17 CommandCentral Storage - Switches Switch QLogic Sphereon 4300 Sphereon 4400, Sphereon 4700 Sphereon 4500 SAN BOx2-64 SANbox 5200, SANbox, 5600, SANbox 5602 Model Firmware Ancillary SW OS Platform Features SNMP MIB , , , , , , , , , , , , , , , , , , , , , , , , , , , , SANbox SANBox2-8, SANBox McDATA SMI-S Agent Compatible with EFCM 9.7.1,2,3 or 4 or EFCM 9.6.x, SMI-S Agent Brocade Integrated SMI Agent DCFM , , , Brocade Network Advisor 11.0, 11.1, McDATA SMI-S Agent Compatible with EFCM 9.7.1,2,3 or 4 or EFCM 9.6.x, SMI-S Agent Brocade Integrated SMI Agent DCFM , , , Brocade Network Advisor 11.0, 11.1, Solaris 8,Solaris 9,Solaris 10,Windows 2000,Windows 2003,Windows 2008 Windows 2000, Windows 2003, Windows 2008, Solaris 8,9,10 AIX, HP-UX, Linux Discovery Discovery Multi-Zone Set discovery Monitoring Alerting FA MIB 3.0 FA MIB 3.1 FA MIB 3.0 Not Notes CommandCentral 5.2 has SMI-S only configuration option for McData. Discovery of switches using SWAPI is removed from the CommandCentral 5.1 release onwards as Brocade has EOLed these API interfaces. For users migrating from CommandCentral 5.0 to the 5.2 version, its recommended to convert the discovery method from SWAPI to SMI-S. Users need to remove the old SWAPI configuration from the CommandCentral web GUI and configure Explorers with the SMI-S agents using 5.0MP1_RP6. Contact Symantec Technical Support for more details. SMI Agent is compatible with EFCM 9.7.1, 9.7.2, 9.7.3, or 9.6.x It is not recommended to install SMI-S agent on the CommandCentral Management Server. SMI-S agent should be installed preferably on a Windows host. Host on which EFCM is running may be used. One SMI-S agent per EFCM is the recommended scale. Its required to uninstall the SWAPI Bridge Agent. Refer to McData SMI-S Agent Users Guide. Chapter 1, page 8 "Memory and CPU recommendations. contains SMIS Memory/CPU/Sizing information and JVM resizing instructions. Monitoring of switches discovered through McDATA SMI-S provider in proxy mode requires setting "EFCMIPAddress". Monitoring of switches discovered through McDATA SMI-S provider in direct switch connection mode is not supported. i10k switches with virtualization is not supported. Monitoring is not supported for i10k switches for firmware 9.x. Monitoring of switches discovered through McDATA SMI-S provider in DCFM proxy mode is not supported. Performance monitoring is not supported with SNMP V3. For the Brocade Integrated SMI Agent DCFM , minimum supported M-EOSc and M-EOSn switch firmware is 9.6.x. Please refer to the Documentation for additional information regarding supported Switch Firmware and Models with Brocade DCFM 10.4.x Integrated SMI Agent. Topology and zoning discovery through GS explorer. Monitoring is not supported. Each QLogic switch maintains its own zoning database. ONLY inactive zones and zonesets on the switch inband connected to a CommandCentral Storage host will be discovered. "Orphaned Zonesets" are not supported. 17

18 C CommandCentral Storage - Storage Devices Storage Device 3PAR Model OS Platform Monitoring & Alerting Features Ancilliary SW Notes Inserv E200, T400 Solaris 8,Solaris 9,Solaris 10,Windows 2000,Windows 2003,Windows 2008 InServ S400X Environmental Deep Mapping Firmware (with Embedded SMI-S 1.1 provider) Requires a network connection to the arrays and the CIMVAIL Explorer. The CIM Agent (SMI-S provider) runs on the array controller itself (in other words, it is embedded with controller software). The embedded SMI-S provider, by default, is turned off. This needs to turned on by logging into the array if you want to manage this array via CommandCentral Storage. Thin Provisioning is not supported. 18

19 CommandCentral Storage - Storage Devices Storage Device Model OS Platform Monitoring & Alerting Features Ancilliary SW Notes AX100 AX150 Celerra NS20, NS80, NSX, NS700G, NS500G,NS20FC, NS700, NS-480, NS-120, NS- 120FC, NSG Environmental ~Performance Not Deep Mapping Snapshot Discovery (SnapView Snapshots, SnapView Clone, MirrorView (Sync)) NAVCLI 6.19, 6.22, 6.24, 6.26, 6.29 Virtual Data mover. Deep mapping discovery. DART , DART 6.x NAVISECCLI (Secure CLI mode) also supported. Thin provisioning and Data de-duplication not supported. iscsi discovery is supported from both managed server platform. iscsi storage correlation is supported on Windows only and requires use of Microsoft iscsi initiator version Supports correlation of the physical disks of the Celerra storage system and their backend array volumes (LUNs). Checkpoint and replication is not supported for CCS 5.2RU2. CLARiiON CX4-120, CX4-240, CX4-480, CX4-960 NAVCLI 6.28, 6.29, 7.30, 7.31 CX-4 arrays need minimum version of Navicli Thin provisioning discovery is supported from Naviseccli 7.30 onwards. EMC CLARiiON CX200 CX400 CX600 CLARiiON CX300 CX500 CX700 CLARiiON CX3-10 CX3-20 CX3-40 CX3-80 Solaris 8,Solaris 9,Solaris 10,Windows 2000,Windows 2003,Windows 2008 Environmental ~Performance Deep Mapping Snapshot Discovery (SnapView Snapshots, SnapView Clone, MirrorView (Sync)) NAVCLI 6.7, 6.16, 6.19, 6.24, 6.26, 6.29, 7.30, 7.31 CLARiiON FC4700 FC Deep Mapping NAVCLI 6.7, 6.16, 6.19, 6.24, 6.26 VNX 5100, 5300, 5700, 7500 Not Virtual Data mover. Deep Mapping Snapshot Discovery (SnapView Snapshots, SnapView Clone, MirrorView (Sync)) Storage Pools. See the EMC Support Matrix to determine which storage array firmware version is compatible with a given NAVICLI version. Network connectivity is required between the storage arrays and the host where NAVICLI is installed. The storage array configuration must be "Shared Access Configuration" which requires Access Logix support enabled. NAVISECCLI (Secure CLI mode) supported. NAVCLI 6.19, 6.22, 6.24, 6.26, 6.28, 6.29, 7.30, 7.31 NAVISECCLI (Secure CLI mode) supported. NAVISECCLI 7.31, OE 7, OE 31 See the EMC Support Matrix to determine which storage array firmware version is compatible with a given NAVICLI version. Network connectivity is required between the storage arrays and the host where NAVICLI is installed. The storage array configuration must be "Shared Access Configuration", which requires Access Logix support enabled. NAVISECCLI (Secure CLI mode) supported. Monitoring is not supported for VNX arrays. Please see CC 5.2 RU3 release notes for configuring VNX unified devices. FAST discovery is not supported for VNX arrays. Thin provisioning discovery is supported for VNX block devices. DMX DMX-3 DMX-4 Windows 2000,Windows 2003,Windows 2008,Solaris 8,Solaris 9,Solaris 10,HP-UX 11i v2*,aix 5.2,AIX 5.3,Linux Red Hat AS/ES v3.0, v4.0 (32 )** Deep Mapping Snapshot(BCV, Clone, Snap) Discovery SRDF Discovery *1 Virtual provisioning (DMX-3 and DMX-4) EMC Solutions Enabler 5.5, 6.0, 6.2, 6.3.1, 6.4, 6.5.1, 7.0, 7.1.2, 7.2.1, , For discovery, the VCMDB LUN must be visible to the host where the EMC Solutions Enabler and VolumeLogix (if required) are installed. With Enginuity 5670 and later, access to the VCM database does not require that the VCM device be mapped to an FA and presented to a server, as long as there are gatekeepers available. The discovery is supported via SYMAPI server as well, in which the case VCMDB LUN must be visible to the host where SYMAPI server is installed. The CommandCentral Symmetrix explorer still needs the EMC Solutions Enabler (SYMCLI) to be installed on the host (where the explorer is running) and it (SYMCLI) should be configured to access the SYMAPI server host over IP. Do not run more than one tool (GUI or CLI) at the same time which alters the device masks on an array, because this can corrupt array configuration data. CommandCentral cannot discover ESCON type Front End Directors; only Fibre Channel type Front End Directors are supported. Performance Reporting is only supported on Windows and Solaris hosts. *For HP-UX 11i v2, for the list of the required OS patches/updates please refer the CommandCentral Storage Release Notes (System Requirements) SYMCLI has issues with snapshot discovery, is recommended. EMC Solutions Enabler qualified for AIX 5.2 ML05 only. For non-meta LUN deletion, requires 5670 with EMC Solutions Enabler 5.3 or above. 1 If EMC Symmetrix/DMX has SRDF enabled, then SYMCLI 6.2 or later is required for the SRDF discovery. Monitoring is not supported with SE