MBG with 2 IP addresses

[Tinos]

Hi all.
I have a micollab which used to work fine until the server brokedown.
The MBG and MiCollab were virtualized in ESXI. The host has 4 physical NICs.
MBG has a private and public IP address. Both private and public IP addresses are connected to the host on 2 different physical NICs.
Micollab works perfect internally but fails from the internet (it used to work before the breakdown).
My challenge is on configuring Networking in ESXI the correct way.
I have the private network connected on vmnic0 and the public one on vmnic1. With this micollab only works internally.
See attached snapshot.All vmnics are up and the red X is not there anymore.
Please assist.I would like to learn from this experience.

 

[sarond]

Looks like both physical NICs are connected to the same vSwitch (virtual switch in ESXi)
You need to create a new vswitch by "add Networking..." use the physical NIC vmnic1.
You need to go to the properties of the existing vSwitch and remove vmnic1 first before you can create a new vSwitch with it though.

You then add that to the VM (vMBG)

There is more to it than that like IP addressing, Gateways etc... but I am going to assume you know all those details.

 

[Tinos]

Hi sarond.

I have created a second vSwitch1 and assigned vmnic1.
Now how do I add vMBG to this switch since it is already on vSwitch0?
I believe the end result should have the vMBG having one connection to vSwitch0-->vmnic0--> private network(192.168.1.x) and other connecting to vSwitch1 -->vmnic1-->public network(167.x.x.x)
How do I do it?

 

[sarond]

Go to the vMBG VM and edit it, you can then add another NIC.

You will then need to reconfigure your vMBG to use the second adapter as the WAN.

 

[Tinos]

Hi sarond.
I have done as you advised and I get the below error:
Reconfigure virtual machine invalid configuration for device 0
see attachement

 

[sarond]

I have never seen that error before.

Can you create another VM (of any kind, you don't have to install anything) and add both adapters?

 

[Tinos]

I have resolved the issue of IP addresses by recreating VM. I now get an error in micollab server when I run diagnostics as follows:
micollab client deployment test from public internet - error:etimeout (400 Bad Request) from host 168.x.x.x
What can be wrong?

 

[Tinos]

I have checked the error and its 3 possible corrective measures. I don't understand what is config download host and there is no firewall.

 

[jpruder]

Might have to verify external dns values to see if the point correctly. For the newest software I'm thinking it's best to have both the names on the micollab and mbg resolve to the mbg if using the web proxy