I'm using Cisco Unified Operations Manager (OM) v1.1 to monitor my IPT deployment. When I want to create performance graph for the voice gateway, an error message appears. The error said that OM doesn't manage the Call Manager where the corresponding gateway have registered.
When I investigate the error log, it is said that OM cannot collect data. The device is experiencing communication problems.
I have checked about wrong credentials (username / password). But it's not the problem.
What kind of problem may happen in this case? I really need this graph for my periodical report.
For any help and reply, really thanks in advance.
Here's some things to look at:
Check if GPF server is up using: NMSROOT\bin\pdshow GPF
Make sure the devices are in monitored state. If not it cannot get any data as all of the data comes via http. Devices -> Device Mgmt.
If not edit credentails under Devices -> Device Credentials.
Check if csv files are written under NMSROOT\data\#GSUDATA# for the named device.
Check if polling is enabled under admin settings for voice health/data.
Check whether the device is in partially monitored state. If the device is in partially monitored state then check whether the windows username and password are entered as the primary credentials in DCR.
Check the error log file (NMSROOT\data\gsu\_#GSUDATA#_\Error.log) to see whether there have been any errors while collecting data for the device.
Following is the list of strings that can be found in the error messages and the probable causes for the errors.
- Cannot collect WMI* * if there is a communication problem with device.
- Incomplete WMI counters if there is an error occurred while processing the data.
- No WMI counter if no data is available in the device.
WMI credentials are your Admin login credentials to WINDOWS, not the application. They go under primary credentials in the DCR page on the screen you add snmp communites. OM -> Devices -> Device Credentials.
And finally, check out the Detailed Device View (DDV), look under the "Unity Version" for this device, if that is blank, it's likely your hitting bug CSCsh46239.
Hopefully this helps to determine the source of the problems.