Configuring Dynamic Profiles for PPP
A dynamic profile acts as a template that enables you to create, update, or remove a
configuration that includes attributes for client access (for example, interface or protocol)
or service (for example, IGMP). Using these profiles you can consolidate all of the common
attributes of a client (and eventually a group of clients) and apply the attributes
simultaneously.
After they are created, the profiles reside in a profile library on the router. You can then
use the dynamic-profile statement to attach profiles to interfaces. To assign a dynamic
profile to a PPP interface, you can include the dynamic-profile statement at the [edit
interfaces interface-name unit logical-unit-number ppp-options] hierarchy level:
[edit interfaces interface-name unit logical-unit-number ppp-options]
dynamic-profile profile-name;
To monitor the configuration, issue the show interfaces interface-name command.
For information about dynamic profiles, see Dynamic Profiles Overview in the Junos
Subscriber Access Configuration Guide.
For information about creating dynamic profiles, see Configuring a Basic Dynamic Profile
in the Junos Subscriber Access Configuration Guide.
For information about assigning a dynamic profile to a PPP interface, see Attaching
Dynamic Profiles to Static PPP Subscriber Interfaces in the Junos Subscriber Access
Configuration Guide.
NOTE: Dynamic profiles for PPP subscribers are supported only on PPPoE
interfaces for this release.
Related
Documentation
Configuring Dynamic Authentication for PPP Subscribers•
Configuring the PPP Challenge Handshake Authentication Protocol
•
PPP Challenge Handshake Authentication Protocol on page 493
•
Configuring the PPP Challenge Handshake Authentication Protocol on page 494
•
Displaying the Configured PPP Challenge Handshake Authentication
Protocol on page 495
PPP Challenge Handshake Authentication Protocol
For interfaces with PPP encapsulation, you can configure interfaces to support the PPP
Challenge Handshake Authentication Protocol (CHAP), as defined in RFC 1994, PPP
Challenge Handshake Authentication Protocol (CHAP). When you enable CHAP on an
interface, the interface can authenticate its peer and can be authenticated by its peer.
By default, PPP CHAP is disabled. If CHAP is not explicitly enabled, the interface makes
493Copyright © 2017, Juniper Networks, Inc.
Chapter 16: Configuring Point-to-Point Protocol (PPP)
To Next Page
Loading...
Need help?
General
