08-09-2012 12:39 AM - edited 03-07-2019 08:14 AM
Hi,
I am having a lab switch. Recently I am getting
"%SCHED-3-SEMLOCKED: SNMP ENGINE attempted to lock a semaphore, already locked by itself" message and the switch has started to hang a little bit. I just want to know what this log means
and how to trouble shoot.
I'm using C3750, version 12.2(25)SEE3
Thanks,
Sri
Solved! Go to Solution.
08-09-2012 01:05 AM
Hi,
The traceback may vary.
Conditions: This symptom is observed if the snmp engine is shut down during the processing of an snmpset. Entering the command no snmp-server in config mode is one way that the snmp engine can be shut down. The likely hood of the snmp engine being shut down during the processing of an snmpset is very small.
Workaround: There is no workaround other than to reboot the device.
Regards
Please rate if it helps.
08-09-2012 03:59 AM
Hi Srikant,
It's an IOS defect (most likely CSCse97398) that is why the device is displaying this behavor. A reload is a workaround, but the issue may return. To resolve this issue you must upgrade to 12.2(35)SE or greater which contains the fix for the above defect.
HTH
Anthony
08-09-2012 12:45 AM
Hi Srikanth,
Just reboot the device will solve this problem.
and this is the only way.
REgards
Please rate if it helps.
08-09-2012 12:55 AM
Thanks Sandeep. Also can you explain what does this syslog means:
%SCHED-3-SEMLOCKED: SNMP ENGINE attempted to lock a semaphore, already locked by itself
and why the device started generating this syslog?
08-09-2012 01:05 AM
Hi,
The traceback may vary.
Conditions: This symptom is observed if the snmp engine is shut down during the processing of an snmpset. Entering the command no snmp-server in config mode is one way that the snmp engine can be shut down. The likely hood of the snmp engine being shut down during the processing of an snmpset is very small.
Workaround: There is no workaround other than to reboot the device.
Regards
Please rate if it helps.
08-09-2012 03:59 AM
Hi Srikant,
It's an IOS defect (most likely CSCse97398) that is why the device is displaying this behavor. A reload is a workaround, but the issue may return. To resolve this issue you must upgrade to 12.2(35)SE or greater which contains the fix for the above defect.
HTH
Anthony
08-09-2012 06:38 AM
Thanks Sandeep and answanso its really helpful.
I tried to look more into this issue and I have found another bug related to this : CSCti85075
could this be associated to my ios?
and can you explain traceback in detail. I know a very little about it. It would be great help if you guys can explain it in detail.
08-09-2012 06:42 AM
Hi Srikant,
CSCti85075 isn't fixed for your train of IOS.
Thanks
Anthony
08-09-2012 06:47 AM
HI Srikant,
Have you tried to reboot the device??
Regards
08-09-2012 06:24 PM
Yes rebooting the device solves the issue. Thanks Sandeep, Anthony
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