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. IP address of shutdown interface (Joseph Bernard)
2. Re: IP address of shutdown interface (Eric Miller)
3. Re: question about serial numbers and the 'snmp-server
chassis' command (Eric Miller)
4. SNMP Poll failure (Bavo Seesink)
5. Re: SNMP Poll failure (Oliver Gorwits)
6. Re: question about serial numbers and the 'snmp-server
chassis' command (Sckolnick, Gary)
--- Begin Message ---
We have a router that was split off into two. The older of the two still has
the loopback interface configured but shutdown. Netdisco picked up that IP
address and added it as being one for the old router. I could not get the new
router to get discovered until I deleted the shutdown loopback interface. Is
this by design? Is there a way to figure out that this is happening with a
report or something if it is in case we have other interfaces that are shutdown.
Thanks,
Joseph B.
--- End Message ---
--- Begin Message ---
It's by design since Netdisco can't currently handle overlapping IP
address space. Even though the interface was down the IP address was
still being returned as an alias.
The following SQL should give you any device IP's belonging to ports
that are in a down state:
SELECT di.ip, di.alias, di.port, dp.up
FROM device_ip di
JOIN device_port dp ON di.ip = dp.ip AND di.port = dp.port
WHERE dp.up = 'down'
A custom report can be created with that SQL by following the
documentation at
https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Configuration.pod#reports
Thanks,
Eric
On 2015-01-20 16:31, Joseph Bernard wrote:
We have a router that was split off into two. The older of the two
still has the loopback interface configured but shutdown. Netdisco
picked up that IP address and added it as being one for the old
router. I could not get the new router to get discovered until I
deleted the shutdown loopback interface. Is this by design? Is there
a way to figure out that this is happening with a report or something
if it is in case we have other interfaces that are shutdown.
Thanks,
Joseph B.
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in
Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely
compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
What model / os version of switch?
What version of SNMP::Info is in use on the ND1 and ND2 installs?
Thanks,
Eric
On 2015-01-20 14:40, Sckolnick, Gary wrote:
Hello. We've noticed, comparing the latest Netdisco v2 to our existing
ND1 implementation, that where ND1 was able to retrieve the correct
serial number for a given Cisco switch, ND2 will not retrieve the
serial number, but rather the value configured with the snmp-server
chassis command, if one is set. Since some of our switches are
configured with snmp-server chassis <asset tag>, ND2 reports this
asset tag as the serial number of the switch; ND1 reports the switch's
actual serial number. What's even more curious is that we're not sure
where this is coming from, because a full snmpwalk of the switch does
produce the <asset tag> value.
Any ideas?
________________________
Gary Sckolnick
Network Engineer
Information Services
(802) 847-2541
[email protected]
THE UNIVERSITY OF VERMONT MEDICAL CENTER
UVMHealth.org/MedCenter
This message and any attachments may contain information that is
confidential, privileged and/or protected from disclosure under state
and federal laws. If you received this message in error or through
inappropriate means, please reply to this message to notify the Sender
that the message was received by you in error, and then permanently
delete this message from all storage media, without forwarding or
retaining a copy.
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in
Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely
compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi Oliver,
Thanks for helping
I run the commando that you gave me and it shows the corect community string
that is configured in the deployment.yml.
During the installation i executed the command under the netdisco user
"[netdisco@netmgt /]$ ~/bin/netdisco-deploy"
At the question "Download and update MIB files? [y/N]: y" I answer with yes.
quite fast after that the line apears "MIBs update complete." ........
i see you talking about a directoy "netdisco-mibs" in the home dir. of
netdisco, that one is not there at all. hmmm
i`f looked around but is look like its not installed at all.
Is there a way to manaual install the net-snmp mibs? Or is it better to
re-install the OS and than netdisco again.
That is no problem. Its not in production yet. it was a clean install directly
to 2.030000
thanks in advanced
Greeting
Bavo
--- End Message ---
--- Begin Message ---
Hi Bavo,
Thank you for the additional information.
You should be able to complete the installation using the instructions
here:
https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Deployment.pod#Deploy-without-Internet-access
Note that you should download both files into the home directory of the
netdisco user.
regards,
oliver.
On 2015-01-21 06:57, Bavo Seesink wrote:
Hi Oliver,
Thanks for helping
I run the commando that you gave me and it shows the corect community
string that is configured in the deployment.yml.
During the installation i executed the command under the netdisco
user
"[netdisco@netmgt /]$ ~/bin/netdisco-deploy"
At the question "Download and update MIB files? [y/N]: y" I answer
with yes.
quite fast after that the line apears "MIBs update complete."
........
i see you talking about a directoy "netdisco-mibs" in the home dir.
of
netdisco, that one is not there at all. hmmm
i`f looked around but is look like its not installed at all.
Is there a way to manaual install the net-snmp mibs? Or is it better
to re-install the OS and than netdisco again.
That is no problem. Its not in production yet. it was a clean install
directly to 2.030000
thanks in advanced
Greeting
Bavo
--- End Message ---
--- Begin Message ---
Sorry, I meant to include the exact versions of ND. Here are all the details:
ND1
Netdisco Version: 1.0
SNMP::Info 3.13
Perl Version: 5.8.9 (5.008009)
Postgres Version: PostgreSQL 8.3.7 on i386-portbld-freebsd7.2, compiled
by GCC cc (GCC) 4.2.1 20070719 [FreeBSD]
DBI 1.607 DBD::Pg 2.12.0
Apache Info: Apache/1.3.41 (Unix) mod_perl/1.31
mod_perl Version: 1.31
Mason: Powered by Mason Version 1.42
ZGRViewer: Verison 0.8.2 Interactive GraphViz .svg Viewer used for Network
Map. Author: Emmanuel Pietriga
ND2
Software Version
App::Netdisco 2.030000
DB Schema v39
Dancer 1.3132
Bootstrap 2.3.1
PostgreSQL PostgreSQL 8.4.20 on x86_64-redhat-linux-gnu, compiled by GCC
gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4), 64-bit.
DBI 1.631, DBD::Pg 2.15.1
SNMP::Info 3.23
Perl 5.010001
Switch models where we see this difference between Netdisco/SNMP::Info versions:
296024TT
296048TCS
3550-48
ciscoSm3k16GePoe
cat3560x24P
cat3560x48P
37xxStack
37xxStack
The majority of our switches do not have 'snmp-server chassis <asset tag>'
configured and, therefore, report their actual serial numbers.
Thanks,
~Gary
-----Original Message-----
From: Eric Miller [mailto:[email protected]]
Sent: Tuesday, January 20, 2015 21:49
To: Sckolnick, Gary
Cc: [email protected]
Subject: Re: [Netdisco] question about serial numbers and the 'snmp-server
chassis' command
What model / os version of switch?
What version of SNMP::Info is in use on the ND1 and ND2 installs?
Thanks,
Eric
This message and any attachments may contain information that is confidential,
privileged and/or protected from disclosure under state and federal laws. If
you received this message in error or through inappropriate means, please reply
to this message to notify the Sender that the message was received by you in
error, and then permanently delete this message from all storage media, without
forwarding or retaining a copy.
--- End Message ---
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
