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!

Altering Colours of Errors

Status
Not open for further replies.

Guest_imported

New member
Jan 1, 1970
0
Hey Guys,

I am just beginning to learn HP OpenView Network Node Manager. Im finding it a great management tool, however i dislike the fact that a critical error and a "link down" error both look the same on a map. For example if A is connected to B and B goes down, it shows up Red. Now if B has a critical Error it B also goes Red. I would like to split Critical Errors and Inactive Connections up into two seperate colours.

Also if you still have no idea what im talking about go to Help->Show Legend.

I am not sure if its possible but any help would be great.

Thanx.
 
DavCho,
I'm not sure if I understand what your inquiry is asking so I may not address your question and somebody else may be able to better help you with this. But since you're beginning I'll provide some info that may be pertinent....

In HP Openview NNM devices are listed as critical, major, marginal, etc., based on the severity of the determined outage. The event browser in NNM and HP Openview ITO will report the trouble as a link down/node down trap, but in either case both are valid critcal outages whether received on the map or in the browser(s). Within NNM you will see a red device denoting the critical state, so Status Propagation may be more what you are looking to change more so than the actual colors themselves. Basically it is a way to tell NNM..."Here's how I want the map to show alarm status." I think you can find this by going to Map --> Map Properties and selecting the Status Propagation tab. (It may differ from version to version)

In my environment since NNM is utilized as one of the main sources of monitoring, if for example, router B which lies on a low-level/child submap goes critical, then the higher-level/parent submap will also go critical, alerting the operator that there is a problem with an underlying device on a network or segment. That is only one way to use probagation. A map can be configured to alarm a warning status to the parent submap if 1 network device on a child submap goes red and only alarm a critical status to the parent submap if 5 or 6 or all devices go red on a child submap.

Take a look in the HP Openview NNM Managing Your Network manual, probably somewhere in the map customizations section. It may help you out or at least give you some good information for future reference.

***cgainey

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top