Recommendation: plan disk size before formatting
While deploying Cisco Catalyst 8000V instances, extra disk space is added after the basic system partitions are allocated under the /bootflash partition. If you need to increase the disk size, you must reinstall the instances to realize more usable disk space. The disk for Cisco Catalyst 8000V can be expanded at any time in the hypervisor; however, after the disk is formatted, the Cisco Catalyst 8000V cannot take the additional space.
-
Extra disk space is added after the basic system partitions are allocated under the /bootflash partition.
-
Hypervisor expansion alone does not increase usable space after formatting; reinstall the instance to realize a larger disk size.
Recommendation: configure disk parameters and attach the secondary disk during deployment
Configure the recommended parameters from Cisco Integrated Controller Manager (IMC) before installing the hypervisor because some settings may require disk formatting. For deploying Cisco Catalyst 8000V on AWS, Azure, or GCP platforms, include a cloud-init configuration and attach the secondary disk during deployment.
-
Recommended disk parameters by cloud:
-
For information about deploying a Cisco Catalyst 8000V on different platforms, see these resources:
Applies when deploying instances and planning secondary disk capacity where resizing is considered after formatting.
Applies when configuring IMC settings and deploying on AWS, Microsoft Azure, or Google Cloud Platform with a secondary disk requirement.
Because extra disk space is allocated after the basic system partitions under /bootflash, the instance cannot use additional space after formatting without reinstallation.
Configuring IMC settings before hypervisor installation prevents reformatting, and using the recommended disk types and sizes aligns performance and capacity with provider capabilities.
You avoid reinstallation and ensure that usable disk capacity meets requirements by planning the disk size before deployment and formatting.
Deployment completes with a correctly attached secondary disk and cloud-specific parameters that meet size and performance recommendations.
If you need more capacity after formatting, reinstall the instance to realize the larger disk size.
Use cloud-init to attach the secondary disk during deployment and follow the referenced platform guides for detailed procedures.