1 Cisco Unified Computing System Express Overview
• Cisco Services Ready Engine (SRE) multipurpose x86 blade servers
• Cisco SRE Virtualization (SRE-V) powered by VMware vSphere Hypervisor™ (ESXi)
• Cisco Integrated Management Controller Express (CIMCE) for the SRE blades
Key Product Features
• Ready-to-use general-purpose x86 blade servers
• Enterprise- and production-class bare-metal hypervisor
• Remote management with network and server separation
• Integrated backplane switch for multigigabit connectivity
• Compact, all-in-one networking and computing system
Key Customer Value Propositions
• Consolidate and simplify branch-office infrastructure into one device
• Reduce total cost of ownership (TCO) of branch-office infrastructure
• Optimize branch-office infrastructure for essential edge applications
• Improve application uptime, recovery time, and deployment time
• Maximize infrastructure usage and investment protection
1.1 Cisco Services Ready Engine
Key Product Features
• Versatile platform for hosting Cisco, third-party, and custom applications
• High-performance, high-availability, and high-capacity hardware
• Centralized management and troubleshooting
• Small physical, energy, and carbon footprint
• On-demand application provisioning
Key Customer Value Propositions
• Simplify branch-office infrastructure by consolidating applications into the ISR G2
• Adapt branch-office services to business needs by deploying applications on demand
• Save on the cost of onsite visits, utility bills, and hardware support contracts
Figure 1. Service Modules (SM-SRE)
1.2 Services Ready Engine Virtualization (SRE-V)
Figure 2. Conceptual Overview of Services Ready Engine Virtualization
1.3 Cisco Integrated Management Controller Express
Key Product Features
• Low-level hardware management
• Standard network configuration
• On-demand application provisioning
• Out of band management
Figure 3. Cisco Integrated Management Controller Express Web Interface
2 The SRE-V Lab
• One ISR G2 (2911, 2921, 2951, 3925, 3925E, 3945 or 3945E)
• One SM-SRE (SM-SRE-700-K9 or SM-SRE-900-K9)
• A PC running Windows OS with VMware vSphere Client 4.1 or above
• A server running FTP and NFS service
• A layer three switch
• Windows 2003 ISO image
• A prebuilt virtual machine (VMDK and VMX files) using Window 2003 SE image
Figure 4. Lab Topology
Components within our lab:
• SM-SRE-700-K9 plugged into Slot 1 of ISR G2 2911 running IOS version 15.1.3T
• A PC running Windows OS (IP Address: 10.1.10.10) with VMware vSphere Client 4.1. Windows 2003 ISO file and perbuilt VM are also kept on this PC on E:\ drive within Software directory
• A server (IP Address: 10.10.0.20) running FTP and NFS service hosting SRE-V 1.0.1 image files
• A layer three switch connecting PC, server, router and external network interface of SRE
3 Configure Network Interfaces of SM-SRE Service Module
• IP address of the Cisco router that contains the Cisco SRE Service Module
• Username and password for logging into the router
• One Gigabit Ethernet interface connects to the router Peripheral Component Interconnect Express (PCIe) (refer to interface GE0 in Figure 5). This interface is sm slot/0 and is configured through the Cisco IOS Software CLI.
• The other Gigabit Ethernet interface connects to the multigigabit fabric (MGF) (refer to interface GE1 in Figure 5). This interface, sm slot/1, is also configured through the Cisco IOS Software CLI. After the interface is configured, the vSphere client communicates with the VMware vSphere Hypervisor™ through this interface.
Once configured vSphere client communicates with the VMware vSphere Hypervisor™ through this interface.
Figure 5. Block Diagram of Cisco SRE 900 Service Module
3.1 Configuring Service Module Slot/0 and Service Module Slot/1 Interface(s)
• Successfully configure the SRE-V console manager IP address and default gateway
• Successfully configure the VMware vSphere Hypervisor™ IP address
• Successfully configure the service-module slot/1 interface in trunk mode
• Successfully configure VLAN 1 to be used by VMware vSphere Hypervisor™
Figure 6. Conceptual Diagram of IP Address Assignment for POD 1 (P=1)
• Service-module IP address is assigned to console manager (10.P.20.2).
• Service-module MGF IP address is assigned to VMware vSphere Hypervisor™ (10.P.30.2).
Step 1. Configure ISR G2 with the following IP addressing scheme:
4 Installing, Validating, and Activating SRE-V Software
• Preinstalled with SRE-V software
• Preinstalled with SRE-V software and Windows 2008 R2 64-bit operating system
• Preinstalled with any other applicable application available on the SRE platform; for example, the Cisco Application Extension Platform (AXP), Cisco Wide Area Application Services (WAAS), Cisco Unity® Express, etc.
4.1 Installing SRE-V Software on SM-SRE Service Module
• Successfully install SRE-V infrastructure software
Step 1. Installing SRE-V infrastructure software
Issue the following command to install SRE-V infrastructure software on the SRE hardware using the Cisco IOS Software CLI. You can also use Cisco Configuration Professional or the CiscoWorks LAN Management Solution (LMS) GUI tool to install SRE-V software on one or multiple devices with a few simple clicks.
Router# service-module sm 1/0 install url ftp://10.10.0.20/sre-v-k9.smv.1.0.1.pkg
Note: Our SRE-V install image is kept on FTP server within the root folder. Make sure to change the CLI path appropriately based on where your SRE-V image is kept. SRE-V install will take about four minutes.
Note: It will take about four minutes to install the application.
4.2 Validating SRE-V Software Installation
• Successfully validate installation of SRE-V infrastructure software
Step 1. Validating installation of SRE-V infrastructure software
Issue the following command to validate existence of SRE-V infrastructure software on the SRE hardware using the Cisco IOS Software CLI. You can also use Cisco Configuration Professional or the CiscoWorks LMS GUI tool to view which application is installed on the SRE hardware.
4.3 Activating SRE-V Evaluation License
• VMware vSphere Hypervisor™ Evaluation License: The 60-day evaluation license is bundled with the Cisco SRE-V software image, which you can use to evaluate the hosting environment. Evaluation license requires activation. The End User License Agreement (EULA) must be accepted before the evaluation license is activated.
• Permanent VMware vSphere Hypervisor™ Host License: You can order this perpetual license either along with the VMware vSphere Hypervisor™ software or separately when the built-in evaluation license expires. After permanent licenses are installed, they provide all the permissions necessary to access features in the software image. All permanent licenses are node-locked and validated by the licensing infrastructure during software installation. After a permanent license is installed, you do not need to upgrade it for subsequent releases. Table 1 lists the part numbers for featured licenses.
Table 1. Featured License Part Numbers
• Successfully activate the SRE-V evaluation license
Step 1. Activate SRE-V infrastructure software
Issue the following command to validate the existence of SRE-V infrastructure software on the SRE hardware using the Cisco IOS Software CLI.
Note: Activation of SRE-V license is done from SRE-V CLI and not from IOS CLI i.e. you need to session into the module before executing this CLI.
Router# service-module sm 1/0 session
SRE-Module# license activate sreVHost
ACCEPT? [y/n]? y
Step 2. Configure Hypervisor's Gateway
View and configure SRE-V's gateway by executing show hypervisor ip and hypervisor set ip default-gateway CLI respectively.
SRE-Module# show hypervisor ip
Default Gateway: None
SRE-Module# hypervisor set ip default-gateway 10. P.30.1
Step 3. Reload the service module (SM-SRE) for license activation to take effect. You need to issue this command from the Router. Exit from Service-Module prompt and then issue this CLI.
Issue the reload command; when prompted to confirm, press Enter. The system continues with the reboot.
5 Configuring User(s), Group(s), Role(s), and Permission(s)
• Successfully create users
• Successfully create groups
• Successfully create roles and add privileges to roles
• Successfully add roles to user groups
5.1 Creating User(s)
• Successfully create two SRE-V users
• Successfully update a user's password
• Successfully delete a user
Step 1. Creating user(s) using the console-manager CLI:
Service-Module# user create jsmith password Usr!234 [fullname "John Smith" ]
Service-Module# user create rlee password rob!123 [fullname "Robert Lee" ]
Step 2. Update user jsmith's password using the console-manager CLI:
Step 3. Delete user rlee using the console-manager CLI:
Note: When you delete a specific user, the user group to which the user belongs to is not deleted, nor is the role that was assigned to that user deleted.
5.2 Creating Group(s)
• Successfully create two SRE-V groups
• Successfully add user(s) to group(s)
• Successfully delete a group
Step 1. Create group(s) using the console-manager CLI:
Step 2. Update group SuperAdmins with user jsmith using the console-manager CLI:
Step 3. Delete group BasicAdmins using the console-manager CLI:
Note: When you delete a specific group, the user accounts that belong to the group are not deleted, nor are the roles that are assigned to that group.
5.3 Creating Role(s)
• Successfully create two SRE-V roles
• Understand what privilege and privilege group signify
• Successfully add privileges and remove privileges from a role
• Successfully delete a role
Step 1. Create role(s) using the console-manager CLI:
Step 2. Understand what privilege and privilege group signify:
• The VirtualMachine.Config.AddNewDisk privilege belongs to the privilege group called VirtualMachine.Config.
• The VirtualMachine.Config privilege group also has other privileges besides the VirtualMachine.Config.AddNewDisk privilege.
Step 3. Add and remove privileges and privilege groups from a role using the console-manager CLI:
Step 4. Delete a role using the console-manager CLI:
5.4 Working with Permissions: Adding Roles to User(s) or User Group(s)
• Successfully assign a role to a user
• Successfully assign a role to a group
• Successfully remove a role from a user
Step 1. Assign a role to a user:
Service-Module# permission add SuperRole user jsmith [virtual-machine VM ]
Service-Module# permission add SuperRole user jsmith [nopropogate]
• virtual-machine VM (optional): This command gives the user permission to access the specified virtual machine. Role permissions are provided at object level in ESXi. Without the virtual-machine keyword in this command, the user has the permission to access all of the virtual machines in the system.
• Nopropogate (optional): This command does not allow role permissions to be propagated to the sub-entities of the host. Without the nopropogate keyword, permissions are propagated to the granted object.
Step 2. Assign a role to a group:
Service-Module# permission add SuperRole group SuperAdmins [virtual-machine VM ]
Service-Module# permission add SuperRole group SuperAdmins [nopropogate]
Step 3. Revoke a role from a user:
6 The VMware vSphere Hypervisor™
6.1 Connecting to VMware vSphere Hypervisor™
Step 1. Launch vSphere client and enter the following information. Upon the prompt, click Ignore and proceed (Figure 7):
• IP address: 10.P.30.2
• Username: esx-admin
• Password: change_it
Figure 7. VMware vSphere Client
Step 2. Validate connectivity to the VMware vSphere Hypervisor™ (Figure 8).
Figure 8. Connectivity Validation
7 SRE-V Networking
• vSwitch0: This switch uses the MGF interface to connect the VMware vSphere Hypervisor™ and the guest virtual machines to the outside world. The MGF interface is sm slot/1. vSwitch0 contains two port groups:
– Management network: Used by the VMware vSphere Hypervisor™ to connect to the vSphere client
– VM network: Used by the guest virtual machines to connect to the outside world
• ciscoSwitchLocal: This switch contains CiscoReservedLocal port group, which is used for internal communication between the console manager and the VMware vSphere Hypervisor™.
• ciscoSwitch: This switch contains the CiscoReserved port group, which is used for the following:
– External connection to the Cisco SRE Service Module management interface, such as Secure Shell (SSH) Protocol, Cisco Licensing Manager (CLM), and the web service application programming interface (API)
– Internal communication between the Cisco ISR G2 and the Cisco SRE Service Module
7.1 Understanding Preexisting vSwitch(es)
• Understand vSwitches in the SRE-V Hypervisor™
Step 1. First click the Configuration tab and then click Networking (Figure 9).
Figure 9. Virtual Switches
Even if you live and breathe hypervisor(s) do not delete or modify the following:
• vSwitch0: Management network
• ciscoSwitchLocal: CiscoReservedLocal
• ciscoSwitch: CiscoReserved
7.2 Creating a vSwitch
• Successfully create a vSwitch
Step 1. Click the Add Networking link at the top right of the screen and select Virtual Machine (Figure 10).
Figure 10. Adding a Virtual Machine
Step 2. Select Create a virtual switch and select vmnic0 (Figure 11).
Figure 11. Creating a Virtual Switch
Step 3. Give the port group a name: VM Network External Port and leave the VLAN ID as it is (Figure 12).
Figure 12. Giving Port Group a Name
Step 4. Click Finish (Figure 13).
Figure 13. Virtual Switches Configured
Step 5. Validate creation of vSwitch1 (Figure 14) and click on Properties
Figure 14. Validating Creation of vSwitch1
7.3 Modifying vSwitch or Port-Group Properties
• Successfully modify vSwitch properties
Step 1. Select vSwitch and click Edit (Figure 15).
Figure 15. Modifying vSwitch Properties
Step 2. Select the General tab and leave the port number unchanged; then select the Security tab and change Promiscuous mode to Accept (Figure 16).
Figure 16. Changing Promiscuous Mode
Step 3. Select Traffic Shaping and update Policy Exception Status to Enabled. Leave NIC Teaming at the default settings and click OK (Figure 17).
Figure 17. Changing Status of Traffic Shaping
Step 4. Select Network Adapters, click Edit, and view its settings (Figure 18).
Figure 18. Editing Network-Adapter Settings
8 SRE-V Storage
• Successfully create a datastore using the network file system (NFS).
Step 1. Click the Configuration tab; then click Storage and then Add Storage (Figure 19).
Figure 19. Adding Storage
Step 2. Select Network File System and then click Next (Figure 20).
Figure 20. Selecting Storage Type
Step 3. Enter IP: 10.10.0.20, Folder: /NFS_PX. Enter Datastore Name: NFS_PX and click Next (Figure 21). X is the number of your POD. Make sure you have setup a folder which is being shared using NFS protocol.
Figure 21. Naming Datastore
Step 4. Click Finish and validate creation of a datastore (Figure 22).
Figure 22. Validating Creation of Datastore
9 SRE-V Virtual Machine(s)
9.1 Creating Virtual Machine(s)
• Successfully create two virtual machines
• Successfully modify virtual machines
Step 1. Invoke the virtual-machine creation wizard.
Figure 23. Virtual-Machine Creation Wizard
Step 2. Select Custom and click Next (Figure 24).
Figure 24. Custom Creation of Virtual Machine
Step 3. Provide a name to the virtual machine; for example, VM-Retail (Figure 25).
Figure 25. Naming the New Virtual Machine
Step 4. Select datastore1. That is where virtual-machine's files should be kept and click Next (Figure 26).
Figure 26. Selecting Datastore for Virtual-Machine Files
Step 5. Select Virtual Machine 7 for compatibility with the newer version of VMware products (Figure 27).
Figure 27. Selecting Virtual Machine for Compatibility with Newer VMware Products
Step 6. Select the operating system that you plan to install: Window 2003 Standard Edition (32 Bit). (Refer to Figure 28.)
Figure 28. Selecting Operating System to Install
Step 7. Enter the amount of memory you want to allocate. For now enter 1024 MB and click Next (Figure 29).
Figure 29. Memory Configuration
Step 8. Select VM Network External Port network interface and click Next (Figure 30).
Figure 30. Selecting Network Interface
Step 9. Select LSI Logic Parallel and click Next (Figure 31).
Figure 31. SCSI Controller Settings
Step 10. Leave the default settings Create a new virtual disk and click Next (Figure 32).
Figure 32. Selecting Disk
Step 11. Enter Disk Size 2 GB, leave the rest as default, and click Next (Figure 33).
Figure 33. Selecting Disk Size
Step 12. Leave the default options as they are and click Next (Figure 34).
Figure 34. Advanced Options
Step 13. Click Finish (Figure 35).
Figure 35. Completion of New Virtual Machine Creation
9.2 Installing Operating System from an ISO
• Successfully mount a client device and install an operating system
• Successfully mount an ISO from a datastore and install an operating system
Step 1. Select VM-Retail and click Edit Setting under the Summary tab (Figure 36).
Figure 36. Editing Virtual-Machine Settings
Step 2. Click CD/DVD Drive under the Hardware tab and select Client Device (Figure 37).
Figure 37. Client Device for CD/DVD Drive
Figure 38. Datastore ISO Image (This is an example to show that image can also be kept on the datastore).
Note: Do not execute this step
Step 3. Under the Summary Tab click Power On and then click Open Console (Figure 39).
Figure 39. Summary Tab
Step 4. You should see a screen similar to Figure 40.
Figure 40. VM-Retail Booting
Step 5. Click the icon and select Connect to ISO image on local disk. Browse to E:\Software and select Win2k3.iso (Figure 41).
Figure 41. Connecting to ISO Image
Note: Point to the Windows 2003 ISO file or any other Windows IOS file you have available within your setup.
Step 6. Click VM > Guest > Send Ctrl+Alt+del (Figure 42).
Figure 42. Rebooting VM-Retail
Step 7. Keep using defaults and continue installation of the Windows 2003 operating system. When prompted, enter VM-Retail as Computer Name and cisco as Administrator Password (Figure 43).
Figure 43. Installing Windows
Step 8. Select Typical settings and enter Cisco in the Work Group textbox. When the operating system finishes installation, click VM > Guest > Send Ctrl+Alt+del and enter Administrator and cisco as username and password, respectively (Figure 44).
Figure 44. Administrator Username and Password
Note: Ignore any messages that pop-up during first login.
9.3 Building a Virtual Machine Using Preexisting VMDK file
• Successfully create a virtual machine using VMDK
Step 1. Click Configuration > Storage. Right click datastore1 and click Browse. Click the icon and select Upload Folder. Identify the location where you have kept a prebuilt Virtual Machine (VMDK and VMX files). In our setup the images are saved on the PC at the following location E:\Software\VM-Healthcare.
Copy over E:\Software\VM-Healthcare (Figure 45). We assume you have a preexisting VMDK, if not build a VM and save the files on your PC.
Figure 45. Uploading a Folder
Step 2. Start the virtual-machine creation wizard. Select Custom and click Next (Figure 46). Refer to 9.1 for more information.
Figure 46. Custom Configuration
Step 3. Provide a name to the virtual machine: VM-Healthcare and click Next (Figure 47).
Figure 47. Naming the Virtual Machine
Step 4. Select datastore1. That is where virtual-machine's files should be kept and click Next (Figure 26).
Figure 48. Selecting Datastore for Virtual-Machine Files
Step 5. Select Virtual Machine 7 for compatibility with the newer versions of VMware products (Figure 49).
Figure 49. Selecting Virtual Machine for Compatibility with Newer Versions of VMware Products
Step 6. Select the operating system that you plan to install: Window 2003 Standard Edition (32 Bit) and click Next (Figure 50).
Figure 50. Choosing Operating System to Install
Step 7. Enter the amount of memory you want to allocate. For now enter 512 MB and click Next (Figure 51).
Figure 51. Choosing Memory
Step 8. Select VM Network interface and click Next (Figure 52).
Figure 52. Choosing Virtual-Machine Network
Step 9. Select LSI Logic Parallel and click Next (Figure 53).
Figure 53. SCSI Controller Settings
Step 10. Select Use an existing virtual disk and click Next (Figure 54).
Figure 54. Selecting a Disk
Step 11. Browse and select datastore1 > VM-Healthcare > VM-Healthcare.vmdk and click Next (Figure 55).
Figure 55. Browsing VMDK File
Step 12. Leave the default options as they are and click Next (Figure 56).
Figure 56. Default Options
Step 13. Click Finish (Figure 57).
Figure 57. Completion
Step 14. Start the virtual machine and log in with username Administrator and password cisco (Figure 58).
Figure 58. Starting Virtual Machine
9.4 Configure Networking (External) for a Virtual Machine (VM-Retail)
• Successfully configure the IP address and validate connectivity
Step 1. Click Start > Control Panel > Network Connections > Local Area Connection (Figure 59).
Figure 59. Configuring Local Area Connection
Step 2. Click Properties > Internet Protocol (TCP/IP) > Properties and enter the following details and click OK, OK and Close (Figure 60):
• IP address: 10.1.100.P
• Subnet mask: 255.255.255.0
• Default gateway: 10.1.100.254
Figure 60. Properties
Step 3. Launch the command prompt and test connectivity to 10.1.100.254 and to other virtual machines. Ask your instructor for IP addresses for other virtual machines (Figure 61).
Figure 61. Command Prompt
9.5 Configure Networking (Internal) for a Virtual Machine (VM-Healthcare)
• Successfully configure IP address and validate connectivity of virtual machines
Step 1. Click Start > Control Panel > Network Connections > Local Area Connection (Figure 62).
Figure 62. Configuring Local Area Connection
Step 2. Click Properties > Internet Protocol (TCP/IP) > Properties and enter the following details and click on OK, OK and Close (Figure 63).
• IP address: 10.P.30.3
• Subnet mask: 255.255.255.0
• Default gateway: 10.P.30.1
Figure 63. Properties
Step 3. Launch the command prompt and test connectivity to 10.P.30.1, 10.P.10.1, and 10.P.20.1. (Figure 64). Refer to 3.1 to understand which IP corresponds to which interface
Figure 64. Command Prompt
9.6 Advanced Network Configuration (VLANs)
• Successfully create two port groups in a vSwitch
• Successfully assign virtual networks to virtual machines
• Successfully configure IP addresses for virtual machines
• Successfully configure VLANs on the router
Creating Port Group(s)
Step 1. Click Configuration > Networking and select Properties for vSwitch0 (Figure 65).
Figure 65. vSwitch0 Configuration
Step 2. Click Add (Figure 66).
Figure 66. Creating a Port Group
Step 3. Select Virtual Machine and click Next (Figure 67).
Figure 67. Creating Connection Type
Step 4. Provide a name to the port group: VM Network - Retail, enter VLANID 40, and click Next (Figure 68).
Figure 68. Port Group Properties
Step 5. Click Finish (Figure 69).
Figure 69. Completion of Port Group Creation
Step 6. Click Add (Figure 70).
Figure 70. Creating a Port Group
Step 7. Select Virtual Machine and click Next (Figure 71).
Figure 71. Creating Connection Type
Step 8. Provide a name to the port group: VM Network - Healthcare, enter VLANID 50, and click Next (Figure 72).
Figure 72. Port Group Properties
Step 9. Click Finish (Figure 73).
Figure 73. Completion of Port Group Creation
Step 10. Click Close (Figure 74).
Figure 74. Closing Window
Configuring VLANs on the Router
Step 11. Go back to the router and begin entering the following commands.
Assigning Virtual Machines to Port Group(s)
Step 12. Go back to vSphere client and right click on virtual machine VM-Healthcare, click Edit Settings > Network adapter 1, and select VM Network - Healthcare and click OK (Figure 75).
Figure 75. Editing Virtual Machine's Network Connection
Step 13. Select virtual machine VM-Retail, click Edit Settings > Network adapter 1, and select VM Network - Retail and click OK (Figure 76).
Figure 76. Editing Virtual Machine's Network Connection
Step 14. Validate that your configuration looks like Figure 77 by clicking on Hypervisor's IP > Configuration > Networking.
Figure 77. Configuration Validation
Configuring IP Address of Both Virtual Machines (Refer to section 9.5)
Step 15. Configure the VM-Retail IP address as 10.P.40.2 and the VM-Healthcare IP address as 10.P.50.2. Enter subnet mask as 255.255.255.0 and gateways as 10.P.40.1 and 10.P.50.1, respectively (Figure 78).
Figure 78. Configuring IP Address and Gateway
Step 16. Validate reachability to the router by pinging 10.P.10.1 from both the virtual machines (Figure 79).
Figure 79. Validate Connectivity from VM-Retail and VM-Healthcare
Step 17. Modify allowed VLAN(s) on the router and observe the change in connectivity (Figure 80).
Router(config)# interface sm 1/1
Router(config-if)# switchport trunk allowed vlan remove 40
Figure 80. Command Prompt of VM-Healthcare
Configure an access control list (ACL) on a different VLAN interface and observe the change in connectivity.
10 High-Level Overview of SRE-V Hypervisor Settings
• Observe what is in the Getting Started tab
• Observe what is in the Summary tab
• Observe what is in the Virtual Machine tab
• Observe what is in the Resource Allocation tab
• Observe what is in the Performance tab
• Make Edits under the Configuration tab
• Observe what is in the Local Users & Groups tab
• Observe what is in the Events tab
• Observe what is in the Permissions tab
10.1 Overview of VMware vSphere Hypervisor™ Configuration
Step 1. Getting Started tab (Figure 81).
Figure 81. Getting Started Tab
Step 2. Summary tab (Figure 82).
Figure 82. Summary Tab
Step 3. Virtual Machines tab (Figure 83).
Figure 83. Virtual Machines Tab
Step 4. Resource Allocation tab (Figure 84).
Figure 84. Resource Allocation Tab
Step 5. Performance tab (Figure 85).
Figure 85. Performance Tab
Step 6. Configuration tab (Figure 86).
Figure 86. Configuration Tab
Step 7. Click Configuration Tab > Time Configuration and select Properties then select Options. Click NTP Settings and click Add. Enter Network Time Protocol (NTP) server IP 10.P.10.1 and click OK (Figure 87). Observe the hypervisor synchronizing time with the router. Make sure router is configured to run NTP protocol.
Figure 87. Time Configuration
Step 8. Click Configuration Tab > DNS and Routing Configuration. Click Properties and enter SRE-V and Cisco as your Host Name and Domain respectively. Click OK (Figure 88).
Figure 88. DNS and Routing Configuration
Step 9. Click the Configuration Tab > Virtual Machine Startup and Shutdown option and select Properties. Check the box below System Settings and make edits to Default Startup Delay (Figure 89).
Figure 89. Virtual Machine Startup and Shutdown
Step 10. Click Configuration Tab > Security Profile and select Properties. Observe the services that are running and those that have stopped (Figure 90).
Figure 90. Stopped and Running Services
Step 11. Local Users & Groups tab
Figure 91. Local Users & Groups Tab
Step 12. Events tab (Figure 92).
Figure 92. Events Tab
Step 13. Permissions tab
Figure 93. Permissions Tab
10.2 Overview of Virtual Machine Settings
• Successfully add a USB device to a virtual machine and modify the memory footprint
• Successfully modify the name of a virtual machine
• Successfully modify CPU resource allocation of a virtual machine
Step 1. Click Add and select USB Controller and select defaults to add it to your virtual machine. Now modify Memory Size by reducing it from 1 GB to 512 MB (Figure 94).
Figure 94. Memory Size Modification
Step 2. Click Options and update Virtual Machine Name to anything you wish (Figure 95).
Figure 95. Changing Name of Virtual Machine
Step 3. Click Resources and update Shares to High (Figure 96).
Figure 96. Resource Allocation
11 Understanding Differences Between SRE-V and Standard VMware vSphere Hypervisor™
• Cisco SRE-V enables VMware vSphere Hypervisor™ to be provisioned on a Cisco SRE Service Module, which is integrated in the Cisco ISR G2.
• Configuration of the VMware vSphere Hypervisor™ IP address is done through the Cisco ISR G2.
• Configuration of the user management tasks is done using the Cisco SRE-V CLI instead of the VMware vSphere client.
• License management for the Cisco SRE-V is done through Cisco Software Licensing.
• Software upgrade packages for the Cisco SRE-V are obtained from Cisco.com. Software upgrades are done using the Cisco SRE-V CLI.
• System operation such as firmware settings, advanced settings, and Peripheral Component Interconnect (PCI) Passthru settings are disabled.