Managing hp netservers, Discovery and events, Anaging hp netservers – HP zl User Manual

Page 49

Advertising
background image

hp toptools for openview nnm

user guide

5.11 Managing hp netservers


HP Netserver L-series and E-series products running Windows NT, Windows 2000, Linux or Novell NetWare are
managed by HP Toptools for OpenView NNM through:

• Automatic discovery and identification on the NNM console

• Automatic trap destination setting for HP Netservers

• Automatic detection of HP Toptools Remote Control (with control actions enabled)

• Access to HP Toptools property pages

• Creation of subsystem status icons that display hardware status as a result of events

• Wake on LAN function

To enable management of HP Netserver products, HP Toptools for Servers agents must be installed on each server.
Agents may be obtained from the Netserver Navigator CD or downloaded from the HP Toptools website. The
Netserver agent installation program for Windows NT or Netware allows distribution of Netserver agents to multiple
target systems, and may not require a reboot to ‘take effect’. Using a ‘push’ distribution saves cost in deployment
time while avoiding reboot reduces downtime – especially during the workday.

Figure 5-16. HP Netservers can be located using the Find By Attribute feature of NNM.

5.11.1

Discovery and Events


Support for HP Netservers begins during installation of HP Toptools for OpenView NNM when Netserver MIBs are
compiled, trap definitions loaded, and the bridge discovery service (hpttBrdgDisc.exe) is installed. As the bridge
performs discovery, it identifies HP Netserver agents and enables the attribute “isHPNetserver”. Once identified,
the bridge changes the Netserver icon on the map and enables toptools menu items. Users can search for all
Netserver products using the Find By tool as shown in Figure 5-16, or build a map filter based on the attribute
isHPNetserver.

As discovery continues, each Netserver is automatically configured to send its alerts to the NNM console where the
alerts are translated and displayed in the Alarm browser and as status in the Netserver’s node submap. By
automatically setting the trap destination on Netservers, administrators avoid the time-consuming task of having to
visit each system individually to manually set the correct destination.

Page

49

Advertising