EMC ProSphere Version 1.0

Transcription

1 EMC ProSphere Version 1.0 Preparing for Deployment P/N REV A05 EMC Corporation Corporate Headquarters: Hopkinton, MA

2 Copyright 2011 EMC Corporation. All rights reserved. Published October, 2011 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. 2 EMC ProSphere: Preparing for Deployment

3 Contents Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Deployment Prerequisites Virtual hardware requirements... 8 Configure Hosts Validate HBAs Configure Windows hosts and WMI Configure UNIX and Linux hosts Prepare for discovery of VMware guests Prepare for discovery of VMware infrastructure Configure Arrays Configure the EMC SMI-S Provider Integrate ProSphere with SPA Configure Switches and Fabrics Configure Cisco switches Configure the Brocade CMDCE Integrated SMI Agent Configure the Brocade SMI Agent Configure the Brocade SMI Agent for EOS Next Steps EMC ProSphere: Preparing for Deployment 3

4 4 EMC ProSphere: Preparing for Deployment

5 . Preface As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information about product features, refer to your product release notes. If a product does not function properly or does not function as described in this document, please contact your EMC representative. Revision History Revision Date Description A01 July 5, 2011 Final documentation build prior to the 1.0 release of ProSphere A02 July 21, 2011 Revisions required between the final documentation build and preparations for the 1.0 release. A03 August 21, 2011 Revisions associated with Update This version is included in the embedded documentation library. A04 September 16, 2011 Revisions associated with Update Corrected path names associated with inq Utility. Revised Prerequisites for Windows Server 2003 and Windows Server 2008 on page 11. A05 October 18, 2011 Revisions associated with Update Edited Prerequisites for Windows Server 2003 and Windows Server 2008 on page 11. Added two steps to Integrate ProSphere with SPA on page 25. Audience Conventions used in this document This document is part of the EMC ProSphere TM documentation set. The document is intended for use by system administrators and integrators responsible for preinstallation configuration of hosts, arrays, switches, and fabrics in ProSphere. EMC uses the following conventions for special notices. Note: A note presents information that is important, but not hazard-related. EMC ProSphere: Preparing for Deployment 5

6 Preface Typographical conventions EMC uses the following type style conventions in this document: Bold Used in running (nonprocedural) text for: Names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, man pages Used in procedures for: Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus) What user specifically selects, clicks, presses, or types Italic Used in all text (including procedures) for: Full titles of publications referenced in text Emphasis (for example a new term) Variables Courier Used for: System output, such as an error message or script URLs, complete paths, filenames, prompts, and syntax when shown outside of running text Courier bold Used for: Specific user input (such as commands) < > Angle brackets enclose parameter or variable values supplied by the user Vertical bar indicates alternate selections - the bar means or Contacting Customer Support Where to get help EMC support, product, and licensing information can be obtained as follows. Product information For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at: Technical support For technical support, go to Powerlink and choose Support. On the Support page, you will see several options, including one for making a service request. Note that to open a service request, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account. Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your general opinions of EMC documentation to: techpubcomments@emc.com Send your opinions of EMC ProSphere documentation to: ProSphere_doc_comments@emc.com 6 EMC ProSphere: Preparing for Deployment

7 1 Deployment Prerequisites This chapter provides resource prerequisites for EMC ProSphere. Because meeting hardware requirements can require substantial time, it is advisable as a first step to consider how to meet them. The chapter includes the following sections: Virtual hardware requirements... 8 Deployment Prerequisites 7

8 Deployment Prerequisites Virtual hardware requirements To take advantage of vsphere features that enhance availability and flexibility of a virtual infrastructure, it is recommended to install ProSphere on an ESX/ESXi server cluster. The product can be installed on a single ESX server if the server meets hardware requirements. Table 1 on page 8 specifies the virtual hardware requirements for the three virtual machines that constitute an unscaled deployment of ProSphere. The table helps system administrators make deployment placement decisions based on current and expected hardware resource utilization. Table 1 Virtual hardware requirements Virtual Machine Virtual Processor Memory Storage In a scaled deployment, one or more Discovery Engine Collectors (Collectors) are added to the deployment. Each Collector that is added to the product requires the following additional resources: ProSphere Application 4 64-bit CPUs 8 GB RAM 230 GB Discovery Engine 4 64-bit CPUs 8 GB RAM 40 GB Historical Database 2 64-bit CPUs 6 GB RAM 230 GB Total Required Storage= 600 GB a a.the total allows for one Discovery Engine Collector, RAM, and a couple of snapshots bit CPUs 6 GB RAM 20 GB storage Note: No special VMware configuration procedures are required before deploying ProSphere. The EMC ProSphere Administrators Guide describes the virtual machines in ProSphere. When deciding whether to use think or thick provisioning for storage space, consider the future storage capacity requirements of all virtual machines on the same datastore. Disk space usage of the ProSphere Application and Historical Database will grow over time. 8 EMC ProSphere: Preparing for Deployment

9 2 Configure Hosts This chapter provides instructions for the installation and configuration of third-party software used to discover hosts and related performance data. The chapter includes the following sections: Validate HBAs Configure Windows hosts and WMI Configure UNIX and Linux hosts Prepare for discovery of VMware guests Configure Hosts 9

10 Configure Hosts Validate HBAs All host platforms require the following for successful discovery by EMC ProSphere: EMC-supported host bus adapter (HBA) drivers and firmware. The EMC ProSphere Support Matrix provides specific details. Vendor-specific, SNIA-compliant libraries for HBAs. To validate that the appropriate SNIA libraries are installed, download and run the inq application from EMC Powerlink using the following procedure: 1. From EMC Powerlink, select the menu options Home, Support, Product and Diagnostic Tools, INQ Utility. 2. Select the latest version of inq. 3. Select the operating system for your host. 4. Download inq and follow the provided installation instructions. 5. Run the following command on the host after installation: Inq -hba If the command lists the HBAs, then the SNIA libraries are properly installed, which means that ProSphere can discover the HBAs. Note: HBA model and part numbers should be verified before updating hosts with SNIA libraries for HBAs. You can verify compatible versions of HBAs and SNIA libraries using available EMC interoperability guides at 10 EMC ProSphere: Preparing for Deployment

