Cluster and package status in MC service guard cluster

Below table will explain what is the cluster and package status (required state) at the time of any cluster configuration change and package configuration change. Hope this will help for system admins.

Task / Change in cluster config	Cluster status / Required Cluster State
Add a new node.	All cluster nodes must be running.
Delete an existing node	A node can be deleted even if it is down or unreachable.
Change maximum configure packages	Cluster must not be running
Change timing parameters	Cluster must not be running
Change cluster lock configuration	Cluster must not be running
Change serial heartbeat configuration	Cluster must not be running.
Change IP address for heartbeats	Cluster must not be running
Change addresses of monitored subnets	Cluster must not be running.

Package Modification	Package status / Package required state
Add a new package	Other packages can be running.
Remove a package.	Package must be halted. Cluster can be running.
Add a new node.	Package(s) may be running.
Remove a node.	Package(s) may be running on different nodes.
Add/remove a new service process	Package must be halted.
Add/remove a new subnet.	Package must be halted. / Cluster may need halting if subnet  is new to the cluster
Add/remove a new EMS resource	Package must be halted. / Cluster may need halting if EMS resource is new to the cluster.
Changes to the run/halt script contents	Recommended that package be halted to avoid any timing problems while running the script.
Script timeouts	Package may be running.
Service timeouts	Package must be halted.
Failfast parameters	Package must be halted.
Auto_Run	Package may be running.
Local LAN failover	Package may be running.
Change node adoption order	Package may be running.