Answer the question
In order to leave comments, you need to log in
How do you define logical network sites in System Center VMM?
I’ll make a reservation right away that I’m just mastering VMM, so don’t beat with my feet.
Here I have, say, two data centers: in Moscow and in Nizhny Novgorod. And I have three service logical networks: Management, Live Migration and Storage. Type of networks: VLAN-based independent networks. Each has two sites - Moscow and NN, each site has IP networks and VLANs registered directly.
And even just now it dawned on me that there are usually a few more hosts in data centers than in my lab. And that there are still different racks, and that there are a lot of them, and that keeping a thousand or two servers in one broadcast domain is not a good idea.
Therefore, I'm interested to hear your opinions on how best to define the site boundary for VMM. Rack? Row of racks? An entire data center? Well, at the same time, I will be very happy to learn about how IP addressing is organized in large data centers (the boundaries of IP networks, the number, lengths of masks, and that's all). Honestly, I googled and couldn't find it.
Answer the question
In order to leave comments, you need to log in
You have VLAN based. The broadcast domain is within a VLAN. Do not put many servers in one VLAN, and you will be happy :-) And they are in the same rack there, or at different ends of the city - it does not matter (well, if transmission delays are not critical). Everything depends on the tasks. Somewhere, geography comes first as a grouping criterion, and somewhere, semantic/functional grouping. Those. servers can be engaged in different things, and virtualize different things. It is logical that they should be combined into clusters, based on the functions assigned to these servers. And put the management of these servers in different VLANs.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question