Forum Discussion
upgrade from ltm 10.2.3 to 11.2.0 fails to load config due to unicast non existant ips
Is there a specific reason I multicase ip range would be implemented on f5 versions 10.x? If so , should the ip addresses referenced in them actually be assigned as self ips, or would they only become active while the system attempted to failover?
I assume that if these were actually needed to be up interfaces and the network failover configuration is merly the rule on how to act with the ips in the case of an evet, then something about version 11.x does not like this process.
However I have noticed that version 11.x does some actual validation of ip addresses, netmasks , etc and if this is the case of it failing becuase again of validation I would assume then that someone entered in a faulty configuration and never finished its design or setup before moving on.
Any advice/clarification on how version 11.x would act for this would be greatly apprieciated.
- bman_12685Nimbostratusdisregard this post, since this system was inherited i assumed the config was incomplete, and never utilized as such I removed it and got past that issue.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com