ITEM: FX5810L
Hacmp/ attempting to sync cluster getting a netmask error
Env: Model H50/J30, AIX 4.2.1
Problem: Getting error when Sync Cluster Topology.
Action Taken: Sync Cluster Topology, get error:
Node nodename1 does not have a loopback entry in /etc/host
Node nodename2 does not have a loopback entry in /etc/host
then get:
Netmask on en0 on nodename1 does not match the netmask
on en0 on nodename2.
Netmask on en1 on nodename1 does not match the netmask
on en1 on nodename2.
netmask is 255.255.255.0 everywhere
I checked xmenu and find 2ea items with similar errors:
FL2439 and FG5338
These pointed to a problem with HACMP 4.2.2 that was
resolved with a software update.
I will send the latest HACMP updates to him express overnite
He will install them and see if that resolves his problem.
Actino Taken: Check /etc/hosts
primary 192.9.200.3 AFW2 afw2
192.9.200.5 TEST test
192.9.200.6 TESTBOOT testboot
10.1.1.2 TESTSTDBY teststdby
192.9.200.4 AFW2BOOT afw2boot
10.1.1.1 AFW2STDBY afw2stdby
secndry 192.9.200.3 AFW2 afw2
192.9.200.4 AFW2BOOT afw2boot
10.1.1.1 AFW2STDBY afw2stdby
192.9.200.5 TEST test
192.9.200.6 TESTBOOT testboot
10.1.1.2 TESTSTDBY teststdby
No errors evident. Check HA fileset levels:
cluster.base.server.rte - 4.2.2.2 & 4.2.2.1 ????
Fixes not correctly sent/applied.
Will order the following:
IX75705 IX75702 IX75099 IX74856 IX71161 IX74750
lppchk -v --> nothing
ifconfig en\# on all netmask=0xffffff00
/usr/sbin/cluster/utilities/cldare -vrt -> O.K.
Retry syncing through smit again.
boot adapter on node TEST on network 0S not on proper subnet
On node TEST:
smitty tcpip - further configuration - network
interfaces - network interface selection - change/show
characteristics of a network interface
Is subnet correct? NO Change the value and hit enter.
Verify all othr interfaces with the same procedure.
All others seem O.K.
Resyncronize. -----> O.K.
*ACTION PLAN: CWCA
Support Line: Hacmp/ attempting to sync cluster getting a netmask error ITEM: FX5810L
Dated: June 1998 Category: N/A
This HTML file was generated 99/06/24~13:30:13
Comments or suggestions?
Contact us