Forum Discussion

DKC_21494's avatar
DKC_21494
Icon for Nimbostratus rankNimbostratus
Apr 08, 2009

config save hangs ...

I am trying to backup my configuration for an F5 unit that I recently became responsible for. After typing "BIGPIPE config save myconfig", the system waits a few seconds, clears the console and prints "Saving active configuration...", then nothing. I am finding a ucs file in the /var/local/ucs directory of 238123 bytes.

 

 

I am concerned that I may have a corrupted configuration, so if anyone can help me to answer the next set of logical questions:

 

 

1) Has this process actually hung? I am expecting more text making me feel good about my backup, but I might just be expecting too much.

 

 

2) Is there a way to validate the current configuration in the F5?

 

 

3) Is there a way to validate the generated ucs file without loading it back into my only F5?

 

 

4) Is there an alternative to this method for saving the complete F5 configuration?

 

 

Many Thanks!

3 Replies

  • You get returned to the prompt when the command completes:

     

     

    [hoolio@test1_6400:Active] ~ b config save test.ucs

     

    Saving active configuration...

     

    [hoolio@test1_6400:Active] ~

     

     

    A UCS archive is a gzip'd tar archive. So you can use the tar command on the LTM command line or a Zip utility on your workstation to see if the UCS is a valid tar archive:

     

     

    [hoolio@test1_6400:Active] ~ tar tvfz /var/local/ucs/test.ucs |less

     

     

    This should list the files in the archive.

     

     

    A 238kB UCS isn't very large. I wouldn't expect it to take more than a minute to create a UCS of that size. In 9.4.7, LTM returns an error if the config save process fails:

     

     

    [hoolio@test1_6400:Active] ~ b config save test.ucs

     

    Saving active configuration...

     

    /tmp/configsync.spec: Error creating package

     

     

    WARNING:There are error(s) during saving.

     

    Not everything was saved.

     

    Be very careful when using this saved file!

     

     

    Error creating package

     

    Error during config save.

     

    BIGpipe parsing error:

     

    01020001:3: The requested operation failed.

     

     

    If you're not able to test by loading the UCS and not sure if the UCS that's being created is valid, you could open a case with F5 Support and see if they could load your UCS on a test unit.

     

     

    Aaron

     

  • Hi,

     

     

    I edited the pool name through BigIP LTM CLI interface but when I save the config it is still showing the old pool name.

     

     

    Please help what all commands are required to save the configuration.

     

     

    Regards,

     

    Puneet