Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Predefined Variables in Dynamic Profiles

 

Junos OS Predefined Variables

Junos OS contains many predefined variables. The dynamic profile obtains and replaces values for these variables from an incoming client data packet and configuration (local and RADIUS). These variables are predefined—you use them in the body of a dynamic profile without first having to define the variables at the [dynamic-profiles profile-name variables] hierarchy level. Table 1 provides a list of predefined variables, their descriptions, and where in the Junos OS hierarchy you can configure them.

Table 1: Junos OS Predefined Variables and Definitions

Variable

Definition

Access and Access-Internal Routes

$junos-framed-route-cost

Cost metric of an IPv4 access route. You specify this variable with the metric statement at the [edit dynamic-profiles profile-name routing-options access route address] hierarchy level.

$junos-framed-route-distance

Distance of an IPv4 access route. You specify this variable with the preference statement at the [edit dynamic-profiles profile-name routing-options access route address] hierarchy level.

$junos-framed-route-ip-address-prefix

Route prefix of an IPv4 access route. You specify this variable at the [edit dynamic-profiles profile-name routing-options access] hierarchy level for the route statement.

$junos-framed-route-ipv6-address-prefix

Route prefix of an IPv6 access route. You specify this variable with the route statement at either of the following hierarchy levels:

  • [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options rib $junos-ipv6-rib access]

  • [edit dynamic-profiles profile-name routing-options rib $junos-ipv6-rib access]

$junos-framed-route-ipv6-cost

Cost metric of an IPv6 access route. You specify this variable with the metric statement at either of the following hierarchy levels:

  • [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options rib $junos-ipv6-rib access route $junos-framed-route-ipv6-address-prefix]

  • [edit dynamic-profiles profile-name routing-options rib $junos-ipv6-rib access route $junos-framed-route-ipv6-address-prefix]

$junos-framed-route-ipv6-distance

Distance of an IPv6 access route. You specify this variable with the preference statement at either of the following hierarchy levels:

  • [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options rib $junos-ipv6-rib access route $junos-framed-route-ipv6-address-prefix]

  • [edit dynamic-profiles profile-name routing-options rib $junos-ipv6-rib access route $junos-framed-route-ipv6-address-prefix]

$junos-framed-route-ipv6-nexthop

IPv6 next-hop address of an access route. You specify this variable with the next-hop statement at either of the following hierarchy levels:

  • [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options rib $junos-ipv6-rib access route $junos-framed-route-ipv6-address-prefix]

  • [edit dynamic-profiles profile-name routing-options rib $junos-ipv6-rib access route $junos-framed-route-ipv6-address-prefix]

$junos-framed-route-ipv6-tag

Tag value of an IPv6 access route. You specify this variable with the tag statement at either of the following hierarchy levels:

  • [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options rib $junos-ipv6-rib access route $junos-framed-route-ipv6-address-prefix]

  • [edit dynamic-profiles profile-name routing-options rib $junos-ipv6-rib access route $junos-framed-route-ipv6-address-prefix]

$junos-framed-route-nexthop

IPv4 next-hop address of an access route. You specify this variable at the [edit dynamic-profiles profile-name routing-options access route address] hierarchy level for the next-hop statement.

$junos-framed-route-tag

Tag value of an IPv4 access route. You specify this variable at the [edit dynamic-profiles profile-name routing-options access route address] hierarchy level for the tag statement.

$junos-framed-route-tag2

Tag2 value for static routes. You specify this variable at the [edit dynamic-profiles profile-name routing-options access route $junos-framed-route-ip-address-prefix] hierarchy level for the tag2 statement.

$junos-interface-name

Logical interface of an access-internal route. DHCP or PPP supplies this information when the subscriber logs in. You specify this variable at the [edit dynamic-profiles profile-name routing-options access-internal route address] hierarchy level for the qualified-next-hop statement.

This variable is also used for creating dynamic IP demux interfaces.

$junos-ipv6-rib

Routing table for an IPv6 access route. You specify this variable with the rib statement at the [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options] hierarchy level.

You can use this variable to specify a nondefault routing instance for the route.

$junos-subscriber-ip-address

IP address of a subscriber identified in an access-internal route. You specify this variable at the [edit dynamic-profiles profile-name routing-options access-internal] hierarchy level for the route statement.

This variable is also used for creating dynamic IP demux interfaces.

$junos-subscriber-mac-address

MAC address for a subscriber identified in an access-internal route. You specify this variable at the [edit dynamic-profiles profile-name routing-options access-internal route address qualified-next hop underlying-interface] hierarchy level for the mac-address statement.

Dynamic Protocols

$junos-igmp-access-group-name

Specifies the access list to use for the source (S) filter.

$junos-igmp-access-source-group-name

Specifies the access list to use for the source-group (S,G) filter.

$junos-igmp-enable

Ensures that IGMP is not disabled on the interface by an AAA-based authentication and management method (for example, RADIUS). You specify this variable at the [dynamic-profiles profile-name protocols igmp] hierarchy level for the interface statement.

$junos-igmp-immediate-leave

Enables IGMP immediate leave on the interface. You specify this variable at the [dynamic-profiles profile-name protocols igmp] hierarchy level for the interface statement.

$junos-igmp-version

IGMP version configured in a client access profile. Junos OS obtains this information from the RADIUS server when a subscriber accesses the router. The version is applied to the accessing subscriber when the profile is instantiated. You specify this variable at the [dynamic-profiles profile-name protocols igmp] hierarchy level for the interface statement.

$junos-interface-name

Name of the dynamic interface to which the subscriber access client connects. Its use is in dynamically enabling IGMP on the subscriber interface. You specify this variable at the [dynamic-profiles profile-name protocols igmp] hierarchy level for the interface statement.

The interface name is derived from concatenating the $junos-interface-ifd-name and the $junos-underlying-interface-unit variables obtained when a subscriber is created dynamically at the [dynamic-profiles profile-name interfaces] hierarchy level.

$junos-ipv6-ndra-prefix

Prefix value for the router advertisement interface. Junos OS obtains this information from the RADIUS server when a subscriber accesses the router. The prefix value is applied to the accessing subscriber when the profile is instantiated. You specify this variable at the [dynamic-profiles profile-name protocols router-advertisement interface $junos-interface-name] hierarchy level.

$junos-mld-access-group-name

Specifies the access list to use for the group (G) filter.

$junos-mld-access-source-group-name

Specifies the access list to use for the source-group (S,G) filter.

$junos-mld-enable

Ensures that MLD is not disabled on the interface by an AAA-based authentication and management method (for example, RADIUS). You specify this variable at the [dynamic-profiles profile-name protocols mld] hierarchy level for the interface statement.

$junos-mld-immediate-leave

Enables MLD immediate leave on the interface. You specify this variable at the [dynamic-profiles profile-name protocols mld] hierarchy level for the interface statement.

$junos-mld-version

MLD version configured in a client access profile. Junos OS obtains this information from the RADIUS server when a subscriber accesses the router. The version is applied to the accessing subscriber when the profile is instantiated. You specify this variable at the [dynamic-profiles profile-name protocols mld] hierarchy level for the interface statement.

Dynamic CoS — Traffic-Control Profile Parameters

$junos-cos-adjust-minimum

Minimum adjusted shaping rate configured in a traffic-control profile in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the adjust-minimum statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

$junos-cos-byte-adjust

Byte adjustment value configured in a traffic-control profile in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the bytes option with the overhead-accounting statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

$junos-cos-byte-adjust-cell

Overhead bytes when downstream ATM traffic is in cell-mode.

Note: Do not configure the $junos-cos-byte-adjust-cell variable when the $junos-cos-byte-adjust variable is configured.

$junos-cos-byte-adjust-frame

Overhead bytes when downstream ATM traffic is in frame-mode.

Note: Do not configure the $junos-cos-byte-adjust-frame variable when the $junos-cos-byte-adjust variable is configured.

$junos-cos-delay-buffer-rate

Delay-buffer rate configured in a traffic-control profile in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the delay-buffer-rate statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

$junos-cos-excess-rate

Excess rate configured in a traffic-control profile in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the excess-rate statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

$junos-cos-excess-rate-high

Rate configured for excess high-priority traffic in a traffic-control profile in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the excess-rate-high statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

$junos-cos-excess-rate-low

Rate configured for excesslow-priority traffic in a traffic-control profile in a dynamic profile for subscriber access. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the excess-rate-low statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

$junos-cos-guaranteed-rate

Guaranteed rate configured in a traffic-control profile in a dynamic profile Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the guaranteed-rate statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

$junos-cos-guaranteed-rate-burst

Burst size for the guaranteed rate that is configured in a traffic-control profile in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable with the burst-size option in the guaranteed-rate statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

$junos-cos-scheduler-map

Scheduler-map name configured in a traffic-control profile in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the scheduler-map statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

Note: The scheduler map can be defined dynamically (at the [edit dynamic-profiles profile-name class-of-service scheduler-maps] hierarchy level) or statically (at the [edit class-of-service scheduler-maps] hierarchy level).

$junos-cos-shaping-mode

Shaping mode configured in a traffic-control profile in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the overhead-accounting statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

$junos-cos-shaping-rate

Shaping rate configured in a traffic-control profile in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the shaping-rate statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

$junos-cos-shaping-rate-burst

Burst size for the shaping rate configured in a traffic-control profile in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable with the burst-size option in the shaping-rate statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

$junos-cos-shaping-rate-excess-high

Shaping rate configured for excess high-priority traffic in a traffic-control profile for a dynamic interface set or dynamic ACI interface set at a household level. Specifying this variable in a traffic-control profile for a dynamic subscriber interface is prohibited.

$junos-cos-shaping-rate-excess-high-burst

Shaping rate burst size configured for excess high-priority traffic in a traffic-control profile for a dynamic interface set or dynamic ACI interface set at a household level. Specifying this variable in a traffic-control profile for a dynamic subscriber interface is prohibited.

$junos-cos-shaping-rate-excess-low

Shaping rate configured for excess low-priority traffic in a traffic-control profile for a dynamic interface set or dynamic ACI interface set at a household level. Specifying this variable in a traffic-control profile for a dynamic subscriber interface is prohibited.

$junos-cos-shaping-rate-excess-low-burst

Shaping rate burst size configured for excess low-priority traffic in a traffic-control profile for a dynamic interface set or dynamic ACI interface set at a household level. Specifying this variable in a traffic-control profile for a dynamic subscriber interface is prohibited.

$junos-cos-shaping-rate-priority-high

Shaping rate configured for high-priority traffic in a traffic-control profile for a dynamic interface set or dynamic ACI interface set at a household level. Specifying this variable in a traffic-control profile for a dynamic subscriber interface is prohibited.

$junos-cos-shaping-rate-priority-high-burst

Shaping rate burst size configured for high-priority traffic in a traffic-control profile for a dynamic interface set or dynamic ACI interface set at a household level. Specifying this variable in a traffic-control profile for a dynamic subscriber interface is prohibited.

$junos-cos-shaping-rate-priority-low

Shaping rate configured for low-priority traffic in a traffic-control profile for a dynamic interface set or dynamic ACI interface set at a household level. Specifying this variable in a traffic-control profile for a dynamic subscriber interface is prohibited.

$junos-cos-shaping-rate-priority-low-burst

Shaping rate burst size configured for low-priority traffic in a traffic-control profile for a dynamic interface set or dynamic ACI interface set at a household level. Specifying this variable in a traffic-control profile for a dynamic subscriber interface is prohibited.

$junos-cos-shaping-rate-priority-medium

Shaping rate configured for medium-priority traffic in a traffic-control profile for a dynamic interface set or dynamic ACI interface set at a household level. Specifying this variable in a traffic-control profile for a dynamic subscriber interface is prohibited.

$junos-cos-shaping-rate-priority-medium-burst

Shaping rate burst size configured for medium-priority traffic in a traffic-control profile for a dynamic interface set or dynamic ACI interface set at a household level. Specifying this variable in a traffic-control profile for a dynamic subscriber interface is prohibited.

$junos-cos-traffic-control-profile

Traffic-control profile configured in a dynamic profile for subscriber access. The Junos OS obtains the profile information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the traffic-control-profiles statement at the [edit dynamic-profiles profile-name class-of-service] hierarchy level.

Dynamic CoS — Scheduler Parameters

$junos-cos-scheduler

Name of a scheduler configured in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable at the [edit dynamic-profiles profile-name class-of-service schedulers] hierarchy level.

$junos-cos-scheduler-bs

Buffer size as a percentage of total buffer, specified for a scheduler configured in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the buffer-size statement with the percent option at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] hierarchy level.

$junos-cos-scheduler-pri

