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

Syslog Message: PFE-3: fpc0 IF: Could not increment reroute counters for ifl 131079(2)

0

0

Article ID: KB36927 KB Last Updated: 14 Jun 2021Version: 1.0
Summary:

This article explains the meaning of the following ifl reroute counter syslog messages:

Jan  8 13:25:51  sw1 : %PFE-3: fpc0 IF: Could not increment reroute counters for ifl 131079(2)
Jan  8 13:25:51  sw1 : %PFE-3: fpc0 nh_unilist_update_weight:2239NH: Failed to inc re-route counters for nh (type Unilist, id 131097, proto ipv4), target nh (type Indirect, id 131078, proto ipv4)
Jan  8 13:25:51  sw1 : %PFE-3: fpc0 IF: Could not increment reroute counters for ifl 131079(2)
Jan  8 13:25:51  sw1 : %PFE-3: fpc0 nh_unilist_update_weight:2239NH: Failed to inc re-route counters for nh (type Unilist, id 131097, proto ipv4), target nh (type Indirect, id 131080, proto ipv4)
Symptoms:

During events such as interface flap, reboot, configuration change, route convergence, node failures etc., the below syslog messages are seen:

Jan  8 13:25:51  sw1 : %PFE-3: fpc0 IF: Could not increment reroute counters for ifl 131079(2)
Jan  8 13:25:51  sw1 : %PFE-3: fpc0 nh_unilist_update_weight:2239NH: Failed to inc re-route counters for nh (type Unilist, id 131097, proto ipv4), target nh (type Indirect, id 131078, proto ipv4)
Jan  8 13:25:51  sw1 : %PFE-3: fpc0 IF: Could not increment reroute counters for ifl 131079(2)
Jan  8 13:25:51  sw1 : %PFE-3: fpc0 nh_unilist_update_weight:2239NH: Failed to inc re-route counters for nh (type Unilist, id 131097, proto ipv4), target nh (type Indirect, id 131080, proto ipv4)
Cause:

Certain reroute counters failed to increment for NH type Unilist next hops. Under normal conditions when a valid next hop is available, these counters increment without any errors. However, under conditions such as interface flap, reboot, configuration change, node failures, etc., the next hop may stay in a HOLD state temporarily.  And the next-hop may not get resolved for a brief period of time due to various reasons such as unavailability of the interface due to the interface being initialized.  As a result, the counter fails to increment and these error logs appear on the device during this period.

Solution:

This is expected behavior. These syslog messages appear only momentarily during convergence, which happens when there is a topology change event with respect to the interface or a reboot event on the device.

There is no service impact on the device, so they can be safely ignored.

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