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:
This document describes how to install Cisco Nexus 1000V InterCloud. The Cisco Nexus 1000V InterCloud software is available at the download URL location provided with the software. The Cisco Nexus 1000V InterCloud software package contains the following contents:
Software | Image Name |
---|---|
Cisco Nexus 1000V InterCloud VSM |
n1000v-dk9.5.2.1.SK1.1.1.ova |
Cisco Prime Network Services Controller image |
nsc.3.0.1x.ova |
InterCloud Extender image |
n1000v-dk9.5.2.1.IC1.1.1.ova |
InterCloud Switch image |
n1000v-dk9.5.2.1.IC1.1.1.img |
InterCloud Agent image |
ica-5.2.1.IC1.1.1.<OS>.<version>.<arch>.rpm The images for the following OS versions and architecture are included: ica-version.win2k8r2.x86_64.zip icaami-version.win2k8r2.x86_64.zip |
Note |
You need to unzip the file before you begin the installation process. |
Note |
The AWS IP address in the desired region need to be open. See https://forums.aws.amazon.com/ann.jspa?annID=1701. |
See the Cisco Prime Network Services Controller Quick Start Guide for more information.
Note |
The management port profile may be the same port profile that is used for the Cisco Nexus 1000V VSM on the enterprise. The port profile is configured in the VSM and is used for the Cisco Prime Network Services Controller management interface. |
See the Cisco Prime Network Services Controller Quick Start Guide for more information.
You require the following software to install Cisco Nexus 1000V InterCloud
Installing Cisco Nexus 1000V InterCloud consists of the following steps. After completing each procedure, return to this section to make sure that you have completed all required procedures in the correct sequence.
Step 1 |
Installing Cisco Prime Network Services Controller using OVA. See Installing Cisco Prime Network Services Controller Using OVA. See the Cisco Prime Network Services Controller Quick Start Guide for more information about installing Cisco Prime Network Services Controller. |
Step 2 |
Registering the VM Manger (vCenter) with Cisco Prime Network Services Controller. See Registering VM Manager with Cisco Prime Network Services Controller. |
Step 3 | Installing Cisco Nexus 1000V VSM for InterCloud. |
Step 4 |
Configuring port profiles in the Cisco Nexus 1000V VSM for InterCloud. See Configuring Port Profiles. See the Cisco Nexus 1000V Port Profile Configuration Guide for information about port profiles. |
Step 5 |
Registering Cisco Nexus 1000V InterCloud Switch with Cisco Prime Network Services Controller. See Registering Cisco Nexus 1000V VSM for InterCloud with Cisco Prime Network Services Controller. |
Use this procedure to configure port profiles in the Cisco Nexus 1000V InterCloud VSM and the Cisco Nexus 1000V VSM in the enterprise.
In the Cisco Nexus 1000V InterCloud VSM for InterCloud, you will need to configure the following port profiles:
Note |
You will need to configure this port profile, if you select the Advanced Option in the Cisco Prime Network Services Controller for separate tunnel interface. If you do not select the Advanced Option, then management interface will be used for tunnel interface. |
Note |
The VLANs specified in the trunk port profile for internal tunnel trunk interfaces for InterCloud Extender and InterCloud Switch should exist in the trunk port profile for InterCoud Extender enterprise trunk interface. |
Step 1 |
Configuring port profiles for the Cisco Nexus 1000V VSM in the enterprise. See the Cisco Nexus 1000V Port Profile Configuration Guide for information about configuring port profiles. |
Step 2 |
Configuring trunk port profile for internal tunnel trunk interfaces for InterCloud Extender and InterCloud Switch. See Configuring Trunk Port Profile for InterCloud Extender and InterCloud Switch. |
Step 3 |
Configuring access port profile for InterCloud Switch management interface. See Configuring Access Port Profile For InterCloud Switch Management Interface. |
Step 4 |
Configuring access port profile for data traffic for VMs in InterCloud. See Configuring Access Port Profile for Virtual Machine Data Traffic. |
Use this procedure to configure trunk port profile for internal tunnel trunk interfaces for InterCloud Extender and InterCloud Switch.
This example shows how to configure a default trunk port profile for InterCloud Extender:
switch# configure terminal switch(config)# port-profile port-profile type vethernet N1K_Cloud_Default_Trunk switch(config-port-prof)# switchport mode trunk switch(config-port-prof)# switchport trunk allowed vlan 72,2315-2350 switch(config-port-prof)# no shutdown switch(config-port-prof)# state enabled switch(config-port-prof)# max ports 64 switch(config-port-prof)# description port profile created for N1000V internal usage switch(config-port-prof)# system vlan 72 switch(config-port-prof)# publish port-profile switch(config-port-prof)#
This example shows how to configure a trunk port profile for InterCloud Extender:
switch# configure terminal switch(config)# port-profile port-profile type vethernet Trunk_To_Cloud switch(config-port-prof)# switchport mode trunk switch(config-port-prof)# switchport trunk allowed vlan 72,2315-2350 switch(config-port-prof)# no shutdown switch(config-port-prof)# state enabled switch(config-port-prof)# max ports 64 switch(config-port-prof)# system vlan 72 switch(config-port-prof)# publish port-profile switch(config-port-prof)#
Use this procedure to configure access port profile for InterCloud Switch management interface.
Step 1 |
switch# configure terminal Enters global configuration mode. |
||
Step 2 |
switch(config)# [no] vlan vlan-id Creates or deletes, and saves in the running configuration, a VLAN or a range or VLANs. |
||
Step 3 |
switch(config)# port-profile type vethernet name Enters port profile configuration mode for the named port profile. If the port profile does not already exist, it is created using the following characteristics: |
||
Step 4 |
switch(config-port-prof)# switchport mode access Sets port mode access. |
||
Step 5 |
switch(config-port-prof)# switchport access vlan [vlan-id-access] Assigns an access VLAN ID to this port profile.
|
||
Step 6 |
switch(config-port-prof)# no shutdown Administratively enables all ports in the profile. |
||
Step 7 |
switch(config-port-prof)# state enabled Enables the port profile and applies its configuration to the assigned ports. |
||
Step 8 |
switch(config-port-prof)# system vlan vlan-id Adds system VLAN to this port profile. Specify the VLAN as configured in step 5. |
||
Step 9 |
switch(config-port-prof)# publish port-profile <name> Publishes port profile to Cisco Prime Network Services Controller. |
||
Step 10 |
(Optional)switch(config-port-prof)# copy running-config startup-config Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
This example shows how to configure a port profile for InterCloud Switch management interface:
switch# configure terminal switch(config)# port-profile type vethernet mgmt-access switch(config-port-prof)# switchport mode access switch(config-port-prof)# switchport access vlan 72 switch(config-port-prof)# no shutdown switch(config-port-prof)# state enabled switch(config-port-prof)# system vlan 72 switch(config-port-prof)# publish port-profile mgmt-access switch(config-port-prof)#
Use this procedure to configuring access port profile for data traffic for VMs in the cloud.
Step 1 |
switch# configure terminal Enters global configuration mode. |
||
Step 2 |
switch(config)# [no] vlan vlan-id Creates or deletes, and saves in the running configuration, a VLAN or a range or VLANs. |
||
Step 3 |
switch(config)# port-profile type vethernet name Enters port profile configuration mode for the named port profile. If the port profile does not already exist, it is created using the following characteristics: |
||
Step 4 |
switch(config-port-prof)# switchport mode access Sets port mode access. |
||
Step 5 |
switch(config-port-prof)# switchport access vlan [vlan-id-access] Assigns an access VLAN ID to this port profile.
|
||
Step 6 |
switch(config-port-prof)# no shutdown Administratively enables all ports in the profile. |
||
Step 7 |
switch(config-port-prof)# state enabled Enables the port profile and applies its configuration to the assigned ports. |
||
Step 8 |
switch(config-port-prof)# publish port-profile <name> Publishes port profile to Cisco Prime Network Services Controller. |
||
Step 9 |
(Optional)switch(config-port-prof)# copy running-config startup-config Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
This example shows how to configure a port profile for VM data traffic in the Cisco Nexus 1000V InterCloud VSM for InterCloud:
switch# configure terminal switch(config)# port-profile type vethernet CSW_2318 switch(config-port-prof)# switchport mode access switch(config-port-prof)# switchport access vlan 2318 switch(config-port-prof)# no shutdown switch(config-port-prof)# state enabled switch(config-port-prof)# publish port-profile CSW_2318 switch(config-port-prof)#
Use this procedure to install Cisco Prime Network Services Controller using OVA.
Step 1 | Choose the host on which to deploy the Cisco Prime Network Services Controller virtual machine. |
Step 2 |
From the File menu, select Deploy OVF Template. The Deploy OVF Template window opens. |
Step 3 |
In the Deploy from a file or URL field, enter the path to the Cisco Prime Network Services Controller OVA file and click Next. The OVF Template Details window opens. |
Step 4 |
Click Next. The End User License Agreement window opens. |
Step 5 |
Click Accept to accept the End User License Agreement and then click Next. The Name and Location window opens. |
Step 6 |
In the Name field, enter the name of the Cisco Prime Network Services Controller. The name can contain up to 80 characters and must be unique within the inventory folder. |
Step 7 |
In the Inventory Location pane, select the location that you would like to use and click Next. The Deployment Configuration window opens. |
Step 8 |
From the Configuration drop-down list, select Installer and click Next. The Host/Cluster window opens. |
Step 9 |
Select the host to install the Cisco Prime Network Services Controller VM. The Storage window opens. |
Step 10 |
In the Datastore pane, choose the datastore for the VM and click Next. The Disk Format window opens. |
Step 11 |
Click either Thin provisioned format or Thick provisioned format radio-button to store the VM vdisks and click Next. The Network Mapping window opens. |
Step 12 |
In the network mapping pane, select the management network port profile for the VM and click Next. The Properties window opens. |
Step 13 |
In the Properties pane, enter the following:
Ignore the Cisco Prime Network Services Controller Restore configuration. Click Next.The Ready to Complete window opens. |
Step 14 |
In the Ready to Complete window, review the deployment settings information and click Finish. Power on the VM after the VM deployment is complete. |
You can use your browser to connect to the Cisco Prime Network Services Controller.
You have installed Cisco Prime Network Services Controller.
Step 1 |
Open a browser. In the browser Address field, enter the IP address that you designated for your Cisco Prime Network Services Controller instance and click Enter. A Website Security Certification window opens. Add a security exception to proceed to the login page for Cisco Prime Network Services Controller. |
Step 2 | Using the appropriate username and password, log into the Cisco Prime Network Services Controller. |
Step 3 | In the Virtual Network Management Center, click . |
Step 4 | In the VM Managers window, click Export vCenter Extension and save the file. |
Step 5 |
In the vSphere Client window, click The Plug-in Manager window opens. |
Step 6 |
In the Available Plug-ins pane, right-click to chooseNew Plug-in. The Register Plug-in window opens. |
Step 7 | In the Register Plug-in window, click Browse to select the Cisco Prime Network Services Controller vCenter extension file. |
Step 8 | Click Register Plug-in. |
Step 9 |
Click Ignore on the security warning message. When the registration has completed successfully, a message is displayed. |
Step 10 | Click OK and close the Plug-in window. |
Step 11 | In the Virtual Network Management Center, click . |
Step 12 |
In the VM Managers pane, click Add VM Manager. The Add VM Manager window appears. |
Step 13 | In the VM Managers pane, enter the following information: |
Step 14 |
Click OK. The registration is successful, if in the VM managers pane, the Operational State of the VM Manager is stated as UP. |
Use this procedure to install the Cisco Nexus 1000V VSM for InterCloud.
You have the following information:
Step 1 | In the vSphere Client, choose . |
Step 2 | In the Source screen, specify the location of the OVA file n1000v-dk9.5.2.1.SK1.1.0.0.ova and click Next. |
Step 3 | The OVF Tempalte Details screen opens displaying product information, including the size of the file and size of the VM disk. |
Step 4 | Click Next. |
Step 5 | Read the Cisco Nexus 1000V License Agreement. |
Step 6 | Click Accept and then click Next. |
Step 7 |
Add the VSM name, choose the folder location within the inventory where it will reside and then click Next. The name for the VSM must be unique within the inventory folder and less than 80 characters. |
Step 8 |
From the Configuration drop-down list, choose Nexus 1000V Installer. This choice configures the primary VSM using the GUI setup dialog. |
Step 9 | Click Next. |
Step 10 | Choose the data center or cluster on which to install the VSM. |
Step 11 | Click Next. |
Step 12 |
Choose the datastore in which to store the file if one is available. On this page, you choose from datastores already configured on the destination cluster or host. The virtual machine configuration file and virtual disk files are stored on the datastore. Choose a datastore large enough to accommodate the virtual machine and all of its virtual disk files. |
Step 13 | Click Next. |
Step 14 | Choose Thick provisioned disk format for storing virtual machine virtual disks, and click Next. |
Step 15 | In the Network Mapping screen, choose the networks that are present in your inventory. |
Step 16 | Click Next. |
Step 17 | Specify the following properties for your primary VSM: |
Step 18 | Click Next. |
Step 19 |
Verify the configuration and then click Finish. A status bar displays as the VM installation progresses. |
Step 20 |
Click Close. You have completed installing the Cisco Nexus 1000V software. |
Step 21 |
Right-click the VSM and then choose Open Console. You have completed installing the Cisco Nexus 1000V software. |
Step 22 | Click the green arrow to power on the VSM. |
Step 23 |
Enter the following commands at the VSM prompt:
switch# configure terminal switch(config)# setup |
Step 24 |
Enter the HA role. If you do not specify a role, standalone is assigned by default. This example shows the HA role as primary. Enter HA role[standalone/primary/secondary]: primary [#########################################] 100% ---- Basic System Configuration Dialog ---- This setup utility will guide you through the basic configuration of the system. Setup configures only enough connectivity for management of the system. *Note: setup is mainly used for configuring the system initially, when no configuration is present. So setup always assumes system defaults and not the current system configuration values. Press Enter at anytime to skip a dialog. Use ctrl-c at anytime to skip the remaining dialogs. Would you like to enter the basic configuration dialog (yes/no): This example shows the HA role as secondary. Enter HA role[standalone/primary/secondary]: secondary Setting HA role to secondary will cause a system reboot. Are you sure (yes/no) ? : |
Step 25 | Do one of the following: If you are setting up the primary/active VSM, go to Step 17. |
Step 26 |
If you have set up the VSM virtual machine (VM) to boot from the CD-ROM, and are installing the secondary VSM from the ISO image attached to your CD-ROM, remove the virtual CD-ROM now so that the VSM does not boot from the CD. This step is necessary if you have set up the VSM VM to boot from the CD-ROM before the hard drive. |
Step 27 |
If you are setting up the secondary/standby VSM, when prompted to reboot the VSM, answer yes. The secondary VSM VM is rebooted and brought up in standby mode. The password on the secondary VSM is synchronized with the password on the active/primary VSM. Any configuration made on the active/primary VSM is now automatically synchronized with the standby. This example show the system rebooting when the HA role is set to secondary. Setting HA role to secondary will cause a system reboot. Are you sure (yes/no) ? :y [########################################] 100% HA mode set to secondary. Rebooting now... You have completed this procedure for the secondary VSM. |
Step 28 |
Enter yes to enter the basic configuration dialog. Would you like to enter the basic configuration dialog (yes/no): yes |
Step 29 |
Enter no to create another login account. Create another login account (yes/no) [n]: no |
Step 30 |
Enter no to configure a read-only SNMP community string. Configure read-only SNMP community string (yes/no) [n]: no |
Step 31 |
Enter no to configure a read-write SNMP community string. Configure read-write SNMP community string (yes/no) [n]: no |
Step 32 |
Enter no to configure a read-write SNMP community string. Configure read-write SNMP community string (yes/no) [n]: no |
Step 33 |
Enter a name of the switch. Enter the switch name: n1000v |
Step 34 |
Enter yes to configure out-of-band management and then enter the mgmt0 IPv4 address and subnet mask. Continue with Out-of-band (mgmt0) management configuration? [yes/no] [y]: yes Mgmt0 IPv4 address: 172.28.15.152 Mgmt0 IPv4 netmask: 255.255.255.0 |
Step 35 |
Enter yes to configure the default gateway. Configure the default-gateway: (yes/no) [y]: yes IPv4 address of the default gateway : 172.23.233.1 |
Step 36 |
Enter no to configure advanced IP options. Configure Advanced IP options (yes/no)? [n]: no |
Step 37 |
Enter yes to enable the Telnet service. Enable the telnet service? (yes/no) [y]: yes |
Step 38 |
Enter yes to enable the SSH service and then enter the key type and the number of key bits. Enable the ssh service? (yes/no) [y]: yes Type of ssh key you would like to generate (dsa/rsa) : rsa Number of key bits <768-2048> : 1024 |
Step 39 |
Enter yes to enable the HTTP server. Enable the http-server? (yes/no) [y]: yes |
Step 40 |
Enter no to enable the NTP server. Configure NTP server? (yes/no) [n]: yes |
Step 41 |
Enter yes to to configure the SVS domain parameters and then enter the mode (L2 or L3), and the control and packet VLAN IDs. Configure svs domain parameters? (yes/no) [y]: yes Enter SVS Control mode (L2 / L3) : L3 |
Step 42 |
Enter yes to configure the VEM feature level and then enter 0 or 1 . feature level will be set to 4.2(1)SV2(1.1), Do you want to reconfigure? (yes/no) [n] Current vem feature level is set to 4.2(1)SV2(1.1) You can change the feature level to: vem feature level is set to the highest value possible The system now summarizes the complete configuration and asks if you want to edit it. The following configuration will be applied: Switchname n1000v interface Mgmt0 ip address 172.28.15.152 255.255.255.0 no shutdown no telnet server enable ssh key rsa 1024 force ssh server enable feature http-server svs-domain svs mode L3 control vlan 1 packet vlan 1 domain id 101 |
Step 43 |
Do one of the following:
Would you like to edit the configuration? (yes/no) [n]:no |
Step 44 |
Enter yes to use and save this configuration. If you do not save the configuration now, none of your changes will be part of the configuration the next time that the switch is rebooted. Enter yes to save the new configuration and to ensure that the kickstart and system images are also automatically configured. Use this configuration and save it? (yes/no) [y]: yes [########################################] 100% |
After Installing the Cisco Nexus 1000V in the provider cloud, you must register the Cisco Nexus 1000V VSM with Cisco Prime Network Services Controller.
Step 1 |
On the Cisco Nexus 1000V VSM for InterCloud CLI, enter the following commands: switch# configure terminal switch(config)# nsc-policy-agent switch(config-nsc-policy-agent)# registration-ip 10.106.192.192 switch(config-nsc-policy-agent)# shared-secret Example_Secret123 switch(config-nsc-policy-agent)# policy-agent-image bootflash:/vsmcpa.<filename>.bin switch(config)# copy running-config startup-config switch(config)# exit |
Step 2 |
Verify if the registration is successful by entering the show nsc-pa status command. This example shows that the Cisco Prime Network Services Controller is reachable : switch# show nsc-pa status NSC Policy-Agent status is - Installed Successfully. Version 3.0(0.33)-vsmc The Cisco Nexus 1000V VSM for InterCloud is now registered with the Cisco Prime Network Services Controller. |