I am fairly new to netscaler administration and have noticed when logging into various netscalers in our environment, they may have the save running config button illuminated, showing changes that have been made but yet to be saved. I totally understand that a GUI can have bugs and artifacts, and have been told that it will randomly report needing to be saved when it does not really need to be. However, in each instance, the "last config saved time" is prior to the "last config changed time" on the system information. Is that common that the netscaler would have incorrect timetamps and be reporting that it needs to be saved when in reality it doesn't? Is there any netscaler KBs or documentation that reflects that as a common occurrence? I haven't found it if so.

Yup. completely common. It just happens.

The button illumination or even the timestamps being incorrect?

The button enumeration. Basically every time you see the dot on it and hit save it will tell you if there isn't any necessary changes.

But if the last saved is earlier than the last changed, it definitely hasnt been saved since changed, correct?

Correct.

Awesome - thanks

If you look at the Diagnostics section and do a saved vs. running, you usually see that the hashed password for the RPC is what is shown as "changed." This is a known GUI issue. I want to say the hashed value changes often even though the actual password has not changed, and you will get a "There are no changes" message if you try and save.