11 Configure Hosts Configure Windows hosts and WMI Windows host discovery is dependent upon Windows Management Instrumentation (WMI). The following sections describe how to configure WMI to work with ProSphere. Prerequisites for Windows Server 2003 and Windows Server 2008 The following are prerequisites for Windows host discovery by ProSphere: Discovery must be done under the access profile of a user that is an Administrator or a member of the Administrators group. These credentials are entered as WMI credentials in ProSphere. The EMC ProSphere Administrators Guide explains how to create access credentials. The user account used for discovery must be permitted access to the host to be discovered. The user has WMI privileges. The user has write privileges to the default Temp directory. On Windows 2003, the path for the default Temp directory is: C:\Document and Settings\<user name>\local settings\temp ProSphere tries to write data to the default Temp directory. If this directory does not have write privileges, ProSphere tries to write data to C:\Windows\Temp. If the C:\Windows\Temp directory does not have write privileges, ProSphere tries to write data to the user-configured %Temp% directory. If the user-configured %Temp% directory does not have write privileges, the operation fails. On Windows 2008, the path for the default Temp directory is: C:\Users\<user name>\appdata\local\temp ProSphere tries to write data to the default Temp directory. If this directory does not have write privileges, ProSphere tries to write data to C:\Windows\Temp. If the C:\Windows\Temp directory does not have write privileges, ProSphere tries to write data to the user-configured %Temp% directory. If the user-configured %Temp% directory does not have write privileges, the operation fails. Note: To find the exact location of the %Temp% directory: Select Start->Run Type %Temp% This opens the directory. Ensure that the Visual C SP1 Redistributable Package is installed on the host. Note: In case the windows update option is enabled and you do not find this package on your system, you can download the package from Configure Windows hosts and WMI 11

12 Configure Hosts Ensure that the WMI and Remote Registry services are running. Note: To ensure that the services are started: Select Start->Run Type services.msc. The Services window appears. Ensure the Windows Management Instrumentation and Remote Registry services are started. If they are not, right click on the services and select Start Make appropriate registry changes on a Windows Server 2008 R2 host. The section Make registry changes on a Windows Server 2008 R2 host on page 18 provides information on the required registry changes. For WMI, to allow access to the Root/CIMV2 namespace and all subnamespaces the following permissions must be set: Execute Methods Full Write Partial Write Enable Account Remote Enable Read Security The section Add a user with the necessary WMI permissions on page 13 provides information on how to set the necessary permissions. Microsoft Distributed Object Component Model (DCOM) communication is enabled on the server to be discovered. The section Enable DCOM on page 13 provides information on how to configure DCOM on port 135. The host firewall is properly configured to permit DCOM on port 135. The section Add a firewall exception to open Dynamic RPC ports on page 15 provides information on how to configure DCOM on port 135. ProSphere must be using Windows credentials with remote DCOM permissions and WMI permissions. Add a user with the necessary remote DCOM permissions To configure a DCOM-enabled user account on a Windows server host: 1. Log on to the server as a local or domain user who has full read/write permissions to the %Temp% directory. 2. Click the Windows Start button and then select Run. 3. Type dcomcnfg and click OK. The Component Services dialog box appears. 4. Expand Component Services in the Console Root tree view, and then expand Computers. 5. Right-click My Computer from the expanded Computers tree view, and then select Properties. The My Computer Properties dialog box appears. 6. Click Default Properties. 7. Select Enable Distributed COM on this computer. 8. Click COM Security. 9. Click Edit Limits in the Launch and Activation Permissions area. The Launch Permission dialog box appears. 12 EMC ProSphere: Preparing for Deployment

13 Configure Hosts 10. Ensure the Administrators group or the user name you require is in the list of Group and user names. In case the Administrators group or the user name is not present in the list: a. Click Add. The Select, Users, Computers, or Groups dialog box appears. b. Type the Administrator group or user name in the Enter the object names to select field. The user name you add must have full permissions to the %Temp% directory. c. Click OK. This navigates you back to the Launch Permission dialog box. 11. Select the Remote Launch and Remote Activation boxes, in the Permissions for Administrators area, to provide the user with these permissions and then click OK. 12. Click OK to close the My Computer Properties and Component Services dialog boxes. Enable DCOM On the host to be discovered, verify that the following registry key value is set to Y: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole ->EnableDCOM Add a user with the necessary WMI permissions To set WMI privileges for a Windows user account: 1. Log on to the server as a local or domain user. 2. Click the Windows Start button and then select Run. 3. Type WMIMGMT.MSC and click OK. The Windows Management Infrastructure (WMI) dialog box appears. 4. Right-click on WMI Control (Local) and then select Properties. The WMI Control (Local) Properties dialog box appears. 5. Click the Security tab. 6. Select the Root > CIMV2 namespace and then click Security. The Security for ROOT\CIMV2 dialog box appears. 7. Select the user account or group that has the DCOM permission setting required for discovery, as selected in Add a user with the necessary remote DCOM permissions on page 12 In case the user account or group name is not listed, step 10 on page 13 provides instructions to add the required user account or group. 8. Ensure that all the permissions are enabled in the Permissions for Administrators area. 9. Click Apply and then OK. The WMI Control (Local) Properties dialog box appears. 10. Click OK. The Windows Management Infrastructure (WMI) dialog box appears. 11. Close the Windows Management Infrastructure (WMI) dialog box. Configure Windows hosts and WMI 13

14 Configure Hosts Configure dynamic RPC ports Note: This procedure is applicable to both Windows Server 2003 and Windows Server 2008 and is required only when the firewall is enabled and all the dynamic RPC ports traffic is blocked in the customer environment. To configure dynamic RPC ports: 1. Log on to the server as a local or domain user. 2. Click the Windows Start button and then select Run. 3. Type regedt32.exe and click OK. The Registry Editor dialog box appears. 4. Expand the following registry key path: HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc 5. Create subkeys under Rpc by right-clicking on Rpc and then selecting New >Key. 6. Set the new key name to Internet. 7. Right-click the Internet key and select New > Multi-String Value. Set the new value to Ports. 8. Right-click on the Ports key and select Modify. The Edit Multi-String dialog box appears. 9. Type in the dynamic RPC ports that are open or a range of ports that are configured as dynamic RPC. Note: The dynamic RPC port details or the range of ports typed in the Edit Multi-String dialog box are those that are configured as dynamic RPC in the customer environment. For example, the range of dynamic RPC ports can be set as Right-click the Internet key and select New > String Value. 11. Set the new string name to PortsInternetAvailable. 12. Right-click PortsInternetAvailable and select Modify. The Edit String dialog box appears. 13. Type the letter Y in the Value Data field and then click OK. 14. Right-click the Internet key and select New > String Value. 15. Set the new string name to UseInternetPorts. 16. Right-click UseInternetPorts and select Modify. The Edit String dialog box appears. 17. Type the letter Y in the Value Data field and then click OK. 18. Exit the Registry Editor. 19. Restart the host to reflect these dynamic port changes. Note: In ProSphere, if you configure a single port (for example: port 135) and try to discover hosts, multiple threads from topology and performance data collection collide on that host resulting in discovery errors. Therefore, a range of ports is required for discovery to be successful. 14 EMC ProSphere: Preparing for Deployment

