Juniper JUNOSE SOFTWARE 11.2.X - BROADBAND ACCESS CONFIGURATION GUIDE 7-20-2010 Configuration Manual page 134

JunosE 11.2.x Broadband Access Configuration Guide
sscc restart
96
Use to configure support for L2TP LAC interfaces on the SRC client. LAC support enables
policy and QoS configuration on L2TP interfaces.
When you configure LAC interfaces to be managed by the SRC client, the router
generates COPS messages for every LAC interface created and removed from the
router and sends them to the COPS server.
Such messages contain the necessary details about the newly created and removed
LAC interfaces that enable the SRC software or the COPS server to determine the
policy and QoS management for these interfaces
Observe the following guidelines when you configure the policy and QoS settings
support for L2TP LAC interfaces:
Access Node Control Protocol (ANCP), also known as Layer 2 Control (L2C) rate
report, which contains the a QoS adjustment factor to be applied to the upstream
data rate and downstream data rate reported by ANCP for a DSL type, for L2TP LAC
interfaces is not supported.
LAC interfaces that participate in L2TP tunnel switching are not supported for
management of policy and QoS settings by the SRC client.
L2TP dial-out sessions, in which VPNs that use B-RAS to dial out to remote offices
that have only narrowband dial-up access, are not supported for policy and QoS
management by the COPS client.
L2TP network server (LNS) sessions are not supported for policy and QoS
management by the COPS client because the interfaces configured on router, which
functions as an LNS, are not reported as L2TP interfaces to the SRC software.
Example
host1(config)#sscc protocol lac
Use the no version to restore the default, which is to disable L2TP LAC support on the
SRC client.
See sscc protocol lac
Use to force the router to restart a COPS connection to, and resynchronize with, the
SRC software, without removing the SRC client. The no sscc enable cops command
removes the SRC client.
When you issue this command, the SRC client closes the connection and connects
again to the SRC software, which then requests complete synchronization. As part of
the synchronization, the SRC client provides information about the policies that are
already installed on the router to the SRC software.
To enable a complex restart where the SRC client closes the connection and clears
the PIB structures and tables, use the optional clean-state keyword. Then, the SRC
client connects to the SRC software, which requests full synchronization, which restores
correct policies and QoS provisioning. Using this option consumes more time because
the command enables the router to clear the existing PIB structures in addition to
performing the synchronization.
Copyright © 2010, Juniper Networks, Inc.