Brocade Communications Systems Brocade 8/12c Installation Manual page 12

Brocade network advisor installation guide v11.1x (53-1002320-01, may 2011)
Hide thumbs Also See for Brocade 8/12c:
Table of Contents

Advertisement

Management server and client ports
TABLE 4
Trial and Licensed Version ports (Continued)
Port Number Ports
24610
jboss.jrmp.invoker.port - port 10
24611
jboss.pooled.invoker.port - port 11
24612
jboss.connector.socket.port - port 12
24613
jboss.web.ajp.port - port 13
24614
jboss.web.service.port – port 14
24615
connector.bind.port – port 15
10
55555
Client Export Port
55556
Launch in Context (LIC) client hand
shaking port
1
Port is not configurable (either in the switch or the Management server).
2
Every FTP session requires an additional port which is randomly picked. If the firewall is enabled then FTP operation (used for firmware
download, technical support, firmware import (from client-server) and so on.) will fail.
3
Ports configurable in the switch and the Management server. Port must be the same for all switches managed by the Management
server.
4
Ports used to launch the Web Tools application for Fabric OS switches from the Management client. This is applicable only when the
Fabric OS version is earlier than 6.1.1.
5
Port used for SSL communication. If SSL is enabled, you must open 443*, 24604, and 24605 in the firewall. If SSL is not enabled, port
80* must be open in the firewall and 443*, 24604, and 24605 can be closed. An asterisk (*) denotes the default web server port number.
If you set the web server port number to a port other than the default, you must open that port in the firewall.
6
The Syslog listening port is configurable in the Management server. The switch always sends syslog messages to port 514. If you have
any other syslog daemon on the Management server machine already listening to 514, then the Management Server can be configured
to listen to a different port. You must manually configure relay in existing syslogd to forward the syslog messages to the Management
Server listening on the configured port.
7
Ports used for communicating with M-EOSn (M-i10K) directors. M-i10K always uses NMRU over SSL (2049). M-i10K always uses 8080
for http requests (firmware download, configuration backup/ restore, data collection). If M-EOSn firmware version is less than 9.1 the
Management application uses 8080 for XML-RPC requests (discovery and asset collection). If the M-EOSn firmware version is more
than 9.1 then it always uses SSL port (4430) for XML-RPC.
8
Port must be opened in firewall for the server when the remote ODBC client needs to talk to the Management database server (Only for
EE). The same port is used by the Management server to database server (local). This is not used by the Management client.
9
Ports used for communicating with M-EOS (excluding M-i10K) switches (only required when the Management server manages M-EOS
switches).
10
Port should be opened in firewall in the Management client to allow communication between server and client (only applicable for
M-EOS switches). If this port is not opened in the firewall, then the M-EOS element manager does not receive updates. Also if multiple
clients are opened, it will try to use the next available port (55556). So if there are n clients opened in the same machine then you must
open 55555 (configurable) to 55555 + n ports in the firewall.
11
The Management server tries to find a contiguous block of 16 ports from the starting port configured (for example, 24600); if any port in
this range is not available for the Management application, then you must provide a new starting port. Note that Port 1 to Port 15 in
"Ports" column of the table above are not separately configurable and those ports vary based on the starting port number configuration
(specified as Port 0 in the above table). The port numbers mentioned in the table above are the default ports (for example, when 24600
is selected as the starting port number).
12 of 47
Transport
Description
TCP
RMI/JRMP invoker port
TCP
Pooled invoker port
TCP
Socket invoker port
TCP
AJP 1.3 connector port
TCP
Web service port
TCP
Port to listen for requests on
TCP
Client port to which server
pushes the M-EOS device
Element Manager updates
TCP
Client port used to check if a
Management application client
opened using LIC is running on
the same host
NOTE: If this port is in use, the
application uses the
next available port.
Communication Path Open in Firewall
Client–Server
Client–Server
Server
Server
Server
Server
Server–Client
Client
Brocade Network Advisor Installation Guide
53-1002320-01
Yes
Yes
No
No
No
No
Yes
No

Advertisement

Table of Contents
loading

This manual is also suitable for:

Network advisor 11.1.xBrocade bladesystem 4/24

Table of Contents