Well, I finally got a pretty much vanilla HACMP install finished, using HACMP 5.3.
As tests, from the nim installation server I repeaded the follwoing command:
root@nim [/]:for i in 1 2 3 4
> do
> snmpinfo -m get -c public -h ha12$i -v 1.3.6.1.4.1.2.4.12.7.1.2.3
> done
ibm.4.12.7.1.2.3 = ibmAIX (1.3.6.1.4.1.2.6.191)
ibm.4.12.7.1.2.3 = ibmAIX (1.3.6.1.4.1.2.6.191)
ibm.4.12.7.1.2.3 = ibmAIX (1.3.6.1.4.1.2.6.191)
ibm.4.12.7.1.2.3 = ibmAIX (1.3.6.1.4.1.2.6.191)
This worked each time - before installing the cluster.* software; after installing the software; after running the two node configuration wizard (to be very standard); after starting one node.
# ./clfindres
-----------------------------------------------------------------------------
Group Name State Node
-----------------------------------------------------------------------------
AppB_group ONLINE ha_121
OFFLINE ha_122
The file snmpd.conf file has been updated, by the installation of the software. So I removed the software from one node (124)
root@nim[/test]:ls -l
total 96
-rw-r----- 1 root system 10164 Feb 2 17:02 snmpd.conf.ha121
-rw-r----- 1 root system 10164 Feb 2 17:02 snmpd.conf.ha122
-rw-r----- 1 root system 10164 Feb 2 17:02 snmpd.conf.ha123
-rw-r----- 1 root system 10080 Feb 2 17:02 snmpd.conf.ha124
root@nim[//test]:diff *ha121 *ha124
207d206
< smux 1.3.6.1.4.1.2.3.1.2.1.5 clsmuxpd_password # HACMP/ES for AIX clsmuxpd
root@nim[/test]:
My conclusion is that it is not the HACMP software that is making a change, but an administrator is making changes to the
community line in snmpd.conf.
The default entry when AIX is installed is:
root@nim[/test]:grep community *121 *124
snmpd.conf.ha121:community public
snmpd.conf.ha121:#community private 127.0.0.1 255.255.255.255 readWrite
snmpd.conf.ha121:#community system 127.0.0.1 255.255.255.255 readWrite 1.17.2
snmpd.conf.ha124:community public
snmpd.conf.ha124:#community private 127.0.0.1 255.255.255.255 readWrite
snmpd.conf.ha124:#community system 127.0.0.1 255.255.255.255 readWrite 1.17.2
Also in /etc/snmpd.conf is some documentation about the interpretation of the community statement.
Before adding it I will just say that the default statement allows the community
public to read all variables from any IP address. To make it more restrictive, or even "secret" you change the community name and/or limit the acceptable ranges of IP addresses making queries (with IP_ADDRESS NETMASK pairs).
Now the documentation included inthe default file:
# 2. Set the community names and access privileges for hosts that can make
# requests of this snmpd agent. Define these restrictions as follows:
#
# community <name> <address> <netmask> <permissions> <view name>
#
# where <name> is the community name, <address> is either a hostname or
# an IP address in dotted notation, and <permissions> is one of: none,
# readOnly, writeOnly, readWrite. The default permission is readOnly.
# <netmask> specifies the network mask. The default address and netmask
# are 0.0.0.0. If an address other than 0.0.0.0 is specified, the default
# netmask is 255.255.255.255. If a permission is specified, both the
# address and netmask must also be specified. <view name> defines a
# portion of the MIB tree to which this community name allows access.
# <view name> must be defined as a unique object identifier in dotted
# numeric notation. <view name> is further defined in the view
# configuration entry. If <view name> is not specified, the view for
# this community defaults to the entire MIB tree. Fields to the right
# of <name> are optional, with the limitation that no fields to the
# left of a specified field are omitted.
#
So, please post a grep of
community from your /etc/snmpd.conf files - if permited
