Investigating changing ISE timezone. Admin guide and CLI are not in sync. Which one is correct?
Admin guide says the ISE app must be restarted.
Admin Guide - Change the System Time Zone
Changing the time zone on a Cisco ISE appliance after installation requires ISE services to be restarted on that particular node. Hence we recommend that you perform such changes within a maintenance window. Also, it is important to have all the nodes in a single ISE deployment configured to the same time zone. If you have ISE nodes located in different geographical locations or time zones, you should use a global time zone such as UTC on all the ISE nodes.
CLI guide says the app must be reset:
CLI Guide - Restoring the Time Zone in Cisco ISE Nodes
Warning Changing the time zone on a Cisco ISE appliance after installation causes the Cisco ISE application on that node to be unusable. However, the preferred time zone (default UTC) can be configured during the installation when the initial setup wizard prompts you for the time zones.
Changing time zone impacts different Cisco ISE nodes types of your deployment.
To recover from the impact, use the following steps:
Standalone or Primary ISE Node
Changing the time zone after installation is not supported on a Standalone or Primary ISE node.
If you inadvertently change the time zone, do the following:
- Revert to the time zone back. (the time zone before it changed).
- Run the application reset-config ise command from the CLI of that node
- Restore from the last known good backup before the time zone change on that node.
