This article explains the meaning of the log message and what can be done to find the root-cause of the log messages.
May 29 14:08:32 ex4300-hostname pfex: IFFPC: 'IFD add' (opcode 3) failed
May 29 14:08:32 ex4300-hostname pfex: ifd 649; fpc ifd attach error (22)
May 29 14:08:32 ex4300-hostname pfex: IFRT: 'IFD hardware address configuration' (opcode 226) failed
The above messages indicate that the interface is seemingly not available. IFDs are created at bootup. The RE will then set ADD operation and send it to the PFE. The PFE then consumes the IFD and programs it onto the hardware. Here in this case, it seems that the 'device IFD add' operation is failing.
How to troubleshoot the issue:
1. Check the physical status of the interface and see if the interface comes up. If the physical interface is down, to isolate, you can try to verify the physical port status using a software/hardware loopback testing.
2. If the issue is isolated to the SFP and not the physical port, check and verify if the SFP is a known good working one?
3. If the issue persists, check the device hardware datasheet and check if the SFP is supported on the chassis or not. In case of Juniper SFPs, supported types and models would be listed out in the hardware sheet.
4. To isolate further, Add any other SFP of the same model and check if the messages are still seen?
5. If the issue persists, try any other SFP model in the interface and check if the messages are still seen?
2024-05-31 - Initial Publication2024-06-21 - Updated solution to have a better clarity2024-07-29 - Visibility Modified