1510 Mesh AP Secondary Backhaul question

Answered Question
Nov 11th, 2007
User Badges:

Our outdoor 1510 APs are currently a bit too far apart in some cases. Although I am currently planning fill-in nodes, I want to get something working on these nodes that are too far to mesh on 5.8.


I have enabled secondary backhaul on the system, and was expecting performance similar to what I am used to on other mesh systems that mesh on 2.4. However I saw no improvement at all. I can't even find any statistics on the usage (if any) of 2.4. At the moment, I am pretty disappointed.


It is almost like the feature doesn't work. I'm on 4.1.185.0 and am just a bit reluctant to switch to the mesh-only firmware until I hear some reports from actual users.


Does this feature even work? Is there anything else I must do besides turn on the feature from the CLI?


Thanks


Correct Answer by drolemc about 9 years 6 months ago

This feature works well in my setup. Can you post the configuration from the mesh AP so that we can troubleshoot the issue?

You can also try using the mesh only firmware and check if it works.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Correct Answer
drolemc Fri, 11/16/2007 - 06:48
User Badges:
  • Silver, 250 points or more

This feature works well in my setup. Can you post the configuration from the mesh AP so that we can troubleshoot the issue?

You can also try using the mesh only firmware and check if it works.

ralphfowler Fri, 11/16/2007 - 07:09
User Badges:

Hey! Thanks for the info.

I have moved to the mesh firmware and the latest WCS since I posted this question. I received some info from the TAC as well, but always want to know from someone who actually has it working.


The commands I was given were:


config mesh secondary-backhaul enable (manual mode)

config mesh secondary-backhaul enable force-same-secondary-ch (force mode)

show mesh seconday-backhaul

show mesh secbh-stats Will show you if the seconday is being used



I'm not sure if the first two are either/or though, and also what the second one actually does.


They also told me that RRM has to be disabled and the two radios have to be on the same B channel. That's a lot of management to have to do. I would have expected the B channels to listen ank know who and where their neighbors are and be able to handle this. If this is the case, I sure hope improvements are in the offing!


I'll try to get the config posted, but in the meantiime please let me know any insight you have on getting it TO work. The person I spoke with at TAC had never actually talked to anyone with it working.

ralphfowler Sun, 01/27/2008 - 05:45
User Badges:

Hi MH and thanks for the pointer to that Document.


It was about time I updayed y'all on this issue anyway, so here goes.


The feature does work now, although it didn't work until mesh release #2, as far as I can tell. Once I upgraded to that release, my WCS alarms started showing activity on the secondary backhaul. As a matter of fact- I currently see over 40,000 events of the use of secondary backhaul.


I found out a couple of weeks ago from some Cisco folks when I was out in SanJose that the feature switched on to the secondary backhaul almost on a per packet basis. Although it works for routing around interference, that is useless for what I wanted. If you recall,

I was wanting to permanantly use the 2.4 as backhaul in certain areas- essentially converting the radio to work like a 1505 (or a Tropos 5210).


Looks like that can't happen, but the Cisco folks listened and said they will consider it in the future.


Thanks for the input, everyone!


Ralph

ralphfowler Sun, 01/27/2008 - 05:47
User Badges:

And one final thing- If Cisco is reading this- I believe the document MH quoted has a typographical error in it.


You have titled the section "Routing around an Interface". I believe everywhere else this is referred to as "Routing around Interference".

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