Article ID: 124085, created on Dec 29, 2014, last review on Feb 22, 2016

  • Applies to:
  • Operations Automation 5.5

Symptoms script ( fails with the error:

2014-04-10 14:32:08.995  INFO <- Checking host backups.domain.tld (54) failed [00.466]
2014-04-10 14:32:08.995 ERROR ('There is no networks on host PEMVZMPS04.domain.tld (14)', "Configure 'Bridged' networks")
Traceback (most recent call last):
File "/usr/local/pem/bin/", line 1180, in <module>
File "/usr/local/pem/bin/", line 1172, in main
    convert_host(progress, host_id, hw_host_id, backnet, frontnet, gateway, skip_container_modification)
  File "/usr/local/pem/bin/", line 545, in convert_host
run_checks(progress, host_id, hw_host_id, backnet, frontnet)
  File "/usr/local/pem/bin/", line 527, in run_checks
raise Exception(reason, what_todo)
Exception: ('There is no networks on host PEMVZMPS04.domain.tld (14)', "Configure 'Bridged' networks")


There is a mandatory prerequisite for this procedure: bridged interface(s) should be configured on the hardware node in order to make the conversion work.


Configure the Front Net and the Back Net virtual networks on the hardware node in bridged mode. Please refer to the Virtuozzo User Guide for details:

For example, if you need to create bridged network named Backnet associated with the adapter eth0, the following actions should be done:

# vznetcfg net new Backnet
# vznetcfg net addif backnet eth0

Search Words

how to convert shared containers into hardware nodes

VPS To Host

unable to conve

How to configure Bridged networks for VZLIN Hardware Node

5b048d9bddf8048a00aba7e0bdadef37 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF