Cisco Nexus 1000V for KVM Installation Guide, Release 5.2(1)SK3(1.1)

Bias-Free Language

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.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco Nexus 1000V for KVM Installation Guide, Release 5.2(1)SK3(1.1)

Chapter Title

Preparing for Installation

Results

Updated:
May 26, 2015

Chapter: Preparing for Installation

Preparing for Installation

This chapter contains the following sections:

Downloading the Cisco Nexus 1000V Software

The Cisco Nexus 1000V for KVM software packages are available from two locations and, as such, its image versions are named based on the location. The following table lists the package name and versions based on their location.

Package Name

CCO Image Version

Cisco PPA

VSM

5.2.1.SK3.1.1

5.2.1.sk3.1.0.187-1

VEM

14.04.5.2.1.sk3.1.0.s0.187-1

14.04.5.2.1.sk3.1.0.s0.187-1

VXLAN-GATEWAY

5.2.1.SK3.1.1

5.2.1.sk3.1.0.187-1

The location that you choose to download the software from affects the way that you set up and execute the installation.

  • Downloading from the Cisco PPA—You can set up your installation so that when you deploy the Cisco Nexus 1000V for KVM, the charms retrieve the packages from the Cisco PPA. For charms to install the VSM, VEM, and VXLAN gateway packages from the PPA you must provide the correct Cisco PPA link as the n1kv-source in the global configuration file.

  • Downloading from Cisco.com—You can manually download the software from Cisco.com to an HTTP server so that when you deploy the Cisco Nexus 1000V for KVM, Juju retrieves the software from the HTTP server. To perform this type of installation, you must define the location of the HTTP server for the VSM, VEM, and VXLAN Gateway charms in the global configuration file.

    For example, you can use the MAAS server as the HTTP server because it already provides the HTTP service and its IP address is well known within the cluster.

For information, see the following:

Preparing the Configuration and Mapping Files

Before you can deploy the Cisco Nexus 1000V for KVM, you need to configure several charms with specific configuration information. You do this by defining specific charm parameters in a global configuration file that you create.


Note

You must maintain consistency between the global configuration file parameter names and the charm's config.yaml file parameter names. Do not introduce new parameter names in the global configuration file.

If your deployment requires it, you can deploy VEMs with unique configuration parameters instead of using the configuration parameters that are defined for all VEMs in the config.yaml file. To do this, you need to create a mapping file.

OpenStack Charm Parameters

You must modify the global configuration file for the following Cisco Nexus 1000V for KVM-related OpenStack charms:

  • nova-cloud-controller

  • nova-compute

  • openstack-dashboard

  • quantum-gateway

The following sections provide information about the OpenStack charm parameters that you need to define in the global configuration file.

nova-cloud-controller Charm Parameters

Parameter

Description

openstack-origin: debian-pkg-location

Location of the Cisco Nexus 1000V for KVM Debian package:

openstack-origin:  ppa:cisco-n1kv/icehouse-updates

n1kv-vsm-username: vsm-username

Login for accessing the Cisco Nexus 1000V for KVM (VSM).

n1kv-vsm-password: vsm-password

Secure password for accessing the Cisco Nexus 1000V for KVM (VSM).

n1kv-vsm-ip: vsm-ip-address

IP address of the VSM.

This example shows the nova-cloud controller portion of the global configuration file: 
nova-cloud-controller:
  openstack-origin:  ppa:cisco-n1kv/icehouse-updates
  n1kv-vsm-username: nexus
  n1kv-vsm-password: nexus123
  n1kv-vsm-ip: 192.168.10.1

.
.
.

nova-compute Charm Parameters

Parameter

Description

openstack-origin: debian-pkg-location

Location of the Cisco Nexus 1000V for KVM Debian package:

openstack-origin:  ppa:cisco-n1kv/icehouse-updates

This example shows the nova-compute portion of the global configuration file: 
nova-comute:
  openstack-origin:  ppa:cisco-n1kv/icehouse-updates
.
.
.

quantum-gateway Charm Parameters

Parameter

Description

openstack-origin: debian-pkg-location

Location of the Cisco Nexus 1000V for KVM Debian package:

openstack-origin:  ppa:cisco-n1kv/icehouse-updates

enable-l3-agent: {true | false}

Parameter for enabling or disabling the Layer 3 agent. Following are the valid values:

  • true—Brings up the Linux router as part of the quantum-gateway.

  • false—Does not bring up the Linux router.

This example shows the quantum-gateway portion of the global configuration file: 
quantum-gateway:
  openstack-origin:  ppa:cisco-n1kv/icehouse-updates
  plugin: n1kv
  ext-port: eth1
.
.
.

openstack-dashboard Charm Parameters

Parameter

Description

openstack-origin: debian-pkg-location

Location of the Cisco Nexus 1000V for KVM Debian package:

openstack-origin:  ppa:cisco-n1kv/icehouse-updates

profile:name

Default profile for the dashboard to use, for example, cisco.

This example shows the openstack-dashboard portion of the global configuration file: 

openstack-dashboard:
  openstack-origin:  ppa:cisco-n1kv/icehouse-updates
  profile: cisco
.
.
.

Cisco Nexus 1000V for KVM VSM Charm Parameters

This table lists the Cisco Nexus 1000V for KVM VSM charm parameters that you need to define in the global configuration file.

Parameter

Description

n1kv-source: debian-pkg-location

Location of the Cisco Nexus 1000V for KVM VSM software. The location that you define depends on whether you choose to have Juju download the VSM software (charm) automatically from the Cisco Personal Package Archive (PPA) or you choose to manually download the software from Cisco.com to a local HTTP server. For more information, see Downloading the Cisco Nexus 1000V Software.

Define the debian-pkg-location variable in one of the following two ways:

  • Cisco PPA—n1kv-source:  ppa:cisco-n1kv/n1kv-updates

  • Local HTTP server—http://server-address/vsm-image-name.iso

n1kv-vsm-domain-id: domain-id

Domain number that the VSM will control.

n1kv-vsm-password: vsm-password

Secure password for accessing the Cisco Nexus 1000V for KVM (VSM).

n1kv-vsm-name: vsm-name

Name of the VSM.

n1kv-vsm-role: {primary | secondary}

High availability role. Valid values are primary or secondary.

n1kv-vsm-ip: management-IP-address

IP address of the management interface.

n1kv-vsm-mgmt-netmask: management-ip-subnet-mask

IP address subnet mask of the management interface.

n1kv-vsm-gateway: management-subnet-default -gateway

IP address of the management subnet default gateway.

n1kv-vsm-ctrl-mac:

MAC address of the VSM's control TAP interface. This parameter is optional for the primary VSM, but required for the secondary VSM.

n1kv-vsm-mgmt-mac

MAC address of the VSM's management TAP interface. This parameter is optional for the primary VSM, but required for the secondary VSM.

n1kv-vsm-pkt-mac:

MAC address of the VSM's packet TAP interface. This parameter is optional for the primary VSM.

n1kv-vsm-console-pts:

(Optional) Console port of the VSM VM.

n1kv-vsm-vm-vcpu:

(Optional) Number of vCPUs in the VSM VM. The default and recommended value is two vCPUs.

n1kv-vsm-disk-size:

(Optional) Disk size (GB) of the VSM VM.

n1kv-phy-intf-bridge:

(Optional) Host interface to which the VSM bridge is attached. The bridge connects the VSM with the upstream network. The default value is Ethernet 0 (eth0).

This example shows the primary and secondary VSMs with the n1kv-source defined as the Cisco PPA: 

vsm-primary:
n1kv-source: deb xxxxx | xxxx (variable)
n1kv-vsm-domain-id: 500
n1kv-vsm-password: nexus123
n1kv-vsm-mgmt-ip: 192.168.10.1
n1kv-phy-intf-bridge: eth2
n1kv-vsm-mgmt-gateway: 192.168.10.2
n1kv-vsm-mgmt-netmask: 255.255.255.0
n1kv-vsm-role: primary
n1kv-vsm-name: vsm-p
vsm-secondary:
n1kv-source: deb xxxxx | xxxx (variable)
n1kv-vsm-domain-id: 500
n1kv-vsm-password: nexus123
n1kv-phy-intf-bridge: eth2
n1kv-vsm-role: secondary
n1kv-vsm-name: vsm-s

This example shows the primary and secondary VSM with the n1kv-source defined as an HTTP server: 

vsm-primary:
n1kv-source: http://192.168.10.3/images/vsm-image-name.iso
n1kv-vsm-domain-id: 101
n1kv-vsm-password: nexus123
n1kv-vsm-name: vsm-primary
n1kv-vsm-role: primary
n1kv-vsm-ip: 192.168.10.4
n1kv-vsm-mgmt-netmask: 255.255.255.0
n1kv-mgmt-gateway: 192.168.10.5
.
.
.
vsm-secondary:
n1kv-source: http://192.168.10.6/images/vsm-image-name.iso
n1kv-vsm-domain-id: 101
n1kv-vsm-password: nexus123
n1kv-vsm-name: vsm-secondary
n1kv-vsm-role: secondary

.
.
.

Cisco Nexus 1000V for KVM VEM Charm Parameters

This table lists the Cisco Nexus 1000V for KVM VEM charm parameters. You define the parameters that will be the same among all of the VEMs in your network. For any parameters that you want to customize, you create a mapping file in YAML syntax in the MAAS node’s file system. In the mapping file, you configure a section for each node by using the host name ID, and you include any of the VEM configuration parameters listed in this table.

A typical usage for a custom mapping file is to configure certain nodes (for example, nova-compute or quantum-gateway nodes) with specific management or uplink interface settings. Another typical usage is to create VTEPs for VXLAN or VXLAN Gateway configurations on VEMs. If VTEPs are not configured using DHCP mode, the VTEPs need to be configured with static IP addresses using a custom mapping file.

Parameter

Description

n1kv-source: debian-pkg-location

Location of the Cisco Nexus 1000V for KVM VEM software.

The location that you define depends on whether you choose to have Juju download the VEM software (charm) automatically from the Cisco Personal Package Archive (PPA) or you choose to manually download the software from Cisco.com to a local HTTP server.

The VEM software is comprised of two Debian packages: a VEM DKMS package and a VEM data-path package. Juju downloads both automatically if you specify the Cisco PPA as the source. However, if you choose to manually download the software from Cisco.com, you must download both Debian packages.

For more information, see Downloading the Cisco Nexus 1000V Software.
Define the debian-pkg-location variable in one of the following two ways:

  • Cisco PPA—n1kv-source:  ppa:cisco-n1kv/n1kv-updates

  • Local HTTP server—http://server-address/VEM-DKMS.deb, http://server-address/VEM-DP.deb

vtep_config: virt port-name profile profile-name [mode static | dhcp [address ip-address]]

Virtual Tunnel Endpoint (VTEP) port configuration. Only static IP and MAC addresses are supported.

Note   

The port-name cannot exceed 11 alphanumeric characters. If it does, the VTEP does not come up.

n1kv-node_type: {compute | network}

Type of node that the VEM is intended to be installed on. The default value is compute.

n1kv-vtep_in_same_subnet: {yes | no}

Setting that indicates whether multiple VTEPs are located in the same subnet. The default value is no.

This example shows the VEM with the n1kv-source defined as the Cisco PPA: 

vem:
n1kv-source:  ppa:cisco-n1kv/n1kv-updates
vtep_config: 
node-type: network
vtep_in_same_subnet: yes
vtep_config:'virt vtep1-nw2 profile vxlan-vtep mode static address 192.168.10.2 netmask 255.255.0.0 mac 0e:1f:56:cf:82:53'
.
.
.

This example shows the VEM with the n1kv-source defined as an HTTP server: 

vem:
n1kv-source: http://192.168.10.1/images/VEM-DKMS.deb, http://server-address/VEM-DP.deb
vtep_config: 
node-type: network
vtep_in_same_subnet: yes
vtep_config:'virt vtep1-nw2 profile vxlan-vtep mode static address 192.168.10.2 netmask 255.255.0.0 mac 0e:1f:56:cf:82:53'
.
.
.

This example shows a mapping file with configuration parameters for two nodes. Each section is separated by the host name ID. Within each section, node-specific parameters are defined because they are different from the ones in the config.yaml file. 

maas-node-6:
  host_mgmt_intf: eth1
  uplink_profile: phys eth2 profile sys-uplink 
maas-node-11:
  host-mgmt-intf: eth0
  uplink_profile: phys eth3 profile sys-uplink
  node_type: network
  vtep_config:'virt vtep1-nw2 profile vxlan-vtep mode static address 6.0.8.253 netmask 255.255.0.0 mac 0e:1f:56:cf:82:53'

Cisco Nexus 1000V for KVM VXLAN Gateway Charm Parameters

For VXLAN Gateway, you need to define the source of the vxlan-gateway charm.


Note

The VXLAN Gateway feature has other configuration requirements, including the creation of VTEPs on the VEMs. You can use a common configuration for all VEMs if you use DHCP to assign IP addresses to all of the VTEPs, or you can use a mapping.yaml file. For more information about creating VTEPs using a mapping.yaml file, see Cisco Nexus 1000V for KVM VEM Charm Parameters.

The following table lists the Cisco Nexus 1000V for KVM VXLAN Gateway charm parameter that you need to define in the global configuration file.

Parameter

Description

n1kv-source: debian-pkg-location

Location of the VXLAN Gateway software. The location that you define depends on whether you choose to have Juju download the VXLAN Gateway software (charm) automatically from the Cisco Personal Package Archive (PPA) or you choose to manually download the software from Cisco.com to a local HTTP server. For more information, see Downloading the Cisco Nexus 1000V Software.

Define the debian-pkg-location variable in one of the following two ways:

  • Cisco PPA—n1kv-source:  ppa:cisco-n1kv/n1kv-updates

  • Local HTTP server—http://server-address/VXGW-image.qcow

This example shows the VXLAN Gateway with the n1kv-source defined as the Cisco PPA: 

vxlan-gateway:
  n1kv-source:  ppa:cisco-n1kv/n1kv-updates
.
.
.

This example shows the VXLAN Gateway with the n1kv-source defined as an HTTP server: 

vxlan-gateway: 
  n1kv-source: https://192.168.10.1/images/VXGW-image.qcow
.
.
.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco