![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Remote Site IEEE 802.1X Local Authentication Service
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Contents
Remote Site IEEE 802.1X Local Authentication ServiceLast Updated: July 17, 2012
The Remote Site IEEE 802.1X Local Authentication Service feature provides the ability to configure an access point or wireless-aware router to act as a local RADIUS server. Configuring local authentication service provides a backup authentication service in the event of a WAN link or server failure.
Finding Feature InformationYour software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Restrictions for Configuring Remote Site IEEE 802.1X Local Authentication Service
Information About Configuring Remote Site IEEE 802.1X Local Authentication ServiceOn typical wireless LANs that use 802.1X authentication, access points and wireless-aware routers rely on remote site RADIUS servers to authenticate client devices. This authentication traffic must cross a WAN link. If the WAN link fails, or if the access points and routers cannot reach the RADIUS servers, then the client devices cannot access the wireless network even if their requirements for access are strictly local. To provide for local authentication service or backup authentication service in the event of a WAN link or server failure, you can configure an access point or wireless-aware router to act as a local RADIUS server. The access point or wireless-aware router can authenticate Light Extensible Authentication Protocol (LEAP)-enabled wireless client devices and allow them to join your network. Because the local authentication device does not synchronize its database with the main RADIUS servers. You must configure the local authentication server with client usernames and passwords. The local authentication server also permits you to specify a VLAN and a list of service set identifiers (SSIDs) that a client is allowed to use. Follow these guidelines when you configure an access point or wireless-aware router as a local authentication server:
The table below shows the maximum number of clients that can be configured on a local authentication server.
You configure access points and routers to use the local authentication server when they cannot reach the main servers or when a RADIUS server is not available. The access points and wireless-aware routers stop using the local authentication server automatically when the link to the main servers is restored. If your local authentication server also serves client devices, you must enter the local authentication server access point or router as a network access server (NAS). When a LEAP client associates to the local authentication server access point, the access point uses itself to authenticate the client. How to Configure Remote Site IEEE 802.1X Local Authentication Service
Configuring the Local Authentication Server
SUMMARY STEPS
DETAILED STEPS Configuring User Groups on the Local Authentication ServerPerform this optional task (beginning in local RADIUS server configuration mode) to configure user groups on the local authentication server.
DETAILED STEPS
Creating the User List on the Local Authentication ServerPerform the required task described in the following paragraphs to create a user list on the local authentication server and to configure the users that are allowed to authenticate using the local authentication server.
You must enter a username and password for each user. If you know only the NT hash value of the password, which you can often find in the authentication server database, you can enter the NT hash as a string of hexadecimal digits. To add the user to a user group, enter the group name. If you do not specify a group, the user is not assigned to a specific VLAN and is never forced to reauthenticate. Beginning in local RADIUS server configuration mode, enter the user command for each username: Router(config-radsrv)# user username {password | nthash } password [group group-name] Saving the Configuration on the Local Authentication Server
SUMMARY STEPS
DETAILED STEPS
Configuring Access Points or Routers to Use the Local Authentication ServerPerform this required task to add the local authentication server to the list of servers on the client access point or wireless-aware router.
On the wireless devices that use the local authentication server, use the radius-server host command in privileged EXEC mode to enter the local authentication server as a RADIUS server. The order in which the devices attempt to use the servers matches the order in which you enter the servers in the device configuration. If you are configuring the device to use a RADIUS server for the first time, enter the main RADIUS servers first, and enter the local authentication server last.
Use the radius-server deadtime command in global configuration mode to set an interval during which the access point or router does not attempt to use servers that do not respond, thus avoiding the wait for a request to time out before trying the next configured server. A server marked as dead is skipped by additional requests for the duration of minutes that you specify, up to 1440 (24 hours). To remove the local authentication server from the access point or router configuration, use the no radius-server host command in global configuration mode. DETAILED STEPS
Verifying the Configuration for Local Authentication ServiceUse the show running-config command in global configuration mode to verify the current configuration for local authentication service. DETAILED STEPS
Monitoring and Maintaining 802.1X Local Authentication ServiceTo view statistics collected by the local authentication server, enter the following command in privileged EXEC mode: Router# show radius local-server statistics To reset local authentication server statistics to zero, enter the following command in privileged EXEC mode: Router# clear radius local-server statistics Configuration Examples for Remote Site IEEE 802.1X Local Authentication Service
Setting Up a Local Authentication Server ExampleThis example shows how to set up a local authentication server used by three access points with three user groups and several users: AP# configure terminal AP(config)# aaa new-model AP(config)# aaa group server radius RADIUS_SERVER_GROUP AP(config-sg-radius)# server 10.0.0.1 auth-port 1812 acct-port 1813 AP(config)# aaa authentication login RADIUS_METHOD_LIST AP(config)# radius-server host 10.0.0.1 auth-port 1812 acct-port 1813 key 110337 AP(config)# radius-server local AP(config-radsrv)# nas 10.91.6.159 key 110337 AP(config-radsrv)# nas 10.91.6.162 key 110337 AP(config-radsrv)# nas 10.91.6.181 key 110337 AP(config-radsrv)# group clerks AP(config-radsrv-group)# vlan 87 AP(config-radsrv-group)# ssid batman AP(config-radsrv-group)# ssid robin AP(config-radsrv-group)# reauthentication time 1800 AP(config-radsrv-group)# block count 2 time 600 AP(config-radsrv-group)# group cashiers AP(config-radsrv-group)# vlan 97 AP(config-radsrv-group)# ssid deer AP(config-radsrv-group)# ssid antelope AP(config-radsrv-group)# ssid elk AP(config-radsrv-group)# reauthentication time 1800 AP(config-radsrv-group)# block count 2 time 600 AP(config-radsrv-group)# group managers AP(config-radsrv-group)# vlan 77 AP(config-radsrv-group)# ssid mouse AP(config-radsrv-group)# ssid chipmunk AP(config-radsrv-group)# reauthentication time 1800 AP(config-radsrv-group)# block count 2 time 600 AP(config-radsrv-group)# exit AP(config-radsrv)# user jsmith password twain74 group clerks AP(config-radsrv)# user stpatrick password snake100 group clerks AP(config-radsrv)# user nick password uptown group clerks AP(config-radsrv)# user sam password rover32 group cashiers AP(config-radsrv)# user patsy password crowder group cashiers AP(config-radsrv)# user carl password 272165 group managers AP(config-radsrv)# user vic password lid178 group managers AP(config-radsrv)# end Setting Up Two Main Servers and a Local Authentication Server ExampleThis example shows how to set up two main servers and a local authentication server with a server deadtime of 10 minutes: Router(config)# aaa new-model Router(config)# aaa group server radius RADIUS_SERVER_GROUP Router(config-sg-radius)# server 172.20.0.1 auth-port 1000 acct-port 1001 Router(config-sg-radius)# server 172.10.0.1 auth-port 1645 acct-port 1646 Router(config-sg-radius)# server 10.91.6.151 auth-port 1812 acct-port 1813 Router(config)# radius-server host 172.20.0.1 auth-port 1000 acct-port 1001 key 77654 Router(config)# radius-server host 172.10.0.1 auth-port 1645 acct-port 1646 key 77654 Router(config)# radius-server host 10.91.6.151 auth-port 1812 acct-port 1813 key 110337 Router(config)# radius-server deadtime 10 In this example, if the WAN link to the main servers fails, the access point or wireless-aware router completes these steps when a LEAP-enabled client device associates:
If another client device needs to authenticate during the 10-minute deadtime interval, the access point skips the first two servers and tries the local authentication server first. After the deadtime interval, the access point tries to use the main servers for authentication. When setting a deadtime, you must balance the need to skip dead servers with the need to check the WAN link and begin using the main servers again as soon as possible. Each time an access point or wireless-aware router tries to use the main servers while they are down, the client device that is trying to authenticate might report an authentication timeout. The client device retries and succeeds when the main servers time out and the access point or wireless-aware router tries the local authentication server. You can extend the timeout value on Cisco client devices to accommodate expected server timeouts. Displaying Local Authentication Server Configuration ExampleThe following is sample output for configuration of a local authentication server on the Cisco 2621 router. 2621-1# show run Building configuration... Current configuration : 2954 bytes ! version 12.3 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname 2621-1 ! ! aaa new-model ! ! aaa group server radius RADIUS_LEAP_GROUP server 10.0.0.1 auth-port 1812 acct-port 1813 ! aaa authentication login AUTH_LEAP group RADIUS_LEAP_GROUP aaa session-id common ip subnet-zero ! ! ip dhcp pool 2621-dhcp-pool network 10.0.0.0 255.0.0.0 ! ! ! interface FastEthernet0/0 no ip address shutdown duplex auto speed auto ! interface FastEthernet0/1 no ip address shutdown duplex auto speed auto ! interface FastEthernet1/0 no ip address ! interface FastEthernet1/1 switchport mode trunk no ip address ! interface FastEthernet1/2 no ip address shutdown ! interface FastEthernet1/3 no ip address shutdown ! interface FastEthernet1/4 no ip address shutdown ! interface FastEthernet1/5 no ip address ! ! interface GigabitEthernet1/0 no ip address shutdown ! interface Vlan1 ip address 10.0.0.1 255.0.0.0 ! ip classless ! ip http server no ip http secure-server ! ! ! radius-server local nas 10.0.0.1 key 0 cisco user ap-1 nthash 7 101B2A415547345A5F25790801706510064152425325720D7D04075D523D4F780A user ap-5 nthash 7 144231535C540C7A77096016074B51332753030D0877705A264F450A09720A7307 user user1 nthash 7 1350344A5B5C227B78057B10107A452232515402097C77002B544B45087D0E7200 ! radius-server host 10.0.0.1 auth-port 1812 acct-port 1813 radius-server key cisco ! wlccp authentication-server infrastructure AUTH_LEAP wlccp authentication-server client leap AUTH_LEAP wlccp wds priority 255 interface Vlan1 ! line con 0 line aux 0 line vty 0 4 ! ! ! end Displaying Local Authentication Server Statistics ExampleThe following is sample output for configuration for the show radius local-server statistics command:
router-2621-1# show radius local-server statistics
Successes : 11262 Unknown usernames : 0
Client blocks : 0 Invalid passwords : 8
Unknown NAS : 0 Invalid packet from NAS: 0
NAS : 10.0.0.1
Successes : 11262 Unknown usernames : 0
Client blocks : 0 Invalid passwords : 8
Corrupted packet : 0 Unknown RADIUS message : 0
No username attribute : 0 Missing auth attribute : 0
Shared key mismatch : 0 Invalid state attribute: 0
Unknown EAP message : 0 Unknown EAP auth type : 0
Maximum number of configurable users: 50, current user count: 11
Username Successes Failures Blocks
vayu-ap-1 2235 0 0
vayu-ap-2 2235 0 0
vayu-ap-3 2246 0 0
vayu-ap-4 2247 0 0
vayu-ap-5 2247 0 0
vayu-11 3 0 0
vayu-12 5 0 0
vayu-13 5 0 0
vayu-14 30 0 0
vayu-15 3 0 0
scm-test 1 8 0
router-2621-1#
The first section shows cumulative statistics from the local authentication server. The second section shows statistics for each access point (NAS) that is authorized to use the local authentication server. The third section shows statistics for individual users. If a user is blocked and the lockout time is set to infinite, Blocked appears at the end of the line of statistics for that user. If the lockout time is not set to infinite, Unblocked in x seconds appears at the end of the statistics line for that user. Additional ReferencesMIBsTechnical Assistance
Feature Information for Remote Site IEEE 802.1X Local Authentication ServiceThe following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. © 2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|