The exclusive candidate configuration mode is the only supported candidate configuration mode for NISH client multinode operation.
To access the exclusive candidate configuration mode, use the explicit edit-config exclusive command or the implicit configure exclusive command.
When the operator tries to access the exclusive candidate configuration mode within a multinode context, the NISH client attempts the following actions:
connects to each SR OS node prompting for authentication credentials, if required
obtains an exclusive lock on all the nodes
A warning is displayed for every node for which the NISH client cannot obtain an exclusive lock. The operator can optionally continue the configuration activities with the remaining nodes or exit from configuration mode.
A list of the nodes for which the NISH client has successfully obtained an exclusive candidate configuration lock is stored in memory, and the MD-CLI configuration commands are executed against this set of nodes.
Any node that is added, removed, renamed, or re-labeled using the NISH connections file or from the NISH manager while the exclusive lock remains in force, is ignored until the operator returns to the operational mode.
When the operator is presented with the exclusive configuration mode, the prompt changes. When the operator leaves the exclusive configuration mode, all candidate configurations on all nodes are discarded.