For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Jason_40733's avatar
Jason_40733
Icon for Cirrocumulus rankCirrocumulus
Nov 20, 2013

GTM 10 to 11 upgrade experiences

Anyone have any experiences they can share on GTM 10 to GTM 11 upgrades?   Specifically, has it been a smooth upgrade or did you have to rebuild topology rules, wideip entries, pools, etc.?   We ...
cloud
Jason_04_138617's avatar
Jason_04_138617
Icon for Nimbostratus rankNimbostratus
Feb 26, 2014

Actually yes. I sent F5 some qkviews, both before and after the upgrade. They were able to determine that the issue was being caused by a single HTTP monitor which had been built into a user-created partition. For some reason, this caused a bug. The fix was as follows...

 

After upgrading, I had to move this particular monitor from the user-created partition, to the Common partition. This was accomplished by editing wideip.conf with vi. I simply opened the file in vi, scrolled down to the monitor in question, and changed its partition name.

 

I then ran this command: esrapmtg -l -k

 

At that point, the wideip.conf file loaded up with the modification I had just made in vi, and then all other objects appeared like magic.

 

The F5 engineer I worked with stated this is a known bug where occasionally certain objects created outside of the Common partition can cause a problem during upgrade.

 

Your best bet is probably to open a TAC case with F5 and send them qkviews of before and after the failed upgrade, same as I did, as you may not be able to determine which particular object or objects is causing the hangup without first having F5 review your qkview.