Table of Contents
Advertisement
JUNOS OS 10.4 Release Notes
26
You can include the
fail-over-within-preference
hierarchy level to configure tunnel selection failover within a preference level. With this
method, when the router tries to connect to a destination and is unsuccessful, it selects
a new destination at the same preference level. If all destinations at a preference level
are marked as unreachable, the router does not attempt to connect to a destination
at that level. It drops to the next lower preference level to select a destination. If all
destinations at all preference levels are marked as unreachable, the router chooses
the destination that failed first and tries to make a connection. If the connection fails,
the router rejects the PPP user session without attempting to contact the remote
router.
By default, the router uses a round-robin selection process among tunnels at the same
preference level. Include the
the
[edit services l2tp]
hierarchy level to specify that the tunnel with the highest weight
within a preference is selected until its maximum sessions limit is reached. Then the
tunnel with the next highest weight is selected until its limit is reached, and so on. The
tunnel with the highest configured maximum sessions value has the greatest weight.
Another feature of L2TP LACs on MX Series routers is the ability to control whether
the LAC sends the Calling Number AVP 22 to the LNS. The AVP value is derived from
the Calling-Station-Id and identifies the interface that is connected to the customer
in the access network. By default, the LAC includes this AVP in ICRQ packets it sends
to the LNS. In some networks you may wish to conceal your network access information.
To prevent the LAC from sending the Calling Number AVP to the LNS, include the
disable-calling-number-avp
[Subscriber Access]
Support for dynamic interface sets (M120, M320, and MX Series routers)—Enables
you to configure sets of subscriber interfaces in dynamic profiles. Interface sets are
used for providing hierarchical scheduling. Previously, interface sets were supported
for interfaces configured in the static hierarchies only.
Supported subscriber interfaces include static and dynamic demux, static and dynamic
PPPoE, and static and dynamic VLAN interfaces.
To configure an interface set in a dynamic profile, include the
interface-set-name
statement at the
To add a subscriber interface to the set, include the
statement at the
logical-unit-number
interface-set-name]
hierarchy level. You apply traffic shaping and scheduling parameters
to the interface-set by including the
output-traffic-control-profile profile-name
hierarchy level.
interfaces]
A new Juniper Networks VSA (attribute 26-130) is now supported for the interface set
name, and includes a predefined variable,
supported for RADIUS Access-Accept messages only; change of authorization (CoA)
requests are not supported.
[Subscriber Access]
statement at the
weighted-load-balancing
statement at the
[edit services l2tp]
[edit dynamic-profiles interfaces]
interface interface-name unit
[edit dynamic-profiles interfaces interface-set
interface-set interface-set-name
statements at the static
$junos-interface-set-name
Copyright © 2011, Juniper Networks, Inc.
[edit services l2tp]
statement at the statement at
hierarchy level.
interface-set
hierarchy level.
and
[edit class-of-service
. The VSA is
Advertisement
Table of Contents
