Junos OS

 View Only

  • 1.  Unknown log messages

    Posted 08-28-2024 08:25
    Edited by spuluka 08-28-2024 13:03

    after upgrading QFX5200-32C from 23.4R2.13 to 23.4R2-S1.3 (JTAC recommended) the strange messages appeared in the logs:

    Aug 28 08:03:42  Rack12-Leaf-A kernel: if_pfe_ifl_ccc_tcc_info_tlv: IFL vtep.32769: Unexpected TLV - ifd_link 91
Aug 28 08:04:08  Rack12-Leaf-A last message repeated 516 times
Aug 28 08:04:20  Rack12-Leaf-A last message repeated 229 times
Aug 28 08:04:20  Rack12-Leaf-A kernel: if_pfe_ifl_ccc_tcc_info_tlv: IFL vtep.32769: Unexpected TLV - ifd_link 91
Aug 28 08:04:38  Rack12-Leaf-A last message repeated 351 times
Aug 28 08:06:38  Rack12-Leaf-A last message repeated 2328 times
Aug 28 08:07:37  Rack12-Leaf-A last message repeated 1140 times
Aug 28 08:07:37  Rack12-Leaf-A kernel: if_pfe_ifl_ccc_tcc_info_tlv: IFL vtep.32769: Unexpected TLV - ifd_link 91
Aug 28 08:07:38  Rack12-Leaf-A last message repeated 23 times
Aug 28 08:09:38  Rack12-Leaf-A last message repeated 2326 times
Aug 28 08:11:36  Rack12-Leaf-A last message repeated 2293 times

    there is only 1 VXLAN on this leaf switch in BGP EVPN fabric. I can't find any related information what could it be.





  • 2.  RE: Unknown log messages

    Posted 08-30-2024 03:36
    Edited by dtsname 08-30-2024 03:36

    some evpn traceoptions log output:

    Aug 30 07:23:03.779120 vc_intf_lock:2403:vtep.32769 owner=4 vcif_refcnt=0 vcif_l2vpn_refcnt=0 vcif_l2ckt_refcnt=0 vcif_fec129_refcnt=0 vcif_evpn_refcnt=1vcif_kern_upd_q_refcnt=1
Aug 30 07:23:03.779152 vc_intf_unlock: intf_name=vtep.32769 owner=4 vcif_refcnt=0 vcif_evpn_refcnt=1 vcif_l2vpn_refcnt=0 vcif_l2ckt_refcnt=0 vcif_fec129_refcnt=0 vcif_kern_upd_q_refcnt=2 vc_intf_owned_by_l2vpn=0 vc_intf_owned_by_l2ckt=0 vc_intf_owned_by_l2vpn_fec129=0 vc_intf_owned_by_evpn=1
Aug 30 07:23:03.779289 	Kernel couldn't be updated with CCC IFF data,  Operation not permitted on this ifl,for intf vtep.32769
Aug 30 07:23:03.779314 vc_intf_lock:2403:vtep.32769 owner=4 vcif_refcnt=0 vcif_l2vpn_refcnt=0 vcif_l2ckt_refcnt=0 vcif_fec129_refcnt=0 vcif_evpn_refcnt=1vcif_kern_upd_q_refcnt=1
Aug 30 07:23:03.779321 vc_intf_unlock: intf_name=vtep.32769 owner=4 vcif_refcnt=0 vcif_evpn_refcnt=1 vcif_l2vpn_refcnt=0 vcif_l2ckt_refcnt=0 vcif_fec129_refcnt=0 vcif_kern_upd_q_refcnt=2 vc_intf_owned_by_l2vpn=0 vc_intf_owned_by_l2ckt=0 vc_intf_owned_by_l2vpn_fec129=0 vc_intf_owned_by_evpn=1
Aug 30 07:23:03.831860 vc_intf_lock:2403:vtep.32769 owner=4 vcif_refcnt=0 vcif_l2vpn_refcnt=0 vcif_l2ckt_refcnt=0 vcif_fec129_refcnt=0 vcif_evpn_refcnt=1vcif_kern_upd_q_refcnt=1
Aug 30 07:23:03.831889 vc_intf_unlock: intf_name=vtep.32769 owner=4 vcif_refcnt=0 vcif_evpn_refcnt=1 vcif_l2vpn_refcnt=0 vcif_l2ckt_refcnt=0 vcif_fec129_refcnt=0 vcif_kern_upd_q_refcnt=2 vc_intf_owned_by_l2vpn=0 vc_intf_owned_by_l2ckt=0 vc_intf_owned_by_l2vpn_fec129=0 vc_intf_owned_by_evpn=1
Aug 30 07:23:03.831964 	Kernel couldn't be updated with CCC IFF data,  Operation not permitted on this ifl,for intf vtep.32769
Aug 30 07:23:03.831975 vc_intf_lock:2403:vtep.32769 owner=4 vcif_refcnt=0 vcif_l2vpn_refcnt=0 vcif_l2ckt_refcnt=0 vcif_fec129_refcnt=0 vcif_evpn_refcnt=1vcif_kern_upd_q_refcnt=1
Aug 30 07:23:03.831982 vc_intf_unlock: intf_name=vtep.32769 owner=4 vcif_refcnt=0 vcif_evpn_refcnt=1 vcif_l2vpn_refcnt=0 vcif_l2ckt_refcnt=0 vcif_fec129_refcnt=0 vcif_kern_upd_q_refcnt=2 vc_intf_owned_by_l2vpn=0 vc_intf_owned_by_l2ckt=0 vc_intf_owned_by_l2vpn_fec129=0 vc_intf_owned_by_evpn=1
Aug 30 07:23:03.883019 vc_intf_lock:2403:vtep.32769 owner=4 vcif_refcnt=0 vcif_l2vpn_refcnt=0 vcif_l2ckt_refcnt=0 vcif_fec129_refcnt=0 vcif_evpn_refcnt=1vcif_kern_upd_q_refcnt=1
Aug 30 07:23:03.883036 vc_intf_unlock: intf_name=vtep.32769 owner=4 vcif_refcnt=0 vcif_evpn_refcnt=1 vcif_l2vpn_refcnt=0 vcif_l2ckt_refcnt=0 vcif_fec129_refcnt=0 vcif_kern_upd_q_refcnt=2 vc_intf_owned_by_l2vpn=0 vc_intf_owned_by_l2ckt=0 vc_intf_owned_by_l2vpn_fec129=0 vc_intf_owned_by_evpn=1
Aug 30 07:23:03.883097 	Kernel couldn't be updated with CCC IFF data,  Operation not permitted on this ifl,for intf vtep.32769
Aug 30 07:23:03.883108 vc_intf_lock:2403:vtep.32769 owner=4 vcif_refcnt=0 vcif_l2vpn_refcnt=0 vcif_l2ckt_refcnt=0 vcif_fec129_refcnt=0 vcif_evpn_refcnt=1vcif_kern_upd_q_refcnt=1
Aug 30 07:23:03.883115 vc_intf_unlock: intf_name=vtep.32769 owner=4 vcif_refcnt=0 vcif_evpn_refcnt=1 vcif_l2vpn_refcnt=0 vcif_l2ckt_refcnt=0 vcif_fec129_refcnt=0 vcif_kern_upd_q_refcnt=2 vc_intf_owned_by_l2vpn=0 vc_intf_owned_by_l2ckt=0 vc_intf_owned_by_l2vpn_fec129=0 vc_intf_owned_by_evpn=1
Aug 30 07:23:03.936319 vc_intf_lock:2403:vtep.32769 owner=4 vcif_refcnt=0 vcif_l2vpn_refcnt=0 vcif_l2ckt_refcnt=0 vcif_fec129_refcnt=0 vcif_evpn_refcnt=1vcif_kern_upd_q_refcnt=1
Aug 30 07:23:03.936335 vc_intf_unlock: intf_name=vtep.32769 owner=4 vcif_refcnt=0 vcif_evpn_refcnt=1 vcif_l2vpn_refcnt=0 vcif_l2ckt_refcnt=0 vcif_fec129_refcnt=0 vcif_kern_upd_q_refcnt=2 vc_intf_owned_by_l2vpn=0 vc_intf_owned_by_l2ckt=0 vc_intf_owned_by_l2vpn_fec129=0 vc_intf_owned_by_evpn=1
Aug 30 07:23:03.936393 	Kernel couldn't be updated with CCC IFF data,  Operation not permitted on this ifl,for intf vtep.32769






  • 3.  RE: Unknown log messages

    Posted 11-11-2024 09:13

    Seeing the same messages on our EX4100-24X switches after upgrading to 23.4R2-S2.1 (JTAC recommended release). Did you get to the bottom of this?



    ------------------------------
    ALAN GRAINGER
    ------------------------------



  • 4.  RE: Unknown log messages

    Posted 11-12-2024 05:51

    JTAC confirmed that this is a cosmetic issue:

    https://prsearch.juniper.net/problemreport/PR1826772



    ------------------------------
    ALAN GRAINGER
    ------------------------------

    Original Message


  • 5.  RE: Unknown log messages

    Posted 11-12-2024 06:01

    I just moved to 22.2R3-S4.10 but thanks for your research.



    ------------------------------
    // BR, dtsname
    ------------------------------

    Original Message


Related Content