To collect configuration information automatically, specify the following settings on the Management Server.
To collect IT resource information, specify settings on the Business Server in advance.
Refer to Settings up Business Server for details.
To discover nodes with IPv6 addresses, specify DNS server for reference in network configuration. Also, set to reverse resolution to be able to convert from IPv6 address of Management Server to domain name on DNS server, and set up a DNS server and register the IPv6 addresses of the nodes to be discovered on the server.
For the host name of Management Server which set in DNS server, specify the same host name which confirmed by the "hostname" or "uname -n" command.
Also, Specify the local host name ( the host name which confirmed by the "hostname" or "uname -n" command ) in the hosts file to correspond with IPv4 address. For how to specify them in hosts file, refer to "2.1.3 Checking the Settings in the hosts File"
Privileges required for execution
[Windows]
Administrator privileges are required. If the operating system being used is Windows Server 2008 or a subsequent version, execute the collection processing as an administrator.
[Linux]
System administrator (superuser) privileges are required.
[Windows]
If Systemwalker Runbook Automation is running, then stop it:
<Installation directory for the Systemwalker Runbook Automation Management Server>\bin\swrba_stop |
Modify the IT resource information collection configuration file.
To perform node discovery from a subnet other than the subnet where Management Servers are located, modify the file (for details, refer to "3.1.9.4 How to modify the IT resource information collection configuration file").
Set up the environment:
"%SWCMDB_INSTALL_PATH%\ FJSVcmdbm\bin\cmdbsetupenv.bat" -k AGT_INV |
Modify the Definition File for Collection of Configuration Information
In agent with setting up, it collects information at the following time everyday as a default.
4.30am
Refer to the Definition File for Collection of Configuration Information in the Systemwalker Runbook Automation Reference Guide and change to collecting schedule to any date.
Note that if you do not need to execute automated collect routinely, Add "#" to the first letter of following line with comment out.
AGT_INV 30 4 * * *
Start Systemwalker Runbook Automation:
<Installation directory for the Systemwalker Runbook Automation Management Server>\bin\swrba_start |
Automatically collect IT resource information:
"%SWCMDB_INSTALL_PATH%\FJSVcmdbm\bin\cmdbrefresh.exe" -q type=AGT_INV |
As a result of this command, the nodes connected to the network will be detected automatically, and the information collected will be registered with the CMDB Manager.
Register authentication information on Business Server.
From Business Server which not installed agent package for Business Server, to collect logical server, hardware information, installed software information, as IT resource information, To be need to register authentication information for SSH communication on CMDB
Refer to the 3.1.9.6 Registering authentication information (when collecting IT resource information) .
Point
Refer to "cmdbrefresh (Observed Record Collection Request Command)" in the Systemwalker Runbook Automation Reference Guide for details on the cmdbrefresh command. Check the following messages in the event log to check when the collection processing completes.
FCMDB: INFO: [10004] Update check processing has started. '<Agent service type>'
FCMDB: INFO: [10005] Update check processing has completed. '<Agent service type>'
[Linux]
If Systemwalker Runbook Automation is running, then stop it by issuing the command below:
/opt/FJSVswrbam/bin/swrba_stop |
Modify the IT resource information collection configuration file.
To perform node discovery from a subnet other than the subnet where Management Servers are located, modify the file (for details, refer to "3.1.9.4 How to modify the IT resource information collection configuration file").
Set up the environment:
/opt/FJSVcmdbm/bin/cmdbsetupenv.sh -k AGT_INV |
Modify the Definition File for Collection of Configuration Information
In agent with setting up, it collects information at the following time everyday as a default.
4.30am
Refer to the Definition File for Collection of Configuration Information in the Systemwalker Runbook Automation Reference Guide and change to collecting schedule to any date.
Note that if you do not need to execute automated collect routinely, Add "#" to the first letter of following line with comment out.
AGT_INV 30 4 * * *
Start Systemwalker Runbook Automation
/opt/FJSVswrbam/bin/swrba_start |
Automatically collect IT resource information:
/opt/FJSVcmdbm/bin/cmdbrefresh.sh -q type=AGT_INV |
As a result of this command, the nodes connected to the network will be detected automatically, and the information collected will be registered with the CMDB Manager.
Register authentication information on Business Server.
From Business Server which not installed agent package for Business Server, to collect logical server, hardware information, installed software information, as IT resource information, To be need to register authentication information for SSH communication on CMDB
Refer to the Registering authentication information(when collecting IT resource information) .
Point
Refer to "cmdbrefresh (Observed Record Collection Request Command)" in the Systemwalker Runbook Automation Reference Guide for details on the cmdbrefresh command. Check the following messages in the syslog to check when the collection processing completes.
- FCMDB: INFO: [10004] Update check processing has started. 'Agent service name'
- FCMDB: INFO: [10005] Update check processing has completed. 'Agent service name'
[Windows]
If Systemwalker Runbook Automation is running, then stop it:
<Installation directory for the Systemwalker Runbook Automation Management Server>\bin\swrba_stop |
Modify the agent linkage configuration file.
To perform node discovery from a subnet other than the subnet where Management Servers are located, modify the file (for details, refer to "3.1.9.5 How to modify the agent linkage configuration file").
Set up the environment:
"%SWCMDB_INSTALL_PATH%\FJSVcmdbm\bin\cmdbsetupenv.bat" -k AGT_ADSC |
Modify the Definition File for Collection of Configuration Information
In agent with setting up, it collects information at the following time everyday as a default.
4.30am
Refer to the Definition File for Collection of Configuration Information in the Systemwalker Runbook Automation Reference Guide and change to collecting schedule to any date.
Note that if you do not need to execute automated collect routinely, Add "#" to the first letter of following line with comment out.
AGT_ADSC 45 4 * * *
Start Systemwalker Runbook Automation:
<Installation directory for the Systemwalker Runbook Automation Management Server>\bin\swrba_start |
:Update the observed records managed by the CMDB
"<Installation directory for the Systemwalker Runbook Automation Management Server>\CMDB\FJSVcmdbm\bin\cmdbrefresh.exe" -q type=AGT_ADSC |
As a result of this command, the information collected will be registered with the CMDB Manager.
Point
Refer to "cmdbrefresh (Observed Record Collection Request Command)" in the Systemwalker Runbook Automation Reference Guide for details on the cmdbrefresh command. Check the following messages in the event log to check when the collection processing completes.
FCMDB: INFO: [10004] Update check processing has started. '<Agent service type>'
FCMDB: INFO: [10005] Update check processing has completed. '<Agent service type>'
[Linux]
If Systemwalker Runbook Automation is running, then stop it:
/opt/FJSVswrbam/bin/swrba_stop |
Modify the agent linkage configuration file.
To perform node discovery from a subnet other than the subnet where Management Servers are located, modify the file (for details, refer to "3.1.9.5 How to modify the agent linkage configuration file").
Set up the environment:
/opt/FJSVcmdbm/bin/cmdbsetupenv.sh -k AGT_ADSC |
Modify the Definition File for Collection of Configuration Information
In agent with setting up, it collects information at the following time every day as a default.
4.30am
Refer to the Definition File for Collection of Configuration Information in the Systemwalker Runbook Automation Reference Guide and change to collecting schedule to any date.
Note that if you do not need to execute automated collect routinely, Add "#" to the first letter of following line with comment out.
AGT_ADSC 45 4 * * *
Start Systemwalker Runbook Automation
/opt/FJSVswrbam/bin/swrba_start |
Update the observed records managed by the CMDB:
/opt/FJSVcmdbm/bin/cmdbrefresh.sh -q type=AGT_ADSC |
As a result of this command, the information collected will be registered with the CMDB Manager.
Point
Refer to "cmdbrefresh (Observed Record Collection Request Command)" in the Systemwalker Runbook Automation Reference Guide for details on the cmdbrefresh command. Check the messages in the syslog to check when the collection processing completes.
Perform this setup procedure when using the "Register logical node" operation component. Also, be sure to perform this setup procedure when using the "Deploying systems and registering them in CMDB" or "Changing systems and registering them in CMDB" template, which are operation templates for virtual environments that use the "Register logical node" operation component.
For information on the "Register logical node" operation component, refer to the Systemwalker Runbook Automation Reference Guide. For information on the "Deploying systems and registering them in CMDB" or "Changing systems and registering them in CMDB" template, refer to the Systemwalker Runbook Automation Template Operator's Guide.
[Windows]
When the Systemwalker Runbook Automation has been started, execute the following command and stop it
[Systemwalker Runbook Automation Install directory of Management Server \bin\swrba_stop
Execute the following setting environment command
"%SWCMDB_INSTALL_PATH%\FJSVcmdbm\bin\cmdbsetupenv.bat" -k AGT_INVIP
Execute the following command, start Systemwalker Runbook Automation
[Systemwalker Runbook Automation Install directory of Management Server]\bin\swrba_start
Register certification information of Business server
If you correct logical server information, hardware information, and installed software information such as an IT resource information from Business Server where it has not been installed agent package for Business server, you will need to register certification information to connect by SSH in CMDB.
Refer to the "3.1.9.6 Registering authentication information (when collecting IT resource information)" and register it.
[Linux]
When the Systemwalker Runbook Automation has been started, execute the following command and stop it
/opt/FJSVswrbam/bin/swrba_stop
Execute the following setting environment command.
/opt/FJSVcmdbm/bin/cmdbsetupenv.sh -k AGT_INVIP
Execute the following command, start Systemwalker Runbook Automation
/opt/FJSVswrbam/bin/swrba_start
Register certification information of Business server
If you correct logical server information, hardware information, and installed software information such as an IT resource information from Business Server where it has not been installed agent package for Business server, you will need to register certification information to connect by SSH in CMDB.
Refer to the "3.1.9.6 Registering authentication information (when collecting IT resource information)" and register it.
This section describes how to specify the subnets for which IT resource information is to be collected.
IT resource information collection configuration file
Windows |
|
Linux | /opt/FJSVcmdba/etc/mdr_inv.properties |
Edit "mdr_inv. properties" with using editor.
Entry | Description |
|---|---|
<Group name>.mdbad.inventory.network.address | Subnet address. Separate subnets with commas (,). This item can be omitted if node discovery is performed from only the subnet where Management Servers or Relay Servers are located. Nodes on the specified subnets will be detected. IP addresses in IPv4 and IPv6 formats cannot be specified collectively. Separate them into different groups. |
<Group name>.mdbad.inventory.network.subnetmask | Subnet mask. For IPv6 environments, specify the length of the subnet prefix. |
<Group name>.mdbad.inventory.snmp.community | SNMP community name (public). |
<Group name>.mdbad.inventory.node.discovery.ignore | Whether to disable node discovery. If "true" is specified, then node discovery will not be performed when information is collected periodically by the agent's schedule function, and IT resource information will only be collected for nodes already detected. If IT resource information is collected using the cmdbrefresh command, then node discovery will be performed even if this parameter is set to "true". |
To collect IT resource information by dividing multiple subnets into groups, specify the group name at the start of each parameter.
For large-scale systems, IT resource information can be collected sequentially by dividing subnets into multiple groups. To divide subnets into multiple groups, specify the four parameters for each group after changing the group name in each case.
To collect IT resource information from IPv4 and IPv6 environments, separate them into different groups.
By specifying the group name for <parameter> (for when the agent type is "AGT_INV") when using the configuration information collection schedule configuration file to specify the operation schedule for the agent that collects configuration information, information can be collected at the specified date and time for each group.
The following is an example of the IT resource information collection configuration file (mdr_inv.properties).
# default mdbad.inventory.network.address= mdbad.inventory.network.subnetmask=255.255.255.0 mdbad.inventory.snmp.community=public mdbad.inventory.node.discovery.ignore=true # group1 group1.mdbad.inventory.network.address= 192.0.2.0 group1.mdbad.inventory.network.subnetmask=255.255.255.0 group1.mdbad.inventory.snmp.community=public group1.mdbad.inventory.node.discovery.ignore=true # group2 group2.mdbad.inventory.network.address= 198.51.100.0 group2.mdbad.inventory.network.subnetmask=255.255.255.0 group2.mdbad.inventory.snmp.community=public group2.mdbad.inventory.node.discovery.ignore=true # group3 group3.mdbad.inventory.network.address= 203.0.113.0 group3.mdbad.inventory.network.subnetmask=255.255.255.0 group3.mdbad.inventory.snmp.community=public group3.mdbad.inventory.node.discovery.ignore=true
|
Follow the steps below to specify the subnets where node discovery will be performed.
Copy the template for the agent linkage configuration file as indicated below:
Source:
[Windows]
For Management Servers
<CMDB Manager directory>\FJSVcmdba\etc\mdrdb.user.template |
For Relay Servers
<Agent installation directory>\CMDB\FJSVcmdba\etc\mdrdb.user.template |
[Linux]
/opt/FJSVcmdba/etc/mdrdb.user.template |
Target:
[Windows]
For Management Servers
<CMDB Manager directory>\FJSVcmdba\etc\mdrdb.user |
For Relay Servers
<Agent installation directory>\CMDB\FJSVcmdba\etc\mdrdb.user |
[Linux]
/opt/FJSVcmdba/etc/mdrdb.user |
Edit the new file (mdrdb.user) as described in the table below:
Entry | Description |
|---|---|
mdbad.autodiscovery.network.address | Subnet addresses where nodes on the network will be automatically detected. Separate subnets with commas (,). This item can be omitted if node discovery is performed from only the subnet where Management Servers or Relay Servers are located. Only nodes on the specified subnets will be detected. IP addresses in IPv4 and IPv6 formats cannot be specified collectively. |
mdbad.autodiscovery.network.subnetmask | Subnet mask. For IPv6 environments, specify the length of the subnet prefix. |
mdbad.autodiscovery.snmp.community | SNMP community name. |
The following is an example of the agent linkage configuration file (mdrdb.user).
# Subnet address where node is retrieved mdbad.autodiscovery.network.address= 192.0.2.0,198.51.100.0 # Subnet mask for node retrieval mdbad.autodiscovery.network.subnetmask=255.255.255.0 # Community name of SNMP mdbad.autodiscovery.snmp.community=public |
For IPv6 environments
# Subnet address where node is retrieved |
By executing the cmdbrefresh command after the setup, the list of nodes will be registered with the CMDB. To collect IT resource information, the authentication information (user ID and password) for SSH connections and the machine model information must be registered.
Note that it will not be possible to collect IT resource information unless both the authentication information and the machine model information have been registered and are correct.
Note that nodes that were not running when node discovery was performed for the first time will not be detected, but these nodes can be added to the CMDB by executing the cmdbrefresh command again after these nodes have started.
To register authentication information, follow the steps below:
Create a (CSV format) configuration file.
The file must contain the authentication information, the machine model information and other mandatory information (refer to the Systemwalker Runbook Automation Reference Guide for details).
Register authentication information with the CMDB:
[Windows]
<Installation directory for the Systemwalker Runbook Automation Management Server>\bin\swrba_uaimport -f <file>.csv |
[Linux]
/opt/FJSVswrbam/bin/swrbauaimport -f <file>.csv |
Point
Triggers for collecting IT resource information
The collection of IT resource information is triggered by periodic node discoveries on the Management Server (and Relay Servers). The dates and times when periodic node discovery will run can be specified using the configuration information collection schedule configuration file.
Information can also be collected at any time by executing the cmdbrefresh command.
