03-26-2012 11:24 PM - edited 03-04-2019 03:48 PM
Hi All,
We are using Cisco 4510R-E Switch with 2 WS-X45-SUP6-E in SSO.
The IOS which running on Chassis: cat4500e-ipbasek9-mz.122-54.SG1.bin
From past 3-4 Days we are observing High CPU in this chassis and the process which is consuming maximum CPU is GaliosObflFilesys process.
The output is here:
Yogesh_Cisco4500#sh processes cpu sorted
CPU utilization for five seconds: 59%/0%; one minute: 65%; five minutes: 65%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
80 3582290369 198427228 18053 47.67% 50.69% 50.72% 0 GaliosObflFilesy
Apart from this, we are getting below error messages continously on Console:
384665: Mar 27 08:41:46.933 IST: %C4K_SWITCHINGENGINEMAN-4-TCAMINTERRUPT: (Suppressed 380 times)flCam0 aPErr interrupt. errAddr: 0x1FD9 dPErr: 0 mPErr: 1 valid: 1
384666: Mar 27 08:41:54.538 IST: %C4K_L3HWFORWARDING-4-FLTCAMPARITYERROR: (Suppressed 766 times)FL Tcam Perr with no FwdEntry Hw index: 8152 Hw entry: Sw entry:
384667: Mar 27 08:42:16.972 IST: %C4K_SWITCHINGENGINEMAN-4-TCAMINTERRUPT: (Suppressed 384 times)flCam0 aPErr interrupt. errAddr: 0x1FD9 dPErr: 0 mPErr: 1 valid: 1
384668: Mar 27 08:42:47.006 IST: %C4K_SWITCHINGENGINEMAN-4-TCAMINTERRUPT: (Suppressed 393 times)flCam0 aPErr interrupt. errAddr: 0x1FD9 dPErr: 0 mPErr: 1 valid: 1
384669: Mar 27 08:42:54.571 IST: %C4K_L3HWFORWARDING-4-FLTCAMPARITYERROR: (Suppressed 763 times)FL Tcam Perr with no FwdEntry Hw index: 8152 Hw entry: Sw entry:
Also got the error messages are generated because of SUP in slot 5 which is in Active state:
Yogesh_Cisco4500#sh platform software obfl module all
1 : no obfl storage
2 : no obfl storage
3 : no obfl storage
4 : no obfl storage
5 : slot-5: messages=95200748 int-logged=80533419 int-dropped=0 dirty=yes
5 : slot-5: version=1 sector: size=4096 written=47182041 dirty=21
6 : remote supervisor
7 : no obfl storage
8 : no obfl storage
9 : no obfl storage
10 : no obfl storage
We got one Bug CSCsv17545 which is not hitting in our case since it is resolved 12.2(54)SG1.
Wanted to know whether it is Software issue or hardware and how to isolate the same.