53-1003580-01 15 December 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 . . . . . . . . . . . . . . . . . . . . 23 Logging into a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Launching a remote client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Clearing previous versions of the remote client . . . . . . . . . . . . 25 Launching the SMC on Windows . . . . .
Chapter 4 Uninstallation Uninstalling from Windows systems . . . . . . . . . . . . . . . . . . . . . . . . . 53 Uninstalling from Windows systems (headless uninstall) . . . . . . . . 54 Uninstalling from UNIX systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Uninstalling from UNIX systems (headless uninstall) . . . . . . . . . . . . 55 Appendix A References Network Advisor packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Scalability limits . . . . . . . . .
vi Brocade Network Advisor SAN Installation and Migration Guide 53-1003580-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.1.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 6505 switch 24-port, 16 Gbps Edge switch Fabric OS v7.0.1 or later 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.
TABLE 1 Fabric OS-supported hardware (Continued) Device name Terminology used in documentation Firmware level required Brocade DCX 1, 2 with FS8-18 Blades 8-slot Backbone Chassis with Encryption Blade Fabric OS v6.1.1_enc or later 8-slot Backbone Chassis with 8 Gbps 12-FC port, 10 GbE ports, 2-10 GbE ports blade Fabric OS v6.3.1_CEE Brocade DCX 1, 2 with FCoE10-24 Blades 8-slot Backbone Chassis with 10 Gbps 24-port FCoE blade Fabric OS v6.3.
TABLE 1 Fabric OS-supported hardware (Continued) Device name Terminology used in documentation FX8-24 Blade 1, 2 8 Gbps Extension Blade Firmware level required 1 Professional can discover, but not manage this device. Use the device’s Element Manager, which can be launched from the Connectivity Map, to manage the device. This device cannot be used as a Seed switch. 2 Professional Plus Trial and Licensed version can discover, but not manage, this device.
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, 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-1003580-01
Chapter 1 Installation In this chapter • System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 • Downloading the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 • Pre-installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 • Installing the application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 • 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 1 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 Client operating system requirements Operating system Version Windows® - Guest OS version 7 Enterprise (x86 32-bit) 8 Enterprise (x86 32-bit) 8.
1 System requirements TABLE 3 Client operating system requirements Operating system Version Linux® - Guest VMs - 4 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.
System requirements 1 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 It is recommended that you use FC storage. NOTE To manage more than 9000 SAN ports, you must have a 16 core processor.
1 System requirements Table 6 summarizes the recommended system requirements for server (plus 1 client) installation.
Downloading the software 1 • 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. NOTE If the minimum system requirement is not met, you will be blocked from the configuration and an error message will be displayed. For the website listing patch information, go to http://www.oracle.com/technetwork/java/javase/downloads/index.html.
1 Pre-installation requirements 8. Select the highest version number for the latest GA code. For example, click Brocade Network Advisor 12.3.x, then click Brocade Network Advisor 12.3.3 Brocade GA. To download the documentation, click Brocade Network Advisor 12.3.3 Manuals and then select the manual you want to download. 9. Select one of the following links to download the software: • Network Advisor 12.3.3 GA for Windows • Network Advisor 12.3.
Pre-installation requirements 1 Additional pre-installation requirements for UNIX systems • 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).
1 Installing the application 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 8). If you are migrating data, refer to “Data Migration” on page 39. NOTE is not supported on 32-bit Windows systems. For more information, refer to “Pre-migration requirements” on page 42.
Installing the application 1 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.
1 Headless installation 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 39. Headless installation Headless installation, also known as silent mode installation, is fully supported on all platforms.
Headless installation 1 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 7). • 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.
1 Client-only installation 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
Client-only installation 1 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.
1 16 Client-only installation Brocade Network Advisor SAN Installation and Migration Guide 53-1003580-01
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 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 9. Complete the following steps on the Server Configuration screen (Figure 1). FIGURE 1 Server Configuration screen a. Enter a port number in the Web Server Port # (HTTPS) field (default is 443). b. Enable HTTP redirection to HTTPS by selecting the Redirect HTTP Requests to HTTPS check box. When you enable HTTP redirection, the server uses port 80 to redirect HTTP requests to HTTPS.
2 Configuring Network Advisor 10. (SAN with SMI Agent) Complete the following steps on the 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.
Accessing the Network Advisor interfaces 2 14. 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. 15. Click Login. 16. Click OK on the Network Advisor Login Banner. 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.
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 25. The remote client requires Oracle JRE. For the current supported JRE version for Network Advisor, refer to the Release Notes.
Accessing the Network Advisor interfaces 2 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.
2 Accessing the Network Advisor interfaces 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. Click Configure SMI Agent. The SMIA Configuration Tool Log In dialog box displays. 3. Enter your user name and password. The defaults are Administrator and password, respectively. 4. Click Login.
Configuring performance collection for SMI-A only 2 5. 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. 6. Click Login. The SMIA Configuration Tool displays. Configuring performance collection for SMI-A only For SMI-A only installation, you must enable or disable performance statistics collection using a script. • On Windows systems, complete the following steps. a.
2 Installing the ODBC driver Stopping the process Choose one of the following options: • On Linux systems, type kill -9 “ProcessID”, where ProcessID is the ID of the process you want to stop, and press Enter. For example, kill -9 “27397”. • On Windows systems, type taskkill /F /PID “ProcessID”, where ProcessID is the ID of the process you want to stop, and press Enter. For example, taskkill /F /PID "3328". OR 1. Select Ctrl + Shift + Esc to open Windows Task Manager. 2. Click the Processes tab. 3.
Installing the ODBC driver 2 Adding the data source on Windows systems 1. To add the data source, complete the following steps. Choose one of the following options: • (32-bit OS) Select Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC). • (64-bit OS) (Windows only) Select Start > Run, type %windir%\SysWOW64\odbcad32.exe, and press Enter. The ODBC Data Source Administrator dialog box displays. 2. Click the System DSN tab. 3. Click Add.
2 Installing the ODBC driver Installing the ODBC driver on Linux systems 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. To install the ODBC driver, complete the following steps. 1. Execute the following command in the terminal: > su >chmod 777 edb_psqlodbc.bin > ./edb_psqlodbc.
2 Installing the ODBC driver 3. Open the odbcinst.ini file in a text editor and make sure that the driver path information is correct. After you install the PostgreSQL ODBC driver, the odbcinst.ini should automatically update the driver path. If the driver path is not updated, add the following: [psqlODBC] Description=PostgreSQL ODBC driver Driver=/opt/PostgreSQL/psqlODBC/lib/psqlodbcw.so 4. Save and close the odbcinst.ini file.
2 Smart Card driver installation e. Click OK on the Connection Test dialog box. For 32-bit Linux systems, if an error message (file not found while testing the connection) displays, copy the lib files from the /lib/* directory to the /usr/lib/ directory. For 64-bit Linux systems, if an error message (cannot open library) displays, complete the following steps: 1. Execute the following command: export LD_LIBRARY_PATH=/opt/PostgreSQL/8.
2 Smart Card driver installation Installing the Smart Card driver on the local client 1. Verify that the /opt directory exists. If the /opt directory does not exist, create an /opt directory. If you want to install the driver in a different directory, create that directory. Otherwise, skip this step. > su > mkdir /opt 2. Copy the appropriate pscs file for your platform (Linux) from the DVD and rename the file as pcsc-lite-1.4.101-linux-x86.tar.gz file. 3. Log in as the superuser to untar the pcsc-lite-1.
2 Smart Card driver installation 6. Start the pcscd daemon or stop the pcscd daemon. To start pcscd, type: > /opt/pcsc/pcscctl start To stop pcscd, type: > /opt/pcsc/pcscctl stop 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 33. 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.
Smart Card driver installation 2 Detecting and correcting a default Linux Smart Card driver This section applies to the Linux system only. Some Linux systems may provide a default Smart Card driver and have their own setup to activate it. In this case, you must use the driver provided with Network Advisor. Otherwise, there could be an incompatibility issue between the driver and the native library that could cause a driver detection failure.
2 Configuring an explicit server IP address 5. Remove the existing pcscd start priority file by deleting the file as SNNpcscd, where NN is the start priority. For example, from the preceding step, the file name is S25pcscd. > find /etc/. –name “S25pcscd” –exec rm {} \; -print > sync;sync;sync > reboot After the reboot, the new configuration from the /opt/pcsc/pcscctl file should be under the /etc/rc2.d, /etc/rc3.d, /etc/rc4.d, and /etc/rc5.d directories.
Configuring remote client access to the database 2 5. Complete the following steps on the Server IP Configuration screen. a. Select an address from the Server IP Configuration list. NOTE The host name does not display in the list if it contains invalid characters. 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 the Server IP Configuration list.
2 Configuring remote client access to the database 4. To allow access to a specific IPv4 address, search for the following text and uncomment the second line: # Uncomment below line and provide IPV4 address to allow specific IPv4 remote user #host all all /32 md5 5. To allow access to a specific IPv6 address, search for the following text and uncomment the second line: # Uncomment below line and provide IPV6 address to allow specific IPv6 remote user #host all all /128 md5 6.
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 IBM Network Advisor version migration paths Current version Trial version Licensed Version Professional Plus Enterprise Professional Plus Enterprise Yes1 Yes1 Yes1 Yes1 IBM Network Advisor 12.0.X/12.1.X Professional Plus Licensed No No Yes1 Yes1 IBM Network Advisor 12.0.X/12.1.X Enterprise Trial No Yes1 No Yes1 IBM Network Advisor 12.0.X/12.1.X Enterprise Licensed No No No Yes1 Yes1 Yes1 Yes1 Yes1 IBM Network Advisor 12.3.
3 Pre-migration requirements Pre-migration requirements Before you install IBM 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 3. Install the same version (12.0.X, 12.1.X, or 12.3.X) on the 64-bit Windows server. 4. Select SMC > Restore tab to restore the backup taken on the 32-bit Windows server. 5. Install IBM Network Advisor 12.3.3 on the 64-bit Windows server. Perform seamless migration to IBM Network Advisor 12.3.3 (refer to “Migrating data” on page 46). If you are migrating from IBM Network Advisor 12.0.X, 12.1.X, or 12.3.X on a 32-bit Linux server to IBM Network Advisor 12.3.
3 Pre-migration requirements 3. Install IBM Network Advisor 12.0.X, 12.1.X, or 12.3.X on the 64-bit Linux server (32-bit compatible). 4. Select SMC > Restore tab to restore the backup taken on the 32-bit Linux server. 5. Install IBM Network Advisor 12.3.3 on the 64-bit Linux server (32-bit compatible). Perform seamless migration to IBM Network Advisor 12.3.3 (refer to “Migrating data” on page 46). 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.1.0 release, you must first migrate to IBM Network Advisor 11.1.0 on your current server (refer to Table 11 on page 45 for the release migration path). 1. Install IBM Network Advisor 12.0.
3 Migrating data • 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 b. Click Next on the Copy Data and Settings from previous releases screen. Continue with step 3. NOTE If you are migrating from a 32-bit server, you will need to browse to the shared directory of the 32-bit server on the Copy Data and Settings from previous releases screen. NOTE If you are migrating to the same install location (as the previous version), you will need to browse to the renamed directory on the Copy Data and Settings from previous releases screen. 3.
3 Migrating data 8. Complete the following steps on the FTP/SCP/SFTP Server screen. The default selection reflects the previous edition configuration. a. Choose one of the following options: • Select Built-in FTP/SCP/SFTP Server 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 The internal FTP server uses a default account and port 21. You can configure your own account from the Options dialog box.
3 Migrating data a. Select an address from the Server IP Configuration list. NOTE For SMI Agent, if the Server IP Configuration list contains a duplicate IP address or is empty, an error message displays and the configuration wizard closes. 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.
3 Migrating data d. Enter a port number in the Starting Port # field (default is 24600). 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). NOTE If the default syslog port number is already in use, you will not receive any syslog messages from the device.
Cross flavor migration 3 14. Complete the following steps on the Start Server screen. a. (Trial and Licensed only) Select the Start SMI Agent check box, if necessary. b. (Trial and Licensed only) 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 are started, the Log In dialog box displays.
3 Migration rollback Migration rollback NOTE Migration rollback is not supported if you are performing headless migration. Migration rollback is triggered when a failure occurs while migrating to a different version of Network Advisor. After successful rollback, the previous version will be running and the destination version will be uninstalled. The destination version failure logs and the source version supportsave will be zipped and stored at the source BNA_HOME\support folder in the following format.
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_3. 2.
4 56 Uninstalling from UNIX systems (headless uninstall) Brocade Network Advisor SAN Installation and Migration Guide 53-1003580-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 12 summarizes the scalability limits supported for Network Advisor by edition.
A Edition feature support Edition feature support Table 13 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 13 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 13 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 13 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 13 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 13 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 14 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 14 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 14 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
