This section explains how to perform admin LAN subnet registration.
Registering admin LAN subnets enables management of managed servers belonging to subnets other than that of the admin LAN.
Apply the Cloud Edition license before registering an admin LAN subnet.
Use the following procedure to register an admin LAN subnet.
From the ROR console menu, select [Settings]-[Admin LAN Subnet].
The [Admin LAN Subnet] dialog is displayed.
Click the [Add] button.
The [Add Admin LAN Subnet] dialog is displayed.
Perform the following settings:
Set the subnet name for registration.
Enter a character string beginning with an alphabetic character and containing up to 16 alphanumeric characters, underscores ("_"), hyphens ("-"), and periods (".").
Configure the network address of the subnet used as the admin LAN.
Enter valid values for the network address.
Enter valid values for the subnet mask.
Enter the settings for the gateway used for communication with the admin server on the admin LAN.
Click the [OK] button.
Information
When registering an admin LAN subnet for the first time, change the simplified DHCP service for Resource Orchestrator to the OS standard DHCP Service.
Resource Orchestrator takes exclusive possession of the OS standard DHCP Service.
Note
It is necessary to perform network settings for each admin LAN subnet so that managed servers belonging to subnets other than the admin LAN can communicate with the admin server.
For details on how to configure the network settings, refer to "Chapter 9 Defining and Configuring the Network Environment" in the "Design Guide CE".
In a clustered manager configuration, when registering an admin LAN subnet for the first time, perform "Settings for Clustered Manager Configurations".
When managing a managed server in a separate subnet from the admin server, an OS standard DHCP server is necessary.
For details, refer to "2.1.1.2 Software Preparation and Checks" or "2.1.2.2 Software Preparation and Checks" in the "Setup Guide CE".
Settings for Clustered Manager Configurations
The following configuration is necessary only when registering an admin LAN subnet for the first time.
[Windows Manager]
Information
When configuring a cluster system in an environment that already has an admin LAN registered, perform steps 5 to 10, and 13.
Allocate the shared disk to the primary node.
Right-click [Services and Applications]-[RC-manager] on the Failover Cluster Management tree, and select [Move this service or application to another node]-[1 - Move to node node_name] from the displayed menu.
The name of the primary node is displayed for node_name.
Delete the registry replication settings from the following "Services and Applications" of the manager.
Based on the following table, delete registry replication for the resources.
x64
Resources for Deletion | Registry Key |
|---|---|
Deployment Service | [HKEY_LOCAL_MACHINE\]SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\ResourceDepot |
[HKEY_LOCAL_MACHINE\]SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\DatabaseBroker\Default | |
PXE Services | [HKEY_LOCAL_MACHINE\]SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\DHCP |
[HKEY_LOCAL_MACHINE\]SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\PXE\ClientBoot\ |
x86
Resources for Deletion | Registry Key |
|---|---|
Deployment Service | [HKEY_LOCAL_MACHINE\]SOFTWARE\Fujitsu\SystemcastWizard\ResourceDepot |
[HKEY_LOCAL_MACHINE\]SOFTWARE\Fujitsu\SystemcastWizard\DatabaseBroker\Default | |
PXE Services | [HKEY_LOCAL_MACHINE\]SOFTWARE\Fujitsu\SystemcastWizard\DHCP |
[HKEY_LOCAL_MACHINE\]SOFTWARE\Fujitsu\SystemcastWizard\PXE\ClientBoot\ |
Perform the following procedure for each of the above resources:
Right-click the target resource on [Other Resources] on the [Summary of RC-manager] displayed in the middle of the [Failover Cluster Management] window, and select [Properties] from the displayed menu.
The [target_resource Properties] window will be displayed.
From the [Root Registry Key] displayed on the [Registry Replication] tab, select the above registry keys and click the [Remove] button.
The selected key is removed from [Root Registry Key].
When deleting the second registry key, repeat step b.
Click the [Apply] button.
The settings are applied.
Click [OK] to close the dialog.
Take the following services of the "Services and Applications" for the manager offline.
Deployment Service
TFTP Service
PXE Services
Register the admin LAN subnet.
On the primary node, bring the shared disk of the manager online, and take all other cluster resources offline.
Open [Services] from [Administrative Tools] on the Windows Control Panel, and then configure the startup type of DHCP Server service as "Manual" on the [Services] window.
From the [Services] window, stop the DHCP Server service.
Using Explorer, copy the following folder from the local disk of the primary node to the folder on the shared disk.
Local Disk (Source) | Shared Disk (Target) |
|---|---|
%SystemRoot%\System32\dhcp | Drive_name:\Fujitsu\ROR\SVROR\dhcp |
Example
When the OS has been installed on the C drive, it is %SystemRoot%C:\Windows.
Configure access rights for the folder for the DHCP Server that was copied to the shared disk. Execute the following command using the command prompt of the primary node:
>cacls Drive_name:\Fujitsu\ROR\SVROR\dhcp /T /P "NT AUTHORITY\SYSTEM:F" "BUILTIN\Administrators:F" "NT SERVICE\DHCPServer:F" <RETURN> |
Add the DHCP Server to "Services and Applications" for the manager.
Right-click [Services and Applications]-[RC-manager], and select [Add a resource]-[Other Resources]-[1 - Add a DHCP Service] from the displayed menu.
A [New DHCP Service] will be created in the [DHCP Service] in [Summary of RC-manager].
Right-click the [New DHCP Service], and select [Properties] from the popup menu.
The [New DHCP Service Properties] window will be displayed.
Change the [Resource Name] on the [General] tab, and set the paths given in the following table.
Item | Value to Specify |
|---|---|
Database path | Drive_name:\Fujitsu\ROR\SVROR\dhcp\ |
Monitoring file path | Drive_name:\Fujitsu\ROR\SVROR\dhcp\ |
Backup path | Drive_name:\Fujitsu\ROR\SVROR\dhcp\backup\ |
After making the settings, click the [Apply] button.
From here, the explanation is made assuming that [Resource Name] was set as [DHCP Server].
On the "Resource" of the [Dependencies] tab, select the following name, and select AND from "AND/OR".
Shared Disks
Network Name
Admin LAN IP Address
Click the [Apply] button.
Click the [OK] button.
Configure the registry replication settings from the following "Services and Applications" of the manager.
Following the table in step 2, set replication of the registry of the resource.
Perform the following procedure for each resource.
Right-click the target resource on [Other Resources] on the [Summary of RC-manager] displayed in the middle of the [Failover Cluster Management] window, and select [Properties] from the displayed menu.
The [target_resource Properties] window will be displayed.
Click the [Add] button on the [Registry Replication] tab.
The [Registry Key] window will be displayed.
Configure the above registry key in [Root registry key].
Click the [OK] button.
When configuring the second registry key as well, repeat steps b to d.
After configuration of the registry keys is complete, click the [Apply] button.
Click [OK] to close the dialog.
Configure the dependencies of the resources of the manager "service or application".
Configure the dependencies of resources based on the following table.
If some resources have been configured, select AND from [AND/OR] and add the dependent resource.
Resource for Configuration | Dependent Resource |
|---|---|
PXE Services | DHCP Server |
Restart the manager.
Right-click [Services and Applications]-[RC-manager] on the Failover Cluster Management tree, and select [Bring this service or application online] from the displayed menu.
[Linux Manager]
Information
When configuring a cluster system in an environment that already has an admin LAN registered, in addition to the installation procedure for the cluster system, perform steps 1 to 2 and 4 to 11.
In that case, set the manager that is operating now as the primary node of the cluster system.
Stop cluster applications.
Use the cluster system's operation management view (Cluster Admin) and stop the manager cluster service (cluster application).
Mount the shared disk (Primary node)
Mount the shared disk for managers on the primary node.
Stop automatic startup of the dhcpd service (Primary node and Secondary node)
Disable automatic startup of the dhcpd service by executing the following command.
# chkconfig dhcpd off <RETURN> |
Copy dynamic disk files (Primary node)
Copy the files and directory on the local disk of the primary node to the shared disk for managers.
Execute the following command:
# tar cf - copy_target | tar xf - -C Shared_disk_mount_point/Fujitsu/ROR/SVROR <RETURN> |
Files and Directory to Copy
- /etc/dhcpd.conf (*1)
- /etc/dhcp/dhcpd.conf (*2)
- /var/lib/dhcpd
*1: When using Red Hat Enterprise Linux 5
*2: When using Red Hat Enterprise Linux 6
After copying the files, change source_file_name by executing the following command.
Make sure a name like "source_file_name_old" is specified for the target_file_name.
# mv -i source_file_name target_file_name <RETURN> |
Configure symbolic links for the shared disk (Primary node)
Configure symbolic links from the files and directory on the local disk of the primary node for the files on the shared disk.
Execute the following command:
# ln -s shared_disk local_disk <RETURN> |
Shared Disk | Local Disk |
|---|---|
Mount_destination_of_shared_disk/Fujitsu/ROR/SVROR/etc/dhcpd.conf (*1) | /etc/dhcpd.conf |
Mount_destination_of_shared_disk/Fujitsu/ROR/SVROR/etc/dhcp/dhcpd.conf (*2) | /etc/dhcp/dhcpd.conf |
Mount_destination_of_shared_disk/Fujitsu/ROR/SVROR/var/lib/dhcpd | /var/lib/dhcpd |
*1: When using Red Hat Enterprise Linux 5
*2: When using Red Hat Enterprise Linux 6
Change the settings of the DHCP service (Primary node)
Change the following files when registering the admin LAN subnet, and set the takeover logical IP address after the change to the DHCP server.
Red Hat Enterprise Linux 5
/etc/dhcpd.conf
Red Hat Enterprise Linux 6
/etc/dhcp/dhcpd.conf
Add the following lines, and set the takeover logical IP address.
option dhcp-server-identifier takeover logical IP address; |
Example
When the takeover logical IP address is 192.168.4.100
# |
Unmount the shared disk. (Primary node)
Unmount the shared disk for managers from the primary node.
Mount the shared disk (Secondary node)
Mount the shared disk for managers on the secondary node.
Back up files and configure symbolic links for the shared disk (Secondary node)
Perform step b. of step 4 and back up the files on the local disk.
Perform step 5 and configure symbolic links for the shared disk.
Unmount the shared disk. (Secondary node)
Unmount the shared disk for managers from the secondary node.
Start cluster applications.
Use the cluster system's operation management view (Cluster Admin) and start the manager cluster service (cluster application).
Register the admin LAN subnet.
