Quantcast
Channel: VMware Communities : Popular Discussions - VMware Server 1
Viewing all articles
Browse latest Browse all 74849

VMNET bridged to Wrong ETH port

$
0
0

 

Hello all,

 

 

I use VMWare in a production environment and if the servers reboot (You know when a moron unplug your rackmount server carefully plugged in a UPS) then My VMNET are scrambled.

For instance I have 5 NICs in my server:

 

 

Onboard controller

eth0 - Console (not bridged)

 

 

 

Intel Quad Port Pro/1000 GT PCI-X

 

 

eth5 - VMNET0 (0.0.0.1)

eth6 - VMNET2 (0.0.0.2)

eth7 - VMNET3 (0.0.0.3)

eth8 - VMNET4 (0.0.0.4)

 

 

 

At the last reboot, I had to change my virtual machine to use VMNET4 instead of VMNET3 but the thing is that VMNET4 is currently used as cross wired connection to another VM server SO IT CAN'T BE ON THIS PORT FOR SURE.

To confirm this, if I unplug the physical cable at eth7 then I lose the connection for my virtual machine on VMNET4!

 

 

Here is the output you will certainly want:

 

 

ps ax | grep -i bridge                                                         

4141 ?        S      0:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth5

4151 ?        S      0:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-2.pid /dev/vmnet2 eth6

4156 ?        S      0:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-3.pid /dev/vmnet3 eth7

4161 ?        S      0:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-4.pid /dev/vmnet4 eth8

 

 

 

 

 

So I'd like your help to understand this and make the correction so this won't happen again.

 

 

 

 

 

 


Viewing all articles
Browse latest Browse all 74849

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>