VMware Cloud Community
Peanuts_blackfl
Contributor
Contributor

Work on vCenter from both NIC's

Hi all,

We are 2 students who need to make a paper for our last weeks at school. The assignment is to build a small SAN, but we are having some difficults on the first steps of creating  a few VM's (=our servers)

We have system x3550 from IBM. On this machine is ESXi 4.1.0 installed. On this machine we have a vCenter running to make all our VM and etc.

The problem is:

There are 2 physical ethernet ports on the system x3550 (the NIC's). Each of us is connected with a ethernet cable in the physical ports.

Whenever 1 of us is connecting (on NIC1) to the management network (172.27.4.102) nothing is wrong. He connects to the vCenter (172.27.4.110) with the VMware vSphere Client. All is going well so far. Whenever the other one plugs in his ethernet cable (on NIC2), the first one looses his connection and the 2nd one can do all the managing (=making a VM, deploying, ... through VMware vSphere Client).

It's not that bad after all, since we don't need the vCenter often, just to boot up our VMs.

The real problem lies in the connection to our VMs (=some servers to put up a basic domainnetwork). If 1 of us is on Remote Desktop and the other one connects to another server, the first one looses all connectivity. And that's pretty annoying because we want to both, at the same time, configure our servers..

Now is there a way so we can connect both to vCenter, ping and work on our server? Or is there a workaround?

Or is it really designed so only 1 laptop/computer can connect/ping/... to vCenter and other VMs???

Maarten, really desperate :smileysilly:

added a screenshot of our vSwitch

Reply
0 Kudos
3 Replies
idle-jam
Immortal
Immortal

on way is to disable the nic2, and then connect nic 1 to a wireless AP and that everybody can use it. anyway i would advise doing a active-passive link on the teaming policy. for active-active to work you might need to configure the right load balancing policy and  switch level configuration is needed. for more info please refer to: http://kb.vmware.com/kb/1004088

bulletprooffool
Champion
Champion

Do you have a spare physical swicth knocking about? You can both connect on the same port - just patch the VC to the physical switch?

One day I will virtualise myself . . .
Reply
0 Kudos
depping
Leadership
Leadership

How about just connecting the server to a "switch" and just not using RDP but use the vSphere client on your laptop/desktop to connect?

Duncan (VCDX)

Available now on Amazon: vSphere 4.1 HA and DRS technical deepdive

Reply
0 Kudos