To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | RE: [nv-l] Discovery delays |
From: | James Shanks <jshanks@us.ibm.com> |
Date: | Thu, 22 Jan 2004 10:25:20 -0500 |
Delivery-date: | Thu, 22 Jan 2004 15:54:06 +0000 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
Then either turn on the netmon trace and do it again so you can see what happens when netmon tries to contact the device or open a problem to Support. This functionality works for everyone else. James Shanks Level 3 Support for Tivoli NetView for UNIX and Windows Tivoli Software / IBM Software Group
Yes, I did this as well L: > -----Original Message----- > From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On > Behalf Of James Shanks > Sent: Thursday, January 22, 2004 2:57 PM > To: nv-l@lists.us.ibm.com > Subject: RE: [nv-l] Discovery delays > > > After you updated the seed file, did you then stop and restart netmon > (not "netman") or issue the command "/usr/OV/bin/netmon -y" to cause a > reload of the file? That happens automatically if you use the java seed > file editor but otherwise not. > > > James Shanks > Level 3 Support for Tivoli NetView for UNIX and Windows > Tivoli Software / IBM Software Group > > > > "Pal, Laszlo" <laszlo.pal@eds.com> > Sent by: owner-nv-l@lists.us.ibm.com > > 01/22/2004 03:37 AM > Please respond to nv-l > > To: nv-l@lists.us.ibm.com > cc: > Subject: RE: [nv-l] Discovery delays > > > > > I modified eed file by putting in my netman server as a seed node. After > that I ran pings from that host and run demand pool on it. Nothing has > changed > > Laszlo > > > > -----Original Message----- > > From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] > On > > Behalf Of James Shanks > > Sent: 2004. január 21. 17:20 > > To: nv-l@lists.us.ibm.com > > Subject: RE: [nv-l] Discovery delays > > > > > > I did not suggest a ping and demandpoll. I suggested modifying your > seed > > file. > > > > James Shanks > > Level 3 Support for Tivoli NetView for UNIX and Windows > > Tivoli Software / IBM Software Group > > > > > > > > "Pal, Laszlo" <laszlo.pal@eds.com> > > Sent by: owner-nv-l@lists.us.ibm.com > > > > 01/21/2004 11:00 AM > > Please respond to nv-l > > > > To: nv-l@lists.us.ibm.com > > cc: > > Subject: RE: [nv-l] Discovery delays > > > > > > > > > > I tried this. I removed my netman then I pinged the address from another > > device and then I run demand poll on that device. The removed object > does > > not come up again. Sometimes I don't understand the logic of this cool > > stuff > > :) > > > > Any other idea? > > > > L: > > > > > > > -----Original Message----- > > > From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] > > On > > > Behalf Of James Shanks > > > Sent: 2004. január 21. 14:20 > > > To: nv-l@lists.us.ibm.com > > > Subject: Re: [nv-l] Discovery delays > > > > > > > > > If you want immediate rediscovery then you must put the deleted device > > in > > > the seed file as a positive discovery seed. > > > Just add it's name if you are using DNS or primary IP address to the > > file > > > and one of the first things netmon will do is go out and try to find > the > > > device. > > > Otherwise you wait for it's IP address to show up in some other node's > > ARP > > > cache. netmon won't know it is there unless someone tells him about > > it. > > > If you want him to find ti immediately, then you have to be the > someone. > > > > > > James Shanks > > > Level 3 Support for Tivoli NetView for UNIX and Windows > > > Tivoli Software / IBM Software Group > > > > > > > > > > > > "Pal, Laszlo" <laszlo.pal@eds.com> > > > Sent by: owner-nv-l@lists.us.ibm.com > > > > > > 01/21/2004 05:43 AM > > > Please respond to nv-l > > > > > > To: nv-l@lists.us.ibm.com > > > cc: > > > Subject: [nv-l] Discovery delays > > > > > > > > > > > > > > > Hi, > > > > > > I have a continuous problem with NV713. When I have to re-discover a > > site > > > or > > > a device I delete this and stop and restart netmon daemon. I thought > > this > > > is > > > restarts discovery and the deleted site or device will be re- > discovered. > > > Unfortunately, it does not happen every time. Sometimes the device re- > > > appear > > > in a few days, sometimes it never showed again. What can be the reason > > of > > > this? How can I avoid? > > > > > > Thank you > > > Laszlo > > > > > > > > > > > > > > > > > > > > > |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: [nv-l] Discovery delays, Pal, Laszlo |
---|---|
Next by Date: | Re: [nv-l] two questions, James Shanks |
Previous by Thread: | RE: [nv-l] Discovery delays, Pal, Laszlo |
Next by Thread: | [nv-l] Event -Forwarding: extend cache-file, Haseneder, Martina |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web