Physical memory (HTnM-Agent for NAS (when Store database is adopted))
return to main contents page
return to "Management server" contents page
Note
The memory described here is the "virtual memory", which is the combination of the actual memory (the physical memory capacity that is actually required for each product) and the temporary area on the hard disk (the paging files 
or the swap files that are actually required for each product). If enough actual memory cannot be secured, the processing performance might be affected.
During Hitachi Data Ingestor monitoring (see Note 1)
Table 1 Agent for NAS memory requirements provides general estimates of the amount of memory required for Agent for NAS. 
The term, initial conditions, refers to running one instance of Agent for NAS.
Table 1 Agent for NAS memory requirements
Status of Agent for NAS Memory requirements (megabytes)
Windows Server
2008
Windows Server
2012
Linux
Operating under initial conditions a + b a + b a + b
Other than initial conditions (a + b) xn (a + b) xn (a + b) xn
Legend: a: Memory requirement for the jpcagtn process
b: Memory requirement for the jpcsto process
n: Number of instances of the agent
The memory requirement varies depending on the OS. The following table shows the memory requirements for each process.
Table 2 Agent for NAS memory requirements for each process
Process name Memory requirements (megabytes)
Windows Server
2008
Windows Server
2012
Linux
jpcagtn 20 + z 20 + z 180 + z
jpcsto 9 9 180
Legend: z = (a x 15 +b x 19 + c x 21 +d x 4 + e x 17 + 56)/1,024
The following are necessary only when the indicated records are collected:
a: Number of instances of the PD record (see Note 2)
b: Number of instances of the PI_DEVD record (see Note 2)
c: Number of instances of the PD_FSL record (see Note 2)
d: Number of instances of the PD_IAC record (see Note 2)
e: Number of instances of the PD_FSC record (see Note 2)
In the calculated value for z, discard digits below the decimal point.
�@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@
Note 1: Note that the following file servers are collectively called Hitachi Data Ingestor:
- Hitachi Data Ingestor
- Hitachi Capacity Optimization
- Hitachi NAS Platform F1000 Series
- Hitachi Essential NAS Platform
�@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@
�@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@
Note 2: Table 3 Estimating the number of instances for each record (Agent for NAS) describes how to calculate the number of instances for each record.
 If you will be monitoring an existing Hitachi Data Ingestor, you need to consider the NAS system extension when making the estimation.
�@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@
Table 3 Estimating the number of instances for each record (Agent for NAS)
Record name (record ID) Number of instances
System Summary Overview(PI) 1 (because this is a single-instance record)
Device Detail (PI_DEVD) The number of device files used in the file systems in the NAS system
File System Configuration (PD_FSC)
Device Summary(PI_DEVS) 1 (because this is a single-instance record)
Process Detail (PD) 1000 + Number of CIFS client connections
Channel Node Configuration(PD_CHC) 1 (because this is a single-instance record)
Channel Node Platform Configuration(PD_CPC) 1 (because this is a single-instance record)
File System Detail - Local (PD_FSL) Number of file systems in the NAS system
IP Address Configuration (PD_IAC) Number of IP addresses configured in the NAS system
If you will be monitoring an existing NAS system, you can use the command described in Table 4 Commands for confirming the number of NAS system resources to confirm the number of NAS system resources.
Table 4 Commands for confirming the number of NAS system resources
The number of files systems Command
The number of device files in the file systems fslist
The number of files systems fslist
The number of IP addresses configured in the NAS system iflist
During NAS Platform monitoring
Table 5 Agent for NAS memory requirements
Status of Agent for NAS Memory requirements (megabytes)
Windows Server
2008
Windows Server
2012
Linux (RHEL)
Operating under initial conditions a + b + c a + b + c a + b + c
Other than initial conditions (a + b + c) xn (a + b + c) xn (a + b + c) xn
Legend: a: Memory requirement for the jpcagtn process
b: Memory requirement for the jpcsto process
c: Memory requirement for the Java process, which is a command for collecting NAS Platform information (Note: This process is only loaded into memory when it collects information.)
n: Number of instances of the agent
The memory requirement varies depending on the OS. The following table shows the memory requirements for each process.
Table 6 Agent for NAS memory requirements for each process
Process name Memory requirements (megabytes)
Windows Server
2008
Windows Server
2012
Linux
jpcagtn 20 + z 20 + z 180 + z
jpcsto 10 10 180
java 100 #1 100 #1 300 #1
Legend:
z=(a*1+b*2+c*1+d*1+e*1+f*1+g*1+h*8+i*2+6)/1,024
The following parameters are required only when collecting records:
a: Number of PD_HNC record instances#2
b: Number of PD_HEC record instances#2
c: Number of PD_HFSC record instances#2
d: Number of PD_HPLC record instances#2
e: Number of PD_HSDC record instances#2
f: Number of PI_HNS record instances#2
g: Number of PI_HFSS record instances#2
h Number of PI_HNS record instances#2
   This value needs to be calculated if you want to collect the PI_HNCS records.
i: Number of PI_HNS record instances#2
   This value needs to be calculated if you want to collect the PI_HNHS records.
The final value of z is determined by truncating the value after the decimal part.
#1:
The amount of memory area secured for the Java process depends on the heap area size specified by an argument at process startup and on the OS behavior.
The amount of memory actually used by the process in V8.4.1 is about 50 MB in Windows, and about 60 MB in Linux.
However, because the Windows OS secures about 80 MB and Linux OS secures about 250 MB, memory requirements based on these values are indicated as system estimates.
#2:
Table 7 shows how to estimate the number of instances for each record.
To monitor an existing NAS Platform, the estimation must take into account future system expansions.
Table 7 Estimating the number of instances for each record (Agent for NAS)
Record name (record ID) Number of instances
HNAS SMU Configuration(PD_HSMU) 1 (because this is a single-instance record)
HNAS Node Configuration(PD_HNC) Number of nodes in the NAS system
HNAS EVS Configuration(PD_HEC) Number of EVSs in the NAS system
HNAS File System Configuration(PD_HFSC) Number of file systems in the NAS system
HNAS Storage Pool Configuration(PD_HPLC) Number of storage pools in the NAS system
HNAS System Drive Configuration(PD_HSDC) Number of system drives in the NAS system
HNAS Node Summary(PI_HNS) Number of nodes in the NAS system
HNAS File System Summary(PI_HFSS) Number of file systems in the NAS system
If a monitored NAS system exists, you can check the number of resources in the NAS system by executing commands in the system. 
Table 8 lists the commands that you can use to check the number of resources in a NAS system.
Table 8 Commands that you can use to check the number of resources in a NAS system
Number of resources during NAS Platform monitoring Command
Number of nodes in the NAS system cluster-show
Number of EVSs in the NAS system cluster-show
Number of file systems in the NAS system filesystem-list
Number of storage pools in the NAS system span-object-dump
Number of system drives in the NAS system sd-list