Brocade Network OS NETCONF Operations Guide v4.1.1 - Manual (Page 234)

202 Network OS NETCONF Operations Guide
53-1003231-02
RADIUS
16
radius
local
4. Log in to the switch using an account with TACACS+ credentials. The login should fail with an
“access denied” error.
5. Log in to the switch using an account with RADIUS credentials. The login should succeed.
RADIUS
The RADIUS protocol manages authentication, authorization, and accounting (AAA) services
centrally. The supported management access channels that integrate with RADIUS are serial port,
Telnet, and SSH.
This section provides procedures and examples for client side configuration with RADIUS servers
using the NETCONF interface. Refer to the Network OS Administrator’s Guide for the following
related information:
• An overview of authentication, accounting, and authorization with RADIUS servers
• Server-side RADIUS configuration
Each Brocade switch client must be individually configured to use RADIUS servers. You use the
NETCONF interface to specify the server IP address, authentication protocols, and other
parameters. You can configure a maximum of five RADIUS servers on a Brocade switch for AAA
service.
The parameters in Table 9 are associated with a RADIUS server that is configured on the switch.
TABLE 9 RADIUS server parameters
Parameter Description
hostname IP address (IPv4 or IPv6) or host name of the RADIUS server. Host name requires
prior DNS configuration.
auth-port The User Datagram Protocol (UDP) port used to connect the RADIUS server for
authentication. The port range is 0 through 65535. The default port is 1812.
protocol The authentication protocol to be used. Options include CHAP, PAP, and PEAP. The
default protocol is CHAP. IPv6 hosts are not supported if PEAP is the configured
protocol.