Packet-scheduling priority value specified for a scheduler configured in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the priority statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] hierarchy level.

$junos-cos-scheduler-dropfile-any

Name of the drop profile for random early detection (RED) for loss-priority level any specified for a scheduler configured in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the drop-profile statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name drop-profile-map loss-priority any protocol any] hierarchy level.

Note: The drop profile must be configured statically (at the [edit class-of-service drop-profiles] hierarchy level).

$junos-cos-scheduler-dropfile-high

Name of the drop profile for random early detection (RED) for loss-priority level high specified for a scheduler configured in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the drop-profile statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name drop-profile-map loss-priority high protocol any] hierarchy level.

Note: The drop profile must be configured statically (at the [edit class-of-service drop-profiles] hierarchy level).

$junos-cos-scheduler-dropfile-low

Name of the drop profile for random early detection (RED) for loss-priority level low specified for a scheduler configured in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the drop-profile statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name drop-profile-map loss-priority low protocol any] hierarchy level.

Note: The drop profile must be configured statically (at the [edit class-of-service drop-profiles] hierarchy level) for loss-priority low.

$junos-cos-scheduler-dropfile-medium-high

Name of the drop profile for random early detection (RED) for loss-priority level medium-high specified for a scheduler configured in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the drop-profile statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name drop-profile-map loss-priority medium-high protocol any] hierarchy level.

Note: The drop profile must be configured statically (at the [edit class-of-service drop-profiles] hierarchy level).

$junos-cos-scheduler-dropfile-medium-low

Name of the drop profile for random early detection (RED) for loss-priority level medium-low specified for a scheduler configured in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the drop-profile statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name drop-profile-map loss-priority medium-low protocol any] hierarchy level.

Note: The drop profile must be configured statically (at the [edit class-of-service drop-profiles] hierarchy level).

$junos-cos-scheduler-excess-priority

Priority value of the excess rate specified for a scheduler configured in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the excess-priority statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] hierarchy level.

$junos-cos-scheduler-excess-rate

Value of the excess rate specified for a scheduler configured in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the excess-rate statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] hierarchy level.

$junos-cos-scheduler-shaping-rate

Value of the shaping rate specified for a scheduler configured in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the shaping-rate statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] hierarchy level.

$junos-cos-scheduler-tx

Transmit rate specified for a scheduler configured in a dynamic profile. Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the dynamic profile is attached.

You reference this variable in the transmit-rate statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] hierarchy level.

Dynamic CoS — Dynamic Interface Sets

$junos-aggregation-interface-set-name

Name of a hierarchical CoS L2 interface set that represents a logical intermediate node (DPU-C or PON tree) in the access network. This is also known as the dynamic aggregation interface set. The variable take one of the following values:

  • When the hierarchical-access-network-detection option is configured for the access lines and the value of the Access-Aggregation-Circuit-ID-ASCII attribute (TLV 0x03) received either in the ANCP Port Up message or PPPoE PADR IA tags begins with a # character, then the variable takes the value of the remainder of the string after the # character. The # character identifies the string as a backhaul identifier.

  • When the hierarchical-access-network-detection option is not configured, or if the string does not begin with the # character, then the variable takes the value specified with the predefined-variable-defaults statement.

You reference this variable in the interface-set statement at the [edit dynamic-profiles profile-name interfaces] hierarchy level.

$junos-interface-set-name

Name of the interface set obtained from the RADIUS server Access-Accept message when a subscriber authenticates over the interface to which the dynamic profile is attached.

You reference this variable in the interface-set statement at the [edit dynamic-profiles profile-name interfaces] hierarchy level.

$junos-phy-ifd-interface-set-name

Locally generated name of an interface set that is associated with the underlying physical interface in a dynamic profile. This predefined variable enables you to group all the subscribers on a specific physical interface so that you can apply services to the entire group of subscribers.

This interface set is a default level 2 interface set for four-level hierarchies and a default level 3 interface set for five-level hierarchies.

You can use this predefined variable to conserve CoS resources in a mixed business and residential topology by collecting the residential subscribers into an interface set associated with the physical interface. This causes a level 2 node to be used for the interface set rather than one for each residential interface.

Otherwise, because the business and residential subscribers share the same interface and business subscribers require three levels of CoS, then three levels are configured for each residential subscriber. That results in an unnecessary level 2 node being consumed for each residential connection, wasting CoS resources.

You reference this variable in the interface-set statement at the [edit dynamic-profiles profile-name interfaces] hierarchy level.

$junos-phy-ifd-underlying-intf-set-name

Name of a default, topology-based interface set that is based on the physical interface name with a suffix of “-underlying” to conserve hierarchical CoS L2 nodes.

This interface is used as a default level 2 interface set.

You reference this variable in the interface-set statement at the [edit dynamic-profiles profile-name interfaces] hierarchy level.

$junos-svlan-interface-set-name

Locally generated name of an interface set for use by dual-tagged VLAN (S-VLAN) interfaces. The name is based on the outer tag of the dual-tagged VLAN. The format of the generated variable is physical_interface_name-outer_vlan_tag.

For example, an Ethernet interface of ge-1/1/0, with a dual-tagged VLAN interface that has an outer tag of 111, results in a value of ge-1/1/0-111 for $junos-svlan-interface-set-name.

You reference this variable in the interface-set statement at the [edit dynamic-profiles profile-name interfaces] hierarchy level.

$junos-tagged-vlan-interface-set-name

Locally generated name of an interface set that groups logical interfaces stacked over logical stacked VLAN demux interfaces. You can use this variable for either a 1:1 (dual-tagged; individual client) VLAN or N:1 (single tagged; service) VLAN. The format of the generated variable differs with VLAN type as follows:

  • Dual-tagged (client) VLAN—The format is physical_interface_name-outer_vlan_tag-inner_vlan_tag.

    For example, an Ethernet interface of ge-1/1/0, with a dual-tagged VLAN interface that has an outer tag of 111 and an inner tag of 200, results in a value of ge-1/1/0-111–200 for $junos-tagged-vlan-interface-set-name.

  • Single tagged (service) VLAN—The format is physical_interface_name-vlan_tag

    For example, an Ethernet interface of ge-1/1/0, with an N:1 VLAN that has a single tag of 200, results in a value of ge-1/1/0-200 for $junos-tagged-vlan-interface-set-name.

You reference this variable in the interface-set statement at the [edit dynamic-profiles profile-name interfaces] hierarchy level.

Dynamic Connectivity Fault Management Parameters

