Hi,
We have sold quite a lot of AP900 access points and are in the process of troubleshooting a slowness issue at one site. When we ping the LAN interface of the AP (LAN A port 1) we get quite a varied response. Over a gigabit LAN I would expect this to be constantly less than 1ms? I've tested at a couple of sites and all of the AP's do the same (all running firmware 1.1.4)

Reply from 172.16.11.7: bytes=32 time=4ms TTL=64
Reply from 172.16.11.7: bytes=32 time=2ms TTL=64
Reply from 172.16.11.7: bytes=32 time=5ms TTL=64
Reply from 172.16.11.7: bytes=32 time=8ms TTL=64
Reply from 172.16.11.7: bytes=32 time=4ms TTL=64
Reply from 172.16.11.7: bytes=32 time=4ms TTL=64
Reply from 172.16.11.7: bytes=32 time=1ms TTL=64
Reply from 172.16.11.7: bytes=32 time=1ms TTL=64
Reply from 172.16.11.7: bytes=32 time=1ms TTL=64
Reply from 172.16.11.7: bytes=32 time=5ms TTL=64
Reply from 172.16.11.7: bytes=32 time=6ms TTL=64
Reply from 172.16.11.7: bytes=32 time=3ms TTL=64
Reply from 172.16.11.7: bytes=32 time=1ms TTL=64
Reply from 172.16.11.7: bytes=32 time=1ms TTL=64
Reply from 172.16.11.7: bytes=32 time=1ms TTL=64
Reply from 172.16.11.7: bytes=32 time=2ms TTL=64
Reply from 172.16.11.7: bytes=32 time<1ms TTL=64
Reply from 172.16.11.7: bytes=32 time=8ms TTL=64

We don't seem to be seeing the same behaviour with the AP800 model running firmware 1.1.5.

I've just updated to the latest firmware 1.1.5.2 on the AP900 and the response time is now constantly at >1ms. is this a known problem with the 1.1.4 firmware on the AP900?

I've just ran a ping on a few we have here (all on 1.1.5.1) and they are all under 1ms connected to ProCurve Switches
Don't have nay one a previous FW to test with - sorry

Pinging 10.0.0.242 with 32 bytes of data:
Reply from 10.0.0.242: bytes=32 time<1ms TTL=64
Reply from 10.0.0.242: bytes=32 time<1ms TTL=64
Reply from 10.0.0.242: bytes=32 time<1ms TTL=64
Reply from 10.0.0.242: bytes=32 time<1ms TTL=64
Reply from 10.0.0.242: bytes=32 time<1ms TTL=64
Reply from 10.0.0.242: bytes=32 time<1ms TTL=64
Reply from 10.0.0.242: bytes=32 time<1ms TTL=64
Reply from 10.0.0.242: bytes=32 time<1ms TTL=64
Reply from 10.0.0.242: bytes=32 time<1ms TTL=64
Reply from 10.0.0.242: bytes=32 time<1ms TTL=64
Reply from 10.0.0.242: bytes=32 time<1ms TTL=64

C:\WINDOWS\system32>ping 10.0.0.241 -t

Pinging 10.0.0.241 with 32 bytes of data:
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64
Reply from 10.0.0.241: bytes=32 time<1ms TTL=64


C:\WINDOWS\system32>ping 10.0.0.243 -t

Pinging 10.0.0.243 with 32 bytes of data:
Reply from 10.0.0.243: bytes=32 time<1ms TTL=64
Reply from 10.0.0.243: bytes=32 time<1ms TTL=64
Reply from 10.0.0.243: bytes=32 time<1ms TTL=64
Reply from 10.0.0.243: bytes=32 time<1ms TTL=64
Reply from 10.0.0.243: bytes=32 time<1ms TTL=64
Reply from 10.0.0.243: bytes=32 time<1ms TTL=64
Reply from 10.0.0.243: bytes=32 time<1ms TTL=64
Reply from 10.0.0.243: bytes=32 time<1ms TTL=64
Reply from 10.0.0.243: bytes=32 time<1ms TTL=64
Reply from 10.0.0.243: bytes=32 time<1ms TTL=64