What is the effect of the Disconnect Cluster Member command?

The effect of the Disconnect Cluster Member command is that it changes the High Availability (HA) mode of the affected unit to standalone. When a cluster member is disconnected, the system operates independently rather than as part of a high-availability pair. This action is important in managing Fortinet devices within a network environment, as it allows for maintenance or troubleshooting of a specific unit without impacting the overall HA group.

In standalone mode, the disconnected unit no longer receives configuration updates from the primary or master unit in the HA cluster, and its failover capabilities are also disabled. Thus, it assumes full control over its operations but loses the benefits of redundancy offered by the HA setup.

The disconnect command does not impact the system hostname, firewall rules, or management access configurations directly in the same way it impacts the HA functionality. The hostname and management IP may remain unchanged, and firewall rules may still exist on the device, but the critical change here is the establishment of standalone operations for that cluster member.