This article discusses the meaning and trigger of the following syslog message:
%PFE-3: fpc0 COS(cos_fixed_class_do_unbind_action:2940): Platform failed to unbind fixed class 0 from ifl index 0, bind point 2 from INGRESS direction
The syslog message indicates that COSd is unable to bind the classifier to the IFL.
Note the IFL index is 0, which means IFL was deleted first before COS fixed the class unbind message. Check the sequence of log messages here:
Dec 6 06:20:38 qfx5100 : %PFE-3: fpc0 FAILED to read the QSFP IDEEPROM for port: 103 start addr: 0 - length: 32 Dec 6 06:20:38 qfx5100 : %PFE-3: fpc0 qsfp_tk_eeprom_scanning_check: qsfp-0/0/103 failed scanning eeprom addr 0x0 err 1000
Dec 6 06:20:38 qfx5100 : %PFE-3: fpc0 FAILED to read the QSFP IDEEPROM for port: 103 start addr: 0 - length: 32
Dec 6 06:20:39 qfx5100 /kernel: %KERN-3: if_pfe_ge_ifdpointchange_tlv: Child IFD et-0/0/103 not found to be part of any LAG bundle Dec 6 06:20:39 qfx5100 /kernel: %KERN-3: if_pfe_ge_ifdpointchange_tlv: Child IFD et-0/0/103 not found to be part of any LAG bundle Dec 6 06:20:39 qfx5100 rpd[2110]: %DAEMON-6: EVENT <UpDown> et-0/0/103 index 756 <Broadcast Multicast AeMemberChange> address #0 4.5c.6c.5.31.58 Dec 6 06:20:39 qfx5100 rpd[2110]: %DAEMON-6: EVENT <Delete> et-0/0/103.0 index 568 <Broadcast Multicast> address #0 4.5c.6c.5.31.58
Dec 6 06:20:39 qfx5100 rpd[2110]: %DAEMON-6: EVENT <Delete> et-0/0/103 index 756 <Broadcast Multicast AeMemberChange> address #0 4.5c.6c.5.31.58 Dec 6 06:20:39 qfx5100 rpd[2110]: %DAEMON-6: STP handler: Stp index=107, op=delete, state=Discarding, Topo change generation=0 Dec 6 06:20:39 qfx5100 rpd[2110]: %DAEMON-6: *STP Delete*, notify to other modules Dec 6 06:20:39 qfx5100 : %PFE-3: fpc0 COS(cos_fixed_class_do_unbind_action:2940): Platform failed to unbind fixed class 0 from ifl index 0, bind point 2 from INGRESS direction
Based on above the eeprom read failure event on et-0/0/103 triggered the IFL and IFD to be deleted as the QSFP became detached. Since there is no IFL, the COSd is unable to bind the classifier to the IFL of et-0/0/103. Therefore, it is reporting the above error message IFL 0.
The Cosd logs at the time of issue further confirms this:
Dec 6 06:20:39 GENCFG write failed (op, minor_type) = (add, policy inline) for tbl id 2 ifl 756 et-0/0/103 Reason: No such file or directory Dec 6 06:20:39 GENCFG write failed (op, minor_type) = (delete, policy inline) for tbl id 2 ifl 756 et-0/0/103 Reason: No such file or directory
The chassid logs further confirmed that after the EEPROM read failure occurred on the QSFP at 06:20:38, the QSFP became detached at 06:39:00, which led to the IFD/IFL deletion and COSd bind failure.
Dec 6 06:20:39 notify_sfp_remove: NULL kvpairs for PIC 0 Dec 6 06:20:39 pic_update_port_range Deleting IFD: et-0/0/103 Dec 6 06:20:39 ifdev_detach_port(et-0/0/103) Dec 6 06:20:39 ifd et-0/0/103 marked as gone Dec 6 06:20:39 PIC (fpc 0 pic 0) message operation: change. ifd count 97, flags 0x3
This issue is temporary. The occurrence of this syslog message depends on the QFSP/SFP detached because 30 seconds later, chassisd reports that the QSFP is detected/created once again without any issues and the corresponding IFD and IFL can be seen. The cosd logs do not report any binding errors this time.
Dec 6 06:21:10 notify_sfp_add: NULL kvpairs for PIC 0 Dec 6 06:21:10 create_pic_entry: pic i2c 0xf0af, hw qs 12 supported qs 12, flags 0x0, pic port 103, speed 40000000000 Dec 6 06:21:10 et-0/0/103 ifm_channel: 0x0, ifm_fe = 0, local_dev_id:0, global_dev_id:0, port_num:104 Dec 6 06:21:10 capability: et-0/0/103, cap flag = 43136, media: 2 porttype 184 Dec 6 06:21:10 ifdev_create entered et-0/0/103 Dec 6 06:21:10 et-0/0/103: large delay buffer cleared