Installation Guide
Installation Guide
16 March 2011
Document History
Brocade Network Advisor Installation Guide 53-1002046-01 New document. October 2010
Brocade Network Advisor Installation Guide 53-1002170-01 Updated for the Network May 2011
Advisor 11.1.X release.
Brocade Network Advisor Installation Guide 53-1002357-01 Updated for the Network September 2011
Advisor 11.2.X release.
Brocade Network Advisor Installation Guide 53-1002532-01 Updated for the Network March 2011
Advisor 11.2.1 release.
In this guide
• System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
• Pre-installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
• Installing the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
• Headless installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
• Professional edition configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
• Trial version configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
• License version configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
• SMI Agent only configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
• Syslog troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
• Installing the ODBC driver on Windows systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
• Configuring an explicit server IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
• Smart Card driver installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
• Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
• Edition feature support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
• Network Advisor packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
• Management server and client ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
• Scalability limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
System requirements
Use the following sections to determine if you have met the requirements for this application.
• “Operating system requirements” on page 4
• “Host requirements” on page 6
• “Memory requirements” on page 7
• “Disk space requirements” on page 9
• “Browser requirements” on page 10
• “Client and server system requirements” on page 11
Windows® • 2003 Server SP2 (x86 32-bit) SAN with SMI Agent
• 2008 Server (x86 32-bit) IP only
• XP Professional SP3 (x86 SMI Agent only
32-bit) SAN with SMI Agent + IP
• 7 Professional (x86 32-bit) (Professional, Professional Plus
(Medium), and Enterprise (Medium)
only)
• 2008 R2 Data Center Edition SAN with SMI Agent
(x86 64-bit) IP only
• 2008 R2 Standard Edition (x86 SMI Agent only
64-bit) SAN with SMI Agent + IP
• 2008 R2 Enterprise Edition
(x86 64-bit)
Linux® • RedHat 5.5 Advanced SAN with SMI Agent
Platform (x86 32-bit) IP only
• RedHat 5.6 Advanced SMI Agent only
Platform (x86 32-bit, x86 64-bit SAN with SMI Agent + IP
— Network Advisor will run in
32-bit compatability mode)
• RedHat 6.1 Advanced
Platform (x86 32-bit)
• SuSE Enterprise Server 11 (x86
32-bit)
• Oracle Enterprise 5.6 (x86
32-bit)
VMware® • ESX Server 4.1 Windows 2003 Server SP2 (x86 SAN with SMI Agent
• ESX Server 5.0 32-bit) IP only
• ESX Server i 5.0 SMI Agent only
• vCenter 4.1 SAN with SMI Agent + IP
(Professional, Professional Plus
(Medium), and Enterprise (Medium)
only)
• ESX Server 4.1 • Windows 2008 R2 Data Center SAN with SMI Agent
• ESX Server 5.0 Edition (x86 64-bit) IP only
• ESX Server i 5.0 • Windows 2008 R2 Standard SMI Agent only
• vCenter 4.1 Edition (x86 64-bit) SAN with SMI Agent + IP
• Windows 2008 R2 Enterprise
Edition (x86 64-bit)
• Linux RedHat 5.5 Advanced
Platform (x86 32-bit)
• Linux RedHat 5.6 Advanced
Platform (x86 32-bit, x86
64-bit)
• Linux SuSE Enterprise Server
11 (x86 32-bit)
• Linux Oracle Enterprise 5.6
(x86 32-bit)
Host requirements
Table 3 through Table 5 summarizes the minimum host requirements for running Network Advisor SAN with SMI
Agent + IP on Windows and Linux systems.
Server plus 1 local Intel Core2 duo 2 GHz or Intel Core2 duo 2 GHz or
client equivalent equivalent
Remote client only N/A Intel Core2 duo 2 GHz or
equivalent
TABLE 4 SAN with SMI Agent + IP host requirements for server plus 1 local client
Small LAN Medium LAN Large LAN
Small SAN Enterprise Intel Core2 duo 2GHz or Intel Dual CPU Core2 duo Intel Dual CPU Core2 duo
equivalent 2.4 GHz or equivalent 2.4 GHz or equivalent
Medium SAN Enterprise Intel Dual CPU Core2 duo Intel Dual CPU Core2 duo Intel quad dual core or dual
2.4 GHz or equivalent 2.4 GHz or equivalent quad core, 2.4 GHz or
equivalent
Large SAN Enterprise Intel Dual CPU Core2 duo Intel quad dual core or dual Intel quad dual core or dual
2.4 GHz or equivalent quad core, 2.4 GHz or quad core, 2.4 GHz or
equivalent equivalent
TABLE 5 SAN with SMI Agent + IP host requirements for remote client
Small LAN Medium LAN Large LAN
Small SAN Enterprise Intel Core2 duo 2 GHz or Intel Core2 duo 2 GHz or Intel Dual CPU Core2 duo
equivalent equivalent 2.4 GHz or equivalent
Medium SAN Enterprise Intel Core2 duo 2 GHz or Intel Dual CPU Core2 duo Intel Dual CPU Core2 duo
equivalent 2.4 GHz or equivalent 2.4 GHz or equivalent
Large SAN Enterprise Intel Dual CPU Core2 duo Intel Dual CPU Core2 duo Intel Dual CPU Core2 duo
2.4 GHz or equivalent 2.4 GHz or equivalent 2.4 GHz or equivalent,
Table 6 summarizes the minimum host requirements for running Network Advisor SAN with SMI Agent on Windows
and Linux systems.
Server plus one local Intel Core2 duo Intel Core2 duo Intel Core2 duo Intel Dual CPU Intel Dual CPU
client 2 GHz or equivalent 2 GHz or equivalent 2 GHz or equivalent Core2 duo 2.4 GHz Core2 duo 2.4 GHz
or equivalent or equivalent
Remote client only N/A Intel Core2 duo Intel Core2 duo Intel Core2 duo Intel Core2 duo
2 GHz or equivalent 2 GHz or equivalent 2 GHz or equivalent 2 GHz or equivalent
Table 7 summarizes the minimum host requirements for running Network Advisor IP on Windows and Linux systems.
Server plus one local Intel Core2 duo Intel Core2 duo Intel Dual CPU Intel Dual CPU
client 2 GHz or equivalent 2 GHz or equivalent, Core2 duo 2.4 GHz Core2 duo 2.4 GHz
or equivalent or equivalent
Remote client only N/A Intel Core2 duo Intel Core2 duo Intel Core2 duo
2 GHz or equivalent 2 GHz or equivalent 2 GHz or equivalent
Table 8 summarizes the minimum host requirements for running SMI Agent only on Windows and Linux systems.
Server plus one local Intel Core2 duo Intel Dual CPU Intel Dual CPU
client 2GHz or equivalent Core2 duo 2.4 GHz Core2 duo 2.4 GHz
or equivalent or equivalent
Remote client only Intel Core2 duo Intel Core2 duo Intel Core2 duo
2GHz or equivalent 2GHz or equivalent 2GHz or equivalent
Memory requirements
Table 9 through Table 11 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.
NOTE
The Network Advisor Server for SAN with SMI Agent + IP (Enterprise) with both a large SAN and a large IP is only
supported on 64-bit Windows systems and 32-bit Linux systems.
TABLE 10 SAN with SMI Agent + IP (Enterprise) memory requirements for server plus 1 local client
Small LAN Medium LAN Large LAN
NOTE
The Network Advisor Client for SAN with SMI Agent + IP (Enterprise) is also supported on 32-bit Windows and Linux
systems.
TABLE 11 SAN with SMI Agent + IP (Enterprise) memory requirements for remote client
Small LAN Medium LAN Large LAN
Table 12 summarizes the minimum system memory requirements for running Network Advisor SAN with SMI Agent
on Windows and Linux systems.
Table 13 summarizes the minimum system memory requirements for running Network Advisor IP on Windows and
Linux systems.
Table 14 summarizes the minimum system memory requirements for running SMI Agent only on Windows and Linux
systems.
TABLE 16 SAN with SMI Agent + IP (Enterprise) disk space requirements for server plus 1 local client
Small LAN Medium LAN Large LAN
TABLE 17 SAN with SMI Agent + IP (Enterprise) disk space requirements for remote client
Small LAN Medium LAN Large LAN
Table 18 summarizes the minimum disk space requirements for running Network Advisor SAN with SMI Agent on
Windows and Linux systems.
Table 19 summarizes the minimum required disk space requirements for running Network Advisor IP on Windows
and Linux systems.
Table 20 summarizes the minimum disk space requirements for running SMI Agent only on Windows and Linux
systems.
NOTE
If you enable periodic supportSave or configure the Network Advisor server as the Upload Failure Data Capture
location for monitored switches, then additional disk space will be required. Each switch supportSave file is
approximately 5 MB and each Upload Failure Data Capture file is approximately 500 KB. To determine the disk space
requirements, multiply the frequency of scheduled supportSave files by 5 MB and the expected Upload Failure Data
Capture files by 500 KB before the planned periodic purge activity.
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.6.0 update 26 for Network Advisor
- Oracle JRE 1.6.0 update 26 for Web Tools
For the website listing patch information, go to
http://www.oracle.com/technetwork/java/javase/downloads/index.html.
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.
• In Professional Plus and Enterprise edtions, a single server supports a maximum of 8 clients, which can be local
or remote.
Pre-installation requirements
Before you install Network Advisor, make sure you meet the following requirements for each platform.
• Make sure all system requirements have been met prior to installation. For specific system requirements, refer
to “System requirements” on page 4.
• To avoid errors, close all instances of the application before beginning the installation or uninstallation
procedures.
For UNIX systems, if you still receive error messages after closing the application, enter the following commands:
#ps -ef | grep -i “” to list the process IDs
#kill -9 “Process_ID” where Process_ID is any Management application process
NOTE
SMI Agent is only available with the SAN with SMI Agent or SAN with SMI Agent + IP packages, it is not available with
the IP only package.
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.
NOTE
Do not install to the root directory C:\ (Windows) or / (UNIX).
5. Review the displayed installation summary on the Pre-Installation Summary screen and click Install.
6. Make sure the Launch Configuration check box is selected (default) on the Installation Complete screen, and
click Done.
Headless installation
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.
NOTE
If you use an FTP Server which is not configured on the same machine as the Management application, the
Firmware Repository feature will not be available.
6. Select an address from the Switch - Server IP Configuration Preferred Address list on the Server IP Configuration
screen and click Next.
The Server IP Configuration address is set to “localhost” by default. You cannot change this address.
7. 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.
a. Enter a port number in the Web Server Port # (HTTP) field (default is 80).
b. Enter a port number in the Database Port # field (default is 5432).
ATTENTION
Do not use a port number less than 1024. Using a port number less than 1024 causes the installation to
stop responding (hang or freeze) on “Initialize Database”.
NOTE
The server requires 13 consecutive free ports beginning with the starting port number.
NOTE
If the default syslog port number is already in use, you will not receive any syslog messages from the device.
To find and stop the process currently running on the default syslog port number, refer to “Syslog
troubleshooting” on page 28.
9. Select the Start Client check box, if necessary, on the Start Server screen and click Finish.
After all of the Network Advisor services are started, the Log In dialog box displays.
To make changes to the configuration, you can re-launch the configuration wizard. On Windows systems, select
Start > Programs > Network Advisor 11.X.X > Configuration Wizard. On UNIX systems, execute sh
Install_Home/bin/configwizard.
NOTE
To launch the configuration wizard, you must be the Administrator on Windows systems and the root user on
UNIX systems.
10. Enter your user name and password and click Login.
The defaults are Administrator and password, respectively.
11. Click OK on the Network Advisor Login Banner.
ATTENTION
If you choose to install Trial, once the trial period ends (75 days), you must upgrade to Licensed version.
NOTE
If you use an FTP Server which is not configured on the same machine as Network Advisor, the Firmware
Repository feature will not be available.
NOTE
If the “hostname” contains invalid characters, the host name does not display in the list. Valid characters
include alphanumeric and dash (-) characters. The IP address is selected by default. If an IPv6 address is
selected, server start up will fail.
If Domain Name System (DNS) is not configured for your network, do not select the “hostname” option from
either the Server IP Configuration or Switch - Server IP Configuration Preferred Address list. Selecting the
“hostname” option prevents clients and devices from communicating with the server.
If you select a specific IP address from the Server IP Configuration screen and the selected IP address
changes, you will not be able to connect to the server. To change the IP address, refer to “Configuring an
explicit server IP address” on page 32.
c. Click Next.
8. Complete the following steps on the Server Configuration screen (Figure 2).
NOTE
Do not use port 2638 for any of these port numbers. Port 2638 is used internally by the server.
ATTENTION
Do not use a port number less than 1024. Using a port number less than 1024 causes the installation to
stop responding (hang or freeze) on “Initialize Database”.
e. Enter a port number in the Starting Port Number field (default is 24600).
NOTE
The server requires 16 consecutive free ports beginning with the starting port number.
f. Enter a port number in the Syslog Port Number field (default is 514).
NOTE
If the default syslog port number is already in use, you will not receive any syslog messages from the device.
To find and stop the process currently running on the default Syslog port number, refer to “Syslog
troubleshooting” on page 28.
g. Enter a port number in the SNMP Port Number field (default is 162).
h. Click Next.
If you enter a syslog port number already in use, a “syslog port not free” 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 9.
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.
9. (SAN with SMI Agent + IP or SAN with SMI Agent) Complete the following steps on the SMI Agent Configuration
screen.
NOTE
If you selected IP only, this screen does not display. Continue with step 10.
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. Enter the SMI Agent port number in the SMI Agent Port # field (default is 5989 if SSL Enabled is selected;
otherwise, the default is 5988).
e. Click Next.
10. (SAN with SMI Agent + IP or SAN with SMI Agent Enterprise) Select one of the following options on the SAN
Network Size screen and click Next:
• Small (managing up to 2000 switch ports, 1-20 domains)
• Medium (managing up to 5000 switch ports, 21-60 domains)
• Large (managing up to 9000 switch ports, 61-120 domains)
NOTE
If you selected the 75 day trial with the Professional Plus (2560 switch ports, 4 fabrics and 4096 devices)
option, the SAN Network Size screen does not display. The SAN size defaults to Small.
NOTE
If you installed the SAN with SMI Agent + IP package on a 32-bit Windows system, the Large option is disabled.
NOTE
Port count is equal to the total number of switch ports across all fabrics.
11. Verify your configuration information on the Server Configuration Summary screen and click Next.
12. Complete the following steps on the Start Server screen.
a. (SAN with SMI Agent + IP or SAN with SMI Agent) Select the Start SMI Agent check box, if necessary.
b. (SAN with SMI Agent + IP or SAN with SMI Agent) Select the Start SLP check box, if necessary.
c. Select the Start Client check box, if necessary.
d. Click Finish.
After all of the selected services are started, the Log In dialog box displays.
To make changes to the configuration, you can re-launch the configuration wizard. On Windows systems,
select Start > Programs > Network Advisor 11.X.X > Configuration Wizard. On UNIX systems, execute sh
Install_Home/bin/configwizard.
NOTE
To launch the configuration wizard, you must be the Administrator on Windows systems and the root user on
UNIX systems.
13. Enter your user name and password and click Login.
The defaults are Administrator and password, respectively.
14. Click OK on the Network Advisor Login Banner.
NOTE
If you use the SAN with SMI Agent +IP Enterprise license key and the IP product managed count is more than
550, Event-based collection for IP discovery will be turned off.
If you have the SAN with SMI Agent +IP Enterprise license key, a message displays. Click No on the message to
remain on the Server License screen and edit the license key. Click Yes to close the message and continue with
step 6.
6. Select Internal FTP Server or External FTP Server on the FTP Server screen and click Next.
The internal FTP server uses a default account and port 21. If port 21 is busy, a message displays. Click OK to
close the message and continue. Once Network Advisor is configured, make sure port 21 is free and restart the
server to start the FTP service.
You can configure your own account from the Options dialog box. For instructions, refer to Configuring an
internal FTP server and Configuring an external FTP or SCP server in the user manual.
NOTE
If you use an FTP Server which is not configured on the same machine as Network Advisor, the Firmware
Repository feature will not be available.
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 the an IPv6 address is
selected, server startup will fail.
If DNS is not configured for your network, do not select the “hostname” option from either the Server IP
Configuration or Switch - Server IP Configuration Preferred Address list. Selecting the “hostname” option
prevents clients and devices from communicating with the server.
If you select a specific IP address from the Server IP Configuration screen and the selected IP address
changes, you will not be able to connect to the server. To change the IP address, refer to “Configuring an
explicit server IP address” on page 32.
c. Click Next.
8. Complete the following steps on the Server Configuration screen (Figure 3).
NOTE
Do not use port 2638 for any of these port numbers. Port 2638 is used internally by the server.
NOTE
Do not use a port number less than 1024. Using a port number less than 1024 causes the installation to
stop responding (hang or freeze) on “Initialize Database”.
e. Enter a port number in the Starting Port Number field (default is 24600).
NOTE
The server requires 16 consecutive free ports beginning with the starting port number.
NOTE
If the default syslog port number is already in use, you will not receive any syslog messages from the device.
To find and stop the process currently running on the default syslog port number, refer to “Syslog
troubleshooting” on page 28.
NOTE
If you selected IP only, this screen does not display. Continue with step 10.
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. Enter the SMI Agent port number in the SMI Agent Port # field (default is 5989 if SSL Enabled is selected;
otherwise, the default is 5988).
e. Click Next.
10. (SAN with SMI Agent + IP or SAN with SMI Agent Enterprise) Select one of the following options on the SAN
Network Size screen and click Next:
• Small (managing up to 2000 switch ports, 1-20 domains)
• Medium (managing up to 5000 switch ports, 21-60 domains)
• Large (managing up to 9000 switch ports, 61-120 domains)
NOTE
Port count is equal to the total number of switch ports across all fabrics.
NOTE
If you installed the SAN with SMI Agent + IP package on a 32-bit Windows system, the Large option is disabled
for SAN Network Size (Enterprise).
11. (SAN with SMI Agent + IP or IP Enterprise) Select one of the following options on the IP Network Size screen and
click Next:
• Small (managing up to 1000 device ports, 1-20 products)
• Medium (managing up to 10000 device ports, 21-200 products)
• Large (managing up to 25000 device ports, 201-5050 products)
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).
12. Verify your configuration information on the Server Configuration Summary screen and click Next.
13. Complete the following steps on the Start Server screen.
a. Select the Start SMI Agent check box, if necessary.
Only enabled if you enabled SMI Agent on the SMI Agent Configuration screen.
b. Select the Start SLP check box, if necessary.
Only enabled if you enabled SLP on the SMI Agent Configuration screen.
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.
To make changes to the configuration, you can re-launch the configuration wizard. On Windows systems,
select Start > Programs > Network Advisor 11.X.X > Configuration Wizard. On UNIX systems, execute sh
Install_Home/bin/configwizard.
NOTE
To launch the configuration wizard, you must be the Administrator on Windows systems and the root user on
UNIX systems.
14. Enter your user name and password and click Login.
The defaults are Administrator and password, respectively.
15. Click OK on the Network Advisor Login Banner.
NOTE
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
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 the an IPv6 address is
selected, server startup will fail.
If DNS is not configured for your network, do not select the “hostname” option from either the Server IP
Configuration or Switch - Server IP Configuration Preferred Address list. Selecting the “hostname” option
prevents clients and devices from communicating with the server.
If you select a specific IP address from the Server IP Configuration screen and the selected IP address
changes, you will not be able to connect to the server. To change the IP address, refer to “Configuring an
explicit server IP address” on page 32.
c. Click Next.
NOTE
Do not use port 2638 for any of these port numbers. Port 2638 is used internally by the server.
ATTENTION
Do not use a port number less than 1024. Using a port number less than 1024 causes the installation to
stop responding (hang or freeze) on “Initialize Database”.
NOTE
The server requires 16 consecutive free ports beginning with the starting port number.
NOTE
If the default syslog port number is already in use, you will not receive any syslog messages from the device.
To find and stop the process currently running on the default syslog port number, refer to “Syslog
troubleshooting” on page 28.
NOTE
Port count is equal to the total number of switch ports across all fabrics.
NOTE
To launch the Server Management Console, you must be the Administrator on Windows systems and the
root user on UNIX systems.
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.
NOTE
If you select an invalid location, the ODBC driver is installed in a different location than where the ODBC
executable drivers are located.
9. Click Finish.
The PostgreSQL Unicode ODBC Driver (psqlODBC) Setup dialog box displays.
10. Enter a name for the data source in the Datasource field.
11. Enter the description of the Network advisor database in the Description field.
12. Enter the name of the Network Advisor database in the Database field.
13. Select enable or disable from the SSL Mode list to specify whether or not to use SSL when connecting to the
database.
14. Enter the IP address or host name of the Network Advisor server in the Server field.
15. Enter the database server port number in the Port Number field.
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.
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.bin
NOTE
If you select an invalid location, the ODBC driver is installed in a different location than where the ODBC
executable drivers are located.
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.ini file in an editor and enter the datasource information as follows:
[TestDB]
Description = PostgreSQL 8.3
Driver = /opt/PostgreSQL/psqlODBC/lib/psqlodbcw.so
Database = dcmdb
Servername = 172.26.1.54
UserName = dcmadmin
Password = passw0rd
Port = 5432
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 the an IPv6 address is
selected, server startup will fail.
If DNS is not configured for your network, do not select the “hostname” option from either the Server IP
Configuration or Switch - Server IP Configuration Preferred Address list. Selecting the “hostname” option
prevents clients and devices from communicating with the server.
c. Click Next.
6. Click Next on the Server Configuration screen.
7. (SAN with SMI Agent or SAN with SMI Agent + IP packages) Click Next on the SMI Agent Configuration screen.
8. Verify your configuration information on the Server Configuration Summary screen and click Next.
9. Click Finish on the Start Server screen.
10. Click Yes on the restart server confirmation message.
11. Enter your user name and password and click Login.
The defaults are Administrator and password, respectively.
12. Click OK on the Login Banner.
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.4.101-linux-x86.tar.gz file.
> su
> cd /opt
> gunzip pcsc-lite-1.4.101-linux-x86.tar.gz
> tar -xvf pcsc-lite-1.4.101-linux-x86.tar
After the pcsc_lite_1.4.101.tar file is extracted, the necessary binary, library, and smart card drivers are stored
in the /opt/pcsc directory.
4. If you installed a pcsc directory into a location other than /opt, modify the pcscctl script to change “/opt” to the
directory you specified in step 1.
> cd <new_dir>
> vi pcscctl
Search for “/opt” and change it to the name of the new directory.
5. Create a soft link into the system directory. This is to support the automatic restart of the pcscd daemon upon
system restart.
If you installed the pcsc directory into the /opt directory, just create the soft link. 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.d/pcscd
redhat> chkconfig --add pcscd
NOTE
Before you enter chkconfig --add pcscd, you can enter chkconfig –list | grep pcscd to verify that the pcscd
file is already on the list. If it already exists, you do not need to enter chkconfig –add pcscd. After you reboot
the system, you should expect the following links under /etc/rc2.d, /etc/rc3.d, /etc/rc3.d, /etc/rc4.d, and
/etc/rc5.d.
NOTE
For some Linux vendors, the Smart Card driver may come with the operating system. In this case, extra
system configuration may be needed. For more information, refer to “Detecting and correcting a default
Linux Smart Card driver” on page 36.
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.
Example
> ls –l libpcsc*
lrwxrwxrwx 1 root root 20 Aug 4 16:16 libpcsclite.so ->
libpcsclite.so.1.0.0
lrwxrwxrwx 1 root root 20 Jun 4 12:30 libpcsclite.so.1 ->
libpcsclite.so.1.0.0
lrwxrwxrwx 1 root root 34 Aug 5 14:36 libpcsclite.so.1.0.0
> ls –l libpcsc*
lrwxrwxrwx 1 root root 20 Aug 4 16:16 libpcsclite.so ->
libpcsclite.so.1.0.0
lrwxrwxrwx 1 root root 20 Jun 4 12:30 libpcsclite.so.1 ->
libpcsclite.so.1.0.0
lrwxrwxrwx 1 root root 34 Aug 5 14:36 libpcsclite.so.1.0.0 ->
/opt/pcsc/lib/libpcsclite.so.1.0.0
-rwxr-xr-x 1 root root 35428 Aug 4 16:17 libpcsclite.so.1.0.0.org
If the results contain “pcscd”, and it is not located under /opt/pcsc or /etc/init.d/pcscd, a different driver exists
on the system.
2. Make sure the pcscd file on the /etc/init.d directory is linked to /opt/pcsc/pcscctl by running the following
commands:
> cd /etc/init.d
> ls –l pcscd
lrwxrwxrwx 1 root root 17 Jul 28 01:29 pcscd -> /opt/pcsc/pcscctl
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
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. If the size is different and the existing pcscd script
contains the following information, you must clean up the driver configuration. The example below shows a
different pscsd.org script and how to do the configuration cleanup. The configuration level is 2345, the start
priority is 25, and the stop priority is 88.
> more /etc/init.d/pcscd
#!/bin/sh
#
# pcscd Starts the pcscd Daemon
#
# chkconfig: 2345 25 88
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.
lrwxrwxrwx 1 root root 15 Jul 28 01:50 S94pcscd -> ../init.d/pcscd
6. For the remote client, ensure that the Smart Card native library is linked to the one under /opt/pcsc/lib.
> cd /
> find . –name libpcsclite.so* -print
If the library libpcsclite.so* exists in multiple locations, you must ensure that there is only one library under /lib
or /usr/lib, and that it is linked to the library on /opt/pcsc/lib correctly. For example, to find a copy of the library
on /lib, use the following commands.
> cd /lib
> ls –al libpcsclite.so
Uninstallation
This section provides step-by-step instructions to uninstall Network Advisor and SMI Agent from both Windows and
UNIX systems.
NOTE
Network Advisor is installed on a separate directory from your previous version; therefore, you do not need to uninstall
the previous version immediately. However, you cannot run both versions simultaneously.
NOTE
The Uninstall folder is retained.
1. Go to Install_Home/Uninstall_Network_Advisor11_2_1.
2. Execute ./Uninstall_Network_Advisor11_2_1.
3. Select one of the following options on the Uninstall Option screen:
• Partial Uninstall—Configuration and performance data is retained to be re-used by the new installation.
• Full Uninstall—All data is removed.
4. Click Uninstall.
5. Click Done on the Uninstall Complete screen.
FICON/CUP
Cascaded FICON configuration wizard No No Yes
Cascaded FICON Fabric merge wizard No No Yes
PDCM Matrix Element Element Yes
Manager Manager
Table 22 details whether the IP features are fully or partially supported in the Professional or Licensed Version.
Professional
• SAN — Support for 1 fabric, 1,000 devices, and 1,000 ports
NOTE: SMI Agent is not supported on Professional.
IP Licensed Version — Enterprise
• IP — Support for 5,050 products and 100 MPLS products
Professional
• IP — Support for 20 products
SMI Agent only N/A
NOTE
Professional edition does not support remote clients.
Table 24 lists the ports that need to be opened up in the firewall for Professional.
201 FTP Port (Control) TCP FTP Control port for internal Client–Server No
FTP server Switch–Server Yes
211, 2 FTP Port (Data) TCP FTP Data port for internal Client–Server No
FTP server Switch–Server Yes
221 SSH or Secure Telnet TCP Sectelnet port from server to Server–Switch Yes
switch/client to switch Client–Switch
231 Telnet TCP Telnet port from server/client Server–Switch Yes
to switch Client–Switch
25 SMTP Server port TCP SMTP Server port for E-mail Server–SMTP Yes
communication Server
49 TACACS+ Authentication port TCP TACACS+ server port for Server–TACACS+ Yes
authentication if TACACS+ is Server
chosen as an external
authentication
32768 - Ephemeral ports UDP Ephemeral transport protocol Switch - Server Yes
65535 ports.
Table 25 lists the ports that need to be opened up in the firewall for Trial and Licensed Version.
201 FTP Port (Control) TCP FTP Control port for internal Client–Server Yes
FTP server Switch–Server Yes
211, 2 FTP Port (Data) TCP FTP Data port for internal Client–Server Yes
FTP server Switch–Server Yes
221 SSH or Secure Telnet TCP Sectelnet port from server to Server–Switch Yes
switch/client to switch Client–Switch
231 Telnet TCP Telnet port from server/client Server–Switch Yes
to switch Client–Switch
25 SMTP Server port TCP SMTP Server port for E-mail Server–SMTP Yes
communication Server
49 TACACS+ Authentication port TCP TACACS+ server port for Server–TACACS+ Yes
authentication if TACACS+ is Server
chosen as an external
authentication
80 jboss.web.http.port TCP Non-SSL HTTP/1.1 connector Client–Server Yes
port
803, 4 Switch http TCP Switch non-SSL http port for Server–Switch Yes
http and CAL communication Client–Switch
1611 SNMP Port UDP Default SNMP port Server–Switch Yes
1623 snmp.trap.port UDP Default SNMP trap port Switch–Server Yes
389 LDAP Authentication Server Port TCP LDAP server port for Server–LDAP Yes
authentication if LDAP is Server
chosen as an external
authentication
4433, 4, 5 Switch https TCP Switch SSL http port for https Server–Switch Yes
and CAL communication Client–Switch
5146 Syslog Port UDP Default Syslog Port Switch–Server Yes
636 LDAP Authentication SSL port TCP LDAP server port for Server–LDAP Yes
authentication if LDAP is Server
chosen as an external
authentication and SSL is
enabled
10241, 7 MPI TCP MPI trap recipient port Switch–Server Yes
1812 RADIUS Authentication Server Port TCP RADIUS server port for Server–RADIUS Yes
authentication if RADIUS is Server
chosen as an external
authentication
20481, 9 MPI TCP MPI discovery NMRU port Server–Switch Yes
1,5,7,9
2049 MPI TCP MPI discovery NMRU port for Server–Switch Yes
SSL
26388 Database port (Enforced during install) TCP Port used by database Server–Database Yes
Remote ODBC–
Database
44301, 5, 7 MPI TCP XML-RCP port for SSL Server–Switch Yes
5988 SMI Agent port TCP SMI Agent port SMI Agent Server– Yes
Client
5989 SMI Agent port with SSL enabled TCP SMI Agent port with SSL SMI Agent Server– Yes
enabled Client
80801, 7 MPI TCP XML-RCP port/HTTP port Server–Switch Yes
10
24600 jboss.naming.jnp.port - port 0 TCP Bootstrap JNP service port Client–Server Yes
24601 jboss.connector.ejb3.port - port 1 TCP EJB3 connector port Client–Server Yes
24602 jboss.connector.bisocket.port - port 2 TCP Bisocket connector port Client–Server Yes
24603 jboss.connector.bisocket.secondary.port TCP Bisocket connector secondary Client–Server Yes
- port 3 port
246045 jboss.connector.sslbisocket.port - port 4 TCP SSL Bisocket connector port Client–Server Yes
246055 jboss.connector.sslbisocket.secondary.p TCP SSL Bisocket connector Client–Server Yes
ort - port 5 secondary port
24606 smp.registry.port - port 6 TCP RMI registry port Client–Server Yes
24607 smp.server.export.port - port 7 TCP RMI export port Client–Server Yes
24608 smp.server.cliProxyListening port - port TCP CLI proxy telnet port Client–Server Yes
8
24609 jboss.naming.rmi.port - port 9 TCP RMI naming service port Client–Server Yes
Scalability limits
The following tables summarize the scalability limits for support with Network Advisor.
Table 26 summarizes the SAN scalability limits for support with Network Advisor Enterprise edition.
Number of Fabrics 8 16 24
Number of Domains 20 60 120
Number of Switch Ports 2000 5000 9000
Number of Device Ports 5000 10000 20000
Number of Access Gateways 20 30 40
Performance Monitoring Polling 5 minutes 5 minutes 5 minutes
Table 27 summarizes the SAN scalability limits for support with Network Advisor Professional Plus edition.
Number of Fabrics 4
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 28 summarizes the SAN scalability limits for support with Network Advisor Professional edition.
Number of Fabrics 1
Number of Domains 10
Number of Switch Ports 1000
Number of Device Ports 1000
Number of Access Gateways 5
Performance Monitoring Polling N/A
Table 29 summarizes the IP scalability limits for support with Network Advisor Enterprise edition.
Table 30 summarizes the IP scalability limits for support with Network Advisor Professional edition.
Number of Products 20
Number of MPLS Products 0
Table 31 summarizes the SAN scalability limits for mixed fabrics (Fabric OS and M-EOS fabrics) with Network Advisor.
TABLE 31 Supported limits by SAN size for mixed fabrics (Fabric OS and M-EOS fabrics)
Values Small Medium Large
Number of Fabrics 8 16 24
Number of Domains 10 30 60
Number of Switch Ports 1000 2500 5000
Number of Device Ports 2500 5000 10000
Number of Access Gateways 20 30 40
Performance Monitoring Polling 5 minutes 5 minutes 5 minutes
Table 32 summarizes the SAN scalability limits for pure M-EOS fabrics with Network Advisor.
Number of Fabrics 8 16 24
Number of Domains 10 30 60
Number of Switch Ports 1000 2500 5000
Number of Device Ports 2500 5000 10000
Number of Access Gateways 20 30 40
Performance Monitoring Polling 5 minutes 5 minutes 5 minutes
Table 33 summarizes the SAN scalability limits for pure Fabric OS fabrics with Network Advisor Enterprise edition.
TABLE 33 Enterprise-supported limits by SAN size for SMI Agent only on pure Fabric OS fabrics
Small Medium Large
Number of Fabrics 8 16 24
Number of Domains 20 60 120
Number of Switch Ports 2000 5000 9000
Number of Device Ports 5000 10000 20000
Number of Access Gateways 20 30 40
Table 34 summarizes the SAN scalability limits for SMI Agent only on mixed fabrics (Fabric OS and M-EOS fabrics)
with Network Advisor.
TABLE 34 Supported limits by SAN size for SMI Agent only on mixed fabrics (Fabric OS and M-EOS fabrics)
Values Small Medium Large
Number of Fabrics 8 16 24
Number of Domains 10 30 60
Number of Switch Ports 1000 2500 5000
Number of Device Ports 2500 5000 10000
Number of Access Gateways 20 30 40
Table 32 summarizes the SAN scalability limits for for SMI Agent only on pure M-EOS fabrics with Network Advisor.
TABLE 35 Supported limits by SAN size for SMI Agent only on pure M-EOS fabrics
Small Medium Large
Number of Fabrics 8 16 24
Number of Domains 10 30 60
Number of Switch Ports 1000 2500 5000
Number of Device Ports 2500 5000 10000
Number of Access Gateways 20 30 40