Configuring the SRC Client

You can configure SRC clients on a per-virtual-router basis. To configure the SRC client:

  1. Enable the SRC client and plug-ins such as IP, DHCP, and DHCPv6. With the CLI sscc enable command, you can specify BER-encoded information exchange for COPS-PR.
    host1(config)#sscc enable cops-pr
  2. Specify the IP addresses of up to three service activation engines (SAEs) (primary, secondary, and tertiary). You can optionally specify the port on which the SAEs listen for activity.
    host1(config)#sscc primary address host1(config)#sscc secondary address 192.168.12.1 port 3288
  3. (Optional) Enable policy and QoS configuration support for IPv6 interfaces.
    host1(config)#sscc protocol ipv6
  4. (Optional) Enable policy and QoS configuration support for L2TP interfaces on an L2TP access concentrator (LAC).
    host1(config)#sscc protocol lac
  5. (Optional) Specify on which router the TCP/COPS connection is to be established.
    host1(config)#sscc transportRouter chicago

    Note: If a COPS connection is in the open state (displayed in the “The Connection State is” field in the output of the show sscc info command), the router that you configure on which the COPS connection is to be established by using the sscc transportRouter name command does not take effect.

  6. (Optional) Specify a fixed source address for the TCP/COPS connection created for an SRC client session.
    host1(config)#sscc sourceAddress 10.9.123.8
  7. (Optional) Specify a fixed source interface for the TCP/COPS connection.
    host1(config)#sscc sourceInterface atm 3/0
  8. (Optional) Specify the delay period during which an SRC client waits for a response from the SAE.
    host1(config)#sscc retryTimer 120
  9. (Optional) Specify the time period until which the rebooted SRC client waits for the primary SRC server to establish a connection with the SRC client. If the connection is not established within the configured time period, the SRC client selects the SRC server randomly, which is the default behavior of the SRC client.
    host1(config)#sscc connectivityTimer 5

    Note: The connectivity timer and ping operation to the primary SRC server are initiated when the first uplink or downlink line module other than the ES2 4G or ES2 10G ADV LMs with ES2-S1 Service IOA comes online. The ping operation is tried every 3 seconds after the timer is started until the timer stops or expires. The timer is stopped after a successful ping response is received.

  10. (Optional) Enable the user IP address mask to be sent to an SRC server in place of the interface IP address mask for a virtual router.
    host1(config)#sscc option user-ip-mask-override
  11. (Optional) Enable the calling station ID to be sent to an SRC server for a virtual router.
    host1(config)#sscc option send-calling-station-id

    You can configure a virtual router to send the default calling station ID or the overridden calling station ID to an SRC server irrespective of the RADIUS settings. If you want to enable the SRC client to send the Calling-Station-Id [31] RADIUS attribute to the COPS server only if this attribute is included in the RADIUS Access-Request, Acct-Start, or Acct- Stop message, you can use the radius-default-value attribute with the sscc option send-calling-station-id command.

    host1(config)#sscc option send-calling-station-id radius-default-value

    If you want to enable the SRC client to send the Calling-Station-Id [31] RADIUS attribute to the COPS server, regardless of whether this attribute is included in the RADIUS Access-Request, Acct-Start, or Acct- Stop message, you can use the radius-overridden-value attribute with the sscc option send-calling-station-id command.

    host1(config)#sscc option send-calling-station-id radius-overridden-value

    You must configure either the radius calling-station-format command or the radius override calling-station-id remote-circuit-id before you enable the functionality to cause the calling station ID to be always sent to an SRC server for a virtual router, regardless of whether the ID is included or excluded from the Access-Request and Acct-Start messages.

    Note: If you did not configure Calling-Station-Id attribute format using the radius calling-station-format command or did not configure the PPPoE remote circuit ID to be used in RADIUS messages instead of Calling-Station-Id using the radius override calling-station-id command, the Calling-Station-Id attribute is sent to the COPS server from the SRC client only if this attribute is contained in the RADIUS messages. In such a scenario, the attribute is not sent from the SRC client to the COPS server even if you configured the sscc option send-calling-station-id radius-overridden-value command.

  12. (Optional) Enable the local QoS profile attachment information to be sent to an SRC server for a virtual router.
    host1(config)#sscc option send-local-qos-profile-config
  13. (Optional) Enable the LAC-side NAS-IP address information to be sent to an SRC server for a virtual router.
    host1(config)#sscc option send-lac-nas-ip
  14. (Optional) Enable the LAC-side NAS-Port information to be sent to an SRC server for a virtual router.
    host1(config)#sscc option send-lac-nas-port
  15. (Optional) Enable the SRC client to obtain updated line-rate parameters from ANCP and transmit them to the COPS server.
    host1(config)#sscc update-policy-request enable
  16. (Optional) Restart a COPS connection to, and resynchronize with, an SRC server.
    host1#sscc restart

Related Documentation