Add a network in a high availability environment

In an existing high availability environment, add a new public network, such as an InfiniBand network.

1. Configure the new network settings on the active management node, where eth2 is the newly added network interface.
   • For Linux, IP addresses are configured in the /etc/sysconfig/network-scripts/ifcfg-eth2 scripts.

     # cat /etc/sysconfig/network-scripts/ifcfg-eth2
     DEVICE=eth2
     BOOTPROTO=none
     ONBOOT=yes
     NM_CONTROLLED=yes
     IPADDR=10.10.10.10
     NETMASK=255.255.255.0
     TYPE=Ethernet
     GATEWAY=10.10.10.2
     IPV6INIT=no
     USERCTL=no
     #ifup eth2

   Note: Use ifconfig to check if the new IP addresses are available, and configure the virtual IP address for the new network.
2. Configure the new network settings on the standby management node, where eth2 is the new added network interface.
   • For Linux, IP addresses are configured in the /etc/sysconfig/network-scripts/ifcfg-eth2 scripts.

     # cat /etc/sysconfig/network-scripts/ifcfg-eth2
     DEVICE=eth2
     BOOTPROTO=none
     ONBOOT=yes
     NM_CONTROLLED=yes
     IPADDR=10.10.10.11
     NETMASK=255.255.255.0
     TYPE=Ethernet
     GATEWAY=10.10.10.2
     IPV6INIT=no
     USERCTL=no
     #ifup eth2

   Note: Use ifconfig to check if the new IP addresses are available.
3. Modify the networks table according to the new network attributes.

   # tabedit networks
   # tabdump networks
   #netname,net,mask,mgtifname,gateway,dhcpserver,tftpserver,nameservers,ntpservers,
   logservers,dynamicrange,staticrange,staticrangeincrement,nodehostname,ddnsdomain,
   vlanid,domain,comments,disable
   "provision","172.20.7.0","255.255.255.0","eth1","172.20.7.2",,,,,,"172.20.7.201-
   172.20.7.254","172.20.7.3-172.20.7.200","1",,,,"private.dns.zone",,
   "newnet","10.10.10.0","255.255.255.0","eth2","10.10.10.10",,,,,,"10.10.10.201-
   10.10.10.254","10.10.10.3-10.10.10.200","1",,,,,,

4. Modify the node attribute to add the new network interface in NIC table for the active management node, standby management node and virtual management node.

   # chdef -t node -o primarymn nicips=’eth0!172.20.7.10,eth1!192.168.1.5,
   eth2!10.10.10.10’ 
   nichostnamesuffixes=’eth0!-eth0,eth1!-eth1,eth2!-eth2’
   # chdef -t node -o backupmn nicips=’eth0!172.20.7.11,eth1!192.168.1.6,
   eth2!10.10.10.11’ 
   nichostnamesuffixes=’eth0!-eth0,eth1!-eth1,eth2!-eth2’
   # chdef -t node -o virtualmn nicips=’eth0:0!172.20.7.12,eth1:0!192.168.1.7,
   eth2:0!10.10.10.12’ 
   nichostnamesuffixes=’eth0:0!-eth0,eth1:0!-eth1,eth2:0!-eth2’

   Where primarymn is the name of your management node, and 10.10.10.10 is its new IP address.

   Where backupmn is the name of your standby management node, and 10.10.10.11 is its new IP address.

   Where virtualmn is the name of your virtual management node, and 10.10.10.12 is the new virtual IP address in this network.
5. Regenerate the host and DNS entry for the management nodes.

   # makehosts primarymn, backupmn, virtualmn
   # makedns primarymn, backupmn,virtualmn

6. Reconfigure the PCMHA service agent to add the new network.

   # pcm-ha-support gendata
   # pcm-ha-support start --service PCMHA

7. Synchronize the /etc/hosts to other nodes in the Platform Cluster Manager Community Edition cluster, where backupmn is the standby management node.

   #updatenode backupmn -F
   #updatenode __Managed -F