Skip to main content

Command Palette

Search for a command to run...

Cisco Catalyst 9300 LED Guide: Diagnose System, Port, PoE, and Stack Issues Like a Pro

Published
3 min read
Cisco Catalyst 9300 LED Guide: Diagnose System, Port, PoE, and Stack Issues Like a Pro

If you manage Cisco 9300 switches, LED lights are your first line of feedback for detecting problems. A blinking amber system LED or an unusual port pattern can mean anything from PoE budget issues to a stack error. This guide shows how to interpret each LED, run the right CLI checks, and fix common problems without guesswork.

1. Check System and Power LEDs First

Problem: Switch not responding, SYST LED amber.

LED Meaning & Action:

  • Green: System OK → no action

  • Blinking Green: Booting or upgrading → wait for stable state

  • Amber: Fault (fan, PSU, over-temp) → run show environment all, check logs

Pro Tip: Always check SYST & PSU LEDs first before diving into port-level troubleshooting.

2. Port LEDs: STAT, SPEED, DUPLX

Problem: Intermittent connectivity or slow ports.

LED Patterns & Troubleshooting:

  • STAT Off: No link → confirm no shutdown and cabling

  • Blinking Green: Normal traffic → monitor utilization if network slow

  • Amber / Green-Amber Blink: STP block or CRC errors → check show interface Gi1/0/x counters errors

Speed & Duplex Notes:

  • 10/100/1000 Mb/s indicated by LED flash patterns

  • Use show interfaces status to confirm negotiated speed and duplex

3. PoE LED Interpretation

Problem: PoE devices like phones or cameras not powering.

  • Green: Port supplying power → normal

  • Blinking Amber: Fault / non-compliant device → check cable & device

  • Green/Amber Alternating: Insufficient PoE budget → adjust power allocation or upgrade PSU

CLI Command:

show power inline

Check which ports draw most PoE and adjust accordingly.

4. Stack & StackPower LEDs

Problem: Stack member amber, or devices not communicating in stack.

  • ACTV Green: Active member → OK

  • Blinking Green: Standby member → normal

  • Amber: Stack error → reseat cables, check stack priority

  • StackPower Amber: Insufficient power → verify PSU and ring

CLI Reference:

show switch stack
show switch stack-ports

5. Fans & Beacon LEDs

  • Fan Amber: Replace fan

  • Beacon Blue: Activated to locate switch → useful in racks

Pro Tip: Track fan health with show environment all regularly to avoid sudden hardware failure.

6. Step-by-Step Troubleshooting Flow

  1. Check System & Power LEDs first.

  2. Verify Port LEDs (STAT, SPEED, DUPLX).

  3. Inspect PoE LEDs if powered devices fail.

  4. Confirm Stack & StackPower LEDs for member and power ring health.

  5. Review Fan & Beacon LEDs to prevent hardware issues.

Conclusion

Cisco 9300 LEDs are more than just lights—they’re actionable indicators. By following this guide, network engineers can systematically diagnose issues, reduce downtime, and maintain a reliable network. Combine LED observation with CLI commands for precise troubleshooting.

For in-depth configuration guides and hardware support, visit router-switch.com.

More from this blog

R

RS Network Tips

29 posts