15 Configure Hosts Add a firewall exception to open Dynamic RPC ports If a firewall is enabled, you need to add firewall exceptions that opens port 135 and the dynamic RPC ports. On Windows Server 2008, if you have the default Windows 2008 firewall software then add the the following exception rules to allow the WMI traffic. Inbound firewall exception rule for dynamic RPC ports To create an inbound firewall exception rule ProSphere-Dynamic-RPC-ports: 1. Click Start > Administrative tools > Windows firewall with Advanced Security. 2. Select Inbound Rules in the left hand navigation tree. 3. Right-click Inbound Rules and click on New Rule. 4. Select Rule Type as Custom and click Next. 5. Select This program path in the Program section, and type %SystemRoot%\System32\dllhost.exe as a path for dllhost.exe 6. Ensure Services is set as default (all programs and services only) in the Program section, and click Next. 7. Select TCP for Protocol Type, Dynamic RPC for Local Port, All Ports for Remote Port in the Protocol and Ports section, and click Next. 8. Ensure the Scope and Action properties section is set as default and click Next. 9. Enable Domain, Private, and Public in Profile section, and click Next. 10. Set Name as ProSphere-Dynamic-RPC-ports and click Finish. Note: You can also type the following command at a command prompt to create the above rule: netsh advfirewall firewall add rule name="prosphere-dynamic-rpc-ports" dir=in action=allow program="%systemroot%\system32\dllhost.exe" protocol=tcp localport=rpc profile=public,private,domain Inbound firewall exception rule for port 135 To create an inbound exception rule for the port 135 ProSphere-WMI-DCOM-in: 1. Click Start > Administrative tools (Control Panel)> Windows firewall with Advanced Security. 2. Select Inbound Rules in the left hand navigation tree. 3. Right-click Inbound Rules and click on New Rule. 4. Select Rule Type as Custom and click Next. 5. Select This program path in the Program section, and type %SystemRoot%\System32\svchost.exe as a path for svchost.exe 6. Select Services by clicking on Customize button in the Program section. The Customize Service Settings dialog box appears. 7. Highlight Apply to this Service, select Remote Procedure Call(RPC) as the service, click OK and click Next. 8. Select TCP for Protocol Type, RPC Endpoint Mapper for Local Port, All Ports for Remote Port in the Protocol and Ports section, and click Next. 9. Ensure the Scope and Action properties section is set as default and click Next. 10. Enable Domain, Private, and Public in Profile section, and click Next. Configure Windows hosts and WMI 15

16 Configure Hosts 11. Set Name as ProSphere-WMI-DCOM-in and click Finish. Note: You can also type the following command at a command prompt to create the above rule: netsh advfirewall firewall add rule name="prosphere-wmi-dcom-in" dir=in action=allow program="%systemroot%\system32\svchost.exe" service=rpcss protocol=tcp localport=rpc-epmap profile=public,private,domain Inbound firewall exception rule to allow asynchronous WMI traffic To create an inbound firewall exception rule ProSphere-WMI-Async-in: 1. Click Start > Administrative Tools > Windows Firewall with Advanced Security. 2. Select Inbound Rules in the left hand navigation tree. 3. Right-click Inbound Rules and click on New Rule. 4. Select Rule Type as Custom and click Next. 5. Select This program path in the Program section, and type %SystemRoot%\System32\unsecapp.exe as a path for unsecapp.exe 6. Ensure Services is set as default (all programs and services only) in the Program section, and click Next. 7. Select TCP for Protocol Type, Dynamic RPC for Local Port, All Ports for Remote Port in the Protocol and Ports section, and click Next. 8. Ensure the Scope and Action properties section is set as default and click Next. 9. Select Profile as appropriate for the network, in the Profile section, and click Next. 10. Set Name as ProSphere-WMI-Async-in and click Finish. Note: You can also type the following command at a command prompt to create the above rule: netsh advfirewall firewall add rule name="prosphere-wmi-async-in" dir=in action=allow program="%systemroot%\system32\wbem\unsecapp.exe" protocol=tcp localport=rpc profile=public,private,domain Inbound firewall exception rule called Prosphere-WMI-in To create an inbound firewall exception rule ProSphere-WMI-in: 1. Click Start > Administrative Tools > Windows Firewall with Advanced Security. 2. Select Inbound Rules in the left hand navigation tree. 3. Right-click Inbound Rules and click on New Rule. 4. Select Rule Type as Custom and click Next. 5. Select This program path in the Program section, and type %SystemRoot%\System32\svchost.exe as a path for svchost.exe 6. Select Services by clicking on Customize button in the Program section. The Customize Service Settings dialog box appears. 7. Highlight Apply to this service, select Windows Management Instrumentation as the service, click OK and click Next. 16 EMC ProSphere: Preparing for Deployment

17 Configure Hosts 8. Select TCP for Protocol Type, Dynamic RPC for Local Port, and All Ports for Remote Port in the Protocol and Ports section, and click Next. 9. Ensure the Scope and Action properties section is set as default and click Next. 10. Select Profile as appropriate for the network, in the Profile section, and click Next. 11. Set Name as ProSphere-WMI-in and click Finish. Note: You can also type the following command at a command prompt to create the above rule: netsh advfirewall firewall add rule name=" Prosphere-WMI-in" dir=in action=allow program="%systemroot%\system32\svchost.exe" service=winmgmt protocol=tcp localport=rpc profile=public,private,domain For Windows 2003, if you are using a third-party firewall software or windows firewall software, then you need to configure the firewall exceptions to allow the traffic for port 135 and the dynamic RPC ports. The port 135 must be open to accept the incoming remote connection to the Service Control Manager (SCM), which provides RPC-based services for DCOM. The port allows the client to locate a DCOM service. Note: This procedure is required only if the port 135 is locked in the customer environment. To open the DCOM port: 1. Click Start, and then click Control Panel. 2. Double-click Windows Firewall, and then click the Exceptions tab. 3. Click Add Port. 4. Type DCOM_TCP135 in the Name field, and 135 in the Port number field. 5. Click TCP, and then click OK. 6. Click OK and close the Control Panel window. Note: You can also type the following command at a command prompt to open a port: netsh firewall add portopening protocol=tcp port=135 name=dcom_tcp135 mode=enable Firewall exception rule for dllhost.exe To create a firewall exception for dllhost.exe: 1. Click Start > Control Panel > Windows firewall. 2. Select Exceptions tab and click Add Program. The Add a Program dialog box appears. 3. Click Browse and select dllhost.exe from the path %SystemRoot%\System32\dllhost.exe and click OK. Note: You can also type the following command at a command prompt to create the above rule: netsh firewall add allowedprogram program="%systemroot%\system32\dllhost.exe" name="dllhost.exe" mode=enable Configure Windows hosts and WMI 17

