ucs_2.2_v1_demo_script_2014-01-10

Cisco Demo Cloud (dCloud)

dCloud: The Cisco Demo Cloud

2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 1 of 54

Cisco Unified Computing System 2.2 v1 Last Updated: 10-JAN-2014

About This Cisco Solution

Cisco Unified Computing System (UCS) delivers smart, programmable infrastructure that simplifies and speeds enterprise-class

application and service deployment in bare-metal, virtualized and cloud-computing environments. Unified, model-based

management, end-to-end provisioning, and migration support come together in this next-generation data center platform to

accelerate and simplify application deployment with greater reliability and security.

To learn more about Cisco Unified Computing System, please visit www.cisco.com/go/ucs.

About This Demonstration

This preconfigured Unified Computing System demonstration includes:

Using Cisco UCS Manager for server provisioning and moving service profiles between physical blades

Integration of Cisco UCS Manager with VMware vSphere Auto Deploy to provision fully configured and ready to use

clustered virtual infrastructure servers with just a few mouse clicks

The implementation of Cisco Nexus 1000v and VM-FEX on Cisco UCS Manager

The monitoring of the Cisco UCS environment via well-known management tools such as Microsoft Systems Center

Operations Manager (SCOM) and HP Operations Manager (HPOM)

Creating and launching an e-commerce site using BMC BladeLogic Server Automation

Administrative-level access to the demonstration environment for customization of the demonstration flow

Customize this demonstration and save your customization for future use.

Demonstration Requirements

The table below outlines the requirements for this preconfigured demonstration.

Table 1. Demonstration Requirements

Required Optional

Laptop None for this release

Cisco AnyConnect

Demonstration Configuration

This demonstration contains preconfigured users and components to illustrate the scripted scenarios and features of this solution.

All information needed to complete the demonstration scenarios, is located in the Topology and Servers menus of your active

demonstration.


Topology Menu. Click on any server in the topology and a popup window will appear with available server options. The icons

with a green glow indicate the server is accessible using the Remote Desktop client within the UI.

Servers Menu. Click on or next to any server name to display the available server options and credentials.

Demonstration Preparation

Follow the steps below to schedule your demonstration and configure your demonstration environment.

1. Browse to dcloud.cisco.com, choose the location closest to you, and then log in with your Cisco.com credentials.

2. Schedule a demonstration [Show Me How].

3. Test your bandwidth from the demonstration location before performing any demonstration scenario. [Show Me How]

4. Verify your demonstration has a status of Active under My Demonstrations on the My Dashboard page in the Cisco dCloud

UI.

It may take up to 15 minutes for your demonstration to become active.

5. Access the demonstration workstation named wkst1 located at 198.18.133.36 and login using the following credentials:

Username: dcloud\demouser, Password: C1sco12345.

Recommended method. Use Cisco AnyConnect [Show Me How] and the local RDP client on your laptop. [Show Me

How]

Accept any certificates or warnings.

Alternate method: Use the Cisco dCloud Remote Desktop client with HTML5. [Show Me How]

Accept any certificates or warnings.


Scenario 1. Service Profiles

A service profile is a software definition of a server and its LAN and SAN network connectivity. In other words, a service profile

defines a single server and its storage and networking characteristics. When a service profile is deployed to a server, UCS

Manager automatically configures the server, adapters, fabric extenders, and fabric interconnects to match the configuration

specified in the service profile. This automation of device configuration reduces the number of manual steps required to configure

servers, network interface cards (NICs), host bus adapters (HBAs), and LAN and SAN switches.

Predefined Service Profile Templates. The following service profile templates have been preconfigured and may be used to

provide an overview of the benefits of the Cisco UCS service profile or how to configure service profiles using Cisco UCS:

Service Template ESXi-N1kv-Server_Auto-Deploy

Service Template ESXi-VM-FEX-Server_Auto-Deploy

Service Template Windows_Server_2012

Demonstration Steps

Integration of VMware vSphere Auto Deploy with UCS Manager

When building an ESXi server for a VMware vSphere infrastructure, typically a server administrator would have to manually install

the ESXi hypervisor, then configure various server, networking, and storage settings as well joining the server to a cluster and

distributed virtual switch. This traditional manual build process could take hours or days, depending on the number of servers and

configuration requirements. With Cisco UCS Manager integrated with VMware Auto Deploy, multiple complex ESXi server builds

can be completed automatically in less than half an hour with just a few mouse clicks.

Using Cisco UCS Manager integrated with VMware Auto Deploy, this section of the demonstration will show:

How quick and easy it is to create six ESXi servers via service profile templates

Automatic installation of the ESXi hypervisor and cluster membership

Automatic configuration of the ESXi hosts, including unique server settings, networking and shared storage

Automatic joining of the ESXi servers to the designated virtual distributed switch, in this case the Cisco Nexus 1000v or

VM-FEX

1. From the demonstration workstation, double-click on the UCS Manager shortcut on the desktop. Log in with the following

credentials: Username: demouser, Password: C1sco12345, Domain: dCloud.

2. In the Navigation pane, select the Servers tab.

3. On the Servers tab, expand Servers > Service Profiles Templates > root.

4. Select Service Template ESXi-N1kv-Server_Auto-Deploy. This is a pre-configured service profile template that will be used

to create ESXi servers using the Cisco Nexus 1000v virtual distributed switch.

5. Right-click and select Create Service Profiles From Template from the menu.


Figure 1. Create Service Profiles From Template Option

6. On the Create Service Profiles From Template window:

a. In the Naming Prefix field, enter ESXi-N1kv-Server-.

b. In the Name Suffix Starting Number field, leave the default number 1.

c. In the Number of Instances field, enter 3.

Figure 2. Create Service Profile From Template Window Example

7. Click OK and then click OK on the informational popup window confirming the service profiles were successfully created.

8. In the Navigation pane, go back to the Service Profile Templates section.


9. Select Service Template ESXi-VM-FEX-Server_Auto-Deploy. This is a pre-configured service profile template that will be

used to create ESXi servers using a VM-FEX virtual distributed switch.

