Forum Discussion

daboochmeister's avatar
daboochmeister
Icon for Cirrus rankCirrus
Jul 29, 2015

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 host...
BIG-IP Access Policy Manager (APM)
oam
oracle
security
daboochmeister's avatar
daboochmeister
Icon for Cirrus rankCirrus

Actually - I think we figured it out. The APM OAM module just uses the access server hostname that you configure in to establish an initial connection with the OAM servers - during that initial connection, it retrieves a more complete configuration from OAM (which it saves in file ObClientAccess.xml, buried in the OAM file system tree under /config/aaa). I noticed in that file that the plain names are being returned from the OAM server.

 

We still haven't found where in the OAM configuration it's occurring, but it's definitely something on the OAM side.

 

Can a moderator pls mark this response as the answer to this question? I don't seem to be able to mark my own responses as answers.

 

daboochmeister's avatar
daboochmeister
Icon for Cirrus rankCirrus
Jul 31, 2015
Thanks, Nut Pornsopon - the hosts file is temporary, till we get DNS updated (a different group within our organization manages DNS, and we're going through the process of coordinating an alias). I think you're understanding the overall issue correctly - we use FQDN in our APM AAA server configuration (for the "access server hostname", specifically), but after the initial use of that FQDN to reach the primary OAM server, the configuration received back from OAM has plain names in it, and those plain names are used from that point on. So we're coordinating with the OAM group to get their configuration corrected to use FQDN.