$junos-action-profile

Name of the action profile configured in a dynamic profile.

$junos-ccm-interval

Continuity check interval time configured in a dynamic profile.

$junos-loss-threshold

The number of continuity check messages lost before marking the remote MEP as down, configured in a dynamic profile.

$junos-ma-name-format

Name of the maintenance association name format configured in a dynamic profile.

$junos-md-name-format

Name of the maintenance domain format configured in a dynamic profile.

$junos-ma-name

Name of the maintenance association configured in a dynamic profile.

$junos-md-level

Value of ’Level’, configured in a dynamic profile.

$junos-md-name

Name of the maintenance domain configured in a dynamic profile.

$junos-mep-id

The ’MEP’ value configured in the dynamic profile.

$junos-remote-mep-id

The ’Remote MEP’ value configured in the dynamic profile.

Filters — RADIUS-obtained Policies

$junos-input-filter

Name of an input filter to be attached; filter name is derived from RADIUS VSA 26-10 (Ingress-Policy-Name) or RADIUS attribute 11 (Filter-ID) to the interface.

$junos-input-interface-filter

Name of an input filter to be attached to a family any interface; filter name is derived from RADIUS VSA 26-191 (Input-Interface-Filter) to the interface.

You can also specify the filter name with the $junos-input-interface-filter statement at the [edit dynamic-profiles profile-name interfaces interface-name unit logical-interface-number filter input] hierarchy level.

$junos-input-ipv6-filter

Name of an IPv6 input filter to be attached; filter name is derived from RADIUS VSA 26-106 (IPv6-Ingress-Policy-Name) to the interface.

$junos-output-filter

Name of an output filter to be attached; filter name is derived from RADIUS VSA 26-11 (Egress-Policy-Name) to the interface.

$junos-output-interface-filter

Name of an output filter to be attached to a family any interface; filter name is derived from RADIUS VSA 26-191 (Output-Interface-Filter) to the interface.

You can also specify the filter name with the $junos-output-interface-filter statement at the [edit dynamic-profiles profile-name interfaces interface-name unit logical-interface-number filter output] hierarchy level.

$junos-output-ipv6-filter

Name of an IPv6 output filter to be attached; filter name is derived from RADIUS VSA 26-107 (IPv6-Egress-Policy-Name) to the interface.

Services

$junos-input-ipv6-service-filter

Starting in Junos OS Release 17.2R1, name of an IPv6 input service filter to be attached. The filter name is derived from RADIUS-VSA 26-202 (IPv6 input service filter) to the interface.

You specify this variable at the [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number family inet6 service input service-set service-set-name service-filter] hierarchy level.

$junos-input-ipv6-service-set

Starting in Junos OS Release 17.2R1, name of an IPv6 service set to be attached. The service set name is derived from RADIUS-VSA 26-200 (IPv6 input service set) to the interface.

You specify this variable at the [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number family inet6 service input service-set] hierarchy level.

$junos-input-service-filter

Starting in Junos OS Release 17.2R1, name of an IPv4 input service filter to be attached. The filter name is derived from RADIUS-VSA 26-198 (IPv4 input service filter) to the interface.

You specify this variable at the [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number family inet service input service-set service-set-name service-filter] hierarchy level.

$junos-input-service-set

Starting in Junos OS Release 17.2R1, name of an IPv4 input service set to be attached. The service set name is derived from RADIUS-VSA 26-196 (IPv4 input service set) to the interface.

You specify this variable at the [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number family inet service input service-set] hierarchy level.

$junos-output-ipv6-service-filter

Starting in Junos OS Release 17.2R1, name of an IPv6 service filter to be attached. The filter name is derived from RADIUS-VSA 26-203 (IPv6 output service filter) to the interface.

You specify this variable at the [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number family inet6 service output service-set service-set-name service-filter] hierarchy level.

$junos-output-ipv6-service-set

Starting in Junos OS Release 17.2R1, name of an IPv6 service set to be attached. The service set name is derived from RADIUS-VSA 26-201 (IPv6 output service set ) to the interface.

You specify this variable at the [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number family inet6 service output service-set] hierarchy level.

$junos-output-service-filter

Starting in Junos OS Release 17.2R1, name of an IPv4 service filter to be attached. The filter name is derived from RADIUS-VSA 26-199 (IPv4 output service filter) to the interface.

You specify this variable at the [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number family inet service output service-set service-set-name service-filter] hierarchy level.

$junos-output-service-set

Starting in Junos OS Release 17.2R1, name of an IPv4 output service set to be attached. The service set name is derived from RADIUS-VSA 26-197 (IPv4 output service set ) to the interface.

You specify this variable at the [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number family inet service output service-set] hierarchy level.

$junos-pcef-profile

Starting in Junos OS Release 17.2R1, name of a PCEF profile to be attached. The profile name is derived from RADIUS-VSA 26-204 (PCEF profile) to the interface.

You specify this variable at the [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number service] hierarchy level.

$junos-pcef-rule

Starting in Junos OS Release 17.2R1, name of a PCC rule to activate. The rule name is derived from RADIUS-VSA 26-205 (PCEF rule) to the interface.

You specify this variable at the [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number service pcef pcef-profile-name activate] hierarchy level.

Subscriber Interfaces — Dynamic Demux Interfaces

$junos-interface-ifd-name

Name of the device to which the subscriber access client connects. All interfaces are created on this device. Its primary use is in creating single or multiple subscribers on a statically created interface. You specify this variable at the [dynamic-profiles profile-name interfaces] hierarchy level.

When creating a logical underlying interface for a dynamic VLAN demux interface, you must also specify this variable at the [dynamic-profiles profile-name interfaces demux0 unit $junos-interface-unit demux-options underlying-interface] hierarchy level.

$junos-interface-target-weight

Weight for an interface to associate it with an interface set and thus with the set’s aggregated Ethernet member link for targeted distribution. When an interface set does not have a weight, then the interface weight value for the first authorized subscriber interface is used for the set. The value is derived from RADIUS VSA 26-214 Interface-Target-Weight. Also associated with Diameter AVP 214.

$junos-interface-unit

Creates a unit number assigned to the logical interface. The router supplies this information when the subscriber accesses the network. You specify this variable at the [dynamic-profiles profile-name interfaces interface-name] hierarchy level for the unit statement.

$junos-ipv6-address

Selects the IPv6 address of the interface the subscriber uses. You specify this variable at the [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family family], [edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family family], [edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit” family family], and [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family family] hierarchy level for the address statement.

