Forum Discussion
Dexter
Altostratus
AltostratusViprion 2400 -- migrating from 2150B to 2250B
Hi All, I am planing to migrate current 2150B to 2250B on 2400 Chassis. Since its being a while, here are the steps I am planning to perform in order to do successful migration. Kindly guide me...
DexterAltostratus
Altostratusthanks for the detailed info. I know I cannot use 2 different blades at a single time from a same chassis, this means that I'll have to remove the one in production (all business services are down) and then do the migration. Sounds risky.
One thing more, once I swap in the new blade, is there any thing i need to configure/install ? I mean do I need to configure anything from Viprion side or simple connect the console with the 2250 and start migration. Also, I believe I have to go through initial configurations on F5 before I can reach the UCS part, correct?
NAG
Cirrostratus
Cirrostratus1) you said you have 2 viprion chassis. I assume you are using them to host active-standby setup for guests. If that's the true, all the guests are active on one Viprion host so you can carry out change on other Viprion chassis without disrupting prodution services.
2) once you swap the blades, configure management IP and activate license. And then upload Host UCS archive from previous setup and restore it.
Hope it helps,
Nag
- Dexter
Sadly thats not the case. Both Chasiss are standalone, i know its a design issue but I'm stuck now. I believe the only option is to shutdown the complete chasiss and install the new blade and start from scratch, this will result in huge downtime which won't be accepted
- NAG
vCMP hosts running on Viprions will always be standalone.. it's the guests which run upon them are setup as HA pairs. If A and B are in HA pair, if A is active on Host 1, B will be standby on Host 2.
Check if this is your setup, you can manage without downtime.
- Dexter
That too sadly isn't the case either. Both Chassis, Hosts and Guests are seperate environment from each other. Looks like no way around other then to shut the production down :/
- NAG
Looks like, there are no measures to minimise down time are built into the Architecture. Unless you use a new chassis with new blade, there is no way you can avoid downtime.
- Dexter
Yeah, that sucks. One more thing, i believe all I need to do is to first configure the new Blades with Interfaces (IP's, Trunks e.t.c.) and then simply restore the UCS taken from old vCMP to new vCMP.
This will I believe restores the Guests as well with Network Configurations, right? Or do I need to setup Guest same as deployed in current production and then only restore UCS on guest level once the Network configurations are done?