Reconfiguration of the Management and Quorum Network

Virtual SMU Installation and Upgrade Guide for Hitachi NAS Platform

Version
15.1.x
Audience
anonymous
Part Number
MK-92HNAS074-20

Verify/Relocate the location of the adminEVS

  1. Verify and Relocate, as necessary, the location of the adminEVS:
    1. Navigate to Home > Server Settings > EVS Management.
    2. Take note of the name of the adminEVS.
    3. Verify the location of the adminEVS.
    4. If the adminEVS is NOT assigned to Node 1, perform the following steps:
      1. Navigate to Home > Server Settings > EVS Migration
      2. In the EVS Migration section, select Migrate EVS.
      3. In the dropdown, select the adminEVS name.
      4. In the next dropdown, select Node 1.
      5. Click <Migrate>.
      6. When the adminEVS migration to Node 1 has been completed successfully, proceed to the next step.

Additional adminEVS IP addresses on eth1

  1. Navigate to Home > Network Configuration > IP Addresses.
  2. Remove all IP addresses except 192.0.2.x on the eth1 port of the nodes.

Reconfigure IP addresses on the cluster nodes

  1. From the IP Addresses screen, click Add.
  2. In the following screen, enter the new adminEVS IP address and netmask.
    1. Port: eth1
    2. IPv4: IP Address
    3. IPv4: Netmask (select the appropriate netmask from the dropdown)
    4. Click OK.
  3. From the IP Addresses screen, click Details for the Node 1 node address (typically 192.0.2.200).
  4. In the following screen, enter the new cluster node IP address and netmask.
    1. IPv4: IP Address
    2. IPv4: Netmask (select the appropriate netmask from the dropdown)
    3. Click OK.
  5. Click Details for the Node 2 node address (typically 192.0.2.201)
  6. In the following screen, enter the new cluster node IP address and netmask.
    1. IPv4: IP Address
    2. IPv4: Netmask (select the appropriate netmask from the dropdown)
    3. Click OK.
  7. Repeat the previous step for each of the remaining nodes in the Cluster.

Reconfigure Ethernet Cabling

  1. Disconnect all cables from the SMU and Nodes to the Private Management Switch.
  2. Connect the Physical SMU eth0 to the Customer Management Network (this should already be in place)
  3. Connect each of the Nodes to the Customer Management Network:
    1. If a customer network drop exists on eth0 of the Node, move the cable to eth1 on each Node.
    2. If a customer network drop does NOT exist on eth0 of the Node, then connect a new customer network drop to eth1 on each Node.

Change the Cluster Managed Server IP Address

  1. Navigate to Home > SMU Administration > Managed Servers
  2. Click on Details for the Cluster that was just changed. (typically 192.0.2.2)
  3. Change the Server IP Address from 192.0.2.x to the new adminEVS IP address
  4. The Server Username should be supervisor.
  5. Unless changed, the Server Password should be supervisor.
  6. Click OK

The Managed Servers screen should reappear and the Cluster should now show the new adminEVS IP address and Green status.

Remove adminEVS IP addresses on eth0 of the Nodes

  1. From the IP Addresses screen, delete all IP addresses on the eth0 port of the nodes.
    Note: All external communication with applications or users will now be accomplished via the customer network on the eth1 port.

Remove Private Management Node IP addresses on eth1 of the Nodes

  1. From the IP Addresses screen, delete all IP addresses on the eth1 port of the nodes.
    Note: All management and quorum communication between the SMU and the Cluster will now be accomplished via the customer network on the eth1 port.

Reconfigure the Cluster Management and Quorum

  1. Switch to the browser session on the External SMU.
  2. Navigate to Home > Server Settings > Cluster Configuration.
  3. Verify that the SMU can see the Cluster Nodes.
  4. In the Quorum Device section, click Remove to delete the old 192.0.2.1 quorum device.
  5. Click Add.
  6. A new screen with the SMU Quorum with the latest customer-facing IP address should appear.
  7. Select the new SMU Quorum device and click OK
  8. The Cluster should now show a Robust Health.