For example, an ERX1440 Broadband Services Router has tunnel-service modules
installed in slots 4, 9, and 12. Using the load-balancing mechanism, the router
determines that the SM in slot 4 can accommodate the first bundled session for
MLPPP bundle A, and places it there. The first bundled session for bundle A has an
endpoint discriminator of 5. The router subsequently places all bundled sessions for
bundle A (which have an endpoint discriminator of 5) on the SM in slot 4.
When the SM on which the bundled sessions reside has no more space for additional
sessions, the router refuses the L2TP session. This can happen even when other
tunnel-service modules installed in the router have available space.
For more information about endpoint discriminators, see the
Configuring Multilink
PPP
chapter in
JUNOSe Link Layer Configuration Guide
.
Assigning Bundled Group Identifiers
In some cases, an endpoint discriminator is not available for the LNS to use to identify
the links in a bundled session.
This situation might occur when:
■
PPP clients provide endpoint discriminators with null values.
■
PPP clients do not provide an endpoint discriminator option when negotiating
LCP with the LAC.
■
The LAC does not include a endpoint discriminator option in the LCP proxy AVPs.
The router places all bundled sessions without endpoint discriminators on the same
SM. However, if there are many such bundled sessions, the load-balanced distribution
of LNS sessions across the tunnel-service modules can deteriorate because the router
places all bundled sessions on the same SM without evenly distributing the load.
The
bundled-group-id
command enables you to correct this situation by assigning
a numeric bundled group identifier for the router to use when the endpoint
discriminator is unavailable to identify the bundled membership. The router places
bundled sessions with the same bundled group identifier on the same SM in the same
way that it does with endpoint discriminators.
The bundled group identifier applies to the entire router; therefore, if you assign the
same bundled group identifier for different L2TP destination host profiles, the router
places all of the bundled sessions with the same bundled group identifier on the
same SM.
NOTE:
We recommend that you assign bundled group identifiers only when you are
certain that endpoint discriminators are unavailable to identify bundle membership.
■
To assign a numeric bundled group identifier:
host1:boston(config-l2tp-dest-profile-host)#
bundled-group-id 4
Selecting Tunnel-Service Modules for LNS Sessions Using MLPPP
■
377
Chapter 13: Configuring an L2TP LNS
Summary of Contents for JUNOSE 11.0.X MULTICAST ROUTING
Page 6: ...vi...
Page 28: ...xxviii Table of Contents JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 36: ...xxxvi List of Tables JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 42: ...2 Managing Remote Access JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 204: ...164 Managing RADIUS and TACACS JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 292: ...252 Monitoring RADIUS Relay Server JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 336: ...296 RADIUS Client Terminate Reasons JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 368: ...328 Managing L2TP JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 444: ...404 PPP Accounting Statistics JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 494: ...454 Managing DHCP JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 510: ...470 DHCP Local Server Configuration Tasks JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 556: ...516 Configuring DHCP Relay Proxy JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 616: ...576 Managing the Subscriber Environment JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 674: ...634 Managing Subscriber Services JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 767: ...Part 7 Index Index on page 729 Index 727...
Page 768: ...728 Index JUNOSe 11 0 x Broadband Access Configuration Guide...