Wireless Access

Reply
Frequent Contributor II

mesh link unstable

I have a lab with a 7205 controller, AP277 configured as a mesh portal, and AP275 configured as mesh point. All are connected to a S2500 switch to provide a proof of concept to customer. However I cannot get the link to remain up. After a couple of hours the link drops. I have seen the following in the log of the point-

Reboot Information
------------------
AP rebooted Fri Sep 25 11:44:26 GMT 2015; Mesh link could not be sustained for 15 minutes.
------------------------------------------------------------------------------------------

 

 

Around 15 mins before this the portal shows -

[2079]2015-09-25 11:32:19.956: Preserving Recovery PSK.Generating PSK from Passphrase
[2079]2015-09-25 11:32:19.956: SSID - hexdump_ascii(len=7):
     50 65 65 6c 50 4f 43                              PeelPOC
[2079]2015-09-25 11:32:19.956: PSK (ASCII passphrase) - hexdump_ascii(len=13):
     70 33 33 6c 70 30 72 74 35 6b 33 79 21            p33lp0rt5k3y!
[2079]2015-09-25 11:32:20.168: PSK (from passphrase) - hexdump(len=32): 4c f5 ef e8 f9 d2 8e 06 82 aa c7 c6 98 2f 7c c6 10 2b e8 27 59 8d b8 b3 06 85 73 ba e3 28 85 b1
[2079]2015-09-25 11:33:51.778: RX ctrl_iface - hexdump_ascii(len=25):
     44 45 4c 5f 53 54 41 20 39 34 3a 62 34 3a 30 66   DEL_STA 94:b4:0f
     3a 32 65 3a 66 61 3a 33 30                        :2e:fa:30
[2079]2015-09-25 11:33:51.778: CTRL_IFACE DEL_STA 94:b4:0f:2e:fa:30
[2079]2015-09-25 11:33:51.779: WPA: 94:b4:0f:2e:fa:30 WPA_PTK entering state DISCONNECTED
[2079]2015-09-25 11:33:51.779: WPA: 94:b4:0f:2e:fa:30 WPA_PTK entering state INITIALIZE
[2079]2015-09-25 11:46:44.980: RX ctrl_iface - hexdump_ascii(len=70):
     4e 45 57 5f 53 54 41 20 39 34 3a 62 34 3a 30 66   NEW_STA 94:b4:0f
     3a 32 65 3a 66 61 3a 33 30 20 33 30 31 34 30 31   :2e:fa:30 301401
     30 30 30 30 30 46 41 43 30 34 30 31 30 30 30 30   00000FAC04010000
     30 46 41 43 30 34 30 31 30 30 30 30 30 46 41 43   0FAC040100000FAC
     30 32 30 30 30 30  

 

Tech support files attached if anyone can figure out why the link went down or the Point decide to rebootstrap.

Guru Elite

Re: mesh link unstable

You should give us the "show ap mesh tech-support ap-name <name of ap>" before the reboot.  It yields much more info. 

 

- How far apart are the access points?

- What version of ArubaOS are you using?  (I assume 6.4.3.3)



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Frequent Contributor II

Re: mesh link unstable

The access points are on a bench in the lab - so not far apart. Correct, they are running 6.4.3.3.

Attached are the mesh tech-support files in case it rebootstraps again.

Guru Elite

Re: mesh link unstable

I would try using a non dfs channel. Check to see in "show log wireless" if there was a radar event. They should be at least 3 meters apart or even further if possible.


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Frequent Contributor II

Re: mesh link unstable

There does not seem to be any RADAR events around this time -

Sep 25 11:32:19 :404085:  <WARN> |AP Portal:ca:cd:e0@10.2.52.20 sapd|  AM 94:b4:0f:2c:de:10: ARM HT Channel Interference Trigger new 116E/56 old 100E/128 new_rra 116E/3 TCI 10
Sep 25 11:32:19 :400180:  <WARN> |stm|  handle_ap_message_response: BSS 94:b4:0f:2c:de:12 nothing outstanding

 

