# Restart TMM frequency

**URL:** <https://community.f5.com/t/restart-tmm-frequency/73585>\
**Category:** Technical Forums\
**Tags:** application-delivery\
**Created:** [December 4, 2023, 5:03am UTC](https://community.f5.com/t/restart-tmm-frequency/73585 "2023-12-04T05:03:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![SanYang](https://avatars.discourse-cdn.com/v4/letter/s/45deac/32.png) [@SanYang](https://community.f5.com/u/SanYang)\
**Post date:** [December 4, 2023, 5:03am UTC](https://community.f5.com/t/restart-tmm-frequency/73585/1 "2023-12-04T05:03:56Z")

</div>

Hello,

Original environment :

 ![SanYang_0-1701665694368.png](https://d20hrnpixdzcsd.cloudfront.net/original/2X/2/2e4295da19187afa6e23d9ad4a40d651116daa3f.png)

I upgraded one F5 to 15.1.10.2.0.44.2 and switched to Active.

 ![SanYang_2-1701665998601.png](https://d20hrnpixdzcsd.cloudfront.net/original/2X/9/93c3311558632f9c8fbaf16940ac93ebf8bc6387.png)

The standby is constantly rerestarting tmm and the offline and standby states are constantly switching.  
Tried two groups in the same state with the same results…  
Has anyone encountered the same situation ?  
(p.s. For some reason the customer is unable to upgrade the standby to 15.1.10.2.0.44.2…)

Any help is appreciate.

---

<div class="post-metadata">

**Author:** ![F5\_Design\_Engineer](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/f5_design_engineer/32/2479_2.png) [@F5\_Design\_Engineer](https://community.f5.com/u/F5_Design_Engineer)\
**Post date:** [December 4, 2023, 8:40am UTC](https://community.f5.com/t/restart-tmm-frequency/73585/2 "2023-12-04T08:40:51Z")

</div>

Please check the vlan failsafe configurations vlan failsafe timeout value is configured as low, change that value

Also the network settings have to configure on both boxes individually as they don’t replicate so change on both box settings

Is it reboot setting than you need to disable it on the relevant vlans

> **[myF5](https://my.f5.com/manage/s/article/K13297)**

---

<div class="post-metadata">

**Author:** ![SanYang](https://avatars.discourse-cdn.com/v4/letter/s/45deac/32.png) [@SanYang](https://community.f5.com/u/SanYang)\
**Post date:** [December 4, 2023, 8:46am UTC](https://community.f5.com/t/restart-tmm-frequency/73585/3 "2023-12-04T08:46:41Z")

</div>

Hi @F5_Design_Engineer ,

Thanks for your reply.

I checked the settings and did not set vlan failsave…

---

<div class="post-metadata">

**Author:** ![zamroni777](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/zamroni777/32/1473_2.png) [@zamroni777](https://community.f5.com/u/zamroni777)\
**Post date:** [December 4, 2023, 9:31am UTC](https://community.f5.com/t/restart-tmm-frequency/73585/4 "2023-12-04T09:31:09Z")

</div>

check the /var/log/ltm

also upload the qkview to [ihealth.f5.com](http://ihealth.f5.com).  
it may provide some analysis

---

<div class="post-metadata">

**Author:** ![F5\_Design\_Engineer](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/f5_design_engineer/32/2479_2.png) [@F5\_Design\_Engineer](https://community.f5.com/u/F5_Design_Engineer)\
**Post date:** [December 4, 2023, 3:09pm UTC](https://community.f5.com/t/restart-tmm-frequency/73585/5 "2023-12-04T15:09:53Z")

</div>

Hi SanYang,

Have you done the **license reactivation** on the F5 before starting reboot to the new OS partition, if not done, please check and boot back to old partition from console port and fix the license reactivation.or if severity please open a TAC case for live tshoot.

Also&nbsp;&nbsp;it is highly recommended to **Force Offline the standby unit** while you upgrade it so that it will not declate itself as Active if HA issues. When you are ready to upgrade the primary, **before Force Offline the primar** y you have to&nbsp; **Release Offline on the standby** and do a **failover from primary** to make it standby and now once Primary is now standby & the upgraded Standby will be Active, now you can **force offline the primary** which is standby now, although in F5 **Primary /Secondary** are not used in F5 documentation, they use **Active/Standby** , but for our ease we can mark who is Primary before we start the OS upgrade activity and who is Seconday and based on that we can mark Active /Standby and switch the roled after failover. Also remember the reason stated is that HA Active/Standby  will not work properly on two different versions. There you will see HA state as Disconnected.

Please write back for more help.

HTH

🙏
