Top
PRIMECLUSTER  Web-Based Admin ViewOperation Guide 4.6
FUJITSU Software

2.4.1 Management server configuration

This section explains the configuration method of the 3-tier architecture where the management server is independent of monitoring nodes.

It is not necessary to follow this procedure if the management server is set up when installed. Take the following steps according to below "Verification " to check if the setup is correctly done.

Verification

Take the following procedure to check if the setup is correctly done.

Check if the management server is configured for the 3-tier model.

Take the following procedure to check if the management server is configured for the 3-tier model.

  1. Check if the primary management server recognized by each node is identical with the active primary management server.

    Execute the following command on the management server and all monitored nodes.

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam primary-server 

    Confirm if the displayed IP address corresponds to mip (the IP address for identifying own host) of the active primary management server.

    If not, the primary management server is not correctly configured. Set up the configuration according to "Configuration procedure of the management server" of "Configuration procedure".

  2. Check if the secondary management server recognized by each node is identical with the active secondary management server.

    Execute the following command on the management server and all monitored nodes.

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam secondary-server

    Confirm if the displayed IP address corresponds to mip of the active secondary management server.

    If not, the secondary management server is not correctly configured. Set up the configuration according to "Configuration procedure of the management server" of "Configuration procedure".

Check if the topology is multi-network by classified use.

This case is applicable only to the multi-network by classified use.

Verification should be done on all primary and secondary management servers.

  1. Check if the mip value is correctly set.

    Execute the following command:

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam mip

    Confirm if the displayed IP address corresponds to mip (the IP address for identifying own host) on the active management server.

    If not, the mip value of the active management server is not correctly set. Set up the mip value according to "Configuration procedure of multi-network by classified use" of "Configuration procedure".

  2. Check if the httpip value is correctly set.

    Execute the following command:

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam httpip

    Confirm if the displayed IP address corresponds to httpip (the IP address used for client) from the active management server.

    If not, the httpip value of the active management server is not correctly set. Set up the httpip value according to "Configuration procedure of multi-network by classified use" of "Configuration procedure".

  3. Check if the topology is multi-network by classified use.

    Compare the output (mip) done by Step 1 with that (httpip) by Step 2.

    If both values are the same, the topology of multi-network is not configured. Set up the configuration according to "Configuration procedure of multi-network by classified use" of "Configuration procedure".

Configuration procedure

Take the following steps to configure the management server.

Point

Modifications should be done only to the values of the management server and the monitoring node where the setup was incorrect.

  1. Configure the management server.

    Set up the IP addresses of the primary and secondary management server.

    This setup should be done only when creating multi-network between the management server and the client by classified use.

    Configuration procedure of the management server:

    Take the following steps to set up configuration according to "Setup by command" of "7.3 Management server". Regarding this setup, Step 1, and 2 should be done on all management servers and monitoring nodes.

    1. Stop Web-Based Admin View according to Step 1.

    2. Set up the IP address of the management server according to Step 2.

    Configuration procedure of multi-network by classified use:

    Take the following steps to set up configuration according to "Setup by command" of "7.5 Multi-network between server and client by classified use". Regarding this setup, only Step 1 should be done on all management servers.

    • Set up httpip according to Step 1.

      Modify httpip on the management servers.

  2. To validate the setup, restart Web-Based Admin View on all management servers and monitoring nodes.

    Refer to "6.2 Restart".

Note

In the file (hosts) on all the nodes configuring the cluster system and the management server, define the host information (IP address, host name) on all these nodes by a tool (e.g. vi(1). The hosts file is "/etc/inet/hosts" on Solaris OS, but it is "/etc/hosts" on Linux(R).