Yes it's safe...
It will take another IP if the VR is not destroyed / expunged correctly:
the system will expect that this VM can be re-spun-up...
lower your expunge delay if you want to ensure that this VR will use the
same IP...
on ACS / Global settings / expunge delay , set it to 60 sec
Hi Marcus,
is it safe to destroy VR, on some troubleshooting guides it tells us to
never destroy VR? one time i destroyed vr and it took new ip from guest ip
network, so is it safe to destroy VR?
whats your opinions ?
Thanks
2016-05-31 17:38 GMT+03:00 Marc-Andre Jutras :
Hey !
personally, I would recommend to run everything on UTC but it's up to you...
If everything is in ntp-sync, maybe an old api call was waiting on the
VR to get consumed by ACS... Just to be sure, destroy / re-create the VR
and check if you're still seeing the same warning message...
Hi;
All management servers and hypervizors are in ntp time sync.
My management and hypervisor servers are using my local timezone(UTC+5) but
they are synced with ntp but you know systemvm’s are using default UTC
timezone, do i need to set management and hypervisors server to UTC for ACS
to work
Hi,
I see some different logs in my management server. I do not understand what
is the meaning of this [ALERT] , is it bug? Can i ignore that?
The [ALERT] logs are below.
2016-05-30 09:47:45,451 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-10:null) (logid:) Seq 10-1235393672783119940: