Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
959
Views
0
Helpful
6
Replies

Certain Cisco devices are discovered as generic and missing Sys Object id

ENZO CAPPUCCITTI
Level 1
Level 1

‎03-08-2017 01:12 PM

I am a Cisco partner and I have a customer. We just configures themail collector version 2.6 we have done the discovery inventory  and uploads. The SNTC portal has the data. BUT some of the Cisco switches and routers discovered show up as generic devices and are missing their system object  I'd.  The models I have noticed are 3650 switches and 29XXL seri3s routers. Is their a way to resolve this issue?

Labels:
0 Helpful
6 Replies 6

antchris
Cisco Employee
Cisco Employee

‎03-09-2017 10:53 AM

Hello Enzo,

I have been researching your reported issue - kindly provide additional details as to the issue with screen captures. Please send them to the following address for further analysis -

sntc-support-community@cisco.com

Thank you

0 Helpful

usuee
Level 1
Level 1
In response to antchris

‎03-09-2017 02:28 PM

I am having similar issues.  I have a number of devices that are not returning the serial numbers and some that are showing as generic devices.   Most of the devices that are not working are Nexus based, 7010 and 1000v.  I have logged in to the collector and completed an snmpwalk against the device and have gotten quite a bit back.  I do not know the oid that is used for the serial number.  

Here is a cut and paste from the managed device report

Host Name Sys Object Id Device Family Product Model Serial Number Vendor Name OS Name OS Version Discovery Date/Time Source Reachable
(xxx.yyy.105.2) .1.3.6.1.4.1.9.1.282 LANSwitches cat6506 Cisco Systems Inc. IOS 12.2(33)SXI7 Tue, Mar 7, 2017 13:07:20 -0600 Collector TRUE
(xxx.yyy.111.4) .1.3.6.1.4.1.9.12.3.1.3.840 DataCenterSwitches cevChassisN1KV Cisco Systems Inc. NX-OS 5.2(1)SV3(1.5a) Tue, Mar 7, 2017 13:07:20 -0600 Collector TRUE
(xxx.yyy.111.5) DataCenterSwitches Unknown GenericDevice Tue, Mar 7, 2017 13:07:39 -0600 Collector FALSE
mod2-mse-core2 .1.3.6.1.4.1.9.12.3.1.3.612 DataCenterSwitches cevChassisN7Kc7010 Cisco Systems Inc. NX-OS 6.2(12) Tue, Mar 7, 2017 13:07:20 -0600 Collector TRUE
mod2-mse-core2 .1.3.6.1.4.1.9.12.3.1.3.612 DataCenterSwitches cevChassisN7Kc7010 Cisco Systems Inc. NX-OS 6.2(12) Tue, Mar 7, 2017 13:07:32 -0600 Collector TRUE
mod2-mse-core2 .1.3.6.1.4.1.9.12.3.1.3.612 DataCenterSwitches cevChassisN7Kc7010 Cisco Systems Inc. NX-OS 6.2(12) Tue, Mar 7, 2017 13:07:34 -0600 Collector TRUE
mod2-mse-core2 .1.3.6.1.4.1.9.12.3.1.3.612 DataCenterSwitches cevChassisN7Kc7010 Cisco Systems Inc. NX-OS 6.2(12) Tue, Mar 7, 2017 13:07:34 -0600 Collector TRUE
mod2-mse-core2 .1.3.6.1.4.1.9.12.3.1.3.612 DataCenterSwitches cevChassisN7Kc7010 Cisco Systems Inc. NX-OS 6.2(12) Tue, Mar 7, 2017 13:07:35 -0600 Collector TRUE
mod2-mse-core2 .1.3.6.1.4.1.9.12.3.1.3.612 DataCenterSwitches cevChassisN7Kc7010 Cisco Systems Inc. NX-OS 6.2(12) Tue, Mar 7, 2017 13:07:35 -0600 Collector TRUE
mod1-mse-core1 .1.3.6.1.4.1.9.12.3.1.3.612 DataCenterSwitches cevChassisN7Kc7010 Cisco Systems Inc. NX-OS 6.2(12) Tue, Mar 7, 2017 13:07:36 -0600 Collector TRUE
mod2-mse-core2 .1.3.6.1.4.1.9.12.3.1.3.612 DataCenterSwitches cevChassisN7Kc7010 Cisco Systems Inc. NX-OS 6.2(12) Tue, Mar 7, 2017 13:07:32 -0600 Collector TRUE
(xxx.yyy.111.6) .1.3.6.1.4.1.9.12.3.1.3.840 DataCenterSwitches cevChassisN1KV Cisco Systems Inc. NX-OS 5.2(1)SV3(1.5a) Tue, Mar 7, 2017 13:07:35 -0600 Collector TRUE
(xxx.yyy.111.147) .1.3.6.1.4.1.9.12.3.1.3.840 DataCenterSwitches cevChassisN1KV Cisco Systems Inc. NX-OS 5.2(1)SV3(1.5a) Tue, Mar 7, 2017 13:07:34 -0600 Collector TRUE
(xxx.yyy.58.8) Unknown GenericDevice Unknown GenericDevice Thu, Mar 2, 2017 10:41:05 -0600 Collector FALSE
(xxx.yyy.58.12) Unknown GenericDevice Unknown GenericDevice Thu, Mar 2, 2017 11:18:43 -0600 Collector FALSE
(xxx.yyy.135.227) Unknown GenericDevice Unknown GenericDevice Mon, Mar 6, 2017 15:58:49 -0600 Collector FALSE
fme-mod-vsm DataCenterSwitches Unknown GenericDevice Tue, Mar 7, 2017 13:07:39 -0600 Collector FALSE

