Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Filtering, Discovery and Naming Options... beyond the manual.

Filtering, Discovery and Naming Options... beyond the manual.

Filtering, Discovery and Naming Options... beyond the manual.

I currently have HP Openview NNM- NT version up and running. When I do a discovery, it discovers everything. I have looked through the manual at different ways of filtering. I want to use the sysName in SNMP, but it only seems to allow the OID or IP. Also, I am setting up regional sub-maps... and am not really sure of what I am doing, but if I can filter by sysName then it will be easy enough to separate into regions. I also want to use the sysName (which pulls from the set hostname in the router, as I understand) to make a consistent naming convention (non-ip based). Ideally I would like to use part of the descriptor in the router, but I think that may be stepping over the bounds of Openview.

Has anyone out there successfully used these filters & set naming conventions in Openview, who can help me figure all of this out?

RE: Filtering, Discovery and Naming Options... beyond the manual.

If you want to limit NNM discovery by host names (DNS, Hosts), the best way is to put the fully qualified DNS name into a file, then use a filter set reference to that file.  

For example;

Sets {
       Servers2bMgd "" { /filtersets/servers.fs }
// File name and extension can be anything!

Filters {
       Servers2bMgd_f "" { "IP Address" in Servers2bMgd }

This should work for SNMP SysName also.  Refer to Guide to Distribution and Scalability for filter file format/syntax.

RE: Filtering, Discovery and Naming Options... beyond the manual.

My best advice is to call HP support.  Unfortunately, if they're having a bad day, they'll tell you that defining filters falls under a consulting-for-fee category.  It's been a while since I was on the team, but I recall that certain fields are not filterable during discovery, as NNM only obtains a subset of the system MIB branch during discovery, prior to populating it's database with the node.  I'm not sure if sysName is one of those.  If it is, then you should have little problem using unix Regular Expressions in filters for sysNames.  Do a search for "RegEx quick reference" on the net.  These are like DOS wildcards (on steroids).  Don't forget to both enclose them in quotes and escape them with the '\' char.  Also, filters are inclusive, and all-or-nothing... if any single interface passes a filter, the entire network device passes as well.

Good luck!


RE: Filtering, Discovery and Naming Options... beyond the manual.

I am more or less a beginner w/ NNM.  I am trying to set up what I perceive is a straightforward OV-NNM setup:  Monitor all our of WANs 200 routers.  I have created a seed file with simply 5 of our core routers.  However, the only ones that appears are local to the NNM server.  I am not able to discover say a router from New York.  I get a message to the effect of: Unable to add interface x.x.x.x from the seed file: unable to determine subnet mask for new network.  My understanding is I can simply place the IP address of the router and away we go.  Obviously not the case.  I have tried loadhosts but I get an error to the effect ofC:\>loadhosts -m c:\windows\system32\drivers\etc
ERROR: Could not open input file c:\windows\system32\drivers\etc: Permission denied".  I have full rights to this box so I do not understand why I would get such an error.  

Any help would be greatly appreciated.


Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close