1 Deploying the VDS-OS As a Virtual Machine

1 Deploying the VDS-OS As a Virtual Machine
CH AP TE R
1
Deploying the VDS-OS As a Virtual Machine
This chapter provides detailed instructions for deploying VDS-OS as a virtual machine (VM).
VDS-OS provides the basic VM configuration automatically when you deploy through an OVA image
using vSphere, PowerCLI, or similar software, connected through a vCenter or connected directly to an
ESXi host.
•
Deploying a VM Using vSphere, page 1-1
– Deploying a VM Using vCenter (Recommended), page 1-1
– Deploying a Stand-Alone VM Without vCenter, page 1-4
•
Deploying a VM Using a Power CLI Script, page 1-6
•
Configuring the UCS B200 for Load Balancing, page 1-7
– Add a vNIC Adapter Policy, page 1-7
– Add a vNIC to the Host, page 1-7
– Configure the vNIC, page 1-7
Deploying a VM Using vSphere
Log in to vSphere using:
•
The IP address, or hostname and domain, of the vCenter that manages the hypervisor host
•
The IP address, or hostname and domain, of the hypervisor
Deploying a VM Using vCenter (Recommended)
Step 1
From the File menu, select Deploy OVF Template, then select the OVA file.
Step 2
Accept the license agreement.
Step 3
Enter the name of the VM, its location (data-center), and its data-store.
Step 4
Select the deployment configuration.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-1
Chapter 1
Deploying the VDS-OS As a Virtual Machine
Deploying a VM Using vSphere
VM Product
Cores
RAM
Hard Disk
Network
Minimal VDS-OS
4
16 GB
64 GB
Ten 10GEthernet
Standard VDS-OS
8
28 GB
64 GB
Ten 10GEthernet
VOSM
4
4 GB
64 GB
Ten 10GEthernet
Step 5
Select the disk format. We recommend Thick Provision Eager Zeroed, but consult your lab
administrator if you are not sure.
Step 6
Select the OVF properties to customize the VM deployment.
Configure the device:
a.
Note
Enter the hostname.
Do not enter the fully qualified domain name (FQDN) in the Hostname field. Enter only the local
hostname. For example, if the FQDN is vosm.cisco.com, enter only vosm.
b.
Select a management role. This is required for VOSM mode.
c.
Enter the primary management IP (the VOSM IP address). This is required for VDS-OS mode and
for the VOSM Standby role.
d.
Select the checkbox to enable CMS.
If you do not select the checkbox, the property is ignored and the CLI takes precedence.
Configure the network parameters:
a.
Enter the IP address and subnet mask for Network Adapter 1.
If you do not enter an IP address or subnet mask, the configuration on the first interface defaults to
ip address dhcp.
If you set the hostname of a device before powering it on, you can use DHCP to provide a specific
IP address. When it powers up, the device can then communicate with a DHCP server and obtain the
IP address.
b.
Enter the default gateway.
c.
Select the checkbox to set Network Adapter 1 as the primary interface.
If you do not select the checkbox, the property is ignored and the CLI takes precedence.
You can assign the first interface for which you assign an IP address as the primary interface.
You cannot assign the primary interface if the first interface is configured for DHCP instead of static
IP address.
Step 7
Note
Click Finish to deploy the OVA and create the VM.
It can take up to 15 minutes to create the VM.

