Designing and Implementing a Junos Node Unifier Network

Verification
Step-by-Step
Procedure
rib-groups jnu {
import-rib [ jnu-vrf.inet.0 inet.0 ];
import-policy jnu-management;
}
}
routing-instances {
jnu-vrf {
/* Routing-instance containing uplink to controller */
instance-type vrf;
interface ae63.16385;
route-distinguisher 192.168.0.3:1;
vrf-import reject-all;
vrf-export reject-all;
routing-options {
routing-options {
static {
rib-group jnu;
route 169.37.0.1/32 next-hop 192.168.0.1;
route 132.0.1.1/32 next-hop 192.168.0.1;
}
}
}
}
}
Commit the Configuration
JNU uses commit scripts to automate the commit process on the controller and satellite
devices. You commit a configuration for the satellite devices from the controller. Each
satellite device inspects the candidate configuration for errors.
Modify and commit configuration changes only on the controller. When you commit a
configuration on the controller, the flow of the commit process on the controller is as
follows:
1. To commit the new configuration on the controller and on all satellite devices:
user@jnu1-ctrlr> op jnu-commit
The new configuration is validated on each satellite device.
2. If all the satellite devices successfully validate the new configuration, the controller
runs the commit script and displays the following message:
jnu1-sat-ex1:
Configuration check succeeds
jnu1-sat-qfx2:
Configuration check succeeds
• Verifying That Satellite Devices Are Active on page 81
Verifying That Satellite Devices Are Active
Purpose Verify that satellite devices are active.
Copyright © 2013, Juniper Networks, Inc.
Chapter 9: Setting Up a Basic JNU Implementation
81