Cisco Catalyst 3560-X Series, Software Configuration Manual

Page: 258 / 1538

1-26
Catalyst 3750-X and 3560-X Switch Software Configuration Guide
OL-25303-03
Chapter 1 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
If the stack master fails before the port-bounce completes, a port-bounce is initiated after stack master
change-over based on the original command (which is subsequently removed).
If the stack master fails before sending a CoA-ACK message, the new stack master treats the re-sent
command as a new command.
Stacking Guidelines for CoA-Request Disable-Port
Because the disable-port command is targeted at a session, not a port, if the session is not found, the
command cannot be executed.
When the Auth Manager command handler on the stack master receives a valid disable-port command,
it verifies this information before returning a CoA-ACK message:
•
the need for a port-disable
•
the port-id (found in the local session context)
The switch attempts to disable the port.
If the port-disable operation is successful, the signal that triggered the port-disable is removed from the
standby stack master.
If the stack master fails before the port-disable operation completes, the port is disabled after stack
master change-over based on the original command (which is subsequently removed).
If the stack master fails before sending a CoA-ACK message, the new stack master treats the re-sent
command as a new command.
Configuring RADIUS
This section describes how to configure your switch to support RADIUS. At a minimum, you must
identify the host or hosts that run the RADIUS server software and define the method lists for RADIUS
authentication. You can optionally define method lists for RADIUS authorization and accounting.
A method list defines the sequence and methods to be used to authenticate, to authorize, or to keep
accounts on a user. You can use method lists to designate one or more security protocols to be used (such
as or local username lookup), thus ensuring a backup system if the initial method fails. The
software uses the first method listed to authenticate, to authorize, or to keep accounts on users; if that
method does not respond, the software selects the next method in the list. This process continues until
there is successful communication with a listed method or the method list is exhausted.
You should have access to and should configure a RADIUS server before configuring RADIUS features
on your switch.
These sections contain this configuration information:
•
Default RADIUS Configuration, page 1-27
•
Identifying the RADIUS Server Host, page 1-27 (required)
•
Configuring RADIUS Login Authentication, page 1-29 (required)
•
Defining AAA Server Groups, page 1-31 (optional)
• Configuring RADIUS Authorization for User Privileged Access and Network Services, page 1-33
(optional)
•
Starting RADIUS Accounting, page 1-34 (optional)
•
Configuring Settings for All RADIUS Servers, page 1-35 (optional)
•
Configuring the Switch to Use Vendor-Specific RADIUS Attributes, page 1-35 (optional)