Dedicated CSV Network and Single iSCSI 10 GB Link?
- management network
- vm network (client data)
- csv network
- live migration network
- cluster heartbeat network
- iscsi (san)
- backup network
question hyper-v peers this, understand reasoning behind csv network. allowing data move between 4 host if 1 of san networks goes down. however, needed? if use plan use live migration network csv network.
so, think? should keep csv network , combine live migration network , make sure network card set lowest priority?
1 more question. our current design gives 10 gb iscsi connection. again on plane redundant , connected redundant switches. problem see have since host sees 1 network warnings don't have redundancy? should need worry mpio , ignore warnings?
kristopher turner | not brightest bulb far not dimmest bulb.
this looks good. published best practices guide recommends min. 5 networks, you're good.
about iscsi , mpio, need mpio if there's more 1 path between initiator (your server using iscsi lun) , target (the san that's unmasking lun). so, if have 1 iscsi nic on hyper-v host (initiator) , 1 iscsi nic on san, there's no need mpio, since there's 1 path. if have 2 iscsi nics on host, , 2 iscsi nics on san, have 4 paths between particular initiator , target. depending on san vendor may have manually spell out 4 path in mpio config (simply pointing out ipv4 address of each of 4 nics. not nic team or port channel iscsi nics. installing mpio require reboot. default mpio algorithm round robin, can changed, need so.
sam boutros, senior consultant, software logic, kop, pa http://superwidgets.wordpress.com (please take moment vote helpful and/or mark answer, applicable)
Windows Server > Hyper-V
Comments
Post a Comment