About increase the disk size for intersight pva

[NeoChen722593]

Hi All,

 After upgrading the Intersight PVA from 1.0.9-590 to 1.0.9-615,
I got an alarm about "minimum disk size requirements for Intersight Virtual Appliance have changed."
It showed I have to increase the disk size before upgrading to the next release.
So how do I increase the disk size? What steps should I take?

I read the document, it seems that a new intersight needs to be installed new one and restore the backup file.

This approach is a bit exaggerated. Is this the only way?

Will the action of reinstalling and restore the backup file have an impact on the existing environment?

Thanks.
https://www.cisco.com/c/en/us/td/docs/unified_computing/Intersight/b_Cisco_Intersight_Appliance_Getting_Started_Guide/m_appliance_overview.html#vm-resource-requirements-for-existing-deployments>

[Brian Morrissey]

What hypervisor are you using? If it's just vsphere and you don't have any snapshots then you can just:

"shut down the VM, change the CPU, RAM, and disk size as required, and restart the VM."

The changing of the disk sizes and or cpu/ram would be on the VM settings in vSphere just make sure it matches the recommendations in the documentation for the appropriate deployment size.

The backup/restore is also another option but more work, in the case of Intersight Managed Mode domains the impact would be limited manageability through the FI device console until the restored PVA is brought online but the dataplane should continue to function uninterrupted.

[NeoChen722593]

Hi @Brian Morrissey 

1. So what you mean is, I just need to shut down and manually adjust the CPU and memory, as well as the size of the disk to Medium leve, and it's okay?

 If I make adjustments, how do I verify that the resources of Intersight have changed?

Because I opened a case, support replied that as long as the CPU and mem are adjusted, the disk will automatically adjust, but it will take 3-4 hours.

2. May I ask what would happen if resources are not adjusted? The customer has reported that they are currently using less than 20 servers and are only used to manage the servers without using other functions,

What would be the impact if the current small size is not adjusted to medium size? 

or can it keep cpu and memory size to small, just adjust disk to minimum size?

3. May I ask how I can view the current usage of my CPU, Memory, and Disk on Intersight?

[Brian Morrissey]

Hi @NeoChen722593 ,

1. The disk won't be able to expand unless the hypervisor presents more storage for the VM to expand with. The banner should clear once the expansion has been complete, if you ssh into the appliance and look at the status I believe it says something along the lines of "upgrading to medium etc" while its in progress.

2. If the disk size is not adjusted future updates will fail to apply

3. The realtime usage I think can only be seen in the TAC debug shell or techsupport bundle, however it should throw an alarm if there are issues with the CPU/Memory/Disk utilization (https://www.cisco.com/c/en/us/td/docs/unified_computing/Intersight/b_Cisco_Intersight_Appliance_Getting_Started_Guide/m_settings_dashboard.html)
.

[jfweber]

Hi @Brian Morrissey ,
We have the same issue, but with an RHV/KVM/QCOW2 Intersight Private Virtual Appliance. We tried to poweroff the VM, extend the disks that need more space as mentionned in https://www.cisco.com/c/en/us/td/docs/unified_computing/Intersight/b_Cisco_Intersight_Appliance_Getting_Started_Guide/m_appliance_overview.html.
But the banner message is still present and the upgrade to v1.0.9-631 fails at 60% of the process.
Is there any extra action to be done with KVM version of the PVA ?

[Brian Morrissey]

Hi @jfweber ,

I'd recommend having TAC take a look at the appliance techsupport bundle to see if its detecting the disk change from the hypervisor and if its running into any errors when it tries to run the playbook to expand.  I know at one point there was a blurb about Hyper-V/KVM requiring a backup/restore to alter disk sizes but I think that was removed about a year or so ago, are you currently running a relatively newer version or using something older when trying to expand the disks?