When you deploy Parent Managed Child servers, the Child can serve as the system where GDMA agents report their results. This is very useful in keeping the atomic many-to-one traffic inherent in agent based monitoring local to the network where the Child is deployed. However, in contrast to Child Managed Child configurations, Parent Managed Child servers can't serve as the point of configuration or auto-registration, or auto-setup for GDMA agents. This is because the database for all configurations these features depend upon is on the Parent, not the Child in this case.
To allow you to have the GDMA use the Child as the Target Server and keep the GDMA > Server traffic local, you can proxy the requests for configuration externals, for auto-registration, and for auto-setup and plugin downloads to the Parent. This How To provides you the steps for setting this up. Note GroundWork may make this the default in future configurations.
How To Steps
Go to the Child server command line as the gwos user, and change to the gw8 directory:
Enter the following to back up the configuration file you will be modifying:
Next, type the following to edit the file, which will result in a vi session:
Go to line 230, and you will see the start of a section defining the
/gdmalocations. You will need to remove these definitions down to the Monarch location (leave that in place):
Replace the definitions you removed with the following, changing out the
myparentserver.example.comfor your Parent servers DNS name:
- Save the file, you can use
Restart the revproxy:
At this point, your GDMA agents should auto-register on the Parent normally. Of course, you can adjust this proxy config as needed, however be advised an upgrade to the Child server may require adjusting this change (especially if GroundWork adopts this configuration as default).