53-1002320-01 13 May 2011 Brocade Network Advisor Installation Guide Supporting Network Advisor 11.1.
Copyright © 2010-2011, Brocade Communications Systems, Incorporated. Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, IronPoint, IronShield, IronView, IronWare, JetCore, NetIron, SecureIron, ServerIron, StorageX, and TurboIron are registered trademarks, and Network Advisor, Extraordinary Networks, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
In this guide In this guide • Edition feature support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 • Network Advisor packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 • Management server and client ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 • System requirements . . . . . . . . . . . . . . . . . . .
Edition feature support TABLE 1 SAN features supported (Continued) Feature Description Professional Professional Plus Network Advisor Client Authentication Authorization Auditing Network Advisor user management No Yes Yes Yes Yes Yes Layer 2 FC support Yes Yes Yes Encryption configuration and monitoring No Yes Yes Access Gateway – Cisco interop support No Yes Yes Device decommissioning No Yes Yes Fabric Binding Fabric Binding No Yes Yes Fabric Watch All Fabric Watch feat
Edition feature support TABLE 1 SAN features supported (Continued) Feature Description Client - Server support Professional Professional Plus Enterprise No No No NOTE: Raw IPv6 is not supported for Client Server communication (Northbound address) due to a JBOSS version limitation.
Edition feature support TABLE 1 SAN features supported (Continued) Feature Description Professional Professional Plus RBAC Reports User management No Yes Yes Generate Yes Yes Yes View Yes Yes Yes Up to 1000 port support Yes Yes Yes Up to 2560 port support No Yes Yes Up to 9000 port support No No Yes Replicate switch policy configuration No Yes Yes SNMP configuration Yes Yes Yes L2 ACL Yes Yes Yes SMI Agent Server Profile Fabric Profile Indication Sub Profile Zone
Edition feature support TABLE 1 SAN features supported (Continued) Feature Telnet Description Telnet Professional Professional Plus Enterprise Yes Yes Yes NOTE: Telnet through the server is only supported on Windows systems.
Network Advisor packages Network Advisor packages Table 2 summarizes the packages and available versions for each package. TABLE 2 Packages and versions Package Versions SAN with SMI Agent Licensed Version—Enterprise SAN—Support for 24 fabrics, 10,000 devices, and 9,000 switch ports • Licensed Version—Professional Plus • SAN—Support for 4 fabrics, 4,096 devices, and ,2560 switch ports Professional • SAN—Support for 1 fabric and 1,000 ports NOTE: SMI Agent is not supported on Professional.
Management server and client ports TABLE 3 Professional ports (Continued) Port Number Ports Transport Description Communication Path Open in Firewall 80 jboss.web.http.port TCP Non-SSL HTTP/1.1 connector port Client–Server No 803, 4, 5 Switch http TCP Switch non-SSL http port for http and CAL communication Server–Switch Client–Switch Yes 1611 SNMP Port UDP Default SNMP port Server–Switch Yes 3 snmp.trap.
Management server and client ports TABLE 3 Professional ports (Continued) Port Number Ports Transport Description Communication Path Open in Firewall 24610 connector.bind.port – port 10 TCP Port to listen for requests on Server No 1 Port is not configurable (either in the switch or the Management server). 2 Every FTP session requires an additional port which is randomly picked.
Management server and client ports TABLE 4 Trial and Licensed Version ports (Continued) Port Number Ports Transport Description Communication Path Open in Firewall 389 LDAP Authentication Server Port TCP LDAP server port for authentication if LDAP is chosen as an external authentication Server–LDAP Server Yes 4433, 4, 5 Switch https TCP Switch SSL http port for https and CAL communication Server–Switch Client–Switch Yes 5146 Syslog Port UDP Default Syslog Port Switch–Server Yes 636
Management server and client ports TABLE 4 Trial and Licensed Version ports (Continued) Port Number Ports Transport Description Communication Path Open in Firewall 24610 jboss.jrmp.invoker.port - port 10 TCP RMI/JRMP invoker port Client–Server Yes 24611 jboss.pooled.invoker.port - port 11 TCP Pooled invoker port Client–Server Yes 24612 jboss.connector.socket.port - port 12 TCP Socket invoker port Server No 24613 jboss.web.ajp.port - port 13 TCP AJP 1.
System requirements System requirements Use the following sections to determine if you have met the requirements for this application.
System requirements TABLE 5 Server operating system requirements (Continued) Operating system Version Guest OS version Supported packages VMware • • ESX Server 4 vCenter 4.1 • Windows 2003 Server SP2 (32-bit) Windows 2008 Standard Edition (32-bit) SAN with SMI Agent SMI Agent only • • ESX Server 4 vCenter 4.1 • Windows 2008 R2 Data Center Edition (64-bit) Windows 2008 R2 Standard Edition (64-bit) Windows 2008 R2 Enterprise Edition (64-bit) Linux RedHat 5.
System requirements Host requirements Table 7 summarizes the minimum required host requirements for running Network Advisor SAN with SMI Agent on Windows and Linux systems. TABLE 7 SAN with SMI Agent host requirements Professional Professional Plus Enterprise Small Medium Large LAN Server plus one local client Intel Core2 duo 2GHz or equivalent Intel Core2 duo 2GHz or equivalent Intel Core2 duo 2GHz or equivalent Intel Dual CPU Core2 duo 2.4 GHz or equivalent Intel Dual CPU Core2 duo 2.
System requirements Table 10 summarizes the minimum required system memory requirements for running SMI Agent only on Windows and Linux systems. TABLE 10 SMI Agent only memory requirements Server/Client Enterprise Small Medium Large Server plus 1 local client 3 GB 4 GB 4 GB Remote client only 1 GB 2 GB 2 GB Disk space requirements Table 11 summarizes the minimum required disk space requirements for running Network Advisor SAN with SMI Agent on Windows and Linux systems.
System requirements Client and server system requirements Network Advisor has the following client and server system requirements: • • • • • Professional Edition — A single server supports a single client (local client only). Professional Plus Trial — A single server supports a maximum of 8 clients (local or remote). Professional Plus Licensed Version — A single server supports a maximum of 8 clients (local or remote). Enterprise Trial — A single server supports a maximum of 8 clients (local or remote).
System requirements TABLE 16 Supported limits by SAN size for mixed fabrics (Fabric OS and M-EOS fabrics) Values Small Medium Large Number of Fabrics 8 16 24 Number of Domains 10 30 60 Number of Switch Ports 1000 2500 5000 Number of Device Ports 2500 5000 10000 Number of Access Gateways 20 30 40 Performance Monitoring Polling 5 minutes 5 minutes 5 minutes TABLE 17 Supported limits by SAN size for pure M-EOS fabrics Small Medium Large Number of Fabrics 8 16 24 Number of
Pre-installation requirements TABLE 19 Supported limits by SAN size for SMI Agent only on mixed fabrics (Fabric OS and M-EOS fabrics) Values Small Medium Large Number of Fabrics 8 16 24 Number of Domains 10 30 60 Number of Switch Ports 1000 2500 5000 Number of Device Ports 2500 5000 10000 Number of Access Gateways 20 30 40 TABLE 20 Supported limits by SAN size for SMI Agent only on pure M-EOS fabrics Small Medium Large Number of Fabrics 8 16 24 Number of Domains 10 30 6
Installing the application • Make sure that an X Server is available for display and is configured to permit X Client applications to display from the host on which they are installing the Network Advisor server (typically, this simply requires that the systems console be present and running with a logged-in user on the X Server-based desktop session, such as KDE, GNOME, and so on).
Headless installation NOTE Do not install to the root directory C:\ (Windows) or / (UNIX). 5. Review the displayed installation summary on the Pre-Installation Summary screen and click Install. 6. Make sure the Launch Configuration check box is selected (default) on the Installation Complete screen, and click Done.
Headless installation • Make sure that the DISPLAY environment variable is correctly defined in the shell with a valid value (for example, to display to the local console, export DISPLAY=:0.0, or to display to a remote system that has an X Server running, export DISPLAY=Remote_IP_Address:0.0).
Professional edition configuration Professional edition configuration Use Table 22 to help configure Professional edition. If you have not installed the application, refer to “Installing the application” on page 20. If you are migrating data, refer to the Network Advisor Migration Guide.
Professional edition configuration 6. Complete the following steps on the Server IP Configuration screen (Figure 2). FIGURE 2 Server IP Configuration screen The Server IP Configuration address is set to “localhost” by default. You cannot change this address. 7. a. Select an address from the Switch - Server IP Configuration Preferred Address list. b. Click Next. Complete the following steps on the Server Configuration screen (Figure 3). NOTE Do not use port 1527 for any of these port numbers.
Trial configuration d. Enter a port number in the Syslog Port # field (default is 514). NOTE If the default syslog port number is already in use, you will not receive any syslog messages from the device. To find and stop the process currently running on the default syslog port number, refer to “Syslog troubleshooting” on page 39. e. Enter a port number in the SNMP Port # field (default is 162). f. Click Next. If you enter a syslog port number already in use, a message displays.
Trial configuration 4. Select Network Advisor - 75 days Trial on the Installation Type screen and click Next. ATTENTION If you choose to install Trial, once the trial period ends (75 days), you must upgrade to Licensed Version package. 5. Complete the following steps on the Trial Configuration screen. a. (SAN with SMI Agent) Select one of the following from the SAN with SMI Agent options: - b.
Trial configuration 7. Complete the following steps on the Server IP Configuration screen (Figure 5). FIGURE 5 Server IP Configuration screen a. Select an address from the Server IP Configuration list. b. Select an address from the Switch - Server IP Configuration Preferred Address list. NOTE If the “hostname” contains invalid characters, the host name does not display in the list. Valid characters include alphanumeric and dash (-) characters. The IP address is selected by default.
Trial configuration 8. Complete the following steps on the Server Configuration screen (Figure 6). NOTE Do not use port 2638 for any of these port numbers. Port 2638 is used internally by the server. FIGURE 6 Server Configuration screen a. Enable SSL by selecting the SSL Enabled check box (default is not selected). b. Enter a port number in the Web Server Port # field (default is 443 if SSL Enabled is selected; otherwise, the default is 80). c.
Trial configuration 9. (SAN with SMI Agent) Complete the following steps on the SMI Agent Configuration screen (Figure 7). FIGURE 7 SMI Agent Configuration screen a. Enable the SMI Agent by selecting the Enable SMI Agent check box. b. Enable the SLP by selecting the Enable SLP check box, if necessary. Only enabled after you select the Enable SMI Agent check box. c. Enable the SSL by selecting the Enable SSL check box, if necessary. Only enabled after you select the Enable SMI Agent check box. d.
License version configuration 12. Complete the following steps on the Start Server screen. a. (SAN with SMI Agent) Select the Start SMI Agent check box, if necessary. b. (SAN with SMI Agent) Select the Start SLP check box, if necessary. c. Select the Start Client check box, if necessary. d. Click Finish. After all of the services (Server, SLP, and SMI Agent) are started, you can access the Server Management Console.
License version configuration 5. (Licensed Version only) If you are installing a licensed edition, enter the license key (on the Key Certificate) on the Server License screen or browse to the license file (.xml) and click Next. The License Key field is not case-sensitive. 6. Select Internal FTP Server or External FTP Server on the FTP Server screen and click Next. If port 21 is busy, a message displays. Click OK to close the message and continue.
License version configuration 7. Complete the following steps on the Server IP Configuration screen (Figure 9). FIGURE 9 Server IP Configuration screen a. Select an address from the Server IP Configuration list. b. Select an address from the Switch - Server IP Configuration Preferred Address list. NOTE If the “hostname” contains invalid characters, the host name does not display in the list. Valid characters include alphanumeric and dash (-) characters. The IP address is selected by default.
License version configuration 8. Complete the following steps on the Server Configuration screen (Figure 10). NOTE Do not use port 2638 for any of these port numbers. Port 2638 is used internally by the server. FIGURE 10 Server Configuration screen a. Enable SSL by selecting the SSL Enabled check box (default is not selected). b. Enter a port number in the Web Server Port # field (default is 443 if SSL Enabled is selected; otherwise, the default is 80). c.
License version configuration 9. Complete the following steps on the SMI Agent Configuration screen (Figure 11). FIGURE 11 SMI Agent Configuration screen a. Enable the SMI Agent by selecting the Enable SMI Agent check box. b. Enable the SLP by selecting the Enable SLP check box, if necessary. Only enabled after you select the Enable SMI Agent check box. c. Enable the SSL by selecting the Enable SSL check box, if necessary. Only enabled after you select the Enable SMI Agent check box. d.
SMI Agent only configuration After all of the services (SLP and SMI Agent) are started, the configuration wizards closes. To make changes to the SMI Agent configuration, you can re-launch the configuration wizard (Start > Programs > Network Advisor 11.1.X > Configuration Wizard). You can access the SMIA Configuration Tool from the Server Management Console (Start > Programs > Network Advisor 11.1.X > Server Management Console).
SMI Agent only configuration 4. Complete the following steps on the Server IP Configuration screen. FIGURE 12 Server IP Configuration screen a. Select an address from the Server IP Configuration list. b. Select an address from the Switch - Server IP Configuration Preferred Address list. If DNS is not configured for your network, do not select the “hostname” option from either the Server IP Configuration or Switch - Server IP Configuration Preferred Address list.
SMI Agent only configuration 5. Complete the following steps on the Server Configuration screen. NOTE Do not use port 2638 for any of these port numbers. Port 2638 is used internally by the server. FIGURE 13 Server Configuration screen a. Enable SSL by selecting the SSL Enabled check box (default is not selected). b. Enter a port number in the Web Server Port # field (default is 443 if SSL Enabled is selected; otherwise, the default is 80). c.
SMI Agent only configuration 6. Complete the following steps on the SMI Agent Configuration screen. The Enable SMI Agent and Enable SLP check boxes are selected by default and cannot be cleared. 7. a. Enable the SSL by selecting the Enable SSL check box, if necessary. b. Enter the SMI Agent port number in the SMI Agent Port # field (default is 5989 if SSL Enabled is selected; otherwise, the default is 5988). c. Click Next.
Syslog troubleshooting Syslog troubleshooting If the default syslog port number is already in use, you will not receive any syslog messages from the device. Use one of the following procedures (depending on your operating system), to determine which process is running on the syslog port and to stop the process. Windows operating system Finding the process 1. Open a command window. 2. Type netstat –anb | find /i “514” and press Enter. The process running on port 514 displays.
Installing the ODBC driver Installing the ODBC driver You must have the Open Database Connectivity (ODBC) driver to allow remote clients to export data and generate reports. The ODBC driver enables you to configure the data source name (DSN) for the Network Advisor database. Installing the ODBC driver on Windows systems You must have the Open Database Connectivity (ODBC) driver to allow remote clients to export data and generate reports.
Configuring an explicit server IP address 18. Click Test to test the connection. NOTE You can also use the Windows ODBC Driver Manager to add the DSN for the LINUX database server. 19. Click OK on the Connection Test dialog box. 20. Click Save. 21. Click OK on the ODBC Data Source Administrator dialog box.
Smart Card driver installation 6. Click Next on the Server Configuration screen. 7. (SAN with SMI Agent) Click Next on the SMI Agent Configuration screen. 8. Verify your configuration information on the Server Configuration Summary screen and click Next. 9. Click Finish on the Start Server screen. 10. Click Yes on the restart server confirmation message. 11. Enter your user name and password. The defaults are Administrator and password, respectively. 12. Click Login. 13. Click OK on the Login Banner.
Smart Card driver installation 4. If you installed a pcsc directory into a location other than /opt, modify the pcscctl script to change “/opt” to the directory you specified in step 1. > cd > vi pcscctl Search for “/opt” and change it to the name of the new directory. 5. Create a soft link into the system directory. This is to support the automatic restart of the pcscd daemon upon system restart. If you installed the pcsc directory into the /opt directory, just create the soft link.
Smart Card driver installation Installing the Smart Card driver on the remote client 1. Complete steps 1 through 4 in “Installing the Smart Card driver on the local client” on page 42. 2. Run the following commands to support remote clients (Web Start). > cd /usr/lib > ln –s /opt/pcsc/lib/libpcsclite.so . NOTE If a soft link exists on libpcsclite.so, make sure that the final file is linked to /opt/pcsc/lib/libpcsclite.so.xxx. It is recommended that you back up the original.
Smart Card driver installation 3. If there is an existing pcscd script in this directory, you can move and rename this file before you overwrite it. > mv /etc/init.d/pcscd /etc/init.d/pcscd.org 4. Create a soft link using the following command. > ln –s /opt/pcsc/pcscctl /etc/init.d/pcscd The existing pcscd.org script in this directory implies that a different driver version exists. You can compare the existing one with the one under /opt/pcsc/pcscd/sbin.
Uninstallation Uninstallation This section provides step-by-step instructions to uninstall Network Advisor and SMI Agent from both Windows and UNIX systems. NOTE Network Advisor is installed on a separate directory from your previous version; therefore, you do not need to uninstall the previous version immediately. However, you cannot run both versions simultaneously. Uninstalling from Windows systems Follow these instructions to uninstall the Network Advisor and SMI Agent from your Windows system. 1.
Uninstallation Uninstalling from UNIX systems (headless uninstall) If the application was installed using the headless installation, complete the following steps to uninstall Network Advisor and SMI Agent from your UNIX server. 1. Go to Install_Home/Uninstall_Network_Advisor11_X_X. 2.
