Error on Cat 4500 Switch!!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2009 01:43 PM - edited 03-06-2019 07:06 AM
Hi,
I am getting this error on my cat 4500 switch.:
Jul 4 10:11:11: %SYS-3-TIMERNEG: Cannot start timer (0x12589A8) with negative offset (-1983561290). -Process= "Cat4k Mgmt HiPri", ipl= 0, pid= 51
-Traceback= 10B45FA8 10B897F4 116B11C0 119ABC60 11DEA2D0 1177CA8 10E191D811A181D8 118ABABD 11B26B1D 1111ABD1 11B22D24 11B22D8D 118D6614 118D686D 118D6B44 1181712D
I looked at the bugs but could not find anything.
Software running is:12.2(52)SG
Any help would be greatly appriciated.
Thanks
Neha.
- Labels:
-
Other Switching
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2009 10:10 AM
Hi,
I would contact TAC for that kind of error (according to http://www.cisco.com/en/US/docs/ios/12_0/system/messages/emswitch.html, which mentions
'%SYS-3-TIMERNEG : Cannot start timer ([hex]) with negative offset ([dec])
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.')
I know, not the answer you would have expected, but there seem to be less options...
Regards,
uk.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2009 11:20 AM
Are you getting this message AFTER you configure something using the "interface range"?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2009 02:35 AM
Yes, After I apply the cmds the error msg pops up.
But why is the error comes while configuring the vlan on interface range cmd???
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2009 07:42 AM
jbrenesj,
This should be internal bug could you please check this and update me.
I would be very thankfull to you.
Thanks
Neha.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2009 10:27 AM
I have seen two similar cases now but unfortunately this type of condition is usually triggered on the standby supervisor engine when issuing
commands within an interface range and this condition does not always repeat itself and it does not affect performance.
There is no bug yet but I suggest monitoring and if the issue is persistent you might contact TAC for further investigation.
