The first discovery performed after installation is called the initial discovery. Establish the following environment before performing the initial discovery:
Discovering the hardware information
Discovering the hardware configuration information
Register the hardware information of the discovery target using the hardware information management command.
Confirm that the manager of this product can communicate with the hardware to be discovered.
Information
In order to collect CPU information and memory information of a blade server, the target blade server must have been powered on at least one time.
When collecting chassis and blade server information, confirm that the chassis is powered on.
Discovering the virtual environment configuration information
Register the hardware information and the VM host information of the discovery target using the hardware information management command.
Install VMware Tools on the VM guest.
Confirm that the VM host and the VM guest are powered on.
Specify the admin LAN subnet address in the "Hardware discovery definition file". For details on the "Hardware discovery definition file", refer to the Reference Guide.
If Host Isolation Response of vSphere HA clusters has been set to Leave Powered On, when isolating the VM host, the VM host information is not updated by discovery. In addition, the information of the VM guests on that VM host will be deleted.
Discovering OpenStack information
An OpenStack service access user must be registered with this product. Register the service access user referring to "3.10.2 Settings for Linking to OpenStack".
Confirm that the manager of this product can communicate with the OpenStack API services.
Information
Information of deployed stacks and instances is not collected.
In order to collect the information on the CPUs and memory of a server, the corresponding instance must be up and running.
Host name information cannot be collected.
Discovering Windows patch information
Create linkage servers
Refer to "2.1.3 Creating Linkage Servers (Repository Servers)" for details.
Set up business servers
Refer to "3.10.3 Settings for Managing Windows Patches" for details.
Discovering Linux patch information
Create linkage servers
Refer to "2.1.3 Creating Linkage Servers (Repository Servers)" for details.
Set up business servers
Refer to "3.10.4 Settings for Managing Linux Patches" for details.
Discovering the Solaris OS patch information
Not required.
Discovering the software patch information
Set up business servers
When discovering Fujitsu middleware patch information, refer to "3.10.5 Settings for UpdateAdvisor (Middleware)" for details.
Configure settings on the admin server
Register the update application management registry configuration file
When discovering Fujitsu middleware patch information, refer to Step 1-1 and Step 1-2 under "Fujitsu Middleware Patch Management" in "Operation Flow" in the Operation Guide for details.
Note
When performing upgrade or something that changes the version of the Fujitsu middleware installed on the discovery target server, uninstall the older version of the Fujitsu middleware and perform discovery, and then install the new version of Fujitsu middleware.
Registration of the source of information collection
When discovering the patch information of software other than Fujitsu middleware, refer to "Definition of Information Collection Sources" in the Developer's Guide.
Discovering parameter information
Configure settings on the admin server
Collect software configuration information
Refer to Step 1 under "Software Parameter Management" in "Operation Flow" in the Operation Guide for details.
Register software information
This step is not required if using the software definition in which this product is already registered.
Refer to "Definition of Software Information" in "Definition of Software Information" in the Developer's Guide for details.
Register parameters to be collected
This step is not required if using the parameter collection definition in which this product is already registered.
Refer to Step 4 under "Software Parameter Management" in "Operation Flow" in the Operation Guide for details.
Associate the software and the parameter collection definition
This step is not required if using the software definition in which this product is already registered.
Refer to Step 5 under "Software Parameter Management" in "Operation Flow" in the Operation Guide for details.
Hardware Information
Perform the initial discovery of hardware information by executing the following command:
[Windows]
%SWCFMGM_INSTALL_PATH%\CMDB\FJSVcmdbm\bin\cmdbrefresh.exe -q type=AGT_CFMGSRV |
[Linux]
/opt/FJSVcfmgm/CMDB/FJSVcmdbm/bin/cmdbrefresh.sh -q type=AGT_CFMGSRV |
OpenStack information
Perform the initial discovery of OpenStack information by executing the following command:
[Windows]
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_openstack_updateinfo.exe |
[Linux]
/opt/FJSVcfmgm/bin/swcfmg_openstack_updateinfo |
Software patch information
Perform the initial discovery of software patch information by executing the following command.
[Windows]
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_patch_updateinfo.exe -repository |
[Linux]
/opt/FJSVcfmgm/bin/swcfmg_patch_updateinfo -repository |
To discover only particular information, execute the following command:
Windows patch information
[Windows]
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_patch_updateinfo.exe -t windows -repository |
[Linux]
/opt/FJSVcfmgm/bin/swcfmg_patch_updateinfo -t windows -repository |
Linux patch information
[Windows]
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_patch_updateinfo.exe -t linux |
[Linux]
/opt/FJSVcfmgm/bin/swcfmg_patch_updateinfo -t linux |
Solaris OS patch information
[Windows]
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_patch_updateinfo.exe -t solaris |
[Linux]
/opt/FJSVcfmgm/bin/swcfmg_patch_updateinfo -t solaris |
Software patch information
[Windows]
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_patch_updateinfo.exe -t middleware |
[Linux]
/opt/FJSVcfmgm/bin/swcfmg_patch_updateinfo -t middleware |
When performing the patch management of Fujitsu middleware, register newly released Fujitsu middleware patches after the initial discovery has been performed.
Refer to Step 2-1 to Step 2-4 under "Fujitsu Middleware Patch Management" in "Operation Flow" in the Operation Guide for information on how to register newly released Fujitsu middleware patches.
Parameter Information
Perform the initial discovery of parameter information by executing the following command: Discovery cannot be performed for parameter information of Solaris managed servers.
[Windows]
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_param_updateinfo.exe |
[Linux]
/opt/FJSVcfmgm/bin/swcfmg_param_updateinfo |
Refer to "swcfmg_param_updateinfo (Parameter Information Update Command)" in the Reference Guide for information on the options that can be used in swcfmg_param_updateinfo.
Note
Perform the procedure in "3.8 Registering Discovery Schedules" after the initial discovery is complete. The initial discovery can take quite a long time, so if the execution of a discovery registered using the procedure in "3.8 Registering Discovery Schedules" coincides with the execution of the initial discovery, then the regular discovery will fail to execute.
Perform the procedure in "3.9 Registering a Configuration Baseline Creation Schedule" after the initial discovery is complete. The initial discovery can take quite a long time, so if a configuration baseline creation registered using the procedure in "3.9 Registering a Configuration Baseline Creation Schedule" coincides with the execution of the initial discovery, then the configuration baseline will not be created correctly.
Point
Guide to the time required for the initial discovery
It is recommended that the initial discovery be executed before operations commence.
The following tables show an approximate indication of the time required for the initial discovery:
Hardware configuration information
Blade server
Number of physical servers | Time required for the initial discovery |
|---|---|
500 | 100 minutes or more |
Rack mount server
Number of physical servers | Time required for the initial discovery |
|---|---|
500 | 170 minutes or more |
Virtual environment configuration information
Number of Virtual guests | Time required for the initial discovery |
|---|---|
500 | 10 minutes or more |
1,000 | 20 minutes or more |
1,500 | 30 minutes or more |
OpenStack information
Number of Virtual guests | Time required for the initial discovery |
|---|---|
500 | 30 minutes or more |
1,000 | 60 minutes or more |
1,500 | 80 minutes or more |
Software configuration information
Windows patch information
Number of business servers | Number of WSUS servers (*1) | Time required for the initial discovery |
|---|---|---|
500 | 1 | 240 minutes or more |
1,000 | 2 | 330 minutes or more |
1,500 | 3 | 420 minutes or more |
*1: The "Number of WSUS servers" refers to the recommended number of WSUS servers when business servers are managed by distributing them to multiple WSUS servers in order to balance the load on WSUS servers. It is recommended that each WSUS server manage no more than 500 business servers.
Linux patch information
Number of business servers | Time required for the initial discovery |
|---|---|
500 | 240 minutes or more |
1,000 | 420 minutes or more |
1,500 | 600 minutes or more |
Solaris OS patch information
Number of business servers | Time required for the initial discovery |
|---|---|
500 | 60 minutes or more |
1,000 | 120 minutes or more |
1,500 | 180 minutes or more |
Software patch information
Number of business servers | Time required for the initial discovery |
|---|---|
500 | 90 minutes or more |
1,000 | 120 minutes or more |
1,500 | 150 minutes or more |
All software configuration information
To discover all software configuration information, estimate the time required for discovery based on the following conditions:
The time required for the initial discovery of all software configuration information is either of the following, whichever is longer:
|
Example:
To discover OS patch information and software patch information for 1,500 business servers (1,000 Windows business servers + 500 Linux business servers), the time required for the initial discovery is as follows:
Time required for the initial discovery of Windows patch information (1,000 business servers): At least 330 minutes
Time required for the initial discovery of Linux patch information (500 business servers): At least 240 minutes
Time required for the initial discovery of Solaris patch information (500 business servers): At least 60 minutes
Processing time for the initial discovery of software patch information (1,500 business servers): At least 150 minutes
The time required for the initial discovery will be at least 390 minutes (i.e., 240 + 150 minutes).
