mesh and no mes controllers

Unanswered Question
Sep 14th, 2009

Currrently my network is running several wisim for my indoor wireless no mesh solution. with code 4.2.207.0 .

i need a mesh solution for the outside parking lot that will work with

the 1522

now according to the document the options i have is 4.1.192.35M

or Release 5.2.193.0

now i am runnning wcs 4.2.110.0

i would like to keep the same version in the indor ap and perhaps use version

4.1.192.35M for mesh outdoor, according the the readme document its supported to run both version.

has anyone in this forum have both mesh and no mesh controllers?

are they in the same mobility group?

i want to avoid upgrading WCS, as well as the controllers service indor AP.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Lucien Avramov Mon, 09/14/2009 - 18:33

Mesh is supported up to 4.2.176.51M.

4.2.176.51 was release in Jul 1st 2009. You need a WCS version released AFTER Jul 1st 2009 and to be at least 4.2 code.

You need to wait for the next maintenance release of 4.2 or 5.2 or 6.0 code. Soon there should be a maintenance release for 6.0 and that will work with 4.2.176.51M.

You should be able to have mesh and non mesh controllers in the same mobility group, and you can keep 4.1.192.35M if you want.

5.2.193.0 is not a MESH code that I am aware of, as there is no mesh code after 4.2 of my knowledge.

If you want to use 4.1.192.35M Mesh and 4.2.207.0, then you need WC 4.2.128.0. The upgrade from 4.2.110.0 should take you about 10 minutes and will not loose any data, you will need to upgrade your WCS for this scenario to wok as 4.1.192.35M was released AFTER 4.2.110.0 but BEFORE 4.2.128.0

HTH

weterry Mon, 09/14/2009 - 19:51

I can't speak for the WCS questions, but I want to correct a few things here:

The 4.2.176.51M code is intended for only 1500 series Mesh APs, not the 1520's.

In 4.1, Mesh features were combined with the normal controller. In order to progress with 4.2 development, they took out Mesh and split the trains (hince 4.1.192.35M).

However, in 5.2 and 6.0, they have combined the trains again. So you can infact get your 1522s up and running in 5.2.193.0.

My question to you however, is there any particular reason why you are leaving indoor wireless at 4.2? Do you have 1000 Series Airespace equipment holding you back, or are you just comfortable at 4.2?

I've seen mobility defined between the 4.2 and 4.1M code, as well, 4.2-6.0 should be able to have mobility.

Lucien Avramov Mon, 09/14/2009 - 19:58

1520s are supported in 5.2 onwards and 1510s will continue to be supported on Maintenance Releases of 4.2.

ggittins Tue, 09/15/2009 - 03:45

so you are telling me that controllers

running 4.2 and 6.0 can have the same mobility group? will this affect the

APs? since some are at code 4.2

and they might register to a higher code controller

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