Cisco wireless pdf

Step 3 Enter the administrative username and password to be assigned to this controller. The default administrative username and password are admin and admin, respectively. If you do not want to use the service port or if you want to assign a static IP address to the service port, enter none. Step 5 If you entered none in Step 4, enter the IP address and netmask for the service-port interface on the next two lines.

Step 7 Enter the IP address of the management interface. Note The management interface is the default interface for in-band management of the controller and connectivity to enterprise services such as AAA servers. Step 8 Enter the IP address of the management interface netmask. Step 9 Enter the IP address of the default router. Note This prompt does not appear for Cisco Series Controllers because you are not required to configure an AP-manager interface.

Note Although the name that you enter here is assigned to both the mobility group and the RF group, these groups are not identical. Otherwise, enter no. Please see the documentation for more details. Note Enter help to view the list of available country codes. Note You can enter more than one country code if you want to manage access points in multiple countries from a single controller. Step 19 Enable or disable the Note The controller network module installed in a Cisco Integrated Services Router does not have a battery and cannot save a time setting.

Therefore, it must receive a time setting from an external NTP server when it powers up. Step 22 If you entered no in Step 21 and want to manually configure the system time on your controller now, enter YES. If you do not want to configure the system time now, enter no. Step 24 When prompted to verify that the configuration is correct, enter yes or NO.

The controller saves your configuration, reboots, and prompts you to log in. Note Opera and Netscape are not supported. We recommend that you use the service-port interface. Step 2 When prompted, enter a valid username and password and click OK.

The controller Summary page appears. Note The administrative username and password that you created in the configuration wizard are case sensitive. The default username is admin, and the default password is admin. Step 2 Click Close to complete the logoff process and prevent unauthorized users from accessing the controller GUI.

Step 3 When prompted to confirm your decision, click Yes. You also have the option of downloading an externally generated certificate. Otherwise, choose Disabled. The default value is Disabled. Web mode is not a secure connection. The default value is Enabled. Secure web mode is a secure connection. Step 4 In the Web Session Timeout text box, enter the amount of time in minutes before the web session times out due to inactivity.

You can enter a value between 30 and minutes inclusive , and the default value is 30 minutes. Step 5 Click Apply to commit your changes. Note If desired, you can delete the current certificate by clicking Delete Certificate and have the controller generate a new certificate by clicking Regenerate Certificate.

Step 7 Click Save Configuration to save your changes. The default value is disabled. They must use a browser that is configured to use a more secure protocol such as SSLv3 or later.

The default value is enabled. Step 5 To verify that the controller has generated a certificate, enter this command: show certificate summary Information similar to the following appears: Web Administration Certificate Locally Generated Web Authentication Certificate Locally Generated Certificate compatibility mode Step 6 Optional If you need to generate a new certificate, enter this command: config certificate generate webadmin After a few seconds, the controller verifies that the certificate has been generated.

Also, if you load the certificate through the distribution system network port, the TFTP server can be on any subnet. Note Chained certificates are supported for web authentication only and not for the management certificate. The length of the key can vary from bits, which is relatively insecure, to thousands of bits, which is very secure.

When you obtain a new certificate from a Certificate Authority, make sure that the RSA key embedded in the certificate is at least bits long. Step 4 In the Timeout text box, enter the amount of time in seconds that the TFTP server attempts to download the certificate. Step 5 In the Certificate File Path text box, enter the directory path of the certificate. Step 7 Optional In the Certificate Password text box, enter a password to encrypt the certificate. Step 8 Click Apply to commit your changes.

Step 9 Click Save Configuration to save your changes. PEM-encoded file. Are you sure you want to start? Certificate installed. Please restart the switch reset system to use the new certificate. The CLI allows you to use a VT terminal emulation program to locally or remotely configure, monitor, and control individual controllers and its associated lightweight access points.

The CLI is a simple text-based, tree-structured interface that allows up to five users with Telnet-capable terminal emulation programs to access the controller. If you would like to change either of these values, enter config serial baudrate baudrate and config serial timeout timeout to make your changes. If you enter config serial timeout 0, serial sessions never time out.

Step 4 When prompted, enter a valid username and password to log into the controller. The administrative username and password that you created in the configuration wizard are case sensitive. Note The default username is admin, and the default password is admin. You can change it by entering the config prompt command.

You must use a local connection to the serial port to enable Telnet sessions. Step 3 When prompted, enter a valid username and password to log into the controller. The system prompts you to save any changes you made to the volatile RAM. Note The CLI automatically logs you out without saving any changes after 5 minutes of inactivity. You can set the automatic logout from 0 never log out to minutes using the config serial timeout command. From the root level, you can enter any full command without first navigating to the correct command level.

Table lists commands you use to navigate the CLI and to perform common tasks. View commands available at the current level command? View parameters for a specific command exit Move down one level Ctrl-Z Return from any level to the root level save config At the root level, save configuration changes from active working RAM to nonvolatile RAM NVRAM so they are retained after reboot reset system At the root level, reset the controller without logging out Using the AutoInstall Feature for Controllers Without a Configuration When you boot up a controller that does not have a configuration, the AutoInstall feature can download a configuration file from a TFTP server and then load the configuration onto the controller automatically.

