53-1003374-01 18 Aug 2014 Brocade Network Advisor SAN Installation and Migration Guide Supporting Network Advisor 12.3.
Copyright © 2006-2013 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, Brocade Assurance, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, MLX, NetIron, SAN Health, ServerIron, TurboIron, VCS, and VDX are registered trademarks, and AnyIO, Brocade One, CloudPlex, Effortless Networking, ICX, NET Health, OpenScript, and The Effortless Network are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
Contents About This Document In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . viii Fabric OS hardware and software support . . . . . . . . . . . . . . . . viii What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Document conventions . .
Chapter 2 Network Advisor Configuration Configuring Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Accessing the Network Advisor interfaces . . . . . . . . . . . . . . . . . . . . 24 Logging into a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Launching a remote client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Clearing previous versions of the remote client . . . . . . . . . . . . 26 Launching the SMC on Windows . . . . .
Uninstalling from Windows systems (headless uninstall) . . . . . . . . 62 Uninstalling from UNIX systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Uninstalling from UNIX systems (headless uninstall) . . . . . . . . . . . . 63 Appendix A References Network Advisor packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Scalability limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Edition feature support. . . . . . . . . . .
vi Brocade Network Advisor SAN Installation and Migration Guide 53-1003374-01
About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii • Notice to the reader . . . . . . . . . . . .
Supported hardware and software In those instances in which procedures or parts of procedures documented here apply to some devices but not to others, this guide identifies exactly which devices are supported and which are not. Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc. for Network Advisor 12.3.X, documenting all possible configurations and scenarios is beyond the scope of this document.
TABLE 1 Fabric OS-supported hardware (Continued) Device name Terminology used in documentation Firmware level required Brocade M6505 embedded switch 24-port, 16 Gbps embedded switch Fabric OS v7.2.0 or later Brocade 6510 switch 48-port, 16 Gbps switch Fabric OS v7.0.0 or later Brocade 6520 switch 96-port, 16 Gbps switch Fabric OS v7.1.0 or later Brocade 6547 embedded switch 48-port, 16 Gbps embedded switch Fabric OS v7.2.
TABLE 1 Fabric OS-supported hardware (Continued) Device name Terminology used in documentation Firmware level required Brocade DCX 1, 2 with FR4-18i Blades 8-slot Backbone Chassis with 4 Gbps Router, Extension blade Fabric OS v6.0.0 or later Brocade DCX 1, 2 with FC10-6 Blades 8-slot Backbone Chassis with FC 10 - 6 ISL Blade Fabric OS v6.2.0 or later Brocade DCX 1, 2 with FS8-18 Blades 8-slot Backbone Chassis with Encryption Blade Fabric OS v6.1.
TABLE 1 Fabric OS-supported hardware (Continued) Device name Terminology used in documentation Firmware level required Brocade DCX 8510-81, 2 with FC16-64 Blades 16 Gbps 8-slot Backbone Chassis with 16 Gbps 64-port blades Fabric OS v7.3.0 or later FA4-18 Application Platform Blade Application Platform blade FC8-16 Blade FC 8 GB 16-port blade Fabric OS v6.2.0 or later FC 8 GB 32-port blade Fabric OS v6.2.0 or later FC8-32 Blade FC8-32E Blade 3 FC 8 GB 32-port blade Fabric OS v7.0.
Document conventions This section describes text formatting conventions and important notice formats used in this document.
Notice to the reader This document may contain references to the trademarks of the following corporations. These trademarks are the properties of their respective companies and corporations. These references are made for informational purposes only. Corporation Referenced trademarks and products Linus Torvalds Linux Microsoft Corporation Windows, Windows NT, Internet Explorer Netscape Communications Corporation Netscape Red Hat, Inc.
Getting technical help Contact your switch support supplier for hardware, firmware, and software support, including product repairs and part ordering. To expedite your call, have the following information available: 1. Management Application Serial Number To obtain the Management application serial number, select Help > License. The License dialog box displays. 2.
4. World Wide Name (WWN) Use the licenseIdShow command to display the WWN of the chassis. If you cannot use the licenseIdShow command because the switch is inoperable, you can get the WWN from the same place as the serial number, except for the Brocade DCX. For the Brocade DCX, DCX-4S, and DCX 8510-8, access the numbers on the WWN cards by removing the Brocade logo plate at the top of the nonport side of the chassis.
xvi Brocade Network Advisor SAN Installation and Migration Guide 53-1003374-01
Chapter 1 Installation In this chapter • System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 • Downloading the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 • Pre-installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 • Installing the application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 • Headless installation. .
1 System requirements Server and client operating system requirements Table 2 summarizes the required operating system (OS) for servers and the packages supported by each OS version. NOTE It is recommended that you run Network Advisor on a dedicated machine to avoid conflicts with other applications that use the same resources and ports (such as SNMP, web server, and so on). NOTE Enterprise edition and Professional Plus edition are not supported on 32-bit operating systems.
System requirements TABLE 2 Server operating system requirements (Continued) Operating system Version Linux® Guest VMs - 1. 1 Guest OS version Supported packages RedHat Enterprise 6.1 Advanced (x86 32-bit) RedHat Enterprise 6.2 Advanced (x86 32-bit) RedHat Enterprise 6.3 Advanced (x86 32-bit) RedHat Enterprise 6.4 Advanced (x86 32-bit) RedHat Enterprise 6.5 Advanced (x86 32-bit) RedHat Enterprise 7.0 Advanced (x86 32-bit) SuSE Enterprise Server 11.3 (x86 32-bit) Oracle Enterprise 6.
1 System requirements Table 3 summarizes the required OS for clients. Network Advisor clients are supported on 32-bit and 64-bit Windows and Linux systems. NOTE If you are managing more than 9000 SAN ports, the client is not supported on 32-bit systems. TABLE 3 4 Client operating system requirements Operating system Version Windows® - Guest OS version 7 Enterprise (x86 32-bit) 8 Enterprise (x86 32-bit) 8.
System requirements TABLE 3 Client operating system requirements Operating system Version Linux® - Guest VMs 1 - Guest OS version RedHat Enterprise 6.1 Advanced (x86 32-bit) RedHat Enterprise 6.2 Advanced (x86 32-bit) RedHat Enterprise 6.3 Advanced (x86 32-bit) RedHat Enterprise 6.4 Advanced (x86 32-bit) RedHat Enterprise 6.5 Advanced (x86 32-bit) RedHat Enterprise 7.0 Advanced (x86 32-bit) SuSE Enterprise Server 11.3 (x86 32-bit) Oracle Enterprise 6.1 (x86 32-bit) Oracle Enterprise 6.
1 System requirements Memory, host, and disk space requirements Memory requirements are only applicable when there are no other applications running on the Network Advisor server. Paging space should be equal to or exceed the physical memory size. NOTE To manage more than 9000 SAN ports, you must have a 16 core processor. NOTE To efficiently manage more than 9000 SAN ports, it is recommended to allocate a minimum of 2 GB client memory and 6 GB server memory.
System requirements 1 Table 5 summarizes the minimum system requirements for server (plus 1 client) installation.
1 System requirements Browser requirements The launch of Network Advisor and the launch of Element Manager (Web Tools) from the application are supported from the following browsers with a Java plug-in: • Browsers - Windows Internet Explorer 11.0.9 on Windows - Firefox 24 and later on Windows or Linux - Google Chrome 33 on Windows • Java Plug-ins — For the current supported JRE version for Network Advisor and Web Tools, refer to the Release Notes. NOTE For higher performance, use a 64-bit JRE.
Downloading the software 1 Downloading the software You can download the software and documentation from the MyBrocade website. 1. Go to the MyBrocade website. http://my.brocade.com/ 2. Enter your user ID and password. If you do not already have a MyBrocade account, you can create one. 3. Select MyBrocade from the Take me to list, if necessary. 4. Click LOG IN. 5. Click downloads on the main page. 6. Select Management Software from the Download by list. 7.
1 Pre-installation requirements Pre-installation requirements Before you install Network Advisor, make sure you meet the following requirements. • Make sure all system requirements have been met prior to installation. For specific system requirements, refer to “System requirements” on page 1. If you are running Professional Plus or Enterprise edition on a 32-bit machine, you must migrate to a 64-bit machine within your current release, then you can migrate to Network Advisor 12.3.
Installing the application 1 Installing the application Before you install the application, make sure your system meets the minimum pre-installation requirements (refer to “Pre-installation requirements” on page 10). If you are migrating data, refer to “Data Migration” on page 43. NOTE SAN with SMI Agent + IP is not supported on 32-bit Windows systems. For more information, refer to “Pre-migration requirements” on page 47.
1 Installing the application 6. Make sure the Launch Configuration check box is selected (default) on the Installation Complete screen, and click Done. NOTE If a minimum of 10 GB space is not available on your server during installation, a warning message displays and installation fails. If the localhost is not mapped to the loopback address, an error message displays.
Headless installation 1 3. Save and close the file. To configure the application, refer to one of the following sections: • If this is a fresh installation, refer to “Network Advisor Configuration” on page 17. • If you are upgrading from a previous version and need to migrate data, refer to “Data Migration” on page 43. Headless installation Headless installation, also known as silent mode installation, is fully supported on all platforms.
1 Headless installation Performing a headless installation on Windows and UNIX systems To perform a headless installation through the CLI, download the software (refer to “Downloading the software” on page 9). • For Windows systems, complete the following steps: 1. Open a Command Prompt and execute this command: install.exe -i silent -DHEADLESS_CONFIG_MODE="false” 2. From the Install_Home/bin directory, execute this command: configwizard.
Client-only installation 1 Collecting supportsave on Windows and Linux To collect server supportsave, run the script file located at: \bin\commandsupportsave Once the script file is triggered, the server supportsave is collected at the following location: \support Client-only installation You can install a client-only application on a machine other than the server (without using a web browser) by creating a client bundle on the server, and then copying and installing that client on a
1 Client-only installation 4. Enter the IP address of the Network Advisor server in the Network Address list. NOTE The server must be the exact same version, edition, starting port number, and network size as the client. NOTE You can remove a server from the Network Address list by selecting the IP address and clicking Delete. 5. Enter your user name and password. The defaults are Administrator and password, respectively.
Chapter 2 Network Advisor Configuration In this chapter • Configuring Network Advisor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Accessing the Network Advisor interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . • Syslog troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Installing the ODBC driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Smart Card driver installation.
2 Configuring Network Advisor 3. Select one of the following options on the Package screen and click Next. • SAN with SMI Agent • SMI Agent Only (Go to step 8.) NOTE SMI Agent is not supported in a Professional edition configuration. NOTE If you choose to install only the SMI Agent, the configuration defaults to the SAN Enterprise package. When you open the Network Advisor client, a License dialog displays, where you must enter a SAN Enterprise license key to use the client.
2 Configuring Network Advisor 6. Complete the following steps on the FTP/SCP/SFTP Server screen. a. Choose one of the following options: • Select Built-in FTP/SCP/SFTP Server (default) to configure an internal FTP/SCP/SFTP server and select one of the following options: - Select Built-in FTP Server to configure an internal FTP server This is the default option. The internal FTP server uses a default account and port 21. You can configure your own account from the Options dialog box.
2 Configuring Network Advisor 8. Complete the following steps on the Server IP Configuration screen.
2 Configuring Network Advisor b. Select an address from the Switch - Server IP Configuration Preferred Address list. • Select Any from the Switch - Server IP Configuration Preferred Address list to enable switch and server communication with one of the reachable IP address present in the server. By default, Any option is selected. or • Select an IP address from the Switch - Server IP Configuration Preferred Address list. The preferred IP address is used for switch and server communication.
2 Configuring Network Advisor e. Enter a port number in the Syslog Port Number 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 29. f. Enter a port number in the SNMP Port Number field (default is 162). g. Enter a port number in the TFTP Port Number field (default is 69). h.
Configuring Network Advisor 2 12. Enable feature usage data transfer from the application by selecting the Yes, I want to participate option. If you do not want to participate in feature usage data transfer, make sure the No, Thank You option is selected. You can stop participating at any time. To view an example of the usage data, click View Example Data. To stop participating in feature usage data transfer after configuration, refer to “Product improvement” on page 39. 13.
2 Accessing the Network Advisor interfaces Accessing the Network Advisor interfaces Use the following procedures to access Network Advisor from the server and client as well as to access the Server Management Console and the SMI Agent Configuration Tool. Logging into a server You must log into a server to monitor your network. NOTE You must have an established user account on the server to log in. 1. Double-click the desktop icon or open the application from the Start menu.
2 Accessing the Network Advisor interfaces Launching a remote client The remote client link in the Start menu does not automatically upgrade when you upgrade the Management application. You must clear the previous version from the Java cache. To clear the previous version, refer to “Clearing previous versions of the remote client” on page 26. The remote client requires Oracle JRE. For the current supported JRE version for Network Advisor, refer to the Release Notes.
2 Accessing the Network Advisor interfaces 5. Enter your user name and password. The defaults are Administrator and password, respectively. NOTE Do not enter Domain\User_Name in the User ID field for LDAP server authentication. 6. Select or clear the Save password check box to choose whether you want the application to remember your password the next time you log in. 7. Click Login. 8. Click OK on the Login Banner dialog box. The Network Advisor application displays.
Accessing the Network Advisor interfaces 2 Launching the SMC on Linux NOTE The Server Management Console is a graphical user interface and should be launched from the XConsole on Linux systems. Double-click the SMC icon on your desktop. OR 1. On the Network Advisor server, go to the following directory: Install_Directory/bin 2. Type the following at the command line: ./smc OR sh smc Launching the SMIA Configuration Tool 1. Launch the Server Management Console from the Start menu. 2.
2 Accessing the Network Advisor interfaces Launching the SMIA Configuration Tool remote client The remote client link in the Start menu does not automatically upgrade when you upgrade the Management application. You must clear the previous version from the Java cache. To clear the previous version, refer to “Clearing previous versions of the remote client” on page 26. The remote client requires Oracle JRE. For the current supported JRE version for Network Advisor, refer to the Release Notes.
Syslog troubleshooting 2 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. Finding the process 1. Open a command window. 2. Choose one of the following options: • On Linux systems, type netstat –nap | grep 514 and press Enter. The process running on port 514 displays.
2 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.
Installing the ODBC driver 2 10. Enter the IP address or host name of the Network Advisor server in the Server field. 11. Enter the database server port number in the Port Number field. 12. Enter the database user name in the User Name field. 13. Enter the password in the Password field. 14. 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. 15. Click OK on the Connection Test dialog box. 16. Click Save. 17.
2 Installing the ODBC driver Adding the datasource on Linux systems Before you edit the INI files, install Network Advisor (refer to “Installation” on page 1) and make sure the PostgreSQL database is up and running. NOTE For RedHat and Oracle Enterprise systems, the odbc.ini and odbcinst.ini files are located in /etc. For SUSE systems, the odbc.ini and odbcinst.ini files are located in /etc/unixODBC. 1. Open the odbc.
2 Installing the ODBC driver 5. On the Set up user authentication screen, complete the following steps. a. Enter the database user name in the User name field. b. Select the Password required check box. c. Click Test Connection to test the connection. The Authentication Password dialog box displays. d. Enter the database password in the Password field and click OK. e. Click OK on the Connection Test dialog box.
2 Smart Card driver installation Smart Card driver installation Windows operating systems do not require smart card drivers to be installed separately; the driver is bundled with the operating system. However, you must install a smart card driver for the Linux operating systems. You must install both the special USB Chip/Smart Card Interface Device (USB CCID) and the PC/SC IFD driver. You can download the source code and compile it from one of the following websites: • USB CCID (ccid-1.3.7.tar.
Smart Card driver installation 2 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. Otherwise, use the name of the new directory in place of /opt. S.u.s.e> ln –s /opt/pcsc/pcscctl /etc/init.d/pcscd S.u.s.e> chkconfig --add pcscd or redhat> ln –s /opt/pcsc/pcscctl /etc/init.
2 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 34. 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.
2 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.
2 Configuring an explicit server IP address Configuring an explicit server IP address If you selected a specific IP address from the Server IP Configuration screen during installation and the selected IP address changes, you will not be able to connect to the server. To connect to the new IP address, you must manually update the IP address information. To change the IP address, complete the following steps. 1.
Product improvement 2 Product improvement To improve its products, Brocade is collecting usage statistics from the field. If you agree to participate in the program, the Network Advisor server will transmit data back to the secure Brocade web server (HTTPS). The Brocade web server is hosted in a Brocade network.
2 Product improvement Disabling product improvement data transfer You can disable feature usage data transfer from the Options dialog box once your system is up and running. To disable feature usage data transfer from the application, complete the following steps. 1. Select Server > Options. The Options dialog box displays. 2. Select Product Improvement in the Category list. 3. Select the No, thank you option. 4. Click OK to save your selection and close the Options dialog box.
2 Configuring remote client access to the database 11. When the file is successfully created, the client changes the state of the data transfer to “Uploading” and transmits the data. The client transmits the data securely to the Brocade web server using the Apache HTTP Components third-party library. The client communicates with the Brocade web server using an authorization token. 12.
2 42 Configuring remote client access to the database Brocade Network Advisor SAN Installation and Migration Guide 53-1003374-01
Chapter 3 Data Migration In this chapter • Upgrading the license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Supported migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Pre-migration requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Migrating data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Cross flavor migration . . . .
3 Supported migration paths 6. Enter your user name and password. The defaults are Administrator and password, respectively. If you migrated from a previous release, your user name and password do not change. NOTE Do not enter Domain\User_Name in the User ID field for LDAP server authentication. 7. Select or clear the Save password check box to choose whether you want the application to remember your password the next time you log in. 8. Click Login. 9. Click OK on the Network Advisor Login Banner.
3 Supported migration paths TABLE 10 Pre-12.0.0 release migration path Network Advisor 12.3.X Network Advisor 11.0.X Network Advisor 11.0.X > Network Advisor 11.1.X > Network Advisor 12.0.X > Network Advisor 12.3.X Network Advisor 11.1.X Network Advisor 11.1.X > Network Advisor 12.0.X > Network Advisor 12.3.X Network Advisor 11.2.X Network Advisor 11.2.X > Network Advisor 12.0.X > Network Advisor 12.3.X Network Advisor 11.3.x Network Advisor 11.3.X > Network Advisor 12.0.
3 Supported migration paths TABLE 11 Network Advisor version migration paths Current version Professional version Trial Version Licensed Version Enterprise Professional Plus Enterprise Network Advisor 12.3.X Enterprise Trial No Yes1 No Yes1 Network Advisor 12.3.X Enterprise Licensed No No No Yes1 1. Local path migration is only supported when you partially uninstall the current version.
3 Pre-migration requirements Pre-migration requirements Before you install Network Advisor, make sure you meet the following pre-migration requirements. • Make sure all system requirements have been met prior to installation. For specific system requirements, refer to “System requirements” on page 1. • Check for and install the latest Java patches for your operating system. For the current supported JRE version for Network Advisor and Web Tools, refer to the Release Notes.
3 Pre-migration requirements 4. Select SMC > Restore tab to restore the backup taken on the 32-bit Windows server. 5. Install Network Advisor 12.3.1 on the 64-bit Windows server. Perform seamless migration to Network Advisor 12.3.1 (refer to “Migrating data” on page 51). If you are migrating from Network Advisor 12.0.X, 12.1.X, 12.2.X, or 12.3.X on a 32-bit Linux server to Network Advisor 12.3.1 on a 64-bit pure Linux server, complete the following steps. 1. Take server backup for 12.0.X, 12.1.X, 12.2.
3 Pre-migration requirements 4. Select SMC > Restore tab to restore the backup taken on the 32-bit Linux server. 5. Install Network Advisor 12.3.1 on the 64-bit Linux server (32-bit compatible). Perform seamless migration to Network Advisor 12.3.1 (refer to “Migrating data” on page 51). If you are migrating from a pre-12.0.0 release on one server to another server, complete the following steps.
3 Pre-migration requirements If you are migrating from Linux server that is no longer supported to a supported Linux server, complete the following steps. For a list of supported operating system servers, refer to Table 2 on page 2. NOTE If you are migrating from a pre-11.3.0 release, you must first migrate to Network Advisor 11.3.0 on your current server (refer to Table 9 on page 44 for the release migration path). 1. Install Network Advisor 12.0.
Migrating data 3 • 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). You may also need to consider a firewall that might block the display to the X Server which listens by default on TCP port 6000 on the remote host.
3 Migrating data • If data is not detected, the Copy Data and Settings from previous releases screen displays. Complete the following steps: a. Select Yes, from this machine or on network and click Browse to browse to the installation directory. b. Click Next on the Copy Data and Settings from previous releases screen. Continue with step 3.
Migrating data 3 6. Select one of the following options on the Installation Type screen and click Next. NOTE The DCX and DCX 8510-8 Backbone chassis require Enterprise edition. • Network Advisor - Licensed version Continue with step 7. Requires you to enter a license key during configuration to enable features and configuration. • Network Advisor - 120 days Trial Go to step 8. Enables you to manage SAN networks from a single interface for 120 days.
3 Migrating data b. Click Next. If port 21 or 22 is busy, a message displays. Click OK to close the message and continue. Once the Management application is configured make sure port 21 or 22 is free and restart the Server to start the FTP/SCP/SFTP service. NOTE If you use an FTP/SCP/SFTP Server which is not configured on the same machine as the Management application, the Firmware Repository feature will not be available. 9. Complete the following steps on the Server IP Configuration screen.
3 Migrating data 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. 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.
3 Migrating data d. Enter a port number in the Starting Port # field (default is 24600). NOTE For Professional software, the server requires 11 consecutive free ports beginning with the starting port number. NOTE For Trial and Licensed software, the server requires 11 consecutive free ports beginning with the starting port number. e. Enter a port number in the Syslog Port # field (default is 514).
Migrating data 3 13. Enable feature usage data transfer from the application by selecting the Yes, I want to participate option. You can stop participating at any time. To view an example of the usage data, click View Example Data. To stop participating in feature usage data transfer after configuration, refer to “Product improvement” on page 39. 14. Verify your configuration information on the Server Configuration Summary screen and click Next. 15. Complete the following steps on the Start Server screen.
3 Cross flavor migration Cross flavor migration To migrate from Brocade Network Advisor 12.0.X to a non-Brocade Network Advisor 12.3.X, complete the following steps. 1. Install Brocade Network Advisor 12.0.X (refer to “Installing the application” on page 11). 2. Install non-Brocade Network Advisor 12.3.X (refer to “Installing the application” on page 11). 3. Migrate the supported (partial or full) data from Brocade Network Advisor 12.0.
Migration rollback 3 For Linux Install_Home>bin>sh dbsvc start Install_Home>bin>sh service dcmsvc start For Linux, if SLP is enabled Install_Home>bin>sh slpsvc start For Linux, if CIMOM is enabled Install_Home>bin>sh service cimomsvc start Brocade Network Advisor SAN Installation and Migration Guide 53-1003374-01 59
3 60 Migration rollback Brocade Network Advisor SAN Installation and Migration Guide 53-1003374-01
Chapter 4 Uninstallation In this chapter • Uninstalling from Windows systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Uninstalling from Windows systems (headless uninstall). . . . . . . . . . . . . . . • Uninstalling from UNIX systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Uninstalling from UNIX systems (headless uninstall) . . . . . . . . . . . . . . . . . .
4 Uninstalling from Windows systems (headless uninstall) Uninstalling from Windows 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 Windows server. 1. Open a command prompt. 2.
4 Uninstalling from UNIX systems (headless uninstall) 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_Advisor12_3_1. 2.
4 64 Uninstalling from UNIX systems (headless uninstall) Brocade Network Advisor SAN Installation and Migration Guide 53-1003374-01
Appendix A References In this appendix • Network Advisor packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Scalability limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Edition feature support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Management server and client ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A Scalability limits Scalability limits Table 14 summarizes the scalability limits supported for Network Advisor by edition.
A Edition feature support Edition feature support Table 15 details whether the features are supported in the Professional Plus or Enterprise versions, or only through the Element Manager of the device.
A Edition feature support TABLE 15 SAN features supported (Continued) Feature Professional Professional Plus Enterprise Layer 2 FC support Yes Yes Yes Encryption configuration and monitoring Yes Yes Yes Access Gateway – Cisco interop support Yes Yes Yes Device decommissioning Yes Yes Yes End device connectivity Collection Views Yes Yes Yes Fabric binding No Yes Yes Hardware Element Manager Element Manager Element Manager Ports Element Manager Element Manager Element Ma
A Edition feature support TABLE 15 SAN features supported (Continued) Feature Professional Professional Plus Cascaded FICON configuration wizard No No Yes Cascaded FICON Fabric merge wizard No No Yes Element Manager Element Manager Yes Firmware download Yes Yes Yes Capture SupportSave Yes Yes Yes Flow Vision No Yes Yes Frame monitor No Yes Yes HBA management Yes Yes Yes VM management Yes Yes Yes Driver/DIOS management No Yes Yes Fabric assigned WWN No Yes Yes
A Edition feature support TABLE 15 SAN features supported (Continued) Feature Professional Professional Plus Enterprise Real Time Performance collection, display, and reports Yes Yes Yes Historical Performance collection, display, and reports No Yes Yes Thresholds No Yes Yes Top talkers - Supported on SAN switches and Access Gateway No Yes Yes Marching ants No Yes Yes Data aging No Yes Yes End-to-End monitors No Yes Yes Yes Yes Yes Element Manager Element Manager Ele
A Edition feature support TABLE 15 SAN features supported (Continued) Feature Professional Professional Plus Enterprise SMI Agent Server Profile Fabric Profile Indication Sub Profile Zone Control Sub Profile Enhanced Zoning and Enhanced Zoning Control Sub Profile FDMI (Fabric Device Management Interface) Sub Profile Fabrics Virtual Fabrics Sub Profile Topology View Sub Profile FC HBA (Fibre Channel Host Bus Adapter) Profile Fan, Power Supply, and Sensor Profiles Inter Fabric Routing (FCR) Profile Tr
A Edition feature support TABLE 15 SAN features supported (Continued) Feature Professional Professional Plus Enterprise Discovery Yes Yes Yes Configuration No Yes Yes VLAN management Yes Yes Yes VM Plugin Support No Yes Yes Web Element Manager Yes Yes Yes Member selection Yes Yes Yes Zone editing Yes Yes Yes Live fabric library scope Yes Yes Yes QoS support Yes Yes Yes Zone alias support Yes Yes Yes Delete Zone database No Yes Yes Impact analysis Yes Yes
Management server and client ports A Management server and client ports The Management application has two parts: the Server and the Client. The Server is installed on one machine and stores device-related information; it does not have a user interface. To view information through a user interface, you must log in to the Server through a Client. The Server and Clients may reside on the same machine, or on separate machines.
A Management server and client ports TABLE 16 Port usage and firewall requirements (Continued) Port Number Ports Transport Description Communication Path Open in Firewall 802 Management application HTTP server TCP Non-SSL HTTP/1.1 connector port if you use secure client-server communication.
Management server and client ports TABLE 16 A Port usage and firewall requirements (Continued) Port Number Ports Transport Description Communication Path Open in Firewall 18122 RADIUS Authentication Server Port UDP RADIUS server port for authentication if you use RADIUS as an external authentication Server–RADIUS Server Yes 18132 RADIUS Accounting Server Port UDP RADIUS server port for accounting if you use RADIUS as an external authentication Server–RADIUS Server Yes 5432 Database por
A Management server and client ports TABLE 16 Port usage and firewall requirements (Continued) Port Number Ports Transport Description Communication Path Open in Firewall 34568 HCM Agent discovery port TCP Used for HBA management via JSON Server - Managed Host Yes 555561 Launch in Context (LIC) client hand shaking port TCP Client port used to check if a Management application client opened using LIC is running on the same host Client No NOTE: If this port is in use, the application uses
