Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Router Initialization Scripts with NIC Configuration Scenarios

 

The NIC resolutions map VRs to SAEs. For these resolutions, use a router initialization script that associates each VR with the SAE that manages it. Which router initialization script you use depends on whether the SAE obtains IP pools from JunosE VRs:

  • poolPublisher router initialization script—Use when the SAE obtains local IP pools locally from JunosE VRs.

  • iorPublisher router initialization script—Use when the router is one of the following:

  • JunosE routers that do not supply IP addresses from local pools

  • devices running Junos OS

  • CMTS devices

    These devices do not supply IP addresses from local pools in your network.

Table 1 lists which type of initialization script should be used with the various NIC configuration scenarios. The OnePopLoginPull scenario does not require an initialization script.

Table 1: Type of Router Initialization Script to Use for NIC Configuration Scenarios

poolPublisher

iorPublisher

poolPublisher or iorPublisher

One Pop

OnePopDnSharedIp

OnePopAcctId

OneLoginPull

OnePopAllReams

 

OnePopPcmm

OnePopDynamicIp

 

OnePopPrimaryUser

OnePopLogin

 

OnePopSharedIp

MultiPop

 

OnePopStaticRouteIp

 

OnePopVrfIp

Note

If you modify information about IP pools on a VR after the COPS connection is established, the SAE does not automatically register the changes, and you must update the directory.

For more information about router initialization scripts for JunosE routers, including how to update the directory, see Configuring the SAE to Manage JunosE Routers (SRC CLI).

For more information about router initialization scripts for devices running Junos OS, see Configuring the SAE to Manage Devices Running Junos OS (SRC CLI).