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

Configuration Tasks

To use ACP in the SDX network you must:

  1. Configure SAE plug-in properties.
  2. Configure ACP properties.
  3. (Edge and dual mode only) Configure ACP to manage the edge network.
  4. (Backbone and dual mode only) Configure ACP to manage the backbone network.

See the following sections for details about these procedures.

Configuring the SAE

You must configure the SAE to recognize ACP by adding some information about ACP to the SAE properties. To do so:

  1. Configure ACP as an external plug-in for the SAE.
  2. Configure event publishers.
  3. (Backbone and dual mode only) Optionally, configure a hosted plug-in that monitors the state of interfaces on VRS.

Configuring ACP as an External Plug-In

To configure an external plug-in for the SAE, see SDX Components Guide, Vol. 1, Chapter 5, Configuring Authorization and Tracking Plug-Ins. Use the following values for the plug-in attributes:

Configuring Event Publishers

You must configure the SAE to publish the following types of events to ACP:

For information about configuring event publishers, see SDX Components Guide, Vol. 1, Chapter 5, Configuring Authorization and Tracking Plug-Ins. Identify the instance of ACP by the name of the host on which you configured it.

Examples

Configuring the SAE to Monitor Interfaces for Congestion Points

NOTE: Configure this feature only if ACP is in backbone or dual mode.

The SAE uses a hosted internal plug-in to monitor the state of interfaces on a VR for backbone congestion points. If a subscriber tries to activate a service on an interface that is unavailable, the SAE denies the request. The plug-in also monitors the directory for new backbone congestion points. To configure an internal plug-in for the SAE, use the property descriptions below and see SDX Components Guide, Vol. 1, Chapter 5, Configuring Authorization and Tracking Plug-Ins.

When this plug-in initializes, it reads all the backbone services from the directory and generates a list of the DNs (network interfaces) of the backbone congestion points. The SAE sends interface tracking events, which contain the names of the interfaces, VRs, and routers to this plug-in. For this feature to work correctly, the interface, VR, and router must appear in o=AdmissionControl, o=umc (see Configuring Network Interfaces in the Directory).

Plug-in Class

Plugin.acpIntfListener.host

Plugin.acpIntfListener.bindDN

Plugin.acpIntfListener.bindPW

Plugin.acpIntfListener.baseDN

Plugin.acpIntfListener.acpBaseDN

Plugin.acpIntfListener.timeout

Plugin.acpIntfListener.objectref = objectref

Plugin.acpIntfListener.<standardJNDISuffix>
Plugin.acpIntfListener.des.net.juniper.smgt.des.<property suffix>

Configuring ACP Properties

Use SDX Configuration Editor to configure ACP properties. To access the sample data:

  1. Start SDX Configuration Editor.

For information about using SDX Configuration Editor, see SDX Software Basics Guide, Chapter 15, Using SDX Configuration Editor.

  1. Import the SDX system configuration from the directory.
  2. Open the config.xml file in the ACP folder.

    NOTE: You can also use SDX Admin to modify ACP properties in I=ACP, ou=staticConfiguration, ou=Configuration, o=Management, o=umc. Each field description includes a property name for SDX Admin.

Configuring Logging

To configure logging, click the logging tab in the config.xml file. You can see default settings for logging in this file. For information about configuring logging, see SDX Components Guide, Vol. 1, Chapter 12, Configuring Logging.

Configuring ACP Operation

To configure how the ACP operates, click the General tab in the config.xml file, and complete the fields.

ACP backup directory

Mode

ACP event cache size

Congestion point overload control method

Enable user interface auto completion

Background Bandwidth Tuning Factors

User bandwidth exceed message

Network bandwidth exceed message

Backup db reorganization threshold incremental size

Configuring CORBA Interfaces

To configure CORBA interfaces for ACP, click the CORBA tab in the config.xml file, and complete the fields.

ORB Class

ORB Singleton Class

ACP CORBA Reference

ACP remote sync rate update adaptor CORBA reference

Configuring ACP Redundancy

To configure ACP redundancy, click the Redundancy tab in the config.xml file, and complete the fields in the Redundancy area.

Enable ACP redundancy

ACP redundancy local interface CORBA reference

ACP redundancy remote interface CORBA reference

ACP redundancy ping interval in millisecond

Configuring Connections to the Subscribers' Directory

To configure how the ACP connects to the directory that contains subscriber's information:

  1. Click the Data Manager tab in the config.xml file.
  2. Scroll to the heading called User Data and expand it.
    3.
  3. Complete the fields under this heading.

    NOTE: The following descriptions include property names that you can use to modify the properties in SDX Admin. Use the property name with the Global prefix if one directory supports all the components in the network. Use the property name with the <vrGroupName> prefix if you have partitioned the directory to provide information for different parts of the network through different VRs. For more information, see Working with Partitioned Directories.

