05-17-2022 02:35 AM
It looks like snmpd cannot start on ASA in version 9.16.3.3 (Firepower 4100 platform) and reboot of the ASA logical application or entire chassis doesn't help. Reconfiguration doesn't help too. ASA 9.16.3 wasn't tried yet. Let me know if somebody has this issue in any of latest versions. Previously a number of bugs were opened and fixed in older software for exactly same symptoms, but it looks like the issue is back again.
Cisco Adaptive Security Appliance Software Version 9.16(3)3
SSP Operating System Version 2.10(1.166)
ASA# show snmp-server stat
Unable to honour this request now.Please try again later.
ASA# show kernel proc | i snmpd|PID
PID PPID PRI NI VSIZE RSS WCHAN STAT RUNTIME GTIME CGTIME COMMAND
<nothing>
ASA# debug menu netsnmp 5
ASA# debug menu netsnmp 11
Netsnmp_get_snmp_pid:3046:command failed to get snmpd pid with error code 1
Reference:
Solved! Go to Solution.
06-03-2022 08:56 AM
Upgrade to ASA 9.16.3.14 (where few SNMP bugs were fixed including CSCwa89243) didn’t solve the issue, but it seems I found a workaround: it’s necessary to upgrade FXOS as well. I upgraded it from 2.10.1.166 to 2.10.1.179 and now snmpd starts up successfully on the blade.
It’s hard to tell if this is an FXOS bug or just an FXOS upgrade glitch. I mean that when we upgrade, we always upgrade FXOS first, so we initially upgraded from FXOS 2.6 to 2.10.1.166. Then we upgraded ASA from 9.12 to 9.16.3.3. It’s possible that something went wrong during FXOS 2.6 -> 2.10 upgrade, because ASA version was old (9.12) at that point, so, something wasn’t done properly during FXOS upgrade because ASA 9.12 SNMP architecture is old… New FXOS upgrade resolved the issue, because ASA was also new during FXOS upgrade.
06-03-2022 08:56 AM
Upgrade to ASA 9.16.3.14 (where few SNMP bugs were fixed including CSCwa89243) didn’t solve the issue, but it seems I found a workaround: it’s necessary to upgrade FXOS as well. I upgraded it from 2.10.1.166 to 2.10.1.179 and now snmpd starts up successfully on the blade.
It’s hard to tell if this is an FXOS bug or just an FXOS upgrade glitch. I mean that when we upgrade, we always upgrade FXOS first, so we initially upgraded from FXOS 2.6 to 2.10.1.166. Then we upgraded ASA from 9.12 to 9.16.3.3. It’s possible that something went wrong during FXOS 2.6 -> 2.10 upgrade, because ASA version was old (9.12) at that point, so, something wasn’t done properly during FXOS upgrade because ASA 9.12 SNMP architecture is old… New FXOS upgrade resolved the issue, because ASA was also new during FXOS upgrade.
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