10-09-2013 09:54 PM - edited 03-07-2019 03:57 PM
Hi all ,
we r having Cat 4006 switch with SUP 2 . It is having more CPU util and below is the output ,
CPU utilization for five seconds: 81.91%
one minute: 81.08%
five minutes: 81.02%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
--- ----------- ---------- -------- ------- ------- ------- --- ---------------
1 2933730834 0 0 18.09% 18.92% 18.98% -2 Kernel and Idle
2013 Oct 10 10:01:18 IST +05:30 %IP-6-UDP_SOCKOVFL:UDP socket overflow from Source IP: 10.201.53.201, Destination port: 161
193 3542538145 3562126410 12557 46.35% 45.95% 45.55% 0 Packet forwardi
194 2340721807 1077747100 10237 5.67% 5.99% 5.54% 0 Switching overh
195 3261557550 2677388342 32532 13.52% 13.62% 13.65% 0 Admin overhead
> (enable) 2013 Oct 10 10:01:18 IST +05:30 %SYS-4-P2_WARN: 1/Ast
Moreover We are getting below error logs in console ,
2013 Oct 10 10:02:07 IST +05:30 %SYS-4-P2_WARN: 1/Astro 5-5(5/33-40) - management request timed out.
2013 Oct 10 10:02:23 IST +05:30 %SYS-4-P2_WARN: 1/Astro 4-5(4/33-40) - management request timed out
2013 Oct 10 10:03:11 IST +05:30 %SYS-4-P2_WARN: 1/Astro 3-5(3/33-40) - management request timed out.
Show version :
Mod Port Model Serial # Versions
--- ---- ------------------ -------------------- ---------------------------------
1 2 WS-X4013 Hw : 3.2
Gsp: 8.4(11.0)
Is it Related to SUP engine failure problem ?
Kindly suggest,
Thanks!,
Regards,
Vijay
Solved! Go to Solution.
10-13-2013 12:08 PM
Hello Vijay
If the errors are seen only on one Astro (or other stub ASIC) on one module, and a layer 2 loop is not occurring, the problem is most likely a faulty SERDES component on either the Supervisor or Line Card. Check if those symthopms are also experienced in your network, if the error messages is always point to Astro 5 on Module 3, 4 and 5, then either the fifth SERDES component on each module or the fourth SERDES component on the Supervisor is faulty.
A faulty SERDES component can cause intermittent connectivity for control traffic and data traffic to the Astro, resulting in timeouts.
Typically, however, the error message will be continuously displayed if the SERDES is faulty.
I suggest the following steps:
1- Set diagnostics level to complete.
2- Reset the linecard and supervisor.
3- Check the diagnostics results command and consider a rma based on the outputs.
Regards.
Wilson B
10-13-2013 12:08 PM
Hello Vijay
If the errors are seen only on one Astro (or other stub ASIC) on one module, and a layer 2 loop is not occurring, the problem is most likely a faulty SERDES component on either the Supervisor or Line Card. Check if those symthopms are also experienced in your network, if the error messages is always point to Astro 5 on Module 3, 4 and 5, then either the fifth SERDES component on each module or the fourth SERDES component on the Supervisor is faulty.
A faulty SERDES component can cause intermittent connectivity for control traffic and data traffic to the Astro, resulting in timeouts.
Typically, however, the error message will be continuously displayed if the SERDES is faulty.
I suggest the following steps:
1- Set diagnostics level to complete.
2- Reset the linecard and supervisor.
3- Check the diagnostics results command and consider a rma based on the outputs.
Regards.
Wilson B
10-13-2013 12:27 PM
The Catalyst 4006 and Supervisor 2 were end of sales in 2004 and last date of support was May 2010 so an RMA will not be possible. (Reference)
If indeed hardware failure is the issue it may be time to upgrade this very old switch.
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