Forum Discussion

Chris_FP's avatar
Chris_FP
Icon for Cirrus rankCirrus
Jan 13, 2015

Viprion Upgrade - How to make sure existing config is copied

Hi,

 

We've got a number of Viprions (No vCMP, 1 blade) which I need to upgrade from 11.4.1 to 11.5.1. However when I get to the Boot Locations the option to copy config is greyed out and set to no. As these boxes are in a remote location, with no serial connectivity I don't really want to reboot without the existing config being copied over (especially the bigip_base.conf).

 

Surprised that there isn't a SOL document (that I can find!) which explains the situation as having the config not come over is a major issue (and drawback).

 

Can somebody confirm the precises steps to carry out to upgrade a Viprion and make the config move over as well.

 

Many thanks in advance

 

8 Replies

    • Chris_FP's avatar
      Chris_FP
      Icon for Cirrus rankCirrus
      I'd rather have a definite "yes it does" - as I said this box is remote (100's of miles away) so would rather not risk a maybe
    • Chris_FP's avatar
      Chris_FP
      Icon for Cirrus rankCirrus
      I'd rather have a definite "yes it does" - as I said this box is remote (100's of miles away) so would rather not risk a maybe
  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus

    Chris, I believe the upgrade process is exactly the same but, as you note, there is no option to copy config. Whilst this sol doesn't say so it suggests this would be the case:

     

    https://support.f5.com/kb/en-us/solutions/public/14000/700/sol14704.html

     

    I agree with Brad, however, that the config should copy over based on the following sol.

     

    https://support.f5.com/kb/en-us/solutions/public/13000/400/sol13438.html

     

    If you check the output of the commands it should give you the reassurance you need.

     

    Hope this helps,

     

    N

     

  • I realize that this is an older post, but I just went through this with viprion and vcmps. When the vcmps have the new image copied to their boot location, the current configuration is copied over. However, in my situation, that was a few weeks back. During my maint window when I went to make the new boot partition active, the configuration was not copied again. I'm now in a situation where my older configuration (vips, pools, nodes, etc) is as it was the day that I installed the image to the new boot location. I'm having to boot to the older boot location and clsh cpcfg from current boot to new boot manually to correct this.