Would a channel change cause the AP to rebootstrap?

This message still owriies me though -

Reboot Information
------------------
AP rebooted Fri Sep 25 11:44:26 GMT 2015; Mesh link could not be sustained for 15 minutes.
------------------------------------------------------------------------------------------

does this mean that the link repeatedly dropped before 15mins was reached or does it mean that the link went down and could not be re-established for 15 mins - the latter seems to be the case.

The distance on the bench should not matter, unless this is peculiar to Aruba - I've done a million tests with other devices (Cisco mostly) without issue.

Re: mesh link unstable

Crazily enough, you need to get more separation between the portal and point if this is on a bench. The radios are power enough and the receivers sensitive enough, that you can 'overdrive' the radios which can cause stability and performance issues. Your RSSI is WELL above 50, which is too high, so you need less power (try setting power to zero) and/or more distance or some kind of attenuation between them. Give that a shot, but what you are seeing is very common so we need to rule that out (the APs being to close and the radios being over-driven). Good luck!

Jerrod Howard
Sr. Techical Marketing Engineer
Frequent Contributor II

Re: mesh link unstable

I have reprovisioned the devices and its taken 13 mins for the point to request an IP address and come back on to the controller. I understand the radios come up first, but should I set static IP addresses on the devices?

Re: mesh link unstable

You would only want to do static IPs if the DHCP server is slow or not present. 13min is obviously far too long. Let us know what happens when you set power to 0 (they will still have some intrinsic EIRP due to the antennas and the fact that the radio can't REALLY run at 0dBm per chain heh). 

 

Just drop the power to zero and get as much separation as you can. Put them in separate rooms if you can, but same room setups are notoriously bad (which of course make benching configs a PITA, but it's a good problem to have the when radios work so well). 

Jerrod Howard
Sr. Techical Marketing Engineer

Re: mesh link unstable

Also, and this is likely part of why you are seeing issues, make sure they are both provisioned for outdoor or auto, and then make sure the portal stays off the DFS. 277 DFS testing IS NOT complete yet so I don'e belive it will join a portal if the 275 is within DFS.

 

Some quick background color because it's a pain...

 

FCC changed the rules on how and what outdoor devices can certify on. Previously, 'outdoor' access points were never allowed to run in the indoor UNI1 space. The 274/275 certified under the old rules, which means it is fully compliant with the Outdoor and DFS channels but CANNOT run un the UNI1 indoor 5GHz channels. They then changed the rules and allowed 'outdoor' access points to run on the indoor UNI1 channels under certain conditions and requirements. Since the 277 is newer, we submitted it for indoor, DFS, and outdoor. However it has not FULLY completed DFS certification, but IS allowed to run on UNI1 and Outdoor non-DFS channels without issue. The 274/275 is ALSO being re-certified under the new rules so that WHEN IT'S ALL SAID AND DONE, the 27x and 228 family can run the entire 5GHz spectrum, but for now we're in this weird limbo between the older 274/275 and the newer 277/228.

 

TL;DR:

274, 275 - DOES NOT support indoor 5Ghz channels, but IS certified for Outdoor UNI3 and DFS. Has been re-submitted for testing to add support for indoor.

277, 228 - DOES supprot indoor 5GHz channels, as well as Outdoor UNI3, but is NOT YET certified for DFS (is pending and should be very soon upon which we will release a DRT). Is current near completion on testing to add DFS (DFS certification just takes longer to accomplish). 

 

Sorry for the confusion, stick your 275 static on 149E for now, drop the power and add some separation to get the RSSI of the mesh link in the 40s, It should then be very stable.

Jerrod Howard
Sr. Techical Marketing Engineer
Frequent Contributor II

Re: mesh link unstable

Appreciate the info, however we are not regulated by the FCC - how does this affect operations for ETSI? Channel 149 is not available here.

The device has now failed to re-connect to the controller even though it has a hard wired link available.

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: