Can't find what you need?


• Ask the Community
• Create a Case
Reset Search
 

 

Article

What does the logging buffer message "Tx queue for interface ge.x.x is in stalled mode" mean and what causes this?

« Go Back

Information

 
TitleWhat does the logging buffer message "Tx queue for interface ge.x.x is in stalled mode" mean and what causes this?
Question
  • What does the logging buffer message  "Tx queue for interface ge.x.x is in stalled mode" mean and what causes this?
  • Logging Buffer example messages: 
<161>May 18 07:40:19 0.0.0.0-1 TXQMONITO[412174928]: txq_monitor.c(507) 220 %% Tx queue for interface ge.2.12 is in stalled mode
<161>May 18 07:40:27 0.0.0.0-1 TXQMONITO[412174928]: txq_monitor.c(518) 221 %% Interface ge.2.12 is enabled to ignore pause as sequential transmit failures reached ignore pause threshold 
 
Environment
  • Securestack
  • Firmware version 06.42.xx and later
Answer
 
  • Stalled transmit queues are caused by a duplex mismatch, excessive pause frames, or a hardware issue with cabling or NIC
  • Used to assist isolate and identify excessive traffic, pause frame issue and/or possible physical media failures
  • It can be see that a port going into a stalled state can be some type of looped device, which is causing high packet counters. 
Additional notes
TXQMonitoring is enabled by default.
The message will include the port having an issue, the port will be in a down/disabled state.

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255