05-02-2019 03:02 PM - edited 05-02-2019 03:03 PM
CSPC version: 2.8.1.3
Polling device: C6807-XL, SUP 6T
collectorlogin$ snmpwalk -v 2c -c ##### 10.##.##.###
Timeout: No Response from 10.##.##.###
Discovery Settings in CSPC
- SNMP Timeout (in sec): 5000
Inventory setting in CSPC
- snmpv2c timeout(ms): 10000
I can ping the box from CSPC. Other monitoring tools, SolarWinds and NetBrain, don't have the issue polling data from the device. I will appreciate if someone let me know a workaround.
05-02-2019 03:52 PM
Your manual snmpwalk may indicate an issue with your device ACLs or configured SNMP Community strings being used on the device and CSPC. Can you please verify those settings and see if it helps solve your issue.
Thank you,
Jarrett
05-02-2019 04:54 PM
I checked configurations one more time. There is no ACL in Loopback. I got some value this time:
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2018 by Cisco Systems, Inc.
Compiled Sun 04-Mar-18 07:00 by prod_rel_team
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.1934
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1587398108) 183 days, 17:26:21.08
SNMPv2-MIB::sysContact.0 = STRING: i#######@goldcorp.com
SNMPv2-MIB::sysName.0 = STRING: #############
SNMPv2-MIB::sysLocation.0 = STRING: ##########
SNMPv2-MIB::sysServices.0 = INTEGER: 78
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
IF-MIB::ifNumber.0 = INTEGER: 591
IF-MIB::ifIndex.1 = INTEGER: 1
IF-MIB::ifIndex.2 = INTEGER: 2
IF-MIB::ifIndex.3 = INTEGER: 3
IF-MIB::ifIndex.4 = INTEGER: 4
IF-MIB::ifIndex.5 = INTEGER: 5
I checked the credential in CSPC as well. I ran a discovery during ran snmpwalk in the terminal. however, it showed me the same result, Incomplete discovery.
From the switch:
groupname: ####### security model:v2c
contextname: <no context specified> storage-type: permanent
readview : v1default writeview: <no writeview specified>
notifyview: *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF.F
row status: active
interface Loopback0
description Loopback
ip address ######### 255.255.255.255
end
There are ACL configurations that are not related to this matter. Let me know if you need more information to troubleshoot.
Thanks.
05-03-2019 07:16 AM - edited 05-03-2019 07:17 AM
In the discovery settings can you try increasing the max device discovery to 600 under Settings -> Discovery Settings
05-03-2019 11:10 AM
I followed your instruction. However, it showed me the same message. I did:
1. Ran snmpwalk in CSPC terminal
[collectorlogin@MRKCCSPC01 ~]$ snmpwalk -v 2c -c ####### 10.#######
SNMPv2-MIB::sysDescr.0 = STRING: Cisco IOS Software, s6t64 Software (s6t64-IPSERVICESK9-M), Version 15.5(1)SY1, RELEASE SOFTWARE (fc6)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2018 by Cisco Systems, Inc.
Compiled Sun 04-Mar-18 07:00 by prod_rel_team
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.1934
--omitted---
2. Re-added Device Credentials
3. Checked Discovery Settings
4. Checked Discovery Schedule Options
Protocol: snmvpv2c and v1
Discovery Options: Enable Loopback
SNMP timeout: 3 -> 5000
Service Name: 'SMART….Care' selected
I got more device information:
The missing part in View Managed Devices list are Host Name, device Family, and Serial Number.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide