Welcome, Guest. Please login or register.

Author Topic: Nexus 5K nodes discovered but not being written to db  (Read 1898 times)

spiffturk

  • Guest
Nexus 5K nodes discovered but not being written to db
« on: December 16, 2015, 03:59:38 PM »
Hi there,

I recently moved from 1.0.9 to 1.4.300, as well as moving from one server to another.  On the old server, with 1.0.9, things seemed to run fine (though I can't promise I didn't have to tweak something a few years ago).  On the new server, with 1.4.300, nedi seems to see the nodes attached to a Nexus 5k (using profile 1.3.6.1.4.1.9.12.3.1.3.1038.def for N5K-C5596UP) but after a bunch of FWDS lines in the BridgeFwd (SNMP) section showing all the MAC addresses it sees, it doesn't actually write any to the db:

Code: [Select]
...
FWDS:001dd8b71c41 no IFindex for fwd-port 175
FWDS:001dd8b71c3f no IFindex for fwd-port 175
FWDS:001dd8b71c28 no IFindex for fwd-port 175
FWDS:5cb901c3e708 no IFindex for fwd-port 1160
SNMP:Connect 10.x.x.x comm@2113 v2 Tout:10s MaxMS:1472 Retry:1 NB:0
FWDS:Walking BridgeFwd (comm@2113)
FWDS:001517c884dc no IFindex for fwd-port 175
FWDS:50 bridge forwarding entries found

Write Nodes ------------------------------------------------------------------
WNOD:0 inserted, 0 nodes moved and 0 updated in nedi14.nodes

I have copied over the same .def file from the old server to the new one, in case it was some dark magic in there causing issues, but I don't see a change.  Any ideas what I've mucked up here?  After a quick search of the forums, I did try using "Bridge VLX" instead of "Bridge VXP" that I had originally, but that didn't seem to change anything.

Any hints?

Thanks,

--
Will

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2780
    • View Profile
    • NeDi
Re: Nexus 5K nodes discovered but not being written to db
« Reply #1 on: December 17, 2015, 12:46:14 PM »
Try changing Bridge to VLX if set to VXP (or vice versa) in the .def. It seems N5K are not as consistent as I thought (the "no IFindex" output indicates this)
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

spiffturk

  • Guest
Re: Nexus 5K nodes discovered but not being written to db
« Reply #2 on: December 17, 2015, 02:01:47 PM »
Hi Remo,

I had actually tried both, but now that you mention it: the output is slightly different when run with VLX, and NeDi writes a few nodes to the database, but only a handful of the ~1700 MAC addresses that it finds get written as nodes:

Code: [Select]
...
FWDS:1cc1de6ffc24 on Et1/47 Vl197 10G-FD 822 D
FWDS:6cf049590320 on Et1/47 Vl197 10G-FD 823 D
FWDS:24be0504bc52 on Et1/47 Vl197 10G-FD 824 D
FWDS:24be0504bc16 on Et1/47 Vl197 10G-FD 825 D
FWDS:d4856451e3dc on Et1/5 Vl197 1G-FD 8 D
FWDS:0025902bbf77 on Et1/47 Vl197 10G-FD 826 D
FWDS:a0481ca06f76 on Et1/47 Vl197 10G-FD 827 D
FWDS:002590e4ba0e on Et1/47 Vl197 10G-FD 828 D
FWDS:0050563fff01 on Et1/47 Vl197 10G-FD 829 D
FWDS:005056b20050 on Et1/47 Vl197 10G-FD 830 D
FWDS:1703 bridge forwarding entries found

Write Nodes ------------------------------------------------------------------
EVNT:MOD=F/1 L=100 CL=secn TGT=250-DC1-6-1 MSG=Node 308d993090e8 appeared on Po4090 Vl1593
EVNT:MOD=F/1 L=100 CL=secn TGT=250-DC1-6-1 MSG=Node 001dd8b71c70 appeared on Et101/1/14 Vl1593
WNOD:2 inserted, 0 nodes moved and 62 updated in nedi14.nodes

Several hundred of those probably shouldn't be written.  I also notice that in the older NeDi instance, i get an "Arp (SNMP) -----" section, but on the new instance, that section doesn't appear.  I don't know if this is a matter of code change or misconfiguration, but I could see that being the reason it's no writing nodes, perhaps.

Any other suggestions to look at?

And yes, I'm well familiar with how well Cisco and consistency get along.  Oil and water :)

Thanks again,

--
Will

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2780
    • View Profile
    • NeDi
Re: Nexus 5K nodes discovered but not being written to db
« Reply #3 on: December 23, 2015, 09:25:19 AM »
The D at the end of each line indicates another device is connected to that interface, which means nodes won't be assigned.

Also, I don't consider N5k to be "proper" routers, thus not retrieving their ARP tables. You can change that behavior in Defgen.
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo