Unsolved
This post is more than 5 years old
1 Message
0
21415
November 16th, 2010 02:00
M1000e and Hyper V
Hey guys
scouted the forum quickly looking for some advice. i have an m1000e chasis and i want to use it for virtualisation solution.
basically i have an old chasis holding 1855/1955 blades and the switch modules on the back are configurable. i have them teamed for various networks. i,e, 4 for LAN, 3 for dmz network and 3 for access to storage network. so when you give a blade in the chasis an ip address on either network the switch module does all the switching and the NICs arent directly patched on a 1 to 1 basis.
now what i want to do is have the same situation on the m1000e and use that for hyper v basically creating a massive highly available chasis.
my questions are:
is there a module available for the m1000e that is configurable in the same way? at the moment we have only pass through modules.
How would you go about the NIC's in that situation. what is the MAX NICs you can have per blade and would this limit my intended useage?
is there a way to configure any internal networks on the chasis that is only available to the blades and not the outside world. I could use this for live migration, heartbeat or CSV?
ok i think that covers it for now! thanks for your help.
scouted the forum quickly looking for some advice. i have an m1000e chasis and i want to use it for virtualisation solution.
basically i have an old chasis holding 1855/1955 blades and the switch modules on the back are configurable. i have them teamed for various networks. i,e, 4 for LAN, 3 for dmz network and 3 for access to storage network. so when you give a blade in the chasis an ip address on either network the switch module does all the switching and the NICs arent directly patched on a 1 to 1 basis.
now what i want to do is have the same situation on the m1000e and use that for hyper v basically creating a massive highly available chasis.
my questions are:
is there a module available for the m1000e that is configurable in the same way? at the moment we have only pass through modules.
How would you go about the NIC's in that situation. what is the MAX NICs you can have per blade and would this limit my intended useage?
is there a way to configure any internal networks on the chasis that is only available to the blades and not the outside world. I could use this for live migration, heartbeat or CSV?
ok i think that covers it for now! thanks for your help.
No Events found!
Kong Yang
180 Posts
0
November 16th, 2010 13:00
You have quite a few options for IO Modules for the M1000e - http://www.delltechcenter.com/page/IO_Infrastructure .
Your max NICs per blade depends on the blade servers that you have in combination with the IO Modules that you choose.
To isolate your network, you have a few options- you can use VLANs, you can use different subnets, or you can group your ports and LAG them into an internal only switch.
In addition, there are published reference architectures and network guides for Dell M1000e blade solutions running Hyper-V:
http://i.dell.com/sites/content/business/solutions/engineering-docs/en/Documents/reference-architecture-hyper-v-blades-fibre-channel.pdf
http://content.dell.com/us/en/enterprise/d/business~solutions~engineering-docs~en/Documents~hyper_network_guide_01.pdf.aspx