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. Manual topology config (Simon Hobson)
2. Expire nodes / devices problem (Tobias Gerlach)
3. Re: Netdisco Help (Oliver Gorwits)
4. Re: Manual topology config (Oliver Gorwits)
5. Re: Expire nodes / devices problem (Oliver Gorwits)
6. Re: Manual topology config (Simon Hobson)
7. Re: Manual topology config (Oliver Gorwits)
8. Re: Manual topology config (Simon Hobson)
--- Begin Message ---
OK, so I can see I can create a device and specify the number of ports it has -
but I don't see a way of editing the port names. Have I missed something ?
So having setup the devices, I then started fiddling in the database, setting
the port names to what's in the devices etc.
And also, given a device (it's actually a linux box doing DNS for the site and
a little bit of routing), how should I configure the ports in Netdisco when the
topology is :
Eth0 is connected to a Cisco switch, with VLAN1 as the native VLAN. Eth0.100
and eth0.101 are tagged VLANs on the same link. And tun0 is a VPN to another
site where there's another Linux box doing routing and stuff. There's one IP
address on each interface/VLAN, 4 in total.
Should this be :
eth0, native VLAN 1, VLAN membership 1,100,101
tun0, native VLAN and VLAN membership blank
And should the entries for the VLAN IP addresses be against eth0 ?
--- End Message ---
--- Begin Message ---
Hello,
I'm running the latest Netdisco version and I'm wondering why no
entries are removed from the node_ip table. I expected to find there
no MAC adresses older than 14 days here after running the expire job.
Any ideas or suggestions? Thanks a lot in advance.
# cat environments/deployment.yml
..
expire_devices: 14
expire_nodes: 14
expire_nodes_archive: 14
..
# netdisco-do expire
[25938] 2016-09-19 08:56:56 info expire: started at Mon Sep 19 10:56:56 2016
[25938] 2016-09-19 08:56:57 info expire: finished at Mon Sep 19 10:56:57 2016
[25938] 2016-09-19 08:56:57 info expire: status done: Checked expiry
for all Devices and Nodes
node_ip table:
Actions mac ip active time_first time_last dns
Edit Delete 64:27:37:59:10:11 10.239.48.133 FALSE
2014-10-21 20:07:13.548594 2014-10-21 20:07:13.385271 NULL
Edit Delete cc:07:ab:f2:07:e9 10.253.68.234 FALSE
2014-11-13 12:00:57.858954 2014-11-13 16:16:23.115927 NULL
Edit Delete 90:1b:0e:03:3a:3f 10.84.21.75 TRUE
2014-11-10 08:16:04.133489 2014-11-10 08:16:03.584933 NULL
Edit Delete 9c:fc:01:a1:d9:93 10.247.237.231 FALSE
2015-07-13 21:52:10.267051 2015-07-14 00:27:23.878609 NULL
...
--- End Message ---
--- Begin Message ---
Hi Tim,
On 2016-08-10 13:08, Tim Polimeni wrote:
Next I wanted to add the rancid plugin is it as simple as copying the
rancid script into the deployment config and renaming the groups on
which I want them to be?
There are two RANCID extensions for Netdisco.
One is a web plugin to link from Netdisco web interface to your RANCID
repo:
https://metacpan.org/pod/App::NetdiscoX::Web::Plugin::RANCID
This should be installed using "~netdisco/bin/localenv cpanm --notest
App::NetdiscoX::Web::Plugin::RANCID"
Then follow the instructions in the documentation on the page I linked
above.
The other integration is netdisco-rancid-export which is a script you
could run in a cron job to generate RANCID configuration from the list
of known devices in the Netdisco database:
https://metacpan.org/pod/netdisco-rancid-export
Let us know if you have further questions.
regards,
oliver.
In Rancid I have UEN UES MetroE for my different types.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and
traffic
patterns at an interface-level. Reveals which users, apps, and
protocols are
consuming the most bandwidth. Provides multi-vendor support for
NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hello Simon,
On 2016-09-15 15:41, Simon Hobson wrote:
OK, so I can see I can create a device and specify the number of ports
it has - but I don't see a way of editing the port names. Have I
missed something ?
I guess you're talking about the Pseudo Devices feature? This is used
together with Manual Device Topology connect together two devices
(routers, switches) so that the Netdisco presentation is cleaner, when
you have a part of the network Netdisco cannot discover (such as an MPLS
cloud). A pseudo device does not actually exist in real life (will never
be polled), and the ports on the pseudo device cannot be renamed. It
might help to understand what you're trying to achieve...?
So having setup the devices, I then started fiddling in the database,
setting the port names to what's in the devices etc.
I guess you *could* do that for the pseudo device, it would not hurt.
Don't do this for any other devices - your changes will be overridden by
the next discovery job.
And also, given a device (it's actually a linux box doing DNS for the
site and a little bit of routing), how should I configure the ports in
Netdisco when the topology is :
Eth0 is connected to a Cisco switch, with VLAN1 as the native VLAN.
Eth0.100 and eth0.101 are tagged VLANs on the same link. And tun0 is a
VPN to another site where there's another Linux box doing routing and
stuff. There's one IP address on each interface/VLAN, 4 in total.
Ah, you may want a two-port pseudo device between the two tunnel
interfaces, as there won't be a neighbor protocol running there.
Can I assume that the Cisco device is properly discovered by Netdisco
and has the correct ports, VLANs, etc?
Perhaps also read:
https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod
regards,
oliver.
Should this be :
eth0, native VLAN 1, VLAN membership 1,100,101
tun0, native VLAN and VLAN membership blank
And should the entries for the VLAN IP addresses be against eth0 ?
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi Tobias,
On 2016-09-19 10:07, Tobias Gerlach wrote:
I'm running the latest Netdisco version and I'm wondering why no
entries are removed from the node_ip table. I expected to find there
no MAC adresses older than 14 days here after running the expire job.
Any ideas or suggestions? Thanks a lot in advance.
You can run the netdisco-do command with SQL trace on, to see what
commands are run against the database. That might highlight what's going
on.
netdisco-do expire -DQ
p.s. the # in the prompt examples you gave suggests root user (or you
put it there manually for the email). I advise users not to run Netdisco
as root :).
regards,
oliver.
# cat environments/deployment.yml
..
expire_devices: 14
expire_nodes: 14
expire_nodes_archive: 14
..
# netdisco-do expire
[25938] 2016-09-19 08:56:56 info expire: started at Mon Sep 19
10:56:56 2016
[25938] 2016-09-19 08:56:57 info expire: finished at Mon Sep 19
10:56:57 2016
[25938] 2016-09-19 08:56:57 info expire: status done: Checked expiry
for all Devices and Nodes
node_ip table:
Actions mac ip active time_first time_last
dns
Edit Delete 64:27:37:59:10:11 10.239.48.133 FALSE
2014-10-21 20:07:13.548594 2014-10-21 20:07:13.385271 NULL
Edit Delete cc:07:ab:f2:07:e9 10.253.68.234 FALSE
2014-11-13 12:00:57.858954 2014-11-13 16:16:23.115927 NULL
Edit Delete 90:1b:0e:03:3a:3f 10.84.21.75 TRUE
2014-11-10 08:16:04.133489 2014-11-10 08:16:03.584933 NULL
Edit Delete 9c:fc:01:a1:d9:93 10.247.237.231 FALSE
2015-07-13 21:52:10.267051 2015-07-14 00:27:23.878609 NULL
...
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Oliver Gorwits <oli...@cpan.org> wrote:
>> OK, so I can see I can create a device and specify the number of ports
>> it has - but I don't see a way of editing the port names. Have I
>> missed something ?
>
> I guess you're talking about the Pseudo Devices feature?
Yes
> This is used
> together with Manual Device Topology connect together two devices
> (routers, switches) so that the Netdisco presentation is cleaner, when
> you have a part of the network Netdisco cannot discover (such as an MPLS
> cloud). A pseudo device does not actually exist in real life (will never
> be polled), and the ports on the pseudo device cannot be renamed. It
> might help to understand what you're trying to achieve...?
Exactly what you describe - I have some devices (basic switches) that don't do
SNMP so am using the pseudo devices to make them known to Netdisco and link the
bits of network together. But the ability to name the pseudo device ports would
help in terms of matching what's on the screen with what's in the rack.
>> So having setup the devices, I then started fiddling in the database,
>> setting the port names to what's in the devices etc.
>
> I guess you *could* do that for the pseudo device, it would not hurt.
Well it didn't seem to hurt anything ;-)
>> And also, given a device (it's actually a linux box doing DNS for the
>> site and a little bit of routing), how should I configure the ports in
>> Netdisco when the topology is :
>>
>> Eth0 is connected to a Cisco switch, with VLAN1 as the native VLAN.
>> Eth0.100 and eth0.101 are tagged VLANs on the same link. And tun0 is a
>> VPN to another site where there's another Linux box doing routing and
>> stuff. There's one IP address on each interface/VLAN, 4 in total.
>
> Ah, you may want a two-port pseudo device between the two tunnel
> interfaces, as there won't be a neighbor protocol running there.
>
> Can I assume that the Cisco device is properly discovered by Netdisco
> and has the correct ports, VLANs, etc?
Yes, the whole network of Cisco devices was identified fully without any
problem - though it's slightly amusing to see one of our customers left SNMP
access from the outside world turned on so we've accidentally got "significant"
information on their internal network. Since posting, I've managed to get SNMP
and LLDP woking on some of my Linux boxes. Last time I tried it, I just
couldn't get anything working, but this time it "just worked" with hardly any
config - so suddenly the network as discovered by Netdisco is much more
complete.
> https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod
Yes, some of that might well help in working out what's going on.
I've mostly got things sorted now, just a few little niggles (in my network) to
fix. :-)
--- End Message ---
--- Begin Message ---
Hi Simon,
On 2016-09-30 21:12, Simon Hobson wrote:
But the ability to
name the pseudo device ports would help in terms of matching what's on
the screen with what's in the rack.
I've implemented a minor change in behaviour for the next release, which
will help, although it's a compromise.
Each device port has a "name" field that is user configurable on the
device (e.g. in cisco it's called the description). The Netdisco Port
Control feature allows using SNMP SET operations to update the port
name. What I've done is allow pseudo devices to have their port name
field set using the same Port Control operation, except the SNMP is
obviously skipped.
In the user interface, make sure your user is admin or has port control
rights, then tick the Port Controls box in the fields column on the
right, click update, and you then should be able to edit the content of
the Name column. Note that the netdisco-daemon needs to be running.
Or.... you can do it all from the CLI instead using "netdisco-do
portname ..." and ignore the web GUI. Hope this helps :).
Since posting, I've managed to get SNMP and LLDP woking on some of my
Linux boxes. Last time I tried it, I just couldn't get anything
working, but this time it "just worked" with hardly any config - so
suddenly the network as discovered by Netdisco is much more complete.
Marvellous! Could you do me a favour and send over any LLDP and SNMP
config you used (off list is fine)? I would like to include more
instructions for Linux routers in the docs.
regards,
oliver.
--- End Message ---
--- Begin Message ---
Oliver Gorwits <oli...@cpan.org> wrote:
>> Since posting, I've managed to get SNMP and LLDP woking on some of my
>> Linux boxes. Last time I tried it, I just couldn't get anything
>> working, but this time it "just worked" with hardly any config - so
>> suddenly the network as discovered by Netdisco is much more complete.
>
> Marvellous! Could you do me a favour and send over any LLDP and SNMP
> config you used (off list is fine)? I would like to include more
> instructions for Linux routers in the docs.
Will do, I've still got some more boxes to do so I can check I haven't missed
anything. It'll have to wait till I next have some "slack" time at work though
- it's one of those "filler" jobs.
--- 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
