2–Planning
Security
59265-02 B 2-21
In addition to authorization, you can configure the switch to require authentication
to validate the identity of the connecting switch, device, or host. Authentication
can be performed locally using the switch’s security database, or remotely using a
RADIUS server such as Microsoft RADIUS. With a RADIUS server, the security
database for the entire fabric resides on the server. In this way, the security
database can be managed centrally, rather than on each switch. You can
configure up to five RADIUS servers to provide failover.
You can configure the RADIUS server to authenticate just the switch or both the
switch and the initiator device, if the device supports authentication. When using a
RADIUS server, every switch in the fabric must have a network connection. A
RADIUS server can also be configured to authenticate user accounts as
described in “Internet Protocol Support” on page 2-18. A secure connection is
required to authenticate user logins with a RADIUS server. For information about
secure connections, refer to “Connection Security” on page 2-20.
Consider the your devices, switches, and management agents, and evaluate the
need for authorization and authentication. Also consider whether the security
database is to be distributed on the switches or centralized on a RADIUS server,
and how many servers to configure.
The following examples illustrate how to configure a security database:
Security Example: Switches and Adapters with Authentication
Security Example: RADIUS Server
Security Example: Host Authentication
To Next Page
Loading...
Need help?
General
