- Preface
- Overview of the Hardware and Software
- Basic Router Configuration
- Configuring Ethernet CFM and Y.1731 Performance Monitoring on Layer 3 Interfaces
- Configuring Ethernet Virtual Connection Bridge Domain
- Configuring EtherChannel
- Configuring Backup Data Lines and Remote Management
- Configuring Power Efficiency Management
- Configuring Security Features
- Configuring Identity Features on Layer 3 Interface
- Unified Communications on Cisco Integrated Services Routers
- Configuring Next-Generation High-Density PVDM3 Modules
- Multi-Gigabit Fabric on the Router
- Upgrading the Cisco IOS Software
- Wireless Overview
- Configuring the Wireless Device
- Configuring the Radio
- Administering the Wireless Device
- Cisco IOS CLI for Initial Configuration
- Using CompactFlash Memory Cards
- Using ROM Monitor
- Changing the Configuration Register Settings
- Disabling the Mode Button Function
- Preventing Unauthorized Access to Your Access Point
- Protecting Access to Privileged EXEC Commands
Administering the Wireless Device
The following sections describe administration tasks for the wireless device:
Security on the Wireless Device
- Disabling the Mode Button Function
- Preventing Unauthorized Access to Your Access Point
- Protecting Access to Privileged EXEC Commands
- Controlling Access Point Access with RADIUS
- Controlling Access Point Access with TACACS+
Administering the Wireless Device
- Administering the Wireless Hardware and Software
- Resetting the Wireless Device to the Factory Default Configuration
- Monitoring the Wireless Device
- Managing the System Time and Date
- Configuring a System Name and Prompt
- Creating a Banner
Configuring Wireless Device Communication
- Configuring Ethernet Speed and Duplex Settings
- Configuring the Access Point for Wireless Network Management
- Configuring the Access Point for Local Authentication and Authorization
- Configuring the Authentication Cache and Profile
- Configuring the Access Point to Provide DHCP Service
- Configuring the Access Point for Secure Shell
- Configuring Client ARP Caching
- Configuring Multiple VLAN and Rate Limiting for Point-to-Multipoint Bridging
Disabling the Mode Button Function
You can disable the mode button on the wireless device by using the [no] boot mode-button command.
This command disables password recovery. If you lose the privileged EXEC mode password for the access point after entering this command, you will need to contact the Cisco Technical Assistance Center (TAC) to regain access to the access point command line interface (CLI).
Note To reboot the wireless device, use the service-module wlan-ap reset command from the Cisco IOS CLI. See the “Rebooting the Wireless Device” section for information about this command.
The mode button is enabled by default. To disable the access point’s mode button, Follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
DETAILED STEPS
|
|
|
|
|---|---|---|
You can check the status of the mode button by executing the show boot or show boot mode-button command in privileged EXEC mode. The status does not appear in the running configuration. The following shows typical responses to the show boot and show boot mode-button commands:
BOOT path-list: flash:/c1200-k9w7-mx-v123_7_ja.20050430/c1200-k9w7-mx.v123_7_ja.20050430
Config file: flash:/config.txt
Private Config file: flash:/private-config
Enable Break: no
Manual boot: no
Mode button: on
Enable IOS break: no
HELPER path-list:
NVRAM/Config file
buffer size: 32768
ap#show boot mode-button
on
ap#
Note As long as the privileged EXEC password is known, you can use the boot mode-button command to restore the mode button to normal operation.
Preventing Unauthorized Access to Your Access Point
You can prevent unauthorized users from reconfiguring the wireless device and viewing configuration information. Typically, the network administrators must have access to the wireless device while restricting access to users who connect through a terminal or workstation from within the local network.
To prevent unauthorized access to the wireless device, configure one of these security features:
- Username and password pairs, which are locally stored on the wireless device. These pairs authenticate each user before the user can access the wireless device. You can also assign a specific privilege level (read only or read/write) to each username and password pair. For more information, see the “Configuring Username and Password Pairs” section. The default username is Cisco, and the default password is Cisco. Usernames and passwords are case sensitive.
Note The characters TAB, ?, $, +, and [ are invalid characters for passwords.
- Username and password pairs are stored centrally in a database on a security server. For more information, see the “Controlling Access Point Access with RADIUS” section.
Protecting Access to Privileged EXEC Commands
A simple way of providing terminal access control in your network is to use passwords and assign privilege levels. Password protection restricts access to a network or network device. Privilege levels define what commands users can issue after they have logged in to a network device.
Note For complete syntax and usage information for the commands used in this section, see Cisco IOS Security Command Reference for Release 12.4.
This section describes how to control access to the configuration file and privileged EXEC commands. It contains this configuration information:
- Configuring Default Password and Privilege Level
- Setting or Changing a Static Enable Password
- Protecting Enable and Enable Secret Passwords with Encryption
- Configuring Username and Password Pairs
- Configuring Multiple Privilege Levels
Configuring Default Password and Privilege Level
Table 1 shows the default password and privilege level configuration.
Setting or Changing a Static Enable Password
The enable password controls access to the privileged EXEC mode.
The
no enable password command in global configuration mode removes the enable password, but you should use extreme care when using this command. If you remove the enable password, you are locked out of the privileged EXEC mode.
To set or change a static enable password, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
DETAILED STEPS
The enable password is not encrypted and can be read in the wireless device configuration file.
The following example shows how to change the enable password to l1u2c3k4y5. The password is not encrypted and provides access to level 15 (standard privileged EXEC mode access):
Protecting Enable and Enable Secret Passwords with Encryption
To provide an additional layer of security, particularly for passwords that cross the network or that are stored on a TFTP server, you can use either the enable password or enable secret command in global configuration mode. The commands accomplish the same thing; that is, you can establish an encrypted password that users must enter to access privileged EXEC mode (the default) or any privilege level that you specify.
We recommend that you use the enable secret command because it uses an improved encryption algorithm.
If you configure the enable secret command, it takes precedence over the enable password command; the two commands cannot be in effect simultaneously.
To configure encryption for enable and enable secret passwords, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
2. enable password [ level level ] { password | encryption-type encrypted- password }
enable secret [ level level ] { password | encryption-type encrypted- password }
DETAILED STEPS
If both the enable and enable secret passwords are defined, users must enter the enable secret password.
Use the level keyword to define a password for a specific privilege level. After you specify the level and set a password, give the password only to users who need to have access at this level. Use the privilege level command in global configuration mode to specify commands accessible at various levels. For more information, see the “Configuring Multiple Privilege Levels” section.
If you enable password encryption, it applies to all passwords, including username passwords, authentication key passwords, the privileged command password, and console and virtual terminal line passwords.
To remove a password and level, use the no enable password [ level level ] command or the no enable secret [ level level ] command in global configuration mode. To disable password encryption, use the no service password-encryption command in global configuration mode.
This example shows how to configure the encrypted password $1$FaD0$Xyti5Rkls3LoyxzS8 for privilege level 2:
Configuring Username and Password Pairs
You can configure username and password pairs, which are locally stored on the wireless device. These pairs are assigned to lines or interfaces, and they authenticate each user before the user can access the wireless device. If you have defined privilege levels, you can also assign a specific privilege level (with associated rights and privileges) to each username and password pair.
To establish a username-based authentication system that requests a login username and a password, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
2. username name [ privilege level ] { password encryption-type password }
DETAILED STEPS
|
|
|
|
|---|---|---|
username name [ privilege level ] { password encryption-type password } |
Enters the username, privilege level, and password for each user.
|
|
Enables local password checking at login time. Authentication is based on the username specified in Step 2. |
||
To disable username authentication for a specific user, use the no username name command in global configuration mode.
To disable password checking and allow connections without a password, use the no login command in line configuration mode.
Note You must have at least one username configured, and you must have login local set to open a Telnet session to the wireless device. If you do not enter a username for the only username, you can be locked out of the wireless device.
Configuring Multiple Privilege Levels
By default, Cisco IOS software has two modes of password security: user EXEC and privileged EXEC. You can configure up to 16 hierarchical levels of commands for each mode. By configuring multiple passwords, you can allow different sets of users to have access to specified commands.
For example, if you want many users to have access to the clear line command, you can assign it level 2 security and distribute the Level 2 password fairly widely. But if you want more restricted access to the configure command, you can assign it Level 3 security and distribute that password to a more restricted group of users.
Setting the Privilege Level for a Command
To set the privilege level for a command mode, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
2. privilege mode level level command
DETAILED STEPS
When you set a command to a privilege level, all commands whose syntax is a subset of that command are also set to that level. For example, if you set the show ip route command to level 15, the show commands and show ip commands are automatically set to privilege level 15 unless you set them individually to different levels.
To return to the default privilege for a given command, use the no privilege mode level level command command in global configuration mode.
The following example shows how to set the configure command to privilege level 14 and how to define SecretPswd14 as the password users must enter to use level 14 commands:
Logging Into and Exiting a Privilege Level
To log in to a specified privilege level or to exit to a specified privilege level, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
DETAILED STEPS
|
|
|
|
|---|---|---|
Controlling Access Point Access with RADIUS
This section describes how to control administrator access to the wireless device by using Remote Authentication Dial-In User Service (RADIUS). For complete instructions on configuring the wireless device to support RADIUS, see the “Configuring Radius and TACACS+ Servers” chapter in Cisco IOS Software Configuration Guide for Cisco Aironet Access Points.
RADIUS provides detailed accounting information and flexible administrative control over authentication and authorization processes. RADIUS is facilitated through authentication, authorization, and accounting (AAA) and can be enabled only through AAA commands.
Note For complete syntax and usage information for the commands used in this section, see Cisco IOS Security Command Reference.
These sections describe RADIUS configuration:
- Default RADIUS Configuration
- Configuring RADIUS Login Authentication (required)
- Defining AAA Server Groups (optional)
- Configuring RADIUS Authorization for User Privileged Access and Network Services (optional)
- Displaying the RADIUS Configuration
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 who are accessing the wireless device through the command-line interface (CLI).
Configuring RADIUS Login Authentication
To configure AAA authentication, you define a named list of authentication methods and then apply the list to various interfaces. The method list defines the types of authentication to be performed and the sequence in which they are performed; it must be applied to a specific interface before any defined authentication methods are performed. The only exception is the default method list (which is named default). The default method list is automatically applied to all interfaces except those that have a named method list explicitly defined.
A method list describes the sequence and authentication methods to be used to authenticate a user. You can designate one or more security protocols for authentication, thus ensuring a backup system for authentication in case the initial method fails. The software uses the first method listed to authenticate users. If that method fails to respond, the software selects the next authentication method in the method list. This process continues until there is successful communication with a listed authentication method or until all defined methods are exhausted. If authentication fails at any point in this cycle—that is, the security server or local username database responds by denying the user access—the authentication process stops, and no other authentication methods are attempted.
To configure login authentication, follow these steps, beginning in privileged EXEC mode. This procedure is required.
SUMMARY STEPS
3. aaa authentication login { default | list-name } method1 [ method2... ]
4. line [ console | tty | vty ] line-number [ ending-line-number ]
DETAILED STEPS
|
|
|
|
|---|---|---|
aaa authentication login { default | list-name } method1 [ method2... ] |
Creates a login authentication method list.
|
|
line [ console | tty | vty ] line-number [ ending-line-number ] |
Enters line configuration mode, and configures the lines for which to apply the authentication list. |
|
To disable AAA, use the no aaa new-model command in global command mode. To disable AAA authentication, use the no aaa authentication login {default | list-name } method1 [ method2... ] command in global command mode. To either disable RADIUS authentication for logins or to return to the default value, use the no login authentication { default | list-name } command in line configuration mode.
Defining AAA Server Groups
You can configure the wireless device to use AAA server groups to group existing server hosts for authentication. You select a subset of the configured server hosts and use them for a particular service. The server group is used with a global server-host list, which lists the IP addresses of the selected server hosts.
Server groups can also include multiple host entries for the same server if each entry has a unique identifier (the combination of the IP address and UDP port number), allowing different ports to be individually defined as RADIUS hosts providing a specific AAA service. If you configure two different host entries on the same RADIUS server for the same service (such as accounting), the second configured host entry acts as a failover backup to the first one.
You use the server group server configuration command to associate a particular server with a defined group server. You can either identify the server by its IP address or identify multiple host instances or entries by using the optional auth-port and acct-port keywords.
To define the AAA server group and associate a particular RADIUS server with it, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
3. radius-server host { hostname | ip-address } [ auth-port port-number ] [ acct-port port-number ] [ timeout seconds ] [ retransmit retries ] [ key string ]
4. aaa group server radius group-name
DETAILED STEPS
|
|
|
|
|---|---|---|
radius-server host { hostname | ip-address } [ auth-port port-number ] [ acct-port port-number ] [ timeout seconds ] [ retransmit retries ] [ key string ] |
Specifies the IP address or hostname of the remote RADIUS server host.
Note The key is a text string that must match the encryption key that is used on the RADIUS server. Always configure the key as the last item in the radius-server host command. Leading spaces are ignored, but spaces within and at the end of the key are used. If you use spaces in your key, do not enclose the key in quotation marks unless the quotation marks are part of the key. To configure the wireless device to recognize more than one host entry that is associated with a single IP address, enter this command as many times as necessary, making sure that each UDP port number is different. The wireless device software searches for hosts in the order in which you specify them. Set the timeout, retransmit, and encryption key values to use with the specific RADIUS host. |
|
Defines the AAA server-group with a group name. This command puts the wireless device in a server group configuration mode. |
||
Associates a particular RADIUS server with the defined server group. Repeat this step for each RADIUS server in the AAA server group. Each server in the group must be previously defined in Step 2. |
||
Enables RADIUS login authentication. See the “Configuring RADIUS Login Authentication” section of the “Configuring Radius and TACACS+ Servers” chapter in Cisco IOS Software Configuration Guide for Cisco Aironet Access Points. |
To remove the specified RADIUS server, use the no radius-server host hostname | ip-address command in global configuration mode. To remove a server group from the configuration list, use the no aaa group server radius group-name command in global configuration mode. To remove the IP address of a RADIUS server, use the no server ip-address command in sg-radius configuration mode.
In the following is example, the wireless device is configured to recognize two different RADIUS group servers ( group1 and group2). Group1 has two different host entries on the same RADIUS server which are configured for the same services. The second host entry acts as a failover backup to the first entry.
Configuring RADIUS Authorization for User Privileged Access and
Network Services
AAA authorization limits the services that are available to a user. When AAA authorization is enabled, the wireless device uses information retrieved from the user’s profile, which is in the local user database or on the security server, to configure the user session. The user is granted access to a requested service only if the user profile allows it.
You can use the aaa authorization command in global configuration mode with the radius keyword to set parameters that restrict a user’s network access to privileged EXEC mode.
The aaa authorization exec radius command sets these authorization parameters:
- Use RADIUS for privileged EXEC access authorization if authentication was performed by using RADIUS.
- Use the local database if authentication was not performed by using RADIUS.
Note Authorization is bypassed for authenticated users who log in through the CLI even if authorization has been configured.
To specify RADIUS authorization for privileged EXEC access and network services, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
2. aaa authorization network radius
DETAILED STEPS
To disable authorization, use the no aaa authorization { network | exec } method1 command in global configuration mode.
Displaying the RADIUS Configuration
To display the RADIUS configuration, use the show running-config command in privileged EXEC mode.
Controlling Access Point Access with TACACS+
This section describes how to control administrator access to the wireless device using Terminal Access Controller Access Control System Plus (TACACS+). For complete instructions on configuring the wireless device to support TACACS+, see the “Configuring Radius and TACACS+ Servers” chapter in Cisco IOS Software Configuration Guide for Cisco Aironet Access Points.
TACACS+ provides detailed accounting information and flexible administrative control over authentication and authorization processes. TACACS+ is facilitated through AAA and can be enabled only through AAA commands.
Note For complete syntax and usage information for the commands used in this section, see Cisco IOS Security Command Reference.
These sections describe TACACS+ configuration:
- Default TACACS+ Configuration
- Configuring TACACS+ Login Authentication
- Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services
- Displaying the TACACS+ Configuration
Default TACACS+ Configuration
TACACS+ and AAA are disabled by default.
To prevent a lapse in security, you cannot configure TACACS+ through a network management application.When enabled, TACACS+ can authenticate administrators who are accessing the wireless device through the CLI.
Configuring TACACS+ Login Authentication
To configure AAA authentication, you define a named list of authentication methods and then apply the list to various interfaces. The method list defines the types of authentication to be performed and the sequence in which they are performed; it must be applied to a specific interface before any defined authentication methods are performed. The only exception is the default method list (which is named default). The default method list is automatically applied to all interfaces except those that have a named method list explicitly defined.
A method list describes the sequence and authentication methods to be used to authenticate a user. You can designate one or more security protocols for authentication, thus ensuring a backup system for authentication in case the initial method fails. The software uses the first method listed to authenticate users. If that method fails to respond, the software selects the next authentication method in the method list. This process continues until there is successful communication with a listed authentication method or until all defined methods are exhausted. If authentication fails at any point in this cycle—that is, the security server or local username database responds by denying the user access—the authentication process stops, and no other authentication methods are attempted.
To configure login authentication, follow these steps, beginning in privileged EXEC mode. This procedure is required.
SUMMARY STEPS
3. aaa authentication login { default | list-name } method1 [ method2... ]
4. line [ console | tty | vty ] line-number [ ending-line-number ]
DETAILED STEPS
To disable AAA, use the no aaa new-model command in global configuration mode. To disable AAA authentication, use the no aaa authentication login {default | list-name } method1 [ method2... ] command in global configuration mode. To either disable TACACS+ authentication for logins or to return to the default value, use the no login authentication { default | list-name } command in line configuration mode.
Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services
AAA authorization limits the services available to a user. When AAA authorization is enabled, the wireless device uses information retrieved from the user profile, which is located either in the local user database or on the security server, to configure the user session. The user is granted access to a requested service only if the information in the user profile allows it.
You can use the aaa authorization command in global configuration mode with the tacacs+ keyword to set parameters that restrict a user network access to privileged EXEC mode.
The aaa authorization exec tacacs+ local command sets these authorization parameters:
- Use TACACS+ for privileged EXEC access authorization if authentication was performed by using TACACS+.
- Use the local database if authentication was not performed by using TACACS+.
Note Authorization is bypassed for authenticated users who log in through the CLI even if authorization has been configured.
To specify TACACS+ authorization for privileged EXEC access and network services, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
2. aaa authorization network tacacs+
DETAILED STEPS
To disable authorization, use the no aaa authorization { network | exec } method1 command in global configuration mode.
Displaying the TACACS+ Configuration
To display TACACS+ server statistics, use the show tacacs command in privileged EXEC mode.
Administering the Wireless Hardware and Software
This section provides instructions for performing the following tasks:
- Resetting the Wireless Device to the Factory Default Configuration
- Rebooting the Wireless Device
- Monitoring the Wireless Device
Resetting the Wireless Device to the Factory Default Configuration
To reset the wireless device hardware and software to its factory default configuration, use the service-module wlan-ap0 reset default-config command in the router’s Cisco IOS privileged EXEC mode.
Because you may lose data, use only the
service-module wlan-ap0 reset command to recover from a shutdown or failed state.
Rebooting the Wireless Device
To perform a graceful shutdown and reboot the wireless device, use the service-module wlan-ap0 reload command in the router’s Cisco IOS privileged EXEC mode. At the confirmation prompt, press Enter to confirm the action, or enter n to cancel.
When running in autonomous mode, the reload command saves the configuration before rebooting. If the attempt is unsuccessful, the following message displays:
When running in Lightweight Access Point Protocol (LWAPP) mode, the reload function is typically handled by the wireless LAN controller (WLC). If you enter the service-module wlan-ap0 reload command, you are prompted with the following message:
Still want to proceed? [yes]
Monitoring the Wireless Device
This section provides commands for monitoring hardware on the router.
Displaying Wireless Device Statistics
Use the service-module wlan-ap0 statistics command in privileged EXEC mode to display wireless device statistics. The following is sample output for the command:
Registration request timeout reset count = 0
Error recovery timeout reset count = 0
Module registration count = 10
The last IOS initiated event was a cli reload at *04:27:32.041 UTC Fri Mar 8 2007
Displaying Wireless Device Status
Use the service-module wlan-ap0 status command in privileged EXEC mode to display the status of the wireless device and its configuration information. The following is sample output for the command:
Service Module is Cisco wlan-ap0
Service Module supports session via TTY line 2
Service Module is in Steady state
Service Module reset on error is disabled
Getting status from the Service Module, please wait..
Image path = flash:c8xx_19xx_ap-k9w7-mx.acregr/c8xx_19xx_ap-k9w7-mx.acre
gr
System uptime = 0 days, 4 hours, 28 minutes, 5 seconds
Router#d was introduced for embedded wireless LAN access points on Integrated Services Routers.
Managing the System Time and Date
You can manage the system time and date on the wireless device automatically, by using the Simple Network Time Protocol (SNTP), or manually, by setting the time and date on the wireless device.
Note For complete syntax and usage information for the commands used in this section, see Cisco IOS Configuration Fundamentals Command Reference for Release 12.4.
This section provides the following configuration information:
Understanding Simple Network Time Protocol
Simple Network Time Protocol (SNTP) is a simplified, client-only version of NTP. SNTP can only receive the time from NTP servers; it cannot provide time services to other systems. SNTP typically provides time within 100 milliseconds of the accurate time, but it does not provide the complex filtering and statistical mechanisms of NTP.
You can configure SNTP to request and accept packets from configured servers or to accept NTP broadcast packets from any source. When multiple sources are sending NTP packets, the server with the best stratum is selected. Click this URL for more information on NTP and strata:
http://www.cisco.com/en/US/docs/ios/12_1/configfun/configuration/guide/fcd303.html#wp1001075
If multiple servers are at the same stratum, a configured server is preferred rather than a broadcast server. If multiple servers pass both tests, the first one to send a time packet is selected. SNTP chooses a new server only if the client stops receiving packets from the currently selected server, or if (according to the above criteria) SNTP discovers a better server.
Configuring SNTP
SNTP is disabled by default. To enable SNTP on the access point, use one or both of the commands listed in Table 2 in global configuration mode.
|
|
|
|---|---|
Configures SNTP to accept NTP packets from any NTP broadcast server. |
Enter the sntp server command once for each NTP server. The NTP servers must be configured to respond to the SNTP messages from the access point.
If you enter both the sntp server command and the sntp broadcast client command, the access point accepts time from a broadcast server but prefers time from a configured server, if the strata are equal. To display information about SNTP, use the show sntp EXEC command.
Configuring Time and Date Manually
If no other source of time is available, you can manually configure the time and date after restarting the system. The time remains accurate until the next system restart. We recommend that you use manual configuration only as a last resort. If you have an outside source to which the wireless device can synchronize, you do not need to manually set the system clock.
This section contains the following configuration information:
Setting the System Clock
If you have an outside source on the network that provides time services, such as an NTP server, you do not need to manually set the system clock.
To set the system clock, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
1. clock set hh : mm : ss day month year
DETAILED STEPS
|
|
|
|
|---|---|---|
Manually sets the system clock by using one of these formats: |
||
This example shows how to manually set the system clock to 1:32 p.m. on July 23, 2001:
Displaying the Time and Date Configuration
To display the time and date configuration, use the show clock [ detail ] command in privileged EXEC mode.
The system clock keeps an authoritative flag that shows whether the time is authoritative (believed to be accurate). If the system clock has been set by a timing source such as NTP, the flag is set. If the time is not authoritative, it is used only for display purposes. Until the clock is authoritative and the authoritative flag is set, the flag prevents peers from synchronizing to the clock when the peers’ time is invalid.
The symbol that precedes the show clock display has this meaning:
Configuring the Time Zone
To manually configure the time zone, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
DETAILED STEPS
|
|
|
|
|---|---|---|
| Because the wireless device keeps internal time in UTC1, this command is used only for display purposes and when the time is manually set. |
||
|
|
The minutes-offset variable in the clock timezone command in global configuration mode is available for situations where a local time zone is a percentage of an hour different from UTC. For example, the time zone for some sections of Atlantic Canada (AST) is UTC-3.5, where the 3 means 3 hours, and the.5 means 50 percent. In this case, the necessary command is clock timezone AST -3 30.
To set the time to UTC, use the no clock timezone command in global configuration mode.
Configuring Summer Time (Daylight Saving Time)
To configure summer time (daylight saving time) in areas where it starts and ends on a particular day of the week each year, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
2. clock summer-time zone recurring [ week day month hh : mm week day month hh : mm [ offset ]]
DETAILED STEPS
The first part of the clock summer-time global configuration command specifies when summer time begins, and the second part specifies when it ends. All times are relative to the local time zone. The start time is relative to standard time. The end time is relative to summer time. If the starting month is after the ending month, the system assumes that you are in the southern hemisphere.
This example shows how to specify that summer time starts on the first Sunday in April at 02:00 and ends on the last Sunday in October at 02:00:
If summer time in your area does not follow a recurring pattern (configure the exact date and time of the next summer time events), follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
1. clock summer-time zone date [ month date year hh : mm month date year hh : mm [ offset ]]
clock summer-time zone date [ date month year hh : mm date month year hh : mm [ offset ]]
DETAILED STEPS
The first part of the clock summer-time global configuration command specifies when summer time begins, and the second part specifies when it ends. All times are relative to the local time zone. The start time is relative to standard time. The end time is relative to summer time. If the starting month is after the ending month, the system assumes that you are in the southern hemisphere.
To disable summer time, use the no clock summer-time command in global configuration mode.
This example shows how to set summer time to start on October 12, 2000, at 02:00, and end on April 26, 2001, at 02:00:
Configuring a System Name and Prompt
You configure the system name on the wireless device to identify it. By default, the system name and prompt are ap.
If you have not configured a system prompt, the first 20 characters of the system name are used as the system prompt. A greater-than symbol (>) is appended. The prompt is updated whenever the system name changes, unless you manually configure the prompt by using the prompt command in global configuration mode.
Note For complete syntax and usage information for the commands used in this section, see Cisco IOS Configuration Fundamentals Command Reference and Cisco IOS IP Addressing Services Command Reference.
This section contains the following configuration information:
Default System Name and Prompt Configuration
Configuring a System Name
To manually configure a system name, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
DETAILED STEPS
When you set the system name, the name is also used as the system prompt.
To return to the default hostname, use the no hostname command in global configuration mode.
Understanding DNS
The DNS protocol controls the Domain Name System (DNS), a distributed database with which you can map hostnames to IP addresses. When you configure DNS on the wireless device, you can substitute the hostname for the IP address with all IP commands, such as ping, telnet, connect, and related Telnet support operations.
IP defines a hierarchical naming scheme that allows a device to be identified by its location or domain. Domain names are pieced together with periods (.) as the delimiting characters. For example, Cisco Systems is a commercial organization that IP identifies by a com domain name, so its domain name is cisco.com. A specific device in this domain, such as the File Transfer Protocol (FTP) system, is identified as ftp.cisco.com.
To keep track of domain names, IP has defined the concept of a domain name server, which holds a cache (or database) of names mapped to IP addresses. To map domain names to IP addresses, you must first identify the hostnames, specify the name server that is present on your network, and enable the DNS.
This section contains the following configuration information:
Default DNS Configuration
Table 3 describes the default DNS configuration.
|
|
|
|---|---|
Setting Up DNS
To set up the wireless device to use the DNS, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
3. ip name-server server-address1 [ server-address2... server-address6 ]
DETAILED STEPS
If you use the wireless device IP address as its hostname, the IP address is used and no DNS query occurs. If you configure a hostname that contains no periods (.), a period followed by the default domain name is appended to the hostname before the DNS query is made to map the name to an IP address. The default domain name is the value set by the ip domain-name command in global configuration mode. If there is a period (.) in the hostname, Cisco IOS software looks up the IP address without appending any default domain name to the hostname.
To remove a domain name, use the no ip domain-name name command in global configuration mode. To remove a name server address, use the no ip name-server server-address command in global configuration mode. To disable DNS on the wireless device, use the no ip domain-lookup command in global configuration mode.
Displaying the DNS Configuration
To display the DNS configuration information, use the show running-config command in privileged EXEC mode.
Note When DNS is configured on the wireless device, the show running-config command sometimes displays a server IP address instead of its name.
Creating a Banner
You can configure a message-of-the-day (MOTD) and a login banner. The MOTD banner appears on all connected terminals at login and is useful for sending messages that affect all network users (such as impending system shutdowns).
The login banner also appears on all connected terminals. It appears after the MOTD banner and appears before the login prompts appear.
Note For complete syntax and usage information for the commands used in this section, see Cisco IOS Configuration Fundamentals Command Reference.
This section contains the following configuration information:
- Default Banner Configuration
- Configuring a Message-of-the-Day Login Banner
- Configuring a Login Banner
Default Banner Configuration
Configuring a Message-of-the-Day Login Banner
You can create a single-line or multiline message banner that appears on the screen when someone logs into the wireless device.
To configure an MOTD login banner, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
DETAILED STEPS
To delete the MOTD banner, use the no banner motd command in global configuration mode.
The following is example shows how to configure a MOTD banner for the wireless device. The pound sign (#) is used as the beginning and ending delimiter:
Configuring a Login Banner
You can configure a login banner to appear on all connected terminals. This banner appears after the MOTD banner and appears before the login prompt appears.
To configure a login banner, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
DETAILED STEPS
To delete the login banner, use the no banner login command in global configuration mode.
The following example shows how to configure a login banner for the wireless device using the dollar sign ($) as the beginning and ending delimiter:
Configuring Ethernet Speed and Duplex Settings
The Cisco 1941-W ISR interface supports only 1000 Mbps speed and duplex settings by default, and the interface is always up. When the wireless device receives inline power from a switch, any change in the speed or duplex settings that resets the Ethernet link reboots the wireless device.
Note The speed and duplex settings on the wireless device Ethernet port must match the Ethernet settings on the port to which the wireless device is connected. If you change the settings on the port to which the wireless device is connected, change the settings on the wireless device Ethernet port to match.
The Ethernet speed and duplex are set to auto by default. To configure Ethernet speed and duplex, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
DETAILED STEPS
|
|
|
|
|---|---|---|
Configures the Ethernet speed. we recommend that you use auto, the default setting. |
||
Configures the duplex setting. we recommend that you use auto, the default setting. |
||
Configuring the Access Point for Wireless Network Management
You can enable the wireless device for wireless network management. The wireless network manager (WNM) manages the devices on your wireless LAN.
Enter the following command to configure the wireless device to interact with the WNM:
Enter the following command to check the authentication status between the WDS access point and the WNM:
Possible statuses are not authenticated, authentication in progress, authentication fail, authenticated, and security keys setup.
Configuring the Access Point for Local Authentication and Authorization
You can configure AAA to operate without a server by configuring the wireless device to implement AAA in local mode. The wireless device then handles authentication and authorization. No accounting is available in this configuration.
Note You can configure the wireless device as a local authenticator for 802.1x-enabled client devices to provide a backup for your main server or to provide authentication service on a network without a RADIUS server. See Using the Access Point as a Local Authenticator at Cisco.com for detailed instructions on configuring the wireless device as a local authenticator: http://www.cisco.com/en/US/docs/routers/access/wireless/software/guide/SecurityLocalAuthent.html.
To configure the wireless device for local AAA, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
3. aaa authentication login default local
4. aaa authorization exec local
5. aaa authorization network local
6. username name [ privilege level ] { password encryption-type password }
DETAILED STEPS
To disable AAA, use the no aaa new-model command in global configuration mode. To disable authorization, use the no aaa authorization { network | exec } method1 command in global configuration mode.
Configuring the Authentication Cache and Profile
The authentication cache and profile feature allows the access point to cache the authentication and authorization responses for a user so that subsequent authentication and authorization requests do not need to be sent to the AAA server.
Note On the access point, this feature is supported only for Admin authentication.
The following commands that support this feature are included in Cisco IOS Release 12.3(7):
Note See Cisco IOS Command Reference for Cisco Aironet Access Points and Bridges, Versions 12.4(10b)JA and 12.3(8)JEC for information about these commands.
The following is a configuration example for an access point configured for Admin authentication using TACACS+ with the authorization cache enabled. Although this example is based on a TACACS server, the access point could be configured for Admin authentication using RADIUS:
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname ap
!
!
username Cisco password 7 123A0C041104
username admin privilege 15 password 7 01030717481C091D25
ip subnet-zero
!
!
aaa new-model
!
!
aaa group server radius rad_eap
server 192.168.134.229 auth-port 1645 acct-port 1646
!
aaa group server radius rad_mac
server 192.168.134.229 auth-port 1645 acct-port 1646
!
aaa group server radius rad_acct
server 192.168.134.229 auth-port 1645 acct-port 1646
!
aaa group server radius rad_admin
server 192.168.134.229 auth-port 1645 acct-port 1646
cache expiry 1
cache authorization profile admin_cache
cache authentication profile admin_cache
!
aaa group server tacacs+ tac_admin
server 192.168.133.231
cache expiry 1
cache authorization profile admin_cache
cache authentication profile admin_cache
!
aaa group server radius rad_pmip
!
aaa group server radius dummy
!
aaa authentication login default local cache tac_admin group tac_admin
aaa authentication login eap_methods group rad_eap
aaa authentication login mac_methods local
aaa authorization exec default local cache tac_admin group tac_admin
aaa accounting network acct_methods start-stop group rad_acct
aaa cache profile admin_cache
all
!
aaa session-id common
!
!
!
bridge irb
!
!
interface Dot11Radio0
no ip address
no ip route-cache
shutdown
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0 54.0
station-role root
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
bridge-group 1 spanning-disabled
!
interface Dot11Radio1
no ip address
no ip route-cache
shutdown
speed basic-6.0 9.0 basic-12.0 18.0 basic-24.0 36.0 48.0 54.0
station-role root
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
bridge-group 1 spanning-disabled
!
interface FastEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
bridge-group 1
no bridge-group 1 source-learning
bridge-group 1 spanning-disabled
!
interface BVI1
ip address 192.168.133.207 255.255.255.0
no ip route-cache
!
ip http server
ip http authentication aaa
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
ip radius source-interface BVI1
!
tacacs-server host 192.168.133.231 key 7 105E080A16001D1908
tacacs-server directed-request
radius-server attribute 32 include-in-access-req format %h
radius-server host 192.168.134.229 auth-port 1645 acct-port 1646 key 7 111918160405041E00
radius-server vsa send accounting
!
control-plane
!
bridge 1 route ip
!
!
!
line con 0
transport preferred all
transport output all
line vty 0 4
transport preferred all
transport input all
transport output all
line vty 5 15
transport preferred all
transport input all
transport output all
!
end
Configuring the Access Point to Provide DHCP Service
The following sections describe how to configure the wireless device to act as a DHCP server:
Setting up the DHCP Server
By default, access points are configured to receive IP settings from a DHCP server on your network. You can also configure an access point to act as a DHCP server to assign IP settings to devices on both wired and wireless LANs.
Note When you configure the access point as a DHCP server, it assigns IP addresses to devices on its subnet. The devices communicate with other devices on the subnet but not beyond it. If data needs to be passed beyond the subnet, you must assign a default router. The IP address of the default router should be on the same subnet as the access point configured as the DHCP server.
For detailed information on DHCP-related commands and options, see the DHCP part in Cisco IOS IP Addressing Services Configuration Guide, Release 12.4. Click this URL to browse to the DHCP part:
http://www.cisco.com/en/US/docs/ios/ipaddr/configuration/guide/
iad_dhcp_rdmp_ps6350_TSD_Products_Configuration_Guide_Chapter.html
To configure an access point to provide DHCP service and to specify a default router, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
2. ip dhcp excluded-address low_address [high_address]
4. network subnet_number [mask | prefix-length]
5. lease {days [hours] [minutes] | infinite }
DETAILED STEPS
Use the no forms of these commands to return to default settings.
The following example shows how to configure the wireless device as a DHCP server, how to exclude a range of IP address, and how to assign a default router:
Monitoring and Maintaining the DHCP Server Access Point
The following sections describe commands you can use to monitor and maintain the DHCP server access point:
show Commands
To display information about the wireless device as DHCP server, enter the commands in Table 4 , in privileged EXEC mode.
clear Commands
To clear DHCP server variables, use the commands in Table 5 , in privileged EXEC mode.
debug Command
To enable DHCP server debugging, use the following command in privileged EXEC mode:
debug ip dhcp server {events | packets | linkage}
Use the no form of the command to disable debugging for the wireless device DHCP server.
Configuring the Access Point for Secure Shell
This section describes how to configure the Secure Shell (SSH) feature.
Note For complete syntax and usage information for the commands used in this section, see the “Secure Shell Commands” section in Cisco IOS Security Command Reference for Release 12.4.
Understanding SSH
SSH is a protocol that provides a secure, remote connection to a Layer 2 or Layer 3 device. There are two versions of SSH: SSH version 1 and SSH version 2. This software release supports both SSH versions. If you do not specify the version number, the access point defaults to version 2.
SSH provides more security for remote connections than Telnet by providing strong encryption when a device is authenticated. The SSH feature has an SSH server and an SSH integrated client. The client supports the following user authentication methods:
- RADIUS (for more information, see the “Controlling Access Point Access with RADIUS” section)
- Local authentication and authorization (for more information, see the “Configuring the Access Point for Local Authentication and Authorization” section)
For more information about SSH, see Part 5, “Other Security Features” in the Cisco IOS Security Configuration Guide for Release 12.4.
Note The SSH feature in this software release does not support IP Security (IPsec).
Configuring SSH
Before configuring SSH, download the cryptographic software image from Cisco.com. For more information, see the release notes for this release.
For information about configuring SSH and displaying SSH settings, see Part 6, “ Other Security Features ” in the Cisco IOS Security Configuration Guide for Release 12.4, which is available at Cisco.com at the following link:
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/12_4/sec_12_4_book.html
Configuring Client ARP Caching
You can configure the wireless device to maintain an address resolution protocol (ARP) cache for associated client devices. Maintaining an ARP cache on the wireless device reduces the traffic load on your wireless LAN. ARP caching is disabled by default.
This section contains this information:
Understanding Client ARP Caching
ARP caching on the wireless device reduces the traffic on your wireless LAN by stopping ARP requests for client devices at the wireless device. Instead of forwarding ARP requests to client devices, the wireless device responds to requests on behalf of associated client devices.
When ARP caching is disabled, the wireless device forwards all ARP requests through the radio port to associated clients. The client that receives the ARP request responds. When ARP caching is enabled, the wireless device responds to ARP requests for associated clients and does not forward requests to clients. When the wireless device receives an ARP request for an IP address not in the cache, the wireless device drops the request and does not forward it. In its beacon, the wireless device includes an information element to alert client devices that they can safely ignore broadcast messages to increase battery life.
Optional ARP Caching
When a non-Cisco client device is associated to an access point and is not passing data, the wireless device might not know the client IP address. If this situation occurs frequently on your wireless LAN, you can enable optional ARP caching. When ARP caching is optional, the wireless device responds on behalf of clients with IP addresses known to the wireless device but forwards out of its radio port any ARP requests addressed to unknown clients. When the wireless device learns the IP addresses for all associated clients, it drops ARP requests not directed to its associated clients.
Configuring ARP Caching
To configure the wireless device to maintain an ARP cache for associated clients, follow these steps, beginning in privileged EXEC mode.
SUMMARY STEPS
DETAILED STEPS
|
|
|
|
|---|---|---|
The following example shows how to configure ARP caching on an access point:
Configuring Multiple VLAN and Rate Limiting for Point-to-Multipoint Bridging
This feature modifies the way that point-to-multipoint bridging can be configured to operate on multiple VLANs with the ability to control traffic rates on each VLAN.
Note A rate-limiting policy can be applied only to Fast Ethernet ingress ports on non-root bridges.
In a typical scenario, multiple-VLAN support permits users to set up point-to-multipoint bridge links with remote sites, with each remote site on a separate VLAN. This configuration provides the capability for separating and controlling traffic to each site. Rate limiting ensures that no remote site consumes more than a specified amount of the entire link bandwidth. Only uplink traffic can be controlled by using the Fast Ethernet ingress ports of non-root bridges.
Using the class-based policing feature, you can specify the rate limit and apply it to the ingress of the Ethernet interface of a non-root bridge. Applying the rate at the ingress of the Ethernet interface ensures that all incoming Ethernet packets conform to the configured rate.
Feedback