Support Support Downloads Knowledge Base Case Manager My Juniper 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

EX8208 and EX8216 Log message: "tsec3 cur_rx_stuck_at: 0x1a001a0 rx_stuck_count: 0"

0

0

Article ID: KB24627 KB Last Updated: 04 Mar 2017Version: 2.0
Summary:
This article provides information about the log message "tsec3 cur_rx_stuck_at: 0x1a001a0 rx_stuck_count: 0",  and how to block the log message from filling up the log file, on local device, or on the syslog server. This is a harmless message.

Symptoms:
The following message is seen continuously in the log file :

Apr 17 00:35:19 JNC82DC2 /kernel: tsec3 cur_rx_stuck_at: 0x1a001a0 rx_stuck_count: 0
Apr 17 01:28:23 JNC82DC2 /kernel: tsec3 cur_rx_stuck_at: 0x7e007e rx_stuck_count: 0
Apr 17 04:04:32 JNC82DC2 /kernel: tsec3 cur_rx_stuck_at: 0x1120112 rx_stuck_count: 0

Cause:

Solution:
The "tsec3" log message helps to understand tsec rx stuck condition and was originally left in the earlier JUNOS releases for additional logging details. The "rx_stuck_count: 0" (count of zero) indicates that the tsec was not stuck so this message is informational onlyharmless.  This message is removed from all JUNOS releases starting from 11.1R1 and later.

Apr 17 00:35:19 JNC82DC2 /kernel: tsec3 cur_rx_stuck_at: 0x1a001a0 rx_stuck_count: 0
Apr 17 01:28:23 JNC82DC2 /kernel: tsec3 cur_rx_stuck_at: 0x7e007e rx_stuck_count: 0
Apr 17 04:04:32 JNC82DC2 /kernel: tsec3 cur_rx_stuck_at: 0x1120112 rx_stuck_count: 0

NOTE: This log message is specific to the EX8208 and EX8216 platforms only.

Filter the Event Message:

Issue the following command to filter the event messages from being sent to syslog server:

user@switch #set system syslog host 10.1.104.25 match "!(.* tsec3 cur_rx_stuck_at.*)"

To filter the message from getting into the logs of the EX Switch use the following command:

user@switch #set system syslog file messages match "!(.* tsec3 cur_rx_stuck_at.*)"


NOTE: This message has been removed in the following JUNOS releases:

  • 10.0R4
  • 10.2R4
  • 10.3R4
  • 10.4R1
  • All later JUNOS releases
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