Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

ON THIS PAGE

Configuring the SAE for SRC ACP (SRC CLI)

 

You must configure the SAE to recognize SRC ACP by adding information about SRC ACP to the SAE properties. The tasks for configuring the SAE for SRC ACP are:

Configuring SRC ACP as an External Plug-In

To configure an external plug-in for the SAE:

  1. From configuration mode, access the configuration statement that configures the external plug-ins.

  2. Specify the plug-in attributes.

    For edge and dual modes—upstream-bandwidth, downstream-bandwidth, service-name, router-name, login-name, user-dn, port-id, session-id, user-ip-address, nas-ip, user-session-id, event-time

    For backbone mode—upstream-bandwidth, downstream-bandwidth, service-name, router-name, session-id, nas-ip, event-time

    For more information about configuring plug-in attributes, see Configuring the SAE for External Plug-Ins (SRC CLI).

Configuring Event Publishers

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

  • (Edge and dual mode only) Global subscriber tracking

  • Global service authorization

  • Global service tracking

For information about configuring event publishers, see Special Types of Event Publishers. Identify the instance of SRC ACP by the name of the host on which you configured it.

Configuring the SAE to Monitor Interfaces for Congestion Points

Note

Configure this feature only if SRC 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.

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 be configured (see Configuring Network Interfaces in the Directory for the Backbone Network).

To configure the ACP interface listener as an internal plug-in for the SAE:

  1. From configuration mode, access the configuration statement that configures the ACP interface listener.

  2. Specify the IP address or name of the host that supports the directory that contains backbone service definitions and network interfaces.

  3. Specify the DN of the directory entry that defines the username with which the plug-in accesses the directory.

  4. Specify the password with which the plug-in accesses the directory.

  5. Specify whether the connection to the directory uses secure LDAP. If you do not configure a security protocol, plain socket is used.

  6. Specify the DN at which SRC ACP stores backbone congestion points.

  7. Specify the DN at which SRC ACP stores edge congestion points.

  8. (Optional) Specify the maximum time that the plug-in waits for the router to respond.

  9. Specify the object reference for the ACP plug-in, as defined by the object reference for SRC ACP (see information about the acp-ior option in Configuring SRC ACP Properties (SRC CLI)).

  10. (Optional) Verify your configuration.