Controllerless Networks

last person joined: 3 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

Aruba IAP 105 Virtual Controller Port 161 not open

This thread has been viewed 0 times

  • 1.  Aruba IAP 105 Virtual Controller Port 161 not open

    Posted Jul 19, 2013 10:01 AM

    Hello Everyone-

     

    I am trying to get some stats in our nagios instance from our virtual controller in our IAP 105 setup. 

     

    I tried setting up SNMP in "Settings" and chose port 161 and clicked "yes" for inform. I also added our SNMP community name as well. 

     

    But when I run NMAP and scan the virtual controller IP, port 161 is in fact not open. (nmap -T4 -F <VC IP>)

     

    I looked at the logs and saw this: "Reached the limit on Inform Notification queue for <Nagios IP>:161"

     

    Am I missing something? Any help would be appreciated. FWIW here is the Nagios command I'm running:

     

     /usr/lib/nagios/plugins/check_snmp -H <Virtual Controller IP> -c tgblue -o <OID>

    External command error: Timeout: No Response from 192.168.0.1:161.



  • 2.  RE: Aruba IAP 105 Virtual Controller Port 161 not open

    Posted Jul 20, 2013 05:24 PM

    Hi, 

    Please verify basic connectivity. I just enabled SNMP by adding readonly v1/2 community in Instant and run snmpwalk: 

     

    pi@raspbmc:~$ snmpwalk -v 2c -c readonly 192.168.1.111
    iso.3.6.1.2.1.1.1.0 = STRING: "ArubaOS Version 6.2.1.0-3.3.0.2"
    [...]

     

    And configuration: 

     

    [...]

    virtual-controller-ip 192.168.1.111

    [...]

    snmp-server community !*****
    [...]


    Works perfectly. 

    Regards, 

     



  • 3.  RE: Aruba IAP 105 Virtual Controller Port 161 not open

    Posted Jul 22, 2013 08:58 AM

    I appreciate the thought, but yes, the IAP 105 cluster has network connectivity :) 

     

    And as I said before, I have added the community string and am able to do an snmpwalk and get results from our monitoring server. However, when I scan the virtual controller using the nmap command, port 161 is not open. 

     

    I'm trying to use the check_snmp Nagios plugin to get some stats and it's returning this error:

     

    /usr/lib/nagios/plugins/check_snmp -H 192.168.0.1 -c tgblue -o 1.3.6.1.4.1.14823.2.3.3.1.2.1.1.7
    External command error: Timeout: No Response from 192.168.0.1:161.



  • 4.  RE: Aruba IAP 105 Virtual Controller Port 161 not open

    Posted Jul 22, 2013 09:07 AM

    Are you sure that there is no such firewall between IAP and you SNMP host? It looks like dropped traffic. BTW, what is the firmware? I did my test on 3.3.0.x

    Regards, 



  • 5.  RE: Aruba IAP 105 Virtual Controller Port 161 not open

    EMPLOYEE
    Posted Jul 22, 2013 09:09 AM
    tyosick@topgunhq.com wrote:

    I appreciate the thought, but yes, the IAP 105 cluster has network connectivity :) 

     

    And as I said before, I have added the community string and am able to do an snmpwalk and get results from our monitoring server. However, when I scan the virtual controller using the nmap command, port 161 is not open. 

     

    I'm trying to use the check_snmp Nagios plugin to get some stats and it's returning this error:

     

    /usr/lib/nagios/plugins/c -H 192.168.0.1 -c tgblue -o 1.3.6.1.4.1.14823.2.3.3.1.2.1.1.7
    External command error: Timeout: No Response from 192.168.0.1:161.

    tyosick@topgunhq.com,

     

    Nmap port scanning of UDP ports is unreliable unless you use a protocol aware version of NMAP.  This is not a problem with the IAP 105, but with Nmap.  Please direct your query to NMAP or Naigos unless you cannot get snmp data from the IAP in with your NMS.

     



  • 6.  RE: Aruba IAP 105 Virtual Controller Port 161 not open

    Posted Jul 22, 2013 03:50 PM

     

    It's possible that the check_snmp plugin only works for TCP ports and not UDP ports. 

     

    I guess my next question would be how to monitor the IAP's from within Nagios... I'm just needing a few stats like bandwith usage, CPU usage...etc. Nothing crazy. Any thoughts on integrating the IAP 105 cluster with Nagios?