Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

network slow through aruba network

This thread has been viewed 8 times

  • 1.  network slow through aruba network

    Posted Jan 14, 2014 02:17 AM
    Hi, I have Aruba 800 controller with 4 device for AP 61. I notice that network is slow when we connect through Access point, as the time take to do ping is more than 2000+ and sometime more. The ping reach to 200+ after reset the power of AP. When I connect to the controller, I saw that 1 or 2 clients are connected to AP and still it show slow. I notice some interfering AP in my area. What should I do to solve the slowness issue. Thanks


  • 2.  RE: network slow through aruba network

    Posted Jan 14, 2014 04:20 AM

    Hi Amir,

     

    As the wireless is an overlay of your wired network, have you confirmed taht there are no wired issues?What are you pings like to the controller over the wired network?

     

    J



  • 3.  RE: network slow through aruba network

    Posted Jan 14, 2014 04:53 AM

    Thank you for your reply here is ping

     

    Here is ping result

    From wireless client to access point

    C:\>ping 192.9.90.139

    Pinging 192.9.90.139 with 32 bytes of data:
    Reply from 192.9.90.139: bytes=32 time=257ms TTL=64
    Reply from 192.9.90.139: bytes=32 time=102ms TTL=64
    Reply from 192.9.90.139: bytes=32 time=97ms TTL=64
    Reply from 192.9.90.139: bytes=32 time=1780ms TTL=64

    Ping statistics for 192.9.90.139:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 97ms, Maximum = 1780ms, Average = 559ms

    C:\>ping 192.9.90.147

    Pinging 192.9.90.147 with 32 bytes of data:
    Reply from 192.9.90.147: bytes=32 time=1609ms TTL=64
    Reply from 192.9.90.147: bytes=32 time=81ms TTL=64
    Reply from 192.9.90.147: bytes=32 time=348ms TTL=64
    Request timed out.

    Ping statistics for 192.9.90.147:
        Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 81ms, Maximum = 1609ms, Average = 679ms

    From wireless client to controller

    C:\>ping 192.9.60.181

     

    Pinging 192.9.60.181 with 32 bytes of data:

    Reply from 192.9.60.181: bytes=32 time=2464ms TTL=255

    Reply from 192.9.60.181: bytes=32 time=1563ms TTL=255

    Reply from 192.9.60.181: bytes=32 time=1771ms TTL=255

    Request timed out.

     

    Ping statistics for 192.9.60.181:

        Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

    Approximate round trip times in milli-seconds:

        Minimum = 1563ms, Maximum = 2464ms, Average = 1932ms

     

    And sometime

     

    C:\>ping 192.9.60.181

     

    Pinging 192.9.60.181 with 32 bytes of data:

    Reply from 192.9.60.181: bytes=32 time=29ms TTL=255

    Reply from 192.9.60.181: bytes=32 time=96ms TTL=255

    Reply from 192.9.60.181: bytes=32 time=34ms TTL=255

    Reply from 192.9.60.181: bytes=32 time=724ms TTL=255

     

    Ping statistics for 192.9.60.181:

        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

        Minimum = 29ms, Maximum = 724ms, Average = 220ms

     

     

    From wire client to access point

     

    C:\>ping 192.9.90.147

    Pinging 192.9.90.147 with 32 bytes of data:

    Reply from 192.9.90.147: bytes=32 time=2114ms TTL=64

    Reply from 192.9.90.147: bytes=32 time=2476ms TTL=64

    Reply from 192.9.90.147: bytes=32 time=1524ms TTL=64

    Request timed out.

     

    Ping statistics for 192.9.90.147:

     

    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss)

     

    Approximate round trip times in milli-seconds:

    Minimum = 1524ms, Maximum = 2476ms, Average = 2038ms

     

     

    C:\>ping 192.9.90.139

    Pinging 192.9.90.139 with 32 bytes of data:

    Reply from 192.9.90.139: bytes=32 time=2389ms TTL=64

    Reply from 192.9.90.139: bytes=32 time=28ms TTL=64

    Reply from 192.9.90.139: bytes=32 time=115ms TTL=64

    Reply from 192.9.90.139: bytes=32 time=573ms TTL=64

     

    Ping statistics for 192.9.90.139:

        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

        Minimum = 28ms, Maximum = 2389ms, Average = 776ms

     

    From wire client to controller

    C:\>ping 192.9.60.181

     

    Pinging 192.9.60.181 with 32 bytes of data:

    Reply from 192.9.60.181: bytes=32 time=266ms TTL=255

    Reply from 192.9.60.181: bytes=32 time=354ms TTL=255

    Reply from 192.9.60.181: bytes=32 time=49ms TTL=255

    Reply from 192.9.60.181: bytes=32 time=2140ms TTL=255

     

    Ping statistics for 192.9.60.181:

        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

        Minimum = 49ms, Maximum = 2140ms, Average = 702ms

     

     our network subnet is class b

     

     



  • 4.  RE: network slow through aruba network

    Posted Jan 14, 2014 04:55 AM

    ping server from wireless is slow (time 2000+)

    ping server from wire is fast (time 2-)



  • 5.  RE: network slow through aruba network

    Posted Jan 14, 2014 04:59 AM

    Ok, so it looks like a wired issue. 

     

    Can you post the output of the following 2 commands?

     

    show log network 30

    show log error 30


    Have you rebooted your controller since you noticed this issue?

     

    Cheers
    J



  • 6.  RE: network slow through aruba network

    Posted Jan 14, 2014 05:01 AM

    Also how are your switches responding to pings? Any dropped packets?



  • 7.  RE: network slow through aruba network

    Posted Jan 14, 2014 09:44 AM

    hi, realy thank you for the support

     

    this is the output for the info

     


    (ARABSOFT) #show log network 30

    Jan 7 22:08:06 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 7 23:26:03 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 7 23:46:14 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 7 23:47:51 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 7 23:59:20 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 8 00:15:47 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 8 01:26:43 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 8 02:45:35 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 8 03:34:01 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 8 06:55:27 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 8 07:08:27 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 8 07:27:22 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 8 19:37:20 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 8 20:55:01 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 8 21:21:46 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 9 02:42:06 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 9 07:28:50 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 9 07:30:20 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 10 23:27:36 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 11 20:48:47 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 12 00:50:21 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 12 00:59:15 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 12 02:55:08 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 12 07:19:01 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 12 17:54:14 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 12 20:10:32 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 13 02:24:19 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 13 07:39:10 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 13 20:15:07 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured
    Jan 13 23:17:25 :208008:  <INFO> |fpapps|  No change in the Vlan Interface 2 state UP Vlan Interface has tunnels configured

     

     


    (ARABSOFT) #show log errorlog 30

    Jan 13 23:05:46 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 13 23:27:17 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 13 23:30:53 <authmgr 132093>  <ERRS> |authmgr|  WPA2 Key message 2 from Station 58:94:6b:5f:8e:98 00:24:6c:95:4e:00 00:24:6c:c1:54:e0 did not match the replay counter 01 vs 02
    Jan 13 23:37:46 <authmgr 132093>  <ERRS> |authmgr|  WPA2 Key message 2 from Station 1c:99:4c:4c:6b:2f 00:24:6c:95:4d:20 00:24:6c:c1:54:d2 did not match the replay counter 01 vs 02
    Jan 13 23:48:47 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 13 23:59:48 <authmgr 132093>  <ERRS> |authmgr|  WPA2 Key message 2 from Station c4:46:19:9a:bc:e3 00:1a:1e:ce:34:a0 00:1a:1e:c4:e3:4a did not match the replay counter 01 vs 03
    Jan 13 23:59:50 <authmgr 132093>  <ERRS> |authmgr|  WPA2 Key message 2 from Station c4:46:19:9a:bc:e3 00:1a:1e:ce:34:a0 00:1a:1e:c4:e3:4a did not match the replay counter 02 vs 04
    Jan 14 00:10:18 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 00:31:49 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 00:52:09 <authmgr 132093>  <ERRS> |authmgr|  WPA2 Key message 2 from Station 8c:70:5a:15:48:f8 00:24:6c:95:4d:20 00:24:6c:c1:54:d2 did not match the replay counter 01 vs 02
    Jan 14 00:53:19 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 01:10:11 <authmgr 132093>  <ERRS> |authmgr|  WPA2 Key message 4 from Station 00:23:14:dd:af:f0 00:1a:1e:ce:34:a0 00:1a:1e:c4:e3:4a did not match the replay counter 02 vs 04
    Jan 14 01:14:50 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 01:36:21 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 01:57:51 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 02:19:22 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 02:40:53 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 03:02:23 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 03:23:54 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 03:45:25 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 04:05:15 <authmgr 132093>  <ERRS> |authmgr|  WPA2 Key message 2 from Station a4:17:31:7b:19:80 00:24:6c:95:4e:00 00:24:6c:c1:54:e0 did not match the replay counter 02 vs 01
    Jan 14 04:05:17 <authmgr 132093>  <ERRS> |authmgr|  WPA2 Key message 2 from Station a4:17:31:7b:19:80 00:24:6c:95:4e:00 00:24:6c:c1:54:e0 did not match the replay counter 03 vs 02
    Jan 14 04:06:55 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 04:26:00 <authmgr 132093>  <ERRS> |authmgr|  WPA2 Key message 2 from Station 00:26:c7:b6:be:94 00:24:6c:95:4e:00 00:24:6c:c1:54:e0 did not match the replay counter 01 vs 02
    Jan 14 04:26:01 <authmgr 132093>  <ERRS> |authmgr|  WPA2 Key message 4 from Station 00:26:c7:b6:be:94 00:24:6c:95:4e:00 00:24:6c:c1:54:e0 did not match the replay counter 04 vs 05
    Jan 14 04:28:26 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 04:49:57 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 05:11:27 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials
    Jan 14 05:25:09 <authmgr 132093>  <ERRS> |authmgr|  WPA2 Key message 4 from Station a0:88:b4:b9:f2:f8 00:24:6c:95:4e:00 00:24:6c:c1:54:e0 did not match the replay counter 02 vs 03
    Jan 14 05:32:58 <authmgr 199802>  <ERRS> |authmgr|  ldapclient.c, ldap_client_bind_admin_cb:833: LDAP Server ACS LDAP: Error in Binding Admin to server: Probably error in credentials

     

     

    based on errorlog, I delete the LDAP server as it is not in use... I didn't restart the controller I will do now



  • 8.  RE: network slow through aruba network

    Posted Jan 14, 2014 09:49 AM

    ping from the controller

     


    (ARABSOFT) #ping 192.9.200.222  ( DNS Server)
    Press 'q' to abort.
    Sending 5, 100-byte ICMP Echos to 192.9.200.222, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 0.34/0.406/0.637 ms

     

     

    (ARABSOFT) #ping 192.9.91.37   (AP1)
    Press 'q' to abort.
    Sending 5, 100-byte ICMP Echos to 192.9.91.37, timeout is 2 seconds:
    !!!..
    Success rate is 60 percent (3/5), round-trip min/avg/max = 0.574/0.800667/1.101 ms

     

     

    (ARABSOFT) #ping 192.9.90.139   (AP2)
    Press 'q' to abort.
    Sending 5, 100-byte ICMP Echos to 192.9.90.139, timeout is 2 seconds:
    .!!!!
    Success rate is 80 percent (4/5), round-trip min/avg/max = 0.582/0.63/0.692 ms

     

     

     

    (ARABSOFT) #ping 192.9.90.147   (AP3)
    Press 'q' to abort.
    Sending 5, 100-byte ICMP Echos to 192.9.90.147, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 0.565/0.629/0.744 ms

     

     

    from this, it seem that i have issue with the wire from switch to Access Point. correct?



  • 9.  RE: network slow through aruba network

    Posted Jan 14, 2014 09:15 AM

     

    Can you please check is there's any packet loss between the AP and the controller ?

     

    If you can console into the AP try pinging the controller and vice versa.

     

    Confirm that there's not a lot of bootstrapping happening on your APs

     

    show ap debug counters 

     

    How many APs do you have attached to the controller and how many clients ?

     

    Run the show cpuload current and show cpuload to see if there's any spikes 

     

    Is possible to connect a device directly into the controller using the same VLANs and then try pinging



  • 10.  RE: network slow through aruba network

    Posted Jan 14, 2014 09:52 AM

    this is show ap debug counters command

     

    (ARABSOFT) #show ap debug counters

    AP Counters
    -----------
    Name               Group     IP Address    Configs Sent  Configs Acked  AP Boots Sent  AP Boots Acked  Bootstraps  Reboots
    ----               -----     ----------    ------------  -------------  -------------  --------------  ----------  -------
    00:1a:1e:c4:e3:4a  Arabsoft  192.9.91.37   475           475            0              0               9           9
    00:24:6c:c1:54:d2  Arabsoft  192.9.90.139  240           240            0              0               6           6
    00:24:6c:c1:54:e0  Arabsoft  192.9.90.147  639           639            0              0               3           3
    Total APs :3

     



  • 11.  RE: network slow through aruba network

    Posted Jan 14, 2014 09:57 AM

    (ARABSOFT) #show cpuload current
      6:06am  up 33 days, 23:17,  0 users,  load average: 0.10, 0.19, 0.19
    133 processes: 132 sleeping, 1 running, 0 zombie, 0 stopped
    CPU states:  1.4% user,  0.0% system,  0.0% nice,  0.4% idle
    Mem:   256144K av,  209272K used,   46872K free,       0K shrd,    3968K buff
    Swap:       0K av,       0K used,       0K free                  110300K cached

      PID USER     PRI  NI  SIZE  RSS SHARE STAT  LIB %CPU %MEM   TIME COMMAND
    22297 root      19   0   480  480   300 R       0 17.4  0.1   0:00 top
       61 root      12   0   864  860   584 S       0  2.3  0.3  2196m syslogd
        2 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 keventd
        3 root      19  19     0    0     0 SWN     0  0.0  0.0  36:16 ksoftirqd_CP
        1 root       8   0   388  388   312 S       0  0.0  0.1   0:11 init
        6 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 kupdated
       51 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 kjournald
        4 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 kswapd
        5 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 bdflush
      459 root       9   0   904  900   576 S       0  0.0  0.3  11:16 nanny
      465 root       9   0 11412  11M  3400 S       0  0.0  4.4   1:07 arci-cli-hel
       59 root       9   0   428  428   344 S       0  0.0  0.1   0:00 syslogd_star
      474 root       9   0   996  996   728 S       0  0.0  0.3   0:00 packet_filte
      475 root       9   0  1456 1452  1004 S       0  0.0  0.5   0:00 certmgr
      476 root       9   0   740  740   560 S       0  0.0  0.2   0:00 soed
      477 root       9   0   432  432   348 S       0  0.0  0.1  35:27 dbstart

    (ARABSOFT) #



  • 12.  RE: network slow through aruba network

    EMPLOYEE
    Posted Jan 14, 2014 11:03 AM
    @Amir Mahouk wrote:

    (ARABSOFT) #show cpuload current
      6:06am  up 33 days, 23:17,  0 users,  load average: 0.10, 0.19, 0.19
    133 processes: 132 sleeping, 1 running, 0 zombie, 0 stopped
    CPU states:  1.4% user,  0.0% system,  0.0% nice,  0.4% idle
    Mem:   256144K av,  209272K used,   46872K free,       0K shrd,    3968K buff
    Swap:       0K av,       0K used,       0K free                  110300K cached

      PID USER     PRI  NI  SIZE  RSS SHARE STAT  LIB %CPU %MEM   TIME COMMAND
    22297 root      19   0   480  480   300 R       0 17.4  0.1   0:00 top
       61 root      12   0   864  860   584 S       0  2.3  0.3  2196m syslogd
        2 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 keventd
        3 root      19  19     0    0     0 SWN     0  0.0  0.0  36:16 ksoftirqd_CP
        1 root       8   0   388  388   312 S       0  0.0  0.1   0:11 init
        6 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 kupdated
       51 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 kjournald
        4 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 kswapd
        5 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 bdflush
      459 root       9   0   904  900   576 S       0  0.0  0.3  11:16 nanny
      465 root       9   0 11412  11M  3400 S       0  0.0  4.4   1:07 arci-cli-hel
       59 root       9   0   428  428   344 S       0  0.0  0.1   0:00 syslogd_star
      474 root       9   0   996  996   728 S       0  0.0  0.3   0:00 packet_filte
      475 root       9   0  1456 1452  1004 S       0  0.0  0.5   0:00 certmgr
      476 root       9   0   740  740   560 S       0  0.0  0.2   0:00 soed
      477 root       9   0   432  432   348 S       0  0.0  0.1  35:27 dbstart

    (ARABSOFT) #

    Amir Mahouk, do you have "drop broadcast and multicast" enabled on your Virtual AP profile (s)?



  • 13.  RE: network slow through aruba network

    Posted Jan 14, 2014 11:09 AM
    Hi.
    I'm not sure. From where should I check


  • 14.  RE: network slow through aruba network
    Best Answer

    EMPLOYEE
    Posted Jan 14, 2014 11:14 AM

    Configuration> Wireless> AP Configuration.  Edit the Ap-Group that your access points are in.  Expand Wireless Lan.  Expand Virtual AP.  Click on the Virtual AP (wireless network) that you are using.  In the Right Pane there should be an option to "Drop Broadcast and Multicast":

     

    dropbcast.png



  • 15.  RE: network slow through aruba network

    Posted Jan 15, 2014 01:29 AM

    thank you

     

    I enable this option and pings time back to normal.

     

    Generl question: how to drop broadcast and multicast in our wire network?



  • 16.  RE: network slow through aruba network

    Posted Jan 14, 2014 09:56 AM

    this is show ap debug counters command

     

    (ARABSOFT) #show ap debug counters

    AP Counters
    -----------
    Name               Group     IP Address    Configs Sent  Configs Acked  AP Boots Sent  AP Boots Acked  Bootstraps  Reboots
    ----               -----     ----------    ------------  -------------  -------------  --------------  ----------  -------
    00:1a:1e:c4:e3:4a  Arabsoft  192.9.91.37   475           475            0              0               9           9
    00:24:6c:c1:54:d2  Arabsoft  192.9.90.139  240           240            0              0               6           6
    00:24:6c:c1:54:e0  Arabsoft  192.9.90.147  639           639            0              0               3           3
    Total APs :3

     

     

     

     

     

    (ARABSOFT) #show cpuload current
      6:06am  up 33 days, 23:17,  0 users,  load average: 0.10, 0.19, 0.19
    133 processes: 132 sleeping, 1 running, 0 zombie, 0 stopped
    CPU states:  1.4% user,  0.0% system,  0.0% nice,  0.4% idle
    Mem:   256144K av,  209272K used,   46872K free,       0K shrd,    3968K buff
    Swap:       0K av,       0K used,       0K free                  110300K cached

      PID USER     PRI  NI  SIZE  RSS SHARE STAT  LIB %CPU %MEM   TIME COMMAND
    22297 root      19   0   480  480   300 R       0 17.4  0.1   0:00 top
       61 root      12   0   864  860   584 S       0  2.3  0.3  2196m syslogd
        2 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 keventd
        3 root      19  19     0    0     0 SWN     0  0.0  0.0  36:16 ksoftirqd_CP
        1 root       8   0   388  388   312 S       0  0.0  0.1   0:11 init
        6 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 kupdated
       51 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 kjournald
        4 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 kswapd
        5 root       9   0     0    0     0 SW      0  0.0  0.0   0:00 bdflush
      459 root       9   0   904  900   576 S       0  0.0  0.3  11:16 nanny
      465 root       9   0 11412  11M  3400 S       0  0.0  4.4   1:07 arci-cli-hel
       59 root       9   0   428  428   344 S       0  0.0  0.1   0:00 syslogd_star
      474 root       9   0   996  996   728 S       0  0.0  0.3   0:00 packet_filte
      475 root       9   0  1456 1452  1004 S       0  0.0  0.5   0:00 certmgr
      476 root       9   0   740  740   560 S       0  0.0  0.2   0:00 soed
      477 root       9   0   432  432   348 S       0  0.0  0.1  35:27 dbstart

    (ARABSOFT) #