• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

a few quick networking questions

B

Berg0

[H]ard|Gawd
Joined
May 16, 2005
Messages
1,038
Hello,

I've got a few ESX and ESXi hosts. most of them have 4 NIC's. Most of the production stuff is using fiber HBA's for the vm storage, but most of the development boxes are using NFS. I've read here and there that you shouldn't run vMotion, management, and NFS traffic together over an aggregated link. but i've also spoken with people who have said it's fine. Anyone doing this? right now i"ve got my NFS VLAN, management VLAN, and vm traffic running over an aggregated link of 2 GbE, and vMotion over a seperate GbE trunk, not aggregated, on it's own VLAN, can I just aggregate all 4 GbE connections, and have my vMotion VLAN on that one? is there a noticeable performance depredation when a vMotion is occurring? do you guys do some form of QoS for that?
 
it's a dev environment. tot hat end, as long as nothing breaks, who gives a shit? here's what I would do:

1 nic for vm traffic
1 nic for nfs/management traffic
2 nic bonded link for vmotion

but, this is only IF your NFS server doesn't have more than one link on it. if it does, then I would create a 3nic bond for vmotion/nfs traffic, and let esx sort if out

lopoetve will come in here and say no vlans for nfs traffic, give it it's own switch...you could do that too:

1nic for vmotion
2 bonded for nfs traffic
1 for management/vm network
 
You must log in or register to reply here.
Back
Top