HP Virtual Connect

[Deleted member 138126]

Alright folks?

Have just installed my first pair of HP VC Flex-10/10D Modules, and I have a few questions, in case anyone here is an expert.

- Is there any way of assigning server profiles with blades powered on? I'm really disappointed that it's forcing me to power the blades off, as that introduces a massive outage in order to cut over (cleanly remove old switches, install new switches, upgrade new switches firmware, configure, shut down blades, assign server profiles, power on blades, check).

- I am going to have 4 enclosures per datacentre (for now), would you recommend a single domain (max 4 enclosures), or would you recommend a domain per enclosure? I don't currently have budget for the VC Enterprise Manager.

Any gotchas or recommendations that spring to mind?

Thanks!

 

[img]

1.no but you can change networks while on just cannot mess with nics.
2. Done both ways. Are you going to still run network from each chassis or just out from 1 nad 4? Honestly we just go single now and script the setup. Didn't see much benefit in combining's apart from reducing my switch port need. I also used an internal link across vc for vmotion so it didn't need to hit the switch.

 

[Deleted member 138126]

Thanks @img.

Am going to run network from each chassis (1 uplink per switch, so 20Gb aggregate uplink per chassis).

What is the reason for going single? If I chose to have a domain for the 4 enclosures now, and needed to revert back to single, is that possible? Or does that require wiping literally everything and starting again?

I thought the benefit of combined domain was to have single point of reference, single pane to configure stuff, plus easy to move blades between chassis?

As far as internal link goes, what about vMotion between chassis?

 

[img]

If you combine them then you can have an internal link across the chassis for vmotion.
If you need to remove a chassis it needs to be wiped.

It is easier if your spanning various racks. I didn't see much benefit as single point as how often do you configure anything again.

Another thing was for patching there is only the risk for one chassis

 

[Deleted member 138126]

After a fair bit of reading, I agree, I'm going to run them individually. Scripting the configuration is dead easy, and shouldn't take more than 10-15 minutes to setup on each enclosure.

Thanks for the input!