• Temperature—Temperature of a standalone Switch or a switch stack member.
• Uptime data—Time when a standalone Switch or a switch stack member starts, the reason the Switch
restarts, and the length of time the Switch has been running since it last restarted.
• Voltage—System voltages of a standalone Switch or a switch stack member.
You should manually set the system clock or configure it by using Network Time Protocol (NTP).
When the Switch is running, you can retrieve the OBFL data by using the show logging onboard privileged
EXEC commands. If the Switch fails, contact your Cisco technical support representative to find out how to
retrieve the data.
When an OBFL-enabled Switch is restarted, there is a 10-minute delay before logging of new data begins.
Related Topics
Configuring OBFL, on page 1646
Displaying OBFL Information
Possible Symptoms of High CPU Utilization
Excessive CPU utilization might result in these symptoms, but the symptoms might also result from other
causes:
•
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
Layer 3 switches:
•
Dropped packets or increased latency for packets routed in software
•
BGP or OSPF routing topology changes
•
HSRP flapping
Note
Consolidated Platform Configuration Guide, Cisco IOS Release 15.2(4)E (Catalyst 2960-X Switches)
1631
Information About Troubleshooting the Software Configuration
To Next Page
Loading...
Need help?
General
