Chapter 1. Overview

About Cisco Intercloud Fabric

About the Cisco Intercloud Fabric Product

Cisco Intercloud Fabric Architecture

Cisco Intercloud Fabric

Secure Cloud Extension

Recommended Network Topology for Cisco Intercloud Fabric

Chapter 2. Installing Cisco Intercloud Fabric

About Installing Cisco Intercloud Fabric

System Requirements

Guidelines and Limitations

Prerequisites

Workflow for VMware Environments

Running the Intercloud Fabric Pre-Installation Check Tool

Installing Intercloud Fabric in VMware Environments

About Networks in Intercloud Fabric

Installing Intercloud Fabric Components

Updating System Settings

Changing the Password for Intercloud Fabric

Managing Service Requests

Chapter 3. Cisco Intercloud Fabric Licenses

About Cisco Intercloud Fabric Licensing

Licensing Requirements

Fulfilling the Product Access Key

Uploading a License File

Managing Licenses

Chapter 4. Upgrading Cisco Intercloud Fabric

About Upgrading Intercloud Fabric

Prerequisites

Workflow for Upgrading Intercloud Fabric

Upgrading Intercloud Fabric Infrastructure Components

Upgrading an Intercloud Fabric Link

Chapter 5. Additional Information

Related Documentation

Documentation Feedback

Obtaining Documentation and Submitting a Service Request

Copyright Page

Chapter 1. Overview

This chapter contains the following sections:

- About Cisco Intercloud Fabric

- About the Cisco Intercloud Fabric Product

- Cisco Intercloud Fabric Architecture

- Cisco Intercloud Fabric

- Secure Cloud Extension

- Recommended Network Topology for Cisco Intercloud Fabric

About Cisco Intercloud Fabric

Cisco Intercloud Fabric provides a faster and flexible response to business needs and addresses the potential challenges with hybrid clouds. A hybrid cloud is an interaction between private and provider clouds where private clouds extend to provider clouds and use provider cloud resources in a secure and scalable way. Intercloud Fabric enables you to place workloads across heterogeneous environments in multiple provider clouds. Intercloud Fabric provides the architectural foundation for secure hybrid clouds, which allows enterprises to easily and securely connect the private clouds to the provider cloud as needed and on demand. Intercloud Fabric provides the following benefits:

- Provides a single point of management and control for virtual workloads across multiple provider clouds.

- Provides a choice of cloud providers, such as Amazon Web Services, Microsoft Azure, and multiple Intercloud Fabric provider-based clouds.

- Provides highly secure, scalable connectivity to extend private clouds to provider clouds.

- Enforces consistent network and workload policies throughout the hybrid cloud.

Cisco Intercloud Fabric

About the Cisco Intercloud Fabric Product

The Cisco Intercloud Fabric architecture provides the following product configurations to address enterprise and service provider customers:

- Cisco Intercloud Fabric for Business

- Cisco Intercloud Fabric for Providers

Cisco Intercloud Fabric for Business is intended for enterprise customers who want to transparently extend their private clouds into provider cloud environments, while keeping the same level of security and policy across environments. Cisco Intercloud Fabric for Business consists of the following components:

- Intercloud Fabric Virtual Machine

- Secure Cloud Extension

The Cisco Intercloud Fabric Installation Guide provides information on installing the components for Cisco Intercloud Fabric for Business.

Cisco Intercloud Fabric for Providers is intended for provider-managed cloud environments, allowing their enterprise customers to transparently extend their private cloud environments into the provider's cloud, while keeping the same level of security and policy across cloud environments.

The Cisco Intercloud Fabric Provider Installation Guide provides information on installing the components for Cisco Intercloud Fabric for Providers.

Cisco Intercloud Fabric Architecture

Cisco Intercloud Fabric is a hybrid cloud solution deployed as virtual machines (VMs) in the private cloud and in the provider cloud. Cisco Intercloud Fabric for Business consists of the following components:

- Intercloud Fabric Virtual Machine: This VM contains the Intercloud Fabric components.

- Secure Cloud Extension: This component contains the Intercloud Fabric Extender (ICX) and the Intercloud Fabric Switch (ICS).

Intercloud Fabric for Business Architecture

Intercloud Fabric Provider Platform provides an extensible adapter framework to allow integration with different provider cloud infrastructure management platforms, and other cloud APIs. It is a virtual appliance that is deployed on the provider cloud and lets service provider customers access cloud resources using Intercloud Fabric APIs. It also translates API calls to different provider infrastructure platforms, giving customers the choice to move their workloads regardless of the cloud API exposed by the service provider.

Intercloud Fabric for Providers Architecture

Cisco Intercloud Fabric

Intercloud Fabric is the single point of management and consumption for hybrid cloud solutions for end users and IT administrators. It offers a single console so that end users and IT administrators can provision workloads to private and provider clouds. Intercloud Fabric exposes northbound APIs that allow customers to programmatically manage their workloads in a hybrid cloud environment or to integrate with other cloud management platforms.

Intercloud Fabric provides a self-service portal for IT administrators to manage and consume hybrid cloud offers, and for end users to consume services. For end users, Intercloud Fabric provides a service catalog that combines offers from multiple clouds and a single self-service IT portal for multiple provider clouds.

Intercloud Fabric has an IT administrative portal from which administrators can perform various tasks, such as configure users, create catalogs, and create virtual machine templates.

Intercloud Fabric Features

Secure Cloud Extension

The Secure Cloud Extension forms the basis for the core switching and services infrastructure in the Cisco Intercloud Fabric solution. The Secure Cloud Extension provides the following features:

- Secure Layer 2 network extension from a private cloud to a provider cloud.

- Advanced switching features for applications running in the provider cloud.

- Support for services such as zone-based firewalls and routing in the provider cloud.

The Secure Cloud Extension consists of several components working together to provide these functions. The private cloud is connected to the provider cloud through a highly secure tunnel that is established between a pair of virtual appliances. The Intercloud Fabric Extender (ICX) runs in the private cloud, and the Intercloud Fabric Switch (ICS) runs in the provider cloud. These appliances can be deployed in a high availability pair to provide redundancy. Virtual services are deployed within this environment to provide firewall and routing support in the provider cloud.

Secure Cloud Extension

Intercloud Fabric Extender

The Intercloud Fabric Extender is a VM that runs in the private cloud. It is responsible for establishing a secure tunnel to connect the Intercloud Fabric components in the private cloud with the provider cloud. The main functions of the Intercloud Fabric Extender are as follows:

- Establishes a secure tunnel to the Intercloud Fabric Switch in the provider cloud.

- Integrates with the private cloud virtual switch, such as a Cisco Nexus 1000V, VMware vSwitch, or DVS.

Intercloud Fabric Switch

The Intercloud Fabric Switch is a VM that runs in the provider cloud. It is responsible for establishing secure tunnels to connect VMs in the provider cloud to the private cloud VMs and other VMs in the cloud. The main functions of the Intercloud Fabric Switch are as follows:

- Establishes a secure tunnel to the Intercloud Fabric Extender in the private cloud.

- Establishes a secure access tunnel to the cloud VMs.

- Switches traffic between the cloud VMs.

- Switches traffic between cloud VMs and VMs in the private cloud.

- Applies network policies to the cloud-switched network traffic.

- Monitors and gathers cloud VM statistics.

Cisco Intercloud Fabric Agent

The Cisco Intercloud Fabric Agent (ICA) provides a network overlay to the VMs in the cloud. It secures the guest VM traffic in the cloud and abstracts the cloud infrastructure. It is deployed in the provider cloud as a secure tunnel driver that runs within the cloud VM's operating system. It redirects network traffic to the secure overlay network as follows:

- Establishes a secure tunnel to connect to an Intercloud Fabric Switch that allows VMs in the cloud to communicate with private cloud VMs and provider cloud VMs.

- Collects secure overlay-related statistics.

Recommended Network Topology for Cisco Intercloud Fabric

We recommend the following network topology for Intercloud Fabric, where the two servers are deployed in a VMware HA-enabled cluster:

Recommended Network Topology for Intercloud Fabric

Chapter 2. Installing Cisco Intercloud Fabric

This chapter contains the following sections:

- About Installing Cisco Intercloud Fabric

- System Requirements

- Guidelines and Limitations

- Prerequisites

- Workflow for VMware Environments

- Running the Intercloud Fabric Pre-Installation Check Tool

- Installing Intercloud Fabric in VMware Environments

- About Networks in Intercloud Fabric

- Installing Intercloud Fabric Components

- Updating System Settings

- Changing the Password for Intercloud Fabric

- Managing Service Requests

About Installing Cisco Intercloud Fabric

The Cisco Intercloud Fabric for Business software is available at Cisco.com.

The Cisco Intercloud Fabric for Business software contains the following zip image:

Name

Description

icfb-k9-3.2.1-pkg.zip

Software to install Intercloud Fabric in VMware environments.

Use this file to install Intercloud Fabric. See Workflow for VMware Environments.

icf-preInstallCheck-1.1.0-pkg.zip

Software to run the Intercloud Fabric pre-installation check tool.

See Running the Intercloud Fabric Pre-Installation Check Tool.

System Requirements

The following tables identify the system requirements for installing Cisco Intercloud Fabric.

System Requirements

Requirement

Description

Intercloud Fabric

CPUs

8 vCPU (64-bit x86 CPU [VT-capable])

Network interface cards (vNICs)

1

RAM

16 GB

Disk

