APM OAM, access server hostname FQDN trimmed to simple name before use...?
Environment: Big-IP 4200v running LTM 11.5.2 with APM
We have an OAM integrated as a AAA server in APM, and for some reason, even though we use a fully-qualified name for the access server hostname, it seems that the OAM SDK calls are all trying to reach out to the simple version of the name (that is, we have host.domain.com in the configuration, but the OAP calls all are made to host:5575, instead of host.domain.com:5575).
I know this is the case, because I have manual name resolution in place at this point, via hosts file entries - and if I don't have the simple name resolved, OAM calls fail - if I add in resolution of the simple name, it works fine.
This does not happen with other OAM integrations we have, on other F5s, they all use the fqdn.
This isn't really a problem, we can live with the simple name - but it's dang curious. Any thoughts?