10. Right-click and select Create Service Profiles From Template from the menu.

11. On the Create Service Profiles From Template window:

a. In the Naming Prefix field, enter ESXi-VM-FEX-Server-.

b. In the Name Suffix Starting Number field, leave the default number 1.

c. In the Number of Instances field, enter 3.

12. Click OK and then click OK on the informational popup window confirming the service profiles were successfully created.

13. On the Servers tab in the Navigation pane, expand Servers > Service Profiles > root.

You will see the service profiles created.

Figure 3. Created Service Profiles Example

14. Select one of the created service profiles.

15. Right-click and select KVM Console from the menu.

This will allow you to see the status of the deployment or provisioning.


Figure 4. KVM Console Option

16. From the demonstration workstation desktop, launch VMware vSphere Client.

a. At the bottom of the login window, check the box for Use Windows session credentials, if it is not already checked, and

click Login.

17. Go to Home > Inventory > Hosts and Clusters.

18. From the Navigation pane, expand the vCenter vc1.dcloud.cisco.com and the Datacenter dCloud.

19. Underneath the Datacenter dCloud, you will see the clusters N1kv Cluster and VM-FEX Cluster. The N1kv Cluster has

been setup for ESXi servers using the Cisco Nexus 1000v. The VM-FEX Cluster has been setup for ESXi servers using VM-

FEX. The ESXi servers created earlier from the service profile templates in UCS Manager will be automatically added to their

designated cluster as part of the Auto Deploy provisioning process.

Figure 5. VMware vSphere Hosts and Clusters Example

20. Monitor the progress of the creation of the servers, while you show other aspects of this demonstration script. This task takes

approximately 20 minutes to complete.

NOTE: While you wait for the servers to be created, we recommend you show the interactive model of UCS B-Series and UCS

5100 series.

21. In the VMware vSphere Client window, show the tasks that have completed and any that may still be in progress.

Show how the ESXi servers are automatically added to the appropriate cluster.


Figure 6. Populating VMware vSphere Client Hosts and Clusters Example

22. Continue to monitor the VMware vSphere Client until all the servers created from the service profile templates have

automatically joined their designated clusters and completed the automated host configurations.

You will know the host configurations have completed, and the ESXi servers are ready to be used when you see the following

three virtual machines with a green icon ( ): MGMSRV, WEBSRV, and DEMSRV. These virtual machines are automatically

spun up when the server clusters are populated and will be used later in the demonstration.


Figure 7. Completed VMware vSphere Client Hosts and Clusters Example

This concludes this demo activity.

Interactive Model of UCS B-Series and UCS 5100 Series

1. From your laptop, go to http://www.cisco.com/en/US/prod/ps10265/ps10279/ucs_kaon_model_preso.html. If prompted, accept

any security warnings.

The Interactive Model of UCS B-Series and UCS 5100 Series webpage will display.

NOTE: Optionally, you can access this page from the demonstration workstation by launching Internet Explorer (IE) and then

clicking the Cisco UCS Interactive Model from the favorites bar. For optimal performance, we recommend accessing the

webpage from your laptop.

Figure 8. Interactive Model of UCS B-Series and UCS 5100 Series Webpage

2. Click the available menu options to show or remove physical components from the model.


3. Click the Notes icon ( ) to display additional information within the image.

Figure 9. Example Notes Popup

4. Click Features, to see the menu of available components.

5. Show as many or as few of the physical components based on customer interest.

6. Remember to check the status of the Integration of VMware Auto Deploy with Cisco UCS Manager, if you are also

demonstrating that task.


Moving Service Profiles Between Physical Blades

Moving Service Profiles. It is possible to move a service profile from one physical blade to another. There are several reasons

that this might be done:

Scheduled maintenance. Routine maintenance can easily be performed on a blade with no disruption of service and no

down time.

Equipment upgrades. The process described in this demonstration can be used when it is necessary to take a blade out

of service for specified upgrades.

Equipment failure. A service profile can be moved from one blade to another in the event of failure. The recovery is

measured in minutes rather than days.


This demonstration illustrates service profile mobility and the ease with which one blade can be removed from service (with a

specific service profile associated and running) and another blade within the same server pool is powered on with the exact same

service profile, but using different hardware.

1. Return to the UCS Manager window.

2. In the Navigation pane, select the Servers tab.

3. On the Servers tab, expand Servers > Service Profiles > root.

4. Select Windows_Server_2012-Server01.

5. In the Work pane, on the General tab, the Properties area identifies the server currently associated with this service profile. In

the example in the figure below, the Associated Server is chassis-1/blade-8.

Figure 10. Windows_Server_2012-Server01 Properties Example

6. From the demonstration workstation, click on the Start Menu and then select Remote Desktop Connection.

a. In the Computer field, enter winsrv, and then click Connect.

b. Log in with the following credentials: Username: administrator, Password: C1sco12345.

7. On the winsrv desktop, launch Notepad from the taskbar. Type some unique content in the Notepad window, for example,

the customers company name, and save the text document to the desktop with a random name such as demotest. Verify the

text file has been saved to the desktop and close the Notepad window.

8. Disconnect or logout from the winsrv RDP session.

9. Return to the UCS Manager window.

10. In the Navigation pane, select the Equipment tab.

11. On the Equipment tab, expand Chassis > Chassis 1 > Servers.

12. Select the server currently associated to the Windows_Server_2012-Server01 service profile.

13. In the Work pane, on the General tab, review the Properties area to confirm that you have selected the correct server.


Figure 11. Service Profile Properties Example

14. In the Actions section, click on Server Maintenance. In the Server Maintenance window, select Decommission and then

click OK. Click Yes to confirm. Click OK.

In the Physical Display area of the Work pane, the server will display Needs Resolution.

Figure 12. Physical Display

15. In the Navigation pane, on the Servers tab, expand Servers > Service Profiles > root.

16. Select Service Profile Windows_Server_2012-Server01.

17. In the Work pane, on the General tab, the Properties area will display that the service profile is now associated with another

server. This may take a few minutes.

The service profile has been moved to the new blade.


Figure 13. Service Profile Properties Example

18. On the General tab, in the Status Details, the Assoc State will state Associating as the UCS Manager goes through a

process to associate the service profile to the new blade. When the service profile has been associated to the new blade the

Assoc State will change to Associated.

Figure 14. Assoc State Associated Example

19. After the Assoc State changes to Associated, wait about 5 minutes for the Windows Server to fully come up, then on the

demonstration workstation, click on the Start Menu, and then select Remote Desktop Connection.

a. In the Computer field, enter winsrv, and then click Connect.


NOTE: If the RDP connection fails, than the Windows Server has not fully come up yet. Wait or a few more minutes or open the

KVM console of the Windows_Server_2012-Server01 service profile to watch the server as it comes up. Once the Windows server

is at the login screen, it is available to accept RDP connections.

20. On the desktop, open the demotest.txt file created earlier to show that it is the same, even though the service profile has

moved to a new hardware blade.

21. Disconnect or logout from the winsrv RDP session.


NOTE: You may see a window to Resolve Slot Issue in the UCS Manager for the server that was decomissioned. If you see this

window, click OK and re-acknowledge the slot for the decommissioned server, as it will be used later in the demonstration.

Cloned Service Profiles. You can clone a service profile in the Cisco UCS Manager GUI. This capability is useful if you need one

service profile with similar values to an existing service profile.



Scenario 2. VM-FEX On UCS Manager

Cisco Virtual Machine Fabric Extender (VM-FEX) is a hardware approach based on the concept of network interface virtualization.

This demonstration focuses on utilizing VM-FEX.

Cisco VM-FEX. Cisco VM-FEX is a hardware-based method of handling traffic to and from a virtual machine on a server with a

VIC adapter. This method has also been referred to as pass-through switching (PTS). This solution replaces software-based

switching with ASIC-based hardware switching and improves performance.

The distributed virtual switch (DVS) framework delivers VM-FEX features and capabilities for virtual machines on Cisco UCS

servers with VIC adapters. This approach provides an end-to-end network solution to meet the new requirements created by server

virtualization.

With VM-FEX, all traffic to and from a virtual machine passes through the DVS and the hypervisor and then returns to the virtual

machine on the server. Switching occurs in the fabric interconnect (hardware). As a result, network policies can be applied to traffic

between virtual machines. This capability provides consistency between physical and virtual servers.

Figure 15. Traffic paths taken by VM traffic on Cisco UCS server with VIC adapter

Demonstration Steps

Cisco VM-FEX Configuration Overview

All configurations required for this demonstration have been pre-configured, however; this section provides an overview of the

configuration process.

1. From the demonstration workstation, go to the open VMware vSphere Client window.

If the application is not open, double-click the VMware vSphere Client shortcut on the desktop and then click Login.

2. From the toolbar, go to Home > Inventory > Hosts and Clusters.

3. In the left pane, expand vc1.dcloud.cisco.com > dCloud > VM-FEX Cluster to view the inventory of hosts and guest virtual

machines.

You will see the servers that you previously created for the VM-FEX Cluster. For example, esxi-vm-fex-

server01.dcloud.cisco.com.


Figure 16. Inventory of Hosts and Clusters Example

4. Go to the open UCS Manager window.

If the application is not open, double-click the UCS Manager shortcut on the desktop and log in with the following

credentials: Username: demouser, Password: C1sco12345, Domain: dcloud.

5. In the Navigation pane, click the VM tab. Expand All > VMware > vCenter vc1 > Datacenter dCloud > Folder VM-FEX-

Switch01 > VM-FEX-Switch01.

You can see the pre-configured Port Profiles.

Figure 17. Port Profiles Example

6. In the Navigation pane, click the Servers tab. Expand Servers > Service Profiles > root.

Select one of the service profiles that you created for the VM-FEX Cluster. For example, ESXi-VM-FEX-Server-1.

7. In the Work pane, click the Network tab.

You can see that the selected profile has a Dynamic vNIC Connection Policy, which is used by the VMs to connect to the VM-

FEX switch.

8. In the Navigation pane, click the VM tab. Expand All > VMware > Virtual Machines.


From here, you can see the host server blades and guest virtual machines, which are connected to the VM-FEX switch along

with their virtual interface IDs that are created.

9. Expand all of the Host Blades under All > VMware > Virtual Machines. Look for a second Virtual Machines folder and

expand it to see the virtual machines.

In the example in the figure below, DEMSRV is associated with vNIC 1500.

Figure 18. Virtual Machine DEMSRV vNIC Example

10. Return to the vSphere Client window.

11. From the navigation bar, go to Home > Inventory > Networking.

You can see the VM-FEX switch created in the Virtual Center. You can also see four port groups that were created: Data,

ERSPAN, Management, and vMotion. The uplink-pg and deleted-pg port-groups are created automatically.

Figure 19. VM-FEX-Switch01 Example



Cloning a VM in the vSphere Client


2. From the navigation bar, go to Home > Inventory > Hosts and Clusters.

3. In the left pane, expand vc1.dcloud.cisco.com > dCloud > VM-FEX Cluster. Select the DEMSRV virtual machine.

4. Right-click the selected virtual machine and choose Clone from the menu.

a. In the Name field, enter DEMSRV-CLONE.

b. For Inventory Location, select the folder VMs. Click Next.

c. For Host / Cluster, select VM-FEX Cluster. Click Next.

d. No further updates are needed. Click Next. Click Next. Click Finish.

5. The newly cloned virtual machine, DEMSRV-CLONE, will appear shortly in the left pane under VM-FEX Cluster.

Figure 20. VM-FEX Cluster After VM Clone Example

6. In the left pane, select VM-FEX Cluster and then in the right pane click the Virtual Machines tab.

You will be able to see which host the VM is on after the cloning is complete.


Figure 21. Virtual Machines Tab Example

7. The cloning process will take about 10 minutes. Check the Recent Tasks area to confirm when the clone task is Completed.

8. Select the cloned VM and click the Power On button ( ) in the toolbar.


Verify the Cloned VM on UCS

1. Return to the UCS Manager window. Select the VM tab.

2. Expand all of the Host Blades under All > VMware > Virtual Machines. Look for a Virtual Machines folder containing

Virtual Machine DEMSRV-CLONE and expand the content. You will see which vNIC is associated with DEMSRV-CLONE.

In the example in the figure below, DEMSRV-CLONE is associated with vNIC 1501.

Figure 22. Virtual Machine DEMSRV-CLONE vNIC Example


4. From the navigation bar, go to Home > Inventory > Networking and then select VM-FEX-Switch01.

5. In the right pane, select the Virtual Machines.


You can see that the newly cloned VM is using VM-FEX-Switch01.

Figure 23. Example


Migrating a VM Using VMotion


2. Navigate to Home > Inventory > Hosts and Clusters, and select the new DEMSRV-CLONE VM cloned earlier.

3. In the right pane, select the Summary tab to identify the host the VM has been assigned to.

In the example in the figure below, the VM is assigned to esxi-vm-fex-server03.dcloud.cisco.com; however, you may have a

different host in your demo.

Figure 24. DEMSRV-CLONE Summary Example


5. Expand all of the Host Blades under All > VMware > Virtual Machines. Select the Host Blade containing Virtual Machine

DEMSRV-CLONE.

6. Verify the host and the vNIC ID of the DEMSRV-CLONE VM.


Figure 25. DEMSRV-CLONE Example


8. In the left pane, drag and drop the DEMSRV-CLONE VM to another ESXi.

The Migrate Virtual Machine window appears.

Note: You may receive a warning about the OS heartbeats of the guest if the migration is attempted immediately after the guest

VM is started. If you receive this warning, click yes to proceed.

9. Accept the recommended default for VMotion priority and click Next. Click Finish.

10. Allow about 15 seconds for VMotion to move the VM from one ESXi host to another. The Host field in the Summary tab

confirms that the VM has been moved successfully


Figure 26. DEMSRV-CLONE Summary After Moving Example


12. Confirm that the VM has moved under a new host but retains the same vNIC.

Figure 27. DEMSRV-CLONE After Move Example



Scenario 3. Cisco Nexus 1000V on UCS

Cisco has developed a software approach based on the concept of network interface virtualization. This demonstration focuses on

the capabilities of the Nexus 1000V.

Cisco Nexus 1000V Series. With the introduction of the DVS framework, VMware also allowed third-party networking vendors to

provide their own implementations of distributed virtual switches by using the vNetwork switch API interfaces. Cisco and VMware

collaborated closely on the design of these APIs, and the Cisco Nexus 1000V Series represents the first example of third-party

DVSs that are fully integrated with VMware Virtual Infrastructure, including VMware vCenter for the virtualization administrator.

When deployed, the Cisco Nexus 1000V Series not only maintains the virtualization administrators regular workflow; it also

offloads the vSwitch and port group configuration to the network administrator, reducing network configuration mistakes and

helping ensure that consistent network policy is enforced throughout the data center.

The Cisco Nexus 1000V Series consists of two main types of components that can virtually emulate a 66-slot modular Ethernet

switch with redundant supervisor functions:

Virtual Ethernet module (VEM) data plane: This lightweight software component runs inside the hypervisor. It enables

advanced networking and security features, performs switching between directly attached virtual machines, provides

uplink capabilities to the rest of the network, and effectively replaces the vSwitch. Each hypervisor is embedded with one

VEM.

Virtual supervisor module (VSM) control plane: This standalone, external, physical or virtual appliance is responsible

for the configuration, management, monitoring, and diagnostics of the overall Cisco Nexus 1000V Series system (that is,

the combination of the VSM itself and all the VEMs it controls) as well as the integration with VMware vCenter. A single

VSM can manage up to 64 VEMs. VSMs can be deployed in an active-standby model, helping ensure high availability.

In the Cisco Nexus 1000V Series, traffic between virtual machines is switched locally at each instance of a VEM. Each VEM is also

responsible for interconnecting the local virtual machines with the rest of the network through the upstream access-layer network

switch (blade, top-of-rack, end-of-row, etc.). The VSM is responsible for running the control plane protocols and configuring the

state of each VEM accordingly, but it never takes part in the actual forwarding of packets

Demonstration Steps

ESXi Hosts and Virtual Machines on Cisco Nexus 1000v

1. From the demonstration workstation, go to the open vSphere Client window.

If the application is not open, double-click the VMware vSphere Client shortcut on the desktop and then click Login.


3. In the left pane, expand vc1.dcloud.cisco.com > dCloud > N1kv Cluster to view the inventory of hosts and guest virtual

machines.


Figure 28. N1kv Cluster Example

4. Telnet to the Nexus 1000V by double-clicking on the putty.exe shortcut on the desktop and then double-clicking Cisco

Nexus 1000v, under Saved Sessions.

Figure 29. PuTTY Configuration

5. Log in with the following credentials: Username: admin, Password: C1sco12345.

6. Type show version to see what version of the NX-OS is running.

Figure 30. Show Version Example

7. Type show module to see the module types.


The show module information includes the VEMs on the N1kv ESXi servers displayed in the VMware vSphere Client.

Figure 31. Show Module Information Correlation To VMware VSphere Client Example

8. Type show interface virtual and you will see that all of the VMs are allocated vEthernet ports. You can also see what hosts

the VMs currently reside on.


Figure 32. Show Interface Virtual Example


Cloning a VM in the vSphere Client

1. Return to vSphere Client window.

2. In the left pane, select the virtual machine MGMSRV under the N1kv Cluster.

3. Right-click the selected virtual machine and then click Clone from the menu.

a. In the Name field, enter MGMSRV-CLONE.

b. For Inventory Location, select the folder VMs. Click Next.

c. For Host / Cluster, select N1kv Cluster. Click Next.

d. No further updates are needed. Click Next. Click Next. Click Finish.

4. The newly cloned virtual machine, MGMSRV-CLONE, will appear shortly in the left pane under N1kv Cluster.

Figure 33. N1kv Cluster With MGMSRV-CLONE

5. Determine which ESXi host contains the new virtual machine. In the left pane, select N1kv Cluster and then in the right pane,

