Article ID: 118101, created on Oct 22, 2013, last review on May 11, 2014

  • Applies to:
  • Operations Automation
  • Panels
  • Virtuozzo containers for Linux


POA task 'Turn on traffic shaping on HW Node' fails with the following diagnostics:

4304 : Can not set network configuration: can't restart shaping: Starting Parallels Virtuozzo Containers shaping: vz
ERROR: Wrong BANDWIDTH value (no such device eth0 on the node) or device is down.
Starting Parallels Virtuozzo Containers shaping [FAILED]


Traffic shaping is disabled on the PVC (Parallels Virtuozzo Containers) hardware node in question and cannot be turned on due to improper configuration of the traffic shaper, in this particular case non-existing network interface eth0 is configured in the traffic shaper.


  1. Check the POA configuration for traffic shaping on the Virtuozzo node in question:

    • Log into the POA Provider Control Panel
    • Go to Service Director > Virtuozzo Manager > VPS Hardware Nodes
    • Click on the required server
    • Switch to the Networking > IP addresses tab
    • Find the network interface(s) in the Frontnet (external network)
  2. Compare the network interface configured in POA with the corresponding settings in the /etc/vz/vz.conf file on the Virtuozzo hardware node, they look like this:


    In the example above you can see that traffic shaping is disabled (TRAFFIC_SHAPING=no), and it is configured for the interface eth0, which does not match to the settings in POA.

    Correct the Virtuozzo configuration file in accordance to the POA settings (enable traffic shaping and specify correct network interface), e.g.:


    where eth3.623 is the name of the external network interface displayed in the POA Provider Control Panel.

    After that restart the failed task in the POA Task Manager.

Refer to the Parallels Virtuozzo Containers documentation for more details about the metnioned above parameters of the PVC traffic shaper:

Search Words

Wrong BANDWIDTH value

restart shaping

traffic shaping

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e8e50b42231236b82df27684e7ec0beb 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 614fd0b754f34d5efe9627f2057b8642 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF