lamav wrote:
Jon, how have you been, buddy? Long time....hope all is well.
Jon, believe me, I am totally feeling what youre saying..Im with you...I want to know the specifics of what in the code forces this requirement...what dataflow breaks if an L2 adjacency doesnt exist?
I think the answer is that the vmkernel interfaces in each of the hypervisors view the network as a large L2 broadcast domain and base their discovery and reachability on that. I know that through vCenter, the vmKernel communicates with other vmkernels in the domain, especially during a vMotion event. Or something like that....
Victor
Funny you should ask. Had a "slight" accident on my mountain bike and fractured my spine so i'm now looking at 6 - 8 weeks of lying in bed hoping that when it sorts itself out i still have the same mobility as before. Should do but i really want to be able to carry on biking. Apart from that everything else is fine. Not doing as much NetPro recently although that may change as i have very little else i can do.
I don't know the specifics in the code but obviously most devices such as servers/pcs/printers etc. all have enough code to understand L3 concepts ie. compare destination IP with my own IP using subnet mask to see if destination is on same or different network etc.. I suspect this code is not there in Vmotion because it doesn't need to be ie. you don't add code to an application that isn't needed. VMotion doesn't care about L3 addressing as such, it is only really cares about L2 addressing. It's a bit like asking why does STP not understand about IPs, the answer being that it doesn't need to because of the network layer it works at.
I appreciate that might not answer your question fully but i don't know the exact implementation details of VMotion.
Jon
