Search Engine: Elastic

Article ID: 118583, created on Nov 12, 2013, last review on Jul 14, 2018

  • Applies to:
  • Plesk Automation 11.1
  • Plesk Automation 11.5


  1. It is not possible to add required network interface to Plesk Automation (PA) service node.

  2. Go to PA Control Panel> Infrastructure Director> Service Nodes>[name of service node]> Networking> IP pools > Attach > Select net interface - required interface is absent.

  3. No configuration files for required network interface are in the /etc/sysconfig/network-scripts/ folder

  4. The network interface persists on the server but the required settings are not set:

    # ip a l
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet scope host lo
        inet6 ::1/128 scope host
           valid_lft forever preferred_lft forever
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
        link/ether 1e:b0:03:7c:19:46 brd ff:ff:ff:ff:ff:ff
        inet brd scope global eth0
        inet6 fe80::1cb0:3ff:fe7c:1946/64 scope link
           valid_lft forever preferred_lft forever
    3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
        link/ether 1e:b0:03:4e:01:ff brd ff:ff:ff:ff:ff:ff


PA records information about network configuration of service nodes only at initial service node registration. And in case of any network configuration changes on service node after registration, it will not be reflected in PA. The only way to update required information is to delete service node from PA, and reattach it back.

The functionality which you expect from the Plesk Automation - Ability to reread network interfaces added after initial service node registration - can be considered as feature request.

The feature request number TP-140883 regarding the matter was created..

Subscribe to our knowledgebase - each product update comes with corresponding KB article:


NOTE: the solution is applicable for unused service nodes only! In case if the service node is used by clients there is no ability to detach it from PPA. In this case you should first move clients services to other service nodes using PA Moving Tool. Moving mail services between service nodes is available only since the 11.5 version.
  1. Create configuration file for the required network interface if it doesn't exist:

    # cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1
  2. Set the required settings in interface configuration file /etc/sysconfig/network-scripts/ifcfg-eth1 e.g.

    # cat /etc/sysconfig/network-scripts/ifcfg-eth1

    You can read more about interface configuration files in CentOS Deployment Guide

  3. Start the required network interface

    # ifup eth1 
  4. Make sure that required network interface is RUNNING

    # ifconfig eth1
  5. Remove service node from PPA.

  6. Add service node back, with already updated network configuration.

e0aff7830fa22f92062ee4db78133079 c1ecc6010feff26cb42d1d14a7881dd6 caea8340e2d186a540518d08602aa065 33a70544d00d562bbc5b17762c4ed2b3

Email subscription for changes to this article
Save as PDF