PRIMECLUSTER Web-Based Admin View Operation Guide
Contents Index PreviousNext

Part 4 Web-Based Admin View operating setup> Chapter 7 Web-Based Admin View setup modification

7.3 Management server

When the management server and the network address used on this management server have to be changed, be sure to set up the following:

There are two types of method: to set up by executing a command on each management server or monitoring node, or to set up from the environment setup screen.

These settings are made in a static operation mode where primary and secondary management servers are fixed. For the setup of dynamic operation of the secondary management server, refer to "Secondary management server automatic migration."

Setup by command

Procedure:

  1. Stop Web-Based Admin View on all the management servers and monitored nodes.

    Refer to "Stop."

  2. Set up the IP address of the management server.

    Execute the following command for all the management servers and monitoring nodes:

    # /etc/opt/FJSVwvbs/etc/bin/wvSetparam primary-server <IP address of primary management server>

    # /etc/opt/FJSVwvbs/etc/bin/wvSetparam secondary-server <IP address of secondary management server>

    Example:

    When the IP addresses of primary management server and secondary server are set to "10.20.30.40" and "10.20.30.41":

    # /etc/opt/FJSVwvbs/etc/bin/wvSetparam primary-server 10.20.30.40

    # /etc/opt/FJSVwvbs/etc/bin/wvSetparam secondary-server 10.20.30.41

    If the primary management server is only used for a management server, set the IP address of the secondary management server for that of the primary one.

  3. Change mip (IP address for identifying own host) on the management servers.

    To change the network address for the management server, change mip to the IP address set up in procedure2 on the primary and secondary management servers.

    Refer to "Network address."

  4. Change httpip (IP address used for a client) on the management servers.

    To change the network address for the management server, change httpip to mip or the IP address that is connected from the client on the primary and secondary management servers.

    Refer to "Multi-network between server and client by classified use."

  5. Restart Web-Based Admin View on all the management servers and monitored nodes.

    Refer to "Restart."

Setting from the environment setup screen

Procedure:

  1. Start up the Web-Based Admin View screen.

    Access to the primary management server from the Web browser.

  2. Set up the IP address of the management server.

    Select the [Web-Based Admin View tools]-[System environment] tab on [Environment settings] to set up for [IP address] of the [Primary server] property and [Secondary server] property.

    If the primary management server is only used for a management server, set the IP address of the secondary management server for that of the primary one.

    Note that [IP address] of the [Secondary server] property is not available if [Secondary management server automatic migration] is set to "Yes."

  3. On the management servers, change mip ("IP address for identifying own host").

    Change mip on the primary and secondary management servers. Refer to "Network address."

  4. On the management servers, set up httpip ("IP address used for a client").

    Change httpip to mip or to IP address at user's discretion. Refer to "Multi-network between server and client by classified use."

    The httpip value cannot be set up from the environment setup screen. Use a wvSetparam command. Refer to "Multi-network between server and client by classified use."
  5. Login to the Web-Based Admin View screen, again.

    When the environment setup is completed, the message "0051 In order to make the settings valid, restart Web-Based Admin View and reconnect it. Are you sure?" appears. If you need to validate the currently chosen value, select [Yes]. Log off, and then login the management server again. If [No] is selected, the setup remains invalid.

    Refer to the message "0051" of "Information message."

The modifications may not get valid on the environment setup screen if the monitoring node is inactive. In such a case, refer to "Setup by command" above.

Contents Index PreviousNext

All Rights Reserved, Copyright(C) FUJITSU LIMITED 2005