I have LMS 2.5, recently updated to LMS 2.51. All the recent (Jan 2006) updates have been applied (Campus MDF 1.7, plus the RME device updates). I have a CallManager 4.1(3)SR2 server installed and DFM reports the device discovery as 'Questioned', the error code is:
*** Data Collector Status Information ***
Error Code = Others
Error Message = MDFId mismatch
Is this a new bug? It previously discovered the CCM server OK.
Ciscoworks keeps track of device model-types by their OID number, which you can see when you manually select the device type under Device Management. In your case an incorrect OID number is being assigned which then leads to incorrect snmp values while trying to query the device.
I'm experiencing the same problem as you. Open Device Management and change the "device type"; you will be presented with a rather large list of items to chose from. In our case the call managers are being catalogued as "Voice >> Call Control >> Cisco Call Manager" which leads to the error you describe; in previous versions of Ciscoworks the devices were listed as "78xx Media Convergence Server" and the devices were monitored as expected. If you select the entry which accurately describes your hardware, specifically the OID must match, then this _should_ fix the issue.
Unfortunately the next time Ciscoworks scans your network it will eronously provide the wrong OID again, leaving you in the same place as before. I haven't opened a TAC case yet but these are the results I've seen.
From my perspective what you're describing sounds like a bug in Common Services; whether your hardware is supported or not in DFM ought to be documented somewhere, likely in the DFM page.
I believe the behaviour you're seeing is somehow tied to DCR, which means that until your call managers can be properly catalogued you won't be able to manage the servers using Ciscoworks. In order to monitor the servers in DFM, or any other module in Ciscoworks, the right OID must be associated with the device so that snmp queries can be performed.
Since this wasn't causing any particular problems I didn't pursue this issue any further.
However I have now installed LMS 2.6 and last week installed the latest updates and guess what? DFM now sees the MCS7825 (HP DL320) as a Callmanager (this is what it complained about previously and I had to manually change it to a MCS 7800 Server) and now it doesn't complain and works.....
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...