Disabling and Re-enabling ACM on One Node

Important:

As mentioned in Disabling ACM on All Nodes, disabling ACM does not stop the ACM services which are running when ACM disabled; consequently, if ACM is disabled locally on the currently active node, the node becomes passive. However, those ACM services still running on the previously active but now passive (locally disabled) node could attempt to access some shared files that are also being accessed by the other Orchestrator nodes that have now become active.

Therefore, you should be careful when locally disabling the active node. After you disable ACM locally, stop all Orchestrator services by running the command aspera-orchestrator stop on the active node; this avoids the potential problem of conflicting access as described above.

To disable ACM for one node only, run acmctl with the -d option on that node:
```
# /opt/aspera/acm/bin/acmctl -d
ACM is disabled locally
```

To verify ACM’s status for a disabled node, run the acmctl –i command on that node:

# /opt/aspera/acm/bin/acmctl -i
Checking current ACM status...
Aspera Cluster Manager for orchestrator - status
------------------------------------------ Local hostname: 	haorchestrator1
Active node: 	haorchestrator2 
Status of this node: 	passive
Status file: 	current Disabled globally: 	no
Disabled on this node: 	yes

To re-enable ACM on a node, run the acmctl command with the -e option on the node:
```
# /opt/aspera/acm/bin/acmctl -e
ACM is enabled locally
```