http://itknowledgeexchange.techtarget.com/virtualization-pro/quickly-adding-virtualcenter-25-network-redundancy/ Sat, 30 Aug 2008 06:03:35 +0000 http://wordpress.org/?v=wordpress-mu-1.2.1 http://itknowledgeexchange.techtarget.com/virtualization-pro/quickly-adding-virtualcenter-25-network-redundancy/#comment-48 Bizrisky Thu, 28 Feb 2008 16:15:33 +0000 http://itknowledgeexchange.techtarget.com/virtualization-pro/quickly-adding-virtualcenter-25-network-redundancy/#comment-48 In our configuration we stack console 2 onto our vmotion nic and both of these are on a separate switch and subnet. You may not be able to easily get to the second console via the VC server but you can certainly use the VC client on your desktop to connect to console 2 IP using the root account (even if VC server is connected to console 1 at the same time). In our configuration we stack console 2 onto our vmotion nic and both of these are on a separate switch and subnet. You may not be able to easily get to the second console via the VC server but you can certainly use the VC client on your desktop to connect to console 2 IP using the root account (even if VC server is connected to console 1 at the same time).

]]> http://itknowledgeexchange.techtarget.com/virtualization-pro/quickly-adding-virtualcenter-25-network-redundancy/#comment-47 Blithespirit Thu, 28 Feb 2008 08:17:34 +0000 http://itknowledgeexchange.techtarget.com/virtualization-pro/quickly-adding-virtualcenter-25-network-redundancy/#comment-47 I found that by adding a second console to the Vmotion network with an IP range that is not on the main network is suffiecient to deal with any problem, the requirement is that HA requires access to a second redundant service console, any range as long as it is the same on all second service console ports will suffice to enable HA removing the notice. if you want true redundancy then a second switch along side the console would be a requirement and as we all know this can then be redundancy sprawl and go silly mode kicks in on expediture. if you add another service console IP address VC will not manage through this as it is only connected by Vswitch0, so the second console will theoretically not do much outside HA. open to views & thoughs ? I found that by adding a second console to the Vmotion network with an IP range that is not on the main network is suffiecient to deal with any problem, the requirement is that HA requires access to a second redundant service console, any range as long as it is the same on all second service console ports will suffice to enable HA removing the notice. if you want true redundancy then a second switch along side the console would be a requirement and as we all know this can then be redundancy sprawl and go silly mode kicks in on expediture. if you add another service console IP address VC will not manage through this as it is only connected by Vswitch0, so the second console will theoretically not do much outside HA. open to views & thoughs ?

]]>