I know its an old thread, but

I know its an old thread, but wanted to Thank you. I am rolling out a new CUCM environment. I was able to confirm my CUCM security passcode because I was able to add an IMP server. But we're going to add a second CUC server later, so I wanted to confirm the CUC security code before starting to configure it. I found this article, and it worked like a charm.

Again used the command set

Again used the command set password user security and entered some other word as password, this time also it accepted the password and prompted me to enter new password.

When it prompted to enter the new password, did you enter the new password or left the process at that time. I believe you did not because if you had then only system would have checked the password that you entered first time after issuing the set password user security command and should have issued something like below since you entered the wrong password intentionally

Continue (y/n)?y

Please wait...

The old password did not match.

Secondly, I do not understand why would someone play with it like this in a real environment unless they are facing one of the below issues:

1) If you are going to add the second server to the existing cluster. During this, system will check if the Security Password matches with the primary node or not. If not, then the DB replication will not come up at all

2) If the DRS backup was taken of a UCCX system or any other UC system for that matter, then while doing the restore system will ask you to enter the Security Password and if it does not match with the one that was there while the backup was taken then the restore will not go through.

BTW, there is a Password Guess utility available in the platform config file that can be accessed only by TAC using the root of your system if you really want to test your Security Password. However, I would definitely not take the risk of playing with Security Password in a production environment using CLI unless I am facing one of the above issues as mentioned above.

Hi Deepak,

Hi Deepak,

Thanks for the response.

"If the DRS backup was taken of a UCCX system or any other UC system for that matter, then while doing the restore system will ask you to enter the Security Password and if it does not match with the one that was there while the backup was taken then the restore will not go through."

I have been provided with a password, but no one knows that is correct or not.

Incase if it is not correct, the cluster is running at risk as backup can't be restored in DR situation.so wanted to validate the password.

Every node in a cluster will

Every node in a cluster will use the same password, so you are able to test it from any server in that cluster. But we need to define a cluster based on what you were asking.

Unity and CUCM are two completely separate entities. Even though there is a high likelihood that whoever built your system used the same passwords, they didnt necessarily have to. Then on to Presence, it depends on the version. If its 9 and below, Presence was also its own separate cluster. In version 10 and above, it is part of the CUCM cluster.

Re: Jamie,There is a way to

This does work..first time wrong password, second time right password. I used cisco123 as the new password both times.

admin:set password user security
Please enter the old password: *************
Please enter the new password: **
Control-C pressed
admin:set password user security
Please enter the old password: *************
Please enter the new password: ********
Reenter new password to confirm: ********
WARNING:
The Disaster Recovery System is dependent on this security password you are attempting to change.
If you need to use any of the older backup archive to restore this system, you need to remember the
older security password. To avoid this scenario, we recommend you to conduct a DRS Backup of your
system/cluster immediately after this password change.
Please make sure that the security password on the publisher is changed first.
The security password needs to be the same on all cluster nodes,
or the publisher and subscriber(s) will not communicate.
After changing the security password on a cluster node, please restart that node.
Continue (y/n)?y
Please wait...
The old password did not match.

###########################################################################admin:set password user security
Please enter the old password: *****************
Please enter the new password: ********
Reenter new password to confirm: ********
WARNING:
The Disaster Recovery System is dependent on this security password you are attempting to change.
If you need to use any of the older backup archive to restore this system, you need to remember the
older security password. To avoid this scenario, we recommend you to conduct a DRS Backup of your
system/cluster immediately after this password change.
Please make sure that the security password on the publisher is changed first.
The security password needs to be the same on all cluster nodes,
or the publisher and subscriber(s) will not communicate.
After changing the security password on a cluster node, please restart that node.
Continue (y/n)?y
Please wait...
BAD PASSWORD: it is based on a dictionary word
admin:

Re: Jamie,There is a way to

Cisco Webex Calling is a cloud service that offers enterprise-grade calling features delivered from the Cisco Webex cloud. This platform is part of the complete Webex collaboration suite that serves the calling, messaging, meeting, team collaboration and...
view more

Cisco SX20 camera moving left right and shaking continuously. We have factory reset the devices still it is a same problem. Even change the camera of working devices with issue devices still the problem.Now the software version of the device is&nbsp...
view more

Hello Experts. We would like to write macro to create a button to switch sources during a call. The only possible view today is content on upside and participants down. This is not the best experience for user's perspective. Someone, could ...
view more

Joining Webex Meetings just got significantly faster – with fewer clicks and less time that’s needed to get into your meetings on desktop and mobile apps.
With our email template simplification, you can enjoy a sin...
view more