Skip to Content
OpenView Network Node Manager: Designing and Implementing an Enterprise Solution
book

OpenView Network Node Manager: Designing and Implementing an Enterprise Solution

by John Blommers
September 2000
Intermediate to advanced content levelIntermediate to advanced
352 pages
6h 41m
English
Pearson
Content preview from OpenView Network Node Manager: Designing and Implementing an Enterprise Solution

Deleting Unwanted Maps

When users are not discouraged from creating NNM maps at will, they will usually leave them on the system for indefinite periods. To list the maps on an NNM system, use this simple command:

					ovwls
				

This lists the maps and their owners. The consequences of having a lot of maps on an NNM system include:

  • larger database

  • longer backup time

  • out of control users

  • longer ovw -mapcount duration

  • longer ovtopofix -a duration

  • reduced overall NNM performance

  • discovery problems

Obviously, the fewer maps, the better. There is no particular reason to have a map named default, although a token map by that name is created for you. You can prevent users from creating their own maps by removing the corresponding registration files. A side effect ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

HP OpenView System Administration Handbook: Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations

HP OpenView System Administration Handbook: Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations

Tammy Zitello, Deborah Williams, Paul Weber

Publisher Resources

ISBN: 0130198498Purchase book