Different channels seen using show ascp neighbour.

[steven_rous]

Edited text files show apparent mismatch between two APs one the Mesh Portal and the other the Meshed AP.   Note.   I've removed some details and replaced with ...  ?

It would appear that both APs are using Channel 112 for the Wifi1 Backhaul link and when we run a show hive <hive id> neighbour command they apparently are seeing each other on Channel 112.

When however I run the show ascp neighbour command the Mesh Portal apparently is seeing the Meshed AP on Channel 132 and not 112?   I'm wondering whether this is correct or a bug.   And if not a bug how this can be correct.  

[steven_rous]

 Sam,   Thanks for your reply.   Please note the Mesh connection  show is up and working.   I've attached the output requested from both APs in a word document attached.    Note ensure you view this as A3 Landscape if it doesn't automatically open that way!    As you will see from output attached both interfaces are reporting to be working on Channel 112 and this has not been configured using static channels.    We have a total of 15 other similar installations working like this and I've seen the reported mismatch elsewhere on other working Mesh connections too.   Personally I think the output from the show ascp neighbour is wrong and therefore possibly a bug because I don't see how the Mesh Portal can see the Mesh AP on Channel 132 when clearly the neighbors are being seen on channels 112 which matches the output of the show wifi1 also.   I  did wonder about setting static channels to form a mesh connection recently when it took a long time for us to establish a Mesh connection at another site.   I think setting it to static would speed up this process but is not absolutely necessary in order for this to work correctly and I would have thought where possible it is better to allow the APs to dynamically allocate channels and strength rather than try and configure this statically?     The only I'm aware of that hasn't been configured as per documentation is the Eth0 Interface on the Mesh AP which has been configured as Backhaul but it shows as being down anyway because it connects to a  physical POE injector and not a LAN switch.   We are not trying to propagate or bridge VLANs over this link to another switch I think this is fine and not an issue either.  

[samantha_lynn]

Thank you for that data. To begin with, when we deploy Mesh, we need to set static channels on the APs involved in the Mesh chain, so that all devices are sure to use the same channel at all times. Additionally, those commands you ran, the output for those commands is based on data gathered during a background scan, could you run "show int wifi0" and "show int wifi1" and share the results (either here or with me directly at communityhelp@aerohive.com) so we can make sure background scans are going through properly?