Register Systemwalker Operation Manager with the cluster system from PRIMECLUSTER's Web-Based Admin View.
The registration procedure is shown below.
Note
The assignment of active and standby nodes may be determined according to the order of node selection. Be careful not to make a mistake in selecting nodes.
1) Stop RMS
Before registering the cluster application, use either ClusterAdmin or the hvdisp command to check that RMS is not running. If RMS is running, stop it on every node in the cluster system using either ClusterAdmin or the hvshut command.
Refer to the PRIMECLUSTER manual for details on the hvdisp and hvshut commands.
Example of how to stop RMS with the hvshut command:
# /opt/SMAW/bin/hvshut -a |
2) Start the userApplication Configuration Wizard window.
Start the top menu for PRIMECLUSTER's Web-Based Admin View and select Global Cluster Services.
Select userApplication Configuration Wizard from the Global Cluster Services window.
The userApplication Configuration Wizard window will be displayed.
3) Create resources.
Select Create Resource from the userApplication Configuration Wizard window, and create the following resources:
Fsystem resources
Inheritance network resources
Procedure resources
Create Fsystem resources.
Perform the following settings in the displayed window:
Create resource window.
Resource type: "Fsystem"
Resource name: Any resource name
Select SysNode window
Select the active and standby nodes.
The first node selected will be the active node, and the next node selected will be the standby node.
Select mount point window
Select the mount point for the shared disk.
Select attributes window
Use the default values.
Confirm registration window
Check the registered contents, and click the Registration button.
Create inheritance network resources.
Perform the following settings in the displayed window:
Create resource window.
Resource type: "Ipaddress"
Resource name: Any resource name
Select SysNode window
Select the active and standby nodes.
The first node selected will be the active node, and the next node selected will be the standby node.
Select takeover IP address window
Select "IP_Address Takeover".
Select interface window
Select the name of the network interface that has been assigned to the logical IP address.
Select IP address and host name window
Specify the logical IP address and host name.
Confirm registration window
Check the registered contents, and click the Registration button.
Create procedure resources.
Perform the following settings in the displayed window:
Create Resource window
Resource type: "Procedure"
Resource name: Any resource name
Select SysNode window
Select the active and standby nodes.
The first node selected will be the active node, and the next node selected will be the standby node.
Select procedure class window
Select the "SystemState3" resource class specified in "4.1.2 Registering state transition procedures."
Select procedure resource window
Select the resource key specified with the "-k" option in "4.1.3 Registering resources that use state transition procedures."
Confirm registration window
Check the registered contents, and click the [Registration] button.
4) Create cluster applications.
Select Create userApplication in the userApplication Configuration Wizard window.
Perform the following settings in the displayed windows:
Setup userApplication name and operation method window
userApplication name: Cluster application name
Resource name: "standby"
Select SysNode window
Select the active and standby nodes.
The first node selected will be the active node, and the next node selected will be the standby node.
Set up attribute window
It is recommended that AutoSwitchOver be set to "HoseFailure|ResourceFailure". Change this value to match the actual cluster system operations.
Select Resource window
Select all of the resources to be registered with the user application.
Confirm registration window
Check the registered contents, and click the [Registration] button.
Registered user applications will be displayed for each node in the list on the left-hand side of the window.
For N:1 active/standby configuration, repeat step 2) "Create resources" and step 3) "Create cluster applications" N times (once for each active node) and register N cluster applications to match the operating environment.
For dual node mutual standby configuration, repeat step 2) "Create resources" and step 3) "Create cluster applications", and register two cluster applications. In the Select SysNode window, the active and standby nodes must be registered in the correct order.
5) Set up dependency relationship between cluster applications
Perform this procedure for N:1 active/standby configuration only.
Set up exclusive control so that multiple active nodes do not start on the same cluster node at the same time.
Select Set up dependency between userApplication in the userApplication Configuration Wizard window.
Specify Exclusivity of userApplication setting.
Add the N Operation Manager cluster applications that have been registered to the group.
