ā10-13-2022 01:45 PM
I'm seeing a lot of mixed results but I'm trying to figure why my time on ISE is wrong. Its off by an hour and I currently have it set for EST. I found a bug online CSCwb01843 where I would think that the daylight savings time would adjust automatically. I've seen some users end up shifting to UTC, but I've seen concerns with changing the time zone in the CLI can kill a deployment and you'll be forced to redeploy the VM. I'm hoping that 3.1 patch 4 resolves the bug so I don't have to update the time zone. Anyone else run into this issue?
Solved! Go to Solution.
ā10-13-2022 10:36 PM
What ISE version are you on now? I have just recently been working on a 3.0 customer whose timezone is subject to daylight savings and I have not noticed any issues before or after the daylight savings kicked in.
The topic of what timezone to configure is not well understood or documented. I have seen deployments running UTC on all nodes, or a mix and match of UTC and local timezone. All manner of combinations. I think it's all a misnomer. My theory is that the timestamp of the MnT is applied and that is used as the final timestamp that can be used in the Live Logs and Reports. The timezone on PANs and PSNs and PxGrid should (in theory) be irrelevant to what we eventually see in the live logs. I think that having the timezone set correctly for each node makes sense since it helps when troubleshooting an issue on a particular node - then the local logs will make sense.
You can change the timezone of a node without killing ISE. I have done that a few times too. It will restart services though
ā10-13-2022 10:36 PM
What ISE version are you on now? I have just recently been working on a 3.0 customer whose timezone is subject to daylight savings and I have not noticed any issues before or after the daylight savings kicked in.
The topic of what timezone to configure is not well understood or documented. I have seen deployments running UTC on all nodes, or a mix and match of UTC and local timezone. All manner of combinations. I think it's all a misnomer. My theory is that the timestamp of the MnT is applied and that is used as the final timestamp that can be used in the Live Logs and Reports. The timezone on PANs and PSNs and PxGrid should (in theory) be irrelevant to what we eventually see in the live logs. I think that having the timezone set correctly for each node makes sense since it helps when troubleshooting an issue on a particular node - then the local logs will make sense.
You can change the timezone of a node without killing ISE. I have done that a few times too. It will restart services though
ā10-14-2022 10:50 AM
We are running 3.1P3 at the moment. I'm schedueld to go to 3.1P4 on early next week. Your information is great! I'm thinking I might have to change it to America/New_York so it follows the automatic change.
ā10-14-2022 10:23 AM
EST is EST. To set the time zone to automatically change, you need to set it to either EST5EDT or America/New_York
ā10-14-2022 10:53 AM
Thanks! I'll give this a shot.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide