Junos OS

Expand all | Collapse all

fpc0 Log Input IFL not found

  • 1.  fpc0 Log Input IFL not found

    Posted 10 days ago
    Hello,

    i have some strange Log messages on the fpc, can anyone explain what this mean and how to fix this ?

    show version
    localre:
    --------------------------------------------------------------------------
    Model: qfx5120-48y-8c
    Junos: 19.4R2-S1.2
    :RE:0% vty fpc0
    
    
    Switching platform (2200 Mhz Pentium processor, 639MB memory, 0KB flash)
    
    FPC0(rgilsx06b vty)# [Thu Jan  7 10:42:28.997 LOG: Debug] PFESVCS: Input IFL not found, iif 424 proto 2
    [Thu Jan  7 10:42:30.512 LOG: Debug] PFESVCS: Input IFL not found, iif 363 proto 2
    [Thu Jan  7 10:42:32.080 LOG: Debug] PFESVCS: Input IFL not found, iif 363 proto 2
    [Thu Jan  7 10:42:34.822 LOG: Debug] PFESVCS: Input IFL not found, iif 363 proto 2
    exit on signal 2​


  • 2.  RE: fpc0 Log Input IFL not found

     
    Posted 10 days ago
    Hello 

    These are not harmful messages, the meanings of the messages are as follow:

    "IIF" is input interface index and
    "proto" is the protocol number

    As per the logs proto is 2 which corresponds to IGMP messages. This means that you are receiving IGMP packets on an interface which is not configured for IGMP.

    If these messages are overloading the log file, you can simply filter them. Please visit the below KB link:
    https://kb.juniper.net/InfoCenter/index?page=content&id=KB9382&actp=METADATA


    ------------------------------

    If my answer provides the solution, please mark my post as "Best Answer".

    ------------------------------




  • 3.  RE: fpc0 Log Input IFL not found

    Posted 10 days ago
    Hello,

    and how i can find out witch interface receive theese igmp packets ?


  • 4.  RE: fpc0 Log Input IFL not found

     
    Posted 10 days ago
    from Index No. , every interface has an index# as shown below 

    Juniper@lab> show interfaces xe-0/2/1.64
    Logical interface xe-0/2/1.64 (Index 1571) (SNMP ifIndex 5032)
    Flags: Up SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.64 ] Encapsulation: ENET2
    Input packets : 18519
    Output packets: 15085677
    Protocol aenet, AE bundle: ae2.64


  • 5.  RE: fpc0 Log Input IFL not found

    Posted 10 days ago
    I already done that, there is no Interface with id 363 in any field, maybe i must open an Jtac case here.

     show interfaces extensive | match 363    
       Input  bytes  :        8644892636333             52934528 bps
        Total octets                 8644892636333   12554042672632
       Input  packets:         102431702438                50363 pps
        3                          1113636              1113636                    0
       Output packets:          60702346665                15363 pps
        Protocol eth-switch, MTU: 1514, Generation: 363, Route table: 6, Mesh Group: __all_ces__, EVPN multi-homed status: Blocking BUM Traffic to ESI,
       Input  bytes  :        8644892636333             52934528 bps
       Input  packets:         102431702438                50363 pps
        3                          1113636              1113636                    0
         Input  packets:              2363821
         Input  packets:              2363821                  966 pps
         Input  packets:            153632879
         Input  packets:            153632879                 1537 pps
    
    {master:0}​