We have a 4 node ISE 2.1 deployment for which I need to change the timezone from EST to EST5EDT.
I began by first making the change on one of our two PSN's, but the process has seem to have hung. Here is a copy of the script...
HSNISE04/admin# sh clock
sh timezone
conf t
clock timezone EST5EDT
end
Fri Oct 27 14:21:37 EST 2017
HSNISE04/admin# sh timezone
EST
HSNISE04/admin# conf t
Enter configuration commands, one per line. End with CNTL/Z.
HSNISE04/admin(config)# clock timezone EST5EDT
% On ISE distributed deployments, it is recommended all nodes be
% configured with the same time zone.
Continue with time zone change? Y/N [N]: Y
HSNISE04/admin(config)# Y
^
% invalid command detected at '^' marker.
HSNISE04/admin(config)# end
HSNISE04/admin# sh timezone
EST
HSNISE04/admin# conf t
Enter configuration commands, one per line. End with CNTL/Z.
HSNISE04/admin(config)# clock timezone EST5EDT
% On ISE distributed deployments, it is recommended all nodes be
% configured with the same time zone.
Continue with time zone change? Y/N [N]: y
System timezone was modified. You must restart ISE for change to take effect.
Do you want to restart ISE now? (yes/no) yes
ISE M&T Log Collector is disabled
ISE M&T Log Processor is disabled
ISE PassiveID Service is disabled
ISE pxGrid processes are disabled
Stopping ISE Application Server...
ISE Certificate Authority Service is disabled
ISE EST Service is disabled
ISE Sxp Engine Service is disabled
ISE TC-NAC Service is disabled
Stopping ISE Profiler Database...
Could not connect to Redis at 127.0.0.1:6379: Connection refused
After waiting 30 minutes for somethign to happen, I opened a second SSH session to the same server to see if I could see what was going on. I noticed that the Application Server was not running:
HSNISE04/admin# sh application status ise
ISE PROCESS NAME STATE PROCESS ID
--------------------------------------------------------------------
Database Listener running 5141
Database Server running 57 PROCESSES
Application Server not running
Profiler Database running
ISE Indexing Engine disabled
AD Connector running 9265
M&T Session Database disabled
M&T Log Collector disabled
M&T Log Processor disabled
Certificate Authority Service disabled
EST Service disabled
SXP Engine Service disabled
TC-NAC Docker Service disabled
TC-NAC MongoDB Container disabled
TC-NAC RabbitMQ Container disabled
TC-NAC Core Engine Container disabled
VA Database disabled
VA Service disabled
pxGrid Infrastructure Service disabled
pxGrid Publisher Subscriber Service disabled
pxGrid Connection Manager disabled
pxGrid Controller disabled
PassiveID Service disabled
DHCP Server (dhcpd) disabled
DNS Server (named) disabled
So, I tried to start the application back up and this is what I got:
HSNISE04/admin# application start ise
Waiting up to 300 seconds for lock: SET_TIMEZONE to complete
Database is still locked by lock: SET_TIMEZONE. Aborting. Please try it later
% Error: Another ISE DB process (SET_TIMEZONE) is in progress, cannot perform Application Start at this time
And of course, on the ISE web console, it is showing that node as disconnected. Additionally, it appears that the timezone change did indeed take affect.
HSNISE04/admin# sh clock
Sat Oct 28 09:13:32 EDT 2017
HSNISE04/admin# sh timezone
EST5EDT
So my question is, how do I get this application server started so I can continue changing the timezone on the other servers in my deployment?
Thanks in advance.
John
