Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Differentiate between Critical and Non Critical 1

Status
Not open for further replies.

Guest_imported

New member
Jan 1, 1970
0
Hello everybody,

I just took over an Openview Project for my new job and though it is a bit overwhelming, I am trying to work through this step by step.

Currently, the only alerts I've been seeing are Cisco linkUp and linkDown traps. Unfortunately, I have over 3000 users on this network and everytime one of them turns their computer on or off, it adds to the alerts.

Is there a better way to filter this? Possibly a way to differentiate between users PC's and Critical Network Equipment?

Any help is appreciated as well as any start up tips.

Thanks in advance,

Carl Hester

 
Carl,

Assuming that you're talking NNM and not ITO (both are openview), you could set up a map filter to tell NNM what you want the map to discover. "A Guide to Scalibility and Distribution for NNM" discusses this in depth with an entire chapter focused on Filter Definition Language.

The language construct is
FilterName "Description of Filter" {AVA}

AVA stands for Attribute Value Assertion and is basically the comparison of a condition to see if an object does or does not meet the filter requirements.
"IP Hostname" == Carl
In this example IP Hostname is object attribute and Carl is the AVA that the object is being compared against....so if an object tries to pass the filter with a hostname other than Carl it will fail.

Something like the following is an example of what can be done....

Devices "Managable Devices" { isNode && isSNMPSupported )
CarlsNetwork "Manageable Devices on My Network" { "IP Address" ~ 10.10.10.100-200 }
Carl_TMF "All Manageable Devices" { Devices || CarlsNetwork || NetsNSegs }

This is just an example in theory that would filter out any devices, in a specific range, on your network that does not support SNMP, but don't quote me on this because I did not test! The default filters file is located in $OV_CONF/C that you can use as starting point. Put your filter in place by choosing Map --> Properties --> Double click on IP Map and input the file under Map Filter. Test it with ovfiltertest first before using it.

Hopefully I haven't been too wordy before you have a chance to investigate the theory behind FDL, but check out this book (Scalability and Distribution), it will become your best friend. Hope this takes you in the direction that you want to go.

***cgainey
 
Great response. Thanks for the help. I've started reading the Scalability and Distribution book. I'll let you know if I come across any other hurdles.

Thanks again,

Carl

 
you mention the book "A Guide to Scalibility and Distribution for NNM" in your post. Where can I find that? Is it available as a pdf on HP's site, or is it an independent work, and if so who is the author.

Thanks,

David
 
cnlov,

Sorry for the delayed respone. Have been away for a while. To answer your question.....yes. Here is the location to find the Guide to Scacibility and Distribution and lots of other HP docs.....


Under "Browse by Topic", select 'Network and Systems Management', select 'HP Openview Network Node Manager'

It is the second guide listed and is available in PDF format.


<cag>
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top