BigIP LTM 10.2.3 -> 11.3.0 upgrade - configuration issues

We've been struggling with the 10.2 to 11.2 upgrade since last September.

 

 

1. We had a .NET issue manifest itself which resulted in us having to implement an enteprise-wide system.net configuration update.

 

2. We also noticed the node name/description switch as well. I'm testing an automated process to re-customize the name field values.

 

3. We use multiple partitions/route domains per LTM and use a custom icmp monitor configuration as opposed to using a default one. The issue is that the custom monitor as defined in 10.2 does not include the partition in the path name (of course), and it was not automatically updated during the upgrade. This resulted in all nodes being marked as down because the path to the icmp monitor could not be found. We have been unable to modify the node config afterwards...not in the GUI (the node properties would not even display), nor via CLI, nor by manually editing the bigip.conf file directly. Everything we tried complained about not finding the path to the monitor during some sort of validation process. This complete failure occurred in our passive production data center, so we were able to roll back without affecting anything major. However, our QA environment has started to have this happen when someone disables a pool member or tries to make any sort of change to a node property...the node becomes completely unusable nor updateable. Why it didn't have a complete failure of all nodes like it did in our passive production environment has yet to be understood. We've been working with support since last week about this.

 

 

I spoke with F5 support this morning and their product development has reproduced this monitor issue in 11.2 and 11.3. I hope to have their workaround in hand later today. I would assume a patch would also be forthcoming.