210-065 · Question #259
A new Cisco DX650 is not registering in the Cisco Communications Manager running version 9.1.2. The latest device package and firmware was uploaded on all Cisco Communications Manager servers in the…
The correct answer is A. A cluster-wide reboot is needed to enable the functionality. After uploading a new device package to CUCM, a cluster-wide restart is required for all services to load the new device definitions before the DX650 can register.
Question
A new Cisco DX650 is not registering in the Cisco Communications Manager running version 9.1.2. The latest device package and firmware was uploaded on all Cisco Communications Manager servers in the cluster. What is most likely the cause of this issue?
Options
- AA cluster-wide reboot is needed to enable the functionality.
- BYou must restart the TFTP server.
- CThe firmware in the Cisco Unified Communications Manager is incorrect.
- DThe software version in the Cisco Unified Communications Manager is incorrect.
How the community answered
(47 responses)- A74% (35)
- B13% (6)
- C4% (2)
- D9% (4)
Why each option
After uploading a new device package to CUCM, a cluster-wide restart is required for all services to load the new device definitions before the DX650 can register.
When a new device package is uploaded to CUCM, the CallManager and TFTP services on every node in the cluster must restart (requiring a cluster-wide reboot) to load the new device firmware and configuration templates into memory. Without this restart, CUCM will not recognize the DX650 device type and cannot serve the correct configuration files needed for registration.
Restarting only the TFTP server is insufficient because the CallManager service also must reload the device package definitions before the DX650 can successfully complete registration.
The firmware was explicitly stated to have been uploaded as the latest version, so an incorrect firmware file is not the cause of the failure.
The question states the correct device package and firmware were already uploaded, which addresses version support - the missing step is the required post-upload service restart, not a version incompatibility.
Concept tested: CUCM device package upload and cluster restart requirement
Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/compat/matrix/ucdevpkg.html
Topics
Community Discussion
No community discussion yet for this question.