Cisco 3500 MCU - Resolving MCU Failure to Register with the Gatekeeper; Resolving Front Panel LED Issues

1-2
Troubleshooting Guide for Cisco Unified Videoconferencing 3500 MCU Release 5.1
OL-12051-01
Chapter 1 Troubleshooting the Cisco Unified Videoconferencing 3500 MCU
Resolving MCU Failure to Register with the Gatekeeper
Resolving MCU Failure to Register with the Gatekeeper
This section describes what to do if the MCU fails to register with the Cisco IOS H.323 Gatekeeper.
Resolving Front Panel LED Issues
This section describes what to do if MCU module front panel LEDs are off at all times, including during
the power off, power on cycle.
Possible Causes Verification Steps
The gatekeeper address is set incorrectly. Verify the Gatekeeper IP address settings.
TCP/IP setup issue.
• Verify that the MCU is assigned a unique IP
address.
• Verify that the subnet mask and default
gateway subnet mask are set correctly.
LAN or cable problem
• Verify the switch port settings.
• Verify that the Ethernet cable is straight
through.
• Try another Ethernet cable.
The MCU cannot register to a Cisco MCM. The
Cisco MCM may not understand the syntax of the
label “MCU”.
Change the registration name of the MCU to
“GW” in the MCU Advanced Commands window.
Possible Causes Verification Steps
Power supply problem
• Make sure that the power supply LED is
green.
• Check the AC cable and fuse.
The MCU module is not inserted correctly in the
Cisco Unified Videoconferencing 3545 chassis, or
a back plane pin is bent.
• Open the telecom latch screws and extract the
MCU module from its slot.
• Verify that there are no bent pins on the back
plane (using a flashlight, if necessary).
• Re-insert the MCU module carefully closing
the latches.