Overview

On JUNOSe routers, the SAE manages interfaces on VRs. On JUNOS routing platforms, the SAE manages interfaces on the JUNOS routing platform. To allow the SAE to manage interfaces on both JUNOSe VRs and JUNOS routing platforms, the SDX software associates a VR called default with each JUNOS routing platform.

For JUNOSe routers, each JUNOSe router in the SDX network and its VRs must appear in the directory. For JUNOS routing platforms, each JUNOS routing platform in the SDX network and its associated VR called default must appear in the directory. This VR is 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.

Directory Model for Router Objects

The router objects in the directory are stored in the network folder, o=network,o=umc. The router objects define:

• Interface classification scripts, which determine the default policy that the router applies to a particular interface. The router objects contain classification profiles that are represented by the auxiliary object class umcClassificationProfile. This class is attached to a router entry.
• Management address of the router.
• QoS profiles configured on the router (JUNOSe routers only).

The physical aspect of a router is modeled by the DMTF object class dlm1Chassis. You can also attach local parameters to router objects by using the parameterAuxClass.

Virtual router objects are modeled in the directory by the class umcVirtualRouter, and they define:

• SNMP communities that the SAE uses to communicate with the virtual router. SNMP information is contained in the auxiliary class snmpInfoAuxClass, which can be attached to umcVirtualRouter objects.
• Service scopes, which determine the availability of services for subscribers who connect to the VR. The association between virtual routers and SSP services for service scoping is performed by attaching the CIM auxiliary class dlm1PhysicalElementLocationAuxClass. This class consists of a DN attribute that points to localities that contain SSP services.
• Local address pools on the JUNOSe VR.
• CORBA reference for the SAE that manages this VR.
• Tracking plug-ins that track interfaces that the SAE manages on this VR.

For detailed information about the SDX LDAP schema and graphics of the object models, see the documentation on the SDX software CD in the folder /SDK/doc/ldap.

Local IP Address Pools on JUNOSe VRs

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.

The IP pool syntax has the following format:

([<ipAddressStart> <ipAddressEnd>] |
{<ipBaseAddress>/(<mask> | <digitNumber>)(,<ipAddressExclude>)*})

where:

• <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
  

  NOTE: You can use spaces in the syntax only to separate the first and last explicit IP addresses in a range.

  
  

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 the 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.