Router Initialization Scripts with NIC Configuration Scenarios

[Contents] [Prev] [Next] [Index] [Report an Error]

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

JUNOS routing platforms

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

Table 11 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 11: 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 with the CLI.

For more information about router initialization scripts for JUNOS routing platforms, see Configuring the SAE to Manage JUNOS Routing Platforms.

Router Initialization Scripts with NIC Configuration Scenarios

Related Topics