$junos-loopback-interface

Selects the loopback interface the subscriber uses. You specify this variable at the [dynamic profiles profile-name interfaces demux0 unit "$junos-interface-unit" family inet] hierarchy level for the unnumbered-address statement.

$junos-preferred-source-address

Selects the preferred IPv4 source address (family inet) associated with the loopback address used for the subscriber. You specify this variable at the [dynamic profiles profile-name interfaces demux0 unit "$junos-interface-unit" family inet unnumbered-address “$junos-loopback-interface”] hierarchy level for the preferred-source-address statement.

Note: Starting in Junos OS Release 16.1, when you specify a static logical interface for the unnumbered interface in a dynamic profile that includes the $junos-routing-instance predefined variable, you must not configure an IPv4 preferred source address. This constraint applies whether you use the $junos-preferred-source-address predefined variable or the preferred-source-address statement. Configuring the preferred source address in this circumstance causes a commit failure.

$junos-preferred-source-ipv6-address

Selects the preferred IPv6 source address (family inet6) associated with the loopback address used for the subscriber. You specify this variable at the [dynamic profiles profile-name interfaces demux0 unit "$junos-interface-unit" family inet6 unnumbered-address “$junos-loopback-interface”] hierarchy level for the preferred-source-address statement.

Note: Starting in Junos OS Release 16.1, when you specify a static logical interface for the unnumbered interface in a dynamic profile that includes the $junos-routing-instance predefined variable, you must not configure an IPv6 preferred source address. This constraint applies whether you use the $junos-preferred-source-ipv6-address predefined variable or the preferred-source-address statement. Configuring the preferred source address in this circumstance causes a commit failure.

$junos-subscriber-demux-ip-address

IP address of the subscriber. Use this variable instead of $junos-subscriber-ip-address when the IP demux subscribers require a framed route returned from the RADIUS server.

You specify this variable at the [dynamic-profiles profile-name interfaces demux0 unit family inet demux-source] hierarchy level.

$junos-subscriber-ip-address

IP address of the subscriber. You specify this variable at the [dynamic-profiles profile-name interfaces demux0 unit family inet demux-source] hierarchy level.

This variable is also used for creating access-internal routes.

$junos-subscriber-ipv6-address

IPv6 address for subscriber. You specify this variable at the [dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family inet6 demux-source] hierarchy level.

$junos-subscriber-ipv6-multi-address

Expands the demux-source into multiple addresses; for example, the IPv6 prefix and /128 address for the subscriber.

You specify this variable at the [dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family inet6 demux-source] hierarchy level.

$junos-underlying-interface

Creates a logical underlying interface for a dynamic IP demux interface. The client logs in on this interface. You specify this variable at the [dynamic profiles profile-name interfaces demux0 unit "$junos-interface-unit" demux-options] hierarchy level for the underlying-interface statement.

When configured, the underlying interface is used to determine the $junos-underlying-interface, $junos-underlying-interface-unit, and $junos-ifd-name variables. For example, if the receiving logical interface is ge-0/0/0.1, the $junos-underlying-interface variable is set to ge-0/0/0 and the $junos-underlying-interface-unit variable is set to 1.

This variable is also used for creating access-internal routes.

Subscriber Interfaces — Static VLAN Interfaces

$junos-interface-ifd-name

Name of the device to which the subscriber access client connects. All interfaces are created on this device. Its primary use is in creating single or multiple subscribers on a statically created interface. You specify this variable at the [dynamic-profiles profile-name interfaces] hierarchy level.

$junos-underlying-interface-unit

Obtains the unit number for the underlying interface. It specifies the use of the underlying interface for the subscriber. You specify this variable at the [dynamic-profiles profile-name interfaces $junos-interface-ifd-name] hierarchy level for the unit statement.

Subscriber Interfaces — Dynamic PPPoE Interfaces

$junos-interface-unit

Specifies the logical unit number when the router dynamically creates a PPPoE logical interface. The $junos-interface-unit predefined variable is dynamically replaced with the unit number supplied by the network when the PPPoE subscriber logs in. You specify this variable at the [edit dynamic-profiles profile-name interfaces pp0] hierarchy level for the unit statement.

$junos-underlying-interface

Specifies the name of the underlying Ethernet interface on which the router dynamically creates the PPPoE logical interface. The $junos-underlying-interface predefined variable is dynamically replaced with the name of the underlying interface supplied by the network when the PPPoE subscriber logs in. You specify this variable at the [edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit” pppoe-options] hierarchy level for the underlying-interface statement.

Subscriber Interfaces — Dynamic Interface Sets

$junos-interface-set-name

Name of an interface set configured in a dynamic profile. To represent the name of a dynamically created agent circuit identifier (ACI) interface set, use the $junos-interface-set-name predefined variable in the interface-set statement at the [edit dynamic-profiles profile-name interfaces] hierarchy level.

$junos-interface-set-target-weight

Weight for an interface set to associate it and its member links with an aggregated Ethernet member link for targeted distribution. The value is derived from RADIUS VSA 26-213 Interface-Set-Target-Weight. Also associated with Diameter AVP 213.

$junos-phy-ifd-interface-set-name

Name of an interface set associated with the underlying physical interface in a dynamic profile.

In a heterogeneous topology where residential and business subscribers share the same physical interface, although only two levels of CoS are required for residential access, business access requires three levels. Because they share the same physical interface, three levels are configured for both, causing an unnecessary level 2 node to be consumed for each residential connection.

Starting in Junos OS Release 16.1, you can reduce the CoS resources wasted on residential access by collecting the residential subscribers into an interface set associated with the physical interface. In this way, a level 2 node is used for the interface set rather than for each residential interface. To do so, specify the $junos-phy-ifd-interface-set-name predefined variable with the interface-set statement at the [edit dynamic-profiles profile-name interfaces] hierarchy level to create the interface set based on the underlying physical interface.

$junos-pon-id-interface-set-name

Locally generated interface set name used to associate individual customer circuits in a passive optical network (PON) to deliver CoS and other services to the set of interfaces.

The name is extracted from the DHCPv4 (Option 82, suboption 2) or DHCPv6 (Option 37) agent remote ID string inserted by an optical line terminal (OLT) in a PON. The OLT must format the agent remote ID string with a pipe symbol (|) as the delimiter between substrings. The substring extracted for the interface set name consists of the characters following the last delimiter in the agent remote ID string.