18 Configure Hosts Make registry changes on a Windows Server 2008 R2 host The following DCOM-related host registry changes are required to discover a Windows Server 2008 R2 host. 1. Run the regedit command to open the Registry Editor and navigate to the key HKEY_CLASSES_ROOT\CLSID\76a64158-cb41-11d1-8b d9b6, which is for the WBEM Scripting Locator. 2. Right-click and select Permissions. 3. Choose the Administrators group and assign Full Control. 4. Click Advanced. 5. Click Owner, and change the owner to Administrators group. 6. Click Apply and OK. 7. Click OK and then exit the Registry Editor. 18 EMC ProSphere: Preparing for Deployment

19 Configure Hosts Configure UNIX and Linux hosts The following sections describe how to configure Linux and UNIX hosts for ProSphere discovery and performance data collection. Discovery requirements For discovery, ProSphere requires user credentials for Secure Shell (SSH) access to UNIX and Linux hosts. The user account used for discovery must be permitted access to the host to be discovered. These credentials are entered as SSH credentials in ProSphere. The EMC ProSphere Administrators Guide explains how to create access credentials. Run with root privileges One important requirement for Linux/UNIX host discovery is the ability for some discovery commands to run as root user. This can be achieved through tools or commands, such as sudo. Use sudo for host discovery Linux and UNIX host discovery requires use of the sudo command to elevate the discovery mechanism to root privilege for select commands. The sudo command enables you to: Temporarily elevate user credentials to root for specific commands that are configured in the sudoers file. Log on to a Linux/UNIX machine as a non-root user. Run SCSI commands to discover storage-related information for the host. The following commands require root privileges to run on a given host and are used for storage resource discovery: /tmp/nl_dwd/inq <path of powermt command>/powermt <path of dmidecode command>/dmidecode Note: If you have logged in as a sudo user, type the following to run the inq command: sudo /tmp/nl_dwd/inq -mapinfo Figure 1 on page 20 provides an example of additional, required sudoers file content. Configure UNIX and Linux hosts 19

20 Configure Hosts # sudoers file. # # This file MUST be edited with the 'visudo' command as root. # # See the sudoers man page for the details on how to write a sudoers file. # # Host alias specification # User alias specification User_Alias CMGU=cmguser # Cmnd alias specification Cmnd_Alias CMGEMC=/tmp/nl_dwd/inq,/<path of powermt command>/powermt,<path of dmidecode command>/dmidecode # Defaults specification # User privilege specification root ALL=(ALL) ALL CMGU ALL=NOPASSWD:CMGEMC # Uncomment to allow people in group wheel to run all commands # %wheel ALL=(ALL) ALL # Same thing without a password # %wheel ALL=(ALL) NOPASSWD: ALL # Samples # %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom # %users localhost=/sbin/shutdown -h now #cmguser ALL=(ALL) NOPASSWD: ALL Figure 1 Sample sudoers file content for Linux/UNIX host discovery Collect performance data For collection of path performance data, specific software (depending on host Operating System) must be running on the host. Solaris iostat Linux (RedHat and SuSE) The iostat package version must be installed on the Linux host for successful path performance collection. If the package is not installed, path performance collection fails with the error Failed to discover performance metrics. AIX sar HP-UX sar Windows 2000 and later The Windows Management Instrumentation (WMI) service must be enabled and running. Consult the relevant manpages and user documentation for installation and configuration instructions for these tools. Contact your UNIX vendor for information about downloading and installing their iostat (or sar) package. 20 EMC ProSphere: Preparing for Deployment

21 Configure Hosts Prepare for discovery of VMware guests For ProSphere to discover a VMware guest, VMware tools is required. Please work with your VMware admin to have VMware tools installed on your VMware guests. Prepare for discovery of VMware infrastructure The virtual infrastructure of VMware environments is discovered by ProSphere using the Virtual Infrastructure (VI) API. This Web Services API is hosted on VirtualCenter and ESX Servers and can be accessed by ProSphere for resource discovery. For more information about this service interface, refer to the VMware vsphere Web Services Documentation at: Discovery requirements For virtual infrastructure discovery, ProSphere requires: Individual ESX credentials or broader VirtualCenter credentials with Browse Datastore permissions. These credentials are entered as VMware Infrastructure credentials in ProSphere. The EMC ProSphere Administrators Guide provides instructions for creating discovery access credentials. Unblocked access to the IP address of the Web Services interface on all VMware ESX and VirtualCenter servers to discover. Prepare for discovery of VMware guests 21

22 Configure Hosts 22 EMC ProSphere: Preparing for Deployment

23 3 Configure Arrays This chapter provides configuration instructions for array data providers used by EMC ProSphere, such as SMI-S providers, to support resource discovery and data collection. This chapter includes the following sections: Configure the EMC SMI-S Provider Integrate ProSphere with SPA Configure Arrays 23

24 Configure Arrays Configure the EMC SMI-S Provider ProSphere can collect resource and performance data for EMC Symmetrix and CLARiiON storage arrays. Requirements for discovery data collection To discover supported Symmetrix, CLARiiON, and VNX storage devices and collect resource data from them in ProSphere, the following requirements must be met: Supported versions of the SMI-S Provider for the array must be installed on a host that is either connected to the array or has unblocked network access to the array. The SMI-S Provider is available for download from EMC Powerlink and may optionally be provided by EMC on CD-ROM. Installation instructions can be downloaded with the software in the EMC SMI-S Provider Release Notes. The SMI-S Provider host must be accessible by ProSphere in the network. The host IP address, access port, username, password, and interop namespace for the provider must be known to enter these as access credentials in ProSphere. These credentials are entered as SMI-S credentials. The EMC ProSphere Administrators Guide provides instructions for creating discovery access credentials. Consult the EMC ProSphere Support Matrix for supported versions of these arrays. Requirements for performance data collection EMC Symmetrix Performance Analyzer must be installed to collect and display Symmetrix performance data for the % busy metric in ProSphere. Integrate ProSphere with SPA on page 25 provides configuration details. Configure the provider The EMC SMI-S Provider is preinstalled on the service processor of Symmetrix VMAX arrays. However, to use this embedded SMI-S Provider, you must perform the following additional configuration steps. Configure a VMAX firewall In many IT environments, the VMAX firewall is normally enabled by default on the Symmetrix service processor. You can use the following instructions to open a port for SMI-S in this firewall. Windows SMI-S Provider host 1. If the VMAX firewall is enabled, you can configure it to allow SMI-S communications using these steps: a. Start the Firewall Configuration Utility located in the Windows Start menu under Programs > EMC Applications. b. Edit the active firewall configuration and add the preexisting firewall rule SMC SMI. This allows the EMC SMI-S Provider to be accessed on port 5989 using HTTPS (SSL) and allows indications to be sent over port 6012 to c. Ensure that the new firewall configuration is the active configuration. d. After the configuration changes have been made, reboot the VMAX service processor for the firewall changes to be updated. 24 EMC ProSphere: Preparing for Deployment

25 Configure Arrays 2. From the Windows Control Panel, double-click Administrative Tools and then Services to view the list of running services. 3. In the Services dialog box, right-click the ECOM service and select Properties. The ECOM Properties dialog box appears. 4. In the ECOM Properties dialog box, select a Startup type of Automatic and then click OK. 5. Reboot the host to allow the ECOM service to start automatically, or right-click ECOM in the Services dialog box and select Start to start it without a host reboot. Note: After you make these changes the embedded EMC SMI provider is only accessible on port 5989 using SSL. Be sure to reflect that in your ProSphere discovery access credentials. Integrate ProSphere with SPA Prerequisites Note: The EMC ProSphere Support Matrix provides the minimum version requirements for SPA and the Symmetrix Management Console (SMC). The following are prerequisites for successful SPA-ProSphere launch-in-context integration. Note: Refer to the ProSphere Release Notes for additional information about known limitations with SPA launch-in-context. 1. Preferably, only one SPA instance manages each Symmetrix array. If more than one SPA instance manages a Symmetrix array, all SPA instances must meet the minimum version requirement and must be the same version. 2. You must have existing, supported versions of SMC and SPA in your data center on a host that can be accessed through HTTP(S) by the ProSphere virtual machines. Ensure that no firewalls block their direct communication. The EMC Symmetrix Management Console and EMC Symmetrix Performance Analyzer Installation Guide provides installation instructions. Installation of SPA is independent of ProSphere installation. Note: SMC can be on a neutral host or on the service processor. SPA is on neutral hosts. SMC and SPA are not installed on ProSphere virtual machines. 3. SMC and SPA can reside on the same host. In this case, SMC and SPA together require 8 GB of RAM. Allow for additional memory required by SMI-S providers installed on the host. 4. Your SPA installation must already be configured to manage the Symmetrix resources in your data center. The EMC Symmetrix Management Console and EMC Symmetrix Performance Analyzer Installation Guide provides configuration instructions. Integrate ProSphere with SPA 25

26 Configure Arrays 5. Add ps-client to SMC as a Launch Client with ControlCenter set as the Client Type. A username and password are not required for this client type. Note: The addition of ps-client will initiate link-and-launch functionality for only one instance of ProSphere. 6. Restart the EMC Symmetrix Management Application Server (SMAS) service on the SMC/SPA host after adding ps-client as a Launch Client. The EMC Symmetrix Management Console and EMC Symmetrix Performance Analyzer Installation Guide provides service restart instructions. 7. To collect Array FE Directors - % Busy data for a Symmetrix array, ensure that the Base and Diagnostic collections are enabled for the array in the Administration -> Data Collection Registration dialog of SPA. 26 EMC ProSphere: Preparing for Deployment

27 Configure Arrays 8. In addition, for the Array FE Directors - % Busy metric chart, ensure SPA s FE Director -> % Busy is enabled in the Administration - Metric Management dialog as shown below. This metric is enabled by default as part of the SPA installation. Integrate ProSphere with SPA 27

28 Configure Arrays 28 EMC ProSphere: Preparing for Deployment

29 4 Configure Switches and Fabrics This chapter provides installation and configuration instructions for some common switch and fabric agents, such as SMI agents, to support resource discovery and data collection in EMC ProSphere. The chapter includes the following sections: Configure Cisco switches Configure the Brocade CMDCE Integrated SMI Agent Configure the Brocade SMI Agent Configure the Brocade SMI Agent for EOS Configure Switches and Fabrics 29

30 Configure Switches and Fabrics Configure Cisco switches This section applies to homogeneous fabrics that contain one or more Cisco switches. ProSphere supports two modes of SNMP communications for Cisco switches. The less secure SNMPv1/v2 mode and more secure SNMPv3 mode. Perform preconfiguration tasks Before you discover a Cisco switch or a homogeneous Cisco fabric in ProSphere: 1. Ensure all hardware (including switch model) and software is listed as supported in the EMC ProSphere Support Matrix 2. Verify the TCP/IP connectivity to the switches to be discovered. Test by issuing a ping command to these switches. 30 EMC ProSphere: Preparing for Deployment

31 Configure Switches and Fabrics 3. Determine if SNMP traps are enabled. Log in to the switch and run the show snmp trap command, as in the following example: SWDevCisco8-9216i# show snmp trap Trap type entity fru fcc fcdomain fcns fcs request-reject fcs discovery-complete fdmi fspf license rscn els rscn ils snmp authentication vrrp zone unsupported member zone request-reject zone merge-failure zone merge-success zone default-zone-behavior-change aaa server state-change link ietf-extended Enabled No No No No No No No No No No No No No No No No No No No yes In this example, many of the traps are not enabled. EMC recommends enabling all traps, unless there is a compelling reason not to do so. 4. Enable SNMP traps. Run the snmp-server enable traps command, as in the following example: SWDevCisco8-9216i# config terminal Enter configuration commands, one per line. End with CNTL/Z. SWDevCisco8-9216i (config)# snmp-server enable traps 5. Display the traps that are enabled. Run the show snmp trap command. The values in the Enabled column should be Yes. EMC recommends that all switches in the Cisco fabric have the same SNMP credentials for use with ProSphere. For example, if the SNMPv1/v2 community setting private is used, all Cisco switches in the fabric should have the SNMPv1/v2 Configure Cisco switches 31

