I'd like to know about System Monitor/6000 and its installation.
The manual (System Monitor/6000 User's Guide,SC31-7042-00) says,
the installation process of the sysmond daemon on a remote node does
the following on that node:
- Comments out all trap destination lines
- Adds a trap destination loopback
...
- Adds configuration entries in the
/usr/adm/sm6000/config/install.config
for those trap destinations. ( Seen in the page 25)
But when I tried to install System Monitor/6000 R1.2 to remote nodes,
I couldn't see such results. The original trap destinations in
/etc/snmpd.conf were not commented out even after the installation.
Q1. Is this result due to the specification change from R1 to R2?
Or is it due to defect?
Q2. If the Q1 is defect, and installing sysmond must modify snmpd.conf,
how are the SNMP-traps designed to be sent to the managers?
Is the scenario shown bellow correct?
In other words, does sysmond refers only to its "Destination Table",
and doesn't refer to "/etc/snmpd.conf"... right?
RISC/6000
Other Agent +--------------------------------------------+
+-----+ | +-----+ |
|snmpd|--------|--+ +-----|snmpd| |
+-----+ IP | | | +-----+ |
network | | | (Snmpd refers to /etc/snmpd.conf
| v v and finds the loopback as its
destination.
|+- P162 -+ Traps are sent to the 162nd port of
|| | the local host. |
|| sysmond| |
|+-|------+ |
+--|-----------------------------------------+
| Sysmond refers to "/usr/adm/sm6000/config/install
v .config", and forwarding traps to the managers
defined in the destination table.
(It doesn't refer to /etc/snmpd.conf, for not to
cause the traps-sending/receiveing loop in the
local node...)
ANSWER
I will check with development about your questions; but, a few comments:
- If AIX NetView/6000 is on the remote node (I doubt this is your case
but, I mention it anyway) I believe the trap field is not messed
with. It IS possible that the latest sysmon installation has
decided NOT to mess with the trap field automatically; the developers
will let us know (I have not tested it).
- I am not sure about your diagram (I am working from home, so this
terminal is not easy to use from a message/printing point of view)
but, if I remember correctly you specify the fact you want sysmond
to register for the traps (via loopback and 162, etc.) at startup
of sysmond. If another manager (such as AIX NetView/6000) has
already registered for traps on the machine sysmond is started on
sysmond will not see the traps.
We re-tried your test and found exactly the same symptoms -
no change to snmpd.conf and no additions to the trap destination table.
Your description of how it SHOULD work is right - traps generated
on the system pass through loopback into sysmond which then forwards
them to the destinations in the trap destination table based on
filtering rules. A couple of points:
1. The trap destination table entries need to be Enabled - this is
obvious, but the default is Disabled, so an update has to be done
2. As mentioned earlier, if NV/6000 is also on the system you
will need to disable trap reception, since they cannot both listen
to port 162
I have told development that the AIX Systems Monitor/6000
documentation in this area needs to be changed.
I fully appreciate your kind responces.
Also I'll wait for the feedbacks from the developper.
Thanks and regards.
ANSWER
The SM/6000 developer came back this morning, with the comment that
the remote install SHOULD work as documented and the fields are
intended to be commented out as mentioned -- assuming that NV/6000 is
NOT installed on the remote machine.
Please confirm that NV/6000 is not on the remote machine and, if that
is true, open a defect if it is a critical matter -- in any case, we
will do additional testing here (unfortunately, all of our machines have
NV/6000 on them or have had it previously and I don't know if that will
confuse the issue.... and feedback your experience to the developers.
In the meantime, open a RETAIN item if there is a customer involved.
I fully appreciate your responce, and I'd like to confirm it.
I take what you say as follows.
(1) If remote machine doesn't have NetView/6000, the SM/6000
installation should not cause the comenting-out in "snmpd.conf".
(2) If remote machine has NetView/6000, the SM/6000 installation
should cause the commenting-out in "snmpd.conf".
Are they both correct?
Thanks and regards.
P.S. As you said, in my test, remote machine didn't have NetView/6000.
Please do me a favor with the last confirmation.
Thanks and regards.
ANSWER
Thanks for confirming that no AIX NetView/6000 is involved.
The developers reported that the remote install should work as in the
documentation. I still have not had a chance to test, myself; I will
try to test today and get with the developers -- but, in the meantime,
it is supposed to work as in the documentation; so, if a customer is
involved please open a Retain item.
I will get back to you as soon as I test.... hopefully, today.
Sugitani-san,
I re-read your today's confirmation note.
In my opinion you are OPPOSITE of what should happen:
- If NV/6000 is installed on the remote machine, I assume that
SM/6000 will NOT comment anything out.
- If NV/6000 is NOT installed on the remote machine, I assume that
SM/6000 will comment something out.
But, perhaps, it will turn out that the clue will be if NV/6000 is on
the LOCAL machine, as well.....
I will let you know what my tests show -- as soon as I get a chance to
test -- or, if I hear from the developer.
Thanks for sticking with this; it sure sounds confusing¢
I have, finally, tested as per your note.
And, as I expected (after your note and previous testing), even
the latest version of SM/6000 ( I have a version of a couple week's old)
still did not comment out the trap entries.
I have passed the following onto development. If this is a critical
matter, all I can suggest is a PMR (program defect) entry.
Thanks for the feedback -- sorry, that I cannot offer up anything other
than a change to documentation; it does not work as it says in the
documentation.
To development:
I finally had a chance to find a machine which was "virgin" (did not
have AIX NetView/6000 on it -- ever -- as far as I know, etc.
The remote install did not comment out all trap destination files
(as was pointed out in the their QandA).
I will close the query and tell them, as far as I can see, they
are correct; the documentation does not reflect what happens.
=========================================================================
Smitty, From the remote machine:
.......................................................................
Communications Applications and Services
Move cursor to desired item and press Enter.
TCP/IP
NFS
SNA Services
NetView Service Point
AIX 3270 Host Connection Program/6000 (HCON)
X.400 Management
XTI
OSI Networking
F1=Help F2=Refresh F3=Cancel F8=Image
F9=Shell F10=Exit Enter=Do
-----------------------------
Previous, is what comm progs are installed there. I am quite sure
AIX NetView/6000 has never been there and I am very sure SM/6000 has
never been there.
-----------------------------
The following is the /etc/snmpd.conf on the remote,
before remote install of sm/6000
###############################################################################
logging file=/usr/tmp/snmpd.log enabled
logging size=0 level=0
community public
community private 127.0.0.1 255.255.255.255 readWrite
community system 127.0.0.1 255.255.255.255 readWrite 1.17.2
community philippe 9.67.38.0 255.255.255.0 readOnly
community philippe 9.67.32.0 255.255.255.0 readOnly
view 1.17.2 system enterprises view
trap public 127.0.0.1 1.2.3 fe # loopback
trap philippe 9.67.32.1 1.3.6 fe # phileth
#snmpd maxpacket=1024 querytimeout=120 smuxtimeout=60
smux 1.3.6.1.4.1.2.3.1.2.1.2 gated_password # gated
-----------------------------------------------------------------------
On the remote, after the install of sm/6000, the following is in
/etc/rc.tcpip.
......................
# Start up AIX Systems Monitor/6000 subagent
start /usr/etc/sm6000 ""
------------------------------------
The following is the /etc/snmpd.conf on the remote,
after remote install of sm/6000
There are some changes to /etc/snmpd.conf -- but, the trap fields are
not commented out.
###############################################################################
logging file=/usr/tmp/snmpd.log enabled
logging size=0 level=0
community public
community private 127.0.0.1 255.255.255.255 readWrite
community system 127.0.0.1 255.255.255.255 readWrite 1.17.2
community philippe 9.67.38.0 255.255.255.0 readOnly
community philippe 9.67.32.0 255.255.255.0 readOnly
view 1.17.2 system enterprises view
trap public 127.0.0.1 1.2.3 fe # loopback
trap philippe 9.67.32.1 1.3.6 fe # phileth
#snmpd maxpacket=1024 querytimeout=120 smuxtimeout=60
smux 1.3.6.1.4.1.2.3.1.2.1.2 gated_password # gated
smux 1.3.6.1.4.1.2.6.12 sm6000 # AIX Systems Monitor/6000: sys
ond
snmpd maxpacket=16000 smuxtimeout=60 # AIX Systems Monitor/6000
-----------------------------------------------------------
Development just came back with a message.
From development:
The script looks for the directories /usr/etc/nm or /usr/OV on the
target machine and if they exist then it does NOT comment out the trap
lines. I will fix this in the next release so it uses the software
installed inventory to check to see if the manager is installed.
Check to see if you have the directories on the machine you installed
I checked -- the machine did not have those lib's. I will
let the developer know and get back to you if
there is information of interest. For now, thanks to your question¢ --
I assume they will fix the problem before the next release.
Thanks.
........................................................................
ITSO Center Raleigh OLSS Feedback
We are trying to improve the quality of the OLSS/QUAT Q&A service that
you have just used. Please use the following scale to rate the answer:
1=EXCELLENT 2=GOOD 3=AVERAGE 4=POOR 5=UNACCEPTABLE
Please send your reply to WTSCPOK(ITSCRAL). Feel free to add any
free-form text to the survey questions.
Q1: Are you satisfied with the speed of the response to your question?
Q2: Was the answer clear and complete?
Q3: If you responded with a rating of 3, 4, or 5 to either Q1 or Q2
please provide some details so we can address any issues.
S e a r c h - k e y w o r d s:
TRAPS
WWQA: ITEM: RTA000073819 ITEM: RTA000073819
Dated: 11/1995 Category: ITSCSAIXNV6
This HTML file was generated 99/06/24~12:43:27
Comments or suggestions?
Contact us