This chapter contains the following sections:
Add the virtual account.
For information about adding virtual account, see Creating a Virtual Account
Install Cisco Prime Network Services Controller (PNSC) using Install PNSC action button.
For information about installing Cisco PNSC, see the Installing Cisco Prime Network Services Controller.
Install Cisco Nexus 1000V using the Install Nexus 1000V action button. Cisco Nexus 1000V is automatically registered with Cisco UCS Director when you install the switch.
For information about installing Cisco Nexus 1000V, see Installing Cisco Nexus 1000V.
Enable Cisco Nexus 1000V forwarding on each virtualized server in the vCenter deployment using the Add Host action button.
For information about adding hosts, see Adding Hosts.
After a successful installation of the Cisco VACS license, Cisco UCS Director enables you to do a new installation of Cisco PNSC. Cisco PNSC is the policy manager for Virtual Security Gateway for traffic between the virtual machines in one virtual cloud account.
![]() Note | The Help link provides you access to the corresponding online help. |
Have the administrator privileges to install Cisco PNSC.
Ensure that Cisco PNSC and any associated Cisco Nexus 1000V switches are not installed on the same virtual account in Cisco UCS Director. Cisco PNSC and the Cisco Nexus 1000V must not be pre-installed on the virtual accounts on which you plan to install these components using Cisco VACS.
Know the location information (data center and IP address) of the host on which you are deploying the Cisco PNSC.
Know the virtual machine resources (management port group and data store) for the Cisco PNSC virtual machine.
Know the DNS and Network Time Protocol (NTP) server information.
Ensure that the data store has sufficient storage space.
Step 1 | From the Cisco UCS Director menu bar, choose . The Cisco VACS management task icons appear. | ||||||||||||||||||||||||||
Step 2 | Click
Install
PNSC.
The
Install
PNSC wizard appears.
![]() | ||||||||||||||||||||||||||
Step 3 | In the
Name and
Location Specification
screen, complete the following fields.
| ||||||||||||||||||||||||||
Step 4 | Click Next. | ||||||||||||||||||||||||||
Step 5 | In the
Placement
and Network Specification screen, complete the following fields.
| ||||||||||||||||||||||||||
Step 6 | click Next. | ||||||||||||||||||||||||||
Step 7 | In the
Install PNSC Summary screen, verify the details of the installation.
If the details are correct, click
Submit. Otherwise, click
Back
to go back to a previous step and modify the details.
| ||||||||||||||||||||||||||
Step 8 | View the
progress of the installation and deployment of Cisco PNSC by choosing the
Service
Request tab, you can view the
Workflow Status or
Logs to determine the status of the installation and
troubleshoot problems.
. In the
|
After successfully installing Cisco PNSC, the Cisco VACS solution enables you to install a Cisco Nexus 1000V switch. You can install multiple Cisco Nexus 1000V switches. Each of these instances are registered with Cisco PNSC that was installed by the Cisco VACS solution.
![]() Note |
|
![]() Note | The Help link provides you access to the corresponding online help. |
You must be a system administrator with full privileges to perform this task.
Set aside one IP address for the VSM and one IP address for the Cisco Virtual Switch Update Manager (Cisco VSUM). Cisco VSUM is the Cisco Nexus 1000V installer.
Set aside virtual machine resources (port groups and datastores) for the installer virtual machine, the primary VSM, and the secondary VSM.
Each VSM (primary and secondary) must have the following minimum system requirements:
The Cisco VSUM must have the following minimum system requirements:
Reserve a unique numeric domain ID for the Cisco Nexus1000V switch.
Step 1 | From the Cisco UCS Director menu bar, choose The . Cisco VACS management task icons appear. | ||||||||||||||||||||
Step 2 | Click
Install
Nexus 1000V.
The
Cisco Nexus 1000V
wizard appears.
![]() | ||||||||||||||||||||
Step 3 | In the
Name and
Location Specification
screen, complete the following fields, and then click
Next:
| ||||||||||||||||||||
Step 4 | In the
Placement
and Network Specification screen, complete the following tasks, and
then click
Next:
| ||||||||||||||||||||
Step 5 | In the
VSM
Deployment Information
screen, complete the following tasks and then click
Next:
| ||||||||||||||||||||
Step 6 | In the
VSM
Host Selection screen, complete the following tasks and then click
Next:
| ||||||||||||||||||||
Step 7 | In the
VSM
Port Group
screen, complete the following tasks and then click
Next:
| ||||||||||||||||||||
Step 8 | In the
SVS
Domain and Server Setup Specification screen, complete the following
tasks and then click
Next.
| ||||||||||||||||||||
Step 9 | In the
VSM
Profile Specification
screen, complete the following tasks and then click
Next.
| ||||||||||||||||||||
Step 10 | In the
Install Nexus1000V Summary screen, verify the details of the
installation. If the details are correct, click
Submit. Otherwise, click
Back
to go back to a previous step and modify the details.
After clicking Submit, a dialog box shows a service request number that can be used to track the progress of the Workflow, as described in the next step.
| ||||||||||||||||||||
Step 11 | View the progress of the installation and deployment of the VSM by clicking on the Service Request tab, you can view the Workflow Status or Logs to determine the status of the installation and troubleshoot problems. . In the | ||||||||||||||||||||
Step 12 | If the deployment tasks is successful, but the Config VSM task fails, then you must resubmit the workflow from the Config VSM task to complete the installation. |
Adding hosts to Nexus 1000V DVS is a complex operation. This section describes the scope of the Add Hosts wizard and how to translate your intended usage into proper choices.
Specifying a Nexus 1000V DVS and the host that is being added to it.
Using a port profile editor to view the existing port profiles and to create new port profiles in case the existing ones are inadequate for your purpose. For an overview of the Cisco Nexus1000V port profiles, see the http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus1000/sw/5_2_1_s_v_3_1_1/port_profile/config/b_Cisco_N1KV_VMware_Port_Profile_Config_521SV311.html
Selecting one or more physical interfaces of the host to migrate to the virtual switch and attaching the right port profile to each one.
Establishing a VM kernel NIC for Cisco Nexus1000V control traffic.
Optionally migrating previously created virtual kernel NICs (vmknics).
Creating one or more (upto a maximum of four) VM kernel NICs for VXLAN encapsulation. In VXLAN terminology, these VM Kernel NICs serve the role of VTEPs, which are the VXLAN Tunnel End Points.
Optionally migrating some or all of the Virtual Machines that may already be present on the host.
Physical port profiles
These contain attributes relevant to the physical interfaces. You can set up a physical port profile to carry multiple VLANs. One of these vlans must be designated as the native VLAN. Traffic on the native VLAN travels on the wire, without 802.1Q encapsulation. A virtual port profile for the purposes of the 'Add Host' wizard can carry traffic on just one VLAN. For any virtual interface, irrespective of whether it is the interface of a VM or a VM Kernel NIC, you can associate a particular virtual port profile only if the VLAN it specifies, has been included in one of the physical port profiles associated with one of the physical interfaces. The VLAN associated with any virtual interface on a host must be carried on one of the physical interfaces of that host.
Physical port profiles also specify if the interfaces that they attach to form a logical bundle and if they do, whether it is a bundle of type '5 tuple hash-based static portchannel' or of type 'MAC Pinning'. For an understanding of what these interface types are, see the http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus1000/sw/5_2_1_s_v_3_1_1/interfaces/config/b_Cisco_N1KV_VMware_Interface_Config_521SV311/b_Cisco_Nexus_1000V_Interface_Configuration_Guide_Release_4_2_1_SV_2_2_1_chapter_0110.html
Virtual port profiles
These contain attributes suitable for VMs or VM Kernel NICs. A specially designated virtual Kernel NIC must be established on each host to exchange management and control signals with the Cisco Nexus1000V Virtual Supervisor Module (VSM). The simplest way is to specify migrating the pre-existing management VM Kernel NIC (usually named vmk0). Alternatively you can create a VM Kernel NIC expressly for this purpose. If you exercise the latter option, we recommend that these specifically created VM Kernel NICs belong to the same VLAN and have IP addresses in the same subnet as the management interface of the VSM module. It is not necessary to ensure this when you are simply choosing to use the management VM Kernel NIC as the control VM Kernel NIC.
You must follow this simple rule for creating VTEP VM Kernel NICs. If the physical interfaces of a host are not in a MAC pinning mode port channel, a single VTEP NIC suffices. If they are in MAC Pinning mode, you can create as many VTEP VM Kernel NIcs as the number of physical interfaces being migrated on that host. Moreover, all VTEP NICs on all hosts in a single virtual switch must be in the same VLAN and the same subnet.
The Cisco VACS Add Host wizard will try to restrict you to legitimate choices. For instance, it will try to detect which VLAN is native on each physical interfaces that you want to migrate. It will also try to discover which VLAN the management VMKernel NIC is on in case you choose to re-use it as the control VM Kernel NIC. However there are times when these automatic discovery attempts can fail. You must ensure correct choices for native VLANs of the physical interfaces as well as the VLAN for the control VM Kernel NIC.
After a successful installation of the Cisco VACS license and Cisco Nexus 1000V, you can install Cisco Nexus 1000V Virtual Ethernet Module (VEM) for a VMware ESXserver .
![]() Note |
|
Before beginning the Cisco Nexus 1000V VEM software installation, you must know or do the following:
Step 1 | From the Cisco UCS Director menu bar, choose . The Cisco VACS management task icons appear. | ||||||||||||||||||||
Step 2 | Click
Add
Host.
The
Add
Host wizard appears.
![]() | ||||||||||||||||||||
Step 3 | In the
Host
Location Specification
screen, complete the following fields :
| ||||||||||||||||||||
Step 4 | Click Next. The Port Profle Configuration screen appears. | ||||||||||||||||||||
Step 5 | In the
Port
Profle Configuration screen, review the port profiles that can be
used by the physical interfaces (PNIC) or the virtual interfaces (VNIC).
The Port Profle Configuration screen lets you view or create port profiles. These port profiles are applied to the physical interfaces that you want to add to the virtual switch or to the virtual interfaces of the VMs. The Port Profile table lists the existing port profiles and displays some suggested port profiles for the selected host. You can modify or delete the suggested port profiles, or add new ones. After you finish managing the port profiles, you are prompted to apply them to the host’s physical interfaces or to the VMs on the host that you want to migrate to the Cisco Nexus 1000V. Any newly created port profiles in this list that are not assigned to any interface—physical or virtual—do not persist on the switch. Before exiting this screen, ensure that suitable port profiles exist for all the physical server ports that you intend to migrate to the Cisco Nexus 1000V. If the UI does not pre populate the Port Profile table with suitable port profiles, you must add them manually.
For Ethernet port profiles, only static port channel and virtual port channel host mode (vPC -HM) is supported. The list of port profiles is displayed. You can modify or delete the suggested port profiles, or add new port profiles. If you want to add more port profiles, click + and fill in the following details in the Add Entry to Port Profile screen. If you want to modify an existing port profile, then select the appropriate port profile and click the edit (pencil) icon which is located next to + and modify the existing field. | ||||||||||||||||||||
Step 6 | In the
Add
Entry to Port Profile screen, complete the following fields:
| ||||||||||||||||||||
Step 7 | Click Next on the Port Profile Configuration screen after you have modified or added the required port profiles. . The Physical NIC Migration Configuration screen appears. | ||||||||||||||||||||
Step 8 | In the
Physical NIC Migration Configuration screen, you can
view all the PNICs present in the host, with a suggested port-profile mapped to
it and the migration to be set to true.
Setting the migration flag to a value of true indicates that the corresponding PNIC will be migrated to Cisco Nexus 1000V. | ||||||||||||||||||||
Step 9 | To edit the
Port-profile mapping, migration status, or the container traffic check for an
existing PNIC, select the appropriate PNIC and click the
edit
(pencil) icon and modify the existing fields.
It is necessary that you enable at least one physical NIC to use for container traffic. If you do not enable it, you cannot proceed with the wizard. | ||||||||||||||||||||
Step 10 | (Optional) In the
Edit
Physical NICs Entry screen, modify the existing fields, and then
click
Submit.
| ||||||||||||||||||||
Step 11 | In the Physical NIC Migration Configuration screen, click Next. The Kernel NIC Migration Specification screen appears. | ||||||||||||||||||||
Step 12 | In the
Kernel
NIC Migration Specification screen, complete the following fields:
Each host in a Cisco Nexus 1000V virtual switch must set up a virtual kernel NIC (VMKNIC) to carry the control protocol between the host software and the VSM. In Cisco Nexus 1000V terminology, this VMKNIC is referred to as the L3 control VMKNIC of the host. This screen enables you to set up and configure the L3 control VMKNIC for the host and also provides you an option to migrate the existing VMKNICs from the vswitch to Nexus1000V DVS.
| ||||||||||||||||||||
Step 13 | (Optional) If you want to modify the attributes of an existing VMKNIC, then select the appropriate VMKNIC, and then click the edit (pencil) icon and modify the existing fields. | ||||||||||||||||||||
Step 14 | (Optional) In the
Edit VM
KNICs Entry screen, modify the existing fields, and then click
Submit.
| ||||||||||||||||||||
Step 15 | (Optional) If
you want to add new VMKNICs instead of using existing VMKNICs, then uncheck the
Migrate Kernel NICs check box and complete the
following fields:
| ||||||||||||||||||||
Step 16 | Click Next. The VXLAN VTEP Interfaces screen appears. | ||||||||||||||||||||
Step 17 | In the
VXLAN
VTEP Interfaces screen, click
+ to add entries to the list of VXLAN VTEP
interfaces list.
VXLAN operation requires that each host have one or more Virtual Tunnel End Points (VTEPs). These are represented as vmknics. If the host has data-capable physical interfaces configured in a static port channel mode, then a single VTEP suffices. If the host has one or more physical interfaces configured using the Mac Pinning configuration, then the user can accordingly create as many VTEPs as there are physical interfaces in the MAC pinning configuration. Creating fewer VTEPs results in underutilization of the physical bandwidth that is available to the host.
You must choose a sufficiently large IP subnet as all the VTEPs of all the hosts added to a single Nexus1000V DVS will belong to the same subnet. This cannot be edited in the UI and the add host process will not proceed further if the IP addresses of the provided subnet are completely utilized. | ||||||||||||||||||||
Step 18 | Click Next. | ||||||||||||||||||||
Step 19 | In the
VM
Migration Configuration screen, select the VM NIC to migrate and
click
Next. If you want to edit an entry, click the
Pencil icon and complete the following tasks in the
Edit VM
NICs to Migrate screen:
| ||||||||||||||||||||
Step 20 | Click Next. | ||||||||||||||||||||
Step 21 | In the
Add
Host Summary Information screen, verify the details of the host
added. If the details are correct, click
Submit. Otherwise, click
Back
to go back to a previous steps and modify the details.
After clicking Submit, a pop-up window appears that shows a service request number that can be used to track the progress of the Workflow, as described in the next step. | ||||||||||||||||||||
Step 22 | You can view
the progress of adding hosts, by clicking on the
Service
Request tab, you can view the
Workflow Status or
Logs to determine the status of the installation and
troubleshoot problems.
. In the
|