440 GB

Intercloud Fabric Extender

Memory

2 GB

CPU

2 vCPU

Disk

3 GB

Intercloud Fabric Component

Memory

2 GB

CPU

1 vCPU

Disk

3 GB

Note

The virtual disk must be capable of at least 40 MBps bandwidth. We recommend that you use solid-state disk (SSD) hardware.

Hypervisor Requirements

Requirement

Description

VMware

Version

ESXi 5.1, 5.5, and 6.0

Client Browser Requirements

Operating System

Operating System Version

Supported Browser

Windows

7 SP1

Internet Explorer 11 or later

Firefox (latest version)

Chrome (latest version)

Mac OS

X (EL Capitan)

Safari (latest version)

Firefox (latest version)

Chrome (latest version)

Important Notes

- HTML5 support is required.

- JavaScript must be enabled.

System Requirements for Provider Clouds

Provider/Model

Device

vCPU

Memory

Disk

AWS

c3.2xlarge

Intercloud Fabric Switch

8

15 GB

20 GB

Guidelines and Limitations

- For VMware environments, the Cisco Nexus 1000V for VMware vSphere, VMware vSwitch, or VDS is already installed in the private cloud. See Cisco Nexus 1000V for VMware for more information.

- An Intercloud Fabric cloud link can support up to a maximum of 100 VMs.

Prerequisites

Provider Cloud Prerequisites

- Using a proxy on a private cloud is not supported when Intercloud Fabric is being used to connect to a public cloud.

- When using AWS or Microsoft Azure as the provider, run the Intercloud Fabric pre-installation check tool to automatically verify that all prerequisites for deploying Intercloud Fabric are met.

- Create a provider account in the cloud provider.

- Certain ports must be open outbound in the firewall to allow the Intercloud Fabric appliance to communicate with the cloud provider.

- TCP ports 22 and 443 are required for the Intercloud Fabric internal management IP.

- Certain ports must be open outbound in the firewall to allow the Intercloud Fabric Extender to communicate with the Intercloud Fabric Switch.

- For an HTTPS tunnel, ports 22 and 443 must be open.

- For a UDP tunnel, ports 22, 443, UDP port 6644, and TCP port 6644 must be open.

- For a TCP tunnel, ports 22, 443, and TCP ports 6644 and 6646 must be open.

- Specify the tunnel protocol when configuring the tunnel profile. You can choose the tunnel profile when you configure an Intercloud Fabric link.

Virtual Machine Manager Prerequisites (for VMware Environments)

- Intercloud Fabric uses port 443 to register the certificate in VMware vCenter. Ensure that port 443 is open. In addition, ensure that port 80 is open for Intercloud Fabric to communicate with vCenter.

- Verify that all Intercloud Fabric cloud hosts are running a supported version of ESX or ESXi: 5.1, 5.5, or 6.0.

- Intercloud Fabric requires administrative access to VMware vCenter.

- Ensure that the hypervisor host and virtual switch are configured as per the "Virtual Switch Prerequisites" section.

Cisco Intercloud Fabric Prerequisites

- Know the IP, subnet mask, and gateway information for Intercloud Fabric.

- Verify that the date and time are set correctly to connect to the cloud provider.

- Know the management port profile or management network name for the VM.

Note

The management port profile can be the same port profile that is used for the Cisco Nexus 1000V Virtual Supervisor Module (VSM). The port profile is configured in the VSM and is used for the Intercloud Fabric management interface. This requirement applies only if you are using a Cisco Nexus 1000V switch; it does not apply if you are using a VMware virtual switch.

- If you do not configure NAT and PAT policies correctly for cloud providers, incoming traffic will not reach the provider.

- Optionally, obtain remote storage server details if you want to use remote storage for images.

- Optionally, run the Intercloud Fabric pre-installation check tool to validate your environment before installing Intercloud Fabric. The tool performs private cloud checks, public cloud checks, and port checks to ensure that the requirements for installing the Intercloud Fabric OVA are complete.

Virtual Switch Prerequisites

- VMware

- For a security policy for the trunk port group on the VMware virtual switch, set the Promiscuous Mode, MAC Address Changes, and Forged Transmits to Accept in the VMware vSphere UI. This requirement applies only if you are using a VMware virtual switch or distributed switch; it does not apply if you are using a Cisco Nexus 1000V switch.

- If the Intercloud Fabric Extender is hosted on a VMware vSwitch or distributed switch (VDS) and if the vSwitch or distributed switch is connected to multiple physical NICs, you must enable the setting Net.ReversePathFwdCheckPromisc=1 in the ESX host where the Intercloud Fabric Extender is hosted. This setting is found under Host > Configuration > Advanced Settings > Net in the VMware vSphere UI. If this setting is not enabled, you might experience traffic loss or duplicate packets between enterprise and cloud VM traffic or Intercloud Fabric Switch module flap at the Intercloud Fabric VSM. This requirement applies only if you are using a VMware virtual switch or distributed switch to host the Intercloud Fabric Extender; it does not apply if you are using a Cisco Nexus 1000V switch.

