Send netdisco-users mailing list submissions to
        netdisco-users@lists.sourceforge.net

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
        netdisco-users-requ...@lists.sourceforge.net

You can reach the person managing the list at
        netdisco-users-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:

   1. Re: discover weirdness (Eric Miller)
   2. Re: Catalyst 3850 neighbor discovery issues (Dan Augustine)
   3. Re: Catalyst 3850 neighbor discovery issues (Oliver Gorwits)
   4. Re: Catalyst 3850 neighbor discovery issues (Oliver Gorwits)
--- Begin Message --- 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
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users



--- End Message ---
--- Begin Message ---
Thank you Michael and Mark for your brutally honest assessment of the 3850.
During installation over the summer, we ran into a Cisco bug which would
not allow the fiber sfp to reestablish link when repatching cables.

In this case, I think this might be a Netdisco issue. Whenever I 'discover'
a 3850 I get the following warning in the log.  I do not see this on
non-3850s.

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_power_pkey"' at populate slice:
{
  admin => "true",
  class => "class0",
  ip => "10.170.10.20",
  module => 1,
  port => "GigabitEthernet1/0/17",
  power => 0,
  status => "searching"
} at /home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm line 563

I'm running version 3.19.

Any ideas?

Regards,
Dan




--
Dan Augustine
Senior Network Engineer
dan.august...@ousd.k12.ca.us
510-879-3000


On Mon, Dec 8, 2014 at 12:31 PM, Michael Butash <mich...@butash.net> wrote:

>  Those switches are kind of a basketcase in general it seems, I've got
> issues supposedly it supports qos mibs as well, and doesn't (still need to
> open a darn case).  I've heard similar stories to yours, and even cisco
> people have said not to bother trying the converged access wireless stuff
> as it's a mess.  Ugh.  It's just like ios, until you find all the
> broken/missing features beneath the cli.
>
> Other than that, I know cisco has been deprecating some of the older mibs,
> and since those are xe, might have on there like they did nexus a lot of
> things.  Maybe standardizing some new oid tree now for neighbors?
>
> I just deployed a lot for a customer, but haven't thrown much snmp against
> them to see how weird aside from trying to get cbqos and l2-qos mib data.
>
> -mb
>
>
>
> On 12/08/2014 01:00 PM, Mark Cooper wrote:
>
> I've got a similar situation. But I have one peer (no others) and it looks
> like it is on the same circle. This is an older version of ND2 and I should
> update it.
>
>
>
>
> I do know from experience that these switches aren't ready for prime time.
> There are a lot of issues with different things you'd expect to work. I.e.
> When I first installed them a little more than a year ago, HSRP didn't work
> yet! Are you kidding me? That feature has been around forever. So I had to
> stack them to get failover, and we can't do maintenance w/o an outage
> window now.
>
>
>
> So at this point, I'm pointing to the switch not enumerating SNMP
> properly, than I am thinking it's the tool. Or anything the tool can do to
> help. Not the same but there are issues with older Nexus code on those
> switches not supporting SNMP at all. So hopefully Cisco will have it
> resolved before too much longer or we can check the feature/bugs on
> Cisco.com for a newer version for the switch and maybe they've got it by
> now. I haven't looked in a while.
>
>
>
> Thanks,
> Mark Cooper
> Cooper's Communications
> m...@coopscommo.com
>
> _________________
>
>
> On Monday, December 08, 2014 10:55:21 AM Dan Augustine wrote:
>
> We have a sizable number of 3850 switches installed. Netdisco only shows
> neighbors when viewing from a non-3850 device.
>
>
>  All of these switches (regardless if they are stacked or standalone), do
> not show any neighbors from the device itself. Every 3850 switch is a lone
> island.
>
>
>
>
>  Is there a way to diagnose why this is happening?
>
>
>  Regards,
>
> Dan
>
>
>  PS: much less importantly, Netdisco is not picking up the hardware
> status for these switches.
>
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> 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, 
> FREEhttp://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Netdisco mailing 
> listnetdisco-users@lists.sourceforge.nethttps://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
> netdisco-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
>

--- End Message ---
--- Begin Message ---
Hi Dan,

On 2014-12-09 04:40, Dan Augustine wrote:
In this case, I think this might be a Netdisco issue. Whenever I
'discover' a 3850 I get the following warning in the log.  I do not
see this on non-3850s. 

As Eric said in another thread:

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.

regards,
oliver.




--- End Message ---
--- Begin Message ---

In fact this might be a different issue... I wasn't paying attention, sorry.

Dan's error is on the device_port_power table and Eric just fixed VLAN related code.

I'm interested that you're reporting this as a neighbor discovery issue but the error is on the PoE table entry.

Nevertheless the new SNMP::Info (3.23) is now released :-}

regards,
oliver.

On 2014-12-09 07:24, Oliver Gorwits wrote:
Hi Dan,

On 2014-12-09 04:40, Dan Augustine wrote:
In this case, I think this might be a Netdisco issue. Whenever I
'discover' a 3850 I get the following warning in the log.  I do not
see this on non-3850s. 

As Eric said in another thread:

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.

regards,
oliver.



------------------------------------------------------------------------------
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
netdisco-users@lists.sourceforge.net
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
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to