Guest

Preview Tool

Cisco Bug: CSCup89391 - SNMP process crash

Last Modified

Dec 17, 2019

Products (8)

  • Cisco Nexus 7000 Series Switches
  • Cisco Nexus 7000 10-Slot Switch
  • Cisco Nexus 7000 4-Slot Switch
  • Cisco Nexus 7700 6-Slot Switch
  • Cisco Nexus 7700 18-Slot Switch
  • Cisco Nexus 7000 18-Slot Switch
  • Cisco Nexus 7700 10-Slot Switch
  • Cisco Nexus 7000 9-Slot Switch

Known Affected Releases

5.2(8b) 6.0(4)S20 6.2(8)

Description (partial)

Symptom:
Device sees a snmpd process crash.
Logs might show similar to:
2015 Mar 30 15:14:27.949 ipt-zbl103-m-fb-02 %$ VDC-1 %$ %SYSMGR-2-SERVICE_CRASHED: Service "snmpd" (PID 8266) hasn't caught signal 11 (core will be saved).
2015 Mar 30 15:14:38.354 ipt-zbl103-m-fb-02 %$ VDC-1 %$ 30 15:14:38 %KERN-0-SYSTEM_MSG: [ 4691.029783] Shutdown Ports.. - kernel
2015 Mar 30 15:14:38.358 ipt-zbl103-m-fb-02 %$ VDC-1 %$ 30 15:14:38 %KERN-0-SYSTEM_MSG: [ 4691.064149]  writing reset reason 16, snmpd hap reset - kernel

Conditions:
The issue appears to occur with DCNM discovery with new SNMP username authenticated through tacacs.

This is specific to a situation where the tacacs server is configured to give 2 roles to the username that is used
authenticate on the switches via dcnm.

I.e. tacacs gives the role "network-admin" AND "vdc-admin"
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.