Note

If the Net.ReversePathFwdCheckPromisc changes while the ESXi host is running, you must toggle (disable then re-enable) the Promiscuous Mode check box in the Intercloud Fabric Extender trunk port group security settings for the change to take effect.

- For the VMware virtual switch, you must set the trunk port group to allow All VLAN IDs in the VMware vSphere UI.

- Cisco Nexus 1000V switch—You must disable Unknown-Unicast-Flooding-Block (UUFB) if you are using a Cisco Nexus 1000V switch in the private cloud. Enter the command no uufb enable to disable UUFB. Enter the command show run | include uufb to verify that you disabled UUFB.

Workflow for VMware Environments

Installing Intercloud Fabric in VMware environments includes the following steps:

Procedure

Step 1

(Optional) Run the Intercloud Fabric pre-installation check tool. See Running the Intercloud Fabric Pre-Installation Check Tool.

Step 2

Install Intercloud Fabric in VMware environments using OVA.
See Installing Intercloud Fabric in VMware Environments.

Step 3

Install the Intercloud Fabric components.
See Installing Intercloud Fabric Components.

Step 4

Upload an Intercloud Fabric license.
See Uploading a License File.

Running the Intercloud Fabric Pre-Installation Check Tool

Run the Intercloud Fabric pre-installation check tool to validate your environment before installing Intercloud Fabric. The tool performs the following checks to ensure that the requirements for installing the Intercloud Fabric OVA are complete:

- Private cloud checks such as vCenter version, session locale, trunk, management network, and data network port group validation, and security group settings validation on the trunk port group.

- Public cloud checks for AWS and Microsoft Azure such as connection validation, credential validation, API endpoint connectivity validation, account permission validation for EC2, and account permission and endpoint access validation for Amazon S3.

- Port checks such as validation for TCP ports 22, 443, 6644, 6646, and UDP port 6644.

Procedure

Step 1

Download the Intercloud Fabric pre-installation check OVA to your desktop.

Step 2

In the VMware vSphere (or vCenter) Client login dialog box, enter your login credentials.

Step 3

Deploy the OVA file and proceed with the OVA deployment wizard.

Step 4

In the Storage pane, select the data store where Intercloud Fabric will be installed.
We recommend that you allocate at least 40 MBps sequential IOPS.

Step 5

In the Network Mapping pane, select the port group (management network) where Intercloud Fabric will be installed.

Step 6

In the Properties pane, provide the password, management IP address, subnet mask, gateway, domain name, and DNS server IP address; then, click Next.

Step 7

Review the parameters and choose Power On After Deployment.

Step 8

Click Submit.

Step 9

After the VM is deployed and running, use SSH to connect to the pre-installation check tool with the following information:

- IP address of the tool

- Username—root

- Password—password provided during the OVA installation

Step 10

Enter the command preInstallcheck to start the test.

Step 11

When prompted, enter the vCenter information such as IP address, admin username, admin password, data center, compute (ESX) host IP address, data store, management network, trunk network, and data network.
You can use the same network for management and data.

Step 12

Verify the summary and enter Y to proceed or N to modify the information.

Step 13

Select the public cloud provider and do the following:

1. For an AWS public cloud, provide the following information:

- Access ID

- Access key

- Region

- Cloud type

- VPC

- Subnet

2. For a Microsoft Azure public cloud, use SCP to copy the Azure certificate from the preInstallcheck VM to a host where the Azure portal is reachable. Upload the certificate to the Azure account from the Azure portal. Then, provide the following information:

- Azure subscription ID

- Location

Step 14

The tool performs a series of checks and displays the results. Look for any failed results and fix them before installing the Intercloud Fabric OVA.

Installing Intercloud Fabric in VMware Environments

Use this procedure to install Intercloud Fabric in VMware environments using an OVA.

Before You Begin

- You need administrator privileges to connect to VMware vSphere or vCenter.

- Confirm that the Intercloud Fabric OVA image is available from the VMware vSphere Client.

- You have the hostname and static IP address for ICF.

- Make sure you are connected to vCenter using a VMware vSphere Client; do not deploy the OVA directly on the ESX host. The following error message is displayed when you attempt to deploy the OVA directly on the ESX host: This OVF package uses features that are not supported when deploying directly to an ESX host.

- Make sure that VMware HA is enabled. See VMware vSphere Documentation.

Procedure

Step 1

In the VMware vSphere (or vCenter) Client login dialog box, enter your login credentials.

Step 2

Click Login.

Step 3

In the Navigation pane, choose the Data Center for Intercloud Fabric deployment.

Step 4

Choose File > Deploy OVF Template.
The Deploy OVF Template window appears.

Step 5

In the Source pane, browse to the location, choose the file, and click Open to choose your OVF source location.

Step 6

In the OVF Template Details pane, verify the details and click Next.

Step 7

In the End User License Agreement pane, read the license agreement and click Accept.

Step 8

In the Name and Location pane, do the following:

1. (Optional) In the Name field, enter the VM name.

2. Choose the Inventory Location where Intercloud Fabric is being deployed and click Next.

Step 9

In the Storage pane, choose the location in which to store virtual machine files.

Step 10

In the Host/Cluster pane, choose the required host, cluster, or resource pool, and click Next.

Step 11

In the Disk Format pane, enter the data store and available space.

Step 12

In the Disk Format pane, click one of the following radio buttons and click Next:

- Thick Provisioned (Lazy Zeroed)—To allocate storage immediately in thick format. We recommend you that you use this format.

- Thick Provisioned (Eager Zeroed)—To allocate storage in thick format. It might take longer to create disks using this format.

- Thin Provisioned—To allocate storage on demand as data is written to disk.

Step 13

In the Network Mapping pane, choose your network and click Next.

Step 14

In the Properties pane, provide the following information and click Next:

- Intercloud Fabric hostname

- Admin password

Note:   The password must contain from 8 to 64 characters (A-Z, a-z, 0-9).

- Management IP address

- Internal management IP address

- Subnet mask

- Gateway

- Optional syslog server IP

- Time zone

Step 15

In the Ready to Complete pane, verify the options selected and click Finish.

Step 16

Make sure you have sufficient vCPU and memory to power on the VM.

Step 17

Power on the VM.

Step 18

After the appliance boots up, copy and paste the Intercloud Fabric IP address that appears into a supported web browser to access the Login page. There might be a delay of up to 30 minutes before you can connect to the Intercloud Fabric UI.

Step 19

On the Login page, enter the ICF admin password that you entered in Step 14.

About Networks in Intercloud Fabric

There are three types of networks in Intercloud Fabric:

- Management network—Manages Intercloud Fabric components and services. In this network, Intercloud Fabric components and services are attached to the management network for connectivity.

- Data network—Manages cloud virtual machine interfaces. In this network, VMs can be attached to one or more data networks for connectivity.

- Transport network—Connects the Intercloud Fabric Routing Service back to the private cloud so that the cloud virtual machine can reach remote networks that are not extended to the public cloud. The transport network is used by the routing service in the public cloud to communicate with the private cloud. Traffic from VMs in the public cloud is routed to the enterprise gateway on the transport network, if the destination network is not in the public cloud.

Use the following guidelines to create networks in Intercloud Fabric:

- During the installation of the Intercloud Fabric components, you must define the management network. The same network is used as the transport network.

See Installing Intercloud Fabric Components.

- Management and transport networks are always extended to the cloud. Cloud properties such as DHCP and L3 are not applicable.

- During the installation of the Intercloud Fabric components, you can use the same network as your data network and enable DHCP for the network on the private cloud.

- A network with IP addresses in the range 10.0.3.0/24 is reserved for internal communication. Do not assign IP addresses in this range for Intercloud Fabric or as IP pool addresses for the management network.

- You can create additional networks later.

- You can only have one management and one transport network. You can use the management network defined during the installation of the Intercloud Fabric components as the transport network. Alternatively, you can disable the transport network created during the installation of the Intercloud Fabric components and create a new transport network. You can also use the data network as the transport network.

IP pools

In Intercloud Fabric, IP pools are used for the following:

- Intercloud Fabric components in the private cloud.

- Intercloud Fabric link components, such as the Intercloud Fabric Extender or an Intercloud Fabric Switch, in the public cloud.

- Virtual machine addresses in the cloud.

Use the following guidelines to create IP pools:

- You can either use the same IP pool for the data and management networks, or create separate IP pools.

- You must create at least one IP pool for the management network during the installation of Intercloud Fabric components and creation of the Intercloud Fabric cloud.

- You can assign IP pools to resource pools and use them for the data network.

Installing Intercloud Fabric Components

Use the following procedure to install the Intercloud Fabric components.

Before You Begin

You have already installed Intercloud Fabric using the OVA.

Procedure

Step 1

Log in to Intercloud Fabric.

Step 2

Click Specify VM Manager Credentials.

Step 3

Complete the following fields for Specify VM Manager Credentials:

Name

Description

Name

Enter the name of the virtual account.

Description

(Optional) Enter the description of the virtual account.

Select VM Manager Type

Choose the VM manager type.

Server Address

Enter the server IP address or the hostname of the virtual account.

Username

Enter the username of the virtual account.

Password

Enter the password of the virtual account.

Step 4

Click Next.
The progress of the task is displayed under Service Request.

Step 5

Click Define Management Network.

Step 6

Complete the following fields for Define Management Network:
See About Networks in Intercloud Fabric for guidelines for creating networks. A network with IP addresses in the range 10.0.3.0/24 is reserved for internal communication. Do not assign IP addresses in this range for Intercloud Fabric or as IP pool addresses for the management network.

Name

Description

Name

Enter the name of the network.

The name can contain from 1 to 64 alphanumeric characters, including hyphens, underscores, periods, and colons.

Description

Enter the description of the network.

VLAN ID

Enter the VLAN ID of the management network in your environment. The VLAN ID range is from 1 to 3967 and from 4048 to 4093.

If you are using Cisco Nexus 1000V, VLAN IDs 3968 to 4047 are unavailable for use. If you are using VMware vSwitch, VLAN IDs 3968 to 4047 are available.

Subnet

Enter the subnet address of the management network in your environment.

The subnet defines the base network and mask. The supported format is x.x.x.x/xx.

Enterprise Gateway

Enter the IP address of the private cloud gateway of the network.

An enterprise gateway is applicable only for stretched networks and is mandatory for management and transport networks.

A stretched network without an enterprise gateway is treated as an unroutable network.

IP Pool Name

Enter the name of the IP pool associated with the network.

The name can contain from 1 to 64 alphanumeric characters, including hyphens, underscores, periods, and colons. You cannot change the name after the object has been saved.

IP Pool Range

Enter the start and end IP address for the range of IP addresses to add to the IP pool.

Supported formats include:

x.x.x.x - y.y.y.y -- IP addresses
between x.x.x.x - y.y.y.y inclusive
x.x.x.x#n --  n IP addresses from x.x.x.x
x.x.x.x -- only one IP address x.x.x.x
x.x.x.x-y
x.x.x.x-y.y
x.x.x.x-y.y.y

Multiple IP ranges can be defined by separating the ranges with commas.

Examples:

10.2.94.197
10.2.94.197-200
10.2.94.197-10.2.94.200
10.2.94.197#5

Use this for data network

Check the check box to use the network for data and management.

A management network is used to manage Intercloud Fabric components and ICF services. In this network, Intercloud Fabric components and services are attached to the management network for connectivity.

A data network is used to manage cloud virtual machine interfaces. In this network, VMs can be attached to one or more data networks for connectivity.

The defaults for the management network include:

- The network is always stretched.

The defaults for the data network include:

- The network is always stretched.

- The network is connected to Intercloud Fabric Routing Service.

See About Networks in Intercloud Fabric for more information.

Step 7

Click Submit.

Step 8

Click Specify Installation Location.

Step 9

Complete the following fields for Specify Installation Location:

Name

Description

IP Pool

Choose the IP pool for the virtual machine.

Primary Host Information

Specify the information for the primary Intercloud Fabric components.

Host

Choose the host where the Intercloud Fabric components will be installed.

If you checked the Enable High Availability check box, you must also select the host for the standby.

Management Port Group

Choose the management port group for the virtual machine.

When using the Cisco Nexus 1000V to deploy the virtual machines, port profiles are created in the Cisco Nexus 1000V VSM. When using VMware vSwitch or VDS, port groups are created in the vCenter.

Initially you must create a management port group or port profile along with a trunk port group or port profile.

Datastore

Choose the data store for the VM. The available data stores are sorted by name.

The storage can be local or shared remote, such as NFS or SAN.

If you checked the Enable High Availability check box, choose the data store for the standby.

Show Advanced Settings

Specify the advanced settings for the virtual machine.

Enable High Availability

Check the check box to enable high availability.

Specify the host, port group, and data store for the standby.

Let System Select a Domain ID

Check this check box to configure the domain ID to the default value. Uncheck this check box to configure the domain ID from 1 to 1023.

Domain ID

Enter the domain ID for Intercloud Fabric. When multiple Intercloud Fabric installations share the same network, Intercloud Fabric must be installed with a unique domain ID. A domain ID must be unique in the entire network and be in the range from 1 to 1023.

Step 10

Click Submit to install.
The installation might take up to 15 minutes to complete.

Step 11

To view the status of the task, see Managing Service Requests.

Step 12

If the installation fails, click View Logs.

Updating System Settings

After you install the Intercloud Fabric OVA, you might have to update the system settings if:

- The preferred DNS server is not reachable.

- The preferred or alternate NTP server is not configured or reachable.

Use this procedure to update the system settings before installing the Intercloud Fabric components.

Before You Begin

You have installed the Intercloud Fabric OVA.

Procedure

Step 1

Log in to Intercloud Fabric.

Step 2

