Starting with Release 10.0.0, Threat Defense Virtual supports dynamic disk expansion across all virtual platforms. This feature helps optimize disk utilization on high-end systems (for example, systems with 64 CPU / 128 GB RAM) where large core dump files, approximately 16 GB in size, previously caused disk space alerts.

Note	Before resizing the disk on Threat Defense Virtual, you must first increase the disk size from the cloud console.

• Default Disk Size: New Threat Defense Virtual deployments use a 100 GB virtual disk, increased from the previous 48.5 GB size.

• Expansion Range: Disk size can be expanded up to 500 GB as per requirement.

• Supported Scenarios: Disk expansion is supported on both new and upgraded Threat Defense Virtual instances.

• After the first boot, users can re-size the disk using the CLI command:

  resize_disk -s <total_size>
  

  Example: resize_disk -s 500

  Note	Disk resizing is not supported during the first boot. If downgraded after resizing, the disk size remains expanded (does not revert to 48.5 GB).

Note	Disk expansion up to 500 GB is supported from version 10.0.0 onwards.

Note	Threat Defense Virtual does not support additional virtual hard disks. Attaching extra disks may result in slow boot performance.

Starting with Release 10.0.0, Threat Defense Virtual uses a standardized interface naming convention across all virtual platforms.

Previous naming convention: GigabitEthernet0/x or TenGigabitEthernet0/x

New naming convention: Ethernet0/x

• Configuration Option:

  To revert to the previous naming format, use the following parameter in the Day 0 configuration:

  "IfNamingConvention": "Old"   // for legacy naming
  "IfNamingConvention": "New"   // for standardized naming

• Scope: This change applies to new deployments only.

• Interface names displayed in the management console, CLI, and Management Center UI follow the new naming format.

  Devices that are upgraded to Release 10.0.0 retain their original interface names to ensure configuration consistency.

Starting with version 10.0.0, Threat Defense Virtual supports deployment with three interfaces (3NIC) across all virtual platforms. Day 0 configuration should include the key-value pair Diagnostic: OFF.

• You can control the inclusion of the diagnostic interface during deployment using the following Day 0 configuration parameter:

  "Diagnostic": "ON"   // Adds the diagnostic interface  
  "Diagnostic": "OFF"  // Removes the diagnostic interface

  Note	This is applicable to new deployments only.

• Existing deployments that are upgraded to Release 10.0.0 retain their current diagnostic interface configuration.

Day0 configuration for Threat Defense Virtual with three NICs

{
	"AdminPassword": "E28@2OiUrhx!",
	"Hostname": "ciscoftdv",
	"FirewallMode": "routed",
	"ManageLocally": "No",
	"Diagnostic": "OFF"
}