Are you using vDS (distributed switch) or standard vswitch? I'm not implying it will necessarily make any difference for you, but wanted to narrow down the possible issues.
there is an HCL guide, you should be able to google out fairly easily. most intel and broadcom Gigabit NICs are supported, but there might be exceptions ...
> until the limitations for VLAN technology is overcome what's the limitation of VLAN? what's not enough from vShield? can you spell it out? thanks.
> but nothing less that physical separation is enough to guarantee security. 1) isolation != security. physical separation is still an isolation, but not necessary security. ...
See more...
> but nothing less that physical separation is enough to guarantee security. 1) isolation != security. physical separation is still an isolation, but not necessary security. 2) i agree VLAN may not provide enough characteristics some people look for, but then i don't agree physical as opposed to virtual separation is necessary in that vSphere is providing a platform to show "virtual is better than physical" in aspects including separation.:)
Can you provide more info so that we can get to the bottom of the real issue. What virtual NIC are you using? problem goes away if you change the virtual nic type to another? how reproducible wh...
See more...
Can you provide more info so that we can get to the bottom of the real issue. What virtual NIC are you using? problem goes away if you change the virtual nic type to another? how reproducible when you had vmotion on the same vswitch?
> Yes, you could consolidate everything to a single vNDS and use VLAN to do the isolation but we could always do that with vNSSs as well. Once again, the point was merely to confirm whether...
See more...
> Yes, you could consolidate everything to a single vNDS and use VLAN to do the isolation but we could always do that with vNSSs as well. Once again, the point was merely to confirm whether or not there is something new in vNDSs that allows for fewer of them to be used. There isn't. Yes, we are on the same page. To make my comment future-proof, we are obviously looking at evolving vDS feature set and I'm not here to rule out the very "misleading" piece you were looking for. We can discuss further privately if you have NDA with us.
It is true that instead of manging two vSS on two hosts, you manage one vDS on one cluster. Btw, this is all software, whether one vswitch or two vswitch, other than the managemen...
See more...
It is true that instead of manging two vSS on two hosts, you manage one vDS on one cluster. Btw, this is all software, whether one vswitch or two vswitch, other than the management hassle (that hopefully vDS is addressing already), do you really care 1 vs. 2 vDS? Also in theory you can consolidate everything onto on vSwitch and use VLAN/PVLAN to do the isolation.
> The slide going around in the VMware presentation about vNDSs is very misleading - it definitely gives the impression that there is a consolidation step when migrating from vNSSs to vNDS...
See more...
> The slide going around in the VMware presentation about vNDSs is very misleading - it definitely gives the impression that there is a consolidation step when migrating from vNSSs to vNDSs. While you can consolidate using VLANs, you could do this with vNSSs as well. The higher consolidation comes when you have lots of hosts, vDS gives you much easier way to manage. vDS has a number of additional features that vSS does not have such as PVLAN. Does it make sense or you expected something else?
Hi, 1) I'm sorry but we don't have netflow experimental support. I will check with the doc people. 2) Drop me a private message if you actually use netflow in 3.5 and would love to discuss...
See more...
Hi, 1) I'm sorry but we don't have netflow experimental support. I will check with the doc people. 2) Drop me a private message if you actually use netflow in 3.5 and would love to discuss with you. Thanks, -howie
Hi, 1) I'm sorry but we don't have netflow experimental support. I will check with the doc people. 2) Drop me a private message if you actually use netflow in production in ESX 3.5 and wou...
See more...
Hi, 1) I'm sorry but we don't have netflow experimental support. I will check with the doc people. 2) Drop me a private message if you actually use netflow in production in ESX 3.5 and would love to discuss with you. Thanks, -howie
the primary reason we advocated dedicated nics for vmotion in the past is for performance and security isolation. but you are right that you may get the same isolation from using VLAN, you are...
See more...
the primary reason we advocated dedicated nics for vmotion in the past is for performance and security isolation. but you are right that you may get the same isolation from using VLAN, you are also right that some people do not feel it is the right tradeoff to dedicate a vswitch for vmotion. all i'm going to say here is that someone's best practice may not be the best in other's environment. today we do NOT require you to have a dedicated vswitch for vmotion anyways. also, you indeed may put all pNICs in one vswitch, but you want to make sure all of them are on the same broadcast domain. after that, you can tweak your teaming policy so that you "dedicate" one of them for vMotion but then it is also available for other clients (VMs etc.) during failover etc. -howie
Are you using it for productiion? I cannot talk about our roadmap on this public forum obviously, but if there are lots of people's life is depending on netflow, it does not hurt for me to know...
See more...
Are you using it for productiion? I cannot talk about our roadmap on this public forum obviously, but if there are lots of people's life is depending on netflow, it does not hurt for me to know. Thanks again!
TOE NICs can run under vSphere 4, but we don't really offload the tcp processing to the NIC because we have not seen enough benefits of doing this across various workload. You may enable TOE in...
See more...
TOE NICs can run under vSphere 4, but we don't really offload the tcp processing to the NIC because we have not seen enough benefits of doing this across various workload. You may enable TOE in VMDirectPath mode though.
see any of the following makes sense to you? 1) feature set. some of the featues only work on vDS but not vSS (standard switch). PVLAN is one example. outbound traffic shaping is anothe...
See more...
see any of the following makes sense to you? 1) feature set. some of the featues only work on vDS but not vSS (standard switch). PVLAN is one example. outbound traffic shaping is another example. there likely will be more down the road. 2) even if you don't care about any of the features, two different types of switches are more complext to manage. 3) some of 1) and 2) may not be so obvious today depending on your use cases, but what about "future proof" aspect? what if you want to move to Nexus 1000V in the future? -howie