Description

This article explains why the syslog message below is reported for a newly configured switching device:

[EX-BCM PIC] ex_bcm_pic_port_unit_from_ifd Cannot retrieve pfe unit/port num! Invalid ifd:.local. pfe port num:0

Symptoms

The following messages are seen continuously in the syslogs. They are seen both on standalone node and Virtual Chassis setup. 

Jul 6 01:00:11 JUNPER pfex: [EX-BCM PIC] ex_bcm_pic_port_unit_from_ifd Cannot retrieve pfe unit/port num! Invalid ifd:.local. pfe port num:0
Jul 6 01:00:12 JUNPER pfex: [EX-BCM PIC] ex_bcm_pic_port_unit_from_ifd Cannot retrieve pfe unit/port num! Invalid ifd:.local. pfe port num:0
Jul 6 01:00:12 JUNPER pfex: [EX-BCM PIC] ex_bcm_pic_port_unit_from_ifd Cannot retrieve pfe unit/port num! Invalid ifd: pfe port num:0
Jul 6 01:00:12 JUNPER fpc0 PFE_BCM_NH-,pfe_bcm_nh_l3_hw_install(),490:bcm l3 egress create object failed for nh 131071(-18:Invalid port)

Solution

These error messages are seen when an ae bundle interface is configured with storm control in EX4300 series switches. This is because of the periodic 1 sec polling of the storm control counters (pfe_bcm_scntl_periodic_read_1sec), wherein the ae IFD is passed to pfe_ifd_get_port_num() to retrieve port num, which is unexpected.

This issue is fixed in Junos OS 13.2X51-D20 and Junos OS 15.1R1. Since these messages do not impact service, they can be safely ignored.

To filter these messages, refer to the following KB article: