Send netdisco-users mailing list submissions to
netdisco-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
netdisco-users-requ...@lists.sourceforge.net
You can reach the person managing the list at
netdisco-users-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: Can netdisco auto-discover to plot whole network?
(Hans Erasmus)
2. Re: Can netdisco auto-discover to plot whole network?
(Oliver Gorwits)
--- Begin Message ---
Hi guys
New info:
Dlink has a funny way of displaying LLDP neigbours. For example:
DGS-3420-28SC:admin#show lldp remote_ports 3
Command: show lldp remote_ports 3
Port ID : 3
-------------------------------------------------------------------------------
Remote Entities Count : 1
Entity 1
Chassis ID Subtype : MAC Address
Chassis ID : 3C-1E-04-C2-D0-00
Port ID Subtype : MAC Address
Port ID : 3C-1E-04-C2-D1-18
Port Description : D-Link DGS-3420-28TC
R1.50.018
Port 25 on Unit 1
System Name : G23A Farmasie SW3
System Description : Gigabit Ethernet Switch
System Capabilities : Repeater, Bridge
Management Address Count : 0
Port PVID : 0
PPVID Entries Count : 0
VLAN Name Entries Count : 0
Protocol ID Entries Count : 0
MAC/PHY Configuration/Status : (See Detail)
Power Via MDI : (None)
Link Aggregation : (See Detail)
Maximum Frame Size : 1536
Unknown TLVs Count : 0
Note the difference in MAC addresses between Chassis ID and Port ID. I have
always known this to be funny, but up until the point where it actually
interfered with what I wanted to accomplish, I never bothered to try and
fix it. So, basically netdisco discovers a MAC address that it has no ARP
entry for, and stops the discovery process.
The fix?
Running the following command on a DGS-3420-28-SC Router:
config lldp ports 1-28 mgt_addr ipv4 enable
And running the following command on the downlink switch connected to the
router:
config lldp ports 25-28 mgt_addr ipv4 enable
Now, netdisco is able to discover the switch after discovery of the router,
and the same with crosslinks to other routers as well.
If you run the show command again (on a port which has been fixed) you get
this:
DGS-3420-28SC:admin#show lldp remote_ports 1
Command: show lldp remote_ports 1
Port ID : 1
-------------------------------------------------------------------------------
Remote Entities Count : 1
Entity 1
Chassis ID Subtype : MAC Address
Chassis ID : 3C-1E-04-BF-2A-00
Port ID Subtype : MAC Address
Port ID : 3C-1E-04-BF-2B-18
Port Description : D-Link DGS-3420-28TC
R1.50.018
Port 25 on Unit 1
System Name : G23A Farmasie SW1
System Description : Gigabit Ethernet Switch
System Capabilities : Repeater, Bridge
Management Address Count : 1
Port PVID : 0
PPVID Entries Count : 0
VLAN Name Entries Count : 0
Protocol ID Entries Count : 0
MAC/PHY Configuration/Status : (See Detail)
Power Via MDI : (None)
Link Aggregation : (See Detail)
Maximum Frame Size : 1536
Unknown TLVs Count : 0
Note the Management Address count. This returns an ipv4 address through
discovery processes and netdisco is able to dynamically discover switches
through routers and "plot" the network as expected.
I will report back with other devices as soon as I can.
Regards
Hans
On Mon, 14 Aug 2017 at 12:35 Hans Erasmus <erasmushan...@gmail.com> wrote:
> Hi Oliver
>
> Again, thanks for the very quick response. It seems that the
> auto-discovery only works on some of the devices, and I need to investigate
> further, but preliminary findings show it may be down to only specific
> routers on specific FW version. Is this possible? For instance, I know for
> a fact that I have enable LLDP on the uplink port of the switches which
> connect to the router, so in my mind netdisco should discover the router,
> find the switch IP, and because LLDP is enabled, query the switch as well.
> Is this assumption correct? It is only after querying the switch that it
> should stop, as there are only nodes connected to it.
>
> I will report back if this is Firmware related or not. Thanks again for
> the trouble!
>
> Hans
>
> On Mon, 14 Aug 2017 at 11:59 Oliver Gorwits <oli...@cpan.org> wrote:
>
>> Hi Hans,
>>
>> On 2017-08-14 07:40, Hans Erasmus wrote:
>> > I am now quering these Dlinks, some are routers and some only
>> > switches. But it seems like I have to manually input every single
>> > device to be discovered manually? Let me try and make it clearer:
>>
>> The first thing to read and understand is this FAQ here:
>>
>>
>> https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod#Understanding-Nodes-and-Devices
>>
>> To automatically discover a network, Netdisco relies on "layer 2
>> discovery protocols" running between devices (LLDP, CDP, etc). It looks
>> like Layer3::DLink already supports LLDP, so once the protocol is
>> enabled on your devices things should work.
>>
>> However that is layer 2 only. For WAN links there is currently no auto
>> discovery (although it is being discussed). In the meantime, if your
>> devices all have management IPs in a known IP prefix or subnet, then you
>> can enter that on your Netdisco Web homepage and Netdisco will scan all
>> IPs for devices.
>>
>> I hope these points help,
>>
>> regards,
>> oliver.
>>
>> > Topology:
>> >
>> >
>> > USR-Backbone1 <----------------------->USR-Backbone2
>> >
>> >
>> > Uplink1 |
>> > | Uplink 2
>> >
>> >
>> > ------------------> Router A <---------------
>> >
>> >
>> > | |
>> > | |
>> >
>> >
>> > Switch 1 Switch 2 Switch X Switch
>> > Y
>> >
>> > So atm I am able to enter the IP of Router A, and it will discover
>> > that it is connected to at least one of the USR-Backbones. Then, when
>> > I drill down in the device details and click on the "ports" tab, I am
>> > able to then again click on port 1 and see what the IP of the device
>> > is connected to it. And this is great, but I was wondering if it is
>> > possible for netdisco to do this automatically? So basically, if you
>> > take the topology above, I want to be able to get all details of all
>> > devices from the USR-backbones right down to the switch feeding the
>> > end user, and all this dynamically/automatically. These devices should
>> > all be added to the inventory list automatically as well. Is this
>> > possible, and am I doing something wrong that this is not happening
>> > when I invoke "discover all" from the web interface?
>> >
>> > Sorry for the confusing post!
>> >
>> > Regards
>> > Hans
>> >
>> ------------------------------------------------------------------------------
>> > Check out the vibrant tech community on one of the world's most
>> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> >
>> > _______________________________________________
>> > Netdisco mailing list
>> > netdisco-users@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/netdisco-users
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Netdisco mailing list
>> netdisco-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/netdisco-users
>>
>
--- End Message ---
--- Begin Message ---
Thanks Hans, I have added a note to the Manual::Vendors page about this,
for the next Netdisco release.
regards,
oliver.
On 2017-08-14 15:16, Hans Erasmus wrote:
Hi guys
New info:
Dlink has a funny way of displaying LLDP neigbours. For example:
DGS-3420-28SC:admin#show lldp remote_ports 3
Command: show lldp remote_ports 3
Port ID : 3
-------------------------------------------------------------------------------
Remote Entities Count : 1
Entity 1
Chassis ID Subtype : MAC
Address
Chassis ID :
3C-1E-04-C2-D0-00
Port ID Subtype : MAC
Address
Port ID :
3C-1E-04-C2-D1-18
Port Description : D-Link
DGS-3420-28TC R1.50.018
Port 25 on Unit 1
System Name :
G23A Farmasie SW3
System Description : Gigabit
Ethernet Switch
System Capabilities :
Repeater, Bridge
Management Address Count : 0
Port PVID : 0
PPVID Entries Count : 0
VLAN Name Entries Count : 0
Protocol ID Entries Count : 0
MAC/PHY Configuration/Status : (See Detail)
Power Via MDI :
(None)
Link Aggregation : (See
Detail)
Maximum Frame Size : 1536
Unknown TLVs Count : 0
Note the difference in MAC addresses between Chassis ID and Port ID. I
have always known this to be funny, but up until the point where it
actually interfered with what I wanted to accomplish, I never bothered
to try and fix it. So, basically netdisco discovers a MAC address that
it has no ARP entry for, and stops the discovery process.
The fix?
Running the following command on a DGS-3420-28-SC Router:
config lldp ports 1-28 mgt_addr ipv4 enable
And running the following command on the downlink switch connected to
the router:
config lldp ports 25-28 mgt_addr ipv4 enable
Now, netdisco is able to discover the switch after discovery of the
router, and the same with crosslinks to other routers as well.
If you run the show command again (on a port which has been fixed) you
get this:
DGS-3420-28SC:admin#show lldp remote_ports 1
Command: show lldp remote_ports 1
Port ID : 1
-------------------------------------------------------------------------------
Remote Entities Count : 1
Entity 1
Chassis ID Subtype : MAC
Address
Chassis ID :
3C-1E-04-BF-2A-00
Port ID Subtype : MAC
Address
Port ID :
3C-1E-04-BF-2B-18
Port Description : D-Link
DGS-3420-28TC R1.50.018
Port 25 on Unit 1
System Name :
G23A Farmasie SW1
System Description : Gigabit
Ethernet Switch
System Capabilities :
Repeater, Bridge
Management Address Count : 1
Port PVID : 0
PPVID Entries Count : 0
VLAN Name Entries Count : 0
Protocol ID Entries Count : 0
MAC/PHY Configuration/Status : (See Detail)
Power Via MDI :
(None)
Link Aggregation : (See
Detail)
Maximum Frame Size : 1536
Unknown TLVs Count : 0
Note the Management Address count. This returns an ipv4 address
through discovery processes and netdisco is able to dynamically
discover switches through routers and "plot" the network as expected.
I will report back with other devices as soon as I can.
Regards
Hans
On Mon, 14 Aug 2017 at 12:35 Hans Erasmus <erasmushan...@gmail.com>
wrote:
Hi Oliver
Again, thanks for the very quick response. It seems that the
auto-discovery only works on some of the devices, and I need to
investigate further, but preliminary findings show it may be down
to only specific routers on specific FW version. Is this possible?
For instance, I know for a fact that I have enable LLDP on the
uplink port of the switches which connect to the router, so in my
mind netdisco should discover the router, find the switch IP, and
because LLDP is enabled, query the switch as well. Is this
assumption correct? It is only after querying the switch that it
should stop, as there are only nodes connected to it.
I will report back if this is Firmware related or not. Thanks again
for the trouble!
Hans
On Mon, 14 Aug 2017 at 11:59 Oliver Gorwits <oli...@cpan.org> wrote:
Hi Hans,
On 2017-08-14 07:40, Hans Erasmus wrote:
I am now quering these Dlinks, some are routers and some only
switches. But it seems like I have to manually input every
single
device to be discovered manually? Let me try and make it
clearer:
The first thing to read and understand is this FAQ here:
https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod#Understanding-Nodes-and-Devices
[1]
To automatically discover a network, Netdisco relies on "layer 2
discovery protocols" running between devices (LLDP, CDP, etc). It
looks
like Layer3::DLink already supports LLDP, so once the protocol is
enabled on your devices things should work.
However that is layer 2 only. For WAN links there is currently no
auto
discovery (although it is being discussed). In the meantime, if
your
devices all have management IPs in a known IP prefix or subnet,
then you
can enter that on your Netdisco Web homepage and Netdisco will
scan all
IPs for devices.
I hope these points help,
regards,
oliver.
Topology:
USR-Backbone1 <----------------------->USR-Backbone2
Uplink1 |
| Uplink 2
------------------> Router A
<---------------
| |
| |
Switch 1 Switch 2 Switch X
Switch
Y
So atm I am able to enter the IP of Router A, and it will
discover
that it is connected to at least one of the USR-Backbones.
Then, when
I drill down in the device details and click on the "ports"
tab, I am
able to then again click on port 1 and see what the IP of the
device
is connected to it. And this is great, but I was wondering if
it is
possible for netdisco to do this automatically? So basically,
if you
take the topology above, I want to be able to get all details
of all
devices from the USR-backbones right down to the switch feeding
the
end user, and all this dynamically/automatically. These devices
should
all be added to the inventory list automatically as well. Is
this
possible, and am I doing something wrong that this is not
happening
when I invoke "discover all" from the web interface?
Sorry for the confusing post!
Regards
Hans
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot [2]
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users [3]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot [2]
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users [3]
Links:
------
[1]
https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod#Understanding-Nodes-and-Devices
[2] http://sdm.link/slashdot
[3] https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
