Adding JUNOS Routing Platforms and Virtual Routers
On JUNOS routing platforms, the SAE manages interfaces. The SRC software associates a virtual router called default with each JUNOS routing platform. Each JUNOS routing platform in the SRC network and its associated virtual router (VR) called default must appear in the directory. The VRs are not actually configured on the JUNOS routing platform; the VR in the directory provides a way for the SAE to manage the interfaces on the JUNOS routing platform.
There are two ways to add routers to the directory:
- Use SDX Admin to detect operative routers in the SRC network and add them to the directory. This operation creates a VR called default in the directory for each detected JUNOS routing platform.
- Add each router and VR individually. You need to add routers and VRs individually if you use an LDAP client other than SDX Admin or if you want to add inoperative routers.
NOTE: You must define connected SAEs for each router in the virtual router object of the directory. This step is required for the SAE to work with the router. See Specifying the SAEs That Can Manage the Router.
Adding Operative JUNOS Routing Platforms
To add routers that are currently operative and have an operating SNMP agent:
The Discover Network dialog box appears.
For each JUNOS routing platform, the software creates one VR called default. You can modify the configuration of these objects. For information about configuring these objects, see Adding Routers Individually and Adding Virtual Routers Individually.
Adding Routers Individually
To add a single router with SDX Admin:
The New EdgeDevice dialog box appears.
The new device appears in the navigation pane, and the Main tab of the EdgeDevice pane appears.
![]()
See Router Fields.
Router Fields
In SDX Admin, you can modify the following fields in the content pane for a router (orderedCimKeys=<EdgeDeviceName>, o=network, o=umc).
Description
- Information about this device; keywords that the SRC find utility uses.
- Value—Text string
- Example—ERX-1400 router located in Ottawa
Management Address
- IP address of the router or CMTS device. If you add a router using the discover network feature, the software automatically adds the IP address of the first SNMP agent on the router to respond to the discover request.
- Value—IP address
- Example—192.0.1.1
Router Driver Type
QoS Profiles
- For JUNOSe routers, specifies quality of service (QoS) profiles that are configured on the router.
- Value—List of QoS profiles on separate lines
- Guideline—This field applies to JUNOSe routers only
- Example—atm-default
Adding Virtual Routers Individually
- In the navigation pane, right-click the device to which you want to add the VR, and select New > VirtualRouter.
The New VirtualRouter dialog box appears.
- For JUNOSe routers, the name of the VR, which is case sensitive, must exactly match the name of the VR configured on the router.
- For JUNOS routing platforms and CMTS devices, use the name default.
The new VR appears in the navigation pane, and the Main tab of the VirtualRouter pane appears.
![]()
- Select the SAE Connection tab in the VirtualRouter pane, and add SAEs that are connected to the router. See Specifying the SAEs That Can Manage the Router.
NOTE: This step is required for the SAE to work with the router.
- Click Save.
Virtual Router Fields
In SDX Admin, you can modify the following fields in the content pane for a virtual router (virtualRouterName=<virtualRouterName>, orderedCimKeys=<EdgeDeviceName>, o=network, o=umc).
SNMP Read Community
- SNMP community name associated with SNMP read-only operations for this VR.
- Value—Text string
- Example—admin
SNMP Write Community
- SNMP community name associated with SNMP write operations for this VR.
- Value—Text string
- Example—public
Scope
Local Address Pools
- List of IP address pools that a JUNOSe VR currently manages and stores.
- Value—You can specify an unlimited number of ranges of local IP address pools for JUNOSe VRs. You can specify either the first and last addresses in a range or the first IP address and a factor that indicates the start of the range. You can also specify IP addresses to exclude. Use spaces in the syntax only to separate the first and last explicit IP addresses in a range.
The IP pool syntax has the format:
([<ipAddressStart> <ipAddressEnd>] | {<ipBaseAddress>/(<mask> | <digitNumber>)(,<ipAddressExclude>)*})
- <ipAddressStart>—First IP address (version 4 or 6) in a range
- <ipAddressEnd>—Last IP address (version 4 or 6) in a range
- <ipBaseAddress>—Network base address
- <mask>—IP address mask
- <digitNumber>—Integer specifying the number of significant digits of the first IP address in the range
- <ipAddressExclude>—List of IP addresses to be excluded from the range
- |—Choice of expression; choose either the expression to the left or the expression to the right of this symbol
- *—Zero or more instances of the preceding group
- Guidelines—Configure this field on JUNOSe VRs only. If you do not configure the PoolPublisher router initialization scripts for a JUNOSe router, configure this field for the JUNOSe VR.
- Default—No value
- Example—This example shows four ranges for the IP address pool.
([10.10.10.5 10.10.10.250]{10.20.20.0/24}{10.21.0.0/255.255.0.0}{10.20.30.0/24,10.20.30.1})
- The first range (a simple range) specifies all the IP addresses between the two IP addresses 10.10.10.5 and 10.10.10.250.
- The second range specifies all the IP addresses in the range 10.20.20.0 to 10.20.20.255.
- The third range uses a network mask to specify all the IP addresses in the range 10.21.0.0 to 10.21.255.255.
- The fourth range specifies all the addresses of the network 10.20.30.0 to 10.20.30.255, excluding the address 10.20.30.1.
Static Address Pools
- List of IP address pools that a JUNOSe VR manages but does not store. You can configure these address pools only in the SRC software.
- Value—See the field Local Address Pools.
- Guidelines—Configure this field on JUNOSe and CMTS VRs only.
- Default—No value
- Example—([10.10.10.5 10.10.10.250] {10.20.20.0/24})
Managing SAE IOR
- Common Object Request Broker Architecture (CORBA) reference for the SAE managing this VR.
- Value—One of the following items:
- The actual CORBA reference for the SAE
- The absolute path to the interoperable object reference (IOR) file
- A corbaloc URL in the form corbaloc::<host>:8801/SAE
- Default—No value
- Guidelines—The PoolPublisher and IorPublisher router initialization scripts provide this information when the router connects to the SAE. If you do not select one of these router initialization scripts, enter a value in this field.
- Example—One of the following items:
- Absolute path—/opt/UMC/sae/var/run/sae.ior
- corbaloc URL—corbaloc::boston:8801/SAE
- Actual IOR— IOR:000000000000002438444C3A736D67742E6A756E697...
Tracking Plug-in
- Plug-ins that track interfaces that the SAE manages on this VR. The SAE calls these plug-in instances for every interface it manages. The SAE calls these plug-ins after an interface comes up, when new policies are installed on the interface, and when the interface goes down.
- Value—Comma-separated list of plug-in instances
- Guidelines—Enter plug-in instances and network information collector (NIC) SAE plug-in agents that are specific to this VR.
- Default—No value
- Example—nicsae, flexRadius
Specifying the SAEs That Can Manage the Router
You must add the addresses of SAEs that can manage this router. This step is required for the SAE to work with the router. To add the SAEs, select the SAE Connection tab in the VirtualRouter pane.
![]()
Adding an SAE
To specify the active SAE and the redundant SAE, enter an exclamation point (!) after the hostname or IP address of the connected SAE.
Modifying an SAE Address
- Click the IP address of the SAE in the Connected SAE box.
- Modify the IP address in the field below the Connected SAE box.
- Click Modify.
Deleting an SAE Address
- Click the IP address of the SAE in the Connected SAE box.
- Remove the IP address from the field below the Connected SAE box.
- Click Delete.
Connected SAE