Top
Systemwalker Runbook Automation Reference Guide
Systemwalker

3.8.1 Remove as load balancing target

Description

This operation component uses IPCOM to remove a server from a load balancing target.

Options

Basic Options

(1) hostname

Host name or IP address for connecting through an operation management network set in IPCOM.

An argument error occurs if the host name or IP address is omitted.

The maximum length of the host name or IP address is 1,024 characters. An argument error occurs if this is exceeded.

(2) lbhostname

Host name or IP address of the server that is to be removed from a load balancing target managed by IPCOM.

An argument error occurs if the host name or IP address is omitted.

The maximum length of the host name or IP address is 1,024 characters. An argument error occurs if this is exceeded.

Advanced Options

(1) removetime

Time period until the server is removed from a load balancing target managed by IPCOM.

Specify removetime in seconds.

Values between 0 and 3600 can be specified.

For example: If the removetime is 10 minutes: 600

An argument error occurs if a value outside the above range is entered.

If removetime is omitted, 0 (seconds) is specified.

(2) username

Name of the user connecting with SSH to the IP address for connecting through an operation management network set in IPCOM.

The connecting user name must have a user role of administrator.

If the connected user name and password required for connection are not specified, the Configuration Management Database (CMDB) is searched based on the specified host name or IP address and Systemwalker Runbook Automation automatically sets the acquired connected user name as the value.

The maximum length of the connected user name is 1,024 characters. An argument error occurs if this is exceeded.

(3) password

Password of the user connecting with SSH to the IP address for connecting through an operation management network set in IPCOM.

If the connected user name and password required for connection are not specified, the Configuration Management Database (CMDB) is searched based on the specified host name or IP address and Systemwalker Runbook Automation automatically sets the acquired connected user password as the value.

The maximum length of the connected user password is 1,024 characters. An argument error occurs if this is exceeded.

(4) execusername

The execusername value cannot be used in operation components.

Invalidated when the value of execusername is input.

(5) execpassword

Password for the command for transitioning to the administrator EXEC mode (admin command).

If the password necessary for "execusername" and transitioning to the administrator EXEC mode is omitted, the Configuration Management Database (CMDB) is searched based on the specified host name or IP address and Systemwalker Runbook Automation automatically sets the acquired administrator user password as the value.

The maximum length of the password for transitioning to the administrator EXEC mode is 1,024 characters. An argument error occurs if this is exceeded.

(6) timeout

This is the completion timeout (seconds) for the execution of operation components.

Values between 300 and 86400 (1 day) can be specified.

For example: When timeout is to occur every 10 minutes: 600

When the execution of the operation components is not completed even if the specified time passes, the processing of the operation components is interrupted in return value 201.

(7) retry

This is the retry count for the execution of operation components.

When the operation components end in return value 161, the retry count is specified. Values between 0 and 5 can be specified.

As a result of retrying, if the operation components ended by the return values other than 161, the execution of the operation components ends even if it doesn't reach the specified retry count. The return values of the operation components become the value executed at the end.

For example: When retries are to be performed twice: 2

(8) retry_interval

This is the retry interval (seconds) for operation components.

When the operation components end in return value 161, the retry interval is specified. Values between 1 and 14400 can be specified.

For example: When retrying in 300 seconds: 300


If the specification of the timeout, retry and retry_interval is omitted, and a value beyond the limits of the above-mentioned is input, the value specified with the operation components definition file becomes effective. Refer to "2.5 Definition File for Operation Components" for details.

Return Values

Icon

Name

Return value

Description

Success

0

Removal from the load balancing target was successful.

Failure

161

Removal from the load balancing target failed. Retried if a retry count has been specified.

187

Authentication failed when an attempt was made to connect to the server over the network (using SSH).

Alternatively, an error occurred during the processing of communications with server (file transfer infrastructure). In this case, the error code for the file transfer infrastructure is output to the execution results. Refer to "3.21 Detailed Code of File Transfer Infrastructure" for information on error codes.

188

When an operation component was performing an operation on a Business Server where an RBA Agent has not been installed, the network communications (SSH) with the Business Server was closed.

189

An attempt to connect to the server over the network (using SSH) failed.

Alternatively, an error occurred during the processing of communications with the server (file transfer infrastructure). In this case, the error code for the file transfer infrastructure is output to the error output. Refer to "3.21 Detailed Code of File Transfer Infrastructure" for information on error codes.

197

There is an error in the option content.

-

-

201

Execution of operation component timed out.

202

The operation component was not executed. There is a problem in the setting to execute operation components.

203

Failed to execute the operation component. There is a problem in the Operation Automation Server environment.

205

The operation component was not executed. There is a problem with the input information specification of the operation component.

206

The operation component was not executed normally. There is a problem with the output information specification of the operation component.

207

The operation components were not executed. There is a possibility that the operation components are not registered in the Management Server.

208

The Automated Operation Process has been canceled because the Automated Operation Process was recovered while the operation component was executing.

Output information

Variable

Description

message

This variable will be set to the following message if the server is successfully removed from the load balancing target, .

The operation component was successful.

If removing the server form the load balancing target fails, this variable will be set to the content of the error as a string.

returnCode

This variable is set to the return value.

Notes