05-22-2020 01:26 AM
Good day everybody,
yesterday I had an outage on a WS-C4510R+E.
syslog showed that the fantray stoped working:
Fan tray has failed | C4K_IOSMODPORTMAN | FANTRAYBAD |
Too few working fans in fan tray, the chassis will overheat. If not resolved, in 0 minutes 30 seconds the chassis will power down | C4K_CHASSIS | INSUFFICIENTFANSDETECTEDPOWERDOWN |
Failed to read system fan tray status register from hardware | C4K_CHASSIS | FANTRAYREADFAILED |
after power off and on it booted normaly. Everything is working so far. But now I wonder what to do next, and I try to determine the likelyhood of this to happen again.
switch#show environment status fantray
Fantray : Good
Fantray removal timeout : 30
Power consumed by Fantray : 255 Watts
unfortunately I wasn't able to find any reference value for the power consumption of the fantray, to see if it needs a cleaning or it's just old and dying....
Thanks!
Solved! Go to Solution.
05-24-2020 11:50 PM
05-22-2020 01:42 AM - edited 05-22-2020 01:44 AM
Post the complete output to the following command:
sh log on summary start 0:0:0 20 may 2020
05-22-2020 02:11 AM - edited 05-22-2020 02:17 AM
Thanks Leo, here is the requested output.
Switch#sh log on summary start 0:0:0 20 may 2020
PID: WS-C4510R+E , VID: 10 , SN: <SN> -------------------------------------------------------------------------------- UPTIME SUMMARY INFORMATION -------------------------------------------------------------------------------- First customer power on : 12/27/2012 22:51:15 Total uptime : 7 years 12 weeks 5 days 1 hours 15 minutes Total downtime : 0 years 8 weeks 2 days 9 hours 11 minutes Number of resets : 28 Number of slot changes : 3 Current reset reason : 0x9 Current reset timestamp : 05/21/2020 22:17:38 Current slot : 6 Current subslot : 0 Current uptime : 0 years 0 weeks 0 days 12 hours 0 minutes -------------------------------------------------------------------------------- Reset | | Reason | Count | -------------------------------------------------------------------------------- No historical data to display -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ENVIRONMENT SUMMARY INFORMATION -------------------------------------------------------------------------------- MM/DD/YYYY HH:MM:SS Ins count Rem count ------------------------------------------------------------ VID PID TAN Serial No -------------------------------------------------------------------------------- No environment summary data to display -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- TEMPERATURE SUMMARY INFORMATION -------------------------------------------------------------------------------- Number of sensors : 7 Sampling frequency : 1 minutes Maximum time of storage : 10 minutes -------------------------------------------------------------------------------- Sensor | ID | Maximum Temperature 0C -------------------------------------------------------------------------------- Stub A 0 38 Stub B 1 34 XPP 2 44 VFE 3 54 NFE 4 44 CPU 5 51 FPGA 6 35 -------------------------------------- Temp Sensor ID 0C 1 2 3 4 5 6 7 -------------------------------------- 1 15y 15y 15y 15y 15y 15y 15y 20 0m 149m 0m 0m 0m 0m 0m 21 0m 21h 0m 0m 0m 0m 0m 22 0m 82h 0m 0m 0m 0m 0m 23 0m 139h 0m 0m 0m 0m 0m 24 0m 188h 0m 0m 0m 0m 0m 25 40m 400h 0m 0m 0m 0m 0m 26 40h 218h 0m 0m 0m 0m 18m 27 88h 108m 0m 0m 0m 0m 96h 28 191h 0m 0m 0m 0m 0m 157h 29 208h 0m 0m 0m 0m 0m 235h 30 380h 0m 0m 0m 0m 0m 409h 31 145h 0m 0m 0m 0m 0m 155h 32 10m 0m 0m 0m 0m 0m 10m 34 0m 14m 0m 0m 366m 0m 0m 35 0m 0m 0m 0m 46h 0m 14m 36 0m 0m 0m 0m 126h 0m 0m 37 0m 0m 0m 0m 164h 0m 0m 38 14m 0m 56h 0m 274h 981m 0m 39 0m 0m 157h 0m 339h 64h 0m 40 0m 0m 160h 0m 97h 96h 0m 41 0m 0m 313h 0m 0m 202h 0m 42 0m 0m 343h 40h 0m 357h 0m 43 0m 0m 23h 103h 0m 288h 0m 44 0m 0m 14m 170h 14m 30h 0m 45 0m 0m 0m 291h 0m 0m 0m 46 0m 0m 0m 386h 0m 0m 0m 47 0m 0m 0m 63h 0m 0m 0m 51 0m 0m 0m 0m 0m 14m 0m 54 0m 0m 0m 14m 0m 0m 0m -------------------------------------------------------------------------------- INTERRUPT SUMMARY INFORMATION -------------------------------------------------------------------------------- Name | ID | Offset | Bit | Count -------------------------------------------------------------------------------- No historical data to display -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ERROR MESSAGE SUMMARY INFORMATION -------------------------------------------------------------------------------- Facility-Sev-Name | Count | Persistence Flag MM/DD/YYYY HH:MM:SS -------------------------------------------------------------------------------- No historical data to display --------------------------------------------------------------------------------
its a dual sup setup, currently the secondary sup is active:
Switch#sh redundancy
Redundant System Information : ------------------------------ Available system uptime = 13 hours, 30 minutes Switchovers system experienced = 3 Standby failures = 0 Last switchover reason = user_forced Hardware Mode = Duplex Configured Redundancy Mode = Stateful Switchover Operating Redundancy Mode = Stateful Switchover Maintenance Mode = Disabled Communications = Up Current Processor Information : ------------------------------ Active Location = slot 6 Current Software state = ACTIVE Uptime in current state = 12 hours, 54 minutes Peer Processor Information : ------------------------------ Standby Location = slot 5 Current Software state = STANDBY HOT Uptime in current state = 12 hours, 43 minutes
Since I had the following messages on the primary sup:
IOSDLOG: eip_os_info_cempmempoolentry_instance_ctx_init: ../iosd/providers/os_info_p/cempmempoolentry_crudx_cb.c: 63: mempool 1 wasn't found in the list IOSDLOG: process_get_oper_prop_values: ../VIEW_ROOT/cisco.comp/nova-libeiipc/eicore_provider.c: 249: provider returned error (rc=102, err=Getter for cempMemPoolType returned error )
oh in temperature history data, I could not find a rise prior the incident.
05-22-2020 04:00 AM
Nothing odd from the output:
Can you post the output to the following commands:
sh version dir crashinfo: sh log on uptime detail
05-24-2020 10:30 PM - edited 05-24-2020 10:31 PM
Good Morning Leo, thanks again for taking the time!
sh log on uptime details:
swith#sh log on uptime detail -------------------------------------------------------------------------------- UPTIME SUMMARY INFORMATION -------------------------------------------------------------------------------- First customer power on : 12/27/2012 22:51:15 Total uptime : 7 years 13 weeks 0 days 22 hours 15 minutes Total downtime : 0 years 8 weeks 2 days 9 hours 11 minutes Number of resets : 28 Number of slot changes : 3 Current reset reason : 0x9 Current reset timestamp : 05/21/2020 22:17:38 Current slot : 6 Current subslot : 0 Current uptime : 0 years 0 weeks 3 days 9 hours 0 minutes -------------------------------------------------------------------------------- Reset | | Reason | Count | -------------------------------------------------------------------------------- No historical data to display -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- UPTIME CONTINUOUS INFORMATION -------------------------------------------------------------------------------- Time Stamp | Reset | Uptime MM/DD/YYYY HH:MM:SS | Reason | years weeks days hours minutes -------------------------------------------------------------------------------- 12/27/2012 22:51:15 0x0 0 0 0 0 0 12/27/2012 22:58:50 0x9 0 0 0 0 0 01/12/2013 01:00:59 0x0 0 0 0 0 20 02/20/2013 13:24:42 0x0 0 0 0 0 0 02/21/2013 11:09:14 0xE 0 0 0 14 0 02/22/2013 00:34:20 0x9 0 0 0 13 0 02/22/2013 05:25:15 0x9 0 0 0 4 0 02/22/2013 05:50:41 0x0 0 0 0 0 0 02/22/2013 06:00:48 0x0 0 0 0 0 0 02/24/2013 04:50:21 0x0 0 0 0 0 0 06/30/2013 12:09:56 0x9 0 17 6 22 0 09/01/2013 09:25:27 0xE 0 8 6 21 0 09/01/2013 11:39:46 0x9 0 0 0 2 0 09/01/2013 16:14:13 0x9 0 0 0 4 0 09/28/2013 15:07:15 0x0 0 3 5 22 0 10/14/2013 16:10:30 0x9 0 2 2 0 0 10/24/2013 15:06:05 0xE 0 1 2 22 0 10/24/2013 15:26:59 0xE 0 0 0 0 0 10/24/2013 15:35:26 0x9 0 0 0 0 0 10/24/2013 17:53:14 0x9 0 0 0 2 0 01/11/2014 16:22:22 0x0 0 11 1 18 0 01/07/2015 17:26:34 0x0 0 51 4 0 0 02/21/2015 16:12:44 0x0 0 6 2 22 0 11/05/2016 18:40:07 0x0 1 36 5 19 0 11/05/2016 19:33:27 0x0 0 0 0 0 25 12/10/2016 15:40:12 0x0 0 4 6 16 0 05/21/2020 21:46:34 0x0 3 23 2 3 0 05/21/2020 22:17:38 0x9 0 0 0 0 30 --------------------------------------------------------------------------------
dir crashinfo: only contains files from 2012 /2013...
sh version:
Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500e-UNIVERSALK9-M), Version 03.04.02.SG RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2013 by Cisco Systems, Inc. Compiled Thu 05-Sep-13 19:06 by prod_rel_team Cisco IOS-XE software, Copyright (c) 2005-2010, 2012 by cisco Systems, Inc. All rights reserved.... ROM: 15.0(1r)SG7 Switch uptime is 3 days, 9 hours, 42 minutes Uptime for this control processor is 3 days, 9 hours, 6 minutes System returned to ROM by SSO Switchover System restarted at 22:16:24 summer Thu May 21 2020 System image file is "bootflash:cat4500e-universalk9.SPA.03.04.02.SG.151-2.SG2.bin" Jawa Revision 7, Snowtrooper Revision 0x0.0x1C Last reload reason: Reload command This product contains cryptographic features.....
return this product immediately. License Information for 'WS-X45-SUP7-E' License Level: ipbase Type: Permanent Next reboot license Level: ipbase cisco WS-C4510R+E (MPC8572) processor (revision 10) with 2097152K/20480K bytes of memory. Processor board ID <SN> MPC8572 CPU at 1.5GHz, Supervisor 7 Last reset from Reload 7 Virtual Ethernet interfaces 192 Gigabit Ethernet interfaces 8 Ten Gigabit Ethernet interfaces 511K bytes of non-volatile configuration memory. Configuration register is 0x2102
05-24-2020 11:50 PM
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