• the need for a port-bounce • the port-id (found in the local session context) The switch initiates a port-bounce (disables the port for 10 seconds, then re-enables it). If the port-bounce is successful, the signal that triggered the port-bounce is removed from the standby switch. If the active switch fails before the port-bounce completes, a port-bounce is initiated after active switch changeover based on the original command (which is subsequently removed). If the active switch fails before sending a CoA-ACK message, the new active switch 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 active switch 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 switch.
If the active switch fails before the port-disable operation completes, the port is disabled after active switch changeover based on the original command (which is subsequently removed). If the active switch fails before sending a CoA-ACK message, the new active switch treats the re-sent command as a new command. Default RADIUS Configuration RADIUS and AAA are disabled by default. To prevent a lapse in security, you cannot configure RADIUS through a network management application. When enabled, RADIUS can authenticate users accessing the device through the CLI. RADIUS Server Host Device-to-RADIUS-server communication involves several components:
• Hostname or IP address • Authentication destination port • Accounting destination port • Key string • Timeout period Configuring RADIUS Stacking Guidelines for CoA-Request Disable-Port Configuring RADIUS 11