Welcome, Guest. Please login or register.

Author Topic: All Nodes in a network has been seen only at one switch  (Read 2900 times)

steffen1

  • Guest
All Nodes in a network has been seen only at one switch
« on: August 28, 2009, 11:05:40 PM »
Hello,

Using NeDi v1.0.4, it is my 1st time I get in trouble with nodetables:
In a network where nodes are connected to several Layer-2 Switches and only 2 Layer-3 (Cat6500-12.2(33)SX)
Switches, NeDi stores all nodes in the network to only one Layer-3 Switch, so that it appears as all nodes
will be connected to only one switch, IFName shows <switch>-VL501 or <switch>-VL502 in each row.

After deleting all Nodes and did a ./nedi.pl -A, the problem still remains. So I did a
./nedi.pl -a -v C65-L3-1

The thing I don't understand is, allthough "old IF kept" will displayed (thats the correct Switch / Interface),
nedi will allways write this nodes to the "sticky switch C65-L3-1", that is in the case of "old IF kept"
allways wrong. ???

IP/Domain/Names has been scrambled
 NOD:000bcdf1a578 [ IP:172.16.76.170 w3kp2.beispiel.de  0-> old IF kept l2sw-1-Gi0/16:0]
 NOD:0018fefc7048 [ IP:172.16.76.27 power1.beispiel.de  0-> old IF kept C65-L3-2-Gi3/7:0]
 NOD:001f27375641 [ IP:172.16.77.129 l2sw-1  250-> C65-L3-1-Gi1/1:50 Vl502 ] C65-L3-1-Gi1/1
 NOD:00215af48c52 [ IP:172.16.76.190 w3ka1.beispiel.de  0-> old IF kept l2sw-1-Gi0/12:0]
 NOD:0023ae6494b0 [ IP:172.16.74.3 iLo199.beispiel.de  0-> old IF kept l2sw-3-Fa0/46:0]
 NOD:001f6cc91a80 [ IP:172.16.77.61   50-> old IF kept l2sw-2-Gi0/1:50]
 


Thanks for hints,

Steffen

steffen1

  • Guest
Re: All Nodes in a network has been seen only at one switch
« Reply #1 on: August 31, 2009, 04:22:17 PM »
After comparing and recognizing, that we have the same problem with v1.0.4 in our lab,
I installed a 2nd v1.0.0/2008 nedi instance in our lab and after the 1st discovering the problem disappears
for the nedi v1.0.0 instance and the nodes will be shown where they realy belongs to.

The problem seems to be that in v1.0.4 all IP-nodes will be pulled on to the <L3-device> - <L3 Interface from Arp Table> that owns the Default Gateway.

Does anybody knows about this problem and has allready identified which function in which lib is the
cause for the different behaviour?

thx, Steffen

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2701
    • View Profile
    • NeDi
Re: All Nodes in a network has been seen only at one switch
« Reply #2 on: September 01, 2009, 01:06:45 AM »
I don't remember, if a changed anything there on top of my head. -v should reveal as to why the wrong interfaces are populated, though. If you could email me this output of both versions I'll look into it...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

steffen1

  • Guest
Re: All Nodes in a network has been seen only at one switch
« Reply #3 on: September 02, 2009, 02:43:09 PM »
I have to apologize. Before emailing the discover-logs, I cretaed a 3rd instance with v1.0.4 (orig) as well
and the problem disappeared. :o I was so shure that my SNMPv3 extensions doesnt influence the overall NeDi logic. But due the more complexity and alternatives in how to setup a SNMpv3 session and this in combination of mixed v1/2/3 support in a network forced me to encapsolate this in one function and of cource to replace all SNMP-session opens with this function as well. I did care only for the timeout multiplier but
I forgot one very special thing:
Bridge Forwarding MIB opens VLAN based views only, if you extend the VLAN-number
after the community or V3-user, e.g.: You will get the nodes in VLAN701 only,
if you query the device using public@701 instead of public.

The problem has ben fixed now in the v3-able Code as well:
http://forum.nedi.ch/index.php?topic=546.0

Sorry again for this, the original v1.0.4 doesnt have this issue with node tables.
« Last Edit: September 02, 2009, 02:50:57 PM by steffen1 »

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2701
    • View Profile
    • NeDi
Re: All Nodes in a network has been seen only at one switch
« Reply #4 on: September 04, 2009, 07:05:39 PM »
No problem, but that complexity was the reason I didn't get further in the v3 integration. I'll open a new topic on that, so the community can share their ideas on how to handle future v3 support...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo