|
No
problem. The tech on my PMR had me totally disable the snmpCollect.
The problem was still happening, so when he asked me if other products were
installed, it made me think of the scripts we have running. I checked
those that are run from cron and found it running every hour. Once I
looked at the script and saw what it did, it was obvious.
Craig,
Mind if I ask now you
determined is was another script?
I assume you stopped all of NetView, and the request were still be made
with incorrect community name?
Mark F
Sklenarik
IBM SWG Tivoli Solutions
Quality Assurance
Business Impact Management and Event Correlation
Software
Quality Engineer
IBM Corporation
"Treptow, Craig"
<Treptow.Craig@principal.com>
Sent by: owner-nv-l@lists.us.ibm.com
01/06/2005 09:40 AM
|
|
To
| <nv-l@lists.us.ibm.com>
|
|
cc
|
|
|
Subject
| RE: [nv-l]
Authentication failures coming Netview -
Resolved |
|
I apologize. This was self induced by a script that
was running and I had completely forgot about.
-----Original Message-----
From: owner-nv-l@lists.us.ibm.com
[mailto:owner-nv-l@lists.us.ibm.com]On Behalf Of Treptow,
Craig
Sent: Wednesday, January 05, 2005 11:15 AM
To:
nv-l@lists.us.ibm.com
Subject: RE: [nv-l] Authentication failures
coming Netview
Thanks.
I have opened a PMR this morning. I will update the list when I
know more.
I appreciate all of your suggestions.
-----Original Message-----
From:
owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On Behalf
Of Mark Sklenarik
Sent: Wednesday, January 05, 2005 10:51
AM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l]
Authentication failures coming Netview
Hi Craig,
Sorry this is the first I have seen your reply.
It appears there is a bug in
NetView, your best option is to call IBM Support for future debug assistance.
I would have to start asking for netmon traces and ip traces, to determine
when and why NetView is making request with incorrect community
names.
So at the time
of failure, the output from netmon -a 175 shows that NetView has the correct
community name stored?
How many communities are listed in /usr/OV/conf/communityNames.conf file?
Is the
MaximumCommunityNames parameter set on /usr/OV/conf/netmon.conf? Only have to
set this if more than the default of 6 communities are used.
Mark F Sklenarik
IBM
SWG Tivoli Solutions
Quality Assurance
Business Impact
Management and Event Correlation
Software Quality Engineer
IBM
Corporation
"Treptow, Craig"
<Treptow.Craig@principal.com>
Sent by:
owner-nv-l@lists.us.ibm.com
01/05/2005 09:48 AM
|
|
To
| "NetView
List \(E-mail\)" <nv-l@lists.us.ibm.com>
|
|
cc
|
|
|
Subject
| Re: [nv-l]
Authentication failures coming
Netview |
|
Hi. I have lost your replies,
so I'm replying to what I'm reading on the archives.
To Mark
Sklenarik:
Yes, the device looks good in the xnmsnmpconf
view.
There is nothing else on this machine except Netview, so I doubt
something else is doing it, but I will take another look.
We do have
/usr/OV/conf/communityNames.conf, and the strings being tried are listed in
that file.
No, it was not trying public.
I did the netmon -a 160
and 175 commands. The device looks fine in that
output.
snmpCollect is not collecting from anything.
To
James Robin:
Yes, this is a Cisco router and we gave these lines in the
config:
snmp-server community XXXXXXX RO 80
snmp-server community
YYYYYYY RW 81
snmp-server host 162.131.23.89 public
snmp-server host
162.131.38.61 public
-----Message Disclaimer-----
This
e-mail message is intended only for the use of the individual or
entity to
which it is addressed, and may contain information that is
privileged,
confidential and exempt from disclosure under applicable law.
If you are
not the intended recipient, any dissemination, distribution or
copying of
this communication is strictly prohibited. If you have
received this
communication in error, please notify us immediately by
reply email to
Connect@principal.com and delete or destroy all copies of
the original
message and attachments thereto. Email sent to or from the
Principal
Financial Group or any of its member companies may be retained
as required
by law or regulation.
Nothing in this message is intended to constitute
an Electronic signature
for purposes of the Uniform Electronic Transactions
Act (UETA) or the
Electronic Signatures in Global and National Commerce Act
("E-Sign")
unless a specific statement to the contrary is included in this
message.
-----Message Disclaimer-----
This e-mail
message is intended only for the use of the individual or
entity to which
it is addressed, and may contain information that is
privileged,
confidential and exempt from disclosure under applicable law.
If you are
not the intended recipient, any dissemination, distribution or
copying of
this communication is strictly prohibited. If you have
received this
communication in error, please notify us immediately by
reply email to
Connect@principal.com and delete or destroy all copies of
the original
message and attachments thereto. Email sent to or from the
Principal
Financial Group or any of its member companies may be retained
as required
by law or regulation.
Nothing in this message is intended to constitute
an Electronic signature
for purposes of the Uniform Electronic Transactions
Act (UETA) or the
Electronic Signatures in Global and National Commerce Act
("E-Sign")
unless a specific statement to the contrary is included in this
message.
-----Message
Disclaimer-----
This e-mail message is intended only for the use of the
individual or
entity to which it is addressed, and may contain information
that is
privileged, confidential and exempt from disclosure under
applicable law.
If you are not the intended recipient, any dissemination,
distribution or
copying of this communication is strictly prohibited. If
you have
received this communication in error, please notify us immediately
by
reply email to Connect@principal.com and delete or destroy all copies
of
the original message and attachments thereto. Email sent to or from
the
Principal Financial Group or any of its member companies may be
retained
as required by law or regulation.
Nothing in this message
is intended to constitute an Electronic signature
for purposes of the
Uniform Electronic Transactions Act (UETA) or the
Electronic Signatures in
Global and National Commerce Act ("E-Sign")
unless a specific statement to
the contrary is included in this
message.
-----Message Disclaimer-----
This e-mail message is intended only for the use of the individual or
entity to which it is addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable law.
If you are not the intended recipient, any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
reply email to Connect@principal.com and delete or destroy all copies of
the original message and attachments thereto. Email sent to or from the
Principal Financial Group or any of its member companies may be retained
as required by law or regulation.
Nothing in this message is intended to constitute an Electronic signature
for purposes of the Uniform Electronic Transactions Act (UETA) or the
Electronic Signatures in Global and National Commerce Act ("E-Sign")
unless a specific statement to the contrary is included in this message.
|