Pakge name act as the Physical node

[Ala AlWhaibi]

Hi Everyone,

Whenever I try to login to CDE or telnet, I get the package name instead of the physical node.

Also if I try to run "cmviewcl" command I get this error:

# cmviewcl
Error: Permission denied to 127.0.0.1
cmviewcl : Cannot view the cluster configuration.
Either this node is not configured in a cluster, user doesn't have
access to view the cluster configuration, or there is some obstacle
to viewing the configuration. Check the syslog file for more information.
For a list of possible causes, see the Serviceguard manual for cmviewcl.

Anyone Has any idia about it? is it the database to resolve hostname get Corrupted?

Please your Help

[Steven E. Protter]

Shalom,

127.0.0.1 is localhost, internal networking for the host.

It should not be used in SG configurations as far as I know. If it is, try using the IP address or hostname of the system.

Also confirm networking on the system is correct in /etc/rc.config.d/netconf

SEP

[Ala AlWhaibi]

It was working fine but suddenly I am getting this error. it only appear yasterday.

On the other node of cluster, the command is running fine!

When you login to the physical node you got this message "Welcome to PkgName". it was "Welcome to HostName".

[Fred Ruffet]

Are you using two NICs ? It may be that the package IP is down, and if you've configured the node IP as a backup, all is messed up.

A "netstat -rnv" on both node may be a good thing to be posted here (with an explanation of what IP is for the node and for the package).

Regards,

[Ala AlWhaibi]

Here is the nslookup for the localhost:
on the efficted node:

# nslookup 127.0.0.1
Using /etc/hosts on: pkgxx01

looking up FILES
Name: localhost
Address: 127.0.0.1
Aliases: loopback

on the helthy node

# nslookup 127.0.0.1
Name Server: server-dns
Address: 172.22.255.50

Trying DNS
Name: localhost
Address: 127.0.0.1


----
for your request, both node are up and both pakages are up! I can access my application and it is running, but any cluster command on this node is failing.

Here you are.
efficted node:

# netstat -rnv
Routing tables
Dest/Netmask Gateway Flags Refs Interface Pmtu
127.0.0.1/255.255.255.255 127.0.0.1 UH 0 lo0 4136
172.22.255.99/255.255.255.255 172.22.255.99 UH 0 lan0:1 4136
192.168.2.2/255.255.255.255 192.168.2.2 UH 0 lan1 4136
172.22.255.70/255.255.255.255 172.22.255.70 UH 0 lan0 4136
192.168.2.0/255.255.255.0 192.168.2.2 U 2 lan1 1500
172.22.0.0/255.255.0.0 172.22.255.70 U 3 lan0 1500
172.22.0.0/255.255.0.0 172.22.255.99 U 3 lan0:1 1500
127.0.0.0/255.0.0.0 127.0.0.1 U 0 lo0 0
default/0.0.0.0 172.22.0.1 UG 0 lan0 0


helthy node:
# netstat -rnv
Routing tables
Dest/Netmask Gateway Flags Refs Interface Pmtu
127.0.0.1/255.255.255.255 127.0.0.1 UH 0 lo0 4136
172.22.255.98/255.255.255.255 172.22.255.98 UH 0 lan0:1 4136
172.22.255.72/255.255.255.255 172.22.255.72 UH 0 lan0 4136
192.168.2.1/255.255.255.255 192.168.2.1 UH 0 lan1 4136
192.168.2.0/255.255.255.0 192.168.2.1 U 2 lan1 1500
172.22.0.0/255.255.0.0 172.22.255.72 U 3 lan0 1500
172.22.0.0/255.255.0.0 172.22.255.98 U 3 lan0:1 1500
127.0.0.0/255.0.0.0 127.0.0.1 U 0 lo0 0
default/0.0.0.0 172.22.0.1 UG 0 lan0 0



Ala

[Fred Ruffet · Accepted solution]

What I understand for your conf is =>
node with problem :
172.22.255.99 package IP
192.168.2.2 heartbeat IP
172.22.255.70 node IP

healthy node:
172.22.255.98package IP
172.22.255.72 node IP
192.168.2.1 heartbeat IP

There's a difference in the nslookups. One looks for files, other for /etc/hosts. /etc/nsswitch.conf file should not be the same on the two nodes. And probably, DNS and hosts file does not answer the same things.

You could see it by doing nslookup for both nodes and both packages on the two nodes and compare results.

You should choose between DNS and files and make the two nodes look at the same source.

Regards,

[Ala AlWhaibi]

Many Thanks Fred, I fixed both of the node to use DNS, but it the problem still there.
Anyway I had the chance to reboot this node and everythig is fine now.

I'm not sure if this will help, but we run "Nessus" Security scanner and it logs to the server for security checks. I found these error from syslog:

May 13 02:49:58 erppws01 cmcld: Inbound connection from unconfigured address 172.16.10.72

and on cmomd.log:

instance of LogEntryInstTable {
timestamp = "May 13 03:04:25";
source = "294";
category = "ERROR";
path = "omd";
message = "Invalid request format from 172.16.10.72, expected \"request \" at \"xxxxxxxx\"";
};
instance of LogEntryInstTable {
timestamp = "May 13 03:04:25";
source = "295";
category = "ERROR";
path = "omd";
message = "Invalid request format from 172.16.10.72, expected \"request \" at \"%#012345\"";
};


where 172.16.10.72 is ip which run nessus utility.



Also Thanks to you Steven.


Ala