The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
Configuring Cisco Nexus 1000V InterCloud consists of the following steps.
Step 1 |
Adding a provider to Cisco Prime Network Services Controller. See Adding a Provider to Cisco Prime Network Services Controller |
Step 2 |
Uploading the infrastructure images to Cisco Prime Network Services Controller. See Uploading Cisco Nexus 1000V InterCloud Link Images to Cisco Prime Network Services Controller. |
Step 3 | Configuring an InterCloud device profile. |
Step 4 | Configuring a tunnel profile. |
Step 5 | Configuring a MAC address pool. |
Step 6 |
Adding a VM Manager. See Adding a VM Manager. |
Step 7 | Configuring an InterCloud link. |
Step 8 | Importing an InterCloud Agent image. |
Step 9 | Importing a VM image. |
Use this procedure to add a provider to Cisco Prime Network Services Controller .
Step 1 | Open a browser window. In the browser navigate to AWS EC2 console at http://aws.amazon.com/console/. |
Step 2 | Log in to your AWS EC2 account. |
Step 3 | Navigate to . |
Step 4 |
Navigate to . Note the Access Credentials and the Security Access Key. You will require this information to register your provider account in Cisco Prime Network Services Controller. |
Step 5 | Log in to Cisco Prime Network Services Controller. |
Step 6 | In the Cisco Prime Network Services Controller, navigate to . |
Step 7 | Click Create Provider Account to register the AWS provider account. The Create Provider Account window opens. |
Step 8 |
In the Create Provider Account window, enter the following:
|
Step 9 |
Click Ok to register the provider account. Once the provider is registered successfully, the default region will be populated to us-east-1. |
Step 10 |
To verify if the registration is successful, in the Cisco Prime Network Services Controller, navigate to . In the Provider Accounts window, the default region will be populated to us-east-1. |
Step 11 | To change the default region, in the Cisco Prime Network Services Controller, navigate to . |
Step 12 | In the AWS pane, choose a new default region from the Default Region drop-down menu and click Save . |
An InterCloud link includes two virtual gateways: one on the enterprise network and one on the cloud. The gateway on the enterprise network is referred to as the InterCloud Extender, and the one on the cloud is referred to as the InterCloud Switch.
Note |
You must install two infrastructure images: an InterCloud Extender image and an InterCloud Switch image. |
Step 1 | Download the InterCloud Extender and InterCloud Switch images from http://software.cisco.com/download/navigator.html?mdfid=284653427&i=rm and place them in a location that is accessible from Prime Network Services Controller server. |
Step 2 | Choose InterCloud Management > InterCloud Link > Infrastructure Images. |
Step 3 | Click Import Infrastructure Image. |
Step 4 |
In the Import Infrastructure Image dialog box:
|
An InterCloud device profile is a set of custom attributes and device policies that you can apply to an InterCloud extender or switch. You specify device profiles for the InterCloud extender and switch when you create an InterCloud link or by applying a different device profile to the InterCloud extender or switch after the link is deployed.
Prime Network Services Controller includes a default InterCloud device profile. You can edit the default InterCloud device profile, but you cannot delete it.
Step 1 | Choose InterCloud Management > InterCloud Policies > Tunnel Profiles. | ||||||||||
Step 2 | In the General tab, click Add Tunnel Profile. | ||||||||||
Step 3 |
In the Add Tunnel dialog box, enter the following information, then click OK:
|
Add a MAC address pool to allocate a group of MAC addresses to a Virtual Private Cloud.
Step 1 | Choose InterCloud Management > InterCloud Link > MAC Pools. |
Step 2 | Click Add MAC Address Pool. |
Step 3 |
Enter the following information, then click OK:
|
Adding a VM Manager to Prime Network Services Controller establishes a connection between the selected VM and Prime Network Services Controller and enables you to take advantage of other Prime Network Services Controller features, such as InterCloud Management.
A VM Manager extension file is required to establish a secure connection between the VM management software and Prime Network Services Controller. Export the VM Manager extension file by clicking Export vCenter Extension, and installing the file as a plugin on all VM management servers to which you want to connect.
Note |
If you use Internet Explorer, do one of the following to ensure that you can download the extension file:
|
For detailed information on configuring Prime Network Services Controller connectivity with the VM management software, see the Cisco Prime Network Services Controller 3.0 Quick Start Guide, available at http://www.cisco.com/en/US/products/ps11213/tsd_products_support_series_home.html.
Step 1 | Choose any of the following: | ||||||||||
Step 2 | Click Add VM Manager. | ||||||||||
Step 3 |
In the Add VM Manager dialog box, supply the following information, then click OK:
|
A Virtual Private Cloud (VPC) is a logical grouping of different cloud infrastructure components and resources that enable an enterprise to extend the private data center into one public cloud provider. Each VPC is associated with a Cloud Provider account and a MAC address pool. An InterCloud link is created in the context of a Virtual Private Cloud (VPC)and you create an InterCloud link by using a wizard.
Step 1 | Choose InterCloud Management > InterCloud Link > VPCs. | ||
Step 2 | Click Extend Network to Cloud. | ||
Step 3 |
In the Configure VPC screen, provide the information described in Configure VPC Screen, then click Next.
|
||
Step 4 | In the Configure InterCloud Link screen, provide the information described in Configure InterCloud Link Screen, then click Next. | ||
Step 5 |
In the InterCloud Extender screen, select the image to use for the InterCloud Extender, then click Next. Cisco Prime Network Services Controller automatically selects the data store to use for the InterCloud Extender instance. |
||
Step 6 | In the Select VM Placement screen, navigate to and select the VM to use for the InterCloud Extender instance, then click Next. | ||
Step 7 | In the Configure Properties screen, provide the information described in Configure Extender Properties Screen, then click Next. | ||
Step 8 | In the Configure Network Interfaces screen, provide the information described in Configure Extender Network Interfaces Screen, then click Next. | ||
Step 9 | In the InterCloud Switch screen, select the required InterCloud Switch image, then click Next. | ||
Step 10 | In the Configure Properties screen, provide the information described in Configure Switch Properties Screen, then click Next. | ||
Step 11 | In the Configure Network Interfaces screen, provide the information described in Configure Switch Network Interfaces Screen, then click Next. | ||
Step 12 | In the Configure Tunnel Profile screen, provide the information described in Configure Tunnel Profile Screen, then click Next. | ||
Step 13 | In the Summary screen: |
Field | Description |
---|---|
Name |
Virtual Private Cloud (VPC) name. |
Description |
Brief description. |
Provider Account |
|
Location |
Provider region in which to create the VPC. If the provider account selected in the previous field is already associated with a region, a check mark and the status Completed are displayed next to the drop-down list. |
MAC Pool |
|
Default VSM |
Default VSM to use for the VPC. |
Field | Description |
---|---|
InterCloud Link Name |
InterCloud link name. |
Description |
Brief description. |
VSM |
Virtual Supervisor Module (VSM) to use for the InterCloud link. This drop-down list is automatically populated with VSMs capable of supporting InterCloud services. |
High Availability |
Check the Enable HA check box to indicate that the InterCloud link is in active standby mode. Uncheck the check box to indicate that the InterCloud link is in standalone mode. If you check the check box, subsequent screens will require information for both the primary and secondary InterCloud Extenders and Switches. |
Field | Description |
---|---|
Primary Name |
InterCloud Extender name. |
Secondary Name |
(Displayed if high availability is enabled) Secondary InterCloud Extender name. |
Device Profile |
|
SSH User Name |
Username for SSH access (read-only). Default value is admin. |
SSH Password |
Password for SSH access. |
Confirm Password |
Confirming entry for SSH password. |
Field | Description |
---|---|
General Tab |
|
Primary Data Trunk Interface Port Profile |
Select the data trunk interface port profile to use for the InterCloud Extender. |
Secondary Data Trunk Interface Port Profile |
Displayed if you did not check the Same as Primary check box in the Select VM Placement screen. Select the data trunk interface port profile to use for the secondary InterCloud Extender. |
Management Interface |
|
Primary |
|
Port Profile |
Select the port profile to use for the primary InterCloud Extender management interface. |
IP Address |
IP address for the management interface. |
Netmask |
Management interface subnet mask. |
Gateway |
Management interface gateway IP address. |
Secondary The following fields are displayed only if high availability is enabled. |
|
Port Profile |
Displayed if you did not check the Same as Primary check box in the Select VM Placement screen. Select the port profile to use for the secondary InterCloud Extender management interface. |
IP Address |
IP address for the secondary management interface. |
Netmask |
Secondary management interface subnet mask. |
Gateway |
Secondary management interface gateway IP address. |
Advanced Tab |
|
External Tunnel Interface |
|
Primary The following fields are displayed if the Same as Management Interface check box is unchecked. |
|
Port Profile |
Port profile to use for the external tunnel interface. |
IP Address |
External tunnel interface IP address. |
Netmask |
Subnet mask to apply to the external tunnel interface IP address. |
Gateway |
IP address of the gateway for the external tunnel interface. |
Secondary The following fields are displayed if the Same as Management Interface check box is unchecked and high availability is enabled. |
|
Port Profile |
Port profile to use for the secondary external tunnel interface. |
IP Address |
Secondary external tunnel interface IP address. |
Netmask |
Subnet mask to apply to the secondary external tunnel interface IP address. |
Gateway |
IP address of the gateway for the secondary external tunnel interface. |
Internal |
|
Use Default Internal Interface |
|
Field | Description |
---|---|
Primary Name |
InterCloud Switch name. |
Secondary Name |
(Displayed if high availability is enabled for this link) Secondary InterCloud Switch name. |
Device Profile |
|
SSH User Name |
Username for SSH access (read-only). Default value is admin. |
SSH Password |
Password for SSH access. |
Confirm Password |
Confirming entry for SSH password. |
Field | Description |
---|---|
General Tab |
|
Port Profile |
From the drop-down list, choose the port profile to use for the InterCloud Switch management interface. |
Primary |
|
IP Address |
IP address for the management interface. |
Netmask |
Management interface subnet mask. |
Gateway |
Management interface gateway IP address. |
Secondary The following fields are displayed if high availability is enabled. |
|
IP Address |
IP address for the secondary management interface. |
Netmask |
Secondary management interface subnet mask. |
Gateway |
Gateway IP address for the secondary management interface. |
Advanced Tab |
|
Use Default Internal Interface |
Check the check box to use the default internal interface for the InterCloud Switch. Uncheck the check box to select a port profile for the tunnel trunk. |
Tunnel Trunk Port Profile |
Displayed if the Use Default Internal Interface check box is cleared. From the drop-down list, choose the tunnel trunk port profile. |
Field | Description |
---|---|
InterCloud Extender to InterCloud Switch |
|
InterCloud Switch to VM |
|
An InterCloud Agent image enables you to securely place a VM image, called a template, in the cloud. After the VM template is in place, you can create VM instances in the cloud.
The InterCloud Agent image that you choose must match your VM operating system. You can obtain InterCloud Agent images from http://www.cisco.com/go/services-controller. After you download an image, do not change the image filename.
Step 1 | Download the appropriate InterCloud Agent image for your VM operating system from http://www.cisco.com/go/services-controller. | ||||||||||||||||||
Step 2 | Choose InterCloud Management > InterCloud Link > InterCloud Agent Images. | ||||||||||||||||||
Step 3 | Click Import InterCloud Agent Image. | ||||||||||||||||||
Step 4 |
In the InterCloud Agent Image dialog box, provide the following information, then click OK:
|
After you import an InterCloud Agent image, you are ready to import a VM image. The imported image will be used to create a template on the cloud, which will then allow you to create VM instances from the template on the cloud.
Import the appropriate InterCloud Agent image for your VM operating system, as described in Importing an InterCloud Agent Image.
Step 1 | Choose InterCloud Management > Enterprise > VM Images. |
Step 2 | Click Import VM Image. |
Step 3 | In the Import VM Image dialog box, provide the information described in Import VM Image Dialog Box, then click OK. |
Field | Description |
---|---|
Name |
VM image name. |
Description |
VM image description. |
Format |
VM image format: AMI, ISO, or OVA. |
Properties The Properties area is not displayed for OVA images. |
|
Number of NICs |
(AMI images only) Number of NICs for the VM. The value in this field must match the value for the image being imported. |
OS |
(AMI images only) VM operating system: CommunityEnterprise OS (CentOS), Red Hat Enterprise Linux (RHEL), Windows, or Unknown. The value in this field must match the value for the image being imported. |
Architecture |
(AMI images only) VM architecture: 32-bit, 64-bit, or Unknown. The value in this field must match the value for the image being imported. |
Disk (GB) |
Amount of disk space (in gigabytes) for the VM. |
CPU Cores |
Number of CPU cores for the VM. |
Memory (MB) |
Amount of memory (in megabytes) for the VM. |
Import |
|
Protocol |
Protocol to use for the import operation: FTP, SCP, or SFTP. |
Hostname / IP Address |
Hostname or IP address of the remote host. |
User Name |
Account username on the remote host. |
Password |
Account password on the remote host. |
Remote File |
Remote filename, starting with a slash (/). |
After you establish an InterCloud link and download the required InterCloud Agent and VM images, you are ready to create VM templates in the cloud. After they are created, these VM templates are used to instantiate cloud VMs.
You can create VM templates in a cloud in the following ways:
Perform the following prerequisites on the Windows enterprise VM before creating cloud VM templates.
Use this procedure to create a template in a cloud from an existing VM image. The template is created in the specified VPC and can then be used to create VM instances in the cloud.
Step 1 | Choose InterCloud Management > Enterprise > VM Images > image. |
Step 2 | Click Create Template in Cloud. |
Step 3 | In the Infrastructure screen in the Create Template in Cloud Wizard, select the VPC in which the template is to reside, then click Next. |
Step 4 | In the Template Properties screen, provide the information described in Template Properties Screen, then click Next. |
Step 5 | In the Network Properties screen, optionally add a port profile to each NIC as follows, then click Next: |
Step 6 | In the Configure Application Parameters screen, provide the information described in Configure Application Parameters Screen for ISO Templates, then click Next. |
Step 7 | In the Summary and Apply screen, confirm that the information is accurate, then click Finish. |
Field | Description |
---|---|
Template Name |
Cloud template name. |
SSH User |
SSH account username. |
OS Information |
|
OS |
VM operating system (read-only): CommunityEnterprise OS (CentOS), Red Hat Enterprise Linux (RHEL), Windows, or Unknown. |
Architecture |
Architecture type (read-only): 32-bit, 64-bit, or Unknown. |
Template Properties The following fields display values for the enterprise image and the cloud template. The enterprise values are read-only, but you can modify the values for the cloud template. |
|
Memory (MB) |
Amount of memory (in megabytes) for the template. |
CPU Cores |
Number of CPU cores for the template. |
Disk (GB) |
Amount of disk space (in gigabytes) for the template. |
Field | Description |
---|---|
Timezone |
Time zone to use when starting a cloud VM using this template. |
Hostname |
VM hostname. |
Root Password |
Password for the root account. |
Confirm Password |
Confirming password entry. |
Add-on Packages |
Additional packages available for the image being imported. The specific packages listed depend on the ISO image being imported. Check the check boxes of any packages you want to include with the ISO image. |
You can use an existing VM template in your data center to create a template on the cloud. After you create the template on the cloud, you can use it to instantiate cloud VMs.
Ensure that at least one VM template is available for you to upload to the cloud.
Step 1 | Choose InterCloud Management > Enterprise > VM Managers. |
Step 2 | In the navigation pane, navigate to the data center, cluster, host, or resource pool with the required template. |
Step 3 | In the Templates table, select the required template, then click Migrate Template to Cloud. |
Step 4 | In the Infrastructure screen, select the destination VPC, then click Next. |
Step 5 | In the Template Properties screen, provide the information described in Template Properties Screen, then click Next. |
Step 6 | In the Network Properties screen, optionally assign a port profile to each NIC as follows, then click Next: |
Step 7 | In the Summary and Apply screen, confirm that the information is correct, then click Finish. |
Prime Network Services Controller enables you to create a template under a specific VPC from an imported VM image or a VM in the data center.
Step 1 | Choose InterCloud Management > Public Cloud > VPCs > vpc > Templates. |
Step 2 |
Click Add New Template. The Add New Template wizard opens. |
Step 3 |
In the Source Image screen, do one of the following, then click Next:
|
Step 4 | In the Template Properties screen, provide the information described in Template Properties Screen, then click Next. |
Step 5 | In the Network Properties screen, optionally assign a port profile to each NIC as follows, then click Next: |
Step 6 | In the Summary and Apply screen, confirm that the information is accurate, then click Finish. |
After you create a VM template on a cloud, you can instantiate one or more cloud VMs.
Step 1 | Choose InterCloud Management > Public Cloud > VPCs > vpc > Templates. |
Step 2 | In the Templates table, choose a deployed template, then click Instantiate VM. |
Step 3 | In the Infrastructure screen, do the following, then click Next: |
Step 4 | In the VM Properties screen, provide the information described in VM Properties Screen, then click Next. |
Step 5 |
In the Network Properties screen, provide the following information, then click Next:
|
Step 6 | In the Review Summary and Apply screen, confirm that the information is accurate, then click Finish. |
Field | Description |
---|---|
SSH User |
Username for SSH access. |
OS Information |
|
OS |
Cloud VM operating system (read-only): CommunityEnterprise OS (CentOS), Red Hat Enterprise Linux (RHEL), Windows, or Unknown. |
Architecture |
Architecture type (read-only): 32-bit, 64-bit, or Unknown. |
Template Properties The following fields display values for both the template and the cloud VM. The values for the template are read-only, but you can modify the values for the cloud VM as needed. |
|
Memory (MB) |
Amount of memory (in megabytes) for the cloud VM. |
CPU Cores |
Number of CPU cores on the cloud VM. |
Disk (GB) |
Amount of disk space (in gigabytes) for the cloud VM. |
If you instantiate a cloud VM from a VM that has a static IP address in the enterprise data center, you can access the cloud VM by using the same enterprise IP address. If you instantiate a cloud VM from a VM that uses DHCP in the enterprise data center, you can access the cloud VM by using the IP address that the VM obtained from the DHCP server. After the cloud VM is created, the Prime Network Services Controller UI displays the enterprise IP address details for your reference.
Step 1 | Choose InterCloud Management > Public Cloud > VPCs > vpc > VMs. |
Step 2 |
Click Instantiate New VM. The Instantiate New VM Wizard opens. |
Step 3 | In the Infrastructure screen, choose the required InterCloud Link from the drop-down list, then click Next. |
Step 4 |
In the Source screen, do one of the following:
|
Step 5 | In the VM Properties screen, provide the information as described in VM Properties Screen, then click Next. |
Step 6 |
In the Network Properties screen, provide the following information, then click Next. The information you need to enter depends on whether you are using a VM or a template to instantiate the cloud VM:
|
Step 7 |
In the Summary and Apply screen, do one of the following, depending to the source of the cloud VM:
|
Field | Description |
---|---|
VM Name |
Cloud VM name. |
SSH User |
Username for SSH access. |
OS Information |
|
OS |
VM operating system (read-only): CommunityEnterprise OS (CentOS), Red Hat Enterprise Linux (RHEL), Windows, or Unknown. |
Architecture |
VM architecture (read-only): 32-bit, 64-bit, or Unknown. |
Template Properties The following fields display values for both the template and the cloud VM. The template values are read-only, but you can modify the values for the cloud VM as needed. |
|
Memory (MB) |
Amount of memory (in megabytes) for the VM. |
CPU Cores |
Number of CPU cores for the VM. |
Disk (GB) |
Amount of disk space (in gigabytes) for the VM. |
You can migrate an existing VM in your data center to the cloud and thereby create a new cloud VM. After you migrate the enterprise VM to the cloud, you cannot migrate it back to the enterprise data center. However, when you migrate the VM to the cloud, you can retain the original VM in the data center.
Note |
Do not make any changes to a VM or its structure in VMware vCenter while the VM is being migrated to the cloud. Similarly, do not make any changes to a VM or its structure in VMware while aborting the migration of the VM to the cloud. If you need to make changes in VMware vCenter that affect the VM, abort or terminate any migration in progress, make the changes in VMware vCenter, and then migrate the VM to the cloud. |
Step 1 | Choose InterCloud Management > Enterprise > VM Managers. |
Step 2 | In the navigation pane, navigate to and select the data center, cluster, host, or resource pool with the required template. |
Step 3 | In the VMs table, select the VM to use for the VM template, then click Migrate VM to Cloud. |
Step 4 | In the Infrastructure screen, select the InterCloud link to use for the VM template, then click Next. |
Step 5 | In the VM Properties screen, provide the information described in VM Properties Screen, then click Next. |
Step 6 | In the Network Properties screen, optionally assign a port profile to each NIC as follows, then click Next: |
Step 7 | In the Summary and Apply screen: |