This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Wireless
- ExtremeWireless (WiNG)
- Device slowly transmit data after migration Contro...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Device slowly transmit data after migration Controller NX9500 and AP 8533
Device slowly transmit data after migration Controller NX9500 and AP 8533
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
09-15-2022 12:05 PM
We have a problem with slowly transmit data after migration locally controller and Access Point to WiNG 7.0.
Model AP is AP8533 version 7.5.1.6-001R
Model Controller is NX-5500-100R0-WR NX5500 version 7.5.1.6-001R
Problem is on mobile devices are very slowly transmit data to server. When are devices connected to SSID.
I check all connection and all is good. We have a huge time out and dropped packets to devices and from devices.
And I don’t known where I can search problem, because all Is good, we not have a problem with WAN and LAN. Problem existing when I migrated controller and AP to WiNG 7.0
Do you can help with that ?
Sending 1000, 1500-byte ICMP Echos to 10.207.29.55, timeout is 2 seconds:
!!!!!!..!!!!!!!!!!!!!!!!.!!.!!!!!.!!!!!!!!.!...!.!.!!.!!!!!!!!!!!!.!!!
!!!!!.!.!.!!!..!!!!!!!!...!.!!!.!...!!!!!!!!.!!!!...!!.!...!!.!!!!!.!.
!!!!..!.!!!!!!!!!.!!!!.!!!....!..!!!..!!!!!!!.!.!!!!.!.!.!!!!!!...!!.!
!!!.!!!..!!!!.!.!!!!!!!!!!.!!!!!.!!.!!!......!!...!.!.!..!!!!.....!...
!!!!!.....!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!...!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!.!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!
Success rate is 89 percent (899/1000), round-trip min/avg/max = 76/176/1944 ms
Sending 1000, 1500-byte ICMP Echos to 10.207.28.254, timeout is 2 seconds:
!!!.!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!.!!!!!!!!!.!!!!!.!!!!!!!!!!!!.!!.!
!!!!!!!!!.!!......!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!
!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!
!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.
!!!!!!!!!!!!!!!!!!!!!!!!!!...!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!
!!!!!!.!!!!...!.!!!!!!!!.!!!!!!!!!!!!.!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!
Success rate is 96 percent (961/1000), round-trip min/avg/max = 70/162/1572 ms
C:\WINDOWS\System32>ping 10.207.28.246 -n 100
Pinging 10.207.28.246 with 32 bytes of data:
Reply from 10.207.28.246: bytes=32 time=204ms TTL=116
Reply from 10.207.28.246: bytes=32 time=209ms TTL=116
Reply from 10.207.28.246: bytes=32 time=127ms TTL=116
Reply from 10.207.28.246: bytes=32 time=148ms TTL=116
Reply from 10.207.28.246: bytes=32 time=135ms TTL=116
Reply from 10.207.28.246: bytes=32 time=136ms TTL=116
Request timed out.
Request timed out.
Reply from 10.207.28.246: bytes=32 time=271ms TTL=116
Request timed out.
Request timed out.
Reply from 10.207.28.246: bytes=32 time=321ms TTL=116
Reply from 10.207.28.246: bytes=32 time=126ms TTL=116
Request timed out.
Reply from 10.207.28.246: bytes=32 time=198ms TTL=116
Request timed out.
Request timed out.
Reply from 10.207.28.246: bytes=32 time=140ms TTL=116
Reply from 10.207.28.246: bytes=32 time=129ms TTL=116
Reply from 10.207.28.246: bytes=32 time=155ms TTL=116
Reply from 10.207.28.246: bytes=32 time=170ms TTL=116
Reply from 10.207.28.246: bytes=32 time=192ms TTL=116
Reply from 10.207.28.246: bytes=32 time=223ms TTL=116
Reply from 10.207.28.246: bytes=32 time=233ms TTL=116
Reply from 10.207.28.246: bytes=32 time=207ms TTL=116
Reply from 10.207.28.246: bytes=32 time=132ms TTL=116
Reply from 10.207.28.246: bytes=32 time=129ms TTL=116
Request timed out.
Reply from 10.207.28.246: bytes=32 time=299ms TTL=116
Reply from 10.207.28.246: bytes=32 time=197ms TTL=116
Reply from 10.207.28.246: bytes=32 time=206ms TTL=116
Request timed out.
Request timed out.
Reply from 10.207.28.246: bytes=32 time=185ms TTL=116
Reply from 10.207.28.246: bytes=32 time=209ms TTL=116
Request timed out.
Reply from 10.207.28.246: bytes=32 time=166ms TTL=116
Reply from 10.207.28.246: bytes=32 time=189ms TTL=116
Reply from 10.207.28.246: bytes=32 time=298ms TTL=116
Reply from 10.207.28.246: bytes=32 time=202ms TTL=116
Reply from 10.207.28.246: bytes=32 time=307ms TTL=116
Reply from 10.207.28.246: bytes=32 time=117ms TTL=116
Reply from 10.207.28.246: bytes=32 time=133ms TTL=116
Reply from 10.207.28.246: bytes=32 time=125ms TTL=116
Reply from 10.207.28.246: bytes=32 time=140ms TTL=116
Reply from 10.207.28.246: bytes=32 time=145ms TTL=116
Reply from 10.207.28.246: bytes=32 time=169ms TTL=116
Reply from 10.207.28.246: bytes=32 time=182ms TTL=116
Reply from 10.207.28.246: bytes=32 time=190ms TTL=116
Reply from 10.207.28.246: bytes=32 time=206ms TTL=116
Reply from 10.207.28.246: bytes=32 time=218ms TTL=116
Reply from 10.207.28.246: bytes=32 time=121ms TTL=116
Reply from 10.207.28.246: bytes=32 time=142ms TTL=116
Reply from 10.207.28.246: bytes=32 time=148ms TTL=116
Reply from 10.207.28.246: bytes=32 time=178ms TTL=116
Reply from 10.207.28.246: bytes=32 time=179ms TTL=116
Reply from 10.207.28.246: bytes=32 time=194ms TTL=116
Reply from 10.207.28.246: bytes=32 time=121ms TTL=116
Reply from 10.207.28.246: bytes=32 time=128ms TTL=116
Reply from 10.207.28.246: bytes=32 time=131ms TTL=116
Reply from 10.207.28.246: bytes=32 time=139ms TTL=116
Reply from 10.207.28.246: bytes=32 time=177ms TTL=116
Reply from 10.207.28.246: bytes=32 time=169ms TTL=116
Reply from 10.207.28.246: bytes=32 time=170ms TTL=116
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.207.28.246:
Packets: Sent = 72, Received = 53, Lost = 19 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 117ms, Maximum = 321ms, Average = 178ms
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
09-19-2022 08:38 AM
Hello,
Without visibility into your config and the tech support dump, it would difficult to guess this cause. I would recommend you start with the basic causes per this article: https://extremeportal.force.com/ExtrArticleDetail?an=000063581
I hope it helps,
BR,
Christoph S.
