WLSE

Unanswered Question
Nov 5th, 2007

Wireless Lan Controllers, use the LWAPP protocol for the comunication with the lighweigh access point. And the access point usan the option 43 of the DCHCP server to find el WLC. How the WLSE works with the access points? What protocol use WLSE for the comunication with the access points?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
rob.huffman Mon, 11/05/2007 - 07:39

Hi Ricardo,

Q. What ports and protocols does the WLSE use?

A. For discovery and fault monitoring, the WLSE primarily uses SNMP (UDP port 161). For applying configuration changes, the WLSE uses SNMP, HTTP (TCP port 80 or as configured), and TFTP (UDP port 69).

Q. How do configuration files get transferred to access points?

A. Even though access points support both TFTP and FTP, the WLSE uses only TFTP to upload and download configuration files.

http://www.cisco.com/en/US/docs/wireless/wlse/1.1/user/guide/faqs.html

Hope this helps!

Rob

ricardorojas123 Mon, 11/05/2007 - 12:46

Rob, I have another dude the lighweight access points, througth 43 option DHCP they can reach the Wireless Lan Controllers, but the autonomous access points, How Can to reach its WLSE?

rob.huffman Mon, 11/05/2007 - 13:52

Hi Ricardo,

Here are the two methods;

Deployment Wizard

The Deployment Wizard replaces many of the manual configuration procedures that are normally required to configure infrastructure access points and WDS devices and to configure the WLSE to discover and manage those devices.

Specifically, the Deployment Wizard helps you configure a Wireless LAN (WLAN) using the Cisco Structured Wireless-Aware Network (SWAN) framework. (For additional information on SWAN, see the Cisco Structured Wireless-Aware Implementation Guide on Cisco.com.) The wizard creates basic configurations for access points (APs) that can be deployed to existing devices managed by WLSE or deployed to devices that are added later. The wizard also configures WDS devices.

Besides configuring the devices to be managed by the WLSE, the Wizard enters the necessary device credentials on the WLSE and places devices in the managed state.

Newly-installed devices require basic configuration in order to be managed by the WLSE. The basic configurations created by the Wizard can be applied only to devices that are supported by the WLSE. Configurations are downloaded to devices when the devices power up and are deployed according to criteria that you set in the Wizard.

The SWAN framework for WLANs relies on the presence of Wireless Domain Services (WDS).

When you install a new AP device in the network using the Deployment Wizard, the following occurs:

1. The newly powered on device contacts the DHCP server to provide an IP address.

2. The device downloads the wlsestartup.ini file, which contains only minimal credentials and a command to Telnet to the WLSE.

3. The WLSE then discovers the device, adds it to inventory, manages it, and downloads a configuration template to it via SSH.

This template contains user-specified credentials (entered in the Wizard Configuration step), which overwrite the existing minimal credentials that were uploaded in the wlsestartup.ini file. The template also contains security information.

From this doc;

http://www.cisco.com/en/US/docs/wireless/wlse/2.13/user/guide/deploywz.html#wpxref52603

Or you can use the Manual Methods

If you do not use the Deployment Wizard, you can use the configuration methods methods described in the following paragraphs.

Before you can use the WLSE to manage newly added devices, the following tasks must be performed:

Configure the devices

Configure the WLSE

Discover the devices

Move the devices to the managed state

(Optional) set up your own device groupings to make management easier.

http://www.cisco.com/en/US/docs/wireless/wlse/2.13/user/guide/devices.html#wp1989925

Hope this helps!

Rob

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode