| Management Server | ||||||||||||
| return to main contents page | ||||||||||||
| return to "Port information" contents
page |
||||||||||||
| Reception ports of Common Component | ||||||||||||
| Reception ports of Device Manager server | ||||||||||||
| Reception ports of Tiered Storage Manager server | ||||||||||||
| Reception ports of Replication Manager server | ||||||||||||
| Reception ports of Tuning Manager server | ||||||||||||
| Reception ports of Global Link Manager server | ||||||||||||
| Reception ports of Command Director server | ||||||||||||
| Reception ports of Compute Systems Manager server | ||||||||||||
| Reception ports of Automation Director server | ||||||||||||
| Reception ports of HTnM-Agent for RAID | ||||||||||||
| Legend: | ||||||||||||
| Y: If you are using a firewall, you might have to register a firewall exception manually depending on the environment. For more information, please refer to the manual for each product. | ||||||||||||
| N: Even if you are using a firewall, registering a firewall exception manually is not required. | ||||||||||||
| Reception ports of Common Component | ||||||||||||
| Port number | Description | Register firewall exception | Originator | |||||||||
| 22015/tcp | Used
for accessing the HBase 64 Storage Mgmt Web Service when communicating with
management clients (GUI). This port number can be changed. This port is also used when SSL is enabled. To interrupt non-SSL communication from outside the network to the management server, you need to edit the user_httpsd.conf file. |
Y | Client | Device
Manager Tiered Storage Manager Replication Manager Tuning Manager Compute Systems Manager Global Link Manager Automation Director |
||||||||
| 22016/tcp | Used for accessing the HBase 64
Storage Mgmt Web Service when performing SSL communication with management
clients (GUI). This port number can be changed. |
Y | Client | Device
Manager Tiered Storage Manager Replication Manager Tuning Manager Compute Systems Manager Global Link Manager Automation Director |
||||||||
| 22017/tcp to 22030/tcp, 22033/tcp, 22034/tcp |
Reserved by Common Component. | N | - | - | ||||||||
| 22031/tcp | Used
internally for Common Component communication (single sign-on). This port number can be changed. This port is used only when Tuning Manager and Device Manager are installed on the same host. |
N | - | - | ||||||||
| 22032/tcp | Used
internally for Common Component communication (HiRDB). This port number can be changed. |
N | - | - | ||||||||
| 22035/tcp | Used
internally for Common Component communication (communication with the Web
server). This port number can be changed. |
N | - | - | ||||||||
| 22036/tcp | Used
internally for Common Component communication (naming service). This port number can be changed. |
N | - | - | ||||||||
| 22037/tcp | Used
internally for Common Component communication (communication with the Web
server). This port number can be changed. |
N | - | - | ||||||||
| 22038/tcp | Used
internally for Common Component communication (communication with the Web
server). This port number can be changed. |
N | - | - | ||||||||
| 22121/tcp | Used
internally for Common Component communication (communication with the Web
server). This port number can be changed. |
N | - | - | ||||||||
| 22122/tcp | Used
internally for Common Component communication (naming service). This port number can be changed. |
N | - | - | ||||||||
| 22123/tcp | Used
internally for Common Component communication (communication with the Web
server). This port number can be changed. |
N | - | - | ||||||||
| 22124/tcp | Used
internally for Common Component communication (communication with the Web
server). This port number can be changed. |
N | - | - | ||||||||
| 22125/tcp | Used
internally for Common Component communication (communication with the Web
server). This port number can be changed. |
N | - | - | ||||||||
| 22126/tcp | Used
internally for Common Component communication (naming service). This port number can be changed. |
N | - | - | ||||||||
| 22127/tcp | Used
internally for Common Component communication (communication with the Web
server). This port number can be changed. |
N | - | - | ||||||||
| 22128/tcp | Used
internally for Common Component communication (communication with the Web
server). This port number can be changed. |
N | - | - | ||||||||
| 22286/tcp | Port
used by the Collection Manager to track login attempts from other components
(Tuning Manager - Main Console, Tuning Manager - Performance Reporter, Device
Manager). |
N | Management server | Collection Manager | ||||||||
| 22613/tcp | This
port is used for internal communication with Hitachi Command Suite Common
Component (for communication with the Web server). This port number can be changed. |
N | Management server | Compute Systems Manager | ||||||||
| 22614/tcp | This
port is used for internal communication with Hitachi Command Suite Common Component (for communication with the Web server). This port number can be changed. |
N | Management server | Compute Systems Manager | ||||||||
| 24231/tcp | RMI
registry port number that HCS TuningManager REST Application Service
uses. |
N | Management server | Tuning Manager | ||||||||
| 24232/tcp | Port
number that server management commands use to communicate with HCS
TuningManager REST Application Service. |
N | Management server | Tuning Manager | ||||||||
| 24233/tcp | Port
number of the stripped-down Web server that HCS TuningManager REST
Application Service uses. |
N | Management server | Tuning Manager | ||||||||
| 24234/tcp | AJP
port of HCS TuningManager REST Application Service. |
N | Management server | Tuning Manager | ||||||||
| Any unused port number |
Port
used to callback Tuning Manager - Performance reporter (GUI) from Collection
Manager. You can set to a fixed arbitrary port by making an entry in the Performance Reporter config.xml file and configuring the Collection Manager settings. |
N | Management server | Collection Manager | ||||||||
| Any unused port number |
Port
used to callback Tuning Manager - Performance reporter (command) from
Collection Manager. You can s[et to a fixed arbitrary port by making an entry in the Performance Reporter config.xml file and configuring the Collection Manager settings. |
N | Management server | Collection Manager | ||||||||
| Reception ports of Device Manager server | ||||||||||||
| Port number | Description | Register firewall exception | Originator | |||||||||
| 162/udp | Used
for receiving SNMP traps from storage systems (VSP G series, VSP F series, Virtual Storage
Platform, Universal Storage
Platform V/VM, Hitachi USP, and HUS VM) and file servers. You cannot change the settings by using Device Manager. If products using these ports are installed on the same computer, change the settings of those products. |
Y | Management and monitoring target | VSP
G series, VSP F series (controller) Virtual Storage Platform Universal Storage Platform V/VM Hitachi USP HUS VM |
||||||||
| 427/tcp | Used for communication with a CIM client (service discovery). You cannot change the settings by using Device Manager. If products using these ports are installed on the same computer, change the settings of those products. | Y | Others | CIM client | ||||||||
| 1024/tcp
to 65535/tcp |
This setting
is required for acquiring performance information such as parity group usage
rate and volume IOPS from a remotely connected Tuning Manager. This port number is used for communication between Device Manager and View Server of Tuning Manager.Register the port number set for the ownPort parameter in the config.xml file and the configforclient.xml file. |
Y | Management server | Tuning Manager | ||||||||
| 2001/tcp | Used
internally for Device Manager server communication, for communication with management
clients (via the GUI or the CLI),
for communication with storage systems, and for communication with hosts
(Device Manager agents and file servers). Note that the Device Manager server
cannot start if this port is being used by another product. You can change
this port number by modifying the server.http.port property in the
server.properties file of the Device Manager server. This port is also used when SSL is enabled. To interrupt non-SSL communication from outside the network to the management server, you need to edit the user_httpsd.conf file. |
Y | Application
Server Client Management and monitoring target |
Normal
host Virtual machine Device Manager GUI or CLI Hitachi Virtual File Platform Hitachi NAS Platform Universal Storage Platform V/VM Hitachi USP |
||||||||
| 2001/tcp | Used for
communication between the Replication Manager and remote Device Manager
server (the value that has been specified for server.http.port in the
server.properties file). If you select HTTP at Protocol the default port number (2001) that the Device Manager server uses for HTTP communication is set. Change the port number only when you want to use a port that is different from the default. |
Y | Management server | Replication Manager | ||||||||
| 2443/tcp | Used
internally for Device Manager server communication, for SSL communication
with management clients (via the GUI or the CLI), and for SSL communication
with storage systems (VSP G series or VSP F series). You can change this port number by modifying the server.https.port property in the server.properties file of the Device Manager server. |
Y | Client | Device Manager GUI or CLI | ||||||||
| 2443/tcp | For
VSP G1000, this setting is required when user accounts are authenticated in
Hitachi Command Suite when logging in to CCI or the SVP. This port number can
be changed. |
Y | Client | VSP
G1000 VSP Gx00 models or VSP Fx00 models (SVP) |
||||||||
| 2443/tcp | Used
for communication between the Replication Manager and remote Device Manager
server (the value that has been specified for server.http.port in the
server.properties file). If you select HTTPS (with SSL) at Protocol the default port number (2443) that the Device Manager server uses for HTTPS communication is set. Change the port number only when you want to use a port that is different from the default. |
Y | Management server | Replication Manager | ||||||||
| 5983/tcp | Used
for receiving event indications from SMI-S providers. You can change this port number by modifying the server.smisclient.indication.port property in the server.properties file of the Device Manager server. |
Y | Others | SMI-S provider | ||||||||
| 5988/tcp | Used for
non-SSL communication with a CIM client (Objectoperation). This port number can be changed. |
Y | Others | CIM client | ||||||||
| 5989/tcp | Used for SSL
communication with a CIM client (Object operation). This port number can be changed. |
Y | Others | CIM client | ||||||||
| 22015/tcp | This setting is required for remotely connecting to Tuning Manager. | Y | Management server | CIM client | ||||||||
| 23055/tcp | Used
internally for Device Manager server communication. You can change this port number by modifying the server.rmi.port property in the server.properties file of the Device Manager server. |
N | - | - | ||||||||
| 23450/tcp to 23453/tcp | Reserved by Device Manager server. | N | - | - | ||||||||
| 24230/tcp | Used
by HiRDB. You can change this port number by using the htmsetup command. This setting is required for remotely connecting to Tuning Manager. This port number can be changed to one in the range from 5001 to 65535. |
Y | Management server | Tuning Manager | ||||||||
| Any/tcp | Used for
communication with View Server of Tuning Manager. By default, any free port numbers are used. You might want to change the setting to use a specific port number if, for example, a firewall is set up between the Tuning Manager management server and the Device Manager server. In such cases, register the port number for the ownPort parameter in the config.xml and configforclient.xml files. |
Y | Management server | Tuning Manager | ||||||||
| Reception ports of Tiered Storage Manager server | ||||||||||||
| Port number | Description | Register firewall exception | Originator | |||||||||
| 20352/tcp | Used
for communication with management clients. You can change the port by modifying the server.rmi.port property in the server.properties file of the Tiered Storage Manager server. |
Y | Client | Tiered Storage Manager CLI | ||||||||
| 24500/tcp | Used
for SSL communication with management clients. You can change the port by modifying the server.rmi.security.port property in the server.properties file of the Tiered Storage Manager server. |
Y | Client | Tiered Storage Manager CLI | ||||||||
| Reception ports of Replication Manager server | ||||||||||||
| Port number | Description | Register firewall exception | Originator | |||||||||
| 25200/tcp | Specify
an RMI registory port number used by Replication Manager for receiving
processing requests (default value: 25200). |
N | Management
server Client |
Device
Manager Replication Manager CLI |
||||||||
| Reception ports of Tuning Manager server | ||||||||||||
| Port number | Description | Register firewall exception | Originator | |||||||||
| 22285/tcp | The
port number used for the Name Server service of the Tuning Manager
server. Configured on all hosts of the Tuning Manager series programs. The Tuning Manager server uses the port number as default port number. After installing the Tuning Manager server, you can change the port numbers for the Tuning Manager server. |
N | - | - | ||||||||
| 22286/tcp | Used
when a user logs in to the Tuning Manager server, or runs Performance
Reporter. This setting is required for acquiring performance information such as parity group usage rate and volume IOPS from a remotely connected Tuning Manager. This port number can be changed. |
Y | Management server | Device Manager | ||||||||
| 22292/tcp | The
Tuning Manager server uses the port number as default port number. After
installing the Tuning Manager server, you can change the port numbers for the
Tuning Manager server. The port number reserved for Tuning Manager series programs. |
N | - | - | ||||||||
| 22350/tcp | The
Tuning Manager server uses the port number as default port number. After
installing the Tuning Manager server, you can change the port numbers for the
Tuning Manager server. The port number used for the Status Server service of the Tuning Manager server and agents. Configured on the Tuning Manager server and agent hosts. |
N | - | - | ||||||||
| 22900/tcp to 22999/tcp |
This
setting is required for remotely connecting to Tuning Manager. |
Y | Management server | Device Manager | ||||||||
| 24231/tcp to 24242/tcp |
Used
internally for Tuning Manager server communication. This port number can be changed. |
N | - | - | ||||||||
| Reception ports of Global Link Manager server | ||||||||||||
| Port number | Description | Register firewall exception | Originator | |||||||||
| 22620/udp | This setting is required if the management host receives SNMP traps. | Y | Application server | Management host | ||||||||
| Reception ports of Command Director server | ||||||||||||
| Port number | Description | Register firewall exception | Originator | |||||||||
| 25015/tcp | Command
Director proxy port for connecting to Tuning Manager. You can connect to HCmD server using HTTP or HTTPS with the server IP address and port information (25015 for HTTP and 25016 for HTTPS). |
Y | Client | Command Director | ||||||||
| 25016/tcp | Tomcat
SSL port. You can connect to HCmD server using HTTP or HTTPS with the server IP address and port information (25015 for HTTP and 25016 for HTTPS). |
Y | Client | Command Director | ||||||||
| 25045/tcp | Service
port on the Host collector that communicates with the HCmD server. |
Y | Management server | Command Director | ||||||||
| 25046/tcp | Service
port on the Host collector that communicates with the HCmD server. |
Y | Management server | Command Director | ||||||||
| 25055/tcp | Service
port on the HCmD HNAS Data Collector that communicates with the HCmD
server. |
Y | Management server | Command Director | ||||||||
| 25065/tcp | Service
port on the HCmD Data Collector that communicates with the HCmD server. |
N | Management server | Command Director | ||||||||
| 25075/tcp | Port
number for Agent for RAID Extension |
Y | Management server | Command Director | ||||||||
| 25076/tcp | Port
number for Agent for RAID Extension |
Y | Management server | Command Director | ||||||||
| Reception ports of Compute Systems Manager server | ||||||||||||
| Port number | Description | Register firewall exception | Originator | |||||||||
| 162/udp | Used
to receive SNMP traps from management clients. If, during installation, you
change the port number to the recommended port number 22601/udp because
162/udp is used by another product, you must add the changed port number to
the exception list. |
Y | Application server | Host Hypervisor |
||||||||
| 22610/tcp | Used
for communication with Hitachi Device Manager. |
Y | Management server | Device Manager | ||||||||
| 22611/tcp | Used for receiving alerts from a Hitachi server. | Y | Others | SVP | ||||||||
| 67/udp | Used
for PXE booting of managed resources. This port number cannot be
changed. |
Y | Management server | Managed server | ||||||||
| 69/udp | Used
for PXE booting of managed resources. This port number cannot be
changed. |
Y | Management server | Managed server | ||||||||
| 80/tcp | This
port is used for internal communication with the IIS service process. This
port number can be changed. If a product other than Deployment Manager is using this port number, the port number to be used by Deployment Manager must be changed. |
Y | - | - | ||||||||
| 4011/udp | Used
for PXE booting of managed resources. This port number cannot be
changed. |
Y | Management server | Managed server | ||||||||
| 26500/tcp | This
port is used for internal communication between the IIS service process and
Deployment Manager. This port number can be changed. If a product other than Deployment Manager is using this port number, the port number to be used by Deployment Manager must be changed. |
Y | - | - | ||||||||
| 26501/tcp or 56020/tcp | Used
for restoration and backup of managed resource disks. The default is
26501/tcp. This port number can be changed. If an attempt to change this port
number fails, the system uses the default (56020/tcp). If a product other than Deployment Manager is using this port number, the port number to be used by Deployment Manager must be changed. |
Y | Management server | Managed server | ||||||||
| 26502/tcp or 56022/tcp |
Used
for PXE booting of managed resources. The default is 26502/tcp. This port
number can be changed. If an attempt to change this port number fails, the
system uses the default (56022/tcp). If a product other than Deployment Manager is using this port number, the port number to be used by Deployment Manager must be changed. |
Y | Management server | Managed server | ||||||||
| 26503/tcp or 56030/tcp | Used
for PXE booting of managed resources. The default is 26503/tcp. This port
number can be changed. If an attempt to change this port number fails, the
system uses the default (56030/tcp). If a product other than Deployment Manager is using this port number, the port number to be used by Deployment Manager must be changed. |
Y | Management server | Managed server | ||||||||
| 26504/tcp |
Used for deployment manager internal processing. | Y | Management server | Managed server | ||||||||
| 26505/tcp |
Used for deployment manager internal processing. | Y | Management server | Managed server | ||||||||
| 26506/tcp | Used for deployment manager internal processing. | Y | Management server | Managed server | ||||||||
| 26507/tcp |
Used for deployment manager internal processing. | Y | Management server | Managed server | ||||||||
| 26508/tcp or 56023/tcp | Used
for performing deployment operations on managed resources. The default is
26508/tcp. This port number can be changed. If an attempt to change this port
number fails, the system uses the default (56023/tcp). If a product other than Deployment Manager is using this port number, the port number to be used by Deployment Manager must be changed. |
Y | Management server | Managed server | ||||||||
| 56011/tcp |
These
ports are reserved. |
Y | - | - | ||||||||
| 56024/tcp |
These
ports are reserved. |
Y | - | - | ||||||||
| 56028/tcp |
These
ports are reserved. |
Y | - | - | ||||||||
| 56060/tcp | These
ports are reserved. |
Y | - | - | ||||||||
| Reception ports of Automation Director server | ||||||||||||
| Port number | Description | Register firewall exception | Originator | |||||||||
| 22/tcp | Used
for SSH. cjstartweb uses this port. |
Y | Management and monitoring target | Server | ||||||||
| 23/tcp | Used
for Telnet. cjstartweb uses this port. |
Y | Management and monitoring target | Server | ||||||||
| 135/tcp and 139/tcp |
Used
in shared management. cjstartweb uses this port. |
Y | Management and monitoring target | Server | ||||||||
| 445/tcp or udp |
Used
in shared management. cjstartweb uses this port. |
Y | Management and monitoring target | Server | ||||||||
| 20240/tcp | Task processing engine uses this port. | N | - | - | ||||||||
| 20241/tcp | Task processing engine uses this port. | N | - | - | ||||||||
| 20242/tcp | Task processing engine uses this port. | N | - | - | ||||||||
| 20243/tcp | Task processing engine uses this port. | N | - | - | ||||||||
| 20245/tcp | Task processing engine uses this port. | N | - | - | ||||||||
| 22250/tcp | Task processing engine uses this port. | N | - | - | ||||||||
| 23031/tcp | Use
to access the followingservices: - HBase Storage Mgmt Web SSO Service - HSSO-dedicated Web server cjstartweb uses this port. |
Y | - | - | ||||||||
| 23160/tcp | Task processing engine uses this port. | N | - | - | ||||||||
| 23800/tcp | Task processing engine uses this port. | N | - | - | ||||||||
| Reception ports of Configuration Manager REST API server | ||||||||||||
| Port number | Description | Register firewall exception | Originator | |||||||||
| 4369/tcp | Used internally for Configuration Manager REST API server communication in Windows. | N | - | - | ||||||||
| 23450/tcp | Used
for HTTP communications from REST clients to the REST server. This port number can be changed. |
N | Client | REST API | ||||||||
| 23451/tcp | Used
for HTTPS communications from REST clients to the REST server. This port number can be changed. |
N | Client | REST API | ||||||||
| 23452/tcp to 23453/tcp | Used
for the internal communication of the REST server. This port number can be changed. |
N | - | - | ||||||||
| 23455/tcp | Used internally for Configuration Manager REST API server communication in Linux. | N | - | - | ||||||||
| 23458/tcp to 23459/tcp | Used internally for Configuration Manager REST API server communication. | N | - | - | ||||||||
| 35049 to 36047/udp | Used for communication from CCI to the storage system. | N | Management server | CCI | ||||||||
| 37001/udp to 38000/udp | Used
for CCI in the REST API server to communicate to storage systems. This port number can be changed. |
N | Management server | REST API | ||||||||
| Reception ports of HTnM-Agent for RAID | ||||||||||||
| This table explains the port numbers for HTnM - Agent for RAID when using the Tuning Manager API. For details on the port numbers that are used for communication between Collection Manager and Tuning Manager Agent, see the sheet "Tuning Manager Agents". | ||||||||||||
| Port number | Description | Register firewall exception | Originator | |||||||||
| 24221/tcp | Access port for Tuning Manager - Agent REST Web Service for non-SSL communication. | Y | Management server | Tuning Manager# | ||||||||
| 24222/tcp | Access port for Tuning Manager - Agent REST Web Service for SSL communication. | Y | Management server | Tuning Manager# | ||||||||
| #: | ||||||||||||
| Device Manager uses this port only if it is remotely connected to the Tuning Manager and if it is using the Alert Function of Tuning Manager. | ||||||||||||