Cisco Catalyst 3130, Руководство по настройке программного обеспечения

Страница: 208 / 1354

7-20
Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide
OL-12247-04
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
RADIUS Change of Authorization
This section provides an overview of the RADIUS interface including available primitives and how they
are used during a Change of Authorization (CoA).
•
Overview, page 7-20
• Change-of-Authorization Requests, page 7-20
•
CoA Request Response Code, page 7-22
• CoA Request Commands, page 7-23
•
Session Reauthentication, page 7-23
• Stacking Guidelines for Session Termination, page 7-25
Overview
A standard RADIUS interface is typically used in a pulled model where the request originates from a
network attached device and the response come from the queried servers. Catalyst switches support the
RADIUS Change of Authorization (CoA) extensions defined in RFC 5176 that are typically used in a
pushed model and allow for the dynamic reconfiguring of sessions from external authentication,
authorization, and accounting (AAA) or policy servers.
Beginning with Cisco IOS Release 12.2(52)SE, the switch supports these per-session CoA requests:
•
Session reauthentication
• Session termination
•
Session termination with port shutdown
•
Session termination with port bounce
The RADIUS interface is enabled by default on Catalyst switches. However, some basic configuration
is required for the following attributes:
•
Security and Password—refer to the “Preventing Unauthorized Access to Your Switch” section in
the Configuring Switch-Based Authentication chapter in the Catalyst 3750 Switch Software
Configuration Guide, 12.2(50)SE .
•
Accounting—refer to the “Starting RADIUS Accounting” section in the Configuring Switch-Based
Authentication chapter in the Catalyst 3750 Switch Software Configuration Guide, 12.2(50)SE .
Change-of-Authorization Requests
Change of Authorization (CoA) requests, as described in RFC 5176, are used in a push model to allow
for session identification, host reauthentication, and session termination. The model is comprised of one
request (CoA-Request) and two possible response codes:
• CoA acknowledgement (ACK) [CoA-ACK]
•
CoA non-acknowledgement (NAK) [CoA-NAK]
The request is initiated from a CoA client (typically a RADIUS or policy server) and directed to the
switch that acts as a listener.