diff --git a/docs/en-US/add-remove-nic-ui.xml b/docs/en-US/add-remove-nic-ui.xml
new file mode 100644
index 00000000000..777ac7919fa
--- /dev/null
+++ b/docs/en-US/add-remove-nic-ui.xml
@@ -0,0 +1,147 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+
+ Reconfiguring Physical Networks in VMs
+ &PRODUCT; provides you the ability to move VMs between networks and reconfigure a VM's
+ network. You can remove a VM from a physical network and add to a new physical network. You can
+ also change the default physical network of a virtual machine. With this functionality, hybrid
+ or traditional server loads can be accommodated with ease.
+ This feature is supported on XenServer and KVM hypervisors.
+
+ Adding a Physical Network
+
+
+ Log in to the CloudPlatform UI as an administrator or end user.
+
+
+ In the left navigation, click Instances.
+
+
+ Choose the VM that you want to work with.
+
+
+ Click the NICs tab.
+
+
+ Click Add network to VM.
+ The Add network to VM dialog is displayed.
+
+
+ In the drop-down list, select the network that you would like to add this VM
+ to.
+ A new NIC is added for this network. You can view the following details in the NICs
+ page:
+
+
+ ID
+
+
+ Network Name
+
+
+ Type
+
+
+ IP Address
+
+
+ Gateway
+
+
+ Netmask
+
+
+ Is default
+
+
+ CIDR (for IPv6)
+
+
+
+
+
+
+ Removing a Physical Network
+
+
+ Log in to the CloudPlatform UI as an administrator or end user.
+
+
+ In the left navigation, click Instances.
+
+
+ Choose the VM that you want to work with.
+
+
+ Click the NICs tab.
+
+
+ Locate the NIC you want to remove.
+
+
+ Click Remove NIC button.
+
+
+
+
+ remove-nic.png: button to remove a NIC
+
+
+
+
+ Click Yes to confirm.
+
+
+
+
+ Selecting the Default Physical Network
+
+
+ Log in to the CloudPlatform UI as an administrator or end user.
+
+
+ In the left navigation, click Instances.
+
+
+ Choose the VM that you want to work with.
+
+
+ Click the NICs tab.
+
+
+ Locate the NIC you want to work with.
+
+
+ Click the Set default NIC button.
+
+
+
+
+ set-default-nic.png: button to set a NIC as default one.
+
+
+
+
+ Click Yes to confirm.
+
+
+
+
diff --git a/docs/en-US/images/remove-nic.png b/docs/en-US/images/remove-nic.png
new file mode 100644
index 00000000000..27145cebbc7
Binary files /dev/null and b/docs/en-US/images/remove-nic.png differ
diff --git a/docs/en-US/images/set-default-nic.png b/docs/en-US/images/set-default-nic.png
new file mode 100644
index 00000000000..f329aef4a25
Binary files /dev/null and b/docs/en-US/images/set-default-nic.png differ
diff --git a/docs/en-US/using-multiple-guest-networks.xml b/docs/en-US/using-multiple-guest-networks.xml
index 4e7da1e187f..cb7e9c73be3 100644
--- a/docs/en-US/using-multiple-guest-networks.xml
+++ b/docs/en-US/using-multiple-guest-networks.xml
@@ -28,5 +28,6 @@
Each VM has just one default network. The virtual router's DHCP reply will set the guest's default gateway as that for the default network. Multiple non-default networks may be added to a guest in addition to the single, required default network. The administrator can control which networks are available as the default network.
Additional networks can either be available to all accounts or be assigned to a specific account. Networks that are available to all accounts are zone-wide. Any user with access to the zone can create a VM with access to that network. These zone-wide networks provide little or no isolation between guests.Networks that are assigned to a specific account provide strong isolation.
+