Designing and Implementing a Junos Node Unifier Network

CHAPTER 7
Committing Configurations
• Commit Process for Satellites Already Connected to the Controller on page 45
• Commit Process for Satellite Devices That Come Online After the Commit Process on
the Controller on page 46
• Returning to a Previously Committed Junos OS Configuration on page 47
Commit Process for Satellites Already Connected to the Controller
JNU uses commit scripts to automate the commit process on the controller and satellite
devices. You commit configurations for the satellite devices from the controller. You
should modify and commit configuration changes for satellite devices only on the
controller.
Copyright © 2013, Juniper Networks, Inc.
When you commit a configuration on the controller, the flow of the commit process on
the controller is as follows:
1. Enter the following command on the controller:
user@jnu-ctrlr> op jnu-commit
2. The controller polls each satellite device to verify that the device is reachable.
3. The controller sends the new satellite configuration to each satellite device by using
the NETCONF XML management protocol.
4. The controller runs the remote procedure call (RPC) validate process on each satellite
device to validate the new configuration.
5. If all the satellite devices successfully validate the new configuration, the controller
runs the commit script, which runs the RPC commit process on all satellite devices.
When the process is complete, the controller displays the following message:
jnu1-sat-ex1:
Configuration check succeeds
jnu1-sat-qfx2:
Configuration check succeeds
If the new configuration is not successfully validated on all satellite devices in the JNU
network, the commit process stops and the controller displays an error message.
45