// Module included in the following assemblies:
//
// * virt/vm_networking/virt-hot-swap-vm-secondary-network.adoc

:_mod-docs-content-type: PROCEDURE
[id="virt-hot-swapping-vm-secondary-network-web-console_{context}"]
= Hot swapping a virtual machine secondary network by using the web console

[role="_abstract"]
You can hot swap the secondary network of a running virtual machine (VM) by using the {product-title} web console. Hot swapping the secondary network preserves the workload and avoids the need for a VM reboot.

.Prerequisites

* The VM is running and is live migratable.
* The target `NetworkAttachmentDefinition` object exists in the same namespace as the VM. If you created a `ClusterUserDefinedNetwork` object, verify that the cluster user-defined network controller has created the corresponding `NetworkAttachmentDefinition` object.

.Procedure

. Navigate to *Virtualization* -> *VirtualMachines* in the web console.
. Click a running VM to view the *VirtualMachine details* page.
. Click the *Configuration* tab and then click the *Network interfaces* tab.
. Click the Options menu {kebab} beside the network interface that you want to modify and select *Edit*.
. Select the target network from the *Network* list.
. Click *Save*.
+
The network interface row displays a *Pending* label. A warning banner indicates that the VM has pending network changes. The pending changes are applied during the next live migration or reboot.

.Verification

. On the *VirtualMachine details* page, click the *Diagnostics* tab.
. Check the *Status conditions* table and verify that the `MigrationRequired` condition is listed with the reason `AutoMigrationDueToLiveUpdate`.
+
After the live migration completes, the `MigrationRequired` condition disappears and the *Pending* label is removed from the network interface.
