Guest

Cisco Unified Intelligent Contact Management Hosted

Field Notice: CDP Driver Causes Windows Stop Error During Reboot of ICM 4.5


March 1, 2002



Products Affected

Product

ICM, NAM

Problem Description

Windows NT 4.x ICM Systems

On some systems during initial install or during an upgrade to ICM version 4.5, the system will "blue-screen" after re-starting with the following or similar error message:

*** STOP: 0x0000000A (0x536461B6, 0x00000003, 0x8042CB5C)
IRQL_NOT_LESS_OR_EQUAL *** Address 0x8042CB5C base at 0x80400000,
DateStamp 39760637 -ntoskrnl.exe

This error is most likely to be observed on a multi-homed system in which one of the NIC interfaces is enabled, but not configured. If your system is set up in this manner, you can simply disable the NIC interface that has not been configured and the fault will not occur. However, this fault has also been observed on other systems that are not multi-homed but have miniport drivers that act as additional adapter interfaces.

Background

Cisco Discovery Protocol (CDP)

CDP is a device discovery protocol that runs on all Cisco-manufactured equipment (that is, routers, bridges, communication servers, WBU switches, and so on). Each device sends periodic messages to a multicast address. Each receiver enabled device listens to the periodic messages sent by others in order to learn about neighboring devices and determine when their interfaces to the media go up or down. All Cisco ICM server nodes install the CDP protocol driver as a send-only device. This enables neighboring CDP aware devices to discover the ICM nodes.

  • Cisco devices (and other devices which implement CDP) need to discover each other in a protocol/media independent way.

  • Network management applications need to dynamically discover Cisco devices which are neighbors of already known devices, especially neighbors which implement lower layer "transparent" protocols.

  • Network management applications can retrieve the device type and SNMP agent address of neighboring devices. This enables the applications to subsequently send SNMP queries to the neighboring devices.

  • There are a number of other protocols which need to know if and when that protocol is enabled on a neighboring device. Rather than have each such protocol send its own periodic "hello" message, such "hello" messages can be piggy-backed on CDP packets.

  • IT managers and analysts can use tools that support the CDP information, such as CiscoWorks 2000, for configuration monitoring, topology discovery, and fault analysis.

Problem Symptoms

Windows NT 4.x ICM Systems

On some systems during initial install or during an upgrade to ICM version 4.5, the system will "blue-screen" after re-starting with the following or similar error message:

*** STOP: 0x0000000A (0x536461B6, 0x00000003, 0x8042CB5C)
IRQL_NOT_LESS_OR_EQUAL *** Address 0x8042CB5C base at 0x80400000,
DateStamp 39760637 -ntoskrnl.exe

This error is most likely to be observed on a multi-homed system in which one of the NIC interfaces is enabled, but not configured. If your system is set up in this manner, you can simply disable the NIC interface that has not been configured and the fault will not occur. However, this fault has also been observed on other systems that are not multi-homed but have miniport drivers that act as additional adapter interfaces.

Workaround/Solution

Recovering From A Boot Failure

Windows NT 4.x

Try the following steps to recover from the "blue screen" failure:

  1. Try pressing the space bar at the OSLOADER screen and selecting the Last Known Good or Original Configuration option. If this is successful, go to step 5.

  2. If step 1 does not work, and the boot partition is FAT formatted, try booting using a DOS bootable floppy disk. Type C: to access the hard disk drive boot partition. If this is successful, go to step 5.

  3. If steps 1 or 2 do not work, try installing Windows NT again into a different directory (assuming you have sufficient disk space). Reboot and select the new NT install as the boot option. Browse to the original directory where NT was installed (usually WINNT). Browse to the SYSTEM32\DRIVERS subdirectory and delete the CDP.SYS file. If this is successful, go to step 6.

  4. If all other attempts fail, try removing the hard disk drive and install it as a secondary drive in a machine that is running Windows NT. The machine you move the drive to must be running a version of Windows NT that is equal to or greater than the one that failed. Browse to the WINNT\SYSTEM32\DRIVERS directory on the disk drive that has the problem and delete the CDP.SYS file. Re-install the repaired drive in the original computer. Go to step 6.

  5. From the command prompt type the following:

    cd %SYSTEMROOT%\SYSTEM32\DRIVERS
    dir CDP.SYS      -- to confirm the driver is present.
    del CDP.SYS
    dir CDP.SYS      -- to confirm it has been removed.
    
  6. Restart the computer normally and follow the steps for Applying The 4.5a Fix To A Working 4.5 System outlined below.

Applying The 4.5a Fix To A Working 4.5 System

Windows NT 4.x

If you have installed ICM version 4.5 and not observed this failure, you may still want to update the driver to ensure that the error does not occur as a result of a hardware configuration change.

  1. Open Explorer and browse the WINNT\SYSTEM32\DRIVERS directory. If you have installed Windows to a different directory, substitute the appropriate value instead of "WINNT."

  2. Delete the CDP.SYS file from the DRIVERS directory.

  3. Copy the new CDP.SYS file from the DRIVERS\NT4\CDP directory on the 4.5a CD-ROM to the WINNT\SYSTEM32\DRIVERS directory.

  4. Restart the system again and verify that it boots correctly.

  5. Open the Control Panel and select Devices.

  6. Verify that the Cisco Discovery Protocol driver status is "Started."

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCma02991

Cisco Discovery Protocol causes some machines to blue screen

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods: