B.2 Firewall passage directions
The following tables show the firewall passage directions.
Connection type |
Product at server |
Port number (example) |
Firewall passage direction |
Product at client |
Port number |
---|---|---|---|---|---|
Control connection |
JP1/FTP |
20125/tcp |
<- |
JP1/FTP# |
ANY/tcp |
Data connection |
JP1/FTP |
20124/tcp |
-> |
JP1/FTP# |
ANY/tcp |
Connection type |
Product at server |
Port number (example) |
Firewall passage direction |
Product at client |
Port number |
---|---|---|---|---|---|
Control connection |
JP1/FTP |
20125/tcp |
<- |
JP1/FTP# |
ANY/tcp |
Data connection |
JP1/FTP |
ANY/tcp |
<- |
JP1/FTP# |
ANY/tcp |
- #
-
If the product at the client is not JP1/FTP, the port number depends on that product.
ANY means that an available port number assigned by the OS is to be used. If ftsagentdata is omitted, an unused port number assigned by the OS is used. In these cases, the range of available port numbers depends on the OS.
Table B‒4: Firewall passage directions (Operations-Manager function) Operations-Manager Agent
Firewall passage direction
Operations-Manager Console
Service name
Port number (example)
Port number
ftsagent
20252/tcp
<-
ANY/tcp
ftsagentdata
20364/tcp
<-
ANY/tcp