Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Syslog message: 'RPD_KRT_VPLS_IFL_MODIFY: Unable to modify VPLS-related state: -1 (errno No such file or directory)'

0

1

Article ID: KB37505 KB Last Updated: 04 Oct 2021Version: 1.0
Summary:

This article explains the following syslog message and its impact on Juno's daemons:

RPD_KRT_VPLS_IFL_MODIFY: Unable to modify VPLS-related state: -1 (errno No such file or directory)
Symptoms:
Two symptoms are seen:
  1. Syslog 'RPD_KRT_VPLS_IFL_MODIFY' is written in an aggressive way in the syslog messages files 

    Aug 23 11:00:40  test-router rpd[3671]: RPD_KRT_VPLS_IFL_MODIFY: Unable to modify VPLS-related state: -1 (errno No such file or directory)
    Aug 23 11:00:40  test-router last message repeated 13 times
    Aug 23 11:00:40  test-router rpd[3671]: RPD_KRT_VPLS_IFL_MODIFY: Unable to modify VPLS-related state: -1 (errno No such file or directory)
    Aug 23 11:00:40  test-router last message repeated 185 times
  2. The rpd and eventd processes are fully utilized:

    root@test-router> show system processes extensive no-forwarding
    last pid:  4011;  load averages:  2.08,  2.13,  2.12  up 495+13:09:32    13:59:29
    150 processes: 4 running, 144 sleeping, 1 zombie, 1 waiting

    Mem: 514M Active, 3844M Inact, 1878M Wired, 1695M Buf, 9661M Free
    Swap: 8192M Total, 8192M Free

      PID USERNAME       THR PRI NICE   SIZE    RES STATE   C   TIME    WCPU COMMAND
       10 root             4 155 ki31     0K    64K RUN     3    ??? 191.75% idle
     3671 root             1 103    0  3501M  2644M CPU1    1 798.8H 100.00% rpd
     3683 root             1 103    0   727M 16308K CPU0    0 619.9H 100.00% eventd
    < ... > 
Cause:

When the routing protocol process (rpd) attempted to modify the state for a logical interface that is related to VPLS and the request failed, the rpd process may not recover itself and is stuck in this state.

This is due to an undefined interface that exists within a VPLS instance configuration.

Solution:
Check the router configuration and delete all undefined interfaces.

Example:

    VLAN-3003 {
        instance-type vpls;
        vlan-id 3003;
        interface xe-0/0/1.3003; ## 'xe-0/0/1.3003' is not defined
        interface xe-0/0/2.3003;
        interface xe-1/0/1.3003;
        interface ae6.3003;
        routing-interface irb.3003;
        protocols {
            vpls {
                no-tunnel-services;
                vpls-id 12224;
                mtu 9174;
                mac-flush {
                    any-interface;
                }
                neighbor X.X.X.X {
                    pseudowire-status-tlv;
                }
            }
        }
    }
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search