53-1002801-01 17 December 2012 Brocade Network Advisor SAN Installation and Migration Guide Supporting Network Advisor 12.0.
Copyright © 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Fabric OS hardware and software support . . . . . . . . . . . . . . . . .vi What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Document conventions . .
Chapter 2 Network Advisor Configuration Configuring Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Accessing the Network Advisor interfaces . . . . . . . . . . . . . . . . . . . . 19 Logging into a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Launching a remote client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Launching the SMC on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix A References Network Advisor packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Edition feature support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Management server and client ports . . . . . . . . . . . . . . . . . . . . . . . .58 Scalability limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi Network Advisor SAN Installation and Migration Guide 53-1002801-01
About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x • 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 1, 2 with FCoE10-24 Blades 8-slot Backbone Chassis with 10 Gbps 24-port FCoE blade Fabric OS v6.3.1_CEE Brocade DCX-4S 4-slot Backbone Chassis Fabric OS v6.0.0 or later Brocade DCX-4S with FC8-16, FC8-32, and FC848 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.
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 4) - Documented Linux 64-bit troubleshooting (refer to “Testing the connection on Linux systems” on page 25) - Documented unsupported migration work arounds (refer to “Pre-migration requirements” on page 36).
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.
xiv Network Advisor SAN Installation and Migration Guide 53-1002801-01
Chapter 1 Installation In this chapter • System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 • Pre-installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 • Installing the application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 • Headless installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 System requirements Server and Client operating system requirements NOTE The SAN with SMI Agent large installation is only supported on a 64-bit Windows® operating system. Table 2 summarizes the required Operating Systems (OS) for servers and the packages supported by each OS version. Table 3 summarizes the required OS for clients. TABLE 2 Server operating system requirements Operating system Version Windows - Linux® - Guest VMs - 1.
System requirements 1 Host requirements TABLE 3 Client operating system requirements Operating system Version Guest OS version Windows - Supports all client OS versions available for Windows and Linux. Linux Guest VMs 2003 Server SP2 (x86 32-bit) 2008 Server (x86 32-bit) XP Professional SP3 (x86 32-bit) 7 Professional (x86 32-bit) 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 Memory requirements Table 6 summarizes the minimum system memory requirements for running Network Advisor SAN with SMI Agent on Windows and Linux systems.
System requirements 1 Disk space requirements NOTE It is recommended that you add an additional 40 GB of disk space for the default temporary directory. Table 10 summarizes the minimum disk space requirements for running Network Advisor SAN with SMI Agent on Windows and Linux systems.
1 Pre-installation requirements Client and server system requirements NOTE Network Advisor is not supported in a Network Address Translation (NAT) environment where the server and client are on different sides of the NAT Server. Network Advisor has the following client and server system requirements: • In the Professional edition, a single server supports a single client, which must be a local client only.
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 6). If you are migrating data, refer to “Data Migration” on page 33. NOTE On Windows systems, you must be an Administrator with Read and Write privileges to install Network Advisor. NOTE On UNIX systems, you must be the root user to install Network Advisor.
Installing the application 1 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 9) before you configure the application. If the localhost is mapped to the loopback address, the configuration wizard displays.
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, insert the installation DVD into the DVD-ROM drive. • 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 12 Headless installation Network Advisor SAN Installation and Migration Guide 53-1002801-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 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 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.
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 requires Oracle JRE 1.7.0_09. For the website listing patch information, go to http://www.oracle.com/technetwork/java/javase/downloads/index.html. 1. Open a web browser and enter the IP address of the Network Advisor server in the Address bar.
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. 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. Click Configure SMI Agent.
2 Syslog troubleshooting Syslog troubleshooting If the default syslog port number is already in use, you will not receive any syslog messages from the device. Use one of the following procedures (depending on your operating system), to determine which process is running on the syslog port and to stop the process. 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.
Installing the ODBC driver 2 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.
2 Installing the ODBC driver 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.
2 Smart Card driver installation 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 27. 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.
Configuring an explicit server IP address 2 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.
2 Configuring remote client access to the database Configuring remote client access to the database 1. Open the pg.hba.conf file (in the Install_Home\data\databases\ directory). 2. To allow all IPv4 remote connections for all users, search for the following text and uncomment the second line: # IPv4 remote connections (Uncomment below line to allow all IPv4 remote users): #host all all 0.0.0.0/0 md5 3.
Chapter 3 Data Migration In this chapter • Upgrading the license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Supported migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Pre-migration requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Migrating data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 14 shows the migration paths from the Network Advisor 11.1.X, 11.2.X, 11.3.X, and 12.0.0 Professional, Trial, and Licensed versions. For the step-by-step migration procedure, refer to “Migrating data” on page 39. TABLE 14 Network Advisor version migration paths Current version Professional version Trial version Professional Plus Licensed Version Enterprise Professional Plus Enterprise Yes1 Yes1 Yes1 Yes1 Yes1 Network Advisor 11.1.X/11.2.X/11.3.
3 Pre-migration requirements DCFM migration paths NOTE Before you migrate from DCFM to Network Advisor 11.0.X, 11.1.0, 11.1.1, or 11.1.2, you must reset your DCFM password back to the default (password). You cannot migrate directly from DCFM 10.0.X, DCFM 10.1.X or DCFM 10.3.X to Network Advisor 12.0.0. You must first migrate to DCFM 10.4.X, then migrate to Network Advisor 11.1.X, then migrate to Network Advisor 12.0.0. To migrate from DCFM 10.0.X, DCFM 10.1.X or DCFM 10.3.X to DCFM 10.4.
3 Pre-migration requirements Pre-migration requirements when migrating from one server to another • If you are migrating from a pre-12.0.0 release on a 32-bit Windows server to Network Advisor 12.0.0 on a 64-bit Windows server, complete the following steps. NOTE If you are migrating from DCFM 10.4.X or Network Advisor 11.0.X on a 32-bit server, first migrate to Network Advisor 11.1.X on a 32-bit server, then migrate to Network Advisor 12.0 on a 64-bit server by completing the following steps. 1.
3 Pre-migration requirements • If you are migrating from a Network Advisor 12.0.0 one server to another server, complete the following steps. 1. Install Network Advisor 12.0.0 on your current machine (refer to “Data Migration” on page 33) and migrate your data (“Migrating data” on page 39). 2. Back up the server data on your current machine. For instructions, refer to “Configuring backup” in the Brocade Network Advisor User Manual or online help. 3. Install 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 • 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.
3 Migrating data • Network Advisor - Professional Go to step 8. Bundled with Fabric OS and IronWare OS devices to manage small SAN networks from a single interface. 7. Choose one of the following options on the Server License screen: • If you are migrating from a licensed source, the source license information displays. Click Next. Continue with step 8. • If you are migrating from Professional or Trial software to Licensed software, browse to the license file (.xml) and click Next.
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.
Migrating data 3 15. 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. 16. Click Login. 17. Click OK on the Network Advisor Login Banner.
3 46 Migrating data Network Advisor SAN Installation and Migration Guide 53-1002801-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_0_0. 2.
4 50 Uninstalling from UNIX systems (headless uninstall) Network Advisor SAN Installation and Migration Guide 53-1002801-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 17 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 17 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 17 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 17 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 17 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 17 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 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 18 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 18 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 18 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 20 summarizes the SAN scalability limits for support with Network Advisor Professional Plus edition. TABLE 20 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 21 summarizes the SAN scalability limits for support with Network Advisor Professional edition.
