關於linux /etc/sysconfig/network中的NOZEROCONF=yes參數
今天從CSSD Fails to Join the Cluster After Private Network Recovered if avahi Daemon is up and Running (Doc ID 1501093.1)文章中看到了這個參數,
在該文章中,有如下的論述:
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
另外,如下的文章介紹了該參數:
How To Prevent Bogus Entry 169.254.0.0/255.255.0.0 Automatically Added To Routing Table (Doc ID 1161144.1)
在該文章中,有如下的描述:
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
這麼說,若是Oracle Linux/Redhat Linux作為Oracle DB Server使用,是不是要強制:把NOZEROCONF=yes添加到/etc/sysconfig/network中?
感覺是要把NOZEROCONF=yes添加到/etc/sysconfig/network中!
但是在RAC 和 Oracle Clusterware 最佳實踐和初學者指南 (Linux) (Doc ID 1525820.1)中,並沒有NOZEROCONF的描述。