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. report of all nodes that have moved to a new port in the last
day? (R.P. Aditya)
2. BlueCoat not working? (Laurens Vets)
3. Default SNMP version (Laurens Vets)
4. Re: BlueCoat not working? (Eric Miller)
5. Re: Default SNMP version (Eric Miller)
6. Re: Default SNMP version (Alan Buxey)
7. Re: Default SNMP version (Oliver Gorwits)
8. Re: report of all nodes that have moved to a new port in the
last day? (Oliver Gorwits)
9. Re: Default SNMP version (Heywood, Dustin)
--- Begin Message ---
We have several thousand wired IP phones across our campus, and those
phones can be moved to new ports for various reasons. We have been using
Netdisco to let us know when a phone is moved from one switch port to
another by running a nightly SQL report (this is for E911 location
reporting purposes on our campus).
Does anyone have SQL/a report that does something similar to track moved
devices?
I ask because what we were using stopped working recently and I can't
think of a better way.
Thanks,
Adi
following is the description of what we did and when and how it has
stopped working...
We had been using the following query to find all the nodes which had
remote_type of "ip_phone" that had a node.time_recent newer than 1 day,
and it worked fine till we upgraded to 1.3.1
select
n.mac,
p.remote_ip,
d.location,
n.port,
n.vlan,
d.ip,
dp.type,
p.remote_type,
n.time_recent
from
device_port p,
node n,
node_ip ip,
device d,
device_port dp
where
d.ip = n.switch
and dp.ip = d.ip
and dp.port = n.port
and p.remote_ip = ip.ip
and p.remote_type ilike '%ip_phone%'
and p.ip = n.switch
and n.mac = ip.mac
and n.time_recent >= (now() - interval '1 days')
order by
n.time_recent desc
1.3.1 added support to track VLAN changes as well, and a VLAN change
will trigger time_recent to update. However since the upgrade, we find
that several hundred of these phones are shown as having moved with
node.time_recent = node.time_last even when the phone has not been
moved.
I've opened a bug:
http://sourceforge.net/p/netdisco/bugs/99/
which I think is the source of the problem.
--- End Message ---
--- Begin Message ---
Hello List,
I'm trying to add a BlueCoat in Netdisco, but I get the following
error:
[root@management netdisco]# ./netdisco -d bluecoat
n e t d i s c o
--------------------------------------------------
[bluecoat] Discover starting
[bluecoat] [Trying SNMP Version 1]
[bluecoat] [Trying SNMP Version 1]
Cannot find module (BLUECOAT-SG-PROXY-MIB): At line 0 in (none)
The BLUECOAT-SG-PROXY-MIB did not load. See README for
SNMP::Info::Layer3::BlueCoatSG
at ./netdisco line 1395
[root@management netdisco]#
Any idea what I might be doing wrong?
--- End Message ---
--- Begin Message ---
Hello,
I'm running Netdisco 1.3.2 and I have "snmpver = 2" set in
netdisco.conf. Is there a specific reason why Netdisco still tries SNMP
Version 1 first?
[switch] Discover starting
[switch] [Trying SNMP Version 1]
[switch] [Trying SNMP Version 1]
! Storing device details back to database - new community string found.
[ip] Fetching Device Info
[ip] Fetching Device Info
...
Kind regards,
Laurens
--- End Message ---
--- Begin Message ---
Looks like it can not load the MIB referenced. Make sure you have the
Bluecoat MIB's downloaded, the netdisco user has read access to them,
and the bluecoat mibs directory is in your netdisco.conf.
On 2013-10-18 11:45, Laurens Vets wrote:
Hello List,
I'm trying to add a BlueCoat in Netdisco, but I get the following
error:
[root@management netdisco]# ./netdisco -d bluecoat
n e t d i s c o
--------------------------------------------------
[bluecoat] Discover starting
[bluecoat] [Trying SNMP Version 1]
[bluecoat] [Trying SNMP Version 1]
Cannot find module (BLUECOAT-SG-PROXY-MIB): At line 0 in (none)
The BLUECOAT-SG-PROXY-MIB did not load. See README for
SNMP::Info::Layer3::BlueCoatSG
at ./netdisco line 1395
[root@management netdisco]#
Any idea what I might be doing wrong?
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the
most from
the latest Intel processors and coprocessors. See abstracts and
register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Please try running with the debug flag on to see if it actually is
trying version 2 first. "Trying SNMP Version 1" is printed without the
debug flag when version 2 has failed and it falls back to version 1.
Thanks,
Eric
On 2013-10-18 11:43, Laurens Vets wrote:
Hello,
I'm running Netdisco 1.3.2 and I have "snmpver = 2" set in
netdisco.conf. Is there a specific reason why Netdisco still tries SNMP
Version 1 first?
[switch] Discover starting
[switch] [Trying SNMP Version 1]
[switch] [Trying SNMP Version 1]
! Storing device details back to database - new community string found.
[ip] Fetching Device Info
[ip] Fetching Device Info
...
Kind regards,
Laurens
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the
most from
the latest Intel processors and coprocessors. See abstracts and
register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Wasn't there a patch to stop fallback to SNMP v1 ?
alan
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--- End Message ---
--- Begin Message ---
On 2013-10-19 11:10, Alan Buxey wrote:
Wasn't there a patch to stop fallback to SNMP v1 ?
Not that I recall. There was a recent patch from Bill to fix the
fallback from v3.
There are options to go the other way: force SNMP version by device
name/prefix/etc:
snmpforce_v1
snmpforce_v2
snmpforce_v3
Incidentally I'm working on a new config syntax for SNMP Auth in
Netdisco 2 to allow more control, e.g. duplicate v3 usernames, matching
communities to IP prefixes, etc. If anyone has particular use cases
they'd like supported, now is the time to let me know.
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hi Adi,
On 2013-10-17 16:58, R.P. Aditya wrote:
1.3.1 added support to track VLAN changes as well, and a VLAN change
will trigger time_recent to update. However since the upgrade, we
find
that several hundred of these phones are shown as having moved with
node.time_recent = node.time_last even when the phone has not been
moved.
I think our time might be better spent understanding why the phone's
VLAN is changing each time Netdisco visits the device. This doesn't seem
like it should be the case, to me :)
Please can you provide a little more information (perhaps on the ticket
you created) about the vendor/model of switch you have, the vendor/model
of IP phone, and particular configuration (e.g. voice VLAN in use).
...time passes...
It seems Netdisco 1 assumes that a MAC address is globally unique,
whereas to me it's unique only within a VLAN. I think this is where the
[potential] bug comes from. The MAC of your IP phone is used on both
Voice and Data VLANs, so Netdisco is flip-flopping between the two.
I'll comment further on the bug report,
regards,
oliver.
--- End Message ---
--- Begin Message ---
I know id like an option to force v2 without a fallback, this is mostly to
speed discovery jobs, if also like an option to automatically output an snmp
discovered credentials file so that in the event a mode passes discovery once
it will retry those credentials in the event the node is dropped for whatever
reasons
we have about 10 different strings in use for ro and rw so discovery can bog
down sometimes
I know I wrote a script to use onesixtyone to run discovery and then output to
a discovered snmp strings file but it would be nice to have that integrated
Sent from my iPhone
> On Oct 19, 2013, at 5:55 AM, "Oliver Gorwits" <[email protected]> wrote:
>
>> On 2013-10-19 11:10, Alan Buxey wrote:
>> Wasn't there a patch to stop fallback to SNMP v1 ?
>
> Not that I recall. There was a recent patch from Bill to fix the
> fallback from v3.
>
> There are options to go the other way: force SNMP version by device
> name/prefix/etc:
>
> snmpforce_v1
> snmpforce_v2
> snmpforce_v3
>
> Incidentally I'm working on a new config syntax for SNMP Auth in
> Netdisco 2 to allow more control, e.g. duplicate v3 usernames, matching
> communities to IP prefixes, etc. If anyone has particular use cases
> they'd like supported, now is the time to let me know.
>
> regards,
> oliver.
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
If you have received this email in error, can you let me know by return email
so I can make sure it doesn't happen again. Because emails can contain
confidential and privileged material, I'd ask for your help by deleting it and
any attachments. Thanks!
--- End Message ---
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
