Resource Orchestrator is able to manage SPARC Enterprise M4000/M5000/M8000/M9000 servers and servers in SPARC M10-4S/M12-2S by using their XSCF interface as a remote management controller.
Choose values for the following XSCF settings according to the criteria listed below.
This name is used to identify the chassis for SPARC Enterprise M4000/M5000/M8000/M9000 and SPARC M10-4S/M12-2S on the admin server. Each chassis name must be unique within the system.
The first character must be alphabetic, and the name can contain up to 10 alphanumeric characters and hyphens ("-").
These IP addresses can be used to communicate with the admin server.
Set it to lan#0 of XSCF.
Name of the user account used to log into XSCF and gain control over the managed server.
A user account with "platadm" privileges within XSCF must be specified.
This name can contain up to 31 alphanumeric characters, hyphens ("-"), and underscores ("_").
The user name reserved for the system cannot be used. Create a different user name.
For details, refer to the XSCF manual.
Password used to log into the remote management controller with the above user name.
The user password can contain up to 32 alphanumeric characters, blank spaces (" "), and any of the following characters.
"!", "@", "#", "$", "%", "^", "&", "*", "[", "]", "{", "}", "(", ")", "-", "+", "=", "~", ",", ">", "<", "/", "'", "?", ";", ":"
The destination for SNMP traps sent by XSCF should be set to the admin server's IP address.
Name of the SNMP community used to communicate with XSCF.
This community name can contain up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-").
Changing Monitoring Timeout Values of SPARC M10-4S/M12-2S Power Operations
When using SPARC M10-4S/M12-2S, the length of time from starting to completion of power operations increases proportionally to the scale of Building Block configurations. Estimate the timeout values based on actual measured values, by performing power operations with an actual machine, after creating Building Block configuration environments.
The timeout values are changed for all M10-4S/M12-2S managed by the manager. When there are servers in multiple Building Block configurations, estimate the timeout values using the largest Building Block configuration environment.
When changing the timeout value, create the following definition file:
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
power_timeout.rcxprop
In the definition file, enter the configuration information (model name, timeout value of server powering on, timeout value of server powering off, etc.) for each server in a single line, separated by commas (","). Each line is entered in the following format.
model,boot_timeout,shutdown_timeout |
Blank spaces before and after commas (",") are ignored.
When adding comments, start the line with a number sign ("#").
Specify the following items.
Enter the model name of the server to change the timeout value for. Enter M10-4S/M12-2S.
Enter the timeout value for powering on of the server.
Enter an integer. The unit is seconds.
When descriptions other than the above are entered, the default timeout value is used. (default value: 2700 seconds)
Enter the timeout value for powering off of the server.
Enter an integer. The unit is seconds.
When descriptions other than the above are entered, the default timeout value is used. (default value: 1200 seconds)
Example
M10-4S,2700,1200 |
It is not necessary to restart the manager after creating or modifying definition files. The entered descriptions are reflected after modification of definition files.
