Welcome, Guest. Please login or register.

Author Topic: Timeout at non discoverable dev's is too long  (Read 2669 times)

cmesser

  • Jr. Member
  • **
  • Posts: 80
    • View Profile
Timeout at non discoverable dev's is too long
« on: April 19, 2011, 04:56:37 PM »
Hi,

I just noticed that the discovery takes longer now, and I see the following lines in the log:
Code: [Select]
10.16.140.58    No response from b02bhl063, not discoverable             313/87-128s
The device is an LWAPP AP without SNMP. But I don't want to filter out all AP's,
because the newer ones are SNMP capable.
Can I tune the SNMP timeout somewhere?
I think 2 minutes are too much, 30 seconds or so would do  ;).

Christoph

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2777
    • View Profile
    • NeDi
Re: Timeout at non discoverable dev's is too long
« Reply #1 on: April 19, 2011, 09:29:47 PM »
I agree, I hate long timeouts myself! How many communities do you have? You could try to reduce them in nedi.conf, once less used ones are discovered (should still work for v1 and v2).

I've also been considering using a ping for existing devices for faster fault handling. Have a look at -A in conjunction with -Ss, which will then use ping instead of identify...

BTW shouldn't LWAPs be ignored with nosnmpdev set to AIR-LAP or so?
« Last Edit: April 19, 2011, 10:21:32 PM by rickli »
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

cmesser

  • Jr. Member
  • **
  • Posts: 80
    • View Profile
Re: Timeout at non discoverable dev's is too long
« Reply #2 on: April 20, 2011, 10:22:37 AM »
I have four communities in conf.

And yes, I ignored them before, but the newer ones support SNMP and its nice to have them in the map
and so on. I just play around with it a little bit.

Also I noticed that the undiscovered APs, if I search for them in the "Nodes-List", are shown up
connected to the Vlan-Interface at the core and not to the switch interface they are really on.
I can get them only via "Devices-Interfaces" searching for the names in the Comment.


tristanbob

  • Full Member
  • ***
  • Posts: 159
    • View Profile
Re: Timeout at non discoverable dev's is too long
« Reply #3 on: April 20, 2011, 06:04:54 PM »
Before we understood what the "nosnmpdev" did, we were wasting 30 seconds on 400 access points!   (We had 3 communities to check)

Code: [Select]
# Regular expression to match discovery protocol description of non-SNMP
# platforms (like lightweight/controlled APs).
;nosnmpdev      IP\s(Phone|Telephone)|MAP-|AIR-
nosnmpdev       AIR|IP\s(Phone|Telephone)|^ATA|AIR-LAP11|MAP-|AP_Controlled

What models do you know of that support SNMP?

You can specify exact models to exclude in this section.  Just look at a switch that is connected to the access point and do a

 "show cdp n d"

I believe the field you want to match is the "platform":

Code: [Select]
Device ID: te-202-ap
Entry address(es):
  IP address: 192.168.72.176
Platform: cisco AIR-LAP1242AG-A-K9   ,  Capabilities: Trans-Bridge
Interface: GigabitEthernet1/0/10,  Port ID (outgoing port): FastEthernet0
Holdtime : 138 sec
Please visit "Other"->"Invoices" on your NeDi installation to make an annual contribution and support Nedi!

cmesser

  • Jr. Member
  • **
  • Posts: 80
    • View Profile
Re: Timeout at non discoverable dev's is too long
« Reply #4 on: April 21, 2011, 03:02:18 PM »
All new Cisco models (1142, 1252, 1240) , but it's a little bit freaky and it seems that they
stopped the implementation at half way. You can configure it on the CLI, but not on the controller.
And you can't do a working "wr" so the config is lost after the next reboot :( .
At the moment, we run a script out of the Cat Tools to reset snmp after a global reboot :)
But for the future we hope that cisco will implement the settings into the controller.

To specify the exact model is a good idea, I'll test it.

Thanks