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: Catalyst 3850 neighbor discovery issues (Michael Butash) 2. discover weirdness (Joseph Bernard) 3. Re: discover weirdness (Mark Cooper)
--- Begin Message ---
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
[email protected]
_________________
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, 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’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.
--- End Message ---
--- Begin Message ---This error looks like it's already populated this record in the database and it is trying to do it again. Seems like you could smoke the 6500 out of the db altogether and get it to discover the 6500 again. If that 1st pass works, it makes me think that you'll see the same error again on the next run. What's the version of ND2 and SNMP? Thanks,Mark Cooper *Cooper's Communications* [email protected] -------------------- /This e-mail and the information it contains is privileged and/or confidential. It is for the intended addressee(s) only. Any unauthorized use, copying, distribution, disclosure or retention of this e-mail, or any information it contains, is prohibited and could be a criminal offense under the 'insert applicable Act here'. If you are not an intended recipient, please destroy this message and notify the sender immediately./ > 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 ---
------------------------------------------------------------------------------ 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
