Adding Objects for Network Devices to the Directory
For each network device that the SAE manages, you need to add a router object and virtual router object to the directory.
To add a router object to the directory with SDX Admin:
The New EdgeDevice dialog box appears.
The name of the new device appears in the navigation pane.
![]()
- Use the field descriptions in Router Fields to configure the router, and then click Save.
Router Fields
Use the fields in this section to configure routers.
Description
- Information about this device; keywords that the SDX find utility uses.
- Value—Text string
- Example—ERX-1400 router located in Ottawa
Management Address
Router Driver Type
- Type of device that this directory object will be used to manage.
- Value—Select PROXY
- Default—No value
QoS Profiles
Adding Virtual Router Objects
To add a virtual router object to the directory with SDX Admin:
- In the navigation pane, highlight the device to which you want to add the VR, and right-click.
- Select New > VirtualRouter.
The New VirtualRouter dialog box appears.
The name of the new virtual router object appears in the navigation pane, and the VirtualRouter pane appears.
![]()
- Set the parameters in the Main tab in the VirtualRouter pane. See Virtual Router Fields.
- Select the SAE Connection tab in the VirtualRouter pane, and add SAEs that are connected to the router. See Defining SAE Communities.
NOTE: This step is required for the SAE to work with the router.
- Click Save in the VirtualRouter pane.
Virtual Router Fields
Use the fields in this section to define virtual routers.
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
- Service scopes assigned to this VR—See SRC-PE Services and Policies Guide, Chapter 2, Managing Services on a Solaris Platform.
- Value—Text string
- Example—POP-Westford
Local Address Pools
- For JUNOSe routers only. 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
- For JUNOSe routers and CMTS devices only. 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