Support Support Downloads Knowledge Base Service Request 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

Syslog message: BRCM_NH-,brcm_get_vlan_token_from_intf():Invalid interface index for ifl

0

0

Article ID: KB31766 KB Last Updated: 30 May 2017Version: 1.0
Summary:

This article describes the cause and solution for the syslog message: BRCM_NH-, brcm_get_vlan_token_from_intf(),2014:Invalid interface index for ifl 551

Symptoms:

Example syslog messages:

fpc6 BRCM_NH-,brcm_get_vlan_token_from_intf(),2014:Invalid interface index for ifl 892
fpc6 BRCM_NH-,brcm_get_vlan_token_from_intf(),2014:Invalid interface index for ifl 892
fpc0 BRCM_NH-,brcm_get_vlan_token_from_intf(),2014:Invalid interface index for ifl 893
fpc0 BRCM_NH-,brcm_get_vlan_token_from_intf(),2014:Invalid interface index for ifl 893
Cause:

This message can be triggered on a VC setup or on a standalone device as follows:

  • Create an IRB (IFL) (without associating it with an L3 interface)

    set interfaces irb unit 100 family inet address 100.100.100.1/24

  • Commit the configuration.

  • Delete IRB interface

    delete interfaces irb unit 100 family inet address 100.100.100.1/24

Invalid interface index message are displayed because we are deleting the IFL and there is no physical interface associated with it. Thus, brcm_get_hw_l3_interface_index returns -1 as the value of intf_idx and in brcm_get_vlan_token_from_intf if intf_idx is -1, then this message is displayed.

Solution:

Locate the interfaces generating these logs as below:

> show interfaces snmp-index 892
 Physical interface: ge-5/0/16, Enabled, Physical link is Down
   Interface index: 981, SNMP ifIndex: 892
   Link-level type: Ethernet, MTU: 1514, MRU: 0, Speed: Auto, Duplex: Auto, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled,
   Source filtering: Disabled, Flow control: Disabled, Auto-negotiation: Enabled, Remote fault: Online, Media type: Copper,
   IEEE 802.3az Energy Efficient Ethernet: Disabled
   Device flags   : Present Running Down
   Interface flags: Hardware-Down SNMP-Traps Internal: 0x4000
   Link flags     : None
   CoS queues     : 12 supported, 12 maximum usable queues
   Current address: 80:ac:ac:16:ca:33, Hardware address: 80:ac:ac:16:ca:33
   Last flapped   : 2016-10-24 17:06:06 CEST (1d 16:52 ago)
   Input rate     : 0 bps (0 pps)
   Output rate    : 0 bps (0 pps)
   Active alarms  : LINK
   Active defects : LINK
   Interface transmit statistics: Disabled
 
   Logical interface ge-5/0/16.0 (Index 721) (SNMP ifIndex 1080)
     Flags: Device-Down SNMP-Traps 0x20024000 Encapsulation: Ethernet-Bridge
     Input packets : 0
     Output packets: 0
     Protocol eth-switch, MTU: 1514
 
Confirm if this is a working interface connected to any devices. It may be possible that the interface is a 10 Gig (Xe) interface, however it is configured as a 1 Gig (Ge).
 
Delete the interface configuration and the log messages should disappear.
 
If these log messages continue to appear, then make sure that your configuration is proper and there are no stale interface configurations.

If you need further assistance, please open a case with JTAC.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Security Alerts and Vulnerabilities

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