16.5.5. Configure Server Advertisement Properties for Your mod_cluster-enabled HTTPD
For instructions on configuring your HTTPD to interact with the mod_cluster load balancer, refer to Section 16.5.3, “Install the mod_cluster Module Into Apache HTTPD or JBoss Enterprise Web Server HTTPD (ZIP)”. One aspect of the configuration which needs more explanation is server advertisement.
httpd.conf associated with your Apache HTTPD instance. This is often /etc/httpd/conf/httpd.conf in Red Hat Enterprise Linux, or may be in the etc/ directory of your stand-alone Apache HTTPD instance.
Procedure 16.6. Edit the httpd.conf file and implement the changes
Disable the
AdvertiseFrequencyparameter, if it exists.If you have a line like the following in your<VirtualHost>statement, comment it out by putting a#(hash) character before the first character. The value may be different from5.AdvertiseFrequency 5
Add the directive to disable server advertisement.
Add the following directive inside the<VirtualHost>statement, to disable server advertisement.ServerAdvertise Off
Enable the ability to receive MCPM messages.
Add the following directive to allow the HTTPD server to receive MCPM messages from the worker nodes.EnableMCPMReceive On
Restart the HTTPD server.
Restart the HTTPD server by issuing one of the following, depending on whether you use Red Hat Enterprise Linux or Microsoft Windows Server.Red Hat Enterprise Linux
[root@host ]# service httpd restart
Microsoft Windows Server
C:\> net service http C:\> net service httpd start
The HTTPD no longer advertises the IP address and port of your mod_cluster proxy. To reiterate, you need to configure your worker nodes to use a static address and port to communicate with the proxy. Refer to Section 16.5.6, “Configure a mod_cluster Worker Node” for more details.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.