Juniper JUNOSE 11.0.X MULTICAST ROUTING, Configuration Manual

Page: 276 / 788

For example, you might use the RADIUS dynamic-request server to terminate specific
user sessions. Without the RADIUS dynamic-request server, the only way to disconnect
a RADIUS user is from the E Series router. This disconnect method is cumbersome
when a network has many systems. The RADIUS dynamic-request server allows
RADIUS servers to initiate user-related operations, such as a termination operation,
by sending unsolicited request messages to an E Series router.
Figure 5 on page 236 shows a network that would benefit from the RADIUS
dynamic-request server functionality. In Figure 5 on page 236, instead of disconnecting
users on each E Series router, the RADIUS servers can initiate the disconnection.
Although the network has multiple RADIUS servers, the servers share a common
database that contains authorization and accounting information. Having a common
database allows any server to view who is currently valid and connected, and allows
service providers to manage the disconnection of users.
Figure 5: Sample Remote Access Network Using RADIUS
RADIUS Dynamic-Request Server Platform Considerations
RADIUS dynamic-request server is supported on all E Series routers. For information
about the modules supported on E Series routers:
■
See the ERX Module Guide for modules supported on ERX7xx models, ERX14xx
models, and the ERX310 Broadband Services Router.
■
See the E120 and E320 Module Guide for modules supported on the E120 and
E320 Broadband Services Routers.
RADIUS Dynamic-Request Server References
For more information about the RADIUS dynamic-request server feature, see the
following references:
■
RFC 2865—Remote Authentication Dial In User Service (RADIUS) (June 2000)
■
RFC 2866—RADIUS Accounting (June 2000)
236 ■
RADIUS Dynamic-Request Server Platform Considerations
JUNOSe 11.0.x Broadband Access Configuration Guide