Instant On - Wireless

Expand all | Collapse all

Problem AP22 and 2.3.1

  • 1.  Problem AP22 and 2.3.1

    Posted 07-12-2021 04:41 PM
    Having major problems with 2.3.1.  Macbooks seem to have an issue where they are connected just fine, but can't contact their gateway on occasion.  If I get 2 pings going, one to a local server, and one out to the internet, the one to the local server doesn't drop. However the one out to the internet will drop for maybe 20-30 times in a row and the magically come back. 

    These are 3 AP22s connects to a 1930 switch, with a SonicWall as a gateway. I have confirmed the SonicWall isn't blocking anything.  The same Macbooks I can connect to the ISP provided wifi with 0 issues. So it's nothing like that. 

    I don't know, these AP22s have been solid, and now they are just flaking out everywhere even though they are up to date and I've rebooted them.  I'm always at max signal on the macbooks. Real worlds transfer speeds are above 300mbps. They just suddenly can't communicate with the gateway, yet an iphone right next to it, connected to the same SSID, is sitting there running speed tests without any drops, all while the macbook can't get to the gateway.

    I've turned off Wifi6.  Not sure what else to check.


  • 2.  RE: Problem AP22 and 2.3.1

    Posted 07-13-2021 10:24 AM
    Hi,

    can you confirm that turning off WiFi6 knob helped resolving the issue?
    Also, if you can confirm your MacOS version and Macbook type that'll be appreciated.

    Thanks,

    ------------------------------
    Jul.
    ------------------------------



  • 3.  RE: Problem AP22 and 2.3.1

    Posted 07-13-2021 10:36 AM
    2018 Macbook Pro.  Fully up to date Big Sur.  Turning off WiFi6 had no effect.

    I'm still testing, but so far it seems to only happen on an SSID that has both 2.4 and 5Ghz enabled. Last night I tested on an SSID with only 5Ghz, with WiFi6 ON and optimize for video streaming ON and it didn't drop at all. I'm back on a combined SSID now to verify issue returns.  If it does, next I will try 2.4Ghz only to see how that is.

    Thanks,

    Rob


  • 4.  RE: Problem AP22 and 2.3.1

    Posted 07-13-2021 01:10 PM
    I can now confirm that the problem exists on SSIDs with both 2.4Ghz and 5Ghz enabled. Leaving all other settings the same, simply removing 2.4Ghz from the SSID resolves the issue.  Soon I will test with 2.4Ghz only to see if that has the same issue as the combined.


  • 5.  RE: Problem AP22 and 2.3.1

    Posted 08-09-2021 09:35 AM
    Just adding this is still going on. I even added a 4th AP22 to rule out a hardware problem and while connected to it the problem happens. The problem doesn't happen while connected to AT&Ts provided Harris CPE. 

    It also happens on all bands, it's not isolated to 2.4Ghz. Even on a 5Ghz only SSID, with Wifi6 and media optimizations disabled, it still happens, just not as frequently.  It's obvious streaming something like HBOMax which tends not to buffer as much. You'll be watching and then it suddenly stops and says can't connect. I look at my pings and sure enough, pings to a local server are fine, but pings out the gateway drop. I can't even ping the local gateway (SonicWall) itself during this so it's not an internet problem. This persists for perhaps 15 seconds then resumes and is fine again for a couple hours usually before it happens again. idk, something is definitely wrong. It doesn't happen on wired connections. It doesn't happen connecting with WiFi to the AT&T CPE. It only happens while connected to AP22s.


  • 6.  RE: Problem AP22 and 2.3.1

    Posted 08-12-2021 11:39 AM

    Interesting (and frustrating) problem! 

    You initially said this was only affecting MacBooks, while iPhones were okay. Does that still hold true, or have you discovered otherwise? 



    ------------------------------
    Ethan
    ------------------------------



  • 7.  RE: Problem AP22 and 2.3.1

    Posted 08-12-2021 04:03 PM
    The problem is that it's hard to test. It can go several hours with no issue then it hits. The MacBook is used heavily for streaming video so it's obvious when it happens. None of the other devices are used in such a way where they could easily detect a drop. When the drop happens, it's usually for about 45 seconds. Enough to stop streams.  I haven't noticed it on other devices, but I can't rule it out either.


  • 8.  RE: Problem AP22 and 2.3.1

    Posted 08-12-2021 04:11 PM

    Ugh. These types of issues are tough to diagnose if you can't be onsite and don't have remote monitoring. 

    We've been seeing similar issues with our provider here in Western Canada, who uses the same equipment as Comcast. It's their modem/routers (XB6&7) that are having the issues. 

    Have you double checked to be sure there's no accidental QOS / Application blocking or similar settings in the router and APs that might be choking the video feeds? Don’t forget that with an errant click you can neuter application & traffic types.

    Again - is it only Video streams that are affected? 

    Are you familiar with Wireshark? It would be interesting to fire it up when there’s an issues to see what the frames and packets are doing. 

    ------------------------------
    Ethan
    ------------------------------



  • 9.  RE: Problem AP22 and 2.3.1

    Posted 08-12-2021 04:22 PM
    Yes I'm familiar with WireShark, it's hard to get the timing though. I would have to sit and sit waiting.  There's no QoS or bandwidth mgmt in use. It's a synchronous 1Gbps circuit. I leave 3 pings running on the MacBook.

    1 to local gateway (sonicwall)
    1 to 8.8.8.8
    1 to a local server

    During the event. The last one, to a local server in the same subnet, that never drops. It's always fine. During the event, all pings to the local gateway, and then obviously out to the internet from there, fail. Even with QoS or BWM, it still wouldn't drop all pings for 45 seconds to the local gateway.


  • 10.  RE: Problem AP22 and 2.3.1

    Posted 08-12-2021 04:29 PM

    All three pings are being transmitted over wifi?
    If so, I don’t think you have a wifi issue, you have a routing issue. Do you have another router you can drop in place of the sonic wall?

    ------------------------------
    Ethan
    ------------------------------



  • 11.  RE: Problem AP22 and 2.3.1

    Posted 08-12-2021 06:39 PM
    Yes all 3 pings are being transmitted over wifi. The macbook is not wired up, it's only wifi. However, I disagree with the routing problem assessment. The SonicWall I had was a TZ400 and I had the problem. I recently replaced it with a newer TZ470 and still have the problem. There are no other routers.  All 4 APs connect to an Aruba 1930 switch which uplinks to the SonicWall. All other wired devices on the same 1930 switch have no issues, ever. It's a flat network, no subnets or VLANs. It's not the Macbook itself, as the problem never, not even once happens, while I'm connected to directly to the ISP CPEs wifi. It only happens while connected to these Aruba AP22s. It also never happened before. One of the recent updates is when it triggered.


  • 12.  RE: Problem AP22 and 2.3.1

    Posted 08-13-2021 02:17 AM

    You have me worried now. I'm going to pull an AP22 off the shelf and start testing. Better that we discover an issue in the lab instead of a client's in-production network. 

    If I can replicate the issue I'll report back. 

    Just thinking: The ping to your local server is over layer 2. It never drops, right? It's only the layer 3 pings & traffic that are dying. Doesn't that squarely point back to the router? WiFi only exists in layers 1&2. If the wifi was the problem, why aren’t your pings to the local server also dying? They’re literally running over the same layer 2 network.

    We know traffic is flowing most of the time - so what could be intermittently disrupting / corrupting traffic? 



    ------------------------------
    Ethan
    ------------------------------



  • 13.  RE: Problem AP22 and 2.3.1

    Posted 08-13-2021 08:00 AM
    The gateway itself is also responding at layer 2. Pings to the gateway fail. Now the ping out to 8.8.8.8 would be operating at layer 3. 

    Client IP:  192.168.1.50
    Gateway: 192.168.1.254
    Local server: 192.168.1.10

    Pings from that client, to either the gateway or local server operate at layer 2 only.  There is no routing in this scenario, it's all layer 2.  The only time layer 3 routing is involved is when I'm pinging 8.8.8.8.

    So if a ping fails to 192.168.1.254, and not to 192.168.1.10, that has nothing to do with routing, and everything to do with the APs.  That's why I disagreed with the routing issue assessment.

    I'll add that by this point, I'm using a new SonicWall and a new AP22 in the location. So neither of those are the culprit in terms of possible faulty hardware. The only other item that hasn't been replaced is the 1930 switch, but wired clients on it never have an issue, so I don't believe it is the culprit.

    What's interrupting traffic is a bug with the APs.


  • 14.  RE: Problem AP22 and 2.3.1

    Posted 29 days ago
    If ping to local server 192.168.1.10, then I think it is not wifi issue. If you have same result when ping to gateway and local server, then it will be wifi issue

    ------------------------------
    DENNY .
    ------------------------------



  • 15.  RE: Problem AP22 and 2.3.1

    Posted 23 days ago
    I am sorry but that's just not true. I have witnessed similar bugs on other deployments with different gear. The local gateway is the same thing as a local server. So I completely disgree with that assessment.

    I also have more notes now.

    1. The issue affects all devices. Not just Macbooks. It I have verified that Apple TVs, Macbook Pros, Macbook Airs, and a Windows Laptop all have the issue.
    2. It's not DHCP Renewal related. The issues happens even when statically assigned.
    3. I've maually channelized the network, dropping 40Mhz wide channels instead of 80, and avoiding all DFS channels. The issue still happens.

    So I'm at a loss now. This wasn't there with previous firmware.  

    Pings are consistent as well.  After running overnight:

    Pings to local server 0.5% loss
    Pings to Gateway 1% loss
    Pings to Internet 1.5% loss.

    So the loss is only 1% to the gateway but what sucks is almost all of that loss is in a chunk of 60 dropped packets in a row which breaks connections, streams, VPNs.  This happens I would say on average about once per hour to all clients connected to these 4 AP22s.  None of this is witnessed when just connecting to the ISPs Harris device.

    New firewall, new APs, none of that solved it.  All other wired machines on the same 1930 switch can ping the gateway all night long without a single dropped packet. So it isn't the wired network either. All 4 AP22s are home run to the 1930. No mesh is in use. One of these recent firmware updates triggered this.


  • 16.  RE: Problem AP22 and 2.3.1

    Posted 23 days ago
    Oh and when it happens, it happens simultaneously to all clients. At least all clients on the same AP.  I need to do some more testing simultaneously from multiple APs to see if it syncs up with all APs, or if it happens individually per AP, affecting only those clients on that AP.  I know for fact that at a minimum, when it happens to 1 AP, it affects all clients at the same time, in the same way, who are associated with that AP.


  • 17.  RE: Problem AP22 and 2.3.1

    Posted 21 days ago
    What SonicWALL firmware are you using?

    ------------------------------
    Stephan Gladiadis
    ------------------------------



  • 18.  RE: Problem AP22 and 2.3.1

    Posted 20 days ago
    SonicOS 7.0.0-R906 on a TZ470.  But the problem started before I swapped out the older TZ400 that had different firmware. So I don't think it's SonicWall related at all for several reasons.

    1. The SonicWall was upgraded with a new device and new firmware, didn't fix this issue.
    2. There is never an issue on the wired network. You can ping the SonicWall at 0% loss all day from any wired endpoint including endpoints on the same 1930 switch as the AP22s.
    3. It's a flat network with a single subnet and no VLANs.
    4. There are never any issues listed in the SonicWall logs that could even remotely be related to this.



  • 19.  RE: Problem AP22 and 2.3.1

    Posted 23 days ago

    Thanks for the additional details. 

    We've been on vacation and unable to test this is the lab, but it's going to be one of the first priorities once we return. 


    I’m assuming no one from Aruba responds to these forums? Have you opened a ticket with support? 



    ------------------------------
    Ethan
    ------------------------------



  • 20.  RE: Problem AP22 and 2.3.1

    Posted 19 days ago
    Hi,

    We want to assist you in getting this issue resolved. We request you create a support ticket with our Aruba Instant On support team and include setup, all client issues seen, and any additional concerns relating to the issue. This will help our team assist you in narrowing down and resolving the issue. You can reach us at: https://www.arubainstanton.com/contact-support/


    ------------------------------
    Aruba Instant On Communications
    ------------------------------



  • 21.  RE: Problem AP22 and 2.3.1

    Posted 18 days ago
    Hi,

    I am dealing with a similar behavior here. I have 3x AP22 running, with an Aruba 1930 and a Ubiquiti EdgeRouter 4.... I am using my MacBook Air 2020 to stream using AirPlay2 over an Apple TV 4 HD. No matter what I do, it is always have dropping at an intermittent amount of time... 5 min, 1 hour.... no specific time.

    This is really frustrating. I am using this Airplay2 streaming as my 2nd monitor, and the streaming is dropping quite many times per day. I carefully followed Apple advices on how to choose right WiFi settings: channels, bandwidth, etc.

    Not much luck so far.

    I re-tested with my old all-in one wifi-router from Synology RT-2600AC alone... nothing else.... everything is stable, no issue at all. The reason I changed everything here is to let me have a better WiFi coverage.

    I am seriously considering dropping all my Aruba gears for another vendor.

    Jeff

    ------------------------------
    ====
    Jeff | VA2SS
    ------------------------------



  • 22.  RE: Problem AP22 and 2.3.1

    Posted 18 days ago
    That sounds identical to what I am dealing with. It wasn't always like this though, a recent firmware update caused it.  I am currently on the phone with Aruba creating a case. For me, the lengthy drops could be anywhere from 15 to 60 seconds long, and can happen anywhere from 1-4 times per hour.  I haven't been able to find a pattern to it. But I know it's not specific to the AP as I have 4 of them and they all have the issue.

    I wouldn't drop them yet. I think this is just a bug for now. I came from Ubiquiti to these and these were night and day better than Ubiquiti a first, but now the firmware updates broke them a bit.


  • 23.  RE: Problem AP22 and 2.3.1

    Posted 18 days ago
    I'm glad we have corroboration on the issue! It sounds like the team at Aruba are listening, so let's hope they flesh out the bug and get things back on track!

    ------------------------------
    Ethan
    ------------------------------



  • 24.  RE: Problem AP22 and 2.3.1

    Posted 18 days ago
    So far, my work around is not very gracious..... I brought back to life my old Apple AirPort Extreme wifi-router. I created a new and exclusive 5 Ghz wifi SSID... 2.4 Ghz disabled. The 5G network is running only on 1 band that I now use with my Apple TV 4 HD exclusively... for now. I also disabled the band I am using on Aruba network to avoid conflict.

    I left my MacBook Air on Aruba WiFi network to test this out. If things are not getting better, my next step would be to move the MacBook Air also on the same 5G network SSID as the Apple TV 4 HD. Problem still persist.  UPDATED

    UPDATED : Both MacBook Air and Apple TV 4 HD are now on the same 5G network using Apple AirPort Extreme router to avoid dropout.

    It was working with my old Synology too.... But I want to try also with older gears too. 

    It is indeed IMHO related to the use of Aruba AP. 

    Regards.

    ------------------------------
    ====
    Jeff | VA2SS
    ------------------------------



  • 25.  RE: Problem AP22 and 2.3.1

    Posted 18 days ago
    Hi,

    Could someone corroborate this behavior?

    I have 1 SSID only using both 2.4 and 5 bands. The global radio settings is set to use power, for both bands, from low to high... not very high or max..... not more than HIGH period.

    From Aruba portal, I can also confirm that I did not override any radio settings for all 3 AP22.... the override checkbox for specific settings for each AP is not checked for all AP22.

    But if I take a look at each AP22 status to check which power level they are dynamically using.... I have one AP that power is set momentarily to MAXIMUM and another one to VERY HIGH.

    So my understanding is even with global radio settings threshold is set to use power level between LOW and HIGH not much, it does not seems to work at all ????

    Am I the only one?

    Regards.

    ------------------------------
    ====
    Jeff | VA2SS
    ------------------------------



  • 26.  RE: Problem AP22 and 2.3.1

    Posted 18 days ago

    I have only experimented with a few APs' power settings, but found we had very inconsistent performance when the power was set to variable or anything less than High. Not just a small dip in performance, but a drastic reduction in throughput. 

    Have you opened a ticket w/Aruba, Jeff? 



    ------------------------------
    Ethan
    ------------------------------



  • 27.  RE: Problem AP22 and 2.3.1

    Posted 18 days ago
    Hi Ethan

    No, I did not open a case yet. I brought this issue to their attention back in July and received a few tweaks to make it work, such as using less 5G bands, etc... but that do not solved my problem. At that time, I gave up unless I found something relevant to tell them. Going forward, if they do not provide me real explanation.... I am not loosing my time.

    Like I said, I have 3 AP22.... They are all running at AVERAGE power level. But one of them is running at VERY HIGH power on 2.4 and the other one is running at MAXIMUM power on 5G band only. So far, signal/speed level are all green (good) if I refer to the dashboard. I understand that they manage their dynamic power output properly and I have so far no other issue as well.

    But my concern is "Why VERY HIGH power and MAXIMUM power are set when I asked to not go beyond HIGH only ???

    Regards,

    ------------------------------
    ====
    Jeff | VA2SS
    ------------------------------



  • 28.  RE: Problem AP22 and 2.3.1

    Posted 8 days ago
    What are their dBm levels?  When I change mine the names may still say very high or max but their stated dBm value is lower.  Also there are two places to change those setting which is odd.  On the individual AP page on the bottom under radio management and then again on the inventory page under the three dot menu theirs another radio management which you would thinks changes all the APs whereas on the actual individual AP page you would think that would change just that AP but the one on the inventory page doesn't seem to change the individual pages.


  • 29.  RE: Problem AP22 and 2.3.1

    Posted 7 days ago
    Hi,

    I can't tell. Since my last post, I did a wifi site survey to determine a different channel for each AP on both 2.4 and 5. Then I manually setup each AP with their own channel and power level. Power level is now set MIN = MAX... same for both. So power level is always the same now. I do not let AP manage channel and power now by themselves; to many times I saw 2 AP running on the same channel.

    I still can't stream using Airplay from my MacBook Air 2020 to my Apple TV 4 HD without having disruption over time. It is frustrating..... but I cannot be sure at 100% it is related to a WiFi issue.... Airplay is always using WiFi, even if the Apple TV is wired. I will wait for a next major Apple Mac OS release soon to check if the issue still occur.

    Unless my Airplay issue, my network is very efficient and stable.

    Regard.

    ------------------------------
    ====
    Jeff | VA2SS
    ------------------------------



  • 30.  RE: Problem AP22 and 2.3.1

    Posted 3 days ago
    Just as an update, I opened a case a couple weeks ago. I have been testing the living hell out of this.  Aruba support felt it might be the 1930 switch causing an issue, so they moved it to local config mode, and made changes to LLDP. However, that didn't fix anything. They have reviewed everything and can't find an issue. I just got an update that they are escalating this to engineering.  

    So we aren't sure yet if it's the 1930 switch, or the APs.  All APs are connected directly to this 1930 switch. Wired clients on the 1930 switch have no issues ever and can ping the local gateway all night long and not drop a single packet. Wireless clients connected to AP22s, that are subsequently connected to the 1930 switch have this issue where they may drop as many as 80 pings in a row to the local gateway, often several times per hour, all while also still being able to ping a local server. It's really bizarre how they are denied access to only the local gateway, and subsequently the internet, but not other hosts. Again, wired clients on the 1930 switch never ever drop to the local gateway.

    Does anyone else have AP22s connected to a 1930 switch? If so, could you do some extended pings to your local firewall and see if the issue can be reproduced?  I think I might take one of my AP22s, and connect it separately to a different switch to see if it's the 1930 causing it, or the APs.


  • 31.  RE: Problem AP22 and 2.3.1

    Posted 3 days ago
    Progress! When removing an AP22 from the 1930 switch, and connecting it instead to the upstream switch, the problem is resolved for anyone connecting to that AP. I just went 12 hours without the problem happening once whereas before, it would happen several times per hour.
    So the problem isn't isolated to the AP22s, it's somehow a combo problem when an AP22 is directly attached to the 1930 switch. Other wired clients on the 1930 switch still never have an issue. It's only when connecting via AP22, and only if that AP22 is connected to this 1930 switch. So the 1930 switch works perfectly, for anything other than an AP22. The AP22 works perfectly, as long as it isn't attached to the 1930. But put an AP22 on a 1930 and things break.
    Today I am going to try the reverse, and put a PoE unmanaged switch downstream of the 1930 switch and connect the APs to it, with the unmanaged switch uplinked to the 1930. 
    But it does appear to be some type of negotiation issue between AP22s and the 1930 switch.



  • 32.  RE: Problem AP22 and 2.3.1

    Posted 3 days ago
    Hi,

    I am using a 8 port Aruba 1930 switch too. From the beginning, I decided to manage locally the switch instead using the cloud.... much more accessible features that are not covered when cloud managed..... Even ports problem counter is not available when using cloud management.... :-( :-(

    So far, I tried to ping my local gateway over wifi , from my laptop to another device on my network. There is a few miss (packet loss) less than 1% on a 1000 ping test. But what brought to my attention is the latency for the ICMP packet reported between my laptop for both gateway and other devices running on my network. On a test with 1000 packets sent... an average latency from 10 to 20 ms..... seems high on a « not busy at all almost sleeping network ». :-)

    ** At the time I did my test, I was using less than 500 kb bandwidth overall on my network. I have only 1 laptop running, else are IoT or tablets and phone. Network almost idle *** 

    If I do the same test from every AP to the 1930 using wired network, or from the gateway to the 1930 (wired network too).... normal report... less than 5 ms... most of the time near 1-3 ms every time. Latency seems well on target for such devices.

    So ....

    from my laptop (over wifi) and the gateway OR from my laptop (over wifi) a MacBook Air 2020 to any network device = average reported time 10-20ms with 1000 packets sent
    from laptop (over wifi) to 1930 switch = same result as above

    But ...

    from the wired AP to Gateway or from wired AP to 1930 switch = average reported between 1-3ms,

    So the WiFi is adding an additional 10-15 ms latency between the laptop and everything pinged on my network. It should be less than 5ms. Wow!!! And like I said, when pinging over wifi.... I also have an average of  0.3%  - 0.5% packet loss. NO packet loss when ping from wired devices. 

    Why I am having much latency added over wifi ??? Don't know yet.

    Regards,

    ------------------------------
    ====
    Jeff | VA2SS
    ------------------------------



  • 33.  RE: Problem AP22 and 2.3.1

    Posted 3 days ago
    Jeff see my post above. Can you try moving an AP22 off of the 1930 switch in some manner and see if the problem is resolved for guests on that AP? Just hook it up to some other PoE switch, or any switch and use a PoE adapter. My problems disappeared when I moved the AP22 to a different switch. Would like to see how this affects yours as well since I am sure you have the same issue, as you also have a 1930 switch.


  • 34.  RE: Problem AP22 and 2.3.1

    Posted 3 days ago
    I am on it! Let me check....

    ------------------------------
    ====
    Jeff | VA2SS
    ------------------------------



  • 35.  RE: Problem AP22 and 2.3.1

    Posted 3 days ago
    Ok, this is the test I did.

    I connected 1 AP22 (powered over Power supply) on a small unmanaged switch and did again some ping tests.

    I turned off my 2 other AP22.... only 1 AP22 was turned on for my test making sure that I am using the right one connected to my unmanaged switch (not 1930).

    Results

    Over wifi

    Ping 100 packets from laptop over wifi (using AP not connected to 1930.... but using an unmanaged switch)  to gateway (wired) = average latency 11ms with less 1% packet loss
    Ping 100 packets from laptop over wifi to AP22 IP address (wired) = average latency 10ms with less 1% packet loss

    Wired only

    Ping 100 packets from AP22 wired (using web interface tools) to gateway wired = average latency less than 2ms, no packet loss
    Ping 100 packets from AP22 wired (using web interface tools) to 1930 (wired) assigned IP address = average latency less than 3ms, no packet loss
    Ping 100 packets from Gateway wired (using web interface tools) to AP22 (wired) assigned IP address = average latency less than 2ms, no packet loss
    Ping 100 packets from Gateway wired (using web interface tools) to 1930 (wired) assigned IP address = average latency less than 2ms, no packet loss


    So far, doing a ping test over wifi using an AP22 adds substantial latency... as it should be less than 5ms... not 10ms or more. Using previous results, doing ping test thru a 1930 switch seems to add more latency than using another brand name switch when tests are done over wifi.



    ------------------------------
    ====
    Jeff | VA2SS
    ------------------------------



  • 36.  RE: Problem AP22 and 2.3.1

    Posted 3 days ago
    Jeff,

    The latency jumping to 10-15ms isn't going to kill your Airplay sessions. But the lengthy drops that I am describing might. If you have your AP22 connected to the 1930, then let a ping run for an hour to the local gateway, then go back scrolling through it, you may see sections of anywhere from 30 to 80 dropped packets in a row. This may result in over packet loss for the hour around 1.5%.

    Then, with the AP22 connected to a different switch instead of the 1930, do the same test. If I am correct, when scroll back through the results of the ping test, you will not see sections of 30 to 80 pings dropped in a row, and will see overall packet loss for the hour to to the local gateway at around 0.2%.

    You really need to let it run for at least an hour to be sure of a proper test.

    Rob


  • 37.  RE: Problem AP22 and 2.3.1

    Posted 2 days ago
    Hi Rob,

    I know the 10-20ms will not kill my stream with Airplay.... but I still found such latency is unusual for such device when having a network traffic almost idle. We should see results closer to 1-3ms than 10-20ms for 1 hop.

    I started a ping test and I will let it run for a couple of hours. Packet loss might be the culprit for sure. Inside Macbook log, I recently followed the airplay message log until a disconnection..... when the disconnection occurred, error in Macbook OS log, a message was related to a connection loss between the 2 devices.

    Thanks for posting your results :-) 

    Best regards.

    ------------------------------
    ====
    Jeff | VA2SS
    ------------------------------



  • 38.  RE: Problem AP22 and 2.3.1

    Posted 2 days ago

    I ran a few ping tests just out of curiosity. 


    UniFi Lab: pings to gateway= 7-8ms
    AIO Lab: (AP12 + 24 Port PoE1930)= 12-18ms

    Both networks have no traffic transiting them. 

    I find it a bit odd that ping times are 50% higher with the same test device using the same basic parameters. 



    ------------------------------
    Ethan
    ------------------------------



  • 39.  RE: Problem AP22 and 2.3.1

    Posted 3 days ago

    I have another update. I have confirmed that the problem is indeed a compatibility issue between AP22 and 1930 switch. I have taken an unmanaged PoE switch and tried it both upstream and downstream of the 1930 switch. When AP22s are attached to the unmanaged PoE switch, either upstream or downstream of the 1930, they work perfectly. I even used the same port on the 1930 that was previously going to an AP22, to rule out any port issues.

     

    The AP22s actually work just fine, as long as you do not attach them directly to a 1930 switch, but they can pass through it, if first connected to another switch.  I would imagine Aruba should be able to lab this up now that they have very specific on how to reproduce it. I let them know in my ticket.

     

    For now, I have to leave this unmanaged PoE switch hanging off this Aruba 1930 to power the AP22s. As longs as they are not directly connected to the 1930, they work fine. Hopefully they can figure something out soon, but at least I have good wireless again, I just can't use their switch for wifi.


  • 40.  RE: Problem AP22 and 2.3.1

    Posted 2 days ago

    Sorry, I spoke too soon. The problem still happens if the AP22s pass through the 1930 switch at all. So attached to a downstream switch, the problem eventually happens. I timed it for an hour and it didn't happen, but right after that it did.

     

    So as long as the AP22 never passes through the 1930 switch, they will work fine. Anything else connected to the 1930 switch directly, that is not an AP22, also works fine.




  • 41.  RE: Problem AP22 and 2.3.1

    Posted 2 days ago
    Rob, I guess you manage your 1930 locally..... I am wondering if your errors counters for each port are like mine..... unless the total amount of packets..... always no errors nor collisions..... seems strange to having all at 0..... it is normal to have a few hits and missed from time to time no ???

    Errors counters.... are they really working ?? :-)

    ------------------------------
    ====
    Jeff | VA2SS
    ------------------------------



  • 42.  RE: Problem AP22 and 2.3.1