Description

This article explains why the "pfe_platform_ubfd_adjust_packet_info Adjust packet Frame start Error" syslog message may be generated, and indicates whether any action is required.

 

Symptoms

The following syslog error messages may be generated by Flexible PIC Concentrator (FPC):

%PFE-3: fpc* pfe_platform_ubfd_adjust_packet_info Adjust packet Frame start Error

 

Solution

When a micro BFD (ubfd) configuration is present on a router and ubfd is programmed on the FPC, the Packet Forwarding Engine (PFE) will try to update the received ubfd packet with the incoming interface indices (both child and bundle IFL) before sending the packet to the Routing Engine.

If the PFE is unable to update the received ubfd packet, the following syslog error message is generated: 

Apr 12 01:40:34  mx-re0: %PFE-3: fpc1 pfe_platform_ubfd_adjust_packet_info Adjust packet Frame start Error

This message can be ignored if ubfd is not configured on the router.

To know more about Micro BFD Sessions, refer to Understanding Independent Micro BFD Sessions for LAG and Configuring Independent Micro BFD Sessions for LAG .

 

No action is required if there is no ubfd configuration.

However, you can filter out such log messages by using syslog filters (refer to KB22177 - [EX] How to filter two or more specific messages from being written to the syslog file? [juniper.net] ) if there is no ubfd configuration because there would be no impact.

Alternatively, the ubfd packets can be dropped by a firewall filter that is applied on the lo0 interface as shown below:

For IPv4 packets the following filter may be applied: 

family inet {
     filter ubfd {
         term 1 {
             from {
                 protocol udp;
                 destination-port 6784;
             }
             then {
                 discard;
             }
         }
         term 2 {
             then accept;
         }
     }
}
 

For IPv6 packets the following filter may be applied: 

family inet6 {
     filter ufbd-v6 {
         term 1 {
             from {
                 next-header udp;
                 destination-port 6784;
             }
             then {
                 count ufdb-v6;
                 discard;
             }
         }
         term 2 {
             then accept;
        }
     }
}
 

Note: If you have ubfd configured and the above syslog messages are reported, contact Support with the following logs: 

  • request support information
  • show log messages
  • show log chassisd
  • show bfd session

For troubleshooting the BFD issue, refer to KB26746 - [M/MX/T] Troubleshooting Checklist - BFD [juniper.net] .