Once the HA pair is under InCenter, there are two kinds of changes that can be performed using the CLI:
Changes to HAPair Context Objects
Changes are made to the HAPair object in the same way as changes are made to a StandaloneNode object. However, when these changes are deployed, they are automatically applied to both nodes in the pair.
Changes to HAMemberNode Context Objects
Each HAPair created will have two HAMemberNode objects associated with it, each corresponding to a node in the pair. Certain configuration objects are not duplicated between nodes in the pair and these must be changed on each node individually. This is done by changing the CLI context to the relevant HAMemberNode object and then entering the required commands.
Editing the Configuration of an HAPair Object
As an example of changing an HAPair configuration, to add a new IP address object to both nodes in the HA pair, the command sequence could be:Change the CLI context to be the pair:
admin@InCenter:/> cc HAPair my-hapair
admin@InCenter:/my-hapair>
Add the IP address:
For NetWall nodes:
admin@InCenter:/my-hapair> add IP4Address
Name=my-address1
Address=192.0.2.1
Added IPAddress my-address1
For NetShield nodes:
admin@InCenter:/my-hapair> add IPAddress
Name=my-address1
Address=192.0.2.1
Added IPAddress my-address1
Deploy the change to the pair:
admin@InCenter:/my-hapair> activate Activate successful admin@InCenter:/my-hapair> commit Committed
If no other changes need to be made to the HA pair, change the CLI context back to the default:
admin@InCenter:/my-hapair> cc
admin@InCenter:/>
Editing the Configuration of an HAMemberNode Object
It is possible to edit the configuration of just one of the members in an HA pair. This is done by changing the CLI context to be the individual HAMemberNode and then applying the change.Take the following example for a NetWall node:
If a new EthernetDevice object has to be added to just one of the nodes in an HA pair. In this case, the change must be performed on the relevant HAMemberNode object since EthernetDevice is one of the configuration object types that is not available in the HAPair object.
This configuration change can be done using the following steps:
Change the CLI context to be the HAMemberNode object:
admin@InCenter:/> cc HAMemberNode my-node1
admin@InCenter:/my-node1>
Add the EthernetDevice object with an identifier:
admin@InCenter:/my-node1> add EthernetDevice
Name=my-ethdevice
HWIdent=pci=77:77.7
Added EthernetDevice my-ethdevice
admin@InCenter:/my-node1>
Deploy the change to the node:
admin@InCenter:/my-node1> activate Activate successful admin@InCenter:/my-node1> commit Committed
HA Pair Synchronization
When an HA pair is under InCenter control, the following should be noted:Auto-synchronization of the HA pair in the firewalls is disabled.
InCenter deploys the configuration to each member of the pair in sequence.
The order of deployment can be set in the HAPair object.