Forum Discussion

kevin5866_19733's avatar
kevin5866_19733
Icon for Altostratus rankAltostratus
Feb 20, 2019
Solved

Upgrade from 2150-2250 blades

I am planning an upgrade from 2150 blades to 2250 blades. Single blade in each chassis. Not finding any docs regarding this patch. I have upgraded from 2100-2150 in the past and do see those docs out there. I could also rebuild from scratch using UCS files. Also have concerns as interfaces will be different, instead of 1.1-1.8, they will be 1.1-1.4 and 2.1-2.4

 

Are there any docs out there regarding this path, or has anyone done this so I can understand what I am to expect.

 

  • Migrating 2150 blade (Existing chassis) to new 2250 blade (new F5 chassis):

     

    1. Take UCS backup of present devices.
    2. Configure management IP on new blades with different IP.
    3. Restore the UCS files on new blades with no-license and no-platform-check commands
    4. Make sure new blades are connected to different switch ports.
    5. Now change the interfaces 1.1-1.4 and 2.1-2.4 (1.5 to 1.8 move here) on new blades and assign respective VLANs/Self IP's.
    6. Make sure all configurations are in place before the maintenace activity.
    7. During the maintenance activity day disable interfaces on existing 2150 F5 and enable it on new 2250 blade.
    8. Clear the arp entries on connected switches for the subnets which are configured on F5.

    Hope this helps and let me know if any more information is required.

     

4 Replies

  • Migrating 2150 blade (Existing chassis) to new 2250 blade (new F5 chassis):

     

    1. Take UCS backup of present devices.
    2. Configure management IP on new blades with different IP.
    3. Restore the UCS files on new blades with no-license and no-platform-check commands
    4. Make sure new blades are connected to different switch ports.
    5. Now change the interfaces 1.1-1.4 and 2.1-2.4 (1.5 to 1.8 move here) on new blades and assign respective VLANs/Self IP's.
    6. Make sure all configurations are in place before the maintenace activity.
    7. During the maintenance activity day disable interfaces on existing 2150 F5 and enable it on new 2250 blade.
    8. Clear the arp entries on connected switches for the subnets which are configured on F5.

    Hope this helps and let me know if any more information is required.

     

    • kevin5866_19733's avatar
      kevin5866_19733
      Icon for Altostratus rankAltostratus

      This is my backup plan, was wondering if anyone has done the auto upgrade that I have used in the past to go from 2100 to 2150/2250, in this case going from 2150 to 2250.

       

  • Migrating 2150 blade (Existing chassis) to new 2250 blade (new F5 chassis):

     

    1. Take UCS backup of present devices.
    2. Configure management IP on new blades with different IP.
    3. Restore the UCS files on new blades with no-license and no-platform-check commands
    4. Make sure new blades are connected to different switch ports.
    5. Now change the interfaces 1.1-1.4 and 2.1-2.4 (1.5 to 1.8 move here) on new blades and assign respective VLANs/Self IP's.
    6. Make sure all configurations are in place before the maintenace activity.
    7. During the maintenance activity day disable interfaces on existing 2150 F5 and enable it on new 2250 blade.
    8. Clear the arp entries on connected switches for the subnets which are configured on F5.

    Hope this helps and let me know if any more information is required.

     

    • kevin5866_19733's avatar
      kevin5866_19733
      Icon for Altostratus rankAltostratus

      This is my backup plan, was wondering if anyone has done the auto upgrade that I have used in the past to go from 2100 to 2150/2250, in this case going from 2150 to 2250.