Disable a Chassis Cluster
Learn how to disable a chassis cluster.
To return a Firewall to standalone operation or to remove a node from a chassis cluster, you must disable chassis clustering.
Be aware that disabling the cluster can cause the node to fail to load its
configuration if the configuration contains the automatically generated
node0 and node1 groups that define key
resources.
Since these groups are created only for clustered operation, they are removed when the cluster is disabled. As a result, the remaining configuration may become inconsistent and require manual cleanup or validation.
In such events, the node will come up partially amnesiac (logins will be remembered).
To disable chassis cluster, enter the following command:
{primary:node1}
user@host> set chassis cluster disable reboot
Successfully disabled chassis cluster. Going to reboot now.After the system reboots, the chassis cluster is disabled.
After the chassis cluster is disabled using this CLI command, you do not have a similar CLI option to enable it back.
To restore the chassis cluster, set the cluster-id by entering the following command:
{primary:node1}
user@host> set chassis cluster cluster-id cluster-id-number node node-number rebootWhen setting the cluster, the secondary node PFEMAN process will restart.
You can also use the below CLI commands to disable chassis cluster:
-
To disable cluster on node 0:
user@host> set chassis cluster cluster-id 0 node 0 reboot -
To disable cluster on node 1:
user@host> set chassis cluster cluster-id 0 node 1 rebootSetting cluster-id to zero disables clustering on a device.