access (Dynamic Access Routes)
Syntax access {
route prefix {
next-hop next-hop;
metric route-cost;
preference route-distance;
tag route-tag;
}
Hierarchy Level [edit dynamic-profiles profile-name routing-instances $junos-routing-instance
routing-options],
[edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
rib routing-table-name],
[edit dynamic-profiles profile-name routing-options]
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.
Description Dynamically configure access routes.
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].
Options The remaining statements are explained separately.
Required Privilege
Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release History Table DescriptionRelease
Starting in Junos OS Release 15.1, we recommend that you use only access
routes for framed route support.
15.1
Related
Documentation
• Configuring Dynamic Access Routes for Subscriber Management
141Copyright © 2017, Juniper Networks, Inc.
Chapter 12: Configuration Statements (DHCP and DHCP Relay)