Update the following fields for NTP Server. Although configuring an NTP server is optional, we recommend that you configure at least one NTP server for Intercloud Fabric.

Name

Description

Preferred NTP Server

Enter the IP address of the preferred NTP server.

Status

The status of the preferred server is displayed.

Alternate NTP Server

Enter the IP address of the alternate NTP server.

Status

The status of the alternate server is displayed.

Step 3

Complete the following fields for DNS Server. Configuring a DNS server is mandatory. You must configure at least one DNS server for Intercloud Fabric.

Name

Description

Domain Name

Enter the domain name.

Preferred DNS Server

Enter the IP address of the preferred DNS server.

Status

The status of the preferred server is displayed.

Alternate DNS Server

Enter the IP address of the alternate DNS server.

Status

The status of the alternate server is displayed.

Step 4

Click Save.

Changing the Password for Intercloud Fabric

Use this procedure to change the password for Intercloud Fabric.

Procedure

Step 1

Log in to Intercloud Fabric.

Step 2

Click username Change Password.

Step 3

Complete the following fields for Change Password.

Operation

Description

Current Password

Enter the current password.

New Password

Enter the new password. The following characters are permitted: a-z, A-Z, 0-9, ! # $ ( ) * + , . : ; = @ [ ] ^ _ ` { | } ~ -".

Whitespaces are not allowed.

Confirm New Password

Enter the new password again.

Step 4

Click Save.

Managing Service Requests

In Intercloud Fabric, operations that take longer to complete are performed asynchronously to improve performance. These asynchronous workflows are called service requests.

Use this procedure to manage service requests.

Procedure

Step 1

Log in to Intercloud Fabric.

Step 2

Choose Manage > Service Requests > Service Requests.
The Service Requests page lists all of the active service requests.

Step 3

Click a service request to view detailed information such as workflow status and logs for the task.

Chapter 3. Cisco Intercloud Fabric Licenses

This chapter contains the following sections:

- About Cisco Intercloud Fabric Licensing

- Licensing Requirements

- Fulfilling the Product Access Key

- Uploading a License File

- Managing Licenses

About Cisco Intercloud Fabric Licensing

A Cisco Intercloud Fabric license is based on hybrid cloud units (HCUs). An HCU is consumed for every virtual machine running in the public cloud. A powered-off VM does not consume any HCUs.

For Amazon Web Services and Microsoft Azure, two HCUs are checked out per virtual machine. For example, if the HCU count is ten, then five VMs can run in the public cloud. For Cisco-powered providers, one HCU is checked out per virtual machine. For example, if the HCU count is ten, then ten VMs can run in the public cloud.

Cisco Intercloud Fabric includes the following types of licenses:

- Evaluation License (ICFB-EVAL-EBD)—Cisco Intercloud Fabric includes a 60-day evaluation license that lets you try the software before you purchase permanent licenses. The evaluation period starts when you install the software and the evaluation licenses expire within 60 days of installation.

- Permanent License (ICFB-CPC)—Permanent licenses have an expiration date. The license file specifies the number of licenses that you purchased. Contact your Cisco sales representative to purchase permanent licenses.

- Partner License (ICFB-NFR-EBD)—Partner (not for resale) licenses are available only to Cisco partners for demo and lab purposes. Partner licenses have an expiration date. The license file specifies the number of licenses that you purchased. Contact your Cisco sales representative to purchase partner licenses.

Licensing Requirements

Use this procedure to obtain a Cisco Intercloud Fabric license.

Procedure

Step 1

Before you install Intercloud Fabric, generate the Intercloud Fabric license key and claim a certificate (Product Access Key [PAK]).

Step 2

Register the PAK on the Cisco software license site.
See Fulfilling the Product Access Key.

Step 3

After you install Intercloud Fabric, upload the license in Intercloud Fabric.
See Uploading a License File.

Step 4

Check the status of the licenses.
See Managing Licenses.

Fulfilling the Product Access Key

Before You Begin

Obtain the PAK number.

Procedure

Step 1

Navigate to the Cisco Software License website.

Step 2

If you are directed to the Product License Registration page, you can take the training or click Continue to Product License Registration.

Step 3

On the Product License Registration page, click Get New Licenses from a PAK or Token.

Step 4

In the Enter a Single PAK or TOKEN to Fulfill field, enter the PAK number.

Step 5

Click Fulfill Single PAK/TOKEN.

Step 6

Complete the additional fields in License Information to register your PAK.

Step 7

Click Issue Key.
The features for your license appear, and a digital license agreement and a zipped license file are sent to the email address you provided.

Uploading a License File

Use this procedure to upload a license file.

Before You Begin

- If you received a zipped license file by email, extract and save the .lic file to your local machine.

- Register the PAK on the Cisco software license site.

Procedure

Step 1

Log in to Intercloud Fabric.

