We have 02 F5 using High Availability (Active-Standby).
In upgrade processs we need re-active license. but because related to application we should be change time
Example:
The present (28/05/2023). After change time on NTP Server ( Note: F5 synced time with NTP Server). to 30/05/2023 -- then we re-active license and upgrade firmware, -- then tried test application.
Finnally We tried test application finished. we have rollbacked time to 28/05.
Hi @Hoang_Hung , Q) If you are asking if Re-activating license on bigip cause production impact ? A) Yes it Causes impact and interrupt the Production traffic according to this Article from F5 : https://my.f5.com/manage/s/article/K35783352
But unfortunately I don't understand the part of changing time from ( 30/05 ) to ( 28/05 )
Because it relates to the application Example: The application runs only from Monday to Friday. We upgrade from Saturday and tried test application. Note. If need try test we need change to Database, time app to Monday. on NTP server. ( All devices are syned to NTP Server). After we rollback time to the present. Thank
Hi @Hoang_Hung , why don't change this time from Application server itself not from NTP server. by this way you will be totally far from NTP and Bigip appliances and all different Network Devices.
Just I recommend that to be used.
another thing How will you change NTP time , as further I know NTP Protocol sync UTC ( GMT ) Time with all devices , I think you have to change this time from the Backend servers , you have to combine them in your Maintenance window of Upgrade.
Take a look in the Following Article which clarify how NTP Server/Protocol works :
So, it is important to understand what license (re)activation does any WHY it is important I think. What this does is update the various subscription/service conrtact etc dates on the BIG-IP unit to be at parity with what F5 Support has on file. This changes of course when you want to add a new module, or even if you extend your terms of service with F5. That said, what is updated is the last valid date. So when this is updated, it is embedded in the license and is NOT impacted by changing the time... unless you change to a time in the future, after those dates have expired.
Now there are 2 impacts.... - If you do not (re)activate license, and try to install BIG-IP softare (via upgrade) which is newer than those expiration / validity dates, then serviecs will not start and configuration will not load. Outage. - When you (re)activate, the services restart and there is a loss of service. So always suggest performing this on the standby unit, failing over, and finishing up the same (re)activation process on the last unit of the High Availability group. Avoid performing this on the ACTIVE unit.
@Hoang_Hung - If your post was solved it would be helpful to the community to select *Accept As Solution*. This helps future readers find answers more quickly and confirms the efforts of those who helped. Thanks for being part of our community. Lief
