Enter the IP Address and user name and password for the vCenter server credentials, and at the lower left hand section you'll see a status indication.

Click on the browse radio button and it will open another windows where you can pick the host you want.

Same action for the Datastore, click the Browse button and choose the correct DataStore.

Choose the correct vSwtich in the same manner as the host and datastore.

For the second host you can also Key in the values if you know them without browsing. You'll also name the VDS and enter the credentials for the N1Kv, and finally choose the OVA file for the VSM.

The next section you have to choose Layer 2 (older way) and Layer 3 Connectivity. Layer 2 as you would think all VSM's and VEM's have to be on the same subnet. Layer 3 you could have VSM's in a main DC and the VEM's in another data center in different subnets. The Layer 3 option also gives you more trouble shooting advantages; such as ping and trace route.

Control Port Group used for 

    VEM to VSM Heartbeats

Management 

It will now give you the option to review the configuration before moving on. Click next...

You can now see that it's deploying the secondary VSM after already deploying successfully the Primary VSM.

You can see now that the Nexus 1000V plug-in is installed.

You can see that the N1000 V has added the VSM-MGMT switch to the standard switch layout.

The installation will go through the check list.

Final choices to add additional modules. Click Next... You can also add a VIB (vSphere Installation Bundle) file to add the VEM sat this time is you would like.

In this section you can migrate hosts over to the VSM, but it's better to do in manually. So you would just close the program.

You should be able to know log into the N1KV and issue the command "show module" and it will give you all the information that was just configured.

Here is the "show run" You can see it's only running the Essential's version (no DAI or DHCP Snooping SGT, SGACL's)

Next you would need to deploy the VEM's (virtual ethernet modules)

conf t

vlan 4093

name MGMT

vlan 110

name VM-Guests

port-profile type ethernet VM-Sys-Uplink

vmmware port-group

no shut

switchport mode trunk

switchport trunk allowed vlan 1,4093

system vlan 1,4093

state enable d

vlan 115

name vMotion 

port-pr type ethernet Vmotion-Uplink 

vmware port-group

no shut 

switchport mode trunk

switchport trunk allowed vlan 115

system vlan 115

state enabled

port-profile type ethernet VM-Guests

vmware port-group

no shut

switchport mode trunk

switchport trunk allowed vlan 110

state enabled

copy run start (this will save to both VSM's)

As you can see from the above example, the changes we made from the N1Kv is now showing up in Vcenter.

Know you can add a host by right clicking on the N1K and click Add Host

In this example we are moving every other vmnic from the standard vswtich to the N1Kv VDS and choosing the uplink port from the port groups we created earlier.

It should look the the following, when you click next it will migrate these selected vmnics to the N1Kv VDS.

HINT: Make sure you don't overlap VLAN's for the ethernet port profiles, VMWare doesn't care for those.

This is a warning that while migrating the host ports vmnics might look connectivity.

Here is a graphical layout of the N1Kv VDS and the ports.

This example is showing the VUM (VMWare Update Mgr.) installing the VEM's onto the hosts.

You can now see the hosts under the DVS (distributed virtual switch), one has an error relating to no adapter redundancy on host 2.

You have to add the vmnics to the N1Kv DVS.

Click on Manage Physical Adapters (These are the Eth interfaces in the N1Kv) 

Click to add NIC's for the VM-Sys-Uplink

Add the vmnic1 to migrate to the N1Kv DVS. And choose the vmnic 03 for the Vmotion, and vmnic 05 for vm-guest

It will ask you if you really want to move it from the Vswitch to the NK1V-01 DVS. Hit Yes!....

It will look similar to this output, the VM-Guest is grayed out because there are no Guests that are registered wit the VM-Guest vmnic/vlan 110 created yet.

You would now do the same for the second host.

You know have to create the veth port-profiles.

N1Kv1-1

conf t

port-profile type vethernet VMKernel

vwmare port-group

no shut

switchport mode access

swtichport access vlan 1

system vlan 1

state enabled

You can now create the other vEth port-profiles

vPath

    Only new traffic flow must first be sent to VSN, subsequent traffic is forwarded directly by the 

    VSM's and VEM's should all be the sam version

        All VES Heart Beats should increase at roughly at the same rate

            "show mod gem courters"

     Creates the same type of DVS in VMWare as N1Kv does

The Eth ports are your northbound links to the N5K switches and the vEth ports are assigned to VM hosts. If a VM host moves from one blade to another (to another VEM) it keeps the same vEth port. So all the configurations for the vEth ports doesn't have to be reconfigured again.

Flow control policies 

Determine whether the uplink Ethernet ports in a Cisco UCS domain send and receive IEEE 802.3x pause frames when the receive buffer for a port fills.

Network Control Policies 

 Have to trun on CDP, which is off by default and Allow MAC Security otherwise you'll have issues with vm hosts coming up through the fabric interconnects to the rest of the network.

You can now apply this Network Control Policy to the vNIC template

QoS Policies 

First look at the QoS system Class Under LAN Cloud

As you can see the Best Effort and Fibre Channel classes are already created. Also by default the Platinum, Gold, Silver, Bronze are all off by default. 

Once you enable them they will get assigned a Weight % as you see in the above example. The Weight and Weight % apply to the ingress port from this QoS system class. You can also change the MTU that is assigned, and assigned for iSCSI traffic

Apply to the SP Template the the correct vNIC interfaces that we assigned as Mgmt. vNIC's

From the KVM window you would pick the Virtual Media tab and map a Virtual CD drive that has the ESXi installer.

Click "Add Image" and browse to the installer file and check mapped.

You may have to reboot the server as the CD is mapped and hit the F6 Boot Menu form the BIOS and enter the CD setup.

Arrow down to the Cisco Virtual CD/DVD drive

You'll see the following

After the installer package unpacks all the contents of the file, you'll have to choose a disk to install the Hypervisor. You can install to a local disk, or a SAN disk device. If you have a SAN Disk device you have to make sure that the proper zoning is configured on your MDS switches.

The SEGATE is SAN disk in a JBOD. Arrow down to that as drive and hit Enter.

ESXi will will ask for what keyboard layout you want to use and root password.

You'll see the VMWare status for the installation if it was able to write to the drive.

After installation is complete hit F2 to change the Management IP Address to mange the VMWare hyper visor 

After this is done assuming you have Layer 3 connectivity you can go to your desktop and download the VSphere client.

On your desktop install the application and run VSphere Client

Hint: If you want to use the same ISO file, you may run into issues if you use the same ISO file, you can just make a copy of the file as name it as v2 and you'll be able to install tow instances of VMWare as the same time.

Pool was created already from previous lab. If you didn't create the pool you could evoke the creation form this page.

2.) Storage

No local storage has been selected you could choose RAID0 or RAID 5 this was what we configured perviously as part of the server hardware capabilities 

Next, click expert mode

Create vHBA1 for FI-A and choose the VMware adapter policy for the vHBA

Create the QoS policy for FC

This is what it should look like in the end

Name vHBA1 WWPN from UCS-ESX1-FABA and the VMWare Adapter policy and FC QoS Policy

You would know create vHBA2 for FI-B and the final result is as follows

3.) Networking (Create VNIC's 1 and 2 for the vmKernel)

Click Expert and Add to create the vNIC's

Pick the proper pool of MAC address (UCS-1-ESXi)

Choose the Fabric A and the VLAN's this vNIC will be associated with.

Choose the Adapter Policy VMWare

Create VNIC1 (FAB-A) for VMKernel MAC Address Pool UCS-1-ESXi, VLAN Default (native) 110-115, and Adapter policy VMWare

Create VNIC2 (FAB-B) for VMKernel MAC Address Pool UCS-1-ESXi, VLAN Default (native) 110-115, and Adapter policy VMWare

Create VNIC3 (FAB-A) for VMotion MAC Address Pool UCS-1-ESXi, VLAN 115, and Adapter policy VMWare

Create VNIC4 (FAB-B) for VMotion MAC Address Pool UCS-1-ESXi, VLAN 115, and Adapter policy VMWare

Create VNIC6 (FAB-B) For VMWare hosts AC Address Pool UCS-1-ESXi, VLANS 110-114, and Adapter policy VMWare

You could create VNIC 7 and 8 for NFS Data Stores as well

4.) vNIC/vHBA Placement

This is going to be dependent on the Server OS that will reside on the blade server itself. VMWare doesn't really matter what order, but for Windows Servers you should pay particular attention to the order of the vNIC's and vHBA's

5.) Create Boot Policy

The Boot order will start with Boot From SAN first and saying that vHBA1 is the primary 

