Controllerless Networks

last person joined: 2 days ago 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Back to discussions
Expand all | Collapse all

Blinking IAPs in Airwave

This thread has been viewed 0 times

  • 1.  Blinking IAPs in Airwave

    Posted Mar 19, 2014 05:44 AM

    Hi!

    I manage 4 open WLANs with access to Internet. Networks worked properly (in AirWave there was always 100% SNMP and ICMP uptime) for about 1 month since it was deployed. But now some networks are blinking in their status, below is AMP events from Airwave one of WLANs:

    Wed Mar 19 10:04:49 2014SystemStatus changed to 'OK'
    Wed Mar 19 10:04:49 2014SystemUp
    Wed Mar 19 10:02:14 2014SystemStatus changed to 'Virtual Controller is Down'
    Wed Mar 19 10:02:14 2014SystemDown
    Wed Mar 19 09:05:28 2014SystemStatus changed to 'OK'
    Wed Mar 19 09:05:28 2014SystemUp
    Wed Mar 19 09:02:12 2014SystemStatus changed to 'Virtual Controller is Down'
    Wed Mar 19 09:02:12 2014SystemDown
    Wed Mar 19 08:49:22 2014SystemStatus changed to 'OK'
    Wed Mar 19 08:49:22 2014SystemUp
    Wed Mar 19 08:45:11 2014SystemStatus changed to 'Virtual Controller is Down'
    Wed Mar 19 08:45:11 2014SystemDown
    Wed Mar 19 07:54:02 2014SystemStatus changed to 'OK'
    Wed Mar 19 07:54:02 2014SystemUp
    Wed Mar 19 07:54:02 2014SystemTunnel IP changed from 192.168.0.12 to 192.168.0.9.
    Wed Mar 19 07:48:10 2014SystemStatus changed to 'Virtual Controller is Down'
    Wed Mar 19 07:48:10 2014SystemDown
    Wed Mar 19 07:35:52 2014SystemStatus changed to 'OK'
    Wed Mar 19 07:35:52 2014SystemUp
    Wed Mar 19 07:30:10 2014SystemStatus changed to 'Virtual Controller is Down'
    Wed Mar 19 07:30:10 2014SystemDown
    Wed Mar 19 04:04:38 2014SystemStatus changed to 'OK'
    Wed Mar 19 04:04:38 2014SystemUp
    Tue Mar 18 19:57:19 2014SystemStatus changed to 'Virtual Controller is Down'
    Tue Mar 18 19:57:19 2014SystemDown
    Tue Mar 18 16:37:09 2014SystemConfiguration verification succeeded; configuration is good
    Mon Mar 17 16:37:07 2014SystemConfiguration verification succeeded; configuration is good
    Mon Mar 17 15:04:50 2014SystemStatus changed to 'OK'
    Mon Mar 17 15:04:50 2014SystemUp
    Mon Mar 17 15:04:50 2014SystemTunnel IP changed from 192.168.0.17 to 192.168.0.12.

     

    Sometimes there is: Status changed to 'AP is not associated to Virtual Controller'.

     

    Can you tell me what cause this behaviour? It can be link from external vendor (20Mbps symterical), which in the same time provide DHCP server?

    Thanks in advance for help.



  • 2.  RE: Blinking IAPs in Airwave

    EMPLOYEE
    Posted Mar 19, 2014 06:35 AM

    We do not have enough detail about your deployment to provide any advice.  In general it shows a connectivity issue between Airwave and your IAPS.  In order to understand what is going on here, we need more information about your deployment and topology.

     



  • 3.  RE: Blinking IAPs in Airwave

    Posted Mar 19, 2014 09:09 AM

    There are 4 sites, in every site are 4 IAPs connected to Internet link via switch. Every WLAN is cofigured as open (no authentication, works like hotspot) and every virtual controller is connected to Airwave, config below:

    version 6.2.1.0-3.3.0
    virtual-controller-country PL
    virtual-controller-key 83f0dc7f012fcada1bed23ae88a332634f1c82c3eaa055a646
    name LuxMed_Compensa
    organization LuxMed_Compensa
    virtual-controller-ip 192.168.0.254
    terminal-access
    clock timezone none 00 00
    rf-band all
    ams-ip 62.244.133.18
    ams-key 83881bdb06569489260846ab3702cf9dcecc3887d8af7638

    allow-new-aps
    allowed-ap 9c:1c:12:c9:9d:49
    allowed-ap 9c:1c:12:c9:9d:4b
    allowed-ap 9c:1c:12:c9:9d:6d
    allowed-ap 9c:1c:12:c9:9d:37



    arm
     wide-bands 5ghz
     min-tx-power 18
     max-tx-power 127
     band-steering-mode prefer-5ghz
     air-time-fairness-mode fair-access
     client-aware
     scanning
    ip dhcp pool
     subnet 172.16.31.0
     subnet-mask 255.255.255.0
     dns-server 213.241.79.38
     domain-name DHCPserv
     lease-time 59


    syslog-level warn ap-debug
    syslog-level warn network
    syslog-level warn security
    syslog-level warn system
    syslog-level warn user
    syslog-level warn user-debug
    syslog-level warn wireless




    mgmt-user admin 07007c37f817f29f17eca839191da1c8cbbdda40dc0ea9ae

    wlan access-rule default_wired_port_profile
     rule any any match any any any permit

    wlan access-rule wired-instant
     rule 192.168.0.5 255.255.255.255 match tcp 80 80 permit
     rule 192.168.0.5 255.255.255.255 match tcp 4343 4343 permit
     rule any any match udp 67 68 permit
     rule any any match udp 53 53 permit

    wlan access-rule LuxMed-WiFi
     rule any any match any any any permit

    wlan ssid-profile LuxMed-WiFi
     enable
     index 1
     type guest
     essid LuxMed-WiFi
     opmode opensystem
     max-authentication-failures 0
     vlan 1
     rf-band all
     captive-portal disable
     dtim-period 1
     inactivity-timeout 1000
     broadcast-filter none
     dmo-channel-utilization-threshold 90
     local-probe-req-thresh 0
     max-clients-threshold 64

    auth-survivability cache-time-out 24



    wlan external-captive-portal
     server localhost
     port 80
     url "/"
     auth-text "Authenticated"
     auto-whitelist-disable


    blacklist-time 3600
    auth-failure-blacklist-time 3600

    ids classification
    ids rogue-containment

    ids
     wireless-containment none
     infrastructure-detection-level low
     client-detection-level low
     infrastructure-protection-level low
     client-protection-level low


    wired-port-profile wired-instant
     switchport-mode access
     allowed-vlan all
     native-vlan guest
     no shutdown
     access-rule-name wired-instant
     speed auto
     duplex auto
     no poe
     type guest
     captive-portal disable
     no dot1x

    wired-port-profile default_wired_port_profile
     switchport-mode trunk
     allowed-vlan all
     native-vlan 1
     shutdown
     access-rule-name default_wired_port_profile
     speed auto
     duplex full
     no poe
     type employee
     captive-portal disable
     no dot1x


    enet0-port-profile default_wired_port_profile

    uplink
     preemption
     enforce none
     failover-internet-pkt-lost-cnt 10
     failover-internet-pkt-send-freq 30
     failover-vpn-timeout 180


    airgroup
     disable

    airgroupservice airplay
     disable
     description AirPlay
     id _airplay._tcp
     id _raop._tcp

    airgroupservice airprint
     disable
     description AirPrint
     id _ipp._tcp
     id _pdl-datastream._tcp
     id _printer._tcp
     id _scanner._tcp
     id _universal._sub._ipp._tcp
     id _printer._sub._http._tcp
     id _http._tcp
     id _http-alt._tcp
     id _ipp-tls._tcp
     id _fax-ipp._tcp
     id _riousbprint._tcp
     id _cups._sub._ipp._tcp
     id _cups._sub._fax-ipp._tcp
     id _ica-networking._tcp
     id _ptp._tcp
     id _canon-bjnp1._tcp



  • 4.  RE: Blinking IAPs in Airwave

    EMPLOYEE
    Posted Mar 20, 2014 02:23 AM

    If all sites were good and now they are not, I would look at the site where Airwave is located.  What is the bandwidth at that site?  What is the bandwidth at those other sites?

     



  • 5.  RE: Blinking IAPs in Airwave

    Posted Mar 20, 2014 05:21 AM

    I have no information about Airwave site, i have only access in monitor mode (external company manage this platform). In my WLAN networks, there are three sites with 6Mbps symetrical, and one site with 20 Mbps symetrical.



  • 6.  RE: Blinking IAPs in Airwave

    EMPLOYEE
    Posted Mar 21, 2014 12:16 AM

    If there's a lot of network latency between sites, then it's possible that fine tuning the HTTPS timeout under Group -> select group with VC -> Basic tab -> Aruba Instant settings box.  Alternatively, if you open a case with support, they can help determine the relative latency between the APs and AirWave -> from the AirWave perspective (this is done by enabling additional logging to track all packets received from the Instant APs, then tracking the time between messages for gaps larger than the default 5 minutes).



  • 7.  RE: Blinking IAPs in Airwave

    Posted Mar 21, 2014 08:54 AM

    I will try contact with somebody who manage Airwave. Your assumption can be true, because in site where is 20Mbps symetrical and the same avarage number of clients like in the other sites (where is 6Mbps),  there is 100% SNMP and ICMP uptime through whole time.



  • 8.  RE: Blinking IAPs in Airwave

    EMPLOYEE
    Posted Mar 21, 2014 10:25 AM

    For IAPs, SNMP uptime is less important due to the difference in how AirWave communicates with IAPs.  By design, IAPs send packet updates regularly to AirWave over HTTPS not SNMP.  This moves the information exchange from a request based exchange to an announcement style where the IAP gives updates at 5 minute intervals (with 1 minute check up heartbeats).



  • 9.  RE: Blinking IAPs in Airwave

    Posted Mar 21, 2014 10:52 AM

    To be sure, ICMP Uptime means, how much (in observation time)  IAPs, responses to the ping from Airwave? I'm thinking about set limit (actually now there is no restriction) max bandwidth for user and for whole SSID to that level, to provide good communication between IAPs and Airwave.



  • 10.  RE: Blinking IAPs in Airwave

    EMPLOYEE
    Posted Mar 21, 2014 11:58 AM

    Correct.  The AMP will occasionally ping devices to check for uptime.  I'd have to investigate some more, but I believe that IAPs do not adhere to the ping test.  I have a feeling that IAP up-ness is only related to if we are getting update packets over HTTPS.