Cisco Nexus 5000 Series Switch Fabric Manager Software Configuration Guide, NX-OS 4.0 (OL-16598-01, June 2008)

Send comments to [e-mail]
2-19
Nexus 5000 Series Switch Fabric Manager Software Configuration Guide
OL-16598-01
Chapter 2 Installing Cisco Fabric Manager
Running Fabric Manager Behind a Firewall
• Cisco Protocol Analyzer—Enables you to examine actual sequences of Fibre Channel frames easily
using the Fibre Channel and SCSI decoders Cisco developed for Ethereal.
• Cisco Port Analyzer Adapter 2—Encapsulates SPAN traffic (both Fibre Channel control and data
plane traffic) in an Ethernet header for transport to a Windows PC or workstation for analysis. Both
the Cisco Traffic Analyzer and Cisco Protocol Analyzer require the PAA to transport SPAN traffic
to a Windows PC or workstation.
For more information on these tools and how they work together with the Cisco Fabric Manager
management applications, see Chapter 31, “Troubleshooting Your Fabric.”.
Running Fabric Manager Behind a Firewall
For Windows PCs running Fabric Manager, Device Manager, and Performance Manager behind a
firewall, certain ports need to be available.
By default, Fabric Manager Client and Device Manager use the first available UDP port for sending and
receiving SNMP responses. The UDP SNMP trap local ports are 1162 for Fabric Manager, and 1163 or
1164 for Device Manager. Fabric Manager Server also opens TCP RMI port 9099.
You can select the UDP port that Fabric Manager Client or Device Manager uses for SNMP responses
by uncommenting the following statement:
• On a Windows desktop, uncomment the following in the FabricManager.bat or DeviceManager.bat
file in the C:\Program Files\Cisco Systems\MDS9000\bin directory:
rem JVMARGS=%JVMARGS% -Dsnmp.localport=9001
• On a UNIX desktop, uncomment the following in the FabricManager.sh or DeviceManager.sh file
in the $HOME/.cisco_mds9000/bin directory:
# JVMARGS=$JVMARGS -Dsnmp.localport=9001
Fabric Manager Server proxy services uses a configurable TCP port (9198 by default) for SNMP
communications between the Fabric Manager Client or Device Manager and Fabric Manager Server.
The Fabric Manager Server component requires two predictable TCP ports to be opened on the firewall
for an incoming connection:
• server.port = 9099
• server.data.port = 9100
As long as these two ports are open, Fabric Manager Client can connect to the server. Other TCP ports
connected to Fabric Manager Client are initiated by the server, which is behind the firewall.
Table 2-2 lists all ports used by Fabric Manager applications.
Table 2-2 Fabric Manager Port Usage
Communication
Type Port(s) Used
Used by All Applications
SSH Port 22 (TCP)
Telnet Port 23 (TCP)
HTTP Port 80 (TCP)
TFTP Port 69 (UDP)