Cisco Systems 78-11324-02 How VHM Integrates with Third-Party NMSs, Device Types that VHM Manages

Chapter 1 Voice Health Monitor Overview

How VHM Integrates with Third-Party NMSs

How VHM Integrates with Third-Party NMSs

VHM can be integrated with third-party vendors’ NMSs such as HP OpenView Network Node Manager. VHM integrates with an NMS in two ways:

•Although VHM receives traps only from DFM, DFM can receive traps from an NMS or directly from devices. As a result, the traps DFM forwards to VHM may have come from an NMS or from a device.

See Installing and Setting Up the Device Fault Manager on Solaris for the default port numbers used by DFM and NMS and for example configuration scenarios to help you understand how DFM and NMSs can work together.

•VHM provides a trap notifier that allows you to:

–Configure the port and IP address of the NMS that the trap notifier sends SNMP trap messages to.

–Forward event notifications in the form of an SNMP trap to an NMS, when the NMS has been configured to listen on that port.

Device Types that VHM Manages

The voice-specific devices managed by VHM are categorized by voice device group. Table 1-2lists the voice device groups and their descriptions.

Table 1-2 Voice Device Groups

Group	Description
VC (voice cluster)	All CallManagers in a voice cluster,
	and all the devices with voice cards
	that register with any CallManager in a
	cluster (including Voice Gateways and
	Digital Voice Gateways).
VoiceServices	Media servers that may be running
	workflow applications or Cisco voice
	applications.

	User Guide for Voice Health Monitor
78-11324-02		1-9