Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

access-internal (Dynamic Access-Internal Routes)

Syntax

Hierarchy Level

Description

(Releases earlier than Junos OS Release 15.1) Dynamically configure access-internal routes in a dynamic client profile. Access-internal routes are optional, but are used instead of access routes if the next-hop address is not specified in the Framed-Route Attribute [22] for IPv4 or the Framed-IPv6-Route attribute [99] for IPv6.

Note:

Starting in Junos OS Release 15.1, we recommend that you use only access routes for framed route support. We recommend that you do not use access-internal routes. If you configure the access-internal statement in the dynamic profile, it is ignored. The subscriber’s address is stored in the session database entry before the dynamic profile installs the framed route, enabling the next-hop address to be resolved when it is not explicitly specified in the Framed-Route RADIUS attribute (22) or Framed-IPv6-Route attribute [99].

The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 9.5.

Support at the [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options] and [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options rib routing-table-name] hierarchy levels introduced in Junos OS Release 10.1.

Release History Table
Release
Description
15.1
Starting in Junos OS Release 15.1, we recommend that you use only access routes for framed route support.