3com 5500-ei pwr Instrução De Instalação

Página de 1072
 
2-4 
Create an ISP domain and 
enter its view, or enter the view 
of an existing ISP domain 
domain isp-name  
Required 
Configure an AAA scheme for 
the ISP domain 
scheme { local none | radius-scheme 
radius-scheme-name [ local ] | 
hwtacacs-scheme 
hwtacacs-scheme-name [ local ] } 
Required 
By default, an ISP 
domain uses the 
local AAA scheme.
 
 
You can execute the scheme radius-scheme radius-scheme-name command to adopt an already 
configured RADIUS scheme to implement all the three AAA functions. If you adopt the local 
scheme, only the authentication and authorization functions are implemented, the accounting 
function cannot be implemented. 
If you execute the scheme  radius-scheme  radius-scheme-name  local command, the local 
scheme is used as the secondary scheme in case no RADIUS server is available. That is, if the 
communication between the switch and a RADIUS server is normal, the local scheme is not used; 
otherwise, the local scheme is used. 
If you execute the scheme hwtacacs-scheme hwtacacs-scheme-name local command, the local 
scheme is used as the secondary scheme in case no TACACS server is available. That is, if the 
communication between the switch and a TACACS server is normal, the local scheme is not used; 
if the TACACS server is not reachable or there is a key error or NAS IP error, the local scheme is 
used. 
If you execute the scheme local or scheme none command to adopt local or none as the primary 
scheme, the local authentication is performed or no authentication is performed. In this case you 
cannot specify any RADIUS scheme or HWTACACS scheme at the same time. 
If you configure to use none as the primary scheme, FTP users of the domain cannot pass 
authentication. Therefore, you cannot specify none as the primary scheme if you want to enable 
FTP service. 
 
Configuring separate AAA schemes 
You can use the authenticationauthorization, and accounting commands to specify a scheme for 
each of the three AAA functions (authentication, authorization and accounting) respectively. The 
following gives the implementations of this separate way for the services supported by AAA. 
1) For 
terminal 
users 
Authentication: RADIUS, local, HWTACACS or none. 
Authorization: none or HWTACACS. 
Accounting: RADIUS, HWTACACS or none. 
You can use an arbitrary combination of the above implementations for your AAA scheme configuration. 
2)  For FTP users 
Only authentication is supported for FTP users. 
Authentication: RADIUS, local, or HWTACACS. 
Follow these steps to configure separate AAA schemes: