ins-40937 following host names are not valid(下划线“_”导致)

ins-40937 following host names are not valid(下划线“_”导致)

 

总结：/etc/hosts配置中 ias最好不使用下划线“_”，不符合RFC 952规则，会报错

 

192.168.1.1     rac1-priv
192.168.1.2     rac2-priv
192.168.8.3    rac1-vip
192.168.8.4    rac2-vip
192.168.8.5   eas-cluster eas-cluster-sca

192.168.8.1   rac1 szmlserv_82.easou.com
192.168.8.2   rac2 szmlserv_73.easou.com

 

看似没有问题的/etc/hosts配置，但是会报错ins-40937 following host names are not valid ，最后在群内朋友讨论发现，其实hosts 配置中 “_”这个下划线导致报错，这个hosts配置中ias这个下滑线”_”不符合RFC 952规则。

 

 

一、MOS有关介绍

This problem is then highlighted by Microsoft's IE browser that will
not allow connections to hosts that do not match this rule.

 

Bug 3396924 : '_' UNDERSCORE CHARACTER ALLOWED DURING INSTALL PROCESS BUT ILLEGAL IN DNS RFC

 

二、官档注释

 

Note:

All host names must conform to the RFC 952 standard, which permits alphanumeric characters. Host names using underscores ("_") are not enabled.

 

来源：http://docs.oracle.com/cd/E11882_01/install.112/e24660/chklist.htm#BHAGAAGH

 

三、附表：VIP,IP,PRIV,SCAN区别

•GNS virtual IP address (GNS installations only): A static IP address configured in the GNS. The GNS virtual IP listener forwards queries to nodes in the subdomain on the cluster managed by GNS.

Within the subdomain, the GNS uses multicast Domain Name Service (mDNS) to enable the cluster to map hostnames and IP addresses dynamically as nodes are added and removed from the cluster, without requiring additional host configuration in the DNS.

To enable GNS, you must have your network administrator provide a set of IP addresses for a subdomain that is assigned to the cluster (for example, grid.example.com), and forward DNS requests for that subdomain to the GNS virtual IP address for the cluster, which GNS will serve.

•Single Client Access Name (SCAN): A domain name that resolves to all the addresses allocated for the SCAN. Oracle recommends that you allocate three addresses to the SCAN. During Oracle Grid Infrastructure installation, listeners are created for each of the SCAN addresses, and Oracle Clusterware controls which server responds to a SCAN address request.

For high availability, you should provide at least three IP addresses in the DNS to use for SCAN mapping. A SCAN domain name must be unique within your corporate network.

•Virtual IP address: A public internet protocol (IP) address for each node, to be used as the Virtual IP address (VIP) for client connections. If a node fails, then Oracle Clusterware fails over the VIP address to an available node.

During installation, if you do not use Grid Naming Service (which provides the VIP automatically), then you provide VIP addresses. The VIP for each node is associated with the same interface name on every node that is part of your cluster. If you have a domain name server (DNS), then your network administrator should register the host names for the VIP with the DNS, so that the DNS is resolvable from any client, as well as the cluster nodes. The VIP should not be in use at the time of the installation, because this is an IP address that Oracle Clusterware manages.

•Public IP address: A public host name address for each node, assigned by GNS, or assigned by the system administrator during initial system configuration for manual configurations. The public IP address name must be resolvable to the hostname. Register both the public IP and the VIP address with the DNS. If you do not have a DNS, then you must make sure that both public IP addresses are in the node /etc/hosts file (for all cluster nodes).

•Private IP address: A private IP address for each node to serve as the private interconnect address, dedicated exclusively to internode cluster communication. GNS configures the address automatically. If you select manual configuration, then you must ensure that the following is true for each private IP address. The private IP address must be:

◦Separate from the public network

◦Accessible on the same network interface on each node

◦Connected to a network switch between the nodes for the private network; crosscable interconnects are not supported

The private interconnect is used for internode communication by both Oracle Clusterware and Oracle RAC. If you use manual configuration, then the private IP address must be available in each node's /etc/hosts file. Oracle recommends that the private network interconnects ar configured on dedicated switches that are not connected to anything other than the nodes in the same cluster.