Server Address

Server Port

Search Base

Authentication DN

Password

Event Base

Enable Directory Eventing

Directory Polling Interval

Configuring Connections to the Services' Directory

To configure how ACP connects to the directory that contains information about services:

  1. Click the Data Manager tab in the config.xml file.
  2. Scroll to the heading called Service Data and expand it.
    3.
  3. Complete the fields under this heading.

    NOTE: The following descriptions include property names that you can use to modify the properties in SDX Admin. Use the property name with the Global prefix if one directory supports all the components in the network. Use the property name with the <vrGroupName> prefix if you have partitioned the directory to provide information for different parts of the network through different VRs. For more information, see Working with Partitioned Directories.

Server Address

Server Port

Search Base

Authentication DN

Password

Event Base

Enable Directory Eventing

Directory Polling Interval

Congestion Points Base

Reload Congestion Points

Configuring Eventing Properties for Databases

You can configure a few directory eventing properties with SDX Configuration Editor for the subscriber and service databases. If you want to configure other directory eventing properties, you must use SDX Admin rather than SDX Configuration Editor. For information about configuring directory eventing properties, see SDX Components Guide, Vol. 1, Chapter 13, Configuring the Directory Eventing System. If one directory supports all the components in the network, use the following constructions for the properties:

If, however, you have partitioned the directory, see Working with Partitioned Directories.

NOTE: For ACP, always set the value of the des.dispatcher_pool_size property to 1.

Working with Partitioned Directories

If you have partitioned the directory to provide information for different parts of the network through different VRs, you must define the Data Manager properties with SDX Admin rather than with SDX Configuration Editor. To do so:

  1. Access I=ACP, ou=staticConfiguration, ou=Configuration, o=Management, o=umc.
  2. In the properties list, define the name of the VR group for each directory by using the following formats.

<vrGroupName> is an arbitrary name that identifies the group of VRs in the partition.

  1. Define the VRs in the group by defining the property <vrGroupName>.vrs.
  2. Define the properties for connecting to the subscribers' directory and the services' directory by using the following format:

<vrGroupName><property>=<value>

For information about these properties, see Configuring Connections to the Subscribers' Directory and Configuring Connections to the Services' Directory.

  1. Define directory eventing properties for the subscriber's directory and the services' directory by using the format

<vrGroupName>.<des.Name>.des.<property>=<value>

For more information, see Configuring Eventing Properties for Databases.

<vrGroupName>.vrs

Example

In this example the name of the VR group is vr1, and the group contains one VR called bigfoot@erx1

VrUserDatabase.vr1

vr1.factory.class.name = net.juniper.smgt.acp.UserLdapDataManagerFactory

vr1.server.address = 127.0.0.1

vr1.server.port = 389

vr1.server.baseDN = o=users,o=umc

vr1.server.authDN = cn=umcadmin,o=umc

vr1.server.password = admin123

vr1.server.event_baseDN = o=umc

vr1.server.signatureDN = o=umc

vr1.des.enable_eventing = true

vr1.des.pollinginterval = 30

vr1.des.delegate_factory_initial = com.sun.jndi.ldap.LdapCtxFactory

vr1.des.connection_pool_size = 1

vr1.des.dispatcher_pool_size = 1       

vr1.des.fake_delete = false        

vr1.des.show_fake_delete = false

vr1.vrs = bigfoot@default

Configuring ACP to Manage the Edge Network

To configure ACP to manage the edge network you must:

  1. Configure network interfaces that represent locations of congestion points in the directory.
  2. Configure guaranteed bandwidths for subscribers.
  3. Assign network interfaces to subscribers.
  4. Configure guaranteed bandwidths for services.

See the following sections for details about these procedures.

You can configure objects in the directory by means of an LDAP client or by means of a network management database. These sections provide information about the LDAP attributes you must configure and their positions in the LDAP schema, as well as details on how to configure objects with SDX Admin. For detailed information about the SDX LDAP schema, see the documentation on the SDX software CD in the folder /SDK/doc/ldap.

Configuring Network Interfaces in the Directory

You must add network interfaces to the SDX directory. For the edge network, you do so by specifying in the DN o=Admission Control, o=umc the network interfaces of the routers and the switches in the access network between subscribers and the SDX network. Table 50 shows the object class for network interfaces and the associated attributes. 





 Table 50:  ACP Information for Network Interfaces 


 Information


 Mandatory or Optional Information


 LDAP Schema




 Network interface



 Mandatory



 networkInterface (object class)





 Provisioned downstream bandwidth



 Mandatory



 downstreamProvisionedRate (attribute)





 Provisioned upstream bandwidth



 Mandatory



 upstreamProvisionedRate (attribute)





 List of downstream background bandwidths


 Entries separated by commas in the LDAP schema.



 Optional (For information about background bandwidths, see Allocating Bandwidth to Applications Not Controlled by ACP.)



 downstreamBackgroundRate (attribute)





 List of upstream background bandwidths


 Entries separated by commas in the LDAP schema.



 Optional (For information about background bandwidths, see Allocating Bandwidth to Applications Not Controlled by ACP.)



 upstreamBackgroundRate (attribute)