The extracted substring identifies individual customer circuits. You determine the format and contents of the substring, and configure your OLT to insert the information. Typically, the substring might include the name and port of the OLT accessed by the CPE optical network terminal (ONT).

$junos-svlan-interface-set-name

Locally generated interface set name for use by dual-tagged VLAN interfaces based on the outer tag of the dual-tagged VLAN. The format of the generated variable is physical_interface_name - outer_VLAN_tag.

Wholesale Networking

$junos-interface-name

Name of the dynamic interface to which the subscriber access client connects. Its use is in identifying the subscriber interface. You specify this variable at the [dynamic-profiles profile-name routing-instance $junos-routing-instance] hierarchy level for the interface statement.

The interface name is derived from concatenating the $junos-interface-ifd-name and the $junos-underlying-interface-unit variables obtained when a subscriber is created dynamically at the [dynamic-profiles profile-name routing-instance $junos-routing-instance interface] hierarchy level.

$junos-routing-instance

Name of the routing instance to which the subscriber is assigned. This variable triggers a return value from the RADIUS server for Virtual-Router (VSA 26-1).

You reference this variable in the statement at the [dynamic-profiles profile-name] hierarchy level for the routing-instance statement.

Note: Starting in Junos OS Release 16.1, when you specify a static logical interface for the unnumbered interface in a dynamic profile that includes the $junos-routing-instance predefined variable, you must not configure a preferred source address. This constraint applies whether you use the $junos-preferred-source-address predefined variable, the $junos-preferred-source-ipv6-address predefined variable, or the preferred-source-address statement. Configuring the preferred source address in this circumstance causes a commit failure.

$junos-inner-vlan-map-id

Starting in Junos OS Release 16.1R4, identifier for the inner VLAN tag for Layer 2 wholesale, ANCP-triggered, autosensed dynamic VLANs.The VLAN tag is allocated from the inner VLAN ID swap ranges that are provisioned on the core-facing physical interface. The inner VLAN tag is swapped with (replaces) the outer VLAN tag when the subscriber traffic is tunneled to the NSP.

You specify this variable with the inner-vlan-id statement at the [edit dynamic-profiles profile-name interfaces $junos-interface-ifd–name unit $junos-interface-unit input-vlan-map] hierarchy level.

$junos-vlan-map-id

Identifier for a VLAN that is rewritten at the input or output interface as specified by a VLAN map.

You specify this variable with the vlan-id statement at the [edit dynamic-profiles profile-name interfaces $junos-interface-ifd–name unit $junos-interface-unit input-vlan-map] or [edit dynamic-profiles profile-name interfaces $junos-interface-ifd–name unit $junos-interface-unit input-vlan-map] hierarchy levels.

Junos OS Predefined Variables That Correspond to RADIUS Attributes and VSAs

Table 2 lists the RADIUS attributes and Juniper Networks VSAs and their corresponding Junos OS predefined variables that are used in dynamic profiles. When the router instantiates a dynamic profile following subscriber access, the Junos OS uses the predefined variable to specify the RADIUS attribute or VSA for the information obtained from the RADIUS server.

Some predefined variables support the configuration of default values. The configured default value is used in the event that RADIUS fails to return a value for the variable. You configure default values with the predefined-variable-defaults predefined-variable default-value statement at the [edit dynamic-profiles] hierarchy level. When you specify the predefined-variable, you use the name of the Junos OS predefined variable, but you omit the leading $junos- prefix.

Table 2: RADIUS Attributes and Corresponding Junos OS Predefined Variables

Attribute Number and Name

Junos OS Predefined Variable

Description

Default Value Support for Junos OS Predefined Variable

RADIUS Standard Attributes

8

Framed-IP-Address

$junos-framed-route-ip-address

Address for the client

No

11

Filter-ID

$junos-input-filter

Note: Variable is also used for VSA 26-10.

Input filter to apply to client IPv4 interface

Yes

12

Framed-MTU

$junos-interface-mtu

Maximum size of the packet; maximum transmission unit

Yes

22

Framed-Route

$junos-framed-route-ip-address-prefix

(Subattribute 1): Route prefix for access route

No

 

$junos-framed-route-nexthop

(Subattribute 2): Next hop address for access route

No

 

$junos-framed-route-cost

(Subattribute 3): Metric for access route

No

 

$junos-framed-route-distance

(Subattribute 5): Preference for access route

No

 

$junos-framed-route-tag

(Subattribute 6): Tag for access route

No

97

Framed-IPv6-Prefix

$junos-ipv6-ndra-prefix

Prefix value in IPv6 Neighbor Discovery route advertisements

No

99

Framed-IPv6-Route

$junos-framed-route-ipv6-address-prefix

(Subattribute 1): Framed IPv6 route prefix configured for the client

No

 

$junos-framed-route-ipv6-cost

(Subattribute 3): Metric for access route

No

 

$junos-framed-route-ipv6-distance

(Subattribute 5): Preference for access route

No

 

$junos-framed-route-ipv6-nexthop

(Subattribute 2): IPv6 routing information configured for the client

No

 

$junos-framed-route-ipv6-tag

(Subattribute 6): Tag for access route

No

Juniper Networks VSA

26-1

Virtual-Router

$junos-routing-instance

Routing instance to which subscriber is assigned

Yes

26-10

Ingress-Policy-Name

$junos-input-filter

Note: Variable is also used for RADIUS attribute 11.

Input filter to apply to client IPv4 interface

Yes

26-11

Egress-Policy-Name

$junos-output-filter

Output filter to apply to client IPv4 interface

Yes

26-23

IGMP-Enable

$junos-igmp-enable

Enable or disable IGMP on client interface

Yes

26-71

IGMP-Access-Name

$junos-igmp-access-group-name

Access list to use for the group (G) filter

Yes

26-72

IGMP-Access-Src-Name

$junos-igmp-access-source-group-name

Access List to use for the source group (S,G) filter

Yes

26-74

MLD-Access-Name

$junos-mld-access-group-name

Access list to use for the group (G) filter

Yes

26-75

MLD-Access-Src-Name

$junos-mld-access-source-group-name

Access List to use for the source group (S,G) filter

Yes

26-77

MLD-Version

$junos-mld-version

MLD protocol version

Yes

26-78

IGMP-Version

$junos-igmp-version

IGMP protocol version

Yes

26-97

IGMP-Immediate-Leave

$junos-igmp-immediate-leave

IGMP immediate leave

Yes

