About the Nozeroconf=yes parameter in Linux/etc/sysconfig/network

About the Nozeroconf=yes parameter in Linux/etc/sysconfig/network

Today from CSSD fails to Join the Cluster after Private Network recovered if Avahi Daemon are up and Running (Doc ID 1501093.1) article To this parameter,
In this article, there is the following discussion:

Solution

The solution is to shutdown and disable 3rd party zeroconf mDNS process, in this case, avahi-daemon
To shut it down, as root:

# /etc/init.d/avahi-daemon stop

To disable it, as root:

# /sbin/chkconfig  avahi-daemon off

On Oracle Linux/Redhat Linux, "NOZEROCONF=yes" must be included in /etc/sysconfig/network

In addition, the following article describes the parameter:
How to Prevent Bogus Entry 169.254.0.0/255.255.0.0 automatically Added to Routing Table (Doc ID 1161144.1)
In this article, there is the following description:

The route entry "169.254.0.0/16" is the IPV4 "link local" block.It is allocated for communication between hosts on a single link. Hosts obtain these addresses by auto-configuration, such as when a DHCP server may not be found.

This routing entry is added automatically because RHEL/OEL enable Zero configuration networking(zeroconf) by default.

To disable the zeroconf route during system boot or network service restart,
 edit the /etc/sysconfig/network file and add the following NOZEROCONF value to the end of the file:


NETWORKING=YES
HOSTNAME=localhost.localdomain
NOZEROCONF=yes


 More information about zeroconf could be found at: http://en.wikipedia.org/wiki/Zero_configuration_networking

So, if Oracle Linux/redhat Linux is used as Oracle DB server, is it mandatory to add nozeroconf=yes to/etc/sysconfig/network?
The feeling is to add Nozeroconf=yes to the/etc/sysconfig/network!

However, in RAC and Oracle clusterware best Practices and Beginner's Guide (Linux) (Doc ID 1525820.1), there is no nozeroconf description.

About the Nozeroconf=yes parameter in Linux/etc/sysconfig/network