Extreme SLX-OS Troubleshooting Guide, 20.1.1
>
Troubleshooting procedures
>
Troubleshooting standard issues
>
SSH or Telnet operation into the device fails
> Checking for overloaded CPU
Published February 2020
Search this document
Print this page
Email this page
View PDF
Previous
Next
Preface
Text Conventions
Documentation and Training
Getting Help
Providing Feedback
About this document
Supported Hardware
Regarding Ethernet interfaces and chassis devices
Troubleshooting procedures
Troubleshooting overview
Gathering troubleshooting information
Capturing supportSave data
Using information resources
Using a troubleshooting methodology
Understanding troubleshooting hotspots
ACL limits issues
Avoiding oversubscription
Identifying the congestion bottleneck
Congestion mitigation
Licensing
Load balancing distribution
Selecting the MTU
Troubleshooting standard issues
Account and Password Recovery
Recover the admin password from the root account
Root account and password recovery
(DNX devices) Recover the root login account
(XGS devices) Recover the root login account
(DNX devices) Recover the root password
(XGS devices) Recover the root password
CPU use is unexpectedly high
Heavy disk utilization
Packets are dropped in hardware
Verifying packets dropped because of high-latency end device
Verifying the data path
Checking for noise on an optical line
Ping fails
QoS configuration causes tail drops
SNMP MIBs report incorrect values
SNMP traps are missing
SSH or Telnet operation into the device fails
Verifying the status of the management port
Checking for a deny ACL
Checking for overloaded CPU
Traffic is not being forwarded
Upgrade fails
Upgrade failure prior to device reload
Upgrade failure during device reload
Using troubleshooting and diagnostic tools
Tracing a route with the trace-l2 command
Using show commands
Using debug and system diagnostic commands
Traffic mirroring
Supported NTP Regions and Time Zones
Africa
America
Antarctica
Arctic
Asia
Atlantic
Australia
Europe
Indian
Pacific
Checking for overloaded CPU
An overloaded device CPU can prevent SSH or Telnet access.
See
CPU use is unexpectedly high
.
