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

SDX 6.4.x Application Library Guide > Providing Admission Control with ACP > Configuring ACP

Configuring ACP

To use ACP in the SDX network, you must configure perform some configuration. For information about these configuration procedures, see:

  1. Configuring the SAE for ACP
  2. Configuring ACP Properties
  3. (Edge and dual mode only) Configuring ACP to Manage the Edge Network
  4. (Backbone and dual mode only) Configuring ACP to Manage the Backbone Network

Configuring the SAE for ACP

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 Subscribers and Subscriptions Guide, Chapter 6, How to Configure SAE 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 Subscribers and Subscriptions Guide, Chapter 7, Configuring Authorization and Accounting 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, see SDX Subscribers and Subscriptions Guide, Chapter 6, How to Configure SAE Plug-Ins and use the properties described in Internal Plug-In Properties for Monitoring Congestion Points.

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

Internal Plug-In Properties for Monitoring Congestion Points

Use the descriptions in this section to configure an internal plug-in for the SAE.

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 Getting Started Guide, Chapter 17, 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 Monitoring and Troubleshooting Guide, Chapter 2, Configuring Logging for SDX Components.

Configuring ACP Operation

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

ACP Backup Directory

Mode

ACP Event Cache Size

Method to Control Congestion Point Overload

Router Determines Congestion Points

Tuning Factors for Background Bandwidth

Message for Subscribers who Exceed Bandwidth

Message When Traffic Flow Exceeds Bandwidth

Maximum Size of ACP Data Files

Index Keys For Remote Update DB

Interface Tracking Event Filter

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

CORBA Reference for Local Interface

CORBA Reference for Remote Interface

Polling Interval

Ignore User Tracking Out Of Sync

Redundant naming service

Configuring State Synchronization

To configure state synchronization with SAE, click the Redundancy tab in the config.xml file, and complete the state synchronization fields. Enabling state synchronization can affect performance because of resource consumption.

Enable State Synchronization

Number of SAE Events Sent at One Time

Community Heartbeat

Community Acquire Timeout

Community Blackout Timeout

Configuring Connections to the Subscribers' Directory

To configure how ACP connects to the directory that contains subscriber 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.

    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 Eventing

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.

    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

CongestionPoint Base

Reload Congestion Points

Congestion Points Eventing

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 Getting Started Guide, Chapter 14, Distributing Directory Changes to SDX Components. 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 SDX Admin.
  2. In the navigation pane, highlight the entry I=ACP, ou=staticConfiguration, ou=Configuration, o=Management, o=umc.
  3. Click the Main tab in the ACP Configuration pane.
  4. Define the name of the VR group for each directory in the Property field 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 Scripts and Classification

To configure ACP scripts and classification, click the Scripts and Classification tab in the config.xml file, and complete the fields in the ACP Scripts and Classification area.

Scripts Factory Class

Congestion Points Classification Factory Class

Congestion Points Classification Scripts

Congestion Points Profile Scripts

Scripts Extension Path

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 distribution 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 23 shows the object class for network interfaces and the associated attributes. 





 Table 23:  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 fields using the information in Bandwidth for Network Interfaces.
  2. Click Save in the NetworkInterface pane.

Bandwidth for Network Interfaces

Use the fields in this section to define bandwidth for network interfaces.

Downstream Prov. Rate

Upstream Prov. Rate

Downstream Background Bandwidth

Upstream Background Bandwidth

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 24 for each subscriber. 





 Table 24:  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 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 fields using the information in Bandwidth for Subscribers.
  5. Click Save in the User pane.

Figure 20: Admission Control Tab in User Pane

Bandwidth for Subscribers

Use the fields in this section to configure bandwidths for subscribers.

Downstream Prov. Rate

Upstream Prov. Rate

Downstream Sync Rate

Upstream Sync Rate

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 24 shows the LDAP attribute for this type of network interface. 







 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 20).
  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. You can obtain bandwidths for services in two ways:

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

Table 25 shows the LDAP attributes for these services. 





 Table 25:  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. (Optional) Configure an action congestion point.
  3. Configure guaranteed bandwidths for services.
  4. Assign network interfaces to services.
  5. Create congestion points in the directory.
  6. 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 that 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 in the SDX software distribution 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 add only VRs and their interfaces. For information about this procedure, see Configuring Network Interfaces in the Directory.

Extending ACP Congestion Points

You can extend ACP congestion points to initialize and execute applications defined in a backbone congestion point. ACP provides a service provider interface (SPI) to:

The SPI for ACP provides a Java interface that a congestion point application implements. For information about the SPI for ACP, see the documentation in the SDX application library distribution in the folder SDK/doc/acp.

The implementation of the SPI for ACP can be a customized application that performs certain tasks, such as creating or removing congestion points on the router. ACP acts as an interface tracking plug-in, and interface tracking events are treated as remote updates for congestion points when they are created, modified, or removed.

ACP supports applications written in Java or Jython. For scripts written in Java, you must compile and package the implemented SPI for ACP to make it available for use by ACP. A Java implementation can include more than one Java archive (JAR) file.

To use congestion point applications with ACP, configure an action congestion point that references the script (see Configuring Action Congestion Points).

Configuring Action Congestion Points

You can define an application in a backbone congestion point so that ACP can execute it in a predefined manner. Backbone congestion points that are configured to run an application are called action congestion points. If you want to use an action congestion point to execute an application that requires real-time congestion point status, you must enable ACP state synchronization with the SAE (see Configuring State Synchronization).

Before you configure an action congestion point, make sure that you know the location of the application file.

To configure an action congestion point with SDX Admin:

  1. Access SDX Admin.
  2. In the navigation pane, highlight the entry for the network interface in o=Admission Control, o=umc.
  3. Click the Action tab.

The Action tab appears in the NetworkInterface pane.
  1. In the Type field, select one of the following file types that the application uses:
  1. In the Class Name field, enter the class name of the Java or Python class implementing the SPI.
  2. In the File/URL field, enter the URL, or click Load to add a file.

The Load data dialog box appears. For information about loading scripts, see Managing Files from the Load Data Dialog Box.

The URL or the content of the script file appears in the File/URL box.

If you want to remove the URL or file, click Clear.

  1. In the entry box below the Parameters field, enter the parameter as an attribute=value pair, and click Add.

The entry appears in the Parameters field.

To modify the entry:

The modified entry appears in the Parameters field.

  1. Click Save in the NetworkInterface pane.

Managing Files from the Load Data Dialog Box

If you click Load in the Files/URL box, the Load data dialog box appears.

You can manipulate files and folders from the Load data dialog box.

  1. Select the directory that contains the script that implements the application, and then select the file.

or

Type the path to the script file in the Selection box.

If a JAVA implementation includes more than one JAR file, use commas to separate file URL entries, or enter one URL per line.

  1. Click OK.

The content of the script file appears in the File/URL box.

  1. In the Files list, select a file, and click Rename File.

The Rename File dialog box appears.

  1. Enter the new filename, and click OK.

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 26 shows the LDAP attributes for a backbone congestion point. 





 Table 26:  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 26 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 26 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. The LDAP attribute for this network interface is called interfaceRef and it lists the DNs of interfaces associated with backbone congestion points.

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 6 for each interface associated with a congestion point for this subscriber.

Defining a Congestion Point Profile

You can create a congestion point profile that automatically performs congestion point classification. This profile supports only access network mode for ACP.

The congestion point profiles are stored in the directory under o=congestionPoints, o=umc.

To define a congestion point profile:

  1. In SDX Admin under UMC, right-click CongestionPoints, select New, and then select Congestion Point Profile.

The New Congestion Point Profile dialog box appears.

  1. In the New Congestion Point Profile dialog box, enter a name for the profile.

The Congestion Point Profile pane appears in the content area.
  1. Enter a congestion point expression in the box below the Expression box, and then click Add. For information about congestion point expressions, see Congestion Point Expressions.

Congestion Point Expressions

You can enter a congestion point expression by using the syntax listed in this section. You can also embed Python scripting expressions within the congestion point expression.

If you embed Python expressions within a congestion point expression, use the escape sequence <- then -> to enclose the Python expression. See Methods for Use with Scripting Expressions and Match Criteria for Congestion Point Classification.

The syntax for a congestion point expression is:

<NetworkDevice>/<NetworkInterface>[/<CongestionPoint>]

For information about network devices, see SDX Network Guide: SAE, Juniper Networks Routers, and NIC, Chapter 3, Using JUNOSe Routers in the SDX Network or SDX Network Guide: SAE, Juniper Networks Routers, and NIC, Chapter 4, Using JUNOS Routing Platforms in the SDX Network.

For information about interfaces, see SDX Subscribers and Subscriptions Guide, Chapter 4, Classifying Interfaces and Subscribers.

If one of the elements with the path contains a slash (/), use a backslash (\) as an escape character for the slash. For example, \/.

Expressions in Templates for Congestion Point Profiles

You can create a congestion point profile to be used as a template for other profiles. Templates simplify management of congestion points. Rather than configuring each congestion point individually, you can create templates to define common parameters for a class of individual congestion points.

For example, in an environment in which VLAN interfaces GigabitEthernet1/0.1 through GigabitEthernet1/0.1000 have the same available bandwidth, you can specify the characteristics of the VLAN interface once and have ACP create the congestion points based on the template configuration.

When a congestion point expression has the third element, ACP uses the <NetworkDevice>/<NetworkInterface> part of the expression to load the congestion point from the directory, and uses it as a template to create a congestion point in memory for subscriber. The <CongestionPoint> part of the expression distinguishes each congestion point (available bandwidth) created from this template.

Methods for Use with Scripting Expressions

ACP provides the following methods to use in scripting expressions:

Example—slot("atm 4/5:0.32") == "4"

Example—port("atm 4/5:0.32") == "5"

Example—l2id("atm 4/5:0.32") == "0.32"

Example—escape("atm 4/5") == "atm 4\/5"

You can extend the scripting library by creating the file lib/localCPLib.py in the ACP installation directory, by default /opt/UMC/acp/lib/localCPLib.py. ACP reads the definitions in this file at startup, after which they are available for processing.

Match Criteria for Congestion Point Classification

You can use the following match criteria in Python scripting expressions for a congestion point expression:

For more information, see RFC 2131—Dynamic Host Configuration Protocol (March 1997) and RFC 2132—DHCP Options and BOOTP Vendor Extensions (March 1997).

Examples of Congestion Profiles

This section provides examples of expressions used in congestion point profiles.

Profile for Gigabit Ethernet Interface

In the following example, a subscriber who is connecting to router test@erx through interface GigabitEthernet1/0.1, has the congestion point:

"subInterface=1,interfaceName=GigabitEthernet1/0,orderedCimKeys=test@erx,o=Ad
missionControl,o=UMC"

This congestion point is created from a congestion point template:

"interfaceName=GigabitEthernet1/0,orderedCimKeys=test@erx,o=AdmissionControl,o
=UMC"

The following congestion point expression is configured for the congestion point profile cn=vlan, o=CongestionPoints, o=umc:

NOTE: The following example is a single expression that should be entered on a single line.

 

<-routerName->/<-interfaceName[:interfaceName.find('.')]->/

<-interfaceName[interfaceName.find('.')+1:]->

Profile That Contains Three Congestion Points

In the following example, a subscriber who is connecting to router test@erx through interface atm 4/5:0.32 will have three congestion points:

ACP automatically appends o=AdmissionControl, o=UMC.

This profile creates the same congestion points that are created by the ATM autocompletion feature, which is available in this version as well as previous versions of ACP.

The following congestion point expressions are configured for the congestion point profile cn=atm, o=CongestionPoints, o=umc:

<-routerName->/<-escape(portId.replace(' ',''))->

<-routerName->/<-escape(portId[:portId.rindex('.')].replace(' ',''))->

<-routerName->/<-escape(portId[:portId.rindex(':')].replace(' ',''))->

Profile That Uses Congestion Point Templates

In the following example, the congestion points are dynamically created based on templates for the expressions. When you use a template, you specify parameters for the <NetworkDevice>/<NetworkInterface> part of the expression. This part refers to a network interface object in the directory that defines the parameters of the congestion point; that is, the available bandwidth.

The following congestion point expressions are configured for the congestion point profile cn=atm, o=CongestionPoints, o=umc:

<-routerName->/VCI/<-portId->

<-routerName->/VPI/<-portId[:portId.rindex('.')] ->

<-routerName->/PHY/<-portId[:portId.rindex(':')] ->

where:

Changing and Removing a Congestion Point Profile

To change configuration of a congestion point profile:

  1. In SDX Admin, select the congestion point profile.
  2. In the Congestion Point Profile pane, select the expression to change in the Expression box, and click Modify.
  3. Make changes to the expression, and click Add.

The updated expression appears in the Expression box.

To remove a congestion point profile:

  1. In SDX Admin, right-click the congestion point profile.
  2. Select Delete to remove the profile.
[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]