Welcome, Guest. Please login or register.

Author Topic: Wrong Device for Node  (Read 3427 times)

chrisb

  • Guest
Wrong Device for Node
« on: August 05, 2010, 01:45:52 PM »
Hi,

the discovery is now working fine. The switches were discovert by CDP (./nedi.pl -pbu seedlist). In the Seedlist is only our BackBone-Router (Cisco 6506e). The CDP-Links are fine.

The Nodes have only the BackBone as Device, rather than the local switch. The local switches are 2950 and 3560. Does anyone have an idea why the devices are wrong?

I red the source code, but does not find a solution.

ntmark

  • Full Member
  • ***
  • Posts: 136
    • View Profile
    • tvnz.co.nz
Re: Wrong Device for Node
« Reply #1 on: August 05, 2010, 10:24:27 PM »
Are the 2950/3560s using port-channels to the 6509?
I've found nedi sometimes cannot find these switches via CDP.
Just add the ones into the seed list.

chrisb

  • Guest
Re: Wrong Device for Node
« Reply #2 on: August 09, 2010, 03:33:18 PM »
Hi,

yes the switches are connected via port-channel, but nedi found them via cdp without problems. I can view the interfaces for her-sw015 (my computer is connected to this switch). So the her-sw015 should be the device for my computer and not the backbone-router.

chrisb

  • Guest
Re: Wrong Device for Node
« Reply #3 on: August 18, 2010, 06:09:43 PM »
No chance to troubleshoot this? :)

chrisb

  • Guest
Re: Wrong Device for Node
« Reply #4 on: August 19, 2010, 10:42:09 AM »
How does nedi find the device, where the node is connected? Mayby i can check the source code with this information.

chrisb

  • Guest
Re: Wrong Device for Node
« Reply #5 on: August 25, 2010, 01:20:53 PM »
Is it possible, that there is a problem with ether-channels and the nodes?

rufer

  • Guest
Re: Wrong Device for Node
« Reply #6 on: August 25, 2010, 01:32:46 PM »
As far as I understand, Nedi prefers an access port over an Etherchannel. We have the same problem with servers connected on Etherchannels, they appear on some random ports and not on the port-channels.

Greetings
Rufer

chrisb

  • Guest
Re: Wrong Device for Node
« Reply #7 on: August 25, 2010, 03:06:15 PM »
It is realy interesting. In our old nedi (v1.0 20.Mai 2008) does it work.

Is there anywhere a description where i can see, how nedi does define the devices? Which perl-sub does find the right device for the node? Is it sub UpNodif? I don't understand the metric-calculation. Could anyone help?

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2780
    • View Profile
    • NeDi
Re: Wrong Device for Node
« Reply #8 on: August 25, 2010, 07:53:07 PM »
Many changes since then. One of them being lowering the metric of a channel to 40, so it would be preferred over a router:


   my $metric =   $portprop{$dv}{$if}{pho} * 10 +
            $portprop{$dv}{$if}{wln} * 20 +
            $portprop{$dv}{$if}{chn} * 40 +
            $portprop{$dv}{$if}{rtr} * 50 +
            $portprop{$dv}{$if}{upl} * 60;

If a mac shows up on another switch, check the metric. Create static links, if necessary...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo