About the NOZEROCONF = yes parameter in linux/etc/sysconfig/network

About the NOZEROCONF = yes parameter in linux/etc/sysconfig/network

About the NOZEROCONF = yes parameter in linux/etc/sysconfig/network

Today, we saw this parameter in the CSSD Fails to Join the Cluster After Private Network Recovered if avahi Daemon is up and Running (Doc ID 1501093.1) article,
In this article, we will discuss the following:

SolutionThe solution is to shutdown and disable 3rd party zeroconf mDNS process, in this case, avahi-daemonTo shut it down, as root:# /etc/init.d/avahi-daemon stopTo disable it, as root:# /sbin/chkconfig  avahi-daemon offOn Oracle Linux/Redhat Linux, "NOZEROCONF=yes" must be included in /etc/sysconfig/network

In addition, the following article introduces this 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, the following descriptions are provided:

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=YESHOSTNAME=localhost.localdomainNOZEROCONF=yes More information about zeroconf could be found at: http://en.wikipedia.org/wiki/Zero_configuration_networking

In this case, if Oracle Linux/Redhat Linux is used as an Oracle DB Server, Is it mandatory to add NOZEROCONF = yes to/etc/sysconfig/network?
It seems that you want to add NOZEROCONF = yes to/etc/sysconfig/network!

But there is no description of NOZEROCONF in RAC and Oracle Clusterware best practices and the beginner's Guide (Linux) (Doc ID 1525820.1.