To: | Tivoli NetView Discussions <nv-l@lists.ca.ibm.com> |
---|---|
Subject: | Re: [NV-L] Reg Discovery |
From: | Leslie Clark <lclark@us.ibm.com> |
Date: | Fri, 1 Jun 2007 15:02:24 -0400 |
Delivery-date: | Fri, 01 Jun 2007 20:14:14 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <C527DE636D0FE74ABDD3D7E44759013F02FDA642@CHN-HCLT-EVS03.HCLT.CORP.HCL.IN> |
List-help: | <mailto:nv-l-request@lists.ca.ibm.com?subject=help> |
List-id: | Tivoli NetView Discussions <nv-l.lists.ca.ibm.com> |
List-post: | <mailto:nv-l@lists.ca.ibm.com> |
List-subscribe: | <http://lists.ca.ibm.com/mailman/listinfo/nv-l>, <mailto:nv-l-request@lists.ca.ibm.com?subject=subscribe> |
List-unsubscribe: | <http://lists.ca.ibm.com/mailman/listinfo/nv-l>, <mailto:nv-l-request@lists.ca.ibm.com?subject=unsubscribe> |
Reply-to: | Tivoli NetView Discussions <nv-l@lists.ca.ibm.com> |
Sender: | nv-l-bounces@lists.ca.ibm.com |
I assume that you are actually editing the seedfile that netmon is using as seen by "ps -ef | grep netmon" And I assume that the device is actually not being discovered, as seen by "Locate...Object.. By Attribute...IP Address" There can be a few different reasons why netmon will refuse to discover a certain node, and it is usually easiest to figure it out from the netmon.trace file with tracing turned on. The usual cases are: 1) The address you are trying to discover it by is a virtual address - that is, it does not appear in the address table of the device itself, as seen in rnetstat -Ix -c community xx.xx.xx.xx | grep xx.xx.xx.xx In that case, pick a different address on the device to use to discover it by. 2) This happens when you are trying to discover by a name. The name resolves to an address, but that address does not resolve to that name. It will discard the address. In that case, either fix the name resolution problem, or discover it by the address instead of the name. 3) The address is excluded by the ranges in the seedfile, and no address on the device is included. If you enable tracing for netmon (netmon -M -1) and then ping the address you are trying to discover and then grep xx.xx.xx.xx /usr/OV/log/netmon.trace you should see some clue as to why the device is not discovered. There is more about this sort of thing in the Diagnostics Guide Chapter 2. Diagnosing IP Discovery Problems. Cordially, Leslie A. Clark IT Services Specialist, Network Mgmt Information Technology Services Americas IBM Global Services (248) 552-4968 Voicemail, Fax, Pager
Hi, 1. Ping the IP
Thanks & Regards
_______________________________________________ NV-L mailing list NV-L@lists.ca.ibm.com Unsubscribe:NV-L-leave@lists.ca.ibm.com http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only) _______________________________________________ NV-L mailing list NV-L@lists.ca.ibm.com Unsubscribe:NV-L-leave@lists.ca.ibm.com http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only) |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: [NV-L] Traps by hostname, Santhanakrishnan Janakiraman (IT Services), Chennai |
---|---|
Next by Date: | RE: [NV-L] Traps by hostname, James Shanks |
Previous by Thread: | [NV-L] Reg Discovery, Santhanakrishnan Janakiraman (IT Services), Chennai |
Next by Thread: | [NV-L] Reg Discovery, Santhanakrishnan Janakiraman (IT Services), Chennai |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web