Editing these setting files can customize the default behavior of the device polling function. Two setting files are provided: one file is for defining the polling function behavior and the other file is for defining event linkage control. These files are descried in XML.
Reflecting Contents of Setting File
Changed contents are automatically reflected at the next polling operation. (Manager checks the file contents every 30 seconds even while polling is stopped.) Even if executing "Definition File Re-read" using Web Console, be careful that the file may not be reflected.
Customization (Polling Function Behavior Setting File)
Note
If an error is detected in an XML file, the event message shown below is output for each polling operation. In this event, the polling function operates with the default settings.
Message: "[Polling] XML File Format Error(XML file name)"
Be sure not to delete the file itself even if no items are set. If the file is deleted, re-create the file according to the above sample.
When customizing the polling function behavior setting file, do not edit the setting file in the installation directory but edit the one in the customization directory.
The polling function behavior setting file is stored in the following location during Manager installation or upgrading:
Platform of Manager | Location |
|---|---|
Windows | $INS_DIR\ESC\Manager\opt\FJSVssmgr\lib\devicepolling\DP_config.xml |
Solaris OS, | /opt/FJSVssmgr/lib/devicepolling/DP_config.xml |
When customizing the polling function behavior, copy the polling function behavior setting file in the above location to the customization location shown below, and edit the copy of the file.
Platform of Manager | Customization Location |
|---|---|
Windows | $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\devicepolling\DP_config.xml |
Solaris OS, | /etc/opt/FJSVssmgr/current/devicepolling/DP_config.xml |
If the polling function behavior setting file exists in the customization location, Manager operates in accordance with the setting file. If not, it operates in accordance with the default setting file in the installation directory.
Item | Description |
|---|---|
Polling interval | Polling operation interval (including during stoppage) |
Device not subject to polling | Specify a device to exclude it from polling. |
The tag node hierarchy is shown below.
Attribute Name | Description |
|---|---|
value | A polling operation interval is set in seconds (decimal). The minimum interval is 30 seconds. If a value less than 30 is specified, 30 seconds is used for polling. |
No attributes can be set in the Device tag. As many exclude tags as required can be set.
Attribute Name | Description |
|---|---|
address | Specify the IP address of a device to exclude it from polling operations. For IP address, IPv4 or IPv6 format can be specified. |
The default values of the parameters are as follows:
Polling interval: 60 seconds
Device not subject to polling: None
<?xml version="1.0" encoding="UTF-8" ?>
<PollingManagerConfiguration>
<Interval value="60"/>
<Device>
<exclude address="192.0.2.10"/>
<exclude address="192.0.2.11"/>
</Device>
</PollingManagerConfiguration>Customization (Control Event Linkage Setting File)
Note
The portions that can be changed are the name attribute values of the ExternalScript1 and ExternalScript2 tags and the flag attribute value of the Convert tag only. The other portions may not be modified since the changes can possibly cause an abnormal behavior of the polling function.
Events involving the server node agent are not posted to Systemwalker Centric Manager. Use the monitoring function of Systemwalker Centric Manager to monitor operating status.
The setting file is stored in the following directory:
Platform of Manager | Location |
|---|---|
Windows | $INS_DIR\ESC\Manager\opt\FJSVssmgr\lib\snmpth\1_3_6_1_4_1_211_4_1_3_21_1.xml |
Solaris OS, | /opt/FJSVssmgr/lib/snmpth/1_3_6_1_4_1_211_4_1_3_21_1.xml |
Item | Description |
|---|---|
External script name definition | Define the script name when using external script linkage. |
Operation definition | Whether to display a posted status change Whether to output the event log Whether to implement linkage with Systemwalker Centric Manager and linkage with Shell/Bat Whether to implement external script linkage 1 |
External Script name definition
When using external script linkage, define the script name in the name attribute of following definition lines (in full path specification).
Item | Definition Line |
|---|---|
external script linkage 1 | <ExternalScript1 name="c:\somedir\script1.bat" /> |
external script linkage 2 | <ExternalScript2 name="c:\somedir\script2.bat" /> |
Event linkage behavior definition
In the configuration file, there are following definition lines according to the events. To define Event linkage behavior, set in the flag attribute of each definition line.
Event | Definition Line |
|---|---|
When the status becomes normal | <Convert val="0" name="" level="I" flag="001111" /> |
When the status becomes warning | <Convert val="1" name="" level="W" flag="001111" /> |
When the status becomes error | <Convert val="2" name="" level="E" flag="001111" /> |
When the status becomes timeout | <Convert val="3" name="" level="WT" flag="001111" /> |
When communication has been recovered | <Convert val="10" name="" level="IR" flag="001111" /> |
Flag Attribute is shown below.
Attribute Name | Description |
|---|---|
flag | Control of event, linkage with Systemwalker Centric Manager, and linkage with Script (in 6-bits in binary) The "0" is interpreted as "off", the "1" is "on". bit5 ... External script linkage 2 For example, only linkage with Systemwalker Centric Manager is set to on "001000". |