When the controller boots, the AutoInstall process starts. The controller does not take any action until AutoInstall is notified that the configuration wizard has started. If the wizard has not started, the controller has a valid configuration.

If AutoInstall is notified that the configuration wizard has started which means that the controller does not have a configuration , AutoInstall waits for an additional 30 seconds. This time period gives you an opportunity to respond to the first prompt from the configuration wizard: Would you like to terminate autoinstall?

You can abort the AutoInstall task even after this second timeout if you enter Yes at the prompt. However, AutoInstall cannot be aborted if the TFTP task has locked the flash and is in the process of downloading and installing a valid configuration file. The registration of this interface causes AutoInstall to begin the process of obtaining TFTP server information and downloading the configuration file. Each phase of this sequence gives preference to explicitly configured information over default or implied information and to explicit host names over explicit IP addresses.

This file includes the domain name and the list of DNS servers that have been received. If DNS returns a host name, this name truncated at the first period [. If the interface cannot download a configuration file successfully after three attempts, the interface does not attempt further. The first configuration file that is downloaded and installed successfully triggers a reboot of the controller.

After the reboot, the controller runs the newly downloaded configuration. It stops running if it does not find a configuration file after it cycles through this list three times on each registered interface.

Note The downloaded configuration file can be a complete configuration, or it can be a minimal configuration that provides enough information for the controller to be managed by WCS. Full configuration can then be deployed directly from WCS. Note WCS release 5. A WCS administrator can create a filter that includes the host name, the MAC address, or the serial number of the controller and associate a group of templates a configuration group to this filter rule.

WCS pushes the initial configuration to the controller when the controller boots up initially. After the controller is discovered, WCS pushes the templates that are defined in the configuration group. Note Cisco Aironet lightweight access points might not connect to the controller if the date and time are not set properly. Set the current date and time on the controller before allowing the access points to connect to it. Each controller searches for an NTP server and obtains the current time upon reboot and at each user-defined polling interval daily to weekly.

Step 2 In the Timezone area, choose your local time zone from the Location drop-down list. Note You cannot set the time zone delta on the controller GUI.

Step 3 Click Set Timezone to apply your changes. Step 4 In the Date area, choose the current local month and day from the Month and Day drop-down lists, and enter the year in the Year text box. Step 5 In the Time area, choose the current local hour from the Hour drop-down list, and enter the minutes and seconds in the Minutes and Seconds text boxes.

Note If you change the time zone location after setting the date and time, the values in the Time area are updated to reflect the time in the new time zone location. For example, if the controller is currently configured for noon Eastern time and you change the time zone to Pacific time, the time automatically changes to a.

Step 6 Click Set Date and Time to apply your changes. For example, if it is a. GMT Samoa 3. GMT Hawaii 4. GMT Alaska 5. HDX helps optimize performance, mitigation, scalability, and roaming for high-density wireless networks.

This technology allows the access point to support a large number of clients without performance degradation. It offers 80 MHz support and uses silicon-level intelligence to create a self-healing, self-optimizing wireless network that mitigates the effects of wireless interference. It helps access points bridge gaps in coverage caused by mixed client devices It increases access performance and range while providing a better wireless experience.

Clients can roam more intelligently and cleanly between access points. It prevents negative experiences for Wi-Fi users by monitoring the device connection quality and proactively prompting poorly-performing client devices to seek better connections sooner. Cisco Application Visibility and Control AVC solution for wireless networks identifies more than business- or consumer-class applications using deep packet inspection DPI.

With this extraordinary visibility into application traffic, administrators can mark applications for further prioritization, or block them for security reasons or to conserve limited network bandwidth.

AVC offers these benefits:. Proactive monitoring and end-to-end application visibility accelerate troubleshooting and reduce network downtime. Network capacity management and planning improve through greater visibility of application usage and performance. Access points are able to bridge gaps in coverage caused by mixed client devices ClientLink 3. This technology monitors the device connection quality and proactively prompts poorly performing client devices to seek better connections sooner.

Skip to Main content Skip to search Skip to Footer. Wireless Networking Technology Mission-Critical Wireless Strengthen business-focused applications for employees, customers, and communities on the move. Integrated multi-level security policy and enforcement to protect your network and data Consistent policy management and enforcement Single integrated solution to simplify delivery of applications, data, and collaboration services Application visibility and control for improved user experience and security Mobility Services from Cisco and our partners that provide the expertise you need Connected Mobile Experiences Cisco Connected Mobile Experiences CMX is enabled by the Mobility Services Engine MSE , with the CMX license working in coordination with the Cisco Wireless Network.

CMX capabilities of Mobility Services Engine offer: Location-based Wi-Fi analytics for visibility into the number of visitors, their dwell time, and their movements Simple guest access and a customized landing experience Online and social analytics to better understand customer demographics and their mobile behavior An API and SDK to make it easy to create location-based applications and services CMX helps you build a stronger relationship with customers through a more personalized mobile user experience.

Turbo Performance PDF - KB This technology allows the access point to support a large number of clients without performance degradation.