| To: | nv-l@lists.us.ibm.com |
|---|---|
| Subject: | RE: [nv-l] Authentication failures coming Netview - Resolved |
| From: | George deSocio <desocio@us.ibm.com> |
| Date: | Fri, 7 Jan 2005 12:14:07 -0500 |
| Delivery-date: | Fri, 07 Jan 2005 17:14:40 +0000 |
| Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
| In-reply-to: | <83B1FCCE169AD74FBAC555C3B6E7B57709267ADD@pfgdsmmbx004.principalusa.corp.principal.com> |
| Reply-to: | nv-l@lists.us.ibm.com |
| Sender: | owner-nv-l@lists.us.ibm.com |
|
We noticed the port number (from port) on the snmpget was changing for each request, and that the request was hourly. If it's netmon, status polling it doesn't change. netmon usually uses the same from port number. If it's snmpCollect it changes with each request. So it looked like a collection from the sniffer trace. That led to looking at periodic data gathering facilities like snmpCollect. Regards, Geo. George deSocio IBM Americas Support - Distributed Network Management Dept 46-E1ZA IBM B660 CC109 HWY 54 & 600 Park Offices Research Triangle Park, NC 27709
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. -----Original Message----- From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On Behalf Of Mark Sklenarik Sent: Thursday, January 06, 2005 6:24 PM To: nv-l@lists.us.ibm.com Subject: RE: [nv-l] Authentication failures coming Netview - Resolved 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
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
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.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: [nv-l] Authentication failures coming Netview - Resolved, Treptow, Craig |
|---|---|
| Next by Date: | [nv-l] Specific traps to a different log, Clinkscales, Charles |
| Previous by Thread: | RE: [nv-l] Authentication failures coming Netview - Resolved, Treptow, Craig |
| Next by Thread: | [nv-l] Specific traps to a different log, Clinkscales, Charles |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web