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: Netdisco 2.024004 Errors when trying to discover juniper
switch (Oliver Gorwits)
2. Re: Netdisco 2 Name Resolution Question (Oliver Gorwits)
3. Re: Netdisco 2.024004 Errors when trying to discover juniper
switch (Gary Lloyd)
4. Is apache required for Netdisco 2? ([email protected])
5. adding users ([email protected])
--- Begin Message ---
Hi Gary,
You should uncomment the "housekeeping" part of the configuration and
start the netdisco-daemon. This will then get the nodes attached to the
devices (which is what seems to be missing).
For the error below, this is a bit odd as we should not have VLAN 0. I
will look into it. Can you please also let me know what Netdisco version
you're running? Please upgrade to the latest 2.x if you've not done
that.
regards,
oliver.
On 2014-04-02 14:12, Gary Lloyd wrote:
Hello this is my first post.
I am currently trying out netdisco 2 as we are currently netdisco 1.x
users.
It seems OK at discovering cisco equipment, but when I try to
discover
juniper ex2200 switches I am getting the following problem:
[netdisco@melkor ~]$ ~/bin/netdisco-do -D discover -d 10.0.192.130
[15446] info @0.000015> discover: started at Wed Apr 2 14:05:08
2014
The pass option is deprecated. Use password instead. at
/home/netdisco/perl5/lib/perl5/Dancer/Plugin/DBIC.pm line 40.
[15446] debug @0.214281> [10.0.192.130] try_connect with ver: 2,
class: SNMP::Info::Layer3::Juniper, comm: public
[15446] debug @2.205533> [10.0.192.130] device - aliased as
10.0.192.130
[15446] debug @2.205763> resolving 1 aliases with max 50
outstanding requests
[15446] debug @2.368730> [10.0.192.130] device - removed 1 aliases
[15446] debug @2.375727> [10.0.192.130] device - added 1 new
aliases
[15446] debug @8.959597> [10.0.192.130] interfaces - removed 28
interfaces
[15446] debug @8.974682> [10.0.192.130] interfaces - added 28 new
interfaces
[15446] debug @9.508763> [10.0.192.130] vlans - removed 0 device
VLANs
[15446] info @9.521709> discover: finished at Wed Apr 2 14:05:18
2014
[15446] info @9.521867> discover: status error: error running job:
DBIx::Class::Storage::DBI::_dbh_execute_for_fetch():
execute_for_fetch() aborted with 'ERROR: duplicate key value
violates unique constraint "device_vlan_pkey"' at populate slice:
{
description => "default",
ip => "10.0.192.130",
last_discover => "now()",
vlan => 0
} at /home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm
line 457
Also the devices are showing up on the web app, but they are not
showing as having anything attached to their ports.
I have noticed that the UI seems alot faster than version 1.x when
displaying information for the juniper switches.
Can anyone help?
Thanks
_Gary Lloyd_
----------------------------------
IT Services
Keele University
-----------------------------------
--- End Message ---
--- Begin Message ---
Hi Mitch,
On 2014-04-02 18:14, Mitch Todd wrote:
I just set up a new ND2 installation, and found that a lot devices
aren't having their names resolved in v2 where they are in v1. Those
that are resolved in our DNS server are OK; however, most of our
devices are resolved in the /etc/hosts file on the netdisco server,
and I'm seeing ip addresses in the device field where I'm used to
seeing the hostname. Does ND2 ignore the hosts file when it resolves
an IP? so far, I haven't found an answer in the docs.
Thanks for reporting this. Netdisco 2 should take the /etc/hosts file
into account (as a consequence of using AnyEvent::DNS::EtcHosts in
App::Netdisco::Util::DNS).
There might have been a regression... I'll test and let you know.
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hi Oliver
I was running the commands in the housekeeping section in a cron, As i
didn't realise that they were in that file thanks.
The problem I am having is that the junipers are not showing connected
devices to the ports but the cisco ones are showing them. With netdisco 1
we applied an snmp filter on the juniper switches as the netdisco table was
showing two rows for each port with only one of them showing the connected
devices.
The version i am running at the moment is
2.024004<http://search.cpan.org/~oliver/App-Netdisco-2.024004/>
Thanks
*Gary Lloyd*
----------------------------------
IT Services
Keele University
-----------------------------------
On 3 April 2014 21:28, Oliver Gorwits <[email protected]> wrote:
> Hi Gary,
>
> You should uncomment the "housekeeping" part of the configuration and
> start the netdisco-daemon. This will then get the nodes attached to the
> devices (which is what seems to be missing).
>
> For the error below, this is a bit odd as we should not have VLAN 0. I
> will look into it. Can you please also let me know what Netdisco version
> you're running? Please upgrade to the latest 2.x if you've not done
> that.
>
> regards,
> oliver.
>
> On 2014-04-02 14:12, Gary Lloyd wrote:
> > Hello this is my first post.
> >
> > I am currently trying out netdisco 2 as we are currently netdisco 1.x
> > users.
> > It seems OK at discovering cisco equipment, but when I try to
> > discover
> > juniper ex2200 switches I am getting the following problem:
> >
> >> [netdisco@melkor ~]$ ~/bin/netdisco-do -D discover -d 10.0.192.130
> >>
> >> [15446] info @0.000015> discover: started at Wed Apr 2 14:05:08
> >> 2014
> >>
> >> The pass option is deprecated. Use password instead. at
> >> /home/netdisco/perl5/lib/perl5/Dancer/Plugin/DBIC.pm line 40.
> >>
> >> [15446] debug @0.214281> [10.0.192.130] try_connect with ver: 2,
> >> class: SNMP::Info::Layer3::Juniper, comm: public
> >>
> >> [15446] debug @2.205533> [10.0.192.130] device - aliased as
> >> 10.0.192.130
> >>
> >> [15446] debug @2.205763> resolving 1 aliases with max 50
> >> outstanding requests
> >>
> >> [15446] debug @2.368730> [10.0.192.130] device - removed 1 aliases
> >>
> >>
> >> [15446] debug @2.375727> [10.0.192.130] device - added 1 new
> >> aliases
> >>
> >> [15446] debug @8.959597> [10.0.192.130] interfaces - removed 28
> >> interfaces
> >>
> >> [15446] debug @8.974682> [10.0.192.130] interfaces - added 28 new
> >> interfaces
> >>
> >> [15446] debug @9.508763> [10.0.192.130] vlans - removed 0 device
> >> VLANs
> >>
> >> [15446] info @9.521709> discover: finished at Wed Apr 2 14:05:18
> >> 2014
> >>
> >> [15446] info @9.521867> discover: status error: error running job:
> >> DBIx::Class::Storage::DBI::_dbh_execute_for_fetch():
> >> execute_for_fetch() aborted with 'ERROR: duplicate key value
> >> violates unique constraint "device_vlan_pkey"' at populate slice:
> >>
> >> {
> >>
> >> description => "default",
> >>
> >> ip => "10.0.192.130",
> >>
> >> last_discover => "now()",
> >>
> >> vlan => 0
> >>
> >> } at /home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm
> >> line 457
> >
> > Also the devices are showing up on the web app, but they are not
> > showing as having anything attached to their ports.
> > I have noticed that the UI seems alot faster than version 1.x when
> > displaying information for the juniper switches.
> >
> > Can anyone help?
> >
> > Thanks
> >
> > _Gary Lloyd_
> > ----------------------------------
> >
> > IT Services
> > Keele University
> > -----------------------------------
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
--- End Message ---
--- Begin Message ---
Or is it just a convenient addition for site-specific uses like proxied
connections?
--- End Message ---
--- Begin Message ---
Is this supposed to occur in the web admin interface (which I can't get to
because I can't seem to get past the opening page with 'guest') or at a
commandline in postgres?
--- End Message ---
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees_APR
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