To configure a network interface with SDX Admin:

  1. Access SDX Admin.
  2. In the navigation pane, highlight the entry o=Admission Control, o=umc, and right-click.
  3. Select New > NetworkDevice.

The New Network Device dialog box appears.

  1. Enter the name of the network device, and click OK.

An object for the new network device appears in the navigation pane, and basic details for the new network device appear in the Main tab of the NetworkDevice pane.

  1. (Optional) Enter a description for the network device in the Description field, and click Save in the NetworkDevice pane.
  2. In the navigation pane, highlight the network device, and right-click.
  3. Select New > Network Interface.

The New Network Interface dialog box appears.

  1. Enter the name of the network interface, and click OK.

An object for the new network interface appears in the navigation pane, and basic details for the new network interface appear in the Main tab of the NetworkInterface pane.
  1. Complete the bandwidths in the Main tab of the NetworkInterface pane.
  2. Click Save in the NetworkInterface pane.

Configuring Bandwidths for Subscribers

You must configure bandwidths for subscribers that ACP manages in the edge region of the network.

If the access network between the subscriber and the router uses ATM, and all the traffic coming from one DSLAM travels on a single virtual path, you do not need to provision bandwidths for each subscriber. In this case, ACP can derive the congestion points from the router (see Deriving Edge Congestion Points.)

However, if the access network uses a protocol other than ATM, you must provide the information shown in Table 51 for each subscriber. 





 Table 51:  ACP Information for Subscribers 


 Information


 LDAP Attributes




 Provisioned downstream bandwidth



 downstreamProvisionedRate





 Provisioned upstream bandwidth



 upstreamProvisionedRate





 Actual downstream bandwidth for current subscriber session



 downstreamSyncRate





 Actual upstream bandwidth for current subscriber session



 upstreamSyncRate





 List of distinguished names (DNs) of interfaces associated with congestion points



 networkInterfaceRef

To configure bandwidths for subscribers with SDX Admin:

  1. Access SDX Admin.
  2. In the navigation pane, highlight the entry for the residential subscriber in o=users, o=umc.
  3. Click the Admission Control tab in the User pane.
  4. Enter the values for the Prov. Rate and Sync Rate fields.
  5. Click Save in the User pane.

Figure 44: Admission Control Tab in User Pane

Assigning Network Interfaces to Subscribers

You must assign to the subscriber object interfaces (including the router interfaces) for all congestion points between the subscriber and the router. Table 52 shows the LDAP attribute for this type of network interface.





 Table 52:  ACP Information for Subscribers 


 Information


 LDAP Attributes




 List of distinguished names (DNs) of interfaces associated with edge congestion points



 networkInterfaceRef






 








 NOTE: You must define the interface in the directory before you can assign it to a residential subscriber (see Configuring Network Interfaces in the Directory).

To assign an interface with SDX Admin:

  1. Start at the Admission Control pane for the subscriber (see Figure 44).
  2. Click the icon below the Interfaces field.

The Select Object dialog box appears.

  1. Select the network device on which the interface is located.

You can shift-click or control-click network devices to select multiple options.

  1. Click OK.

The network devices appear in the User pane.

  1. Click Add.

The network devices appear in the Scopes field of the pane.

  1. Highlight a network device.
  2. Modify the DN of the network device to include the interface location.
  3. Click Modify.

Repeat Steps 6 to 8 for each interface associated with a congestion point for this subscriber.

Configuring Bandwidths for Services

Upstream and downstream bandwidths must be specified for services that ACP manages. There are two ways to obtain bandwidths for services:

For example, a business partner may need to specify the required values for a particular piece of content through the SAE core API.

Table 53 shows the LDAP attributes for these services. 





 Table 53:  ACP Information for Services 


 Information


 LDAP Attributes




 Required downstream bandwidth



 sspRequiredDownstreamBandwidth





 Required upstream bandwidth



 sspRequiredUpstreamBandwidth

To configure values for services with SDX Admin:

  1. Access SDX Admin.
  2. In the navigation pane, highlight the entry for the service in o=Services, o=umc.
  3. Click the Admission Control tab in the SSP Service pane.
    4.
  4. Enter the values for the Required Downstream Bandwidth and the Required Upstream Bandwidth fields.
  5. Click Save in the SSP Service pane.

Configuring ACP to Manage the Backbone Network

