Quantcast
Channel: VMware Communities : Popular Discussions - VMware Server Archives
Viewing all articles
Browse latest Browse all 69891

BUG: vmnet-bridge bond0.xyz VLAN - too long interface name, not working

$
0
0

I have GSX Server v3.2.1 running on Linux (RHEL4) host.

 

I have bonded 2 NIC's as bond0, and created couple of VLANs.. bond0.12 and bond0.234

 

bond0.12 is bridged to vmnet0

bond0.234 is bridged to vmnet2

 

vmnet0 works OK.

 

vmnet2 doesn't work, because "bond0.234" is too long interface name.. copy&paste from dmesg:

 

"bridge-bond0.23: peer interface bond0.23 not found, will wait for it to come up"

 

It seems GSX (vmnet-bridge binary) clamps the ifname to 8 characters..

 

Process list shows this:

 

/usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-2.pid /dev/vmnet2 bond0.234

 

So the scripts are OK, but the vmnet-bridge binary is not working like it should..

 

eth0.234 works OK, because it's only 8 characters.

 

Is this already known bug/issue?

 

Any workarounds? (other than using only 2 digit VLAN IDs)

 

Thanks!


Viewing all articles
Browse latest Browse all 69891

Trending Articles



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