NimbostratusWe are planning to migrate from B4300 to B4500 in our environment. In current test environment we are having VIPRION 4480 Chassis in which currently one B4300 blade was installed. I am looking for a migration procedure which do not impact any of systems/configurations/services in it. Anyone can please suggest me?
CirrusIf you have HA set up, you can replace the blade in the standby chassis before upgrading the currently active chassis.
Make sure the hardware is compatible with the code version and make sure the old blade and new blade run a common code version before migrating.
F5 doesn't recommend using 2 different blade types in the same chassis.
See this link for adding a blade to a Viprion chassis.
You may try this Manual: VIPRION Systems: Blade Migration)
This covers B2000 to B2250 migration but may work for your case as well. I have not tried on B4450 myself though.
CirrostratusHello Manikanta!
I wonder if you have completed the migration since I'm going to do a very similar migration myself. Any tips for me?
Cheers! Rafael
NimbostratusHi,
Yes, we do completed the migration successfully. The process we followed is, 1. B4300 and B4450 are running on same code. 2. Download the UCS from existing B4300 and remove the blade from Chassis. 3. Update few things in the UCS as per F5 recommendation. 4. Upload it to B4450 with necessary installation steps.
CirrostratusGood!
How did you make sure both blades were on the same code version? Did you happen to have a secondary chassi?
Nimbostratuswe do have secondary chassis which we used to match the code on new blade with the existing one. But I believe, we can ask F5 to send the blades with the code you require.
CirrostratusWell... That ship has sailed... The blades are already on site.
I opened a ticket with F5 to make sure we cover our bases. Let's see what they say...
Thanks!