3 Replies Latest reply on Nov 14, 2017 11:03 AM by ollydrew

    Why does the ${StorageFilename} variable cause a F5 .ucs file to get a garbled.config file name?


      Working on backing up F5 configs and have found that if I keep the ${StorageFilename} variable, the file changes from DeviceName-Date.ucs to a garbled.config file after the file is copied off the F5 and moved to the Binary config location specific within NCM.   This is causing confusion with our network admins as they are expecting to be able to see the .usc file.   I'm also unsure if the file can simple be renamed .ucs and it will work as intended.    Is this a bug?  Is there somewhere within NCM I can define the ${StorageFilename} to prevent this?