Adding Routers and VRs to the Directory

You can detect operative routers and configured JUNOSe VRs in the SDX network and add them to the directory simultaneously with SDX Admin. This operation automatically creates a VR called default in the directory for each detected JUNOS routing platform. However, if you use an LDAP client other than SDX Admin, or you want to add inoperative routers or unconfigured JUNOSe VRs, you must add each router and VR individually.

Adding All Operative Routers and Configured JUNOSe VRs with SDX Admin

To simultaneously add to the directory routers and JUNOSe VRs that are currently operative and have an operating SNMP agent:

1. Start SDX Admin.
2. In the navigation pane, select o=Network, and right-click.
3. Select Discover Network.

The Discover Network dialog box appears.

4. Enter the IP address and prefix of the network, and the SNMP community string.
5. Click OK.

Objects for all routers and JUNOSe VRs that meet the criteria you specified appear under the Networks object in the navigation pane. For each JUNOS routing platform, the software creates one VR called default. You can modify the properties configured for these objects. For information about the properties of these objects, see Adding Routers Individually and Adding VRs Individually.

Adding Routers Individually

To add a router with an LDAP client other than SDX Admin, use the object class dlm1ManagedElement. For information about the object classes and their associated attributes, see the LDAP schema on the SDX software CD in the folder SDK/doc/ldap. The name of the router, which is case-sensitive, must exactly match the name configured on the router.

To add a single router to the directory with SDX Admin:

1. In the navigation pane, highlight o=Network, and right-click.
2. Select New > EdgeDevice.

The New EdgeDevice dialog box appears.

3. In the New EdgeDevice dialog box, enter the name of the router exactly as it is configured in the JUNOS or JUNOSe software, and click OK.

The name of the new device appears in the navigation pane, and information about the router appears in the EdgeDevice pane.

4. Set the parameters in the Main tab of the EdgeDevice pane.
5. Click Save in the EdgeDevice pane.

Description

• Specifies information about this device; keywords that the SDX find utility uses.
• Value - text string
• Example - ERX-1400 router located in Ottawa

Management Address

• Specifies the IP address of the router. If you add the 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

QoS Profiles

• Specifies QoS profiles that are configured on the router. To update this list, see SDX Software Basics Guide, Chapter 17, Managing QoS Services on JUNOSe Routers.
• Value - list of QoS profiles on separate lines
• Example - atm-default

Adding VRs Individually

To add a VR with an LDAP client other than SDX Admin, use the object class umcVirtualRouter. For information about the object classes and their associated attributes, see the LDAP schema on the SDX software CD in the folder SDK/doc/ldap.

• 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, create one VR with the name default.

To add a single VR to the directory with SDX Admin:

1. In the navigation pane of the SDX Admin window, highlight the JUNOSe router that supports the VR, and right-click.
2. Select New > VirtualRouter.

The New VirtualRouter dialog box appears.

3. Enter the name of the VR, and click OK.

• 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, use the name default.

The name of the new VR appears in the navigation pane, and the VirtualRouter pane appears.

4. Set the parameters in the Main tab of the VirtualRouter pane.
5. Click Save in the VirtualRouter pane.

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

• Specifies service scopes assigned to this VR - see SDX Objects Guide, Chapter 1, Managing Services.
• Value - text string
• Example - POP-Westford

Local Address Pools

• Specifies the list of IP address pools that a JUNOSe VR currently manages and stores. (see SDX Components Guide, Vol. 2, Chapter 10, Configuring and Starting the NIC.)
• Value - list of IP address pools. For information on the syntax for IP pools, see Local IP Address Pools on JUNOSe VRs.
• Guidelines - if you do not configure the PoolPublisher or staticRouteAndPoolPublisher router initialization scripts for a JUNOSe router (see SDX Components Guide, Vol. 1, Chapter 1, Overview of the SAE), configure this field for the JUNOSe VR.
• Default - unspecified
• Example - ([10.10.10.5 10.10.10.250] {10.20.20.0/24})

Static Address Pools

• Specifies a list of IP address pools that a JUNOSe VR manages but does not store. You can configure these address pools only in the SDX software.
• Value - see the field Local Address Pools.
• Guidelines - configure this field on JUNOSe VRs only.
• Default - unspecified
• Example - ([10.10.10.5 10.10.10.250] {10.20.20.0/24})

Managing SAE IOR

• Specifies the 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 IOR file
• A corbaloc URL in the form corbaloc::<host>:8801/SAE

• <host> is the name or IP address of the SAE host.

• Default - unspecified
• Guidelines - the PoolPublisher and IorPublisher router initialization scripts provide this information when the router connects to the SAE. For information about configuring router initialization scripts, see SDX Components Guide, Vol. 1, Chapter 1, Overview of 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/ssp/var/run/sae.ior (JUNOSe routers) or /opt/UMC/ssp/var/run/sae.ior (JUNOS routing platforms)
• Corbaloc URL - boston:8801/sae
• Actual IOR - IOR:000000000000002438444C3A736D67742E6A756E697...

Tracking Plug-in

• Specifies the plug-in instances, such as NIC SAE plug-in agents, 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 NIC SAE plug-in agents that are specific to this VR. For information about configuring global interface tracking plug-ins, see SDX Components Guide, Vol. 1, Chapter 5, Configuring Authorization and Tracking Plug-Ins.
• Default - unspecified
• Example - nicsae, flexRadius