This article is designed to explain how to initially set up and access an MCP 2.0 Cloud environment. The basic building blocks of an MCP 2.0 Cloud environment are a Cloud Network Domain, VLAN, and Cloud Server. This article points you to the Introduction articles that explain these concepts as well as the articles that explain how to set them up. In addition, this articles provides links to explanations of other key MCP 2.0 features.
Deploy a Cloud Network Domain and VLAN
In order to get started, you will need to deploy a Cloud Network Domain and VLANs on which to deploy your Cloud Servers. Cloud Network Domains represent a "Virtual Private Data Center" within the Cloud infrastructure. Within this environment, you will deploy VLANs with user-defined private IPv4 address space and a system-defined IPv6 space. The ability to define the private IPv4 space and routing is a key feature of MCP 2.0 locations. The private IPv4 space is routable within the Cloud Network Domain but is not routable outside a given Cloud Network Domain. This means that you can deploy multiple Cloud Network Domains with overlapping IPv4 addresses without having to worry about IP collisions.
There are different types of Cloud Network Domains, each of which has different usage-based pricing structures. See Introduction to Cloud Network Domains and VLANs for a detailed explanation of the capabilities of each type.
These Introduction articles that can help you understand Network Domains, VLANs, routing and IP addressing in the MCP 2.0 environment:
- Introduction to Cloud Network Domains and VLANs
- Introduction to Routing, Network Domain Static Routes, and SNAT in MCP 2.0 Locations
- Introduction to IP Addressing in MCP 2.0
For details on creating, managing Network Domains, see:
- How to Deploy a Network Domain in a MCP 2.0 Data Center Location
- How to View and Manage a Network Domain in a MCP 2.0 Data Center
For details on creating and managing VLANs, see:
- How to Deploy a VLAN on a Network Domain in an MCP 2.0 Data Center
- How to View, Edit, or Delete a VLAN in a MCP 2.0 Data Center location
- How to Expand a VLAN on a Network Domain in a MCP 2.0 Data Center
All Cloud Network Domains include Firewall Rule capabilities that allow you to regulate both IPv4 and IPv6 traffic in and out of the Network Domain as well as to traffic between VLAN's within the Network Domain. As a general rule, traffic within a VLAN or outbound to the Public Internet is allowed, but any other traffic will require a firewall rule in place to allow it.
For more details on default IP traffic behavior and how firewall rules apply to it, we strongly recommend reviewing Introduction to Firewall Rules for Cloud Network Domains in MCP 2.0.
For details on creating and managing firewall rules, see:
Deploy a Cloud Server
Cloud Servers in MCP 2.0 locations can have one or more NICs, each of which can be connected to a separate VLAN. Each Cloud Server can have up to 10 NICs, each of which needs to have assigned its own private IPv4 and IPv6 from the IP space associated with the VLAN to which it's connected. Users can choose the private IPv4 address from the available pool in the NIC but the IPv6 address is assigned by the system by default.
On provisioning of a Cloud Server, users must define a "Primary NIC" for the Cloud Server. This NIC must remain attached to the VLAN for the life of the server and cannot be removed unless the Cloud Server is deleted. CloudControl uses this NIC for services such as Cloud Backup. All other NICs are designated "secondary NICs" and can be added or removed from the Cloud Server. However, changes to the NIC after the initial deployment remove the virtual NIC from the server but do not update the Guest OS of the change. Users will need to configure the Guest OS to deal with additional or removed NIC's after performing the action in CloudControl.
Unlike many Cloud platforms, MCP 2.0 will allow you to specify specific amounts of CPU, RAM, and local storage. CPU performance can vary based on the "CPU Speed" of the virtual CPU presented to the server. Local storage on Cloud Servers is presented using virtual disks attached to the Cloud Server that are visible within the Guest OS. Each disk can have different performance characteristics based on the "Disk Speed" chosen for the "disk".
Please review these Introduction articles that can help you understand more details about these concepts:
- Introduction to Cloud Servers
- Introduction to Cloud Server Provisioning, OS Customization, and Best Practices
- Introduction to CPU Speeds (vCPU Classes)
- Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds
For details on creating and managing Cloud Servers in MCP 2.0, see:
- How to Deploy a Cloud Server from a Guest OS Customization Image
- How to Deploy a Cloud Server from a Non-Guest OS Customization Image
- How to Manage a Cloud Server
- How to Add an Additional NIC to a Cloud Server
- How to Remove a NIC from a Cloud Server
- How to Add Additional Local Storage (Disk) to a Cloud Server
Client-to Site VPN Access
In order to securely access your Cloud environment, you can connect to it via Virtual Private Network (VPN) from your device.
For details on how to connect to your environment via VPN, see:
The Console Access feature allows you to troubleshoot your Cloud Server if an OS or VM Network failure occurs. Using this feature, you will be able to Console into your server to address issues which may render the Cloud Server unreachable via RDP or SSH.
For details on how to gain Console access, see:
Cloud Server Monitoring
The Monitoring feature allows you to establish continuous monitoring of a server from within the hypervisor. For an overview on this optional service, see:
Cloud Server Snapshots
The Snapshots feature allows you to make copies of your Cloud Server as of a specific point in time. For an overview on this optional service, see:
DRS for Cloud
The DRS for Cloud feature allows you to continuously replicate a group of Cloud Servers and then restore them as of a specific point in time. For an overview on this feature, see:
The Security Groups feature allows you to control IP traffic within a VLAN, allow you to prevent NICs attached to the same VLAN from communicating with each other. For an overview on this feature, see:
Every Organization has a Primary Administrator user who has the ability to handle all administrative functions for the Organization. The Primary Administrator can provision Sub-Administrator users with a subset of user Roles, to allow them to control various aspects of the environment. See:
- How to Create a Sub-Administrator using the CloudControl UI
- How to Manage the Primary Administrator User and other Sub-Administrators as the Primary Administrator