Create vHBA2 for the secondary

Create a Boot Target primary under vHBA1 (DISK or LUN pWWN) to boot from

Create another Boot Target secondary under vHBA2 (DISK or LUN pWWN) to boot from.

Final configuration should look as follows

Finally pick the Boot Order Policy you just created and click next

6.) Maintenance Policy

I didn't choose any Maintenance Policy

7.) Server Assignments 

Choose one of the Server Pools that I created earlier and click Next

8.) Operational Policies 

Choose the BIOS Policy Loud Boot and the IPMI SoL-115200

 Choose the default option

Choose WipeBIOS

And Click Finish 

You'll see the final Configuration to make sure it's correct and then click Yes

You'll see the FSM is associating the Service Profile to the blades from that server pools

1.>Management IP Pool....

 Give the pool the starting IP address and then the size, subnet Mask, and finally the default gateway

As you can see from the following output blades are being assigned to the to the Mgmt. IP address pool. These shouldn't change when you change the Service Profile from one blade to the next

2.>Next Create the UUID pools

You'll notice none of the UUID's are assigned, this will be done during the creation of the Service Profile

3.> Create the MAC address Pool

I don't show here but I named the Pool UCS1-ESXi pool. The Pool Size has to be a block size of 16 so placed that size value at 128

As you can see none of the MAC addresses are assigned to a blades via a service profile

4.> Create the nWWN/WWWNN

Create in the bits place of the 2,3,4 to change. The first bit can only be 2 or 5(reserved addresses) So you want to keep it at 2. Bit 2 can be changed depending on the needs for the organization the next 3 bytes are the OUI which you cannot change and the last 3 bytes can be changed according to your organization. I kept it the same as 01 for the UCS Domain 1 and 01 to signify it's a ESXi host.

5.> Create the pWWN/WWPN

Here you have to create a pool for Fabric A and Fabric B

UCS1-ESXi-FabA

Here I have the naming as follows

20:AI (FI A):00:25:B1:01 (UCS Domain 1):01 (ESXi Host):00 for a size of 128

Do the same for FI B and use the naming as follows

20:B1:00:25:B1:01:01:00

You should know see this

6.> Create BIOS Policy 

Disable Quiet Boot to see full startup screens, Don't check Reboot on BIOS Settings Change, this will reboot the servers associated with this BIOS policy.

Here you can change the amount of CPU Cores are used and various other CPU options

Click Finish and you'll see the LoudBoot Option in the root tree

7.> Boot Policy 

I like to leave it as default's 

8.>IPMI (Intelligent Platform Mgmt. Interface)

9.> LOCAL Disk Config Policies 

You'll notice that it has Protect Configuration Checked, this will preserve the RAID settings if disassociated with a service policy. Have to be cognizant of the Scrub Policy setting as well

You have the following RAID Options

11.> Schedules 

This is an example or a reoccurring schedule. In the above example if the tasks are not completed within 2 hours the server will cancel tasks and reboot.

12.> Maintenance Policy 

This was based on the schedule that was created before.

13.> Power Caps (this is optional) 

You can assign Power Caps to particular servers, for instance you can have all our high priority servers in PowerCap 1 that will always be powered on if there are Power Supply failures, or PowerCap 10 for servers that maybe for Testing Purposes only.

14.> Server Pools (Optional)

Here you would pick what blades are to be part of this static pool

You can also create pools for Dynamic Allocation 

In the above example show a pool for servers that have a VIC CNA and 32GB of Memory 

15.> Server Pool Policy Qualifications (Optional) 

Here you can state that it has to be a Virtualized VIC

You can specify what chassis you what these qualifications in

Here you would specify the amount of memory and or clock speed

Here you can specify the number of cores etc...

 Here you can specify if the Blades is Diskless etc....

16.> Server Pool Policy 

So this ties together the Server Pool Qualifications and the Server Pools.

Here you would pick the Target Pool that where configured previously.

Here you would pick the Qualifications that where configured previously.

    Will show pWWN what we are booting form 

        Target LUN/Volume must already have GPT (GUI Partition Table) 

        No fabric failover in UCS, A/A LB takes care of that

            Prefernce would use one vNIC with Failover checked

            ESXi, won't check unless using VLAN0-untagged, otherwise ESXi expects 

            CNA/VIC adapters