Skip to Content

ASCS installed on network alias - how to manage diagnostic agent?

Aug 08, 2017 at 08:57 AM


avatar image

we have installed an instance on a server and the customer requested that the ASCS is installed with a virtual hostname (simple network hostname alias - without dedicated IP; all is done on DNS level). I am not sure why this was requested, as far as I know there is no HA solution.
My question is how to manage the solman plug as now?

In LMDB, landscape browser I see that the PAS is installed under the server hostname (FQDN OK), and ASCS under the virtual name (alias) but no diagnostic agent assigned/found.

LMDB/hosts shows 3 hosts: DB, PAS, ASCS (ASCS with logical name SAP-<sid>-ASCS)

In Managed system config/assing Diag. agent I see:

Could you please advice how to proceed so that the ASCS has a DA assigned?

I read a few notes and guides, but I am still not sure what applies to this case.

As per - ->

In case Managed Systems run with hostnames that are "simple" network hostname aliases (meaning not logical hostnames with dedicated IP addresses, like described in the above Terminology), the presently documented Agents On-the-fly feature will not work.

Should I follow option - Low amount of Logical hosts running on Physical or Virtual Host A (from the same URL)-> and install a separate DA using the logical hostname as for the ASCS? (if so, do I need to use differeny SID for DA or different instance number is enough?)

When checking - saphostctrl -function GetComputerSystem - the result does not contain the logical hostname (I guess because it is set on DNS).


g6flj.png (10.0 kB)
eyh0z.png (7.8 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

0 Answers