L2TP Access Concentrator
Configuring Subscriber Profiles for L2TP Support ▀
Cisco ASR 5x00 Packet Data Network Gateway Administration Guide ▄
399
RADIUS
Attribute
Local
Subscriber
Attribute
Description
Variable
Tunnel-
Preference
tunnel l2tp
preference
Configures the priority of each peer LNS when
multiple LNS nodes are configured.
Important:
This attribute is
only used when the
loadbalance-
tunnel-peers
parameter or
SN-Tunnel-
Load-Balancing
attribute configured
to prioritized.
Integer from 1 to 65535
SN-Tunnel-
Load-
Balancing
loadbalance-
tunnel- peer
A vendor-specific attribute (VSA) used to
provides a selection algorithm defining how an
LNS node is selected by the RADIUS server
when multiple LNS peers are configured within
the subscriber profile.
Random
- Random LNS selection
order, the
Tunnel-Preference
attribute is not used in determining
which LNS to select.
Balanced
- LNS selection is
sequential balancing the load across
all configured LNS nodes, the
Tunnel-Preference
attribute is not
used in determining which LNS to
select.
Prioritized
- LNS selection is
made based on the priority assigned
in the
Tunnel-Preference
attribute.
Client-
Endpoint
local-address
Specifies the IP address of a specific LAC service
configured on the system that to use to facilitate
the subscriber’s L2TP session.
This attribute is used when multiple LAC services
are configured.
IPv4 address in dotted decimal notation.
(xxx.xxx.xxx.xxx)
RADIUS Tagging Support
The system supports RADIUS attribute tagging for tunnel attributes. These “tags” organize together multiple attributes
into different groups when multiple LNS nodes are defined in the user profile. Tagging is useful to ensure that the
system groups all the attributes used for a specific server. If attribute tagging is not supported by your specific RADIUS
server, the system implicitly organizes the attributes in the order that they are listed in the access accept packet.
Configuring Local Subscriber Profiles for L2TP Support
This section provides information and instructions for configuring local subscriber profiles on the system to support
L2TP.