Prestaging Devices Overview
In the Junos Space Connectivity Services Director product, prestaging takes the devices already under Junos Space management and prepares them for service activation. The prestaging process discovers network provider edge (N-PE) devices in the Junos Space database and assigns roles to those devices and their interfaces. N-PE routers and user-to-network interfaces (UNIs) are basic building blocks required for Layer 2 and Layer 3 provisioning.
The Connectivity Services Director application does not support provisioning for J Series devices.
The Junos Space software makes it easy to complete all the prestaging activities you need for up to several hundred devices.
Prestaging uses the Connectivity Services Director application to automatically determine the role of a router based on rules that exist in the system. If a router is an N-PE router, the Junos Space software assigns it the N-PE role. The Junos Space software qualifies each interface on the N-PE router to be a serviceable UNI.
N-PE and UNI recommendations made automatically by the Connectivity Services Director application are appropriate for most situations. In some networks, however, you might need to make some exceptions. You might have recommended N-PE devices that you don’t want to assign the N-PE role for provisioning. In addition, you might want to exclude some interfaces from qualification as UNIs.
Although the prestaging mechanism is automatically run in the background by default in the Connectivity Services Director application of Connectivity Services Director, you can manually configure the prestaging settings by using the Services Activation Director GUI, which provides the prestaging workspace.
To prestage devices while accepting all recommendations made by the Connectivity Services Director application, see Discovering and Assigning All N-PE Devices. To make exceptions to the Connectivity Services Director recommendations, see Discovering and Assigning N-PE Devices with Exceptions.
After a device is prestaged in Connectivity Services Director, the prestaging job is not initiated on the same device again. When a device notification is received by the application, Connectivity Services Director synchronizes the prestaging database on the UI interfaces. If a mismatch is detected in the UNI status of the interface in Connectivity Services Director database and the UNI status of the interface on the device (caused by the application being down or network accessibility problems), the synchronization of the UNI interface might not occur. In such a case, the synchronization operation occurs when a configuration- commit on the device is done the next time. To manually resolve this discrepancy in the UNI status of the interface, you can unassign the UNI role of the interface, which causes prestaging to perform a synchronization.