Predefined Variables in Dynamic Profiles

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.

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.

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.

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]

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]

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]

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]

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]

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.

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.

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.

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.

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.

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.

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.

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

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

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.

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.

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.

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.

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.

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

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

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.

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.

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.

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.

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.

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

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Name of the action profile configured in a dynamic profile.

Continuity check interval time configured in a dynamic profile.

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

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

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

Name of the maintenance association configured in a dynamic profile.

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

Name of the maintenance domain configured in a dynamic profile.

The ’MEP’ value configured in the dynamic profile.

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

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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).

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.

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.

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.

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.

No

Yes

No

No

No

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

No

No

No

No

No

No

No

No

No

No

No

No

Yes

No

Yes

Yes