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: Bad Node (Oliver Gorwits)
2. Re: ND2: pseudo device missing neighbors (Oliver Gorwits)
3. Re: Device Cisco SG300 not recognized (Oliver Gorwits)
4. Re: Device Cisco SG300 not recognized (Nikolaos Milas)
5. Re: [OT] vacancy in my team (Oliver Gorwits)
6. [Netdisco2] Problem with SNMP polling order (Tobias Gerlach)
7. Re: [Netdisco2] Problem with SNMP polling order (Tobias Gerlach)
--- Begin Message ---
Hi Jim,
I think there's a Legend for the colour in Netdisco admin UI, but from
what I recall, red highlight means "undiscovered device".
Translating... The IP has been discovered not as a node (workstation,
printer, etc) but as a device (switch, router). Netdisco will try to
connect using SNMP to the discovered device, fail, and so highlight the
item in the admin UI.
Is this an IP phone or similar device which can be node-like and also
device-like?
regards,
oliver.
On 2013-12-19 04:26, Jim Connolly wrote:
We are having a problem where macs and IPs that are known to be
linked
to a specific network switch are not showing in the nodes table, or
in
a node search. They are showing as the MAC and IP in the Netdisco
admin UI (Device View) as per the attached screenshot, but they have
a
red link above them. We are attempting to query them programmatically
from the nodes table, so this causes a problem with the management
app
reliant on this data.
We upgraded to the latest SNMP::Info with no success.
Device details in Netdisco are:
Model: cisco 37xxStack (SNMP::Info::Layer3::C6500)
OS: ios / 12.2(50)SE1
Actual Make / Model is:
WS-C3750G-24PS 12.2(50)SE1 C3750-IPBASEK9-M
WS-C3750-48TS 12.2(50)SE1 C3750-IPBASEK9-M
What can be done with either switch setup changes or netdisco config
tweaks or software upgrades to get these nodes detecting correctly?
Port list screenshot (note the red links with known node macs and
ips):
Switch Details:
_END ERROR REPORT _
Thanks,
Jim
_JIM CONNOLLY_
Director of Information Technology
CONVEYANT SYSTEMS, INC.
1901 Carnegie Avenue, Suite L
Santa Ana, CA 92705
Telephone: (678) 922-1636
[email protected] [1]
www.conveyant.com
This Email and any documents accompanying this Email contain
information from Conveyant Systems, Inc. which is confidential and/or
privileged. The information is intended only for the use of the
individual or entity named on this Email. If you are not the intended
recipient; you are hereby notified that any disclosure, copying,
distribution or the taking of any action in reliance on the contents
of this Email information is strictly prohibited.
Links:
------
[1] mailto:[email protected]
--- End Message ---
--- Begin Message ---
Hi Mike,
If you're comfortable with SQL you could look at the remote_ip and
remote_port columns of the device_port table.
After adding a pseudo device, it should have rows in this table with
links to the neighbours. Corresponding ports of the real devices it
connects to should have had their remote_ip and remote_port values set.
I wonder whether the connected real device was not found for some
reason?
regards,
oliver.
On 2013-12-19 16:05, Mike Beal wrote:
I'm using v 2.020002, fresh install of everything yesterday. Pseudo
devices and links were created via web interface. I double-checked
this morning, just in case something magically appeared overnight.
Still no links.
FROM: Daniel Tuecks [mailto:[email protected]]
SENT: Wednesday, December 18, 2013 6:53 PM
TO: Mike Beal
CC: [email protected]
SUBJECT: Re: [Netdisco] ND2: pseudo device missing neighbors
Mi Mike,
I've create a few pseudo devices/links from real<->pseudo to
pseudo<->pseudo and I can see both pseudo and physical device in my
topology (Netdisco 2.020001)... (pseudeo devices were created using
the webfrontend on a fresh database).
regards
Daniel
2013/12/19 Mike Beal <[email protected] [4]>
I created a pseudo device and added manual links, yet they don't
show up in the map. When I go to Neighbors, all I see is the pseudo
device. There are no links anywhere. Likewise, when I go to the
nearest physical device and try to see neighbors, the pseudo device
is missing.
Shouldn't I see this device in the map, along with all the links I
manually created?
Thanks,
Mike Beal
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business.
Most IT
organizations don't have a clear picture of how application
performance
affects their revenue. With AppDynamics, you get 100% visibility
into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of
AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
[1]
_______________________________________________
Netdisco mailing list
[email protected] [2]
https://lists.sourceforge.net/lists/listinfo/netdisco-users [3]
Links:
------
[1]
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
[2] mailto:[email protected]
[3] https://lists.sourceforge.net/lists/listinfo/netdisco-users
[4] mailto:[email protected]
--- End Message ---
--- Begin Message ---
Hi,
Have you also updated the MIBs (run netdisco-deploy).
I can forward your message to [email protected] as
well. It might require a patch to the library.
regards,
oliver.
On 2013-12-17 20:51, Nikolaos Milas wrote:
On 26/10/2013 3:54 μμ, Oliver Gorwits wrote:
If these are the same as SRW2024 or SRW2048 models then yes, they
work
fine.
We have a few deployed and see the VLANs (native and tagged), and
node
MACs on the ports.
Hi guys,
I am on ND2 (in parallel to ND1, yet on a new server), and I see that
SG300-28 is getting recognized fine as "cisco / SRW2024-K9 V02"
("SRW2024-K9" is the official Cisco designation for SG300-28).
It also shows connected *devices* correctly.
However, ports (on the Ports tab) show up strangely as follows, and
node
MACs (and other info) do *not* get displayed at all (only devices);
on
standard Catalyst switches, nodes are visible fine (even on Cisco
Catalyst Express 500).
1
Po1
Po2
Po3
Po4
Po5
Po6
Po7
Po8
gi1
gi2
gi3
gi4
gi5
gi6
gi7
gi8
gi9
gi10
gi11
gi12
gi13
gi14
gi15
gi16
gi17
gi18
gi19
gi20
gi21
gi22
gi23
gi24
gi25
gi26
gi27
gi28
tunnel1
Note: I am on CentOS 6 using ND 2.020002 and SNMP:Info v3.08.
Could you please advise me whether I can expect full node visibility
on
these devices using ND2?
Thanks,
Nick
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most
IT
organizations don't have a clear picture of how application
performance
affects their revenue. With AppDynamics, you get 100% visibility into
your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of
AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
On 20/12/2013 2:57 μμ, Oliver Gorwits wrote:
Have you also updated the MIBs (run netdisco-deploy).
Yes, following the published upgrade instructions:
$ ~/bin/localenv cpanm --notest App::Netdisco
$ ~/bin/netdisco-deploy
$ ~/bin/netdisco-web restart
$ ~/bin/netdisco-daemon restart
I can forward your message [email protected] as
well. It might require a patch to the library.
Please do! If there is any progress in this issue, please notify us, if
possible!
Thanks and best regards,
Nick
--- End Message ---
--- Begin Message ---
Just a reminder about our vacancy which closes next week. I forgot to
mention that we offer a relocation and family support package, and
welcome applications from member[1] and co-operating states[2]:
http://www.jobs.ac.uk/job/AHS124/network-analyst/
Drop me an email off-list if you have a question.
regards,
oliver.
[1] Austria, Belgium, Denmark, Finland, France, Germany, Greece,
Iceland, Ireland, Italy, Luxembourg, the Netherlands, Norway, Portugal,
Serbia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United
Kingdom.
[2] Bulgaria, Croatia, Czech Republic, Estonia, former Yugoslav
Republic of Macedonia, Hungary, Israel, Latvia, Lithuania, Montenegro,
Morocco, Romania and Slovakia.
On 2013-12-04 23:21, Oliver Gorwits wrote:
Hi folks,
I figure that interest in LAN, WAN, data centre, a bit of Linux, and
coming from somewhere in Europe, might have some crossover with
people
on this list. Please take a look at our vacancy and drop me a line if
you have any questions:
http://www.jobs.ac.uk/job/AHS124/network-analyst/
p.s. and yes, we do run Netdisco 2 in production :-)
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hello,
I recently updated from Netdisco 1.3.2 to Netdisco 2.020002 without
any problems so far.
We have SNMPv3 and SNMPv2 devices as well in our network, in summary
about ~3000.
My deployment.yml looks as follows (only the SNMP relevant part):
snmpver: 3
community: []
community_rw: []
snmp_auth:
-
tag: v2cemea
community: string1
-
tag: v2camerica
community: string2
-
tag: v2capa
community: string3
-
tag: v3global
user: v3username
auth:
pass: secret
proto: MD5
priv:
pass: secret
proto: AES
Discovering of a new device works fine. Doesn't matter what SNMP
version is configured. ND starts with v3, then tries v2 community
strings and at least again for v1.
In future we have to deploy on all devices v3 instead of v2.
But here is the big problem, when I change the SNMP version from v2 to
v3, than ND will not try to reach the device with the v3 credentials.
Here is an example:
netdisco@server:~> ~/bin/netdisco-do -D discover -d 1.2.3.4
[1925] info @0.000014> discover: started at Fri Jan 3 11:54:46 2014
[1925] debug @0.284574> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info::Layer2::Baystack, comm: string1
[1925] debug @4.772507> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info::Layer2::Baystack, comm: string1
[1925] debug @8.778624> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info::Layer2::Baystack, comm: string2
[1925] debug @12.793444> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info::Layer2::Baystack, comm: string3
[1925] debug @16.807209> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info, comm: string1
[1925] debug @20.942497> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info, comm: string1
[1925] debug @24.948641> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info, comm: string2
[1925] debug @28.963591> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info, comm: string3
[1925] debug @32.977029> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info::Layer2::Baystack, comm: string1
[1925] debug @36.994538> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info::Layer2::Baystack, comm: string1
[1925] debug @41.000445> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info::Layer2::Baystack, comm: string2
[1925] debug @45.015187> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info::Layer2::Baystack, comm: string3
[1925] debug @49.028760> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info, comm: string1
[1925] debug @53.043990> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info, comm: string1
[1925] debug @57.048070> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info, comm: string2
[1925] debug @61.062583> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info, comm: string3
[1925] info @65.078802> discover: finished at Fri Jan 3 11:55:51 2014
[1925] info @65.078992> discover: status error: discover failed:
could not SNMP connect to 1.2.3.4/32
netdisco@server:~>
The opposite way, deactivate v3 and activate v2 on the switch, works fine:
netdisco@server:~> ~/bin/netdisco-do -D discover -d 1.2.3.4
[2307] info @0.000015> discover: started at Fri Jan 3 12:09:49 2014
[2307] debug @0.278486> [1.2.3.4] try_connect with ver: 3, class:
SNMP::Info::Layer2::Baystack, comm: v3user:v3username
[2307] debug @0.827602> [1.2.3.4] try_connect with ver: 3, class:
SNMP::Info, comm: v3user:v3username
[2307] debug @1.024884> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info::Layer2::Baystack, comm: string1
[2307] debug @1.350217> [1.2.3.4] device - aliased as 1.2.3.4
[2307] debug @1.350614> resolving 1 aliases with max 250 outstanding requests
[2307] debug @1.526184> [1.2.3.4] device - removed 1 aliases
[2307] debug @1.531474> [1.2.3.4] device - added 1 new aliases
...
Am I wrong with my deployment.yml config?
Thanks in advance for any ideas!
Regards
Tobias
--- End Message ---
--- Begin Message ---
I have to add that it doesn't matter which snmp default version is configured.
--- End Message ---
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