26-100

MLD-Immediate-Leave

$junos-mld-immediate-leave

MLD immediate leave

Yes

26-106

IPv6-Ingress-Policy-Name

$junos-input-ipv6-filter

Input filter to apply to client IPv6 interface

Yes

26-107

IPv6-Egress-Policy-Name

$junos-output-ipv6-filter

Output filter to apply to client IPv6 interface

Yes

26-108

CoS-Parameter-Type

$junos-cos-scheduler-map

(T01: Scheduler-map name) Name of scheduler map configured in traffic-control profile

Yes

 

$junos-cos-shaping-rate

(T02: Shaping rate) Shaping rate configured in traffic-control profile

Yes

 

$junos-cos-guaranteed-rate

(T03: Guaranteed rate) Guaranteed rate configured in traffic-control profile

Yes

 

$junos-cos-delay-buffer-rate

(T04: Delay-buffer rate) Delay-buffer rate configured in traffic-control profile

Yes

 

$junos-cos-excess-rate

(T05; Excess rate) Excess rate configured in traffic-control profile

Yes

 

$junos-cos-traffic-control-profile

(T06: Traffic-control profile) Name of the traffic-control profile configured in a dynamic profile

Yes

 

$junos-cos-shaping-mode

(T07; Shaping mode) CoS shaping mode configured in a dynamic profile

Yes

 

$junos-cos-byte-adjust

(T08; Byte adjust) Byte adjustments configured for the shaping mode in a dynamic profile

Yes

 

$junos-cos-adjust-minimum

(T09; Adjust minimum) Minimum adjusted value allowed for the shaping rate in a dynamic profile

Yes

 

$junos-cos-excess-rate-high

(T10; Excess rate high) Excess rate configured for high-priority traffic in a dynamic profile

Yes

 

$junos-cos-excess-rate-low

(T11; Excess rate low) Excess rate configured for low-priority traffic in a dynamic profile

Yes

 

$junos-cos-shaping-rate-burst

(T12; Shaping rate burst) Burst size configured for the shaping rate in a dynamic profile

Yes

 

$junos-cos-guaranteed-rate-burst

(T13; Guaranteed rate burst) Burst size configured for the guaranteed rate in a dynamic profile

Yes

26-130

Qos-Set-Name

$junos-interface-set-name

Name of an interface set configured in a dynamic profile

Yes

26-146

CoS-Scheduler-Pmt-Type

$junos-cos-scheduler

(Null: Scheduler name) Name of scheduler configured in a dynamic profile

Yes

 

$junos-cos-scheduler-tx

(T01: CoS scheduler transmit rate) Transmit rate for scheduler configured in a dynamic profile

Yes

Available for multiple parameters:

  • Percent

  • Rate

 

$junos-cos-scheduler-bs

(T02: CoS scheduler buffer size) Buffer size for scheduler configured in a dynamic profile

Yes

Available for multiple parameters:

  • Percent

  • Temporal

 

$junos-cos-scheduler-pri

(T03: CoS scheduler priority) Packet-scheduling priority for scheduler configured in a dynamic profile

Yes

 

$junos-cos-scheduler-dropfile-low

(T04: CoS scheduler drop-profile low) Name of drop profile for RED loss-priority level low for scheduler configured in a dynamic profile

Yes

 

$junos-cos-scheduler-dropfile-medium-low

(T05: CoS scheduler drop-profile medium-low) Name of drop profile for RED loss-priority level medium-low for scheduler configured in a dynamic profile

Yes

 

$junos-cos-scheduler-dropfile-medium-high

(T06: CoS scheduler drop-profile medium-high) Name of drop profile for RED loss-priority level medium-high for scheduler configured in a dynamic profile

Yes

 

$junos-cos-scheduler-dropfile-high

(T07: CoS scheduler drop-profile high) Name of drop profile for RED loss-priority level high for scheduler configured in a dynamic profile

Yes

 

$junos-cos-scheduler-dropfile-any

(T08: CoS scheduler drop-profile any) Name of drop profile for RED loss-priority level any for scheduler configured in a dynamic profile

Yes

 

$junos-cos-scheduler-excess-rate

(T09: CoS scheduler excess rate) Excess rate configured for a scheduler in a dynamic profile

Yes

Available for multiple parameters:

  • Percent

  • Proportion

 

$junos-cos-scheduler-shaping-rate

(T10: CoS scheduler shaping rate) Shaping rate configured for a scheduler in a dynamic profile

Yes

Available for multiple parameters:

  • Percent

  • Rate

 

$junos-cos-scheduler-excess-priority

(T11: CoS scheduler excess priority) Excess priority configured for a scheduler in a dynamic profile

Yes

26-191

Input-Interface-Filter

$junos-input-interface-filter

Name of an input filter to be attached to a family any interface.

No

26-192

Output-Interface-Filter

$junos-output-interface-filter

Name of an output filter to be attached to a family any interface.

No

26-196

IPv4-Input-Service-Set

$junos-input-service-set

Name of an IPv4 input service set to be attached.

No

26-197

IPv4-Output-Service-Set

$junos-output-service-set

Name of an IPv4 output service set to be attached.

No

26-198

IPv4-Input-Service-Filter

$junos-input-service-filter

Name of an IPv4 input service filter to be attached.

No

26-199

IPv4-Output-Service-Filter

$junos-output-service-filter

Name of an IPv4 output service filter to be attached.

No

26-200

IPv6-Input-Service-Set

$junos-input-ipv6-service-set

Name of an IPv6 input service set to be attached.

No

26-201

IPv6-Output-Service-Set

$junos-output-ipv6-service-set

Name of an IPv6 output service set to be attached.

No

26-202

IPv6-Input-Service-Filter

$junos-input-ipv6-service-filter

Name of an IPv6 input service filter to be attached.

No

26-203

IPv6-Output-Service-Filter

$junos-output-ipv6-service-filter

Name of an IPv6 output service filter to be attached.

No

26-204

Adv-Pcef-Profile-Name

$junos-pcef-profile

Name of a PCEF profile to be attached.

No

26-205

Adv-Pcef-Rule-Name

$junos-pcef-rule

Name of a PCC rule to activate.

No

26-211

$junos-inner-vlan-tag-protocol-id

Name of VLAN map to activate

Yes

26-212

$junos-routing-services

Enables or disables routing services capability. If you enable this variable in your configuration and RADIUS does not return the VSA, then routing services are disabled for the subscriber.

No

26-213

