Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[EX] Meaning of log message - tsec3 cur_rx_stuck_at: 0x1640164 rx_stuck_count: 0



Article ID: KB21123 KB Last Updated: 27 Jul 2011Version: 1.0
This article explains about the meaning of log message -'tsec3 cur_rx_stuck_at: 0x1640164 rx_stuck_count: 0'. This message helps to understand tsec rx stuck condition. It is a harmless log message. 
 Meaning of the log message - tsec3 cur_rx_stuck_at: 0x1640164 rx_stuck_count: 0.
This message helps to understand tsec rx stuck condition, The count in the message identifies that the rx of tsec is not stuck. This is harmless.

  • tsec - It is a hardware device which stands for 'trispeed ethernet controller'
  • 3 - digit 3 means it is the 3 rd controller in the CPU
  • cur - current

Tsec Rx lockup occurs because of Tsec RX FIFO overflow. There is no way to avoid Tx lockup condition, so SW detects the lockup condition and recovers from there. To avoid any false detection, SW has the count of 3 as the threshold, before declaring Rx Lockup. This message is kept for better understanding of the system.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search