"The CDP Protocol Driver service failed to start"

[dalexeyev]

Hi,

Got this error after 2000.2.7.sr4 OS Upgrade of Callmanager 3.3.3(sr4).

Nothing informational in the event viewer:

"The description for Event ID ( 2 ) in Source ( CDP ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: , COpenAdapter::InternalGetTcpipProviderInfo failed!."

"Cisco Discovery Protocol Support Configuration" (http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/products_administration_guide_chapter09186a0080182147.html#85397) did not help - cdp.sys, cdpintf.dll are at place, implementing cdp2k101.reg without any positive results.

Any ideas/suggestions are highly appreciated!

Dmitry

[gogasca]

Hi Dmitry,

Seems to be

CSCsa91562

SYMPTOM: Indication on server console that one or more services failed to start. System event log shows CDP Protocol Driver Service failed to start.

CONDITION: Microsoft hotfix MS05-019 has been installed individually or as part of 2000.2.7sr3.

WORKAROUND

Upgrade to either Cisco CallManager Release 3.3(5), 4.0(2a), or 4.1(3) if you want to maintain the same functionality.

Otherwise to disable CDP functionality:

1) Open Computer Management console and click on Device manager.

2) Go to view menu and click on "show hidden devices"

3) Now in the right pane you should be able to see "Non-Plug and Play Drivers"

4) Opening that should let you see "CDP driver"

5) Right click that and say "Disable"

Gonz-

[dalexeyev]

Thanks for Your reply, Gonz-!

BTW, what troubles may I expect due to disabled CDP ?

Dmitry

[clsalaza]

CCM and other cisco devices use CDP only to discover neighbour cisco devices. You should not have any troubles for it only that autodiscovery will be disabled and you will need to explicitly declare anything that is currently being autosensed by CDP.

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a0080182147.html#1019025

" Any Cisco device with CDP support can locate a Cisco CallManager by using these periodic messages. For example, a device can locate Cisco CallManager agent IP addresses using the CDP cache from the direct neighboring devices."

which means that all of them will be need to point explicitly to CCM instead of just get that info from CDP. Most new deployments relay on explicit configuration rather than just getting the CCM location just from CDP (i.e. DHCP). Let us know...

[jessakhanian]

Hello,

Disabling the CDP driver on the server gets rid of the "failed service" messages, but it sounds like as if any CiscoWorks server monitoring the server (such as ITEM) will not be able to communicate with the server. This is how I read it from the release notes for the Service Release (see below):

CSCsa91562 - Service failed to start error message for CDP.sys driver after installing MS05-019 that is part of this service release. CDP is the Cisco Discovery Protocol driver used for integration with Cisco serviceability products like CiscoWorks IP Telephony Monitor. When the CDP.sys driver fails to start CiscoWorks will put this server in the unknown server category. Installing MS05-019 will not affect call processing or telephony features. CallManager versions 3.3(4), 3.3(5), 4.0(2), and all versions of 4.1 have a newer version of CDP.sys (4.0.0.0) that works with MS05-019.

I haven't had a chance to test ITEM to see if it still sees the affected server or not. Has anyone else run into this? Another work-around, I guess, would be uninstall MS05-019, but that hotfix seems rather critial to have on the server.

Thanks,

Joseph