select the Virtual Machines tab.


Figure 34. N1kv Cluster Example

6. The cloning process will take about 10 minutes. Check the Recent Tasks area to confirm when the clone task is Completed.

7. Select the cloned VM and click the Power On button ( ) in the toolbar.


Verify Cloned VM on the Cisco Nexus 1000v

1. Return to the Nexus 1000V telnet session.

2. Type show interface virtual to identify the virtual interface (VethX) assigned to the cloned VM (MGMSRV-CLONE).

NOTE: It may take up to one minute after powering on the VM before you are able to see it.

Figure 35. Show Interface Virtual

3. Type show interface brief to identify the VLAN assigned to this virtual interface.


Figure 36. Show Interface Brief Example


Exploring the Cisco Nexus 1000V Networking Configuration

It is helpful to become familiar with the current port configuration on the Nexus 1000V.

1. Return to the vSphere Client window. Press Ctrl+Shift+N to move to the Networking section, where the Nexus 1000V switch

is displayed, prior to preceding to the next demonstration step of creating a port profile.

The navigation bar displays Home > Inventory > Networking.

2. The left pane displays the port groups on the Nexus 1000V switch. Select a port group and explore the tabs in the right pane.

3. In the left pane, expand vc1.dcloud.cisco.com > dCloud > N1kv-Switch01 > N1kv-Switch01.

The port groups listed (for example, ERSPAN_Port_Group, Secure_Webserver_Port_Group, etc.) can only be created on the

Nexus 1000V as port-profiles and will then be populated in this list as a port group to be used by server administrators through

the VMware vSphere Client.

Figure 37. N1kv Port Groups Example

4. Return to the Nexus 1000V telnet session. Type show port-profile brief.


This list is the same as seen in the VMware vSphere Client. The port-profiles within the Cisco Nexus 1000v are shown as port

groups within the VMware vSphere Client.

Figure 38. Show Port-Profile Brief Example


Creating a new Port Profile

Port profiles are created on the Nexus 1000V by a network administrator using the command line interface.


2. Type the following commands to create a new port-profile called test_100:

N1kv-Switch01# configure terminal

N1kv-Switch01 (config)# port-profile test_100

N1kv-Switch01 (config-port-prof)# switchport mode access

N1kv-Switch01 (config-port-prof)# switchport access vlan 100

N1kv-Switch01 (config-port-prof)# no shutdown

N1kv-Switch01 (config-port-prof)# vmware port-group

N1kv-Switch01 (config-port-prof)# state enabled

N1kv-Switch01 (config-port-prof)# end

After entering the state enabled command, you will see the newly created port profile (test_100) appear within the vSphere

Client immediately as a port group. It is now available for a server administrator to apply to any of the VMs within this vCenter.


If you go back to vSphere Client and navigate back to your newly created VM (MGMSRV-CLONE), right-click and select Edit

Settings, and then highlight Network adapter 1. Within the Network Connection section, the Network label dropdown list

includes the newly created port profile (test_100).


Migrating a VM using VMotion


2. Navigate to Home > Inventory > Hosts and Clusters (or press Ctrl+Shift+H), and select the new MGMSRV-CLONE VM

created earlier.

3. From the right pane, select the Summary tab to identify the host this VM has been assigned to.

Figure 39. Summary Tab Before VM Moved Example

4. In the left pane, drag and drop the MGMSRV-CLONE VM to another ESXi host.


Note: You may receive a warning about the OS heartbeats of the guest if the migration is attempted immediately after the guest

VM is started. If you receive this warning, click yes to proceed.

5. Accept the recommended default for vMotion Priority and click Next. Click Finish.

6. Allow about 15 seconds for vMotion to move the VM from one ESXi host to another.

The Host field in the Summary tab confirms that the VM has been moved successfully.


Figure 40. Summary Tab After VM Moved Example

7. Return to the Nexus 1000V telnet session, and use the various CLI commands to also verify the ESXi host has changed, but

the virtual interface and VLAN remain the same.



Scenario 4. Virtual Machine Traffic Inspection (using ERSPAN)

ERSPAN sessions allow you to monitor traffic on one or more ports, or one or more VLANs, and send the monitored traffic to one

or more destinations. ERSPAN sends traffic to a network analyzer such as a Wireshark package or other Remote Monitoring

(RMON) probe.

Demonstration Steps

Launch the Wireshark Network Analyzer Tool

VM and web traffic is monitored using the Wireshark network analyzer tool. The efficiency gained from the ability to connect to any

port group and virtually mirror traffic from any device on the port group is presented. A VMotion is performed and the ability of the

Nexus 1000V to maintain an ERSPAN session is demonstrated.

1. From the demonstration workstation, click on the Start Menu and then select Remote Desktop Connection.

a. In the Computer field, enter mgmsrv, and then click Connect.


2. Double-click the Wireshark shortcut ( ) on the desktop to launch Wireshark.

3. In the Capture area, click Start.

Figure 41. Capture Area Example


Wireshark has already been configured to monitor all traffic from several sources, including traffic from a web server and

numerous ICMP messages.

Figure 42. Wireshark Capture Display Example

4. From the toolbar, click ERSPAN Filter.

Figure 43. ERSPAN Filter

5. From the demonstration workstation, launch IE.

6. Arrange the IE window and the mgmsrv desktop so you can easily see both windows.

7. From IE, click on the UCS Demo Website link in the Favorites bar.

8. Browse the website to generate web traffic.

NOTE: If you do not see any packets in the Wireshark capture display, click the browser reload button.

9. Return to the Wireshark capture session and click the Stop the running live capture ( ) button in the toolbar to stop the

capture.


11. Type show monitor session 3.

The type of traffic is erspan-source and the source port-profile is ERSPAN_Port_Group. The destination IP address is

198.19.7.10.


Figure 44. Show Monitor Session 3 Example

12. From the demonstration workstation open a command prompt and type in ipconfig to verify the IP address as 198.18.133.36.

Figure 45. Host IP Address Example

13. Return to the Wireshark capture session. Select one of the captured HTTP packets with a source IP of 198.18.133.36, the

demonstration workstation and a destination IP of 198.19.6.10, the web server WEBSRV.

Figure 46. Captured HTTP Packet Example


This demonstrates that the ERSPAN session monitoring web HTTP traffic to the web server is sending the monitored traffic to the

Wireshark network analyzer tool running on the MGMSRV VM.


vMotion the Web Server

NOTE: This scenario demonstrates one of the unique aspects of the Nexus 1000V; policies defined move with the Virtual Machine

during VMotion. Thus, a VMs ERSPAN sessions continue despite VMotion.

1. Return to vSphere Client window.

2. Move the WEBSRV VM from one ESXi host to another ESXI host, following the procedure in section Migrating a VM Using

vMotion.

3. Return to Wireshark, click the Start a new live capture ( ) button in the toolbar and repeat the packet capture described

above.

The results should be the same.


Policy-based Virtual Machine Connectivity (using ACL)

Network security concerns are addressed here. There is no need for complicated server builds; this demonstration displays the

simplicity of letting the network deal with security.

The Cisco Nexus 1000V is initially configured to allow any traffic to and from the web server WEBSRV. To enhance security, a

secure port profile using Access Control Lists (ACLs) can be applied which allows only HTTP traffic to be delivered to the web

server. These settings are preserved if the VM is moved for any reason (for example, using VMotion or DRS).

Accessing the web server via HTTP, Telnet and ICMP

This portion of the demo will show the server before the secure ACL is applied.

1. From the demonstration workstation, launch Internet Explorer. From the Favorites bar, click the UCS Demo Website link.

2. Open a command prompt and type ping websrv. The web server should reply.

3. Type telnet websrv.

The web server will respond with a login prompt indicating a telnet session could be established. This is also a security

concern.

4. Close Internet Explorer and the command prompt window.


Verifying Initial Cisco Nexus 1000V Port Settings

Several CLI commands are used to identify the current configuration of the Nexus 1000V and the web server.



2. Type show interface virtual. The response will show that the web server is on Virtual Ethernet x (for example, Virtual

Ethernet 7).

3. Type show interface vethernet x. The response will display the port profile applied for Virtual Ethernet x (for example, Virtual

Ethernet 7) is ERSPAN_Port_Group.

4. Type show port-profile brief. This will list all configured port profiles.

Note: The commands in steps a and b below, are case-sensitive

a. Type show port-profile name ERSPAN_Port_Group to identify the specific configuration for this port profile.

b. Type show port-profile name Secure_Webservers_Port_Group. This port profile includes the use of ACLs. The web-in

in and web-out out named ACLs will only allow web traffic to the server.

Figure 47. Show Port Profile Example

c. Type show access-lists to see the specifics of web-in and web-out. This will permit only web traffic and deny anything

else.

Figure 48. Show Access Lists Example


Applying Secure_Webservers_Port_Group port profile

The port profile with the security policy will be applied from the VMware vSphere Client. This eliminates the need to connect to

each physical server to lock it down, which can be resource intensive.




3. In the left pane, expand vc1.dcloud.cisco.com > dCloud > N1kv Cluster. Select WEBSRV.

4. In the right pane, select the Summary tab.

a. Click Edit Settings in the Commands area.

b. Click Network adapter 1.

Observe the Network label drop-down has the port profile Secure_Webservers_Port_Group (N1kv_Switch01).

5. Using the Network label drop-down list, change the port profile to Secure_Webservers_Port_Group (N1kv_Switch01).

Click OK.

Figure 49. WEBSRV Virtual Machine Properties Example

6. The security port polices of Secure_Webservers_Port_Group have been applied and only web traffic should be allowed to

and from the web server.


Verifying the Policy

With the security port policies of Secure_Webservers_Port_Group applied, security is enhanced and the only access to the web

server is HTTP traffic.

1. From the demonstration workstation, launch Internet Explorer. From the Favorites bar, click the UCS Demo Website link.

Connectivity to the web server is still allowed.

2. Open a command prompt and type ping websrv.

The ping should time out. This demonstrates that ICMP traffic cannot get through to the web server.


3. Type telnet websrv.

The telnet command response will be Could not open connection to the host, on port 23: Connect failed.


VMotion the web server

This optional portion of the demo will show that you can VMotion the web server from one host to another and the port policy will

not be affected.


2. From the toolbar, go to Home > Inventory > Hosts and Clusters.

3. In the right pane, select WEBSRV.

4. In the left pane, select the Summary tab to identify which host the web server is associated with.

5. In the right pane, drag and drop the WEBSRV VM to another ESXi host.


6. Accept the recommended default for VMotion priority and click Next. Click Finish.

7. Allow about 15 seconds for VMotion to move the VM from one ESXi host to the other.

8. Repeat the steps in Verifying the Policy above to demonstrate that the policy moved when the VM was assigned to a new

host.



Scenario 5. Cisco UCS Management Pack for Microsoft SCOM

Operations Manager enables you to monitor services, devices, and operations for many computers in a single console. Operators

can gain rapid insight into the state of the IT environment and the IT services running across different systems and workloads by

using numerous views that show state, health, and performance information, as well as alerts generated for availability,

performance, configuration and security situations.

Value of the Cisco UCS Management Pack for Microsoft System Center Operations Manager. The Cisco UCS Management

Pack for Microsoft System Center Operations Manager (SCOM) simplifies management by enabling IT personnel to:

View Cisco Unified Computing System (UCS) hardware, service profiles, operating systems, and virtual machines on a

single interface (This demo does not include the integration of SCOM for Virtual Machines).

View the health of Cisco Unified Computing System hardware, including chassis, blades, and subsystems, in the native

Microsoft SCOM format.

Visually correlate blades, service profiles, and host operating systems using Microsoft SCOM state views to quickly

determine how an event will affect the overall system.

Cisco UCS Management Pack graphically depicts Cisco Unified Computing System hardware, service profiles, host operating

systems, and virtual machines. Correlation of events with the blades and service profiles they affect simplifies identification of root

causes, accelerating problem resolution.

Demonstration Steps

This section only demonstrates the integration of Microsoft SCOM with UCS Manager. It does not include any actions to

demonstrate the Microsoft SCOM capabilities.

Cisco UCS Management Pack for SCOM

1. From the demonstration workstation, double-click the SCOM 2012 shortcut on the desktop.

The Monitoring Overview will be displayed.


Figure 50. Monitoring Overview Example


2. Navigate to Monitoring > Cisco Unified Computing System > Cisco UCS Instance > UCSM > Diagram. Click Yes on the

popup window.

This will give you a view of the different topology diagrams, such as Hardware Inventory and Service Profile.

Figure 51. Diagram View Example

3. Expand UCSM HW Inventory by clicking the plus sign ( ) and then expand Chassis 1, to see the contents of the Chassis.

Expand the subfolders to see the various hardware components present.

The same diagram can be seen if you navigate to Monitoring > Cisco Unified Computing System > Cisco UCS Instance >

UCSM > HW Inventory > Diagram.


Figure 52. Diagram View Chassis Hardware Components Example

4. Navigate to Monitoring > Cisco Unified Computing System > Cisco UCS Instance > UCSM > Service Profiles >

Diagram. This will provide you with a view of the service profile topology diagrams.


Figure 53. Diagram View Service Profiles Example

5. Navigate to Monitoring > Active Alerts to see all of the Alerts that the SCOM has received.


Figure 54. MS SCOM Active Alerts With Selected UCSM Alert Example

6. To show the correlation between alerts seen in SCOM with the actual UCS Manager, return to the UCS Manager window.

7. In the Navigation pane, on the Admin tab, expand All > Fault, Events and Audit Log. Select Faults.

8. In the Work pane, look for the fault that correlates with the alert selected in SCOM.

In our example figures (Figures 56 and 57), we have selected the alert server pool default is empty with an F0463 code.


Figure 55. UCS Manager Faults Example



Scenario 6. Navigation of HPOM

Hewlett Packard (HP) Operations Manager (OM) software features a consolidated infrastructure management console that

correlates fault and performance events across entire IT infrastructures. It monitors both physical and virtual servers to identify the

cause of event storms, allowing faster time to resolution.

Cisco UCSM Smart Plugin. Cisco UCSM Smart Plugin provides the monitoring capability for Unified Computing System Manager

(UCSM) nodes for HP Operations Manager (HPOM).

With the integration of Cisco UCSM Smart Plugin with the HPOM product, users can use the HPOM console for managing the

faults on Cisco UCSM. It enables users to view the service hierarchy of the UCS nodes being monitored. It also enables users to

view and acknowledge faults for the UCSM node.

Demonstration Steps

This section demonstrates the integration of HPOM with UCS Manager. It shows how you monitor alerts for UCS.

If your organization uses HPOM as a system monitoring tool, this section will show you how seamlessly HPOM integrates with

UCS Manager. This section will provide a high-level overview of the HPOM Status and Alerts features.

Cisco UCSM Smart Plugin

1. From the demonstration workstation, double-click the HPOM shortcut on the desktop. You are automatically logged in.

2. This will open the HP Operations Manager and you will see all of the alerts for the UCS Manager.

Figure 56. HPOM UCS Manager Alerts Example

3. Scroll through the list of alerts and show the alerts.


4. Double-click on an alert to show more detail. A Message Properties window will open.

Explore the different tabs available.

Figure 57. Message Properties Example

5. Expand Services > Systems Infrastructure > UCSM.

You will see a drop-down of all of the components of the UCS Manager that have been discovered by the HP Operations

Manager.

Figure 58. UCS Manager Components Example

6. Expand components to show further details.


Figure 59. Expanded Components Example

7. Highlight a specific component and from the toolbar select View > Active Messages.

Only active messages for the highlighted component will be displayed.

Figure 60. Active Messages Example

8. You can drilldown to specific components.


In the figure below, Server 1 > Inventory > Interface Cards > Interface Card 1, has been expanded and the alerts related to

Interface Card 1 is displayed.

Figure 61. Alerts For Specific Component Example

9. Compare the alerts in HPOM with the alerts in UCS Manager.

a. In HPOM, expand Nodes > UCSM (UCS Manager) and then select an alert. Double-click on the alert to display the

Message Properties.

b. In UCS Manager go to the Admin tab and then expand All > Faults, Events and Audit Log > Faults. Locate the

corresponding error.

c. In the examples in the following figure, you can see the same information. For example, the fault description is Virtual

interface 32776 link is down; reason Non participating.


Figure 62. HP Operations Manager and UCS Manager Fault Messages Example

10. Acknowledge an alert in HPOM and show the alert has also been acknowledged in UCS Manager.

a. In HPOM, expand Nodes > UCSM (UCS Manager) and then select an alert. Double-click on the alert to display the

Message Properties.

b. In UCS Manager go to the Admin tab and then expand All > Faults, Events and Audit Log > Faults. Locate the

corresponding error.

c. In HPOM, right-click on the alert and then select Acknowledge. This will acknowledge the alert in HPOM.

d. In UCS Manager, you can see that the alert has also been acknowledged. If the alert was in a Cleared state, the alert will

disappear and no longer display.



Scenario 7. BMC BladeLogic for UCS

BMC BladeLogic for Cisco Unified Computing System, which includes BMC Atrium technology, integrates with and builds on the

Cisco UCS Manager to produce differentiated integrated device and system management functions. The result is a computing

system that is dramatically simpler to maintain and operate, enabling enterprises to deliver business services much more efficiently

and with uncompromising availability and performance.

IMPORTANT: This scenario must be performed before or after Moving Service Profiles Between Physical Blades in this script. It

cannot be performed at the same time as the Moving Service Profiles Between Physical Blades.

BMC BladeLogic helps administrators with the automated instantiation and ongoing configuration of the Cisco Unified Computing

System, including help with:

Displaying and configuring in-context Cisco Unified Computing System logical management constructs, called service

profiles

Provisioning the full technology stack: hardware resources, physical and virtual server instances, and business line

applications

Coordinating event interaction between Cisco UCS Manager and BMC BladeLogic Operations Manager through granular

XML interfaces

BMC BladeLogic for Cisco Unified Computing System provides the capability to provision and configure entire business services to

deliver complete services to the business faster and with lower risk and cost. The solution helps ensure that all changes meet

security, operational and regulatory policies and reduces the risk of change in a highly complex environment.

UCS Manager is the GUI that runs blade servers. A company called BMC Software, a Cisco partner and a leader in virtual

computer science, built the interfaces for UCS Manager. BMC has designed and built their own GUI, called BladeLogic. BMC

BladeLogic controls and manages the UCS environment separate from Cisco UCS Manager,

BMC BladeLogic will do some of the same things as UCS Manager (for example, build templates, provision servers, and firmware

loads), plus the addition of other critical configuration to the OSs, virus checker, and browsers.

Demonstration Steps

The BMC BladeLogic management tool will be used to fully provision a bare metal server with all of the necessary hardware

components, operating systems and the applications and web servers necessary to bring a fully functional e-commerce website

online and ready for business.


Create E-Commerce Web Server Using BMC BladeLogic Server Automation Console

IMPORTANT: If you completed the Moving Service Profiles Between Physical Blades task, you will need to re-acknowledge the

server decommissioned during that task if you have not already done so. This server is needed in order to complete this task. This

must be completed before you can perform this task.

To re-acknowledge the server:

From the demonstration workstation, go to the UCS Manager window. Select the Equipment tab.

Expand Equipment > Chassis > Chassis 1 > Servers and then select the server that the Windows_Server_2012-

Server01 service profile was moved from. The server icon will have a question mark over it.

Click OK on the Resolve Slot Issue.

In the right pane, click Re-acknowledge Slot. Click Yes. Click OK. It will take a few minutes for the re-acknowledgement

to complete. Wait for the Overall Status of the server to show as Unassociated before proceeding. The Overall Status

can be observed from the Status section of the General tab for the server.

1. From the demonstration workstation, double-click the BMC SA shortcut on the desktop to launch the BMC Server

Automation Console. Enter the password: C1sco12345, the user name is prepopulated.

The BMC BladeLogic Server Automation Console GUI page displays.

2. From the left pane, expand Bladelogic > Jobs > Provisioning Jobs.

3. Select E-Commerce Web Server, right-click and then select Execute from the menu.

This will automatically begin the provisioning of the server.

It may take up to 35 minutes for the provisioning to complete.

4. You can monitor the status of the job by reviewing the Tasks in Progress at the bottom of the screen.

Figure 63. Tasks in Progress Example

5. Go to the open UCS Manager window.

6. On the Servers tab, expand Servers > Service Profiles > root.

7. You will see a new service profile, named RedHat_5.3-Server01.


Figure 64. Demo Service Profile Example

8. Right-click on the service profile named RedHat_5.3-Server01 and select KVM Console from the menu.

You can also monitor the status of the request from this view.


Launch the website created by the BMC BladeLogic Server Automation Console

IMPORTANT: Do not proceed to the website until the Tasks in Progress have completed. Doing so might disrupt the provisioning

process, in which case the demonstration will need to be started again from the beginning.

1. From the BMC Server Automation Console, verify that all tasks in the Tasks in Progress section have completed. You can

close the KVM console once the rhweb 1 login prompt appears.

2. From the demonstration workstation, launch Internet Explorer (IE).

3. From IE Favorites click JPetStore Demo to open the website that was just created.

4. Browse the e-commerce website and purchase the pet of your choice.

a. Click on an animal.

b. Click on a Product ID. Click Add to Cart.

c. Update the cart if necessary.

d. Click Proceed to Checkout.

e. Review the Checkout Summary. Click Continue.

f. Click Submit.


Figure 65. JPetStore Home Page


Deprovision Server Created For BMC BladeLogic

Follow the steps below to deprovision the server used for the JPetStore.

1. From the BMC Server Automation Console, expand Servers > UCS Managers.

2. Double-click blappucs.

3. In the right pane, expand BladeLogic UCS Manager > 198.18.0.10 > Organization > org-root > Profiles.

4. Select ls-RedHat_5.3-Server01, and then right-click and select Delete Profile from the drop-down list.

5. The Delete Profile Wizard will open.

a. On the Reclaim Identities window, click Next.

b. On the Devices to delete window, click Next.

c. On the Servers to decommission window, under Servers, select the server listed and then move it to the Servers to

decommission section. Click Finish.



Appendix A. Save Your Customized Demonstration

To perform a custom save of the UCS demonstration, follow the steps below, after you have completed your customizations.

Customizations made to the UCS Manager may not load correctly when attempting to run the custom demo if the steps below are

not followed.

IMPORTANT: If you completed the Create E-Commerce Web Server Using BMC BladeLogic Server Automation Console task,

you must deprovision the e-commerce web server, before completing the steps below. To deprovision the e-commerce web

server, follow the steps in the Deprovision Server Created For BMC BladeLogic task.

The e-commerce web server cannot be saved and will need to be provisioned again when the custom demo is started, if needed.

1. Complete all customizations to your demonstration before continuing.

2. On the demonstration workstation, go to the C: drive and open the folder named Scripts.

3. In the Scripts folder, locate the file named Custom_Demo_Save_Pre-Script.bat and then double-click on the file.

A command window will open to execute the script and will close when the script has completed.

This script will save any customizations to the UCS Manager and prepare the demo environment for a clean save. Part of this

process involves clearing all hosts and VMs that have been added to the vCenter.

Do not run the Custom_Demo_Save_Pre-Script.bat script until after you have completed all customizations.

4. After the Custom_Demo_Save_Pre-Script.bat script has completed, go to the Cisco dCloud UI. Go to My Dashboard > My

Demonstrations and save your customized UCS demonstration.

NOTE: When starting your custom, saved UCS demonstration, it may take longer than the normal 15 minutes for the demo session

environment to be ready as your customizations are applied.

ucs_2.2_v1_demo_script_2014-01-10

Documents

demonstration environment

demonstration requirements

active demonstration

preconfigured demonstration

demonstration scenarios

demonstration location

demonstration flow

demonstration preparation