Step 2

Choose Dashboard > Common Tasks > Upload License File.

Step 3

Click Browse, navigate to and select the Intercloud Fabric .lic file, and click Upload.
After the license file is successfully processed, you receive a confirmation message.

Step 4

(Optional) To view the license status, see Managing Licenses.

Managing Licenses

Use this procedure to manage Intercloud Fabric licenses. See About Cisco Intercloud Fabric Licensing for more information.

Procedure

Step 1

Log in to Intercloud Fabric.

Step 2

Choose Administration > ICF Licenses.
The license details are displayed. If the system uses more HCUs than are available, you must either upload a new license or suspend one or more virtual machines in the cloud to comply with the license agreement. To purchase additional licenses, contact your Cisco sales representative.

The following icons display the license status:

The license is active.

The license is inactive.

The license has expired.

Step 3

(Optional) Click the + icon to upload a new license.

Step 4

Click Browse, navigate to and select the Intercloud Fabric .lic file, and click Upload.
After the license file is successfully processed, you receive a confirmation message.

Chapter 4. Upgrading Cisco Intercloud Fabric

This chapter contains the following sections:

- About Upgrading Intercloud Fabric

- Prerequisites

- Workflow for Upgrading Intercloud Fabric

- Upgrading Intercloud Fabric Infrastructure Components

- Upgrading an Intercloud Fabric Link

About Upgrading Intercloud Fabric

The only supported upgrade path for Intercloud Fabric Release 3.2.1 is from 3.1.1.

You can obtain the upgrade software for Intercloud Fabric from the Download Software page.

Prerequisites

Intercloud Fabric Infrastructure Components

- Before starting the upgrade, verify that all services are up and running.

- The upgrade includes two .tar files: Icf-upgrade-patch-3.1.1.tar.gz and Icf-upgrade-3.2.1.tar.gz. Apply the patch.tar file first, followed by the upgrade.tar file.

Intercloud Fabric Link

- Verify that the Intercloud Fabric infrastructure components have been upgraded.

- Disable the Routing Service.

Workflow for Upgrading Intercloud Fabric

Upgrading Intercloud Fabric includes the following steps:

Procedure

Step 1

Upgrade the Intercloud Fabric infrastructure components. See Upgrading .

Step 2

Upgrade the Intercloud Fabric links. See Upgrading an .

Upgrading Intercloud Fabric Infrastructure Components

Use this procedure to upgrade Intercloud Fabric infrastructure components.

Before You Begin

- Download the upgrade package from Cisco.com.

- Untar the package and obtain the two tar.gz files, which you must use in the following order:

1. Icf-upgrade-patch-3.1.1.tar.gz—Patches the 3.1.1 test bed.

2. Icf-upgrade-3.2.1.tar.gz—Upgrades 3.1.1 to 3.2.1.

Procedure

Step 1

Log in to Intercloud Fabric.

Step 2

Using SSH, connect to the Intercloud Fabric VM CLI console as an administrator.
Note:   For more information, see the Cisco Intercloud Fabric Administration Guide, section "Using Cisco Intercloud Fabric VM CLI Commands."

Step 3

At the SELECT> prompt, enter the option to upgrade and then press Return.

Step 4

At the Do you want to upgrade [y/n]? prompt, enter y and then press Return.

Step 5

When prompted for the SCP, enter command syntax similar to the following and then press Return:
host@198.51.100.254:/home/host/username/upgrade/Icf-upgrade-3.2.1.tar.gz

Step 6

Enter the SCP password at the prompt and press Return.

What to Do Next

The upgrade setup proceeds in the following sequence:

- Intercloud Fabric VM-based content is upgraded, including any new CLIs.

- The Intercloud Fabric Controller is upgraded.

- The Intercloud Fabric Director is upgraded.

- The icfVSM is upgraded.

Upgrading an Intercloud Fabric Link

Use this procedure to upgrade an Intercloud Fabric link.

Before You Begin

- Verify that the Intercloud Fabric VM and icfVSM have been upgraded.

- Disable the Routing Service.

Procedure

Step 1

From a browser, log in to the Intercloud Fabric UI.

Step 2

Click the upgrade link for each of the Intercloud Fabric links.

Chapter 5. Additional Information

- Related Documentation

- Documentation Feedback

- Obtaining Documentation and Submitting a Service Request

Related Documentation

Cisco Intercloud Fabric for Business

The Cisco Intercloud Fabric for Business documentation is available at the following URL:

Click Here

Cisco Intercloud Fabric for Provider

The Cisco Intercloud Fabric for Provider documentation is available at the following URL:

Click Here

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to: intercloud-fabric-doc-feedback@cisco.com.

We appreciate your feedback.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What's New in Cisco Product Documentation RSS feed. RSS feeds are a free service.

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Click Here . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)