Network Management

last person joined: yesterday 

Keep an informative eye on your network with HPE Aruba Networking network management solutions
Expand all | Collapse all

System ExecUIQuery failed for 10.X.X.X: 500 Connect failed: con

This thread has been viewed 9 times
  • 1.  System ExecUIQuery failed for 10.X.X.X: 500 Connect failed: con

    Posted May 25, 2016 03:01 PM

    I am seeing a large number of entries like this one in the event log on my APMs.

    Can someone explain to me what this means? everything seems to be working fine but there are too many of these entries to ignore.

     

    Wed May 25 14:46:57 2016SystemSystemExecUIQuery failed for 10.X.X.X: 500 Connect failed: connect: timeout; Operation now in progress.


  • 2.  RE: System ExecUIQuery failed for 10.X.X.X: 500 Connect failed: con

    EMPLOYEE
    Posted May 25, 2016 04:47 PM

    What version of ArubaOS and what AP model?  



  • 3.  RE: System ExecUIQuery failed for 10.X.X.X: 500 Connect failed: con

    EMPLOYEE
    Posted May 25, 2016 11:56 PM

    This error is typically when Airwave attempts to login to a controller but has incorrect credentials.



  • 4.  RE: System ExecUIQuery failed for 10.X.X.X: 500 Connect failed: con

    Posted Feb 14, 2018 09:34 AM

    Did this ever get resolved?  I have the same problem



  • 5.  RE: System ExecUIQuery failed for 10.X.X.X: 500 Connect failed: con

    EMPLOYEE
    Posted Feb 14, 2018 09:46 AM

    ExecUIQuery daemon is for getting PEF application and destination information from the controller when Airwave detects controller is bootstrapped and also for getting on demand clients information when preferred amon VS snmp is enabled.

     

     If IP addresses in the events are of controllers? then, make sure provide correct credentials in manage page of the controller in Airwave.

     

    Regards,

    pavan



  • 6.  RE: System ExecUIQuery failed for 10.X.X.X: 500 Connect failed: con

    Posted Feb 14, 2018 10:28 AM

    Thanks Pavan. They are controllers. Is that because I have them set for monitor only mode?



  • 7.  RE: System ExecUIQuery failed for 10.X.X.X: 500 Connect failed: con

    EMPLOYEE
    Posted Feb 14, 2018 10:49 AM

    Hi,

    No, check whether controller credentials proivded in Airwave APs/Devcies>manage page is correct.

     

    Regards,

    Pavan



  • 8.  RE: System ExecUIQuery failed for 10.X.X.X: 500 Connect failed: con

    Posted Oct 01, 2018 01:10 PM

    Also check your control plane firewall or interface ACLs. I enabled all traffic on all ports to and from my whole management net, 172.16.0.0/16. Here's what I did in my control plane firewall:

     

    configure terminal
    firewall cp
    # REMOVE THE FIRST DENY RULE AND EVERYTHING UNDERNEATH IT.
    no ipv4 deny any proto 6 ports 22 22
    no ipv4 deny any proto 6 ports 80 80
    no ipv4 deny any proto 6 ports 443 443
    no ipv4 deny any proto 6 ports 4343 4343
    no ipv4 permit 172.16.0.0 255.255.0.0 proto 17 ports 8211 8211
    no ipv4 permit 192.168.8.0 255.255.248.0 proto 17 ports 8211 8211
    no ipv4 deny any proto 17 ports 8211 8211
    no ipv6 deny any proto 17 ports 8211 8211
    
    # ADD IN THE ALLOW ALL RULES FOR MANAGEMENT
    ipv4 permit 172.16.0.0 255.255.0.0 proto 6 ports 0 65535
    ipv4 permit 172.16.0.0 255.255.0.0 proto 17 ports 0 65535
    
    # READD ALL THE RULES YOU JUST REMOVED
    ipv4 deny any proto 6 ports 22 22
    ipv4 deny any proto 6 ports 80 80
    ipv4 deny any proto 6 ports 443 443
    ipv4 deny any proto 6 ports 4343 4343
    ipv4 permit 192.168.8.0 255.255.248.0 proto 17 ports 8211 8211
    ipv4 deny any proto 17 ports 8211 8211
    ipv6 deny any proto 17 ports 8211 8211

     

    Or you can configure all traffic/all ports to/from your AirWave server:

    configure terminal
    firewall cp
    # REMOVE THE FIRST DENY RULE AND EVERYTHING UNDERNEATH IT.
    no ipv4 deny any proto 6 ports 22 22
    no ipv4 deny any proto 6 ports 80 80
    no ipv4 deny any proto 6 ports 443 443
    no ipv4 deny any proto 6 ports 4343 4343
    no ipv4 permit 172.16.0.0 255.255.0.0 proto 17 ports 8211 8211
    no ipv4 permit 192.168.8.0 255.255.248.0 proto 17 ports 8211 8211
    no ipv4 deny any proto 17 ports 8211 8211
    no ipv6 deny any proto 17 ports 8211 8211
    
    # ADD IN THE ALLOW ALL RULES FOR MANAGEMENT
    ipv4 permit host AIRWAVE-SERVER-IP proto 6 ports 0 65535
    ipv4 permit host AIRWAVE-SERVER-IP proto 17 ports 0 65535
    
    # READD ALL THE RULES YOU JUST REMOVED
    ipv4 deny any proto 6 ports 22 22
    ipv4 deny any proto 6 ports 80 80
    ipv4 deny any proto 6 ports 443 443
    ipv4 deny any proto 6 ports 4343 4343
    ipv4 permit 192.168.8.0 255.255.248.0 proto 17 ports 8211 8211
    ipv4 deny any proto 17 ports 8211 8211
    ipv6 deny any proto 17 ports 8211 8211

    If you're concerned about only allowing certain ports I believe the ports AirWave actually wants are 80, 443, and 4343.