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

Configuring SRC-ACP to Manage the Backbone Network

The tasks to configure SRC-ACP to manage the backbone network are:

Configuring Network Interfaces in the Directory for the Backbone Network

You configure network interfaces in the directory in the same way for edge and backbone congestion points.

Extending SRC-ACP Congestion Points for the Backbone Network

You can extend SRC-ACP congestion points to initialize and execute applications defined in a backbone congestion point.

SRC-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 SDK documentation in the SDK+AppSupport+Demos+Samples.tar.gz file on the Juniper Networks Web site at: https://www.juniper.net/support/csc/swdist-erx/src.html You can locate the files in the SDK/doc/acp directory.

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

SRC-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 SRC-ACP. A Java implementation can include more than one Java archive (JAR) file.

To use congestion point applications with SRC-ACP, configure an action congestion point that references the script.

Configuring Action Congestion Points

You can define an application in a backbone congestion point so that SRC-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 SRC-ACP state synchronization with the SAE).

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

Use the following configuration statements to configure action congestion points:

shared admission-control device name interface name {
action-type (url | python | java-class | java-archive);
action-class-name action-class-name;
action-file-url action-file-url;
action-parameters [action-parameters...];
action-file-name action-file-name;
}

To configure an action congestion point:

  1. From configuration mode, access the configuration statement that configures network interfaces.
    user@host# edit shared admission-control device name interface name

    Enter the name of the network device and the name of the virtual router.

  2. (Optional) Specify the file type of the application.
    [edit shared admission-control device name interface name]
    user@host# set action-type (url | python | java-class | java-archive);
  3. (Optional) Specify the name of the class implementing the SPI.
    [edit shared admission-control device name interface name]
    user@host# set action-class-name action-class-name
  4. (Optional) Specify the URL or the content of the file. For action congestion point implementations written in Java of the url action type, configure the URL that specifies the location of the Java archives (.jar files) containing the action congestion point implementation. For other action types, you must load the action congestion point implementation with the action file name option.
    [edit shared admission-control device name interface name]
    user@host# set action-file-url action-file-url
  5. (Optional) Specify the parameter as an attribute=value pair.
    [edit shared admission-control device name interface name]
    user@host# set action-parameters [action-parameters...]
  6. (Optional) Load the local file that contains the action congestion point implementation. This file is the uncompiled Python source code or the compiled result of the Java file (binary .class or .jar file).
    [edit shared admission-control device name interface name]
    user@host# set action-file-name action-file-name
  7. (Optional) Verify your configuration. 
    [edit shared admission-control device name interface name] 
user@host# show 

    

    8. 




Configuring Bandwidths for Services in the Backbone Network


To configure bandwidths for services in the
same way for edge and backbone congestion points:




Configuring Congestion Points for Services in the Backbone
Network


You must assign a congestion point to each
service that SRC-ACP manages. When SRC-ACP receives a service authorization
event, congestion points for a service session can be determined by: 



To configure congestion points with congestion
point classification: 


    

  1. From configuration mode, access the configuration statement
that configures services. 

    

    user@host# edit services global service name admission-control congestion-point-classification 

    

    

    
    

    For more information about services,
see Overview of Services for the SRC Software. 
    

    2. 

  2. Specify the backbone congestion point expression. 

    

    [edit services global service name admission-control congestion-point-classification] 
    

    user@host# set expression [expression...] 
    

    

    
    

    The syntax for a backbone congestion
point expression is defined in the format <NetworkDevice>/<NetworkInterface>/<InstanceID>
which maps to a congestion point. 
    


    For information about congestion point expressions, see Congestion Point Expressions. For information
about the attributes that can be embedded in the expression, see Plug-In Attributes for Use with Backbone Congestion Point Expressions. 
    

    3. 

  3. (Optional) Specify the backbone congestion point script. 

    

    [edit services global service name admission-control congestion-point-classification] 
    

    user@host# set script script 

    

    

    
    

    For information about congestion point
functions, see Using Functions for Backbone Congestion Point Classification Scripts. 
    

    4. 



To configure congestion points with congestion
point profiles: 


    

  1. From configuration mode, access the configuration statement
that configures services. 

    

    user@host# edit services global service name admission-control 

    

    

    
    

    For more information about services,
see Overview of Services for the SRC Software. 
    

    2. 

  2. (Optional) Specify the backbone congestion points. This
value is ignored if you configure congestion points with congestion
point classification. 

    

    [edit services global service name admission-control] 
    

    user@host# set congestion-points [congestion-points...] 
    

    

    
    

    The backbone congestion point is defined
in the format <-vrName->/<-serviceName->, which locates a congestion
point profile that contains a list of congestion points. 
    


    3. 




Plug-In Attributes for Use with Backbone Congestion Point Expressions


These plug-in attributes must be available for service
authorization and service tracking events. 




accountingId








ifRadiusClass








ifSessionId








interfaceAlias








interfaceDescr








interfaceName








loginName









nasIp







nasPort








portId







primaryUserName








radiusClass








serviceName








serviceScope








serviceSessionName








serviceSessionTag








sspHost








substitutions.<substitution name>








userIp







userMacAddress








userType








vrName







Using Functions for Backbone Congestion Point Classification
Scripts


SRC-ACP provides the following functions
to use in backbone congestion point classification scripts:




Configuring Congestion Point Profiles in the Directory


If you are using congestion point classification, you
do not need to configure congestion point profiles. 


To configure individual backbone congestion point
profiles: 


    

  1. From configuration mode, access the configuration statement
that configures congestion point profiles. 

    

    user@host# edit shared congestion-points profile name 

    

    

    
    

    Enter the name of the virtual router
that supports the congestion point. 
    

    2. 

  2. (Optional) Verify your configuration.

    [edit shared congestion-points profile name] 
user@host# show 

    

    

    3. 




Assigning Interfaces to Congestion Point Profiles


If you are using congestion point classification, you
do not need to assign interfaces to congestion point profiles.


You must assign interfaces either to VRs or to
individual services under the VRs. Services inherit interface assignments
from the associated VR unless you assign an interface to the individual
service. This network interface lists the DNs of interfaces associated
with backbone congestion point profiles. 


Use the following configuration statements to configure
interface assignments: 





shared congestion-points profile name { 


     interface [interface...]; 


}





To assign interfaces to congestion point
profiles: 


    

  1. From configuration mode, access the configuration statement
that configures congestion point profiles. 

    

    user@host# edit shared congestion-points profile name 

    

    

    
    

    Enter the name of the network device
to which you want to assign the congestion point profile. 
    

    2. 

  2. (Optional) Specify the interfaces associated with a congestion
point profile for this subscriber. 

    

    [edit shared congestion-points profile name] 
    

    user@host# set interface interface 

    

    

    
    

    3. 

  3. (Optional) Verify your configuration.

    [edit shared congestion-points profile name] 
user@host# show 

    

    

    4. 



 


Related Topics




[Contents]
[Prev]
[Next]

[Index]

[Report an Error]










Copyright © 2009, Juniper Networks, Inc.
All rights reserved.
	Trademark Notice.