
OPERATIONAL DEFECT DATABASE
...

...
After TMM crashes and restarts, in-TMM monitors do not run. ... Monitored pool members are down. ... Impact ... Monitored pool members are offline. ... Conditions ... -- In-TMM monitors are enabled. -- TMM exits abnormally, as a result of one of the following: + TMM crashing and restarting + TMM being sent a termination signal (i.e. using 'pkill' to kill TMM) Note: This issue does not occur if TMM is restarted using 'bigstart' or 'tmsh sys service'. ... Workaround ... Do not use in-TMM monitors. ... 2. After TMM restarts, manually restart bigd: tmsh restart sys service bigd 3. ... Add an entry to /config/user_alert.conf such as the following, so that the system restarts bigd when TMM starts up. ... On an appliance or single-slot vCMP guest/tenant: alert id1046917 "Tmm ready - links up." { exec command="bigstart restart bigd" } On a VIPRION or multi-slot vCMP guest/tenant: alert id1046917 "Tmm ready - links up." { exec command="clsh --color=all bigstart restart bigd" } Note: This cha...
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.