Configuration Modifications on Remaining Nodes in Cisco Unified CM Cluster | CCIE Collaboration Exam

CCIE Collaboration Exam: Configuration Modifications on Remaining Nodes in Cisco Unified CM Cluster

Prev Question Next Question

Question

The Cisco Unified CM 9.0 publisher server in a five-node cluster failed to boot after a power outage.

Which four configuration modifications can still be made on the remaining nodes? (Choose four.)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E. F. G.

AEGH.

In a Cisco Unified Communications Manager (CUCM) cluster, the publisher server is responsible for storing the configuration and database information for the entire cluster. In case of a failure of the publisher server, the other nodes in the cluster can still function, but some changes may be restricted due to the lack of access to the centralized database.

The following configuration modifications can still be made on the remaining nodes of the CUCM cluster:

A. Call Forward All: This feature allows users to redirect incoming calls to another phone or voicemail box. This configuration can be modified on any phone device in the cluster, regardless of the server's availability.

B. Device Security Profile: Device security profiles can be used to enforce security policies for devices registered with CUCM, such as IP phones and softphones. These profiles can be modified on any device in the cluster, regardless of the server's availability.

C. PIN Reset: PIN reset allows users to reset their PIN (Personal Identification Number) for accessing voicemail and other features. This configuration can be modified on any phone device in the cluster, regardless of the server's availability.

D. Add a new DN: Adding a new Directory Number (DN) to a phone device can be done on any server in the cluster, but it may require a restart of the device.

E. Extension Mobility Login: Extension Mobility allows users to log in to any phone device in the cluster and use their personal settings and configuration. This configuration can be modified on any phone device in the cluster, regardless of the server's availability.

F. Busy Trigger: Busy trigger determines how many calls a phone device can handle simultaneously. This configuration can be modified on any phone device in the cluster, regardless of the server's availability.

G. Message Waiting Indication: Message Waiting Indication (MWI) allows users to see if they have new voicemail messages waiting. This configuration can be modified on any phone device in the cluster, regardless of the server's availability.

H. Device Mobility: Device Mobility allows users to move between different locations or subnets and still use their personal settings and configuration. This configuration can be modified on any phone device in the cluster, regardless of the server's availability.

In summary, configuration changes that rely on the centralized database and configuration, such as adding new devices or modifying the system-level configuration, may not be possible during a publisher server outage. However, device-level configuration changes such as call forwarding, PIN reset, and security profiles can still be modified on any device in the cluster, regardless of the server's availability.