Configuring SRC-ACP to Manage the Backbone Network
To configure SRC-ACP to manage the backbone network, you must:
- Configure network interfaces that represent locations of congestion points in the directory.
- (Optional) Configure an action congestion point.
- Configure guaranteed bandwidths for services.
- Assign network interfaces to services.
- Create congestion points in the directory.
- Assign network interfaces to congestion points.
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. 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 for the Edge Network.
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:
- Create custom congestion point applications that authorize service activation and track service start and stop events.
- Obtain congestion point information from remote update.
- Retrieve congestion point status.
- Track congestion point state.
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 SRC 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. 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 (see Configuring Action Congestion Points).
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 (see Configuring SRC-ACP Redundancy).
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...];}To configure an action congestion point:
- From configuration mode, access the configuration statement that configures network interfaces.
user@host# edit shared admission-control device name interface nameEnter the name of the network device and the name of the virtual router.
- (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);- (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- (Optional) Specify the URL or the content of the script file.
[edit shared admission-control device name interface name]user@host# set action-file-url action-file-url- (Optional) Specify the parameter as an attribute=value pair.
[edit shared admission-control device name interface name]user@host# set action-parameters [action-parameters...]- (Optional) Verify your configuration.
[edit shared admission-control device name interface name]user@host#show
Configuring Bandwidths for Services in the Backbone Network
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 in the Edge Network.
Configuring Congestion Points for Services in the Backbone Network
You must assign a congestion point to each service that SRC-ACP manages.
To configure values for services:
- From configuration mode, access the configuration statement that configures services.
user@host# edit services global sae-service name admission-controlFor more information about configuring services, see SRC-PE Services and Policies Guide, Chapter 1, Managing Services with the SRC CLI.
- (Optional) Specify the backbone congestion points.
[edit services global sae-service name admission-control]user@host# set congestion-points [congestion-points...]The backbone congestion point is defined in the format <-vrName->/<-serviceName->.
- To allow the software to automatically define the congestion point, use the entry <-vrName->/<-serviceName->. When SRC-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.
Configuring Congestion Points in the Directory
To configure individual backbone congestion points:
- From configuration mode, access the configuration statement that configures congestion points.
user@host# edit shared congestion-points profile nameEnter the name of the virtual router that supports the congestion point.
Assigning Interfaces to Congestion Points
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 points.
Use the following configuration statements to configure interface assignments:
shared congestion-points profile name {interface [interface...];}To assign interfaces to congestion points:
- From configuration mode, access the configuration statement that configures congestion points.
user@host# edit shared congestion-points profile nameEnter the name of the network device to which you want to assign the congestion point.