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

[QFX] What does 'brcm_rt_ip_mc_ipmc_bdvlan_install:1962 Multicast stat ctr attach success ' mean?

0

0

Article ID: KB35742 KB Last Updated: 25 Apr 2020Version: 1.0
Summary:

This article explains the meaning, trigger and impact of the following message on the QFX switches:

'brcm_rt_ip_mc_ipmc_bdvlan_install:1962 Multicast stat ctr attach success <xxxxxxxx>'
Symptoms:

Following are often seen in the log messages:

Feb 14 19:06:05 2020  QFX5X00 fpc0 brcm_rt_ip_mc_ipmc_bdvlan_install:1962 Multicast stat ctr attach success 6307983 
Feb 14 19:06:05 2020  QFX5X00​ fpc0 brcm_rt_ip_mc_ipmc_bdvlan_install:1962 Multicast stat ctr attach success 6307862 
Feb 14 19:06:05 2020  QFX5X00​ fpc0 brcm_rt_ip_mc_ipmc_bdvlan_install:1962 Multicast stat ctr attach success 6307928 
Feb 14 19:06:05 2020  QFX5X00​ fpc0 brcm_rt_ip_mc_ipmc_bdvlan_install:1962 Multicast stat ctr attach success 6307968 
Feb 14 19:06:05 2020  QFX5X00​ fpc0 brcm_rt_ip_mc_ipmc_bdvlan_install:1962 Multicast stat ctr attach success 6307869 
Feb 14 19:06:05 2020  QFX5X00​ fpc0 brcm_rt_ip_mc_ipmc_bdvlan_install:1962 Multicast stat ctr attach success 6307981
Cause:

These log messages can be observed at a very high rate since multicast stats support was introduced and the trigger is multicast stats counter retrieval. This is specific to qfx5100, qfx5110, qfx5200 and qfx5120.

Solution:

With the multicast stats counter support was introduced, two messages were introduced to indicate the success and failure of the multicast stat counter attach, 'Multicast stat ctr attach success' and 'Multicast stat ctr attach failed'.

When the multicast traffic stats collection is done, the device attempts to retrieve the statistics of success and failure and is supposed to log the failure counters to the log messages as error. However, the success counters were also considered as error messages and are being logged on the device. Instead, these were supposed to be logged only when debugged for traces.

As mentioned, these logs indicate success counters and are informational messages without any functional impact on the device as they are mistakenly categorized as error logs.This has been fixed in the following releases:

  • junos:14.1X53-D28
  • junos:14.1X53-D40
  • junos:15.1R5
  • junos:16.1R3

You can also suppress repeating non-impacting messages. For instructions, refer to KB9382 - How to prevent certain syslog messages from being written to the log file.

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