routing-service (Dynamic Profiles)
Syntax
routing-service (disable <:$junos-routing-services> | enable<:$junos-routing-services>);
Hierarchy Level
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-name]
Description
Enable configuration of additional routing protocols required by client connections on dynamically created enhanced subscriber management interfaces.
When clients use only the standard access-internal routes, access routes, and framed routes, you do not need to configure routing services. In other words, the routing service configuration is not required for simple client reachability purposes.
You do not need to configure routing services for Internet Group Management Protocol (IGMP) and the Multicast Listener Discovery (MLD) protocol because these protocols are natively supported on enhanced subscriber management interfaces.
routing-service is supported for the Layer
2 Tunneling Protocol (L2TP) network server subscribers and Point-to-Point
Protocol over Ethernet (PPPoE) subscribers. Any other access models,
otherwise mentioned, for example aggregated inline service interface,
Multilink Point-to-Point Protocol (MLPPP) over L2TP network server
(LNS) are not supported.
Enable configuration of all routing protocols except Internet
Group Management Protocol (IGMP) and the Multicast Listener Discovery
(MLD) protocol on dynamically created enhanced subscriber management
interfaces. IGMP and MLD are natively supported on enhanced subscriber
management interfaces, and therefore do not require you to specify
the routing-service statement in the dynamic profile.
When a dynamic profile containing the routing-service statement is instantiated, the router creates an enhanced subscriber
management logical interface, also referred to as a pseudo logical
interface, in the form demux0.nnnnnnnnnn (for
example, demux0.3221225472). Any associated subscriber routes or routes
learned from a routing protocol running on the enhanced subscriber
management interface use this pseudo interface as the next-hop interface.
The routing-service statement replaces the
deprecated routing-services statement. If you upgrade to Junos OS Release 18.4R1 or higher with
a configuration that has active subscribers with routing-services enabled, then routing services remain enabled for those subscribers.
For all new subscribers after the upgrade, you must use the routing-service statement.
You can specify the $junos-routing-services predefined variable to determine, per subscriber, whether routing services can be enabled or disabled by the value of the Routing-Services VSA (26-212) returned in the RADIUS Access-Accept message during subscriber authentication. A value of 0x0000 disables installation of routing services. A value of 0x0001 enables the installation of routing services. Any other value is rejected.
The routing-service statement is not supported
for DHCP dynamic profiles. Do not enable it for DHCP dynamic profiles.
However, if the routing-service statement is enabled for
a dynamic VLAN profile, that VLAN can stack DHCP subscribers.
Options
| disable | Disable routing services for all subscribers instantiated on the interface by the profile. |
| disable:$junos-routing-services | Prevent routing services from being enabled or disabled by the value of the Routing-Services VSA (26-212) for the subscriber being authenticated. |
| enable | Enable routing services for all subscribers instantiated on the interface by the profile. |
| enable:$junos-routing-services | Allow routing services to be enabled or disabled by the value of the Routing-Services VSA (26-212) for the subscriber being authenticated. |
Required Privilege Level
interface
Release Information
Statement introduced in Junos OS Release 18.4R1.