12-12-2024 01:51 AM
Hello,
we would like to make an installation of a CUCM/CUP 15 cluster over WAN (2 sites), by using PCD.
Our goal is the following:
Is it possible? If yes, how can we configure the remote PCD as an external server for the local PCD for the CUCM/CUP installation?
TIA and regards.
12-12-2024 02:06 AM
That's possible, but there is a limitation for the remote NFS: it must be a Linux NFS. Windows NFS will never work with PCD. After a long discussion with Cisco, they released a bug ID (CSCwm92153) to update the documentation to mention this.
Once the remote site sets up the Linux NFS, PCD can use it during the installation of the remote site. The NFS must be added to the ESXi as a datastore, and on the PCD, configure the datastore as remote NFS.
The alternative I recommend in this case is a fresh install with data export, which will be quicker than PCD migration. Also, as far as I know, Cisco prefers this option.
12-12-2024 02:25 AM
Hello @Nithin Eluvathingal,
thanks for the information.
As mentioned before, the remote NFS that we would like to use is another PCD node (which is of course Linux-based), already added to the remote ESXi node as a NFS datastore.
The issue is that we do not know how to configure it as an external server for installation/migration tasks on the "real" PCD node (i.e., the one where we will configure the installation task).
We have tried, but we always receive errors, so we are doing something wrong in the configuration of this section:
Regards.
12-12-2024 02:39 AM
You can't use another PCD as the NFS. You need a Linux NFS mounted on the ESXi in the remote site. This ESXi datastore must then be added to the PCD as an NFS path in HQ.
Copy the files to both the HQ PCD and the remote NFS. During the task configurations, select the files accordingly so that the PCD will use the file location based on the node.
However, as I mentioned, a fresh install with data export is the best solution for your scenario.
Even though I'm a big fan of PCD, these days I rely heavily on fresh installs with data export."
12-12-2024 02:52 AM
Hello @Nithin Eluvathingal,
OK, let's suppose to have this Linux NFS and that we have mounted it on the remote ESXi node as a NFS datastore.
How can we add it as a NFS path on the PCD, in the section shown in the previous screenshot?
Thanks and regards.
12-12-2024 03:09 AM
If I recall correctly, these were the details I took from the email communication with TAC:
12-12-2024 03:13 AM
I faced some challenges with the Linux permissions, which prevented the PCD from adding it. I'm confused whether the IP address and credentials used were for the ESXi or the NFS. I have this VM in a shutdown state in my lab, and I can spin it up coming sunday to confirm. If you don't have time, you can give it a try and come back if you face any issues.
12-12-2024 03:19 AM
If you search Google, you can find many videos on how to create an NFS using Linux. Create one, then search for how to add the NFS on ESXi as a datastore. Add that NFS on the ESXi, and then proceed with the PCD configurations.
I don't recall whether I used NFS 3 or NFS 4 when adding the NFS drive as a datastore on the ESXi. I need to access my lab, which I can do only on Sunday. If I can access it during the weekend, I will confirm it.
To avoid all such complications, I have started using the fresh install with data export option
12-12-2024 04:10 AM
Hello @Nithin Eluvathingal,
how do you manage the registration of the phones (and the other devices) on the CUCM nodes when you use the fresh install with data import option?
I mean, at a certain point during the migration, you have some CUCM nodes with the old version and other CUCM nodes with the new version, but they can't "talk" each other, and the same goes for the phones, based on the node on which they are registered.
A similar issue is valid for the CUCM IM&P nodes and the Jabber clients (related to the IM&P features).
So, how do you manage this issue?
Regards.
12-12-2024 04:39 AM
You must be performing the migration during the maintenance window. The phones will re-register. PCD and fresh install with data export are similar: one automates the process with minimal intervention from our end, while the other requires manual intervention but takes less time.
When doing the fresh install with data export, build the publisher first, then the subscribers. The phones will re-register based on the CM group configuration. If all the phones register with the subscriber, installing the publisher will not restart the phones. During the subscriber installation, the phones will fall back to the publisher, and once the subscriber is up, the phones will register back with the subscriber.
I haven't spent time checking the presence status during the migration so not sure about the behavior when migrating the IMP.
This is also what happens when using PCD
12-12-2024 10:07 AM
Why would one do a data export when installing a new system. Where did you get that the OP is asking about a migration with PCD? As I read it he/she is asking about how to install a new system.
12-12-2024 10:21 AM - edited 12-12-2024 10:22 AM
Thanks, @Roger Kallberg , for pointing that out. even I'm not sure where that came from. I was replying to the OP as it was migrations, probably because I've been focused on migrations for the past one years and haven't done any new deployments. That might be why I responded as if it were a migration.
@raziel1978kain Fresh install with data export is an option if you are migrating. This option is applicable only if you are migrating to version 15 and not a fresh installation.
If it's a fresh installation, make use of the PCD remote NFS option for the remote site and the local NFS for the HQ site. Alternatively, you can consider the AFG options.
https://www.cisco.com/c/en/us/applicat/content/cuc-afg/index.html
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