Article ID: 124120, created on Dec 31, 2014, last review on Dec 31, 2014

  • Applies to:
  • Operations Automation 5.5
  • Operations Automation 5.4

Symptoms

If new VM is created without public IP, its bridged interface is disconnected from VM. It can be seen by (-) sign in the following command's output:

# pctl list 1.testwin --info | grep net
Boot order: hdd0 cdrom0 fdd0 net0 net1
net0 (+) dev='vme661b3e25.0' ifname='eth0' type=routed mac=123C42D5C0E3 card=e1000 ips='172.28.1.161/255.255.0.0 '
net1 (-) dev='vme661b3e25.1' ifname='eth1' network='Bridged' mac=123C422329FB card=e1000

As result when customer adds new public IP, it is getting added to net1, but not seen inside VM because net1 is disabled:

# pctl list 1.testwin --info | grep net
Boot order: hdd0 cdrom0 fdd0 net0 net1
net0 (+) dev='vme661b3e25.0' ifname='eth0' type=routed mac=123C42D5C0E3 card=e1000 ips='172.28.1.161/255.255.0.0 '
  net1 (+) dev='vme661b3e25.1' ifname='eth1' network='Bridged' mac=123C422329FB card=e1000 ips='46.226.92.10/255.255.255.0 ' gw='46.226.92.1'

After restarting the VM, new IP can be seen inside it.

Cause

Bug CCU-8206

Resolution

The issue has been reported to the development team as a bug CCU-8206. It will be fixed in future versions of POA. Please contact your Account Manager to trace the status of the issue.

To workaround the issue, it is necessary to restart the affected VM.

Search Words

PACI

can't remote access

restart is required to update VM network settings after first IP adding and last IP removal

ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 5b048d9bddf8048a00aba7e0bdadef37

Email subscription for changes to this article
Save as PDF