9.7.2 Importing management information of IM Configuration Management
If necessary, you can edit the management information of IM Configuration Management that has been output (exported) from a host, and you can input (import) the edited information onto a different host. You use the jcfimport command for the import operation, but you cannot import collected host information.
Since importing will change the data held by IM Configuration Management, we recommend that you back up the data before executing the import operation.
This subsection explains the system configuration information that is imported by the jcfimport command. For details about how to apply the imported management information of IM Configuration Management to a system, see 9.7.3 Applying the imported management information of IM Configuration Management to a system.
For details about the jcfimport command, see jcfimport in Chapter 1. Commands of the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
- Organization of this subsection
(1) Host information
In the case of manually-entered information, the content of the export file (host_input_data.csv) is imported.
The table below shows the items that are imported from the export file (host_input_data.csv) for manually-entered information, and the input range for each item.
Item |
Input range |
Required/Optional |
Default |
---|---|---|---|
Host |
A character string of up to 255 bytes may be input. Permitted characters are alphanumeric characters, periods (.) and the hyphen (-), excluding control codes. |
Required#1 |
-- |
IP address |
Permitted characters are alphanumeric characters, periods (.), and colons (;). Control codes are not permitted. |
Optional |
Blank |
Host name list |
Host names can be input. Permitted characters are alphanumeric characters periods (.) and the hyphen (-), excluding control codes. |
Optional |
Blank |
Comment |
A character string of up to 80 bytes may be input. |
Optional |
Blank |
Host type |
You can input one of the following:
|
Optional |
physical |
Active host |
A character string of up to 255 bytes may be input. Permitted characters are alphanumeric characters periods (.) and the hyphen (-), excluding control codes. |
Optional |
Blank |
Standby host |
Host names can be input. For each host name, a character string of up to 255 bytes may be input. Permitted characters are alphanumeric characters periods (.) and the hyphen (-), excluding control codes. |
Optional |
Blank |
VMM host |
A character string of up to 255 bytes can be input. Permitted characters are alphanumeric characters periods (.) and the hyphen (-), excluding control codes. |
Optional |
Blank |
Virtual manager type |
One of the following can be input. This item is not case sensitive.
|
Optional |
Blank |
User name |
A character string of up to 255 bytes can be input. Permitted characters are alphanumeric characters other than control codes. |
Optional |
Blank |
Password#4 |
A character string of up to 255 bytes can be input. Permitted characters are alphanumeric characters other than control codes. |
Optional |
Blank |
Domain name#5 |
A character string of up to 255 bytes can be input. Permitted characters are alphanumeric characters other than control codes. |
Optional |
Blank |
Communication type#6 |
Either http, https, or ssh can be input. This item is not case sensitive. Which communication types you can specify depends on the virtual manager type:
|
Optional |
|
Port number#7 |
A numeric value from 1 to 65535 can be entered. |
Optional |
|
Private key file name#8 |
A character string of up to 256 bytes can be input. This item is case sensitive. Permitted characters are alphanumeric characters other than control codes. |
Optional |
Blank |
Virtualization management former host name |
A character string of up to 255 bytes can be input. Permitted characters are alphanumeric characters, periods (.) and hyphens (-). Control codes are not permitted. |
Optional |
Blank |
Remote communication type |
This item can be used for remote monitoring. You can input one of the following:
|
Optional |
disable |
Authentication information category#9 |
This item can be used for remote monitoring. You can input one of the following:
|
Optional |
Blank |
If characters that do not have code compatibility or model-dependent characters are used in the host information, these characters may become garbled when they are imported.
If any of the conditions listed below applies to the export file (host_input_data.csv) for manually-entered information, an error occurs and the file is not imported.
-
A host name is duplicated.
-
A host name is longer than 255 bytes.
-
The number of hosts exceeds the number supported (1,024 if the IM database size is S or M, and 10,000 if the size is L).
-
A value outside the permitted input range is specified.
-
The number of input data columns is insufficient (the number of commas is insufficient).
-
The host name described for the active host, standby host, or VMM host does not exist in the host information file.
-
A value other than physical or virtual is specified as the host type for the active host or standby host.
-
A value other than physical is specified as the host type for the VMM host.
-
A value other than physical, logical, virtual, or unknown is specified as a host type.
-
A value other than ESX, Hyper-V, KVM, Virtage, vCenter, JP1/SC/CM, SCVMM, vCenter, or Virtage is specified as the virtual manager type.
-
The virtual manager type is specified as a host with type logical or unknown.
-
The host name described for the virtualization management former source host name does not exist in the host information file.
-
A value other than physical or virtual is specified as the host type described for the virtualization management former source host name.
-
A value other than SCVMM is specified as the virtual manager type of a host for which a domain name is set.
-
A value other than vCenter, HCSM, or KVM is specified as the virtual manager type of a host for which a communication type is specified.
-
A character string other than https or http is specified as the communication type of a host whose virtual manager type is vCenter.
-
A character string other than http is specified as the communication type of a host whose virtual manager type is HCSM.
-
A character string other than ssh is specified as the communication type of a host whose virtual manager type is KVM.
-
The virtual system configuration information does not correspond to the information in the following table.
Host type
Virtual manager type
Configuration information corresponding to virtual manager type
Required/Optional
Remarks
Physical host
--
N
--
--
vCenter
Virtual management former host name
Optional
SCVMM is specified as the virtual management former host name.
User name
Optional
Password
Optional
Communication type
Optional
JP1/SC/CM
N
--
--
SCVMM
User name
Optional
--
Password
Optional
Domain name
Optional
HCSM
User name
Optional
--
Password
Optional
Port number
Optional
Communication type
Optional
ESX
Virtual management former host name
Optional
vCenter is specified as the virtual management former host name.
Hyper-V
Virtual management former host name
Optional
SCVMM is specified as the virtual management former host name.
KVM
User name
Optional
--
Port number
Optional
Private key file name
Required
Communication type
Optional
Virtage
Virtual management former host name
Optional
JP1/SC/CM or HCSM is specified as the virtual management former host name.
Virtual host
--
VMM host name
Required
A value other than vCenter, JP1/SC/CM, SCVMM, or HCSM is specified as the VMM host name.
vCenter
VMM host name
Required
A value other than vCenter, JP1/SC/CM, SCVMM, or HCSM is specified as the VMM host name.
SCVMM is specified as the virtual management former host name.
Virtual management former host name
Optional
User name
Optional
Password
Optional
Communication type
Optional
JP1/SC/CM
VMM host name
Required
A value other than vCenter, JP1/SC/CM, SCVMM, or HCSM is specified as the VMM host name.
SCVMM
VMM host name
Required
A value other than vCenter, JP1/SC/CM, SCVMM, or HCSM is specified as the VMM host name.
User name
Optional
Password
Optional
Domain name
Optional
HCSM
VMM host name
Required
A value other than vCenter, JP1/SC/CM, SCVMM, or HCSM is specified as the VMM host name.
User name
Optional
Password
Optional
Port number
Optional
Communication type
Optional
KVM
VMM host name
Required
A value other than vCenter, JP1/SC/CM, SCVMM, or HCSM is specified as the VMM host name.
User name
Optional
Port number
Optional
Private key file name
Optional
Communication type
Optional
Logical host
--
N
--
--
Unknown
--
N
--
--
-
A value other than disable, ssh, or wmi is specified as the remote communication type.
-
A value other than common, host, or a blank is specified as the authentication information category.
-
When ssh or wmi is specified as the remote communication type, a blank is specified for the authentication information category.
If a host has the same host name as the import destination host, that host is not registered in IM Configuration Management as a managed host after the export file (host_input_data.csv) for manually-entered information has been imported.
(2) System hierarchy information
The content of the export file for the system hierarchy information is imported. The export file differs according to the system monitoring method:
-
Agent monitoring
-
Remote monitoring
(a) Configuration information for agent monitoring
The name of the file to which the configuration information for agent monitoring is exported is system_tree_information.txt.
If any of the conditions listed below applies to the content of the export file for the configuration information for agent monitoring, an error occurs and the file is not imported.
-
The same host is described on multiple lines (the managed host has multiple higher hosts).
-
The host configuration is looped.
-
The host name specified for the managing host is not enclosed in square brackets [ ] (] is missing).
-
No host name is specified for the managing host.
-
More than 10,000 hosts are defined.
-
The local host is defined as the managed host.
After the export file (host_input_data.csv) for host information (manually-entered information) or the export file for the configuration information for agent monitoring is edited, the host name specified in the export file for the configuration information for agent monitoring might not be specified in the export file for the host information (manually-entered information) in some cases. In those cases, after the export file for the configuration information for agent monitoring is imported, an import warning message is displayed and the undefined host is automatically registered in IM Configuration Management as a managed host.
When you are trying to import the configuration information for agent monitoring, if the export file for the configuration information for agent monitoring is not found in the specified directory, an error message is displayed and the import operation is halted.
(b) Configuration information for remote monitoring
The name of the file to which the configuration information for remote monitoring is exported is system_remote_tree_information.txt.
If any of the conditions listed below applies to the content of the export file for the configuration information for remote monitoring, an error occurs and the file is not imported.
-
The same host is specified on multiple lines. (The managed host has multiple higher hosts.)
-
The host configuration is looped.
-
The host name specified for the managing host is not enclosed in square brackets [] (] is missing).
-
No host name is specified for the managing host.
-
More than 1,024 hosts are defined.
-
The local host is defined as the managed host.
After the export file (host_input_data.csv) for host information (manually-entered information) or the export file for the configuration information for remote monitoring is edited, the host name specified in the export file for the configuration information for remote monitoring might not be specified in the export file for the host information (manually-entered information) in some cases. In those cases, after the export file for the configuration information for remote monitoring is imported, an import warning message is displayed and the undefined host is automatically registered in IM Configuration Management as a managed host.
When you are trying to import the configuration information for remote monitoring, if the export file for the configuration information for remote monitoring is not found in the specified directory, an error message is displayed and the import operation is halted.
(3) Profile information
The content of the export files for the profile information is imported. The file that is imported differs according to the system monitoring method:
-
Agent monitoring
-
Remote monitoring
Table 9‒10: Export file for agent monitoring profile information to be imported Profile information
Export file name
Event Forwarding Settings File
forward
Log-file trap action definition file
Any name
Log-file trap startup definition file
jevlog_start.conf
Event Log-Trap Action Definition File
ntevent.conf
Local Action Execution Definition File
jbslcact.conf
When agent monitoring profile information is imported, the destination is determined using the directory name under definition_files directory. The directory name on the hierarchy one step below the definition_files directory is read as a host name, and the directory name on the hierarchy two steps below the definition_files directory is read as a product name. The file stored in each directory is registered on the applicable host as settings information. Consequently, if you change the host name in the export file (host_input_data.csv) for host information (manually-entered information), you must also change the directory name. If you do not change it, the profile information cannot be imported.
The profile information file is loaded as a character code described in encode of the export file (data_information.txt) for the export data information. For this character code, the environment variable LANG of the OS of the server that executed the export operation is set. When you import profile information, make sure that the character code described in the export file (data_information.txt) matches the character code of the profile information file.
If characters that do not have code compatibility or model-dependent characters are used in the host information, these characters may become garbled when they are imported.
If more than 10,000 hosts are defined, an error occurs and no file is imported.
If the export file for the profile (configuration file) contains an unsupported product or unsupported profile, these are ignored and processing continues.
(a) Remote monitoring profile information
When remote monitoring is used, the content of the export file for the remote monitoring profile information is imported. The remote monitoring profile information cannot be edited.
The following table describes the export files for remote monitoring profile information to be imported.
Profile information |
Export file name |
---|---|
Remote-monitoring log file trap action-definition file |
Any name |
Remote monitoring startup definition file |
jevlog_start.conf |
Remote-monitoring event log trap action-definition file |
ntevent.conf |
When remote monitoring profile information is imported, the destination is determined using the directory name under definition_files directory.
The directory name on the hierarchy one step below the definition_files directory is read as a host name, and the directory name on the hierarchy two steps below the definition_files directory is read as a product name. The file stored in each directory is registered on the applicable host as settings information. Consequently, if you change the host name in the export file (host_input_data.csv) for host information (manually-entered information), you must also change the directory name. If you do not change it, the profile information cannot be imported.
The profile information file is loaded in the encoding described in encode of the export file (data_information.txt) for the export data information. For this encoding, the value of the LANG environment variable of the OS of the server that executed the export operation is set. When you import profile information, make sure that the character encoding described in the export file (data_information.txt) matches the character encoding of the profile information file. If characters without code compatibility or model-dependent characters are used in the host information, these characters might be unreadable when they are imported.
(4) Remote authentication information
When remote monitoring is used, the content of the export file for the remote authentication information is imported. The name of the file to be imported is wmi.ini or ssh.ini.
When you use remote monitoring, after the remote authentication information is imported, invoke the System Common Settings window from the IM Configuration Management - View, check the settings, and then click the OK button.
(5) Business group information
When business groups are used, the content of the export file for the monitoring group information of IM Configuration Management is imported. If any of the conditions listed below applies to the content of the export file (monitoring_system_data.csv) for the business group information, an error occurs and the file is not imported.
-
Business groups that have the same name exist at the same level.
-
A value outside the permitted input range is specified.
-
The number of input data columns is insufficient (the number of commas does not match).
Save the export file for business group information (monitoring_system_data.csv) with the character encoding specified in line 1 (header information). If you save this file in UTF-8, make sure that no BOM (byte order mark) is included.
The following table describes items that are imported and the input range of each item.
Item |
Input range |
Required/Optional |
Default |
---|---|---|---|
Business group name |
A maximum of 255 bytes of characters can be entered in UTF-8. All characters are permitted except control characters, forward slashes (/), and single-byte commas (,). The first and the last characters cannot be a single-byte space. The characters are case sensitive. To specify a double quotation mark ("), specify two double quotation marks in succession and then enclose the entire string in double quotation marks. Do not use environment-dependent characters for business group names. Such characters can cause character corruption in the definition. |
Required |
-- |
Assigned JP1 resource group name |
A character string of up to 64 bytes can be input. Permitted characters are ASCII codes other than symbols (" / [ ] ; : , | = + ? < >), a tab, or a space. |
Optional |
Blank |
Comment |
A maximum of 80 bytes of characters can be entered in UTF-8. All characters are permitted except control characters. To specify a double quotation mark ("), specify two double quotation marks in succession and then enclose the entire string in double quotation marks. If you specify a comma (,), enclose the entire string in double quotation marks. |
Optional |
Blank |
Host name |
A maximum of 2,500 host names can be specified delimited by a comma (,). When you specify multiple host names, enclose the entire string in double quotation marks ("). For an input range consisting of a single host name, see Table 9-9 Host information that is imported (manually-entered information). |
Optional |
Blank |
(6) Monitoring group information
When business groups are used, the content of the export file for the business group information is imported. If any of the conditions listed below applies to the content of the export file (monitoring_group_data.csv) for the monitoring group information, an error occurs and the file is not imported.
-
Monitoring groups or hosts that have the same name exist at the same level.
-
A value outside the permitted input range is specified.
-
The number of input data columns is insufficient (the number of commas does not match).
-
A higher-level monitoring group is not defined on a line whose line number is younger than that of lower-level monitoring groups.
Save the export file for business group information (monitoring_group_data.csv) with the character encoding specified in line 1 (header information). If you save this file in UTF-8, make sure that no BOM (byte order mark) is included.
The following table describes items that are imported and the input range of each item.
Item |
Input range |
Required/Optional |
Default |
---|---|---|---|
Monitoring group path |
A maximum of 2,048 bytes of characters can be entered in UTF-8. All characters are permitted except control characters. The characters are case sensitive. To specify a double quotation mark ("), specify two double quotation marks in succession and then enclose the entire string in double quotation marks. Do not use environment-dependent characters for monitoring group names. Such characters can cause character corruption in the definition. |
Required |
-- |
Comment |
A maximum of 80 bytes of characters can be entered in UTF-8. All characters are permitted except control characters. To specify a double quotation mark ("), specify two double quotation marks in succession and then enclose the entire string in double quotation marks. If you specify a comma (,), enclose the entire string in double quotation marks. |
Optional |
Blank |
Host name |
A maximum of 2,500 host names can be specified delimited by a comma (,). If you specify multiple host names, enclose the entire string in double quotation marks ("). For an input range consisting of a single host name, see Table 9-9 Host information that is imported (manually-entered information). |
Optional |
Blank |