To configure ACP to manage the backbone network, you must:

  1. Configure network interfaces that represent locations of congestion points in the directory.
  2. Configure guaranteed bandwidths for services.
  3. Assign network interfaces to services.
  4. Create congestion points in the directory.
  5. Assign network interfaces to congestion points.

Refer to the following sections for details about these procedures.

NOTE: You can configure objects in the directory by means of an LDAP browser or by means of a network management database. These sections provide information about the LDAP attributes you must configure and their positions in the LDAP schema, as well as details on how to configure objects with SDX Admin. For detailed information about the SDX LDAP schema, see the documentation on the SDX software CD in the folder /SDK/doc/ldap.

Configuring Network Interfaces in the Directory

You configure network interfaces in the directory in the same way for edge and backbone congestion points. However, for backbone congestion points, you can only add VRs and their interfaces. For information about this procedure, see Configuring Network Interfaces in the Directory.

Configuring Bandwidths for Services

You configure bandwidths for services in the same way for edge and backbone congestion points. For information about this procedure, see Configuring Bandwidths for Services.

Configuring Congestion Points for Services

You must assign a congestion point to each service that ACP manages. Table 54 shows the LDAP attributes for a backbone congestion point. 





 Table 54:  ACP Information Associated with Backbone Congestion Points


 Information


 LDAP Attributes




 Definition of a backbone congestion point in the format <-vrName->/<-serviceName->


    
  
  •  To allow the software to automatically define the congestion point, use the entry <-vrName->/<-serviceName->. When ACP starts operating, it will substitute the VR name and the service name from the request for service activation.
    • 
  
  •  To restrict the congestion point to a specific VR or service, enter the actual VR name or service name, as shown in the following examples.
    • 


  
    
    
  •  vr1@boston/<-serviceName->—Specifies any service available on VR vr1@boston
    • 
    
  •  <vrName>/news—Specifies the service news on any VR 
    • 
    
  •  vr1@boston/news—Specifies the service news available on VR vr1@boston
    • 
    
  •  default@ottawa/news—Specifies the service news available either on the default VR or on a router called ottawa
    • 
  



 congestionPoints

To configure values for services with SDX Admin:

  1. Access SDX Admin.
  2. In the navigation pane, highlight the entry for the service in o=Services, o=umc.
  3. Click the Admission Control tab in the SSP Service pane.
  4. In the entry box below the Congestion Points field, enter the name of one congestion point; see Table 54 for information about the format of this entry.
  5. Click the Add button.

The entry appears in the Congestion Points field.

Configuring Congestion Points in the Directory

You must add backbone congestion points to the directory in o=CongestionPoints, o=umc. Table 54 shows the LDAP attribute for a backbone congestion point.

To configure an individual backbone congestion point in the directory with SDX Admin:

  1. Access SDX Admin.
  2. In the navigation pane, highlight the entry o=CongestionPoints, o=umc, and right-click.
  3. Select New > Congestion Point.

The New Congestion Point dialog box appears.

  1. Enter the name of the VR that supports the new congestion point, and click OK.

The new object appears in the navigation pane, and basic details for the object appear in the Main tab of the Congestion Point pane.

  1. (Optional) Enter a description for the VR in the Description field, and click Save in the NetworkDevice pane.
  2. In the navigation pane, highlight the VR, and right-click.
  3. Select New > Congestion Point.

The New Congestion Point dialog box appears.

  1. Enter the name of the service, and click OK.

The new object appears in the navigation pane, and basic details for the object appear in the Main tab of the Congestion Point pane.

To add all backbone congestion points for all VRs in the directory:

  1. Access SDX Admin.
  2. In the navigation pane, highlight the entry o=CongestionPoints, o=umc, and right-click.
  3. Select New > Create CongestionPoints.

The VRs and the services they support appear in the folder.

Assigning Interfaces to Congestion Points

You must assign interfaces either to VRs or to individual services under the VRs in o=CongestionPoints, o=umc. Services inherit interface assignments from the associated VR unless you assign an interface to the individual service. Table 55 shows the LDAP attribute for this network interface. 





 Table 55:  ACP Information for Interfaces Associated with Backbone Congestion Points


 Information


 LDAP Attributes




 List of distinguished names (DNs) of interfaces associated with backbone congestion points



 InterfaceRef

To assign interfaces to congestion points with SDX Admin:

  1. Access SDX Admin.
  2. In the navigation pane, highlight the entry in o=CongestionPoints, o=umc to which you want to assign the congestion point.
  3. Click the icon below the Interfaces field.

The Select Object dialog box appears.

  1. Select the network device on which the interface is located.

You can shift-click or control-click network devices to select multiple options.

  1. Click OK.

The network devices appear in the User pane.

  1. Click Add.

The network devices appear in the Scopes field of the pane.

Repeat Steps 3 to 8 for each interface associated with a congestion point for this subscriber.

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