Chapter 1 Voice Health Monitor Overview
Overview of VHM
Table
Component or Feature | Description of Dependency |
|
|
Inventory Collection | Inventory Collection synchronizes the VHM device list with DFM; |
| during this process, |
| deleted from DFM inventory will also be added to or deleted from VHM |
| inventory. |
| When Inventory Collect All is triggered in VHM, it sends a rediscovery |
| trigger to DFM. After DFM completes rediscovery, VHM proceeds with |
| rediscovery, importing any newly installed voice cards, ports, or voice |
| applications. |
| If the link between the device and the DFM server is slow, DFM could |
| time out or mark the interface type as Generic. If the rediscovery process |
| times out and DFM does not discover an interface, VHM also will not |
| discover the interface. |
| VHM also registers with DFM to receive device list update events. If any |
| device is added or deleted, or becomes unresponsive, DFM sends an |
| event alarm to VHM. VHM can process the event by, for example, |
| starting to manage new |
| Note If a device appears as Undiscovered in DFM, it also appears as |
| Undiscovered in VHM. If a device appears in a valid category |
| (for example Host, Switch, or Router) in DFM but does not have |
| a voice interface, it will be unsupported in VHM. If a device is |
| uncertified in DFM, it will not appear anywhere in VHM. |
|
|
Alarm logs | VHM generates voice faults and listens for |
| DFM. If VHM receives an alarm for a device it manages, it uses the |
| alarm in voice fault correlations. Alarms for devices that VHM does not |
| manage are dropped. |
| For more information about VHM fault browsers, see Chapter 2, |
| “Monitoring Voice Network Health.” |
|
|
| User Guide for Voice Health Monitor |
