Send netdisco-users mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: Setting macsuck, arpnip to run once a day (Simon Hobson)
2. Re: Setting macsuck, arpnip to run once a day (Andy Ruhl)
3. Re: Setting macsuck, arpnip to run once a day (Simon Hobson)
4. Re: Setting macsuck, arpnip to run once a day (Oliver Gorwits)
5. Re: Setting macsuck, arpnip to run once a day (Oliver Gorwits)
6. Help with LLDP on Dell Powerconnect 35xx (Peters, Robert)
--- Begin Message ---
Andy Ruhl <[email protected]> wrote:
> ... consequently macsuck and arpnip are running nearly constantly. I don't
> mind if they only run once a day or so.
You do realise that both of these grab dynamic information and will be of
limited (if any) use if not run frequently ?
For example, a switch will typically delete a MAC table entry after something
like 5 to 15 minutes after a device is disconnected/switched off. Thus if you
only scan once/day, you'll miss devices that aren't connected & switched on
during a fairly small window. Ditto for ARP table entries on routers.
I don't know if there's an existing ability, but simply rate-limiting queries
would seem to be the best way round this - it's how I'd prefer to do it on a
large network.
--- End Message ---
--- Begin Message ---
On Fri, Jan 2, 2015 at 11:15 AM, Simon Hobson <[email protected]>
wrote:
> Andy Ruhl <[email protected]> wrote:
>
> > ... consequently macsuck and arpnip are running nearly constantly. I
> don't mind if they only run once a day or so.
>
> You do realise that both of these grab dynamic information and will be of
> limited (if any) use if not run frequently ?
> For example, a switch will typically delete a MAC table entry after
> something like 5 to 15 minutes after a device is disconnected/switched off.
> Thus if you only scan once/day, you'll miss devices that aren't connected &
> switched on during a fairly small window. Ditto for ARP table entries on
> routers.
>
> I don't know if there's an existing ability, but simply rate-limiting
> queries would seem to be the best way round this - it's how I'd prefer to
> do it on a large network.
>
Yeap, don't care too much. Most stuff is pretty static. I see the value in
what you're saying but it's not huge to me at the moment.
Explain rate-limiting please.
Andy
--- End Message ---
--- Begin Message ---
Andy Ruhl <[email protected]> wrote:
> Yeap, don't care too much. Most stuff is pretty static. I see the value in
> what you're saying but it's not huge to me at the moment.
Yeah, it depends on your environment.
> Explain rate-limiting please.
Normally, these programs simply throw the SNMP queries out as fast as the
replies come back - so you can have a fair level of traffic depending on how
many parallel thread you run. Also, because the tasks are set off at set times,
you get a "pulse" of traffic - on some of my graphs I san see "ticks" on the
traffic and CPU graphs of my switches/routers. I assume that with 7k devices,
that's the issue you're seeing.
There's an argument for having a "free running" task which sends queries spread
out - applying a maximum rate for the queries, and a minimum interval between
updates for a single host. It's what Nagios does for it's checks - though it's
significantly more programming work than just firing off a task to update all
devices each time it's run.
--- End Message ---
--- Begin Message ---
Hi Andy,
On 2015-01-02 17:57, Andy Ruhl wrote:
I really hope this isn't a stupid question.
No such thing, of course ;-)
Can I just put a line for "when:" that looks like discoverall (cron
format) so it only runs once a day?
Yes, this will work fine. Remove the (now defunct) "min:" lines when
you do that, though.
regards,
oliver.
--- End Message ---
--- Begin Message ---
On 2015-01-02 20:46, Simon Hobson wrote:
There's an argument for having a "free running" task which sends
queries spread out - applying a maximum rate for the queries, and a
minimum interval between updates for a single host. It's what Nagios
does for it's checks - though it's significantly more programming
work
than just firing off a task to update all devices each time it's run.
Yeah I think someone did ask for a "continuous poller" before... ah yes
here's the ticket if you want to add some voice:
https://sourceforge.net/p/netdisco/nd2-features/14/
For further general interest...
What's perhaps also of note is that we do know of many installations
with large numbers (hundreds to thousands) of devices who do manage
hourly polling. I think it has as much to do with the horsepower at the
polling end, and the network device CPUs themselves (slow devices tie up
the pollers).
Pollers (i.e. netdisco-daemon) can be run simultaneously on multiple
servers as well as of course multiple cores on one system. Also giving
the DB more resources helps (and using pgtune script on the PostgreSQL
config).
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hi all,
I've seen a few posts describing issues with Dell Powerconnects not working
with LLDP.
I don't know where to begin troubleshooting.
The interesting part is that my Wireless APs and phones are communicating
LLDP properly, and they are working with connections to other Dell
switches, but they absolutely do not work from our Extreme Summit switches
to Dell switches.
I don't know precisely where to begin.
Here are some of the outputs from relevant commands, let me know if this
isn't pertinent.
>From the consoles, results of show lldp to verify that it's configured
correctly:
>From Dell switch
sh lldp neighbors
Port Device ID Port ID System Name Capabilities TTL
------- --------------- --------------- ----------------- ------------ -----
1/g1 00:04:96:6d:14: 8 SR-X_48p B, R 100
2b
2/e1 c0:8a:de:39:13: c0:8a:de:39:13: SR-008 B, W 98
c0 c3
2/e2 c0:8a:de:36:c4: c0:8a:de:36:c4: SR-202 B, W 105
40 43
>From Extreme
sh lldp neighbors
Port Neighbor Chassis ID Neighbor Port ID TTL Age
=============================================================================
7 00:23:AE:D2:FA:B7 1/g1 120 3
8 5C:26:0A:B3:F7:C4 1/g1 120 14
14 C0:8A:DE:38:6B:B0 C0:8A:DE:38:6B:B3 120 29
Doing the discovery from the command line to the Dell results in this:
try_connect with ver: 2, new class: SNMP::Info::Layer3::Dell, comm: <hidden>
<snipped>
UPDATE device_port
SET remote_type = 'ExtremeXOS (X460-48p) version 15.1.2.12
v1512b12-patch1-4 by release-manager on Thu May 31 13:42:55 EDT 2012'
WHERE ip = '172.30.1.6' AND port = '1/g1'
COMMIT
SELECT me.ip, me.port, me.creation, me.descr, me.up, me.up_admin, me.type,
me.duplex, me.duplex_admin, me.speed, me.name, me.mac, me.mtu, me.stp,
me.remote_ip, me.remote_port, me.remote_type, me.remote_id, me.is_master,
me.slave_of, me.manual_topo, me.is_uplink, me.vlan, me.pvid, me.lastchange
FROM device_port me
WHERE ip = '172.30.1.6' AND port = '2/e1'
BEGIN WORK
UPDATE device_port
SET remote_type = 'AP: Ruckus 7363 Multimedia Hotzone Wireless AP/SW
Version: 9.8.1.0.101'
WHERE ip = '172.30.1.6' AND port = '2/e1'
COMMIT
[27134] 2015-01-04 21:51:11 debug [172.30.1.6] neigh - adding neighbor
10.1.30.15, type [AP: Ruckus 7363 Multimedia Hotzone Wireless AP/SW
Version: 9.8.1.0.101], on 2/e1 to discovery queue
BEGIN WORK
<snipped>
The AP is recognized as a neighbor correctly and autodiscovered, the
Extreme is not.
Here are some snmpwalks to the devices:
Dell Powerconnect 3548
netdisco@monitor:~$ snmpwalk -v 2c -c ***** -Ovq 172.30.1.6
1.0.8802.1.1.2.1.4.1.1.5
"00 04 96 6D 14 2B "
"C0 8A DE 39 13 C0 "
"C0 8A DE 36 C4 40 "
"C0 8A DE 37 FF C0 "
Extreme summitX460-48p
netdisco@monitor:~$ snmpwalk -v 2c -c ***** -Ovq 172.30.1.1
1.0.8802.1.1.2.1.4.1.1.5
"00 23 AE D2 FA B7 "
"5C 26 0A B3 F7 C4 "
"C0 8A DE 38 6B B0 "
"C0 8A DE 37 A7 70 "
netdisco@monitor:~$ snmpwalk -v 2c -c ***** -Ovq 172.30.1.1
.1.0.8802.1.1.2.1.4.1.1.9
"PCT3548_1.5_S2"
"PCT3548_1.6_S3"
"SR-Cafeteria"
"SR-307"
"PCT3424_1.8"
netdisco@monitor:~$ snmpwalk -v 2c -c ***** -Ovq 172.30.1.6
.1.0.8802.1.1.2.1.4.1.1.9
"SR-X_48p"
"SR-008"
"SR-202"
Where do I begin to troubleshoot this?
Thanks for any assistance.
Robert Peters.
--- End Message ---
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
