Well its not an issue of wether or not netmon is picking it up in real time, because as I said earlier we’re tailing the trapd.log and that’s how we find out a node went Down or Up. What we’re looking to do is verification that the Down was a positive down, not some sort of flapping. We know in NetView that netmon will eventually pick it up and change the state of the object to Marginal or Up or whatever it is, but we don’t want to insert anything into the database unless its confirmed. SO if we see a Node Down, we verify it by opening up a tcp connection to a known open port X times, if it is down, we insert data into Oracle. Its not so much real-time, but just for verification. At the same time, we have operators that monitor the NetView console and open tickets when they receive Node Down events. We would like to prevent that from happening by changing the status of the object if we know it was a false down up, because our script would verify it immediately after the Node Down event came through the trapd.log. I hope I am making sense..

Jason Allison
Principal Engineer
ARINC Incorporated

 -----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT com] On Behalf Of Freeman, Michael
Sent: Tuesday, September 21, 2004 12:04 PM
To: nv-l AT lists.us.ibm DOT com
Subject: RE: [nv-l] question about modifying objects in netview 7.1.3

Well we have netmon polling it, but we are relying on information from the trapd.log to use for SLA data. Like if we get a Node Down event or Node Up event, we put that into an Oracle database. We are trying to verify that the Node is really down, in a lot of cases in our network a Node will go down, and then an operator will do a demand poll or ping it, and then it will start responding again. So we have a script that tails the trapd.log file looking for Node Downs and if it receives one, it does a test trying to open a tcp connection a few times to verify that its really down, if it is, it gets inserted into the database. We also want to change the status of that object back to Node Up before netmon gets a chance to do it. Now of course there are other ways to do this verification by having a ruleset that has an inline function that does this but we had some problems with that..

 

So what do you think I should do? Use the API and OVwSetStatusOnObject to change the status, or is there an easier way?

 

Thanks in advance!

Mike Freeman

---

From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT com] On Behalf Of Allison, Jason (JALLISON)
Sent: Tuesday, September 21, 2004 10:31 AM
To: nv-l AT lists.us.ibm DOT com
Subject: RE: [nv-l] question about modifying objects in netview 7.1.3

 

You can use the API, but if you have netmon polling that IP device on interval, it will notice the incorrect status and change it back.  Start at "man OVwSetStatusOnObject", this will give you a start.  If you have any specific questions, feel free to ask.  Some statuses are "Reserved" and it wont allow you to change it via the API (eg Acknowledged), but there are programmatic ways around that.

 

Good luck,

 

Jason Allison
Principal Engineer
ARINC Incorporated

 

 -----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT com] On Behalf Of Freeman, Michael
Sent: Tuesday, September 21, 2004 11:25 AM
To: nv-l AT lists.tivoli DOT com
Subject: [nv-l] question about modifying objects in netview 7.1.3

We are trying to find a way to modify an object in NetView. If we know the node name, and want to change its status from say down, to up, because of an additional verification that proved it was up, how would we go about doing it? Are there any utilities or where should I look in the API?

 

Thanks,

Mike

 

*** Note new e-mail address

--

Michael J. Freeman

Netco Government Services

mfreeman AT netcogov DOT com

--