01-02-2014 12:38 PM - edited 03-14-2019 12:56 PM
Hello,
we have a CUCCX 8.0.2.11005-20 cluster (that is, made by a Publisher and a Subscriber) over WAN.
Currently, we have the Publisher down due to a hardware failure.
But we need to make some modifications to the configuration (for example, to change the value of a parameter on an application).
The problem is that, when we try to apply the modifications, we receive this issue:
"Error while handling the request"
What's wrong? Is there a way to re-activate the ability to make the modifications when the CUCCX Publisher is down?
Thanks in advance for your help.
Best regards, and Happy New Year!
01-03-2014 01:37 AM
Hi,
until the UCCX Publisher is down, you do not have write access to the config database.
The status can be checked on the Cisco Unified CCX Serviceability web page: Tools > Data Store Control Center.
You can varify there, your subscriber has only read permission to the config database.
Best regards
Stanislav
01-03-2014 02:00 AM
Hello Stanislav,
OK, on "Tools > Datastore Control Center > Datastores", for "Cisco Unified CCX Config Datastore", I can see that "Write access" is set to "NO" for the Subscriber.
But on "Tools > Datastore Control Center > Replication Servers", I can read below that:
"Note: Any Configuration in Application Administration and Historical data on the Subscriber node would get over written, when CDS is enabled again."
What does it mean?
Furthermore, we have tried to restore the Publisher (by a fresh install and a DRS), but we have received this error:
What's wrong?
Regards.
01-03-2014 02:51 AM
Hi,
the mesage:
"Note: Any Configuration in Application Administration and Historical data on the Subscriber node would get over written, when CDS is enabled again." is the warning message by a replication reset betwenn publisher and subscriber.
By restoring DRS Backup, please check all requerements listed in the DRS admin guide for your CCX version.
There are listed the supported SFTP servers: Open SSH, Cygwin and Titan. With freeFTPD, there are problems with large backup files possible (I think > 1024 MByte).
Before restoring, you should hava a fresh installed CCX with exact the same version including SUs, node name, ip address and credentials, especially seurity password. I think, the ccxcomponent name depends on the ccx node name. When your new installed ccx system have a different node name or ip address from the old one, DRS backup will be probably unsuccessful.
All requerements for restoring a Publisher node in a HA environment are described in the CCX DRS admin guide.
regards
Stanislav
01-03-2014 03:02 AM
Hello Stanislav,
the guide states that:
"When the subscriber goes down and it is required to make configuration updates from the publisher, you can disable Config Datastore (CDS) and Historical Datastore (HDS) on the subscriber using Disable CDS and HDS icon or button. The database information for the cluster is displayed at the bottom of the window. Once the subscriber is up, you can enable CDS and HDS on the subscriber using the same toggle button."
But if it's the Publisher to be down (as in our scenario), could we use the same "Disable CDS and HDS" icon or button to make configuration updates from the Subscriber?
Regarding the DRS issue, we have used the same server (only the hard disk drives are different, because one of them had a hardware failure, and we have changed the other, too) and the same information (hostname, IP Address, ...) during the installation; in fact, the license MAC is the same. Furthermore, all the other requirements for DRS should be satisfied.
So, do you have other ideas about the DRS issue?
Regards.
01-03-2014 03:31 AM
Hi,
when the license MAC is the same, the new UCCX system should be configured as the old one. When also the system version is the same, the restore problem can be a corrupt backup file.
Which tool do you used be creating ccx backups? With Open SSH, Cygwin or Titan everything should be ok...
regards
01-03-2014 03:45 AM
Hello,
we have used FileZilla Server on a Linux server (fzSftp).
When we have checked the status of the last backup (by DSR webpage), before the hard disk drive failure, it was OK.
Furthermore, the largest file of that backup is about 400 MB, so I don't think it's a size issue...
Regards.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide