Technical Forum
Ask questions. Discover Answers.
cancel
Showing results for 
Search instead for 
Did you mean: 
Custom Alert Banner

error creation time is not user configurable

Surya_Kant_Pasa
Altostratus
Altostratus

Hi Team,

While reloading an Archive on the F5 Device V14.1 we have observed the below error : 

Loading configuration...
/config/loadconfig21.txt
01071d53:3: virtual server: /Common/testvs attribute:creation time is not user configurable.
Unexpected Error: Loading configuration process failed.

The above error is obseved just for V14 and is not observed either on V15 or V13. I have searched the F5 site and could not find any reference for such error, request you to redirect me to any article as to why we are recieving such error only for specific F5 verison, Can this be a bug ?

2 ACCEPTED SOLUTIONS

Hi Surya_Kant_Pasa

Can you delete the lines containing creation-time and last-modified-time from the loadconiig21.txt file and try again?

View solution in original post

CA_Valli
MVP
MVP

Hello, I don't know if it's a bug or not, it looks like "creation time" parameter is not well-liked by the configuration parser. Are you trying to copy config across different versions?

To fix this issue you'll need to manually edit loadconfig21.txt file and remove "creation time" configuration from your Virtual Server object.

 

View solution in original post

4 REPLIES 4

Hi Surya_Kant_Pasa

Can you delete the lines containing creation-time and last-modified-time from the loadconiig21.txt file and try again?

Yes this works, What i wonder is this error was not observed on other version. Thanks for the input.

CA_Valli
MVP
MVP

Hello, I don't know if it's a bug or not, it looks like "creation time" parameter is not well-liked by the configuration parser. Are you trying to copy config across different versions?

To fix this issue you'll need to manually edit loadconfig21.txt file and remove "creation time" configuration from your Virtual Server object.

 

Yes CA_Villi , this Worked. Also removing those attribute does not impact the bigip.conf file in any ways.