The unreachable devices are reachable and when I do a discovery on them, they show up.  After a collection, they are back to generic devices.

This is a fresh reinstall of the collector.

0 Helpful

ENZO CAPPUCCITTI
Level 1
Level 1
In response to antchris

‎03-10-2017 01:44 PM

Here are the screen shots requested This is from my collector but i have a customer who is having the same issue but with 3650 switches. He has many in network (>50) but the same 5 show up as Generic devices.

Preview file
105 KB
Preview file
108 KB
0 Helpful

antchris
Cisco Employee
Cisco Employee
In response to ENZO CAPPUCCITTI

‎03-13-2017 08:51 AM

Enzo,

Thank you for providing screenshots - I would like to also request that you send a screenshot of the following in order to confirm additional details: 

In the CSPC WebUI -> Under 'Reports' -> 'Managed Devices...' Please include a screenshot of this report (to include all of the columns - the last one should be 'Reachable')


Please do not post your network/device information here on the community thread, instead use the following for submitting requested information - sntc-support-community@cisco.com


I have a good idea of why this may be happening but will be able to confirm once I can verify per this requested report.

Thanks

0 Helpful

antchris
Cisco Employee
Cisco Employee
In response to ENZO CAPPUCCITTI

‎03-13-2017 10:54 AM

Hi Enzo,

I was just analyzing the report I requested - I suspect the key in your issue is to ensure that the CSPC can successfully reach the devices in question. In looking at the provided report, I note that there are many such instances of unreachable devices - see the 'Reachable' column in the Managed Device report many are listed as 'false'. The way the CSPC discovers (manages) and collects (data collection) on network devices is through SNMP.  In your case, I would ask you to confirm the configured/saved SNMP related data from the CSPC WebUI ((Under 'Settings' -> 'Device Credentials') and to also verify on the configured device via CLI) to ensure that they are the same. Once you have verified the same SNMP credential(s), you will then need to perform a Discovery job and Data Collection job - once you have verified and performed the outlined, please let me know the results by sending me an updated version of the Managed Device report. 

Thanks

0 Helpful

ENZO CAPPUCCITTI
Level 1
Level 1
In response to antchris

‎03-14-2017 09:41 AM

I appreciate the response and the effort but i think you are still missing the point. I have a number of devices mainly 29XX routers that are discovered and manged. I have deleted them and rediscovered them perfectly but  they always show up as a Generic device in the collector and they are missing Information especially the Sys Object Id. It is a bug in the IOS of the  device or it bug in the collector? Also now my customer has various other issues; for example we cannot discover his 5508 WLC's. I checked the config on my 5508 and matched it to theirs and while mine is discover-able, his appears not to be. So far this customer is not impressed with the collector!  Other issues  I have a 3750 stack which when I run a DAV (device access verification) comes back successful but when i look at Collection Profile run summary all the CLI commands failed for that particular switch stack

0 Helpful
Customers Also Viewed These Support Documents