Welcome, Guest. Please login or register.

Author Topic: Discovery error 'Requested table is empty or does not exist"  (Read 2357 times)

Subordination

  • Newbie
  • *
  • Posts: 26
    • View Profile
Discovery error 'Requested table is empty or does not exist"
« on: November 13, 2014, 08:16:27 PM »
I get the following error polling  a Cisco2921 router, and as a result they IP table (arp) for this device and associated nodes is un-discovered ...

i  Have other Cisco2921 not subject to this error - is it possible to debug further ?

also notable - IP table from this device is successfully discovered in Nedi  1.06 (this version 1.09)
*****
BridgeFwd (SNMP) --------------------------------------------------------------
SNMP:Connect 172.28.156.161 mystring@1 v2 Tout:10s MaxMS:1472
FWDS:Walking BridgeFwd (swtcchcsr@1)
ERR :Fp1 Requested table is empty or does not exist
FWDS:Walking FWD Port to IF index
ERR :Fx1 Requested table is empty or does not exist
FWDS:0 bridge forwarding entries found
****

Thanks
Gerard
« Last Edit: November 14, 2014, 12:11:01 AM by Subordination »

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2780
    • View Profile
    • NeDi
Re: Discovery error 'Requested table is empty or does not exist"
« Reply #1 on: November 14, 2014, 03:58:18 PM »
If you upgraded from oh6 to oh9 you'll have to adapt the database (usually done with nedi.pl -i, but you'll loose existing info). Alternatively you can leave the old one running as "archive" and start a new oh9 VM altogether...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

Subordination

  • Newbie
  • *
  • Posts: 26
    • View Profile
Re: Discovery error 'Requested table is empty or does not exist"
« Reply #2 on: November 14, 2014, 07:28:11 PM »
actually I run both in parallel *106 and 109 - so the 109 was a clean install.
the same point on a 1.06 discovery
***
Arp (SNMP)   ------------------------------------------------------------------
SNMP:Connect 172.28.156.161 mystring v2 Tout:2s MaxMS:1472
ARPS:c0ec6e2c7ee4=172.28.156.194 on Gi0/0.100 vl
....
***


the other perplexing  thing is I have other 2921's that don't get this error i n 109;

Cisco 2921 running 15.2(4)M4 - (the one that gets this error with 109 is running 15.2(4)M6)

***
Arp (SNMP) ------------------------------------------------------------------
SNMP:Connect 172.28.200.97 mystring v2 Tout:2s MaxMS:1472
ARPS:0e20a6eeeff8 172.28.199.236 on Gi0/0 vl
...
***


seems like they choose a different .def file for theses discoveries;

on the one that comes up w/o ARP - it chooses
"SOBJ:Reading 1.3.6.1.4.1.9.1.1044.def" on 109-bld

"SOBJ:1.3.6.1.4.1.9.1.1044.def not found, using other.def"  on 106-bld

and on the one that gets ARP 109-bld
"SOBJ:Reading 1.3.6.1.4.1.9.1.1045.def"

Hopefully that is the issue - what makes this variable choice?

« Last Edit: November 14, 2014, 07:45:24 PM by Subordination »

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2780
    • View Profile
    • NeDi
Re: Discovery error 'Requested table is empty or does not exist"
« Reply #3 on: November 15, 2014, 11:59:06 AM »
Err, sorry my bad. I read table and my brain seem to think in SQL right now :)

You're absolutely right with the .def. They sysobjid read from the device determines the .def. If it doesn't exist it resorts to default.def. In Defgen you can "play" with different ArpND settings to figure out what works...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo