Access (Dynamic Access Routes) - Juniper EX3400 Features Manual

access (Dynamic Access Routes)

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