Provides an overview of how Cloud Server NIC functions work in MCP 2.0
For MCP 1.0 specifics, please see Introduction to Cloud Server NICs in MCP 1.0
In MCP 2.0, each Cloud Server can have one to ten virtual NICs. Each NIC must be associated with a different VLAN within the Cloud Network Domain. You cannot deploy multiple NICs for a single Cloud Server onto the same VLAN. Each NIC has a unique MAC address so that you can positively identify the NIC within the Guest Operating System. Each NIC must be assigned both a "private" IPv4 address and an IPv6 address from within the IP ranges supported by the VLAN.
- Deploying a Server from a Non-Guest OS Customization Image as described in How to Deploy a Cloud Server from a Non-Guest OS Customization Image
- Guest OS Customization deployments require the server to be deployed with all NICs in a connected state. The Guest OS Customization method also requires unique IP addresses so IP conflicts are unlikely.
- Adding a NIC as described in How to Add an Additional NIC to a Cloud Server
- Creating a Cloud Server from a Snapshot as described in How to Create a "Snapshot Preview" Cloud Server from a Successful Snapshot
|Content by Label|