This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
I had this problem a while ago. Here is what was suggested to me at that
time. It did not help much. But I was told, this maybe a fix for the netmon
startup problem due to AIX timing bug. Look at item under B3.
Actions:
A 1. cd to usr/OV/sockets
- bring down netview gui / daemons
- delete all files from that directory (do not delete any
subdirectories)
A 2. Reboot the box a few times to see if the problem still occurs
"AND"
B3. Change following line in /usr/OV/bin/nmcheckconf to allow
more time to communicate with the snmp Agent/snmpd.conf
/usr/OV/security/cmds/snmpget_unsecure -t3 -r2 127.0.0.1 system.sysDescr.0 >
/dev/null 2>&1
Chage t3 to t6 and r2 r4 which is doubling the retry times and wait
-----Original Message-----
From: James Shanks [mailto:jshanks AT us.ibm DOT com]
Sent: Monday, October 29, 2001 11:12 AM
To: IBM NetView Discussion
Subject: Re: [NV-L] Problem with netmon
Have you tried just stopping and restarting snmpd? The MIB message is
usually NOT the problem unless you don't have the default set which includes
rfc1213-MIB-II loaded.
Do "stopsrc -s snmpd", wait a few seconds, then "startsrc -s snmpd" and see
if it restarts. Count to ten and ovstart netmon.
Doesn't help? then check that your /etc/hosts has these two entries first:
127.0.0.1 loopback localhost
<your_ip_address> <your_hostname>
and that xnmsnmpconf has entries for BOTH of these if you are not using
"public" as the default community name.
Try an snmpwalk of your own box and see if it works (don't specify the
community --let it default). If it does, then netmon should start.
If it doesn't then I don't know what to tell you.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group
"Olson, Stephen J" <stolson AT state.pa DOT us>
Sent by: owner-nv-l AT tkg DOT com
10/29/2001 10:42 AM
Please respond to IBM NetView Discussion
To: "'IBM NetView Discussion'" <nv-l AT tkg DOT com>
cc:
Subject: [NV-L] Problem with netmon
Greetings to all,
First, I may be a little cranky this morning since our Netview
box went down after an extended power outage, so I hope I wasn't
too harsh with David about his autoresponder. :)
AIX 4.3 and netview 5.2
(I know, I know, upgrade!!!)
Anyway, this has happened in the past and all I have ever done
is restore to solve the problem.
If the machine has an abrupt shutdown, netmon will not start.
I get the following message ...
____________________________________________________________________-
Cannot communicate with SNMP Agent via loopback address (127.0.0.1); it is
either not running or has been configured with a community name different
from that configured into TME 10 NetView for this system. If a community
name ha
s
been configured into the SNMP Agent, that community name must be configured
via xnmsnmpconf and /usr/OV/conf/ovsnmp.conf for address 127.0.0.1 as well
as for the hostname or IP address of this system.
Or, the /usr/OV/conf/snmpmib and /usr/OV/conf/snmpmib.bin files are
corrupted
and need to be rebuilt using the
Maintain->Rebuild MIB binary file with installation MIB defaults
option in smit
_____________________________________________________________________
When I tried to rebuild the files, it *really* screwed things up.
Any ideas?
Thanks in advance,
Steve Olson
PA State Police
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
I had
this problem a while ago. Here is what was suggested to me at that time. It did
not help much. But I was told, this maybe a fix for the netmon startup problem
due to AIX timing bug. Look at item under B3.
Actions:
A 1. cd to
usr/OV/sockets
- bring down netview gui / daemons
- delete all files from that directory (do not delete
any subdirectories)
A 2. Reboot the box
a few times to see if the problem still occurs
"AND"
B3. Change following line in
/usr/OV/bin/nmcheckconf to allow
more time to communicate with the snmp
Agent/snmpd.conf
/usr/OV/security/cmds/snmpget_unsecure -t3 -r2 127.0.0.1
system.sysDescr.0 > /dev/null 2>&1
Chage t3 to t6 and r2 r4
which is doubling the retry times and wait
Have you
tried just stopping and restarting snmpd? The MIB message is usually NOT
the problem unless you don't have the default set which includes
rfc1213-MIB-II loaded.
Do
"stopsrc -s snmpd", wait a few seconds, then "startsrc -s snmpd" and see if it
restarts. Count to ten and ovstart netmon.
Doesn't help? then check that your /etc/hosts has
these two entries first:
127.0.0.1
loopback localhost
<your_ip_address> <your_hostname>
and that xnmsnmpconf has entries for BOTH of these if
you are not using "public" as the default community name.
Try an snmpwalk of your own box and see if it works
(don't specify the community --let it default). If it does, then netmon
should start.
If it doesn't then I
don't know what to tell you.
James Shanks
Level 3 Support for
Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software
Group
|
| "Olson, Stephen J"
<stolson AT state.pa DOT us>
Sent by: owner-nv-l AT tkg DOT com
10/29/2001 10:42 AM
Please respond to IBM NetView Discussion
|
To:
"'IBM NetView Discussion'" <nv-l AT tkg DOT com>
cc:
Subject: [NV-L] Problem
with netmon
|
Greetings to all,
First, I may be a little cranky this morning
since our Netview
box went down after an extended power outage, so I hope I
wasn't
too harsh with David about his autoresponder. :)
AIX
4.3 and netview 5.2
(I know, I know, upgrade!!!)
Anyway, this
has happened in the past and all I have ever done
is restore to solve the
problem.
If the machine has an abrupt shutdown, netmon will not
start.
I get the following message
...
____________________________________________________________________-
Cannot
communicate with SNMP Agent via loopback address (127.0.0.1); it is
either
not running or has been configured with a community name different
from
that configured into TME 10 NetView for this system. If a community
name
ha
s
been configured into the SNMP Agent, that community name must be
configured
via xnmsnmpconf and /usr/OV/conf/ovsnmp.conf for address
127.0.0.1 as well
as for the hostname or IP address of this system.
Or,
the /usr/OV/conf/snmpmib and /usr/OV/conf/snmpmib.bin files
are
corrupted
and need to be rebuilt using the
Maintain->Rebuild
MIB binary file with installation MIB defaults
option in
smit
_____________________________________________________________________
When
I tried to rebuild the files, it *really* screwed things up.
Any
ideas?
Thanks in advance,
Steve Olson
PA State
Police
_________________________________________________________________________
NV-L
List information and Archives:
http://www.tkg.com/nv-l
|
