Register schedules for regular discoveries.
Hardware Information
Discovery of hardware information is performed every day at the following time by default:
2:00 AM
When modifying the discovery schedule, edit the configuration information collection schedule definition file, and modify it to the arbitrary date for collection. For details on configuration information collection schedule definition files, refer to the Reference Guide.
When it is not necessary to schedule automatic collection, add "#" to the top of the following line of the "configuration information collection schedule definition file".
AGT_CFMGSRV 0 2 * * *
If the schedule is modified or disabled, restart this product. If linked to ServerView Resource Orchestrator, restart ServerView Resource Orchestrator
OpenStack information
For Windows, register the following program with the Task Scheduler:
For Linux, add the following program to cron. Refer to the cron manuals for information on cron.
[Program]
[Windows]
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_openstack_updateinfo.exe
[Linux]
/opt/FJSVcfmgm/bin/swcfmg_openstack_updateinfo
[Options]
None.
Software patch information
For Windows, register the following program with the Task Scheduler:
For Linux, add the following program to cron. Refer to the cron manuals for information on cron.
[Program]
[Windows]
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_patch_updateinfo.exe |
[Linux]
/opt/FJSVcfmgm/bin/swcfmg_patch_updateinfo |
[Options]
-repository |
To perform regular discovery for only particular information, register the following program:
Windows patch information
[Program]
[Windows]
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_patch_updateinfo.exe |
[Linux]
/opt/FJSVcfmgm/bin/swcfmg_patch_updateinfo |
[Options]
-t windows -repository |
Linux patch information
[Program]
[Windows]
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_patch_updateinfo.exe |
[Linux]
/opt/FJSVcfmgm/bin/swcfmg_patch_updateinfo |
[Options]
-t linux |
Solaris OS patch information
[Program]
[Windows]
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_patch_updateinfo.exe |
[Linux]
/opt/FJSVcfmgm/bin/swcfmg_patch_updateinfo |
[Options]
-t solaris |
Software patch information
[Program]
[Windows]
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_patch_updateinfo.exe |
[Linux]
/opt/FJSVcfmgm/bin/swcfmg_patch_updateinfo |
[Options]
-t middleware |
Note
To perform regular discovery for only particular information, discovery for only the following combinations of information can be executed simultaneously:
Information collected by regular discovery | Windows patch information | Linux patch information | Solaris OS patch information | Software Patch Information |
|---|---|---|---|---|
Windows patch information | - | Y | Y | Y |
Linux patch information | Y | - | Y | - |
Solaris OS patch information | Y | Y | - | - |
Software patch information | Y | - | - | - |
Y: Can be executed simultaneously
-: Cannot be executed simultaneously
Parameter information
For Windows, register the following program with the Task Scheduler:
For Linux, add the following program to cron. Refer to the cron manuals for information on cron.
[Program]
[Windows]
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_param_updateinfo.exe |
[Linux]
/opt/FJSVcfmgm/bin/swcfmg_param_updateinfo |
[Options]
Refer to "swcfmg_param_updateinfo (Parameter Information Update Command)" in the Reference Guide for information on the valid options.
Discovery cannot be performed for parameter information of Solaris managed servers.
Note
Discovery of "software patch information" and discovery of "parameter information" cannot be executed concurrently.
Example setting procedures
[Windows]
The following example shows how to register a schedule with the Task Scheduler. In this example, regular discovery is executed for all patch information.
Log in to Windows using an account that belongs to the Administrators group.
Select Start >> Administrative Tools >> Task Scheduler.
The Task Scheduler window will be displayed.
Select Action >> Create Task.
The Create New window will be displayed.
Enter a task name in the Name field in the General tab, and then select Run whether user is logged on or not.
Select the Triggers tab, and then click the New button.
The New Trigger window will be displayed.
Register the discovery schedule.
Select the Actions tab, and then click the New button.
The New Action window will be displayed.
Configure the following settings:
Select Start a program from the Action pull-down menu.
Add the following command to the Program/script field:
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin\swcfmg_patch_updateinfo.exe |
Add the following argument to the Add arguments (optional) field:
-repository |
Click the OK button in the Create Task window.
The following window will be displayed:
Enter the user name for an account belonging to the Administrators group and the corresponding password, and then click the OK button.
[Linux]
The following example shows how to register a schedule with cron. In this example, regular discovery is executed for all patch information.
Perform the following procedure as the root user:
Check that the cron service has started
> service crond status crond (pid xxx) is running...
If the cron service is not running, use the following command to start the cron service:
> service crond start Starting crond:
Point
The cron service normally starts when the operating system starts.
By executing the following command, it is possible to check whether the cron service has been set to start when the operating system starts:
Red Hat Enterprise Linux 6
>chkconfig --list crond crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off
If the cron service has been set to start when the operating system starts, the numbers 2, 3, 4 and 5 above are set to "on" as shown above.
To set the cron service to start when the operating system starts, execute the following command:
>chkconfig --level 2345 crond on
Red Hat Enterprise Linux 7
>systemctl list-unit-files crond.service UNIT FILE STATE crond.service enabled
If the cron service has been set to start when the operating system starts, "STATE" is set to "enabled" as shown above.
To set the cron service to start when the operating system starts, execute the following command:
>systemctl enable crond.service
Execute the following command to edit the schedule definitions:
>crontab -e
Executing the "crontab -e" command starts the vi editor. Refer to the vi editor manuals for information on the vi editor.
Example: Discovering all patch information every day at 2:00
0 2 * * * /opt/FJSVcfmgm/bin/swcfmg_patch_updateinfo -repository > /dev/null 2>&1
Point
Guide to the execution interval for regular discovery
It is recommended that regular discovery be executed once a day, outside business hours (such as late at night).
Take the following guide into account when setting an execution interval:
Hardware configuration information
Blade server
Number of physical servers | Execution interval |
|---|---|
500 | 100 minutes or more |
Rack mount server
Number of physical servers | Execution interval |
|---|---|
500 | 170 minutes or more |
Virtual environment configuration information
Number of Virtual guests | Execution interval |
|---|---|
500 | 10 minutes or more |
1,000 | 20 minutes or more |
1,500 | 30 minutes or more |
OpenStack information
Number of instances | Execution interval |
|---|---|
500 | 10 minutes or more |
1,000 | 20 minutes or more |
1,500 | 30 minutes or more |
Software configuration information
Windows patch information
Number of business servers | Number of WSUS servers (*1) | Execution interval |
|---|---|---|
500 | 1 | 30 minutes or more |
1,000 | 2 | 60 minutes or more |
1,500 | 3 | 60 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 | Execution interval |
|---|---|
500 | 90 minutes or more |
1,000 | 150 minutes or more |
1,500 | 210 minutes or more |
Solaris OS patch information
Number of business servers | Execution interval |
|---|---|
500 | 60 minutes or more |
1,000 | 120 minutes or more |
1,500 | 180 minutes or more |
Software patch information
Number of business servers | Execution interval |
|---|---|
500 | 60 minutes or more |
1,000 | 90 minutes or more |
1,500 | 120 minutes or more |
All software configuration information
To perform regular discovery of all software configuration information, estimate the discovery execution interval based on the following conditions:
The execution interval for regular 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 discovery execution interval is as follows:
Discovery execution interval for Windows patch information (1,000 business servers): At least 60 minutes
Discovery execution interval for Linux patch information (500 business servers): At least 90 minutes
Discovery execution interval for Solaris patch information (500 business servers): At least 60 minutes
Discovery execution interval for software patch information (1,500 business servers): At least 120 minutes
The execution interval for regular discovery will be at least 210 minutes (i.e., 90 + 120 minutes).
Note
If the system is stopped at the specified discovery start time (due to maintenance, for example), discovery will be performed at the next scheduled time.
