Committing configuration changes in a multinode environment from the NISH client is an atomic operation. This means that at the end of a commit operation for a specified set of nodes, every node successfully commits the configuration or all the nodes return to their configuration state before the commit.
To commit a configuration change in a multinode group, every node in the group must have automatic saving of configuration changes enabled in the MD-CLI. This is enabled by configuring the auto-config-save command in the configure system management-interface cli md-cli context on each device and committing this configuration change. The multinode commit process driven from the NISH client uses standard MD-CLI features to achieve the atomic commit. There are two phases to the multinode commit operation:
conditional commit and validation phase (commit confirmed command)
confirmation phase (commit confirmed accept command)
At each stage, the nodes are processed in turn to ensure they are all in the expected state before the next stage.
