trying to configure I/O fencing

[MIG31]

I need help with this trying to configure I/O fencing but I get this error

Would you like to configure I/O fencing on the cluster? [y,n,q] y

    Checking communication on system1 .............................................................................................................. Done
    Checking release compatibility on system1 ...................................................................................................... Done
    Checking VCS installation on system1 ............................................................................................ Version 6.0.100.000
    Checking communication on system2 ............................................................................................................ Failed
CPI ERROR V-9-20-1262 Cannot resolve hostname system2

[Marianne]

Cannot resolve hostname system2

Do you have entries in /etc/hosts for one another on both cluster nodes?

Have you confirmed that rsh or ssh is configured between cluster nodes?

Please download VCS installation guide for your version - it contains all requirements and initial setup steps, including how to setup ssh. It also includes step-by-step instructions on how to configure I/O fencing.

See http://sort.symantec.com/documentation

[rsharma1]

doubklecheck if can you ping system2 from system1. Can you ping systems2's fully qualified domain name from system1? Start the installer only after it pings.

[starflyfly]

Hi, MG

1. you should make sure, ping system2 can work in your host.

2. if error still there, change to 6.0sp1 version.

Regards

[starflyfly]

You may met that error in 6.0pr1 old release. Recent build version may also fix .

[MIG31]

Hey Starfly this is the output on my system2 when i ran the #cat /etc/resolv.conf i have two DNS

> ^C[root@system2 ~]# cat /etc/resolv.conf
# Generated by NetworkManager
domain localdomain
search localdomain
nameserver 192.168.164.2
nameserver 192.168.223.1
[root@system2 ~]# ping 192.168.164.2
PING 192.168.164.2 (192.168.164.2) 56(84) bytes of data.
64 bytes from 192.168.164.2: icmp_seq=1 ttl=128 time=0.571 ms
64 bytes from 192.168.164.2: icmp_seq=2 ttl=128 time=0.157 ms
64 bytes from 192.168.164.2: icmp_seq=3 ttl=128 time=0.159 ms
64 bytes from 192.168.164.2: icmp_seq=4 ttl=128 time=0.214 ms
64 bytes from 192.168.164.2: icmp_seq=5 ttl=128 time=0.161 ms
64 bytes from 192.168.164.2: icmp_seq=6 ttl=128 time=0.159 ms
64 bytes from 192.168.164.2: icmp_seq=7 ttl=128 time=0.184 ms
64 bytes from 192.168.164.2: icmp_seq=8 ttl=128 time=0.255 ms
64 bytes from 192.168.164.2: icmp_seq=9 ttl=128 time=0.210 ms
64 bytes from 192.168.164.2: icmp_seq=10 ttl=128 time=0.257 ms
^C
--- 192.168.164.2 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9866ms
rtt min/avg/max/mdev = 0.157/0.232/0.571/0.119 ms

and system1 output [kidiavai@system1 ~]$ cat /etc/resolv.conf
# Generated by NetworkManager
domain localdomain
search localdomain
nameserver 192.168.164.2
[kidiavai@system1 ~]$ ping 192.168.223.1
PING 192.168.223.1 (192.168.223.1) 56(84) bytes of data.
64 bytes from 192.168.223.1: icmp_seq=1 ttl=128 time=1.19 ms
64 bytes from 192.168.223.1: icmp_seq=2 ttl=128 time=0.831 ms
64 bytes from 192.168.223.1: icmp_seq=3 ttl=128 time=0.823 ms
64 bytes from 192.168.223.1: icmp_seq=4 ttl=128 time=0.755 ms
64 bytes from 192.168.223.1: icmp_seq=5 ttl=128 time=0.946 ms
64 bytes from 192.168.223.1: icmp_seq=6 ttl=128 time=0.831 ms
64 bytes from 192.168.223.1: icmp_seq=7 ttl=128 time=0.557 ms
64 bytes from 192.168.223.1: icmp_seq=8 ttl=128 time=0.728 ms
64 bytes from 192.168.223.1: icmp_seq=9 ttl=128 time=0.546 ms
64 bytes from 192.168.223.1: icmp_seq=10 ttl=128 time=0.832 ms
64 bytes from 192.168.223.1: icmp_seq=11 ttl=128 time=1.22 ms
64 bytes from 192.168.223.1: icmp_seq=12 ttl=128 time=0.819 ms
64 bytes from 192.168.223.1: icmp_seq=13 ttl=128 time=0.851 ms
64 bytes from 192.168.223.1: icmp_seq=14 ttl=128 time=0.707 ms
64 bytes from 192.168.223.1: icmp_seq=15 ttl=128 time=1.12 ms
64 bytes from 192.168.223.1: icmp_seq=16 ttl=128 time=0.825 ms
64 bytes from 192.168.223.1: icmp_seq=17 ttl=128 time=0.886 ms
64 bytes from 192.168.223.1: icmp_seq=18 ttl=128 time=0.837 ms
64 bytes from 192.168.223.1: icmp_seq=19 ttl=128 time=0.833 ms
64 bytes from 192.168.223.1: icmp_seq=20 ttl=128 time=0.839 ms
64 bytes from 192.168.223.1: icmp_seq=21 ttl=128 time=0.859 ms
64 bytes from 192.168.223.1: icmp_seq=22 ttl=128 time=0.795 ms
64 bytes from 192.168.223.1: icmp_seq=23 ttl=128 time=0.899 ms
64 bytes from 192.168.223.1: icmp_seq=24 ttl=128 time=0.817 ms
64 bytes from 192.168.223.1: icmp_seq=25 ttl=128 time=0.824 ms
64 bytes from 192.168.223.1: icmp_seq=26 ttl=128 time=0.720 ms
64 bytes from 192.168.223.1: icmp_seq=27 ttl=128 time=0.961 ms
64 bytes from 192.168.223.1: icmp_seq=28 ttl=128 time=0.828 ms
^X64 bytes from 192.168.223.1: icmp_seq=29 ttl=128 time=1.06 ms
64 bytes from 192.168.223.1: icmp_seq=30 ttl=128 time=0.755 ms
64 bytes from 192.168.223.1: icmp_seq=31 ttl=128 time=0.819 ms
64 bytes from 192.168.223.1: icmp_seq=32 ttl=128 time=0.831 ms
^C
--- 192.168.223.1 ping statistics ---
32 packets transmitted, 32 received, 0% packet loss, time 31556ms
rtt min/avg/max/mdev = 0.546/0.848/1.224/0.149 ms

they are pinging each other but how come on system2 we have two name servers

[Marianne]

Don't use IP addresses with ping tests - use hostnames.

Ensure OS can resolve hostnames - easiest is to add /etc/hosts entries.

[MIG31]

Marianne thats what i get

127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
[root@system1 kidiavai]# vi /etc/hosts
[root@system1 kidiavai]# cat /etc/hosts
127.0.0.1   localhost system1.localdomain system1
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
[root@system1 kidiavai]# hostname -a
system1.localdomain system1
[root@system1 kidiavai]# ssh system2
ssh: Could not resolve hostname system2: Name or service not known
[root@system1 kidiavai]# ping system2
ping: unknown host system2
[root@system1 kidiavai]# vi /etc/hosts
[root@system1 kidiavai]# hostname -a
system1.domain.local system1
[root@system1 kidiavai]# ssh system2
ssh: Could not resolve hostname system2: Name or service not known

[rsharma1]

Looks like the names system1 and system2 are not registered in your name server(s)..

As Marianne suggested in the earlier post, [Do you have entries in /etc/hosts for one another on both cluster nodes?], the /etc/hosts on both nodes should look like:

<<

127.0.0.1   localhost
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

<ip_address_of_system1>    system1.localdomain system1

<ip_address_of_system2>    system2.localdomain system2

>>

After making the above changes in /etc/hosts, also specify the following line in /etc/nsswitch.conf:

<<

hosts: files,dns

>>

So that the name resolution process will begin with checking /etc/hosts file, and if the name cannot be resolved, only then the name resolution will happen with the DNS server

After making these changes, try "nslookup system2" from system1. Then try the ping and ssh ..it should work.

[Marianne]

I don't know how else to ask you to add entries to /etc/hosts.

If you are not the Linux sysadmin, please ask for assistance.

Use 'vi' to add ip address and hostname for both nodes to /etc/hosts on system1 and system2 as per rsharma1's example above.

[starflyfly · Accepted solution]

Hi, Mg

1. manual add following entry in  system1's /etc/hosts:

192.168.223.1 system2

 Or  2. run on system1:

#cp /etc/hosts  /etc/hosts.bak

#echo  "192.168.223.1 system2" >>/etc/hosts

3. test:

ping system2