| Tuning
Manager Agents |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| return to main
contents page |
|
|
|
|
|
return to "Port information" contents
page
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Port
numbers to use for communication between Collection Manager and the Agent |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Direction of traffic
through a firewall |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Port
numbers used when monitoring a storage system |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Port numbers to use
when monitoring switches |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Port
numbers for communication between Agent for NAS and the NAS system |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Passing
traffic through a firewall during storage system monitoring |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Passing
traffic through a firewall when monitoring switches |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Passing
traffic through a firewall between Agent for NAS and the NAS system |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Notes
on using Collection Manager or an Agent when the Windows Firewall is enabled |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Port
numbers to use for communication between Collection Manager and the Agent |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| The
following table lists the port numbers used for Collection Manager and the
Agent. In the default settings, each time a service other than the Name
Server service, |
|
|
|
|
|
|
|
|
|
|
|
|
|
| the
View Server service (between Main Console and the View Server service, and
between Performance Reporter and the View Server service), |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| or
the Status Server service is started, the service automatically uses a port
number not being used by the system. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| The
jpcnsconfig port command can be used to fix the port numbers used by the
system. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Port
numbers to use for communication between Collection Manager and the Agent |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Service name |
Parameter |
Port
number |
Purpose |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Name Server service |
jp1pcnsvr |
22285(*7) |
Used
when a service establishes a communications connection to the Name Server. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NNM Object Manager service |
jp1pcovsvr |
22292(*6) |
The
port reserved for Tuning Manager series programs. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Master Manager service |
jp1pcmm |
20271(*1)(*7) |
Used
when a service establishes a communications connection to the Master Manager. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Master Store service |
jp1pcsto |
20272(*1)(*7)
|
Used
when an Agent records an event. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Correlator service |
jp1pcep |
20273(*1)(*7)
|
Used
when an Agent sends an event to the Tuning Manager server. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Trap Generator service |
jp1pctrap |
20274(*1)(*7) |
Used
when the Trap Generator service sends an SNMP trap |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| View Server service (used when an Agent sends an
event and a report to Performance Reporter) |
jp1pcvsvr2 |
20276(*1)(*7) |
Used
when an Agent sends an event and a report to Performance Reporter. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| View service (between Main Console and View
Server service, and between Performance Reporter and the View Server service) |
jp1pcvsvr |
22286(*7) |
Used
when a user logs in to the Tuning Manager server, or runs Performance
Reporter. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent Collector service (for a health check agent) |
jp1pcagt0 |
Automaticallyassigned(*2)(*7) |
Used
when the Agent Collector service binds an alarm, or obtains a real-time
report. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent Store service (for a health check agent) |
jp1pcsto0 |
Automatically
assigned(*2)(*7) |
Used
when the Agent Store service records performance data, or obtains a
historical report. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Status Server service |
jp1pcstatsvr |
22350 |
Used
when a user checks the status of a service. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Action Handler service |
jp1pcah |
20275(*1)(*8) |
Used
when the Action Handler service executes an action. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent Store service |
jp1pcstox[nnn](*3)(*4) |
Not
applicable(*5) |
Used
when the Agent Store service records performance data, or obtains a
historical report. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent Collector service |
jp1pcagtx[nnn(*3)(*4) ] |
Used
when the Agent Collector service binds an alarm, or obtains a real-time
report. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| (*1) The jpcnsconfig
port command displays this port number as a
default value. You can change this default setting to a desired number. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| (*2) The jpcnsconfig
port command takes all available ports and
automatically assigns them and then displays them. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Aside from the jpcnsconfig port command, ports are also automatically
assigned whenever services are restarted. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| (*3) x indicates the product ID of the
Agent. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| (*4) When multiple instances of the
service are created, a sequential number (nnn) is appended to the second and subsequent instances. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The first instance does not have a sequential number. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| (*5) When you set a port number by
executing the jpcnsconfig port command for the first time after an instance registration, a
port number not being used by the system is displayed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You can change the displayed port number to a desired number. Once you
set a port number by executing the jpcnsconfig port command, this number will
be maintained unless changed. |
|
|
|
|
|
|
|
|
|
|
|
|
| (*6) The jpcnsconfig
port command displays this port number as a
default value only when Collection Manager is installed on Windows Server
2003, Solaris (SPARC), or HP-UX. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| (*7) This port number is also used by
the service when Collection Manager runs in a logical host environment. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| (*8) When a Tuning Manager series
program logical host environment is used on a host on which the Collection
Manager runs, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| the
Action Handler service employs port numbers for communication in both
physical and logical environment. You can specify a port based on environment
requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Direction of traffic through a
firewall |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If
you want to establish a firewall between Collection Manager and Agent, you
must set fixed port numbers for all Collection Manager and Agent
services. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| In
order to allow services to pass traffic through a firewall, you must use port
numbers that comply with the directions shown in the following table. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Single
arrow in the “Traffic Direction” column indicates the direction from which
communications begin. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Dual
arrows indicate that communications can be initiated from either a Tuning
Manager server host or Agent host. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| The
following table describes the directions of traffic through a firewall
between Collection Manager and an Agent. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Directions
of traffic through a firewall between Collection Manager and the Agent
Service name Parameter Passage directions |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Service name |
Parameter |
Passage
directions |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Name Server service |
jp1pcnsvr |
Tuning
Manager server host <--Agent host |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Master Manager service |
jp1pcmm |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Master Store service |
jp1pcsto |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Correlator service |
jp1pcep |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Trap Generator service |
jp1pctrap |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| View Server service |
jp1pcvsvr2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent Collector service (for a health check agent) |
jp1pcagt0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent Store service (for a health check agent) |
jp1pcsto0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Status Server service |
jp1pcstatsvr |
Tuning
Manager server host <-->Agent host |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Action Handler service |
jp1pcah |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent Store service |
jp1pcstox [nnn](*1)(*2) |
Agent host <-- Tuning Manager server host |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent Collector service |
jp1pcagtx[nnn](*1)(*2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| (*1) x indicates
the product ID of the Agent. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| (*2)
When creating multiple instances, an ascending number (nnn) will be appended to the instances created after the first
time. No number will be appended to the instance created first. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| The
side establishing the connection uses a free port number allocated by the OS
as the transmission port. The port numbers used here might differ depending
on the OS. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| To
execute the jpcctrl dump command
or the jpcctrl list command
at an Agent host, execute the command by one of the following methods: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
• Specifying the proxy
option of the jpcctrl dump command
or the jpcctrl list command
so that communications are performed through the Tuning Manager server. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For details about the proxy option of
the jpcctrl dump and jpcctrl list commands, see the Tuning Manager CLI Reference Guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
• Setting port numbers
so that connections can be initiated between Agent hosts (Agent host
<--> Agent host), and traffic can pass through the firewall: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Action Handler service (jp1pcah parameter) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Status Server service (jp1pcstatsvr parameter) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Agent Store service (jp1pcstox [nnn]
parameter) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Agent Collector service (jp1pcagtx
[nnn] parameter) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Note:
x indicates the product ID
of the Agent. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| For
Agent Store and Agent Collector: When multiple instances of the service are
created, a sequential number (nnn) is appended to the second and subsequent instances. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| The
first instance does not have a sequential number. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Port numbers used
when monitoring a storage system |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| The
following describes the port numbers used when monitoring a storage system: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
• When monitoring the
Hitachi HUS100/AMS2000 or Hitachi SMS series: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Agent for RAID uses port numbers that
are not already in use by the system. The Hitachi HUS100/AMS2000 and SMS
series use the following default port numbers. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
These port numbers can, however, be
changed (see Note). |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- When using secure communications—28355 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- When not using secure communications—2000 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
• When monitoring the
Hitachi HUS/AMS/WMS series or Thunder 9500V series: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Agent for RAID uses port numbers that
are not already in use by the system. The Hitachi HUS/AMS/WMS and Thunder
9500V series use the port number 2000 by default. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
These port numbers can, however, be
changed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To change the default port number of
the Hitachi HUS100/ AMS2000/AMS/WMS/SMS or Thunder 9500V series, you must
specify a new port number in the services file, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
which is located on the host that
Agent for RAID is installed on. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you start Agent for RAID without
specifying the new port number in the file, Agent for RAID will not collect
any data. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For details about how to check port
numbers used by a storage system, and how to change port numbers, see the
manual for your storage system. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
• When monitoring the
Hitachi Virtual Storage Platform G1000, Virtual Storage Platform, Hitachi
Unified Storage VM, Universal Storage Platform V/VM series, or Hitachi USP: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Agent for RAID uses a Fibre Channel network or Fibre Channel
over Ethernet (FCoE) to access a storage system. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Therefore, you do
not need to specify port numbers when monitoring a storage system. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Port numbers to use when
monitoring switches |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| The
following describes the port numbers to use when monitoring switches: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
• Brocade switches using
DCFM SMI Agent or Network Advisor SMI Agent Port number used between Agent
for SAN Switch and DCFM SMI Agent, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
or between Agent for SAN Switch and
Network Advisor SMI Agent ¢ DCFM SMI Agent uses the port number set in DCFM
SMI Agent. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The default HTTP and HTTPS port
numbers are 5988, and 5989 respectively. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Network Advisor SMI Agent uses the port number set in
Network Advisor SMI Agent. The default HTTP and HTTPS port numbers are 5988,
and 5989 respectively. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
• Brocade B-Model
switches using SMI Agent for FOS |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Port numbers for communication between Agent for SAN Switch
and SMI Agent for FOS: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Agent for SAN Switch uses
port numbers that are not already in use by the system. The SMI Agent for FOS
uses the port number that has been set for it. The default port number is
5988. |
|
|
|
|
|
|
|
|
|
|
|
|
|
- Port numbers for communication between the SMI Agent for FOS
and the proxy switch: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The SMI Agent for FOS uses
port numbers that are not already in use by the system. The proxy switch uses
the fixed port numbers 111, 897 and 898. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
• Cisco switches using
Cisco DCNM-SAN SMI-S Agent |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Port numbers used for
communication between Agent for SAN Switch and DCNM-SAN SMI-S Agent: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Agent for SAN Switch uses port
numbers that are not already in use by the system. DCNM-SAN SMI-S Agent uses
port number 5988 for HTTP communication and 5989 for HTTPS communication. |
|
|
|
|
|
|
|
|
|
|
|
|
|
• Cisco switches using
Cisco Seed Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Port numbers used for
communication between Agent for SAN Switch and Seed Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Agent for SAN Switch uses port
numbers that are not already in use by the system. Seed switch uses port
number 5988 for HTTP communication and 5989 for HTTPS communication. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Port
numbers for communication between Agent for NAS and the NAS system |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent
for NAS uses port numbers that are not already in use by the system. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
When monitoring Hitachi
Capacity Optimization, Hitachi Data Ingestor, Hitachi NAS Platform F1000
Series, or Hitachi Essential NAS Platform |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The port number 20265 is
reserved in the NAS system. You cannot change this port number. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
When monitoring Hitachi
NAS Platform |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The port number 22 is
reserved in the SMU. You cannot change this port number. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Passing
traffic through a firewall during storage system monitoring |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Set
up the firewall between Agent for RAID and the storage system to allow
traffic to pass through the temporary port used by Agent for RAID. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
When monitoring the
Hitachi HUS100/AMS2000/AMS/WMS/SMS series or Thunder 9500V series |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If a firewall is set up
between Agent for RAID and the Hitachi HUS100/AMS2000/AMS/WMS/SMS series, or
Thunder 9500V series, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
you need to specify
settings as described below to enable traffic to pass through the firewall. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
• For Agent for RAID |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You cannot use a port number for
traffic through the firewall. Make sure that you set an IP address instead. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
• For the Hitachi
HUS100/AMS2000/AMS/WMS/SMS series, or Thunder 9500V series |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Set the IP address and the port
number to be used for traffic through the firewall. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Passing
traffic through a firewall when monitoring switches |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If
a firewall is set up between Agent for SAN Switch and a required product, use
the settings in the following table for passing traffic through a firewall. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Settings
for passing traffic through a firewall when monitoring switches |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Target |
Directions of traffic through a firewall |
Settings for passing traffic through a firewall |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Target |
Setup
Item |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Brocade
(Network Advisor SMI Agent) (HTTP and HTTPS communication) |
Network Advisor SMI Agent <- Agent |
Network
Advisor SMI Agent |
Network
Advisor SMI Agent port number |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent |
Network
Advisor SMI Agent IP address* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Brocade
(DCFM SMI Agent) (HTTP and HTTPS communication) |
DCFM SMI Agent <-Agent |
DCFM
SMI Agent |
DCFM
SMI Agent port number |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent |
DCFM
SMI Agent IP address* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Brocade
(SMI Agent for FOS) |
SMI Agent for FOS<- Agent |
SMI
Agent for FOS |
Agent
IP address* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent |
SMI
Agent for FOS IP address* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Proxy Switch <- SMIAgent for
FOS |
Proxy
Switch |
SMI
Agent for FOS IP address* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SMI Agent for FOS |
Proxy
Switch IP address* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Cisco
Seed Switch (HTTP and HTTPS communication) |
Seed Switch <-Agent |
Seed
Switch |
Seed
Switch port number (HTTP:5988/HTTPS:5989) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent |
Seed
Switch IP address* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Cisco
DCNM-SAN SMI-S Agent (HTTP and HTTPS communication) |
DCNM SAN SMI-S Agent <- Agent |
DCNM-SAN
SMI-S Agent |
DCNM-SAN
SMI-S Agent port number (HTTP: 5988/HTTPS: 5989) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent |
DCNM
SAN SMI-S Agent IP address* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Legend: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Agent: A host on which
Agent for SAN Switch is installed |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<-: The direction in
which transmission (connection establishment) is started, from right to left |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* You cannot use a port
number to enable communication through a firewall. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Passing
traffic through a firewall between Agent for NAS and the NAS system |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If
a firewall is set up between Agent for NAS and the NAS system, on the Agent
side you cannot use a port number to pass traffic through the firewall. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Firewall
transit settings when monitoring Hitachi Capacity Optimization, Hitachi Data
Ingestor, Hitachi NAS Platform F1000 Series, or Hitachi Essential NAS
Platform |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Direction |
Source IP address |
Destination IPaddress |
Source port |
Destination port |
Protocol |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent for NAS ->NAS system |
IP
address of the Agent for NAS host |
IP
address of the NAS system |
any |
20265 |
TCP |
|
|
|
|
|
|
|
|
|
|
|
|
| NAS system ->Agent for NAS |
IP
address of the NAS system |
IP
address of the Agent for NAS host |
20265 |
any
port |
TCP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Firewall
transit settings when monitoring Hitachi NAS Platform |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Direction |
Source IP address |
Destination IPaddress |
Source port |
Destination port |
Protocol |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent for NAS ->SMU |
IP
address of the Agent for NAS host |
IP
address of the SMU |
any |
22 |
TCP |
|
|
|
|
|
|
|
|
|
|
|
|
| SMU ->Agent for NAS |
IP
address of the SMU |
IP
address of the Agent for NAS host |
22 |
any
port |
TCP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Notes
on using Collection Manager or an Agent when the Windows Firewall is enabled |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Collection Manager |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The port numbers used by
the services indicated in the following table must be added to the Windows
Firewall exceptions list. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Services of Collection
Manager |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Service name |
Parameter |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Name Server
service |
jp1pcnsvr |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Master
Manager service |
jp1pcmm |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Master
Store service |
jp1pcsto |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Correlator
service |
jp1pcep |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Trap
Generator service |
jp1pctrap |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The View Server
service |
jp1pcvsvr2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The View Server
service (between Performance Reporter and the View Server service) |
jp1pcvsvr |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Action
Handler service |
jp1pcah |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Status
Server service |
jp1pcstatsvr
* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* If the status
management function is enabled, the port number used by this service must be
added to the Windows Firewall exceptions list. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent for RAID |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The port numbers used by
the services indicated in the following table must be added to the Windows
Firewall exceptions list. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Services of Agent for RAID |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Service name |
Parameter |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Action
Handler service |
jp1pcah |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Agent Store
service |
jp1pcstod[nnn](*1) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Agent
Collector service |
jp1pcagtd[nnn](*1) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Status
Server service |
jp1pcstatsvr(*2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(*1) A port number must be added for each created instance. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If multiple instances have been created, a sequence number
(nnn) is appended to the second and later instances. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A sequence number is not appended to the first created
instance. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(*2) If the status management function is enabled, the port number
used by this service must be added to the Windows Firewall exceptions list. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent for RAID Map and Agent for
Platform (Windows) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The port numbers used by
the services indicated in the following table must be added to the Windows
Firewall exceptions list. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Services of Agent for
RAID Map and Agent for Platform (Windows) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Service name |
Parameter |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Action
Handler service |
jp1pcah |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Agent Store
service |
jp1pcstot |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
jp1pcstoe |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Agent
Collector service |
jp1pcagtt |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
jp1pcagte |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Status
Server service |
jp1pcstatsvr(*1) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(*1) If the status management function is enabled, the port number
used by this service must be added to the Windows Firewall exceptions list. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent for SAN Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The port numbers used by
the services indicated in the following table must be added to the Windows
Firewall exceptions list. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Services of Agent for SAN
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Service name |
Parameter |
Program |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Action
Handler service |
jp1pcah |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Agent Store
service |
jp1pcstow[nnn](*1) |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Agent
Collector service |
jp1pcagtw[nnn](*1) |
jpcagtw.exe |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Status
Server service |
jp1pcstatsvr(*2) |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(*1) A port number must be added for each created instance. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If multiple
instances have been created, a sequence number (nnn) is appended to the
second and later instances. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A sequence number
is not appended to the first created instance. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(*2) If the status management function is enabled, the port number
used by this service must be added to the Windows Firewall exceptions
list.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent for NAS |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The port numbers used by
the services indicated in the following table must be added to the Windows
Firewall exceptions list. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Services of Agent for NAS |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Service name |
Parameter |
Program |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Action
Handler service |
jp1pcah |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Agent Store
service |
jp1pcston[nnn](*1) |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Agent
Collector service |
jp1pcagtn[nnn](*1) |
jpcagtn.exe |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Status
Server service |
jp1pcstatsvr(*2) |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(*1) A port number must be added for each created instance. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If multiple
instances have been created, a sequence number (nnn) is appended to the
second and later instances. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A
sequence number is not appended to the first created instance. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(*2) If the status management function is enabled, the port number
used by this service must be added to the Windows Firewall exceptions list. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent for Oracle |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The port numbers used by
the services indicated in the following table must be added to the Windows
Firewall exceptions list. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Services of Agent for Oracle |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Service name |
Parameter |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Action
Handler service |
jp1pcah |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Agent Store
service |
jp1pcstoo[nnn](*1) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Agent
Collector service |
jp1pcagto[nnn](*1) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Status
Server service |
jp1pcstatsvr(*2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(*1) A port number must be added for each created instance. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If
multipleinstances have been created, a sequence number (nnn) is appended to
the second and later instances. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A
sequence number is not appended to the first created instance. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(*2) If the status management function is enabled, the port number
used by this service must be added to the Windows Firewall exceptions list. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent for Microsoft SQL Server |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The port numbers used by
the services indicated in the following table must be added to the Windows
Firewall exceptions list. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Services of Agent for
Microsoft SQL Server |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Service name |
Parameter |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Action
Handler service |
jp1pcah |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Agent Store
service |
jp1pcstoq[nnn](*1) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Agent
Collector service |
jp1pcagtq[nnn](*1) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Status
Server service |
jp1pcstatsvr(*2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(*1) A port number must be added for each created instance. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If multiple instances have been created, a sequence number (nnn) is
appended to List of port numbers the second and later instances. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A sequence number is not appended to the first created instance. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(*2) If the status management function is enabled, the port number
used by this service must be added to the Windows Firewall exceptions list. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Agent for Microsoft Exchange
Server |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The port numbers used by
the services indicated in the following table must be added to the Windows
Firewall exceptions list. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Services of Agent for
Microsoft Exchange Server |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Service name |
Parameter |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Action Handler
service |
jp1pcah |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Agent Store
service |
jp1pcstoz |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Agent Collector
service |
jp1pcagtz |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Status Server
service |
jp1pcstatsvr(*1) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(*1) This needs to be registered when the status management
function is enabled. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|