Switching

Expand all | Collapse all

Strange log messages in EX2300

Jump to Best Answer
  • 1.  Strange log messages in EX2300

    Posted 07-28-2017 07:09

    Hello! I have brand new EX2300-48. After basic configuration I've notice a strange lines in message logs:

     

    fpc0 PFESVCS: Input IFL not found
    dc-pfe: PFESVCS: Input IFL not found

    They appear in log constantly with interval 10-30 seconds.

     

    Model: ex2300-48t
    Junos: 15.1X53-D55.5
    

    I did googled and didn't find anything about this messages. What can be a reason? Thank you!


    #log
    #switch
    #EX2300
    #Error


  • 2.  RE: Strange log messages in EX2300

    Posted 07-28-2017 11:54
    Input IFL not found

    https://kb.juniper.net/InfoCenter/index?page=content&id=KB2820

     

    See if tht helps.

     

     



  • 3.  RE: Strange log messages in EX2300

     
    Posted 07-28-2017 16:32

    Can you confirm that all the configured interfaces exist.

     

    And all the physical interfaces have a configuration.

     

    I think this occurs when there is a mismatch between hardware and configuration.



  • 4.  RE: Strange log messages in EX2300

    Posted 07-30-2017 23:01

    Here is interfaces configuration:

     

    interfaces {
        interface-range ER_0_46 {
            member-range ge-0/0/0 to ge-0/0/46;
            unit 0 {
                family ethernet-switching {
                    interface-mode access;
                    vlan {
                        members VLAN30;
                    }
                }
            }
        }
        ge-0/0/47 {
            description "Trunk";
            unit 0 {
                family ethernet-switching {
                    interface-mode trunk;
                    vlan {
                        members [ IPPHONE_VLAN VLAN30 ];
                    }
                }
            }
        }
        irb {
            unit x {
                description "MGMT NET";
                family inet {
                    filter {
                        input acl-re-protect;
                    }
                    address xx.xx.xx.xx/24;
                }
            }
        }
        me0 {
            description "OOB Management";
            unit 0 {
                family inet {
                    address 172.16.255.1/24;
                }
            }
        }
    }
    


  • 5.  RE: Strange log messages in EX2300

     
    Posted 08-16-2017 02:55

    Config looks valid.

     

    Is anything doing SNMP polling on the device?  

    Maybe they are looking at the wrong sub interface number in the requests.



  • 6.  RE: Strange log messages in EX2300

    Posted 08-18-2017 06:28

    Yes, we have SNMP requests to this switch. I will double check templates and look if it's realy SNMP causes messages to appear.

    Thank you.



  • 7.  RE: Strange log messages in EX2300

    Posted 08-21-2017 05:34

    We did turned off SNMP checks of this switch, but messages are still generating.



  • 8.  RE: Strange log messages in EX2300
    Best Answer

     
    Posted 08-23-2017 03:17

    Is there any more data with the log like the actual index number?

     

    We can see all the ifl setup on the device this way

     

    show interfaces extensive | match ifIndex

    I also did a search in the PR database (Problem Reports - Junos bugs) and I don't see this listed but your version of Junos was not availalbe as a filter either.  This is starting to feel like a bug.

     

    prsearch.juniper.net/InfoCenter/index?page=prsearch



  • 9.  RE: Strange log messages in EX2300

    Posted 08-28-2017 03:00

    Here's my syslog configuration for this device:

        syslog {
            user * {
                any emergency;
            }
            host xx.xx.xx.xx {
                any any;
                source-address xx.xx.xx.xx;
            }
            file messages {
                any notice;
                authorization info;
            }
            file interactive-commands {
                interactive-commands any;
            }
        }
    

    And this is what I'm getting on syslog server - https://pastebin.com/tZj2GYBN

     

     



  • 10.  RE: Strange log messages in EX2300

     
    Posted 08-29-2017 03:09

    There does not seem to be enough information here for me to tie this to a particular port.  But there are errors for both logical (ifl) and physical (ifd) in the logs.  I'm not sure how to interpret the "port 28" on the ifd error but assume this might be the index of that physical interface.  Try this search to see if there is a match:

     

    show interfaces extensive | find "Interface index: 28"

    This will start the interface output in the affected physical interface.  Look at the name of the next interface that shows.

     

    Run show interfaces terse and see the name of the interface before that interface and this will be the one with the matching index 28.  Thus the potential source of the messages.

     



  • 11.  RE: Strange log messages in EX2300

    Posted 08-30-2017 03:31

    Unfortunately, I didn't find interface with index 28, and interface 28 itself (if this error maybe mean physical interface) has zero counters and I believe from moment of first start there was nothing connected to this port. So I'm kinda in dead end. For time this switch is in production I didn't notice any influences of this error messages on device performance, and maybe you are right, that this can be some kind of bug.

     

    Any way, thank you for your help!



  • 12.  RE: Strange log messages in EX2300

    Posted 09-26-2017 06:41

    We were getting the same log messages on our new ex2300 switches. This is how I fixed it. I am not a Juniper engineer, so I will not go into detail about why this happens or how these changes fix the issue. I hope that someone smarter than me will chime in.

     

    This solution worked for me, however there is not enough information here for me to say it will work for you.

     

    The cause of my issue:

    The log message appears when a device connecting to a wireless access point requests a DHCP address. This may not be the only action that generates this log message, but it consistently did for my testing. Our wireless APs connect to a trunk port with several VLANs configured for different wireless SSIDs.

     

    My fix was to add an irb interface with a family of inet (IPv4) to interfases irb. Then I set the l3-interface for the vlan to the irb I created. Once I did this the error messages stopped. I did not need to configure the interface for dhcp or give it a static ip address for this to work. See the examples below.

     

     

    Here is an example of how our WIFI ports and vlans were configured on our ex2200's <--- This configuration works fine on the older switches.

     

    interfaces {

                    ge-0/0/17 {

                                    unit 0 {

                                                    family ethernet-switching {

                                                                    port-mode trunk;

                                                                    vlan {

                                                                                    members [ VLAN1 VLAN2 VLAN3 VLAN4 ];

                                                                    }

                                                                    native-vlan-id VLAN5;

                                                    }

                                    }

                    }

     

                    vlan {

                                    unit 4 {

                                                    family inet {

                                                                    address X.X.X.X/XX;

                                                    }

                                    }

                    }

    }

    vlans {

                    VLAN1 {

                                    vlan-id 1;

                    }

                    VLAN2 {

                                    vlan-id 2;

                    }

                    VLAN3 {

                                    vlan-id 3;

                    }

                    VLAN4 {

                                    vlan-id 4;

                                    l3-interface vlan.4;

                    }

                    VLAN5 {

                                    vlan-id 5;

                    }

    }

     

     

    Here is how they were translated to enhanced layer 2 <--- This configuration caused all the same error messages you are reporting.

    interfaces {

        ge-0/0/42 {

            native-vlan-id 5;

            unit 0 {

                family ethernet-switching {

                    interface-mode trunk;

                    vlan {

                        members [ VLAN1 VLAN2 VLAN3 VLAN4 VLAN5 ];

                    }

                    storm-control sc;

                }

            }

        }

                    irb {

                                    unit 4 {

                                                    family inet {

                                                                    address X.X.X.X/XX;

                                                    }

                                    }

                    }

    }

     

    vlans {

                    VLAN1 {

                                    vlan-id 1;

                    }

                    VLAN2 {

                                    vlan-id 2;

                    }

                    VLAN3 {

                                    vlan-id 3;

                    }

                    VLAN4 {

                                    vlan-id 4;

                                    l3-interface irb.4;

                    }

                    VLAN5 {

                                    vlan-id 5;

                    }

    }

     

    Here is my new EX2300 configuration <--- This configuration stopped all the same error messages you are reporting.

     

    interfaces {

        ge-0/0/42 {

            native-vlan-id 5;

            unit 0 {

                family ethernet-switching {

                    interface-mode trunk;

                    vlan {

                        members [ VLAN1 VLAN2 VLAN3 VLAN4 VLAN5 ];

                    }

                    storm-control sc;

                }

            }

        }

                    irb {

                                    unit 1 {

                                                    family inet; <---- Added to interfaces irb

                                    }

                                    unit 2 {

                                                    family inet;

                                    }

                                    unit 3 {

                                                    family inet;

                                    }

                                    unit 4 {

                                                    family inet {

                                                                    address X.X.X.X/XX;

                                                    }

                                    }

                                    unit 5 {

                                                    family inet;

                                    }

                    }

    }

     

    vlans {

                    VLAN1 {

                                    vlan-id 1;

                                    l3-interface irb.1; <---- Added to each vlan

                    }

                    VLAN2 {

                                    vlan-id 2;

                                    l3-interface irb.2;

                    }

                    VLAN3 {

                                    vlan-id 3;

                                    l3-interface irb.3;

                    }

                    VLAN4 {

                                    vlan-id 4;

                                    l3-interface irb.4;

                    }

                    VLAN5 {

                                    vlan-id 5;

                                    l3-interface irb.5;

                    }

    }

     

     



  • 13.  RE: Strange log messages in EX2300

     
    Posted 09-26-2017 07:51

    Maybe to assist is could you respond with:

     

    1.  What version of Junos are you using?

    2.  What is the exact log message you [were] seeing?

    3.  Where is the DHCP Server located ?  Is there just one (maybe redundant)?  What IP address and is it in a different VLAN to your VLANs on the EX2300?

    4.  What does interface ge-0//0/17 actually connect to?  Device and its config?

     

    This might be a start, . . .



  • 14.  RE: Strange log messages in EX2300

    Posted 11-13-2018 11:05

    Thank you GNUGUY (Message 12 of 14).

    The solution did work on my EX-2300.

    No "dc-pfe: PFESVCS: Input IFL not found" messages anymore.



  • 15.  RE: Strange log messages in EX2300

    Posted 11-23-2018 05:35

    Any one knows any other sollution to this issue?
    I'm having the same problem here with EX2300C-12p and adding a L3 interface for every vlan, evein if it's not required is a bit silly, to say the least.