53-1002699-01 17 December 2012 Brocade Network Advisor Installation and Migration Guide Supporting Network Advisor 12.0.
Copyright © 2006-2012 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 IronWare OS hardware and software support . . . . . . . . . . . . . . . xi Network OS hardware and software support. .
Headless installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Additional pre-installation requirements for UNIX systems (headless installation) . . . . . . . . . . . . . . . . . . . . . 14 Performing a headless installation on Windows and UNIX systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Troubleshooting the Linux headless installation . . . . . . . . . . .
Chapter 4 Uninstallation Uninstalling from Windows systems . . . . . . . . . . . . . . . . . . . . . . . . . 55 Uninstalling from Windows systems (headless uninstall) . . . . . . . . 56 Uninstalling from UNIX systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Uninstalling from UNIX systems (headless uninstall) . . . . . . . . . . . . 57 Appendix A References Network Advisor packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Edition feature support. . . . . . .
vi Network Advisor Installation and Migration Guide 53-1002699-01
About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi • 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.0.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 6510 switch 48-port, 16 Gbps switch Fabric OS v7.0.0 or later Brocade 7500 Extension switch 4 Gbps Router, Extension Switch Fabric OS v5.1.0 or later Brocade 7500E Extension switch 4 Gbps Extension Switch Fabric OS v5.1.0 or later FR4-18i Blade 4 Gbps Router, Extension blades Brocade AP7600 switch 4 Gbps 32-port Switch Fabric OS v6.1.
TABLE 1 Fabric OS-supported hardware (Continued) Device name Terminology used in documentation Firmware level required Brocade DCX-4S with FC8-16, FC8-32, and FC8-48 Blades 4-slot Backbone Chassis with 8 Gbps 16-FC port, 8 Gbps 32-FC port, and 8 Gbps 48-FC port blades Fabric OS v6.2.0 Brocade DCX-4S with FC8-64 Blades 4-slot Backbone Chassis with 8 Gbps 64-FC port blades Fabric OS v6.4.0 Brocade DCX-4S with FR4-18i Blades 4-slot Backbone Chassis with 4 Gbps Router, Extension blade Fabric OS v6.
IronWare OS hardware and software support The following firmware platforms are supported by this release of Network Advisor 12.0.X: • • • • • • BigIron 2.7.02e (sustaining mode) or later FastIron 7.2.0 or later NetIron 5.1.0 or later ServerIron (JetCore) 11.0 or later ServerIron ADX 12.2.0 or later TurboIron 4.2.0 or later For platform-specific firmware requirements, refer to Table 2. Table 2 lists the hardware platforms supported by this release of Network Advisor 12.0.
TABLE 2 IronWare OS-supported hardware (Continued) Device name xii Terminology used in documentation Firmware level required ICX 643048-HPOE switch 48-port Campus LAN HPOE switch FastIron 07.4.00 and later ICX 645024 switch 24-port Campus LAN switch FastIron 07.4.00 and later ICX 645024 Base L3 router 24-port Campus LAN Base L3 router FastIron 07.4.00 and later ICX 645024 Base router 24-port Campus LAN Base router FastIron 07.4.
TABLE 2 IronWare OS-supported hardware (Continued) Device name Terminology used in documentation FastIron Edge X 624 Enterprise LAN Edge switch, 24 10/100/1000 Mbps ports FastIron Edge X 448 Enterprise LAN Edge switch, 48 10/100/1000 Mbps ports FastIron Edge X 648 Enterprise LAN Edge switch, 48 10/100/1000 Mbps ports FastIron Edge X 424HF Enterprise LAN Edge switch, 20 100/1000 Mbps SFP ports FastIron Edge X 624HF Enterprise LAN Edge switch, 20 100/1000 Mbps SFP ports FastIron WS devices Ente
TABLE 2 IronWare OS-supported hardware (Continued) Device name Terminology used in documentation Firmware level required TurboIron Family Data Center switch 4.1.00d or 4.2.00 or later 1. TurboIron 24X (T1-24X-AC) Data Center switch 4.1.00d or 4.2.00 or later Brocade 6650 Switch Data Center switch FastIron 7.5 and later Brocade 6650 Base L3 Router Data Center base L3 router FastIron 7.5 and later Brocade 6650 Router Data Center router FastIron 7.
What’s new in this document The following changes have been made since this document was last released: • Information that was added: - Documented OS cache requriements (refer to “Operating system cache requirements” on page 6) - Documented downloading the software (refer to “Downloading the software” on page 9) - Documented unsupported migration work arounds (refer to “Pre-migration requirements” on page 45).
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.
xx Network Advisor Installation and Migration Guide 53-1002699-01
Chapter 1 Installation In this chapter • System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 • Downloading the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 • Pre-installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 • Installing the application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 • Headless installation. .
1 System requirements Server and Client operating system requirements Table 4 summarizes the required Operating Systems (OS) for servers and the packages supported by each OS version. NOTE Large installations (SAN with SMI Agent or IP only) are only supported on 64-bit Windows® operating systems. NOTE SAN with SMI Agent + IP is not supported on 32-bit Windows operating systems. TABLE 4 Server operating system requirements Operating system Version Windows - Linux® - Guest VMs - 1.
System requirements TABLE 5 1 Client operating system requirements Operating system Version Guest OS version Linux - Supports all client OS versions available for Windows and Linux. Guest VMs RedHat Enterprise 6.1 Advanced Platform (x86 32-bit/64-bit) SuSE Enterprise Server 11 (x86 32-bit) Oracle Enterprise 6.1 (x86 32-bit) VMware® ESX Server i 5.
1 System requirements Table 9 summarizes the minimum host requirements for running Network Advisor SAN with SMI Agent on Windows and Linux systems. TABLE 9 SAN with SMI Agent host requirements Professional Professional Plus Enterprise Small Medium Large LAN Server plus one local client Intel Core2 duo 2 GHz or equivalent Intel Core2 duo 2 GHz or equivalent Intel Core2 duo 2 GHz or equivalent Intel Dual CPU Core2 duo 2.4 GHz or equivalent Intel Dual CPU Core2 duo 2.
System requirements 1 Memory requirements Table 12 through Table 14 summarizes the minimum system memory requirements for running Network Advisor SAN with SMI Agent + IP on Windows and Linux systems. NOTE These requirements are only applicable when no other applications are running on Network Advisor. NOTE Paging space should be equal to or exceed the physical memory size.
1 System requirements Table 15 summarizes the minimum system memory requirements for running Network Advisor SAN with SMI Agent on Windows and Linux systems.
System requirements TABLE 19 1 Linux swap space requirements Installed physical memory (RAM) size Recommended swap size 2 GB 4 GB 3 GB 4 GB 4 GB 4 GB Greater than 4 GB and less than 8 GB Equal to the amount of RAM Greater than or equal to 8 GB and less than 64 GB .5 times the amount of RAM Disk space requirements Table 20 through Table 22 summarizes the minimum disk space requirements for running Network Advisor SAN with SMI Agent + IP on Windows and Linux systems.
1 System requirements Table 23 summarizes the minimum disk space requirements for running Network Advisor SAN with SMI Agent on Windows and Linux systems.
Downloading the software 1 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 under Windows - Firefox under Windows or Linux • Java Plug-ins - Oracle JRE 1.7.0 update 09 for Network Advisor - Oracle JRE 1.7.0 update 09 for Web Tools For the website listing patch information, go to http://www.oracle.
1 Pre-installation requirements 5. Click downloads on the main page. 6. Select Management Software from the Download by list. 7. Click Brocade Network Advisor in the Product Name list. 8. Select the highest version number for the latest GA code. For example, click Brocade Network Advisor 12.0.x, then click Brocade Network Advisor 12.0.0 Brocade GA. To download the documentation, click Brocade Network Advisor 12.0.0 Manuals and then select the manual you want to download. 9.
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 10). If you are migrating data, refer to “Data Migration” on page 41. NOTE SAN with SMI Agent + IP is not supported on 32-bit Windows systems. For more information, refer to “Pre-migration requirements” on page 45.
Installing the application 1 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. If the localhost is not mapped to the loopback address, an error message displays. You must map the loopback address to the localhost (refer to “Mapping the loopback address to the localhost” on page 13) before you configure the application.
1 Headless installation Headless installation Headless installation, also known as silent mode installation, is fully supported on all platforms. Once initiated, the headless installation requires minimal user interaction and runs based on the default values provided. Headless installation performs the actual installation; however, you must use the Configuration wizard in graphical user interface mode to copy data and settings, configure the FTP or SCP server, configure IP, and configure server ports.
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 9). • For Windows systems, open a Command Prompt and execute this command: install.exe -i silent -DUSER_INSTALL_DIR="C:\Program Files\Network Advisor11.X.X" • For UNIX systems, open a UNIX shell and execute this command: install.
1 16 Headless installation Network Advisor Installation and Migration Guide 53-1002699-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 IP SAN with SMI Agent + IP 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.
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 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.
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). NOTE Do not use port 1527 for any of these port numbers. Port 1527 is used internally by the server. 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.
2 Configuring Network Advisor f. Enter a port number in the SNMP Port Number field (default is 162). g. Click Next. If you enter a syslog port number already in use, a message displays. Click No on the message to remain on the Server Configuration screen and edit the syslog port number. Click Yes to close the message. If you enter a port number already in use, a Warning displays next to the associated port number field. Edit that port number and click Next.
Configuring Network Advisor 2 12. (IP Enterprise) Select one of the following options on the IP Network Size screen and click Next: NOTE Port count is equal to the total number of all managed product ports. NOTE If you installed the SAN with SMI Agent + IP package on a 32-bit Windows system, the Large option is disabled for IP network size (Enterprise and Professional Plus). • Small (managing up to 1-20 products) • Medium (managing up to 21-200 products) • Large (managing up to 201-5050 products) 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.
Accessing the Network Advisor interfaces 2 3. Log into another server by entering the IP address to the other server in the Network Address field. NOTE The server must be the exact same version, edition, starting port number, and network size as the client. 4. Remove a server from the Network Address list by selected the IP address and clicking Delete. 5. Enter your user name and password. The defaults are Administrator and password, respectively.
2 Accessing the Network Advisor interfaces 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. Launching the SMIA Configuration Tool remote client The remote client requires Oracle JRE 1.7.0_09. For the website listing patch information, go to http://www.oracle.
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 16. Enter the database user name in the User Name field. 17. Enter the password in the Password field. 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.
2 Installing the ODBC driver Adding the Datasourse 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 32. 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 our products we are 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 40 Configuring remote client access to the database Network Advisor Installation and Migration Guide 53-1002699-01
Chapter 3 Data Migration In this chapter • Upgrading the license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Supported migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Pre-migration requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Migrating data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Upgrading the license TABLE 28 SAN + IP upgrade paths Current software release To software release SAN + IP Professional SAN Professional Plus + IP Trial or Enterprise Licensed version SAN + IP Enterprise Trial or Licensed version SAN Professional Plus + IP Enterprise Trial SAN Professional Plus + IP Enterprise Licensed version SAN + IP Enterprise Trial or Licensed version SAN Professional Plus + IP Enterprise Licensed version SAN + IP Enterprise Licensed version SAN + IP Enterprise Trial SAN
3 Supported migration paths Supported migration paths You cannot migrate directly from Network Advisor 11.0.X to Network Advisor 12.0.0. To migrate from Network Advisor 11.0.X, you must first migrate to Network Advisor 11.1.X, then migrate to Network Advisor 12.0.0. To migrate from Network Advisor 11.0.X to Network Advisor 11.1.X, refer to the Network Advisor Migration Guide for Network Advisor 11.1.X. NOTE Network Advisor 11.1.X includes 11.1.0, 11.1.1, 11.1.2, 11.1.3, 11.1.4, and 11.1.5.
3 Supported migration paths TABLE 30 Network Advisor version migration paths Current version Professional version Trial version Professional Plus Licensed Version Enterprise Professional Plus Enterprise Yes2 Yes2 Yes2 Yes2 Yes2 Network Advisor 12.0.0 Professional Plus trial No Yes2 Yes2 Yes2 Yes2 Network Advisor 12.0.0 Professional Plus Licensed No No No Yes2 Yes2 Network Advisor 12.0.0 Enterprise trial No No Yes No Yes2 Network Advisor 12.0.
3 Pre-migration requirements EFCM and Fabric Manager migration paths You cannot migrate directly from EFCM or Fabric Manager to Network Advisor 12.0.0. To migrate from EFCM or Fabric Manager, you must first migrate to DCFM 10.3.X, then migrate to Network Advisor 11.1.X, then migrate to Network Advisor 12.0.0. For more information about migrating from EFCM or Fabric Manager to DCFM 10.3.X, contact your customer representative.
3 Pre-migration requirements 5. Select the Share this Folder option on the Network Advisor Properties dialog box and click OK. The folder icon changes to the shared folder icon. 6. From the 64-bit server, verify that the 32-bit server shared drive is accessible. 7. Install your current application (pre-12.0.0 release) on the 64-bit server (refer to “Data Migration” on page 41) and migrate your data (“Migrating data” on page 48).
3 Pre-migration requirements • Cross OS migration is not supported; however, you can restore a Windows OS backup to a Linux OS and vice versa. If you are migrating from one OS to another, complete the following steps: 1. Install Network Advisor 12.0 (refer to “Installation” on page 1) on the current machine and migrate your data (refer to “Migrating data” on page 48). 2. Back up the server data on your current machine.
3 Migrating data Migrating data The quickest and simplest method of moving from one package to another is to enter the new license information on the Network Advisor License dialog box. To upgrade from a previous release, refer to “Upgrading the license” on page 41. If you have not installed the application, refer to “Installation” on page 1. NOTE Trial to Professional software migration is not supported. NOTE Licensed software to Trial software migration is not supported.
Migrating data 3 5. Click Next on the Data Migration screen. If you have products associated with the Brocade North America or Brocade International Call Home centers, a message displays. To map these Call Home centers to the Brocade E-mail Call Home center after migration, click Yes. To not map these Call Home centers, click No. NOTE Make sure you configure the Brocade E-mail Call Home center (refer to the Brocade Network Advisor User Manual or online help.
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 9. Complete the following steps on the Server IP Configuration screen.
3 Migrating data 10. Complete the following steps on the Server Configuration screen. FIGURE 2 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. You can configure the server port settings from the Options dialog box (Server Port pane).
3 Migrating data f. Enter a port number in the SNMP Port # field (default is 162). g. Click Next. If you enter a syslog port number already in use, a message displays. Click No on the message to remain on the Server Configuration screen and edit the syslog port number. Click Yes to close the message and continue with step 11. If you enter a port number already in use, a warning displays next to the associated port number field. Edit that port number and click Next.
3 Migrating data 13. (IP Enterprise) Select one of the following options on the IP Network Size screen and click Next: NOTE Port count is equal to the total number of all managed product ports. NOTE If you installed the SAN with SMI Agent + IP package on a 32-bit Windows system, the Large option is disabled for IP Network Size (Enterprise and Professional Plus). • Small (managing up to 1-20 products) • Medium (managing up to 21-200 products) • Large (managing up to 201-5050 products) 14.
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_0_0. 2.
4 58 Uninstalling from UNIX systems (headless uninstall) Network Advisor Installation and Migration Guide 53-1002699-01
Appendix A References In this Appendix • Network Advisor packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Edition feature support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Management server and client ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Scalability limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A Edition feature support Edition feature support Table 33 details whether the SAN features are supported in the Professional, Professional Plus, or Enterprise versions, or only through the Element Manager of the device.
A Edition feature support TABLE 33 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 33 SAN features supported (Continued) Feature Professional Professional Plus Enterprise 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 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 HBA Server and Storage port
A Edition feature support TABLE 33 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 33 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 33 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
A Edition feature support TABLE 34 IP features supported (Continued) Feature Professional Base Licensed version Base with Licensed Ethernet Fabrics Base with Unlicensed Ethernet Fabrics Change management Partial support Yes Yes Yes CLI configuration management No Yes Yes Yes CLI Element Manager Yes Yes Yes Yes Configuration snapshot No Yes Yes Yes Configuration repository management Yes Yes Yes Yes Manual backup Yes Yes Yes Yes Yes Yes Yes Yes Save configuration fo
A Edition feature support TABLE 34 IP features supported (Continued) Feature Professional Base Licensed version Base with Licensed Ethernet Fabrics Base with Unlicensed Ethernet Fabrics Fabric Watch NOTE: Only supported on DCB switches.
A Edition feature support TABLE 34 IP features supported (Continued) Feature Professional Base Licensed version Base with Licensed Ethernet Fabrics Base with Unlicensed Ethernet Fabrics MLX/XMR management No Yes Yes Yes MPLS management No Yes Yes Yes LSP No Yes Yes Yes VCID pool No Yes Yes Yes VLL manager No Yes Yes Yes VLL monitor No Yes Yes Yes VPLS manager No Yes Yes Yes VPLS monitor No Yes Yes Yes Real Time Performance collection, display, and reports Ye
A Edition feature support TABLE 34 IP features supported (Continued) Feature Professional Base Licensed version Base with Licensed Ethernet Fabrics Base with Unlicensed Ethernet Fabrics Topology management Yes Yes Yes Yes User Management No Yes Yes Yes VIP Server management No Yes Yes Yes VLAN management Yes Yes Yes Yes VM Plugin Support No Yes Yes Yes Web Element Manager Yes Yes Yes Yes Web Tools/Fabric Watch Yes Yes Yes Yes Member selection Yes Yes Yes Yes
A Management server and client ports 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.
Management server and client ports TABLE 35 A 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.
A Management server and client ports TABLE 35 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
Scalability limits TABLE 35 A Port usage and firewall requirements (Continued) Port Number Ports Transport Description Communication Path Open in Firewall 246112 JBoss Transaction Services Recovery Manager port TCP Not used remotely Server Yes 246122 JBoss Transaction Status Manager port TCP Not used remotely Server Yes 246132 JBoss Pooled invoker port TCP Not used remotely Server Yes 246142 JBoss Socket invoker port TCP Not used remotely Server Yes 246152 JBoss RMI dynamic
A Scalability limits Table 37 summarizes the SAN scalability limits for support with Network Advisor Professional Plus edition. TABLE 37 Professional Plus-supported limits by SAN size Values Limits Number of Fabrics 36 Number of Domains 20 Number of Switch Ports 2560 Number of Device Ports 4096 Number of Access Gateways 20 Performance Monitoring Polling 5 minutes Table 38 summarizes the SAN scalability limits for support with Network Advisor Professional edition.
A Scalability limits Table 41 summarizes the SAN scalability limits for pure Fabric OS fabrics with Network Advisor Enterprise edition.