After the VM has been successfully created, if you need to fine-tune the VM, right-click the VM, then
select Edit Settings . . .
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-2
OL-28084-04
Chapter 1
Deploying the VDS-OS As a Virtual Machine
Deploying a VM Using vSphere
Step 8
Power on the VM.
The OVF properties are applied only when you first boot up. To modify the properties, use the CLI to
customize the VM.
Step 1
Select Open Console and log in using admin as the username and the default password.
Step 2
Verify network connectivity by pinging the default gateway IP address.
Step 3
Verify that you can ping the VM from your workstation.
Step 4
Log in to the VM using admin as the username and the default password.
Note
Step 5
To release the cursor, press CTRL+ALT (Windows) or CTRL+OPTION (Mac).
Verify that the device mode is set to virtual-origin-system-manager, by entering the following
commands:
vosm#show device-mode current
Current device mode: virtual-origin-system-manager
If it is not set to virtual-origin-system-manager, set it and reload the server, by entering the following
commands:
vosm(config)#device mode virtual-origin-system-manager
vosm#reload
vosm# reload?[confirm]
Step 6
Note
Step 7
Verify that the primary interface is set to tenGigabitEthernet 1/0 using the show run command.
If you set Network Adapter 1 as the primary interface when you configured the network parameters, the
primary interface should be set correctly.
Set the NTP server and the DNS server.
vosm(config)#ntp server ?
Hostname or A.B.C.D or X:X:X:X: :X
NTP server name or IP address (maximum of 4)
vosm(config)#ip name-server ?
A.B.C.D or X:X:X:X: :X Domain server IP address (maximum of 8)
Step 8
Verify that the CMS is running.
vosm#show cms processes
Service cms_httpd is running
Service cms_vosm is running
If it is not running, enable it.
vosm(config)#cms enable
vosm#show cms info
VDS-OS information :
Model
Node Id
Device Mode
Current VOSM role
CMS services information :
=
=
=
=
GENERIC
173
vosm
Primary
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-3
Chapter 1
Deploying the VDS-OS As a Virtual Machine
Deploying a VM Using vSphere
Service cms_httpd is running
Service cms_vosm is running
Step 9
You can now access the GUI from your browser.
Step 10
Enter configuration mode.
Step 11
Enter the interface IP addresses.
To enable the DHCP server to choose the IP addresses, enter ip address dhcp.
For DHCP IP addresses obtained via DHCP client IDs, enter ip address dhcp client-id id, and configure
the DHCP server to expect this DHCP client ID.
Step 12
Enter the default gateway: ip default-gateway ip
Step 13
Enable Telnet, if required.
Step 14
Enter the VOSM IP address.
Step 15
Select the checkbox to enable CMS.
Step 16
Enter the hostname.
Step 17
Enter the device mode.
Step 18
Restart the VM.
After the above steps, the VM is up and running and can be reached (via VOSM web interface/ telnet)
for further application-level configuration.
Deploying a Stand-Alone VM Without vCenter
Step 1
From the File menu, select Deploy OVF Template, then select the OVA file.
Step 2
Accept the license agreement.
Step 3
Enter the name of the VM, its location (data-center), and its data-store.
Step 4
Select the deployment configuration.
VM Product
Cores
RAM
Hard Disk
Network
Minimal VDS-OS
4
16 GB
64 GB
Ten 10GEthernet
Standard VDS-OS
8
28 GB
64 GB
Ten 10GEthernet
VOSM
4
4 GB
64 GB
Ten 10GEthernet
Step 5
Select the disk format. We recommend Thick Provision Eager Zeroed, but consult your lab
administrator if you are not sure.
Step 6
Click Finish to deploy the OVA and create the VM.
Note
It can take up to 15 minutes to create the VM.

After the VM has been successfully created, if you need to fine-tune the VM, right-click the VM, then
select Edit Settings . . .
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-4
OL-28084-04
Chapter 1
Deploying the VDS-OS As a Virtual Machine
Deploying a VM Using vSphere
Step 7
Power on the VM.
To modify the properties the first time, use the CLI to customize the VM.
Step 1
Select Open Console and log in using admin as the username and the default password.
Step 2
Verify network connectivity by pinging the default gateway IP address.
Step 3
Verify that you can ping the VM from your workstation.
Step 4
Log in to the VM using admin as the username and the default password.
Note
To release the cursor, press CTRL+ALT (Windows) or CTRL+OPTION (Mac).
Step 5
Verify that the device mode is set to virtual-origin-system-manager. If it is not set to
virtual-origin-system-manager, set it and reload the server.
Step 6
Verify that the primary interface is set to tenGigabitEthernet 1/0 using the show run command.
Note
If you set Network Adapter 1 as the primary interface when you configured the network parameters, the
primary interface should be set correctly.
Step 7
Set the NTP server and the DNS server.
Step 8
Verify that the CMS is running. If it is not running, enable it.
Step 9
You can now access the GUI from your browser.
Step 10
Enter configuration mode.
Step 11
Enter the interface IP addresses.
To enable the DHCP server to choose the IP addresses, enter ip address dhcp.
For DHCP IP addresses obtained via DHCP client IDs, enter ip address dhcp client-id id, and configure
the DHCP server to expect this DHCP client ID.
Step 12
Enter the default gateway: ip default-gateway ip
Step 13
Enable Telnet, if required.
Step 14
Enter the VOSM IP address.
Step 15
Select the checkbox to enable CMS.
Step 16
Verify that the default gateway can be reached.
After the above steps, the VM is up and running and can be reached (via VOSM web interface/ telnet)
for further application-level configuration.
You can further modify the configuration, through the console or via Telnet into the VM, by entering the
appropriate configuration in configuration mode.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-5
Chapter 1
Deploying the VDS-OS As a Virtual Machine
Deploying a VM Using a Power CLI Script
Deploying a VM Using a Power CLI Script
You can use PowerCLI scripts to customize the VM properties. For example, the following script sets
the device-mode property to SE. You can use similar scripts to set other properties.
# Sample Script for setting OVA properties
Function Wait-vShieldBoot {
do {
$VM = Get-VM $VosHostName
Sleep 5
} until ($VM.ToolsStatus -eq “toolsOK”)
}
$Newproperty = New-VIProperty -Name ToolsStatus -ObjectType VirtualMachine -Value {
param($vm)
$vm.ExtensionData.Guest.ToolsStatus
} -Force
#
# Set parameters
#
$VosOVA = “C:\Users\bhagatyj\Documents\work\vmware\packaging\ovfs\vos_ovf.ova“
$VosHostName = “Vos-120“
$vShieldFQDN = “vshield.virtu-al.local“
$VosDS = “phy-ds-2“
$VosUser = “admin“
$VosPass = “default“
$vCenter = “deming-vc.cisco.com“
$vcUsername = “root“
$vcPass = “vmware“
#
# Execution starts here
#
Write-Host “Connecting to vCenter“
$Connect = Connect-VIServer $vCenter -User $vcUsername -Password $vcPass
Write-Host “Importing the OVF file“
$va = Import-VApp -Name $VosHostName -Datastore $VosDS -VMHost bhagatyj-ucs2.cisco.com
-Source $VosOVA
$vm = Get-VM -Name $VosHostName
$spec = New-Object VMware.Vim.VirtualMachineConfigSpec
$spec.VAppConfig = New-Object VMWare.Vim.VmConfigSpec
$newProp = New-Object VMWare.Vim.VAppPropertySpec
$newProp.Operation = “edit“
$prop = $vm.ExtensionData.Config.VAppConfig.Property | where {$_.Id -eq “devicemode“}
$prop.Value = “se“
$newProp.Info = $prop
$spec.VAppConfig.Property += $newProp
$vm.ExtensionData.ReconfigVM($spec)
Write-Host “Starting the vShield VM“
$Start = Start-VM $VosHostName -Confirm:$false
#Write-Host “Waiting until the vShield VM has started“
#Wait-vShieldBoot
Write-Host “Configuration Complete“
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-6
OL-28084-04
Chapter 1
Deploying the VDS-OS As a Virtual Machine
Configuring the UCS B200 for Load Balancing
Configuring the UCS B200 for Load Balancing
To enable adapter load balancing, use the UCSM GUI to configure the UCS B200 to expose the vNICs
to the host server.
Note
This procedure applies whether the UCSB is stand-alone or is communicating with the Fabric
Interconnect using the GUI.
Add a vNIC Adapter Policy
To optimize load balancing among all virtual CPU cores, you must first create a new adapter policy.
Step 1
Select the Servers tab.
Step 2
In the left pane, expand Servers > Policies > root > Adapter Policies.
Step 3
In the right pane, click Add. The Create Ethernet Adapter Policy window is displayed.
Step 4
Enter a name for the adapter policy, such as Load-Balanced_32.
Step 5
Under Resources, set the following values for the policy:
Step 6
a.
Set Transient Queues to 1.
b.
Set the number of Receive Queues to n, where n is the number of virtual CPU cores. For example,
for 32 virtual CPU cores, set Receive Queues to 32.
c.
Set Completion Queues to n+1, or 33 in our example.
d.
Set Interrupts to n+3, or 35 in our example.
Under Options, enable Received Side Scaling and set the Fallback Timeout to 2 seconds.
Add a vNIC to the Host
Step 1
Select the Servers tab.
Step 2
In the left pane, select the vNICs entry under the service profile of the host server.
Step 3
In the right pane, click Add.
Configure the vNIC
Step 1
On the Create vNIC page, enter a name for the vNIC.
Step 2
Enter a MAC address.
Step 3
At the bottom of the page, select the Adapter Policy that you created earlier, such as Load-Balanced_32.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-7
Chapter 1
Deploying the VDS-OS As a Virtual Machine
Configuring the UCS B200 for Load Balancing
Step 4
Save the policy changes and reboot when prompted to do so.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-8
OL-28084-04
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising