viouser
Contributor
Contributor

VIO API network issue

Hello everyone ,

im about to install VIO 4.1.0.0 on top of my vmware infrastructure but i got an issue with API network, it said that virtual machines IP addresses are in use however im pretty sure that they are not.

vcenter is reachable by vio manager and the DNS works fine, API network doesnt accept any ip address but if i provide the ip of the Default gateway to the load balancer it goes well ! im confused 😕 Can anyone please help me ? Thank you in advance

0 Kudos
10 Replies
Mike_Gray
Enthusiast
Enthusiast

the issue still persist ?

0 Kudos
viouser
Contributor
Contributor

yes it does Smiley Sad

0 Kudos
Mike_Gray
Enthusiast
Enthusiast

Do you have separate port group of your oms management network and api network ? 

0 Kudos
viouser
Contributor
Contributor

yes of course , i ve created 2 port groups , one for the oms management tagged to the appropriate vlan and another port group tagged with different vlan.i did the deploiment many times but the error persists all the time.

0 Kudos
viouser
Contributor
Contributor

no body resolve this issue before ??

0 Kudos
Mike_Gray
Enthusiast
Enthusiast

what is the error you are getting ?

0 Kudos
viouser
Contributor
Contributor

hi Gary , when I provide the pool of addresse  dedicated to the API network it doesnt work with an error : IP addresses are already in use with different virtual machines but im sure they are not 😕

0 Kudos
Mike_Gray
Enthusiast
Enthusiast

are you facing the issue in this step ? or before ready to complete ? what is the metadata proxy network  you are using ?

pastedImage_0.png

0 Kudos
viouser
Contributor
Contributor

yes im stuck on that step i cannot move due to ip adresses problem , what do you mean please  with metadata proxy ?

0 Kudos
escher100
Contributor
Contributor

It's been awhile since activity on this one, but I'm seeing the same issue.  I've been able to create a successful deployment but using a public IP (22.1.1.100) and not a private (192.168.100.100).  Of course this is less than desirable.  I had to set up many static routes to accommodate this in many places.

So my WORKING API is 22.1.1.100

And my WORKING Management is 192.168.101.50 - 192.168.101.55

Any additional information available on this topic?

0 Kudos