
2.
Set the format of the RADIUS Calling-Station-Id to
fixed-format
, and specify the
optional
stacked
keyword to include the S-VLAN ID.
host1(config)#
radius calling-station-format fixed-format stacked
If you use a RADIUS server to authenticate the L2TP tunnel parameters, you must
configure the format for both the L2TP Calling Number AVP 22 (by using the
aaa
tunnel calling-number-format
command) and the RADIUS Calling-Station-ID [31]
attribute (by using the
radius calling-station-format
command).
However, if you use an AAA domain map to authenticate the L2TP tunnel parameters,
you need configure only the L2TP Calling Number AVP 22 format by using the
aaa
tunnel calling-number-format
command. You need not configure the format of the
RADIUS Calling-Station-ID [31] attribute in this case.
Configuring the Fallback Format
You can configure a fallback AVP 22 format. The E Series LAC uses the fallback format
to generate the L2TP Calling Number AVP 22 in the event that the PPPoE agent ID
is null or unavailable. The LAC uses the fallback format only when the configured
calling number format includes either or both of the agent-circuit-id and
agent-remote-id suboptions.
The calling number format determines what element triggers use of the fallback
format, as shown in the following table:
Fallback Trigger
Calling Number Format
agent-circuit-id is empty
agent-circuit-id
Both agent-circuit-id and
agent-remote-id are empty.
agent-circuit-id include-agent-remote-id
agent-remote-id is empty
agent-remote-id
agent-circuit-id is empty
descriptive include-agent-circuit-id
Both agent-circuit-id and
agent-remote-id are empty.
descriptive include-agent-circuit-id
include-agent-remote-id
agent-remote-id is empty
descriptive include-agent-remote-id
You use the
aaa tunnel calling-number-format-fallback
command to configure the
router to generate any of the following fallback AVP 22 formats:
■
descriptive—This is the default fallback AVP 22 format, and includes the following
elements:
<interface ID> <delimit> <UID> <delimit> <interface description>
<delimit> <connect info> <delimit> <PPPoE description>
■
fixed—This format is similar to the fixed format of RADIUS attribute 31
(Calling-Station-Id). If you set up the router to generate the fallback AVP 22 in
354
■
Configuring the Fallback Format
JUNOSe 11.1.x Broadband Access Configuration Guide
Summary of Contents for JUNOSE 11.1.X - BROADBAND ACCESS CONFIGURATION GUIDE 6-4-2010
Page 6: ...vi...
Page 28: ...xxviii Table of Contents JUNOSe 11 1 x Broadband Access Configuration Guide...
Page 36: ...xxxvi List of Tables JUNOSe 11 1 x Broadband Access Configuration Guide...
Page 42: ...2 Managing Remote Access JUNOSe 11 1 x Broadband Access Configuration Guide...
Page 210: ...170 Managing RADIUS and TACACS JUNOSe 11 1 x Broadband Access Configuration Guide...
Page 298: ...258 Monitoring RADIUS Relay Server JUNOSe 11 1 x Broadband Access Configuration Guide...
Page 342: ...302 RADIUS Client Terminate Reasons JUNOSe 11 1 x Broadband Access Configuration Guide...
Page 374: ...334 Managing L2TP JUNOSe 11 1 x Broadband Access Configuration Guide...
Page 450: ...410 PPP Accounting Statistics JUNOSe 11 1 x Broadband Access Configuration Guide...
Page 500: ...460 Managing DHCP JUNOSe 11 1 x Broadband Access Configuration Guide...
Page 516: ...476 DHCP Local Server Configuration Tasks JUNOSe 11 1 x Broadband Access Configuration Guide...
Page 562: ...522 Configuring DHCP Relay Proxy JUNOSe 11 1 x Broadband Access Configuration Guide...
Page 622: ...582 Managing the Subscriber Environment JUNOSe 11 1 x Broadband Access Configuration Guide...
Page 680: ...640 Managing Subscriber Services JUNOSe 11 1 x Broadband Access Configuration Guide...
Page 773: ...Part 7 Index Index on page 735 Index 733...
Page 774: ...734 Index JUNOSe 11 1 x Broadband Access Configuration Guide...