cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
500
Views
5
Helpful
3
Replies

Same Publisher version ... different CLI command options

Mick35
Level 1
Level 1

Hello,

 

I got 2 Clusters (exactly the same version ==> 12.5.1).

 

Using the CLI command "utils disaster_recovery  , I have the following completion options on Publisher Cluster #1 :

admin:utils disaster_recovery

      utils disaster_recovery backup*

      utils disaster_recovery cancel_backup

      utils disaster_recovery device*

      utils disaster_recovery estimate_tar_size

      utils disaster_recovery history

      utils disaster_recovery jschLogs

      utils disaster_recovery prepare*

      utils disaster_recovery restore*

      utils disaster_recovery schedule*

      utils disaster_recovery show_backupfiles

      utils disaster_recovery show_registration

      utils disaster_recovery status

 

And on the second Cluster (from publisher) I have :

admin:utils disaster_recovery
utils disaster_recovery backup*
utils disaster_recovery cancel_backup
utils disaster_recovery device*
utils disaster_recovery estimate_tar_size
utils disaster_recovery history
utils disaster_recovery jschLogs
utils disaster_recovery restore*
utils disaster_recovery schedule*
utils disaster_recovery show_backupfiles
utils disaster_recovery show_registration
utils disaster_recovery show_tapeid
utils disaster_recovery status

 

Why do not I have same options ? Especially why do not I have "utils disaster_recovery prepare" on the first Publisher ?

1 Accepted Solution

Accepted Solutions

Mick35
Level 1
Level 1

Issue is now fixed.

To fix the issue, the workaround is to suppress the "cliCommands.xml" file (need root login access, means that you need to contact the TAC). Your next session (as "administrator" user) will re-create the "cliCommands.xml" file when starting CLI ... and then everything will be ok.

View solution in original post

3 Replies 3

b.winter
VIP
VIP

Hi,

 

for the first command utils disaster_recovery prepare*:

Have you already added any subscribers? I guess, this command is only visible, as long as it's a single-node cluster (so only the pub).

 

Unbenannt.JPG

 

for the second command utils disaster_recovery show_tapeid:

This command is not mentioned in the CLI reference guide at all.

 

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/cli_ref/12_5_1/cucm_b_cli-reference-guide-1251/cucm_b_cli-reference-guide-1251_chapter_01001.html#reference_CDF5A7E0EB28682CB8C862DA04DBD56C

 

Mick35
Level 1
Level 1

Thanks for your answer.

 

In fact, my Clusters already exist (1 Pub and 8 Sub in each Cluster).

 

All nodes are also authenticated. "callmanager DBSub authenticated" when I tape "show network cluster".

Mick35
Level 1
Level 1

Issue is now fixed.

To fix the issue, the workaround is to suppress the "cliCommands.xml" file (need root login access, means that you need to contact the TAC). Your next session (as "administrator" user) will re-create the "cliCommands.xml" file when starting CLI ... and then everything will be ok.