Forum Discussion
Stefan_Klotz
Jun 16, 2015Cumulonimbus
Here is the latest update from the case escalation at F5.
It appears that the v10.2.4 behaviour is the APM operating as designed.
A deeper investigation suggests the way we handled Route Domains in v10.x can result in the communication
problems if the alternate Route Domains have no Parent ID. In v11.x we modified how inter-Route-Domain
communication worked within TMM, with the result that the there is no issue if the alternate Route Domain
has no Parent ID.
So the solution to this issue is to assign a Parent ID to the Route Domains in v10.2.4.
Ciao Stefan 🙂