| Home Prev |  InCenter 2.2.5 On-Premises Administration Guide
|
Next |
|---|
If centralized management has been disabled using the firewall command localconfiguration -enable but the node has not been deleted from InCenter, changes to the configuration can still be entered using InCenter. It is only when those changes are activated that InCenter will give a message indicating that the node is no longer under centralized management control and the changes cannot be deployed.
After locally ending centralized management control but not deleting the node from InCenter, it is possible to bring back the node under centralized management control again. This is done in different ways, depending on whether it is for a standalone node or an HA pair:
For a Standalone Node
Perform an export operation. This will push the current InCenter database version of the configuration back to the node, overwriting the node's current configuration and bringing it back under centralized management control.
For an HA Pair
In InCenter, force the current HA pair configuration in the InCenter database to be pushed out to the pair by using the node <node-name> export command. For example:
admin@InCenter:/> node my-hapair exportAny configuration changes made to the HA pair while it was not under centralized management control will be lost and these will need to be re-applied in InCenter.
