You should manually set the system clock or configure it by using Network Time Protocol (NTP). When the device is running, you can retrieve the OBFL data by using the show logging onboard privileged EXEC commands. If the device fails, contact your Cisco technical support representative to find out how to retrieve the data. When an OBFL-enabled device is restarted, there is a 10-minute delay before logging of new data begins. Fan Failures By default, the feature is disabled. When more than one of the fans fails in a field-replaceable unit (FRU) or in a power supply, the device does not shut down, and this error message appears: Multiple fan(FRU/PS) failure detected. System may get overheated.
Change fan quickly. The device might overheat and shut down. To enable the fan failures feature, enter the system env fan-fail-action shut privileged EXEC command. If more than one fan in the device fails, the device automatically shuts down, and this error message appears: Faulty (FRU/PS) fans detected, shutting down system! After the first fan shuts down, if the device detects a second fan failure, the device waits for 20 seconds before it shuts down. To restart the device, it must be power cycled. Possible Symptoms of High CPU Utilization Excessive CPU utilization might result in these symptoms, but the symptoms might also result from other causes, some of which are the following:
• Spanning tree topology changes • EtherChannel links brought down due to loss of communication • Failure to respond to management requests (ICMP ping, SNMP timeouts, slow Telnet or SSH sessions) • UDLD flapping • IP SLAs failures because of SLAs responses beyond an acceptable threshold • DHCP or IEEE 802.1x failures if the switch does not forward or respond to requests Troubleshooting the Software Configuration Fan Failures Troubleshooting the Software Configuration 9