32 Configure Switches and Fabrics private community name set with a role of network-admin. For an SNMPv3 user, the same SNMPv3 credentials with the role of network-admin should be set on every switch in the fabric. Cisco switch discovery is initiated by pointing ProSphere discovery dialog to a seed switch. ProSphere discovers all switches in the fabric by obtaining the fabric members from the seed switch. Therefore, all Cisco switches need to have either SNMPv1/2 or SNMPv3 configuration set. ProSphere discovers all the connected switches in a physical fabric. ProSphere does not support discovery of Cisco switches over FCIP connections. To discover a Cisco fabric that contains FCIP connections, discover a Cisco switch on either side of the FCIP connection. ProSphere does not support Cisco device aliases or Cisco enhanced device aliases. Configure switches for SNMPv1/2 The SNMPv1/2 information you enter when performing discovery is necessary for ProSphere to contact the switch to obtain information. ProSphere collects data from the switch using the same SNMP community name. It uses SNMP port for communication. This is normally hard set to port Refer to the Cisco documentation for detailed information on configuring Cisco switches for SNMPv1/v2 management. 2. The Cisco switches must have an SNMPv1 community name that has read/write privileges set on every switch in the fabric. The SNMP community selected must have a network-admin role. 3. Log in to the switch and log in as an administrator. 4. Use the snmp-server community command to configure read and write privileges as shown in the next example: Cisco8-9216i# config terminal Enter configuration commands, one per line. End with CNTL/Z. Cisco8-9216i(config)# snmp-server community eccuser rw 5. To determine if an SNMPv1 community user exists, log in to the switch and run the command as shown in following example: Cisco8-9216i# show snmp community Community eccuser Group / Access network-admin Configure switches for SNMPv3 This section contains guidelines on creating SNMPv3 users for discovery of and management of Cisco switches in ProSphere. 32 EMC ProSphere: Preparing for Deployment

33 Configure Switches and Fabrics The SNMPv3 information you enter when performing discovery is necessary for ProSphere to contact the switch to obtain information. ProSphere collects data from the switch using SNMPv3 secure credentials. ProSphere supports SNMPv3 only with SHA authentication and AES128 privacy. It uses the SNMP port for communication. The SNMP port is normally hard set to port 161. Note: ProSphere supports SNMP users that have SHA authentication and AES128 privacy only. Refer to the EMC ProSphere Support Matrix. EMC recommends creating the same SNMP v3 users with the same authentication and privacy passwords on all physical switches in the fabric. The Cisco documentation provides information on creating SNMP v3 users on Cisco MDS switches. For example, to create an SNMPv3 user called ECCuser with a network-admin role, SHA authorization, SHA password eccuser123!, and AES128 authentication with AES128 password of passw0rd123!, do the following: 1. Run the snmp-server user command as shown in following example: Cisco8-9216i# config terminal Enter configuration commands, one per line. End with CNTL/Z. Cisco8-9216i (config)#snmp-server user ECCuser network-admin auth sha eccuser123! priv aes-128 passw0rd123! 2. Confirm the new user creation by running the show snmp user command as shown in the following example: Note: On the switch that uses MD5 authentication, the default user is admin. SWDevCisco8-9216i# show snmp user SNMP USERS User Auth Priv(enforce) Groups admin md5 no network-admin ECCuser sha aes-128(no) network-admin NOTIFICATION TARGET USERS (configured for sending V3 Inform) User Auth Priv SWDevCisco8-9216i# Configure Cisco switches 33

34 Configure Switches and Fabrics Configure the Brocade CMDCE Integrated SMI Agent This section applies to homogenous and mixed fabrics that contain one or more Brocade FOS and/or EOS (McDATA) switches managed by the Brocade CMDCE Integrated SMI Agent. CMDCE Connectrix Manager Data Center Edition (CMDCE) is the next generation Connectrix manager. Brocade CMDCE Integrated SMI Agent has unified management of Brocade FOS, EOS (McDATA), and mixed multiprotocol fabrics in and across data centers under a single namespace. Download the agent CMDCE is available on Powerlink. Go to and follow this path to download the application: Support > Software Downloads and Licensing > Downloads C > Connectrix Manager > EMC Connectrix Manager Data Center Edition. The SMI Integrated Agent is supported with CMDCE Enterprise/Professional Plus and above. Perform preconfiguration tasks Perform the following steps before you discover an individual Brocade FOS or EOS (McDATA) switch or fabric in ProSphere: 1. Read the Brocade CMDCE SMI Agent documentation. This documentation consists of release notes, installation, and user guides. 2. Ensure all hardware (including switch model) and software is listed as supported in the EMC ProSphere Support Matrix. 3. Ensure switch firmware levels are listed as supported in the Brocade SMI Agent release notes available from the Brocade website. CMDCE is available in three flavors: CMDCE Professional Edition Intended for the management of smaller fabrics with Connectrix B Series departmental switches. CMDCE Professional Plus Edition (new in CMDCE ) Midway between Professional and Enterprise for scalability support and also supports the ED-DCX-4S-B. CMDCE Enterprise Edition A full-featured Enterprise class management solution for the largest of data center SAN infrastructures. No license is required for the Professional version; however, a license is required for the Professional Plus or Enterprise Edition, which can be obtained by ordering the models listed above. It is possible to run the CMDCE Professional Plus or Enterprise versions under a 75-day trial license; however, this should only be done for short-term evaluation purposes. After 75 days you will not be able to log in with a CMDCE client; therefore, production environments are only supported if fully licensed. 34 EMC ProSphere: Preparing for Deployment

35 Configure Switches and Fabrics For complete details on installing any of the above-mentioned options, refer to Chapter 2 (Installation) of the Connectrix Manager Data Center Edition Professional, Professional Plus, and Enterprise User Guide. Go to and download the User Guide from Support > Technical Documentation and Advisories > Hardware/Platforms Documentation > Connectrix Directors and Switches > General Reference > Connectrix Manager Data Center Edition Professional, Professional Plus, and Enterprise User Guide. Note: The SMI Integrated Agent is supported with CMDCE Enterprise or Professional Plus and above. Configure the CMDCE to manage a fabric To discover a Brocade fabric in ProSphere, the fabric must be discovered in CMDCE fully. CMDCE discovers a complete fabric through a proxy switch called the seed switch. For more details on selecting the seed switch, refer to the Connectrix Manager Data Center Edition Professional, Professional Plus, and Enterprise User Guide. To discover a fabric in CMDCE: 1. Select Discover > Setup. The Discover Setup dialog box appears. 2. Click Add Fabric to specify the IP addresses of the devices you want to discover. The Address Properties dialog box appears. 3. Type the following details: Fabric Name IP Address User ID Configure the Brocade CMDCE Integrated SMI Agent 35

36 Configure Switches and Fabrics Password 4. Click SNMP. Type the following details: Target Port Time-out (sec) Retries 5. Select SNMP Version and provide the required SNMP details for the selected SNMP version. 6. Click OK. 36 EMC ProSphere: Preparing for Deployment

37 Configure Switches and Fabrics After discovery, the fabric information appears in the main CMDCE window. Configure the Brocade SMI Agent The section applies to homogeneous fabrics that contain one or more Brocade FOS switches. Documentation and drivers for the Connectrix B Series SMI-S The Brocade website for SMI-S drivers and documentation for both B-Series and M-Series can be found on the Brocade home page at the following URL: agent/application_matrix.page Perform preconfiguration tasks Perform the following steps before you discover an individual Brocade FOS switch or a homogeneous Brocade fabric in ProSphere: 1. Read the Brocade SMI Agent documentation. This documentation consists of release notes, installation, and user guides. 2. Ensure all hardware (including switch model) and software is listed in the Brocade SMI Agent documentation Configure the Brocade SMI Agent 37

38 Configure Switches and Fabrics Install the agent on Windows The Brocade SMI Agent (also referred to as the Brocade SMI provider ) is a host-based provider that must be running, and must be configured to manage the selected switches before ProSphere discovery. The Brocade SMI Agent is a proxy agent to a Brocade fabric or multiple Brocade fabrics, and resides on a host. It is not embedded in the switch. The following is the recommended procedure for installing the Brocade SMI Agent for use with ProSphere. 1. Determine the most appropriate host location for installing the Brocade SMI Agent. 2. Download the Brocade SMI Agent from the Brocade SMI Agent Download page. The EMC ProSphere Support Matrix provides the version of the SMI provider that ProSphere supports. 3. Extract the zip file. 4. Run the install.exe. 5. Read and accept the license agreement. 6. Check the system configuration. 7. Accept the JRE version. 8. Select an install directory. 9. Select CIMOM HTTP port If this port is in use, you are prompted to enter a new port. 10. Select CIMOM HTTPS port If this port is in use, you are prompted to enter a new port. The agent installs the FM configuration for the SMI Agent. 11. Accept the defaults and click Next. 12. At Enable mutual authentication for client, select No. 13. At Enable mutual authentication for indications, select No. 14. At Import the client certificate for mutual authentication, click Next. 15. At Importing the client certificate for mutual authentication for indications, click Next. 16. At Export the server certificate for mutual authentication, click Next. 17. At Export the server certificate for mutual authentication for indications, click Next. 18. At Enable security, select No if no security, or Yes for Windows security. Brocade documentation provide further details. 19. At Configure events and ARR TCP ports, indicate whether a firewall exists between the switches and the SMI Agent. Brocade documentation provides further details. 20. At Enable console and/or file logging, for Console logging select Yes. For file logging, select Yes. 21. At Configure the log file, accept the defaults. 22. At Configure the proxy connections, observe the following recommendation. 38 EMC ProSphere: Preparing for Deployment

39 Configure Switches and Fabrics Recommendations for EMC proxy configuration During installation of the SMI Agent, add only the proxy switch of each fabric to be discovered in ProSphere. In each fabric to be discovered, one of the switches in the fabric is to be selected as most suitable for a proxy switch. A proxy switch should be selected using the following recommended criteria, which are listed in descending order of importance: Select the switch with the highest FOS firmware version Where possible, select a core switch Where possible, select a director switch This is the only way the proxy switch selection can be controlled. If all switches are added during the configuration of the SMI Agent, the agent will dynamically select the proxy switch. This method may not select the most suitable switch. Verify that the scalability guidelines are met when selecting the number of fabrics and proxy switches. For example, if managing five fabrics containing five switches, the Brocade SMI Agent can be configured to discover a proxy from each of the five fabrics. However, if there are three fabrics of 50 switches per fabric, then three SMI Agents should be used. These scalability guidelines are in the Brocade SMI Agent release notes. The IP address, the username, and password of the proxy switch must be known. Where possible, select a user with the same permissions as the Brocade admin user. This would be the user with privileges to log in to the switch. 23. Note the configuration locations. 24. Configure and start the Brocade SMI Agent as a service. EMC recommends that you select Yes. When configuring the fabric's SMI Agent to proxy, the file provider.xml file is created on the SMI Agent host at the following default location: <SMIA Installation Root>\agent\server\jserver\bin This file should be edited after the first full ProSphere discovery, to enable the SMI Agent to notify ProSphere when a fabric segmentation/merge occurs. All the TCP/IP addresses and configuration details of the switches in the fabric need to be added to the provider.xml file so that when a fabric segmentation or merge occurs, ProSphere can display the new fabrics. If a merge occurs, a rediscovery is necessary before the changes are visible. If ProSphere is managing a three-switch fabric consisting of switch1, switch2, and switch3, you must manually setup three switch entries in the provider.xml file, with the created_by_agent value set to false. By enabling the automatic rescan of this file after a fabric segmentation/merge occurs, the SMI Agent can notify ProSphere about the change in the state of the fabric. Configure proxy connections Perform the following procedure to add proxy connections on the host where the SMI agent is installed: 1. Launch the Brocade SMI Agent Configuration Tool. 2. Click Proxies in the menu tree. Configure the Brocade SMI Agent 39

40 Configure Switches and Fabrics 3. Click Add. 4. Fill out the Proxy Configuration dialog box and click OK. 5. Click Apply The configuration values for the new fabric are displayed in the content pane. The value in the Status column is Not Connected, which means that the proxy entry is configured but the SMI Agent is not connected to the fabric. You are prompted to start the SMI Agent if it is not already started. Click Start Server in the lower left corner of the window. The SMI Agent attempts to log in to the fabric. The Status field in the content pane displays the status of the login attempt. When login is successful, the Status field displays Connected. The SMI Agent is set to use 1 RPC handle as default. The recommendation going forward is to use 1 RPC handle. This does not negatively impact performance. Include multiple switch connection entries from the same fabric Perform the following steps: 1. Stop the SMI Agent server. 2. Edit the provider.xml file manually by providing the connection entry for each switch. 40 EMC ProSphere: Preparing for Deployment

41 Configure Switches and Fabrics 3. Enable the connection reload through the Configuration Tool. 4. Alternatively, you can edit the SMIAgentConfig.xml file and set the connection reload flag to true so that rescan of the provider.xml is enabled. 5. Start the SMI Agent server. The default location of file provider.xml is: <SMIA InstallationRoot>\agent\server\jserver\bin The following example shows how to edit the provider.xml file to configure multiple Brocade switches. <!xml version= 1.0 encoding= ISO ?> <!DOCTYPE connection_config SYSTEM Connection.dtd > <connection_config> <connection address= xxx.xxx.xxx.xxx address_type= IPv4 created_by_agent= false is_password_encrypted= true login_scheme= NonSecureSAN multiple_connections= true num_rpc_handles= 5 password= oca8n6bohod6segnw84qra== protocol= RPC timeout= 60 user= admin /> <!--COPY THE connection TAG ABOVE AND PASTE FOR EACH SWITCH ENTRY. EDIT THE SWITCH IP, USER AND PASSWORD FOR EACH SWITCH--> </connection_config> Configure multiple Brocade switches For fabrics that contain multiple Brocade FOS switches, set the value of the connection reload flag in the SMIAgentConfig.xml file to true. This causes the SMI Agent to reload all the switch entries from the provider.xml file when the connection to the first switch in the discovery sequence is down. For example, if the connection to switch1 remains down, the SMI Agent tries to connect to switch2 or switch3. The default location of file SMIAgentConfig.xml is: <SMIA Installation Root>\agent\server\jserver\bin Configure the Brocade SMI Agent 41

42 Configure Switches and Fabrics The following example shows an SMIAgentConfig.xml file edited to allow a rescan of file. The file provider.xml shows an SMIAgentConfig.xml file with the connection reload flag set to true. This allows a recscan of the file. <?xml version= 1.0 encoding= ISO ?> <!DOCTYPE agent_config SYSTEM smiagentconfig.dtd > agent-config> <! Sample entry for FM database server configuration --> <!-- dbserver driver= url= username= password= / --> <!-- Sample entry for eventing and arr port --> <!-- port_config eventing= arr= / --> <!-- Sample entry for firmware download configuration --> <!-- firmware_download address= username= password= url= / --> <!-- The url field in firmware_download can have both the relative and the absolute path. E.g., if the path is relative it should be: url= SQA/5.0.x/v5.0.1_main_bld37/release.plist but if the path is absolute it should be url= /pub/sre/sqa/5.0.x/v5.0.1_main_bld56/release.plist --> <dbserver driver= com.sybase.jdbc2.jdbc.sybdriver url= username= password= is_password_encrypted= false /> <port-config eventing= arr= /> <secureport_config eventing= arr= /> <host address= /> <connection reload= true /> <eventing retries= interval= /> <timeout fwdlinterval= /> </agent_config> The password encryptor is a tool used to encrypt the switch passwords if they should differ from the proxy switch. This is only necessary when editing the provider.xml and adding the other switches in the fabric after switch discovery. Obtain an encrypted password on page 42 provides more information. Obtain an encrypted password Use the PasswordEncryptor.bat tool, installed with the SMI Agent, to obtain the encrypted password for a switch entered in the provider.xml connection tag. You only need to use this tool when different passwords are configured on the switches. This tool resides in the following default location on the SMI Agent host: <SMIA Installation Root>\agent\bin Execute this tool from the command line as follows: C:\SMIAgent\agent\bin>PasswordEnvryptor.bat Enter the password to encrypt password Encrypted password: cca8n6bohod6segnw84qra== Verify the installation Once the Brocade SMI Agent for FOS is installed, verify that it meets the following conditions: 42 EMC ProSphere: Preparing for Deployment

43 Configure Switches and Fabrics The agent is running on a host with a supported OS that has sufficient processor and memory requirements for the number of ports being managed. Brocade SMI Agent documentation provides more details. The agent has TCP/IP connectivity to the switches being managed. For ProSphere discovery, configure the following items: Port for HTTP communications from ProSphere to SMI Agent. The default is Port for HTTPS communication from ProSphere to SMI Agent. The default is Username and password used by ProSphere to authenticate to the Brocade SMI-S provider. Selection of a proxy switch in the Brocade FOS fabric to be discovered. The IP address, username, and password for a proxy switch must be known. Configure the Brocade SMI Agent for EOS This section applies to homogeneous fabrics that contain one or more Brocade EOS (McDATA) switches. Documentation and drivers for the Connectrix M Series SMI-S The Brocade website for SMI-S drivers and documentation for both B-Series and M-Series can be found on the Brocade home page at the following URL: agent/application_matrix.page Perform preconfiguration tasks Perform the following steps before you discover an individual Brocade EOS (McDATA) switch or a homogeneous Brocade EOS (McDATA) fabric in ProSphere: 1. Read the Brocade SMI Agent for EOS documentation. This documentation consists of release notes, installation, and user guides. 2. Check the Brocade SMI Agent for EOS documentation to ensure all hardware (including switch model) and software is supported by Brocade SMI Agent for EOS. Install the agent on Windows The Brocade SMI Agent for EOS switches is a proxy agent to a fabric or multiple fabrics, and resides on a host. It is not embedded in the switch. The Brocade SMI Agent for EOS can be installed on the Connectrix Manager host if the host processor and memory resources are sufficient. See the Brocade SMI Agent for EOS products installation guide for more information. The Brocade SMI Agent for EOS can only be configured to communicate to one instance of Connectrix Manager. The following is the recommended procedure for installing the Brocade SMI Agent for EOS for use with ProSphere. Configure the Brocade SMI Agent for EOS 43

44 Configure Switches and Fabrics 1. Download Brocade SMI Agent for EOS from the Brocade SMI Agent Download page. The EMC ProSphere Support Matrix provides the version of the SMI provider that ProSphere supports. 2. Extract the zip file. 3. Run the install.exe. 4. Read and accept the license agreement. 5. Select the type of installation. 6. Select the installation set. Select the default. 7. Select the installation directory. 8. Review the preinstallation summary and click Install. 9. Select how SMI Agent for M-EOS communicates with switches. Select one of the following options: a. Via Management Platform option or b. Direct Connection. Direct connection mode can only be used where Connectrix Manager is not installed. 10. If Via Management Platform was selected, enter the network address, username, and password of Connectrix Manager. The username entered is a user that has the required credentials to log into Connectrix Manager. Test the connection validates that this user can successfully authenticate and communicate with Connectrix Manager, as the following screen illustrates. 11. If direct connection is selected, click Add Switch to add the switch configuration details. Add the IP address of the switch, the product type, and the username and password that can authenticate to the switch. To verify that the correct username 44 EMC ProSphere: Preparing for Deployment