[PCA] Name Resolution Does Not Work For All Compute Node ILOMs

Asset ID:	1-72-2242854.1
Update Date:	2017-07-17
Keywords:

Solution Type Problem Resolution Sure

Solution 2242854.1 : [PCA] Name Resolution Does Not Work For All Compute Node ILOMs

Applies to:

Private Cloud Appliance - Version 2.0.5 and later
Private Cloud Appliance X5-2 Hardware - Version All Versions to All Versions [Release All Releases]
Linux x86-64

Symptoms

When attempting to ssh or ping a compute node or ILOM from the master management node, name resolution is working for some nodes or iloms, but not others.

Example:

ilom-ovcacn27r1 can resolve.

[root@ovcamn05r1 ~]# ping ilom-ovcacn27r1
PING ilom-ovcacn27r1 (192.168.4.114) 56(84) bytes of data.
64 bytes from ilom-ovcacn27r1 (192.168.4.114): icmp_seq=1 ttl=64 time=1.67 ms
64 bytes from ilom-ovcacn27r1 (192.168.4.114): icmp_seq=2 ttl=64 time=1.67 ms

However ilom-ovcacn07r1 cannot resolve.

[root@ovcamn05r1 ~]# ping ilom-ovcacn07r1
ping: unknown host ilom-ovcacn07r1

Changes

Cause

Issue caused by dns_hosts not being populated with all hostnames.

Below you can see that ilom-ovcacn07r1is missing.

[root@ovcamn05r1 ~]# grep ilom-ovcacn /nfs/shared_storage/conf/dns_hosts
192.168.4.106 ilom-ovcacn08r1 # ilom 1:8
192.168.4.107 ilom-ovcacn09r1 # ilom 1:9
192.168.4.108 ilom-ovcacn10r1 # ilom 1:10
192.168.4.109 ilom-ovcacn11r1 # ilom 1:11
192.168.4.110 ilom-ovcacn12r1 # ilom 1:12
192.168.4.111 ilom-ovcacn13r1 # ilom 1:13
192.168.4.112 ilom-ovcacn14r1 # ilom 1:14
192.168.4.113 ilom-ovcacn26r1 # ilom 1:26
192.168.4.114 ilom-ovcacn27r1 # ilom 1:27

Solution

Go to the master management node
Backup /nfs/shared_storage/conf/dns_hosts
Edit /nfs/shared_storage/conf/dns_hosts
Add a line for the node with the IP.

Example

192.168.4.1XX ilom-ovcacn07r1 # ilom 1:7
Restart dns.

# service dnsmasq restart

Attachments

This solution has no attachment