This section explains how to register servers.
Register a server to enable it to be managed by Systemwalker Software Configuration Manager.
Manual registration
Use the Server Information Management command to manually register servers. The kinds of information listed below can be specified when registering a server with the swcfmg_server command Refer to "swcfmg_server (Server Information Management Command)" in the Reference Guide for details.
Perform a connection test whenever you register a server (refer to "swcfmg_connectiontest (Connection Test Command)" in the Reference Guide for details).
Item | Description |
|---|---|
IP address | The IP address connected to the admin LAN. |
Server name | Name of the server. A name can be assigned to the server for management purposes. |
Server group | Server group to which the server belongs. |
Host name | Host name of the server. |
Operating system type | Type of operating system. |
OS architecture | Architecture of the operating system. |
Operating system name | Name of the operating system. |
ServerView Resource Orchestrator
To register a server of ServerView Resource Orchestrator, it is necessary for the L-Server to belong to the L-Platform in ServerView Resource Orchestrator. Perform the operations below using ServerView Resource Orchestrator:
Create an L-Platform
Reconfigure the L-Platform and add the L-Server
Import the L-Server to the L-Platform.
Refer to the following manuals for details: L-Servers that already belong to the L-Platform before installing this product are automatically registered as servers after installation.
"L-Platform" in the ServerView Resource Orchestrator Cloud Edition User's Guide for Tenant Administrators
"L-Platform" in the ServerView Resource Orchestrator Cloud Edition User's Guide for Tenant Users
"Importing to L-Platform" in the ServerView Resource Orchestrator Cloud Edition Operation Guide
OpenStack
To register servers of OpenStack it is necessary to perform discovery of the OpenStack information. The instances of OpenStack are registered as servers after discovery. When the following instances are found during discovery, a server group is automatically created for each instance. The instance is registered as a server that belongs to the automatically created server group.
Instances which are not configured for the stack
Instances created using resource_type with a value other than "OS::Nova::Server" using the Heat template.
The server group name and the server group ID of the automatically created server group are as given below.
Server group name | Server group ID |
|---|---|
No stack (instance ID) | NoStack_instance ID |
