Wireless Mesh Config

Unanswered Question
Nov 19th, 2007
User Badges:

Hi all,

I need to config wireless mesh system.

I have Wireless Control System, Wireless Lan Controller 2100, and access point 1310

Any one can tell me step to config this sys tem.

Thanks all, vote 5* for your help.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
conkinkinconkinkin Tue, 11/20/2007 - 02:55
User Badges:

Hi all,

Thanks bbxie, I voted 5* for your help

I have AIR-BR1310G-A-K9, are you sure this product is not support mesh? Can you show me document to ensure that?

If it not support mesh, can i build wireless network with this access point and wireless lan controller:

- All ap use the same ssid, same security policy

- Roaming between wireless area

Can you tell me step to deploy that?

conkinkinconkinkin Tue, 11/20/2007 - 22:09
User Badges:

Any one can tell me step to config wireless network using accesspoint AIR-BR1310G-A-K9 and Wireless Controller 2100:

- All ap use the same ssid, same security policy

- Roaming between wireless area


n.manlangit Sun, 11/25/2007 - 22:58
User Badges:

1310 is not a lightweight AP,, therefore it will not communicate with the lightweight controller 2100.....

conkinkinconkinkin Mon, 11/26/2007 - 04:20
User Badges:

I configed 1310 in lightweight AP mode, it joined Controller 2100.

Any one know how to config roaming in my case or it is default?


Richard Atkin Mon, 11/26/2007 - 04:21
User Badges:
  • Silver, 250 points or more

Roaming between APs on your WLC is enabled by default.

conkinkinconkinkin Fri, 12/14/2007 - 00:47
User Badges:

Hi all,

I configed wireless system with controller 2100 and AP 1310

Almost the time system run normally, but sometime one of AP 1310 reboot, but other still run normally.

I don't know why, do you have any suggest about this problem?

How to view log all event on this system?

Thanks all for help


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