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. Dell Powerconnect 70xx VLANs (fixed) (Jon Gerdes)
2. Re: discover weirdness (Joseph Bernard)
3. Re: discover weirdness (Joseph Bernard)
4. Discover CLI vs Web Inconsistency (inetjunkmail)
5. Re: discover weirdness (Oliver Gorwits)
6. Re: Discover CLI vs Web Inconsistency (Cl?ment GERARDIN)
--- Begin Message ---
All
Somewhere between SNMP::Info 3.20 and 3.23 a bug or extra processing was
put in that means that Dell Powerconnect 70xx now display their VLAN
memberships correctly in ND2 for Trunk ports.
At 3.20, only general ports would list them, trunks would only show VLAN
1 as did access ports. The native VLAN (PVID) was always shown
correctly.
Great stuff. Thanks to whoever sorted that out before I even got to
mention it on list!
Cheers
Jon
--- End Message ---
--- Begin Message ---
That is the problem. I issued the following command, and the discover
weirdness is gone.
~netdisco/bin/localenv cpanm --notest --force SNMP::[email protected]
Thanks!
Joseph B.
On Dec 8, 2014, at 9:20 PM, Eric Miller <[email protected]> wrote:
> The error below is caused by a SNMP::Info bug introduced in version 3.22.
>
> A fix has been pushed to the SNMP::Info git repo and a 3.23 version will be
> released shortly. If you need an immediate fix downgrade SNMP::Info to 3.20.
>
> This is most likely only evident in ND2 not ND1 due to differences in the
> database update routines.
>
> Thanks,
> Eric
>
> On 2014-12-08 16:16, Joseph Bernard wrote:
>> I’ve been using ND1 for a while and poke at ND2 every once in a while
>> to see if all the bugs I’ve run into are fixed. My latest poke at ND2
>> has been weird. I did a discover like I always do but things aren’t
>> working right. We have Cisco 6500’s that link to other Cisco 6500’s
>> that link to many 3750 routers. The links between the 6500’s don’t
>> seem to want to be created by ND2. I get weird errors like the
>> following:
>> error running job:
>> DBIx::Class::Storage::DBI::_dbh_execute_for_fetch():
>> execute_for_fetch() aborted with 'ERROR: duplicate key value violates
>> unique constraint "device_port_vlan_pkey"
>> DETAIL: Key (ip, port, vlan, native)=(10.19.0.6, GigabitEthernet2/44,
>> 1, t) already exists.' at populate slice:
>> {
>> ip => "10.19.0.6",
>> last_discover => \"now()",
>> native => "t",
>> port => "GigabitEthernet2/44",
>> vlan => 1,
>> vlantype => "static"
>> } at /home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm line 487
>> I can use discover on each 3750 to get all the underlying switches,
>> but I cannot get the uplinks to show an association with the
>> connection to the 6500 routers.
>> Thanks,
>> Joseph B.
>> ------------------------------------------------------------------------------
>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>> Get technology previously reserved for billion-dollar corporations, FREE
>> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Netdisco mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
I just saw that 3.23 is out. I got that and it works too.
Thanks,
Joseph B.
On Dec 9, 2014, at 8:46 AM, Joseph Bernard <[email protected]> wrote:
> That is the problem. I issued the following command, and the discover
> weirdness is gone.
>
> ~netdisco/bin/localenv cpanm --notest --force SNMP::[email protected]
>
> Thanks!
> Joseph B.
>
> On Dec 8, 2014, at 9:20 PM, Eric Miller <[email protected]> wrote:
>
>> The error below is caused by a SNMP::Info bug introduced in version 3.22.
>>
>> A fix has been pushed to the SNMP::Info git repo and a 3.23 version will be
>> released shortly. If you need an immediate fix downgrade SNMP::Info to 3.20.
>>
>> This is most likely only evident in ND2 not ND1 due to differences in the
>> database update routines.
>>
>> Thanks,
>> Eric
>>
>> On 2014-12-08 16:16, Joseph Bernard wrote:
>>> I’ve been using ND1 for a while and poke at ND2 every once in a while
>>> to see if all the bugs I’ve run into are fixed. My latest poke at ND2
>>> has been weird. I did a discover like I always do but things aren’t
>>> working right. We have Cisco 6500’s that link to other Cisco 6500’s
>>> that link to many 3750 routers. The links between the 6500’s don’t
>>> seem to want to be created by ND2. I get weird errors like the
>>> following:
>>> error running job:
>>> DBIx::Class::Storage::DBI::_dbh_execute_for_fetch():
>>> execute_for_fetch() aborted with 'ERROR: duplicate key value violates
>>> unique constraint "device_port_vlan_pkey"
>>> DETAIL: Key (ip, port, vlan, native)=(10.19.0.6, GigabitEthernet2/44,
>>> 1, t) already exists.' at populate slice:
>>> {
>>> ip => "10.19.0.6",
>>> last_discover => \"now()",
>>> native => "t",
>>> port => "GigabitEthernet2/44",
>>> vlan => 1,
>>> vlantype => "static"
>>> } at /home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm line 487
>>> I can use discover on each 3750 to get all the underlying switches,
>>> but I cannot get the uplinks to show an association with the
>>> connection to the 6500 routers.
>>> Thanks,
>>> Joseph B.
>>> ------------------------------------------------------------------------------
>>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>>> Get technology previously reserved for billion-dollar corporations, FREE
>>> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Netdisco mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hey:
If I look in my job "Undiscovered Devices" report, I see devices that I
think should be discovered. If I go the the CLI and launch a discovery
with a ./bin/netdisco-do discover -D -d w.x.y.z, it completes seemingly
successfully. If I then go launch a discovery via the web interface, the
job reports failure in the job queue. The error is "could not SNMP connect
to w.x.y.z". snmpwalks and CLI discoveries seem fine but the demonized
discoveries and manually triggered web interface discoveries generate
errors.
Is there a difference between the two? Is there some log I can look at to
get more insight into why the web is failing? The vast majority of
discoveries to the same kinds of devices on the same network are successful
either way.
SoftwareVersion*App::Netdisco <http://netdisco.org/>*2.029012DB Schema
<https://metacpan.org/module/netdisco-db-deploy>v39Dancer
<http://http//perldancer.org/>1.3126Bootstrap <http://getbootstrap.com/>
2.3.1PostgreSQL <http://www.postgresql.org/>PostgreSQL 9.2.7 on
x86_64-redhat-linux-gnu, compiled by gcc (GCC) 4.8.2 20140120 (Red Hat
4.8.2-16), 64-bit.
DBI 1.631, DBD::Pg 2.19.3SNMP::Info <http://snmp-info.sourceforge.net/>3.20
Perl <http://www.perl.org/>5.016003
Thanks for any help,
E
--- End Message ---
--- Begin Message ---
On 2014-12-09 13:50, Joseph Bernard wrote:
I just saw that 3.23 is out. I got that and it works too.
Great, many thanks for the confirmation.
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hi,
Same thing for me (with snmpv3 managment config) "discover failed: could
not SNMP connect to ..."
I had to restart it several time to work by the web, but it work each
time with netdisco-do.
Regards,
inetjunkmail a écrit :
Hey:
If I look in my job "Undiscovered Devices" report, I see devices that
I think should be discovered. If I go the the CLI and launch a
discovery with a ./bin/netdisco-do discover -D -d w.x.y.z, it
completes seemingly successfully. If I then go launch a discovery via
the web interface, the job reports failure in the job queue. The
error is "could not SNMP connect to w.x.y.z". snmpwalks and CLI
discoveries seem fine but the demonized discoveries and manually
triggered web interface discoveries generate errors.
Is there a difference between the two? Is there some log I can look
at to get more insight into why the web is failing? The vast majority
of discoveries to the same kinds of devices on the same network are
successful either way.
Software Version
*App::Netdisco <http://netdisco.org/>* 2.029012
DB Schema <https://metacpan.org/module/netdisco-db-deploy> v39
Dancer <http://http//perldancer.org/> 1.3126
Bootstrap <http://getbootstrap.com/> 2.3.1
PostgreSQL <http://www.postgresql.org/> PostgreSQL 9.2.7 on
x86_64-redhat-linux-gnu, compiled by gcc (GCC) 4.8.2 20140120 (Red Hat
4.8.2-16), 64-bit.
DBI 1.631, DBD::Pg 2.19.3
SNMP::Info <http://snmp-info.sourceforge.net/> 3.20
Perl <http://www.perl.org/> 5.016003
Thanks for any help,
E
------------------------------------------------------------------------
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
