PRIMECLUSTER Web-Based Admin View Operation Guide

2.3.2 NIC switching mode

Note when setting the operating environment for Web-Based Admin View

The setup to automatically make any monitoring node act as a management server (operating modification of the secondary management server) is not validated when making mip used duplex by the NIC switching mode of GLS (Redundant Line Control Function).

While Web-Based Admin View adopts the multi-cast IP address for selecting the secondary management server, the NIC switching mode of GLS does not support this multi-cast IP address. Therefore, when the NIC switching is done by GLS, the primary management server is not switched over to the secondary server.

Note when setting IP address

There are two types of IP addresses that can be set to take over for the NIC switching method by GLS.

• In case of logical IP address takeover

  Make both the logical and physical IP addresses duplex.

• In case of physical IP address takeover

  Make only the physical IP address duplex.

When the IP address, which is made duplex by GLS, is used as a takeover IP address for the cluster system operation (userApplication), the monitoring and the business operation from Web-Based Admin View might be stopped because of the state transition. Accordingly, it is necessary to set up the IP address, which is constantly available regardless of the state transition, to mip or httpip.

The IP address setup varies as described below depending on the fact if the management server (the node operated by Web-Based Admin View) is used as a cluster system node.

1. When the management server is used as a cluster system node
   • In case of the logical IP address takeover

     Only the physical IP address can be set.

   • In case of the physical IP address takeover

     No IP address can be set.

2. When the management server is not used as a cluster system node

   Since the state transition of the cluster system does not affect on the Web-Based Admin View operation, either logical IP address or physical IP address can be set.

3-tier architecture model

In this model, the IP address setup varies depending on the node roles.

1. In case of management server

   Either duplex logical IP address or physical IP address can be set up by either logical IP address takeover or physical IP address takeover.

2. In case of monitoring node

   The duplex physical IP address is set up by the logical IP address takeover.

2-tire architecture model

In this model, the physical IP address is set up by the logical IP address takeover.

Each component and its definition are as follows;

• NIC

  Abbreviation for Network Interface Card. It is inserted into a computer or workstation so that it can be connected to the LAN transmission media.

• Physical IP (address)

  Stands for the IP address assigned to the physical interface.

  Logical IP (address)Stands for the IP address assigned to the logical interface to communicate with other node.

Setup of IP address

Take the following steps to set up the duplex IP address.

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

   Refer to "Stop."

2. Set up IP address

   Execute the following commands on the management server or the monitoring node where the IP address is changed.

   # /etc/opt/FJSVwvbs/etc/bin/wvSetparam mip <mip>

   # /etc/opt/FJSVwvbs/etc/bin/wvSetparam httpip <httpip>

   <mip> indicates mip. Set up either logical or physical IP address.

   <httpip> indicates httpip. Set up either logical or physical IP address.

3. Modify management server

   Change the management server settings on all the management servers and monitored nodes if the changed monitored node acts as a cluster management server as well.

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

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

   For the IP address indicated as <primary management server IP address> and <secondary management server IP address>, set up mip for each management server.

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

   Refer to "Restart."

The NIC switching method takes 10 seconds to 3 minutes (default: 25 - 30 seconds) from the failure occurrence to switchover, and the connection between the client and the management server might be dropped during this time. In such a case, close the active browser, and reconnect to the management server after confirming switchover completion. Otherwise, the connection to the available management server can be established by clicking <Yes> to the 0007 message if it is displayed.

If Client - management server connection time (default: 10 sec.) is extended in the environment setup for Web-Based Admin View, the connection can be sustainable until the NIC switching is completed. On the other hand, the failure detection of the session is delayed in the event of node stop or panic disorder. Based on this fact, the setup of monitoring time should be done.

For this monitoring time of connection, be aware of setting the value (10 - 180 sec.) exceeding the time from occurrence of a NIC failure to completion of switchover.

For the setup of monitoring time, refer to "Environment settings." In the screen of the environment setting screen, up to 60 seconds can only be set at the maximum. Using a command allows a user to set 60 seconds or more.