You responded to an almost 3 year old conversation which covers currently unsupported software versions. The documentation is mentioned earlier in the discussion, and there are multiple topics covers, so 'the same requirement' is probably not what you want. Unless there is no other option, I would never recommend the use of morph-vm, but instead deploy a fresh VM with the correct specifications and then restore your configuration on there.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Feb 18, 2025 07:08 AM
From: toopaki
Subject: ClearPass system morph-vm
@jwilson, Do you have a guide for this conversion you made (list of steps and outcomes), I have same requirement, I want to see how this gets migrated?
Original Message:
Sent: Apr 20, 2022 01:09 PM
From: jwilson4
Subject: ClearPass system morph-vm
Yeah that makes sense.
Thanks again for your help, my publisher and standby-publishers are now C3000V's.
------------------------------
Jesse Wilson
Original Message:
Sent: Apr 20, 2022 12:25 PM
From: Dustin Burns
Subject: ClearPass system morph-vm
Yes, you just never want to delete SCSI 0:0. You may want to open a TAC case and have them assist with this.
------------------------------
Dustin Burns
Lead Mobility Engineer @Worldcom Exchange, Inc.
ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022
If my post was useful accept solution and/or give kudos
Original Message:
Sent: Apr 20, 2022 12:23 PM
From: Jesse Wilson
Subject: ClearPass system morph-vm
Thanks
The part about deleting the old partition isn't in that link that is good information to have! Thank you
------------------------------
Jesse Wilson
Original Message:
Sent: Apr 20, 2022 12:14 PM
From: Dustin Burns
Subject: ClearPass system morph-vm
The system will migrate the data to the new disk. The disk gets partitioned, and the capabilities/label get assigned based on the resources of the disk, CPU, and memory. You will end up getting rid of the old drive once it is migrated to the new 1,800 Gb disk.
See here for more information on the process: https://www.arubanetworks.com/techdocs/ClearPass/6.9/InstallingOnVM_6.9_TechNote/Content/InstallOnVM_6.8/Morphing_ESXi.htm
------------------------------
Dustin Burns
Lead Mobility Engineer @Worldcom Exchange, Inc.
ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022
If my post was useful accept solution and/or give kudos
Original Message:
Sent: Apr 20, 2022 12:00 PM
From: Jesse Wilson
Subject: ClearPass system morph-vm
Trying to understand something that TAC is telling me. I was brought on to my current employer after the initial ClearPass cluster had already been built. It consist of 8 nodes that are all C2000Vs. I would like to morph the publisher and standby publisher to C3000V's because my projected overall authentication total through out the network will be about 12,500 (however we are experiencing explosive growth and that could double in the next 5 years) I have been told by TAC that in order to properly morph to the C3000V on my publisher and standby-publisher I need to add a third disk of 1800 GB, which would bring my total disk space to 2800 GB which is way over what the guides are telling me. I have multiple questions that I am still waiting on TAC to answer but I wanted to post to the community to see if I could gain any insights here.
Questions:
1) Why can't I just expand the second disk that was assigned (the one that is already 1000 GB) ?
note: I only aske because I already did this that is why I have contacted TAC I am receiving this error
2) If I can't just expand the second disk shouldn't the third disk just be 800 GB and not 1800 GB?
------------------------------
Jesse Wilson
------------------------------