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

Device Names Change Unexpectedly

NNM’s periodic configuration checking occasionally turns up a device name change. This is a configuration alarm. As such, it represents a nugget of useful information. NNM determines the selection name of an IP addressable device as follows:

  • the DNS name corresponding to the lowest IP address, otherwise

  • the MIB-2 system name if the device supports SNMP, otherwise

  • the IP address if there is one, otherwise

  • the device MAC address (assuming layer 2 discovery is on)

A typical device name change often corresponds to a change in the DNS database. The IP address inverse DNS lookup previously returned the original device name, but now it returns some other name. This may be completely legitimate or it may be an administrative ...

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