$junos-interface-set-target-weight

Specify a weight for an interface set to associate it and its member links with an aggregated Ethernet member link for targeted distribution.

Yes

26-214

$junos-interface-target-weight

Specify a weight for an interface to associate it with an interface set and thus with the set’s aggregated Ethernet member link for targeted distribution. When an interface set does not have a weight, then the interface weight value for the first authorized subscriber interface is used for the set.

Yes

Predefined Variable Defaults for Dynamic Client Profiles

You can optionally configure default values for many predefined variables. The Junos OS uses the default value in the following cases:

  • When the external RADIUS server is not available

  • When the VSA returned by the RADIUS server does not contain a value for the predefined variable

The RADIUS value for a predefined variable takes precedence over the default value. For example, if you have configured a default for a predefined variable, but RADIUS also returns a value, the system uses the value from RADIUS instead.

The default value must be appropriate to the variable, such as an integer or an alphanumeric string. Starting in Junos OS Release 19.3R1, you can also configure the default value of a predefined variable to be another predefined variable by using a variable expression. In earlier releases, the default value must be fixed; it cannot be a variable.

Note

Expressions are typically configured for user-defined variables and dynamic service profiles. See Using Variable Expressions in User-Defined Variables for more information.

When you use a variable expression, you are setting up a condition that determines the default value of the predefined variable. The value of the default is different when the condition is matched than when it is not matched. In dynamic client profiles, you can configure any of the following operators for variable expressions:

  • equals—Assigns a predefined variable as the default value.

  • ifNotZero(parameter-1, parameter-2)—Sets a condition to be matched. Assigns the value from parameter-2 as the default value only when parameter-1 is nonzero, meaning that the parameter resolved to some value.

  • ifZero(parameter-1, parameter-2)—Sets a condition to be matched. Assigns the value from parameter-2 as the default value only when parameter-1 is zero, meaning that the parameter did not resolve to any value. If parameter-1 did resolve to a value (therefore it is not zero), then the value from parameter-1 is assigned as the default.

You can also nest expressions, which provides additional conditions for setting the variable value. For example, a dynamic profile for a subscriber in a heterogeneous network might have the following configuration for the predefined-variable-defaults statement:

See Dynamic Level 2 and Level 3 Interface Set Naming with Predefined Variables for a detailed explanation of how to evaluate these expressions in the context of a heterogeneous network.

Configuring Predefined Dynamic Variables in Dynamic Profiles

This topic discusses how to configure predefined variables in a dynamic profile. The dynamic profile obtains and replaces data for these variables from an incoming client data packet. You can specify these variables in the body of a dynamic profile without having to first define the variables at the [edit dynamic-profiles profile-name variables] hierarchy level.

Before you configure dynamic variables:

  1. Create a basic dynamic profile.

    See Configuring a Basic Dynamic Profile.

  2. Ensure that the router hardware is configured in the network to accept subscriber access.

To configure predefined variables in a dynamic profile:

  1. Access the desired dynamic profile.
  2. Configure the necessary variables (in this example, for a protocol interface).

    For example, the following simple configuration uses a predefined variable to dynamically create the interface accessed by the IGMP client, enabling IGMP on the subscriber interface:

    For a complete list of supported predefined variables, see Junos OS Predefined Variables.

Configuring Default Values for Predefined Variables in a Dynamic Profile

For any Junos OS predefined variable that can be sourced from RADIUS, you can specify a default value in a dynamic client profile. These default values are used when RADIUS does not supply a value.

Defining default values for these predefined variables enables you to determine whether to source values locally from the profile instead of only from RADIUS. This enables you to use RADIUS as a way to selectively override predefined variable values, instead of being the sole source of those values.

For a list of predefined variables and options for which you can configure default values, see Junos OS Predefined Variables That Correspond to RADIUS Attributes and VSAs.

To configure default values for Junos predefined variables:

  1. Specify that you want to configure the dynamic client profile.
  2. Configure the default value for a predefined variable or for a specific option within a predefined variable.
    Note

    When you specify the predefined-variable, you use the name of the Junos OS predefined variable, but you omit the leading $junos- prefix.

For example, consider the behavior when you have the following configuration to specify a default value for the $junos-routing-instance predefined variable:

  • When RADIUS does not return a routing instance, the subscribers come up in the RI-def routing instance.

  • When RADIUS returns routing-instance RI-res, the subscribers come up in the RI-res routing instance.

When you do not configure a default value for the $junos-routing-instance predefined variable and RADIUS does not return a value, the subscribers come up in the master routing instance, which is the Junos OS default.

Release History Table
Release
Description
Starting in Junos OS Release 19.3R1, you can also configure the default value of a predefined variable to be another predefined variable by using a variable expression.
Starting in Junos OS Release 17.2R1, name of an IPv6 input service filter to be attached.
Starting in Junos OS Release 17.2R1, name of an IPv6 service set to be attached.
Starting in Junos OS Release 17.2R1, name of an IPv4 input service filter to be attached.
Starting in Junos OS Release 17.2R1, name of an IPv4 input service set to be attached.
Starting in Junos OS Release 17.2R1, name of an IPv6 service filter to be attached.
Starting in Junos OS Release 17.2R1, name of an IPv6 service set to be attached.
Starting in Junos OS Release 17.2R1, name of an IPv4 service filter to be attached.
Starting in Junos OS Release 17.2R1, name of an IPv4 output service set to be attached.
Starting in Junos OS Release 17.2R1, name of a PCEF profile to be attached.
Starting in Junos OS Release 17.2R1, name of a PCC rule to activate.
Starting in Junos OS Release 16.1R4, identifier for the inner VLAN tag for Layer 2 wholesale, ANCP-triggered, autosensed dynamic VLANs.
Starting in Junos OS Release 16.1, when you specify a static logical interface for the unnumbered interface in a dynamic profile that includes the $junos-routing-instance predefined variable, you must not configure an IPv4 preferred source address.
Starting in Junos OS Release 16.1, when you specify a static logical interface for the unnumbered interface in a dynamic profile that includes the $junos-routing-instance predefined variable, you must not configure an IPv6 preferred source address.
Starting in Junos OS Release 16.1, you can reduce the CoS resources wasted on residential access by collecting the residential subscribers into an interface set associated with the physical interface.
Starting in Junos OS Release 16.1, when you specify a static logical interface for the unnumbered interface in a dynamic profile that includes the $junos-routing-instance predefined variable, you must not configure a preferred source address.