Guest

Cisco Videoscape Distribution Suite Service Broker

Cisco VDS Service Broker 1.1 Software Installation Guide for UCS Platforms

  • Viewing Options

  • PDF (3.9 MB)
  • Feedback
Cisco VDS Service Broker 1.1 Software Installation Guide for UCS Platforms

Table Of Contents

Cisco VDS Service Broker 1.1 Software Installation Guide for UCS Platforms

Contents

Before you Begin

Install the Hardware

Connect a UCS Management (CIMC) Port

Connect a USB Keyboard and VGA Monitor

Configure the UCS Hardware

Configure CIMC

Configure the BIOS

Configure the BIOS to Boot from a CD-ROM

Configure Remote Presence

Setting up a UCS C220 for the VDS Service Broker Software

Install the VDS-SB or VDSM 1.1 software

VM Hardware Definition

System Requirements

Deploying the VDS-SB or VDSM Virtual Appliance using vCenter

Deploying the VDS-SB or VDSM Virtual Appliance without vCenter

Replacing Virtual Machines across OVA Releases

Replacing a VDSM

Replacing an Service Broker

Upgrade Procedure

Related Documents

Obtaining Documentation and Submitting a Service Request


Cisco VDS Service Broker 1.1 Software Installation Guide for UCS Platforms


First Published: June 28, 2013

This document provides detailed instructions for installing the Cisco Videoscape Distribution Suite Service Broker (VDS-SB) or Videoscape Distribution Suite Manager (VDSM) 1.1 software on UCS platforms.

Contents

The following information is included in this document:

Before you Begin

Install the Hardware

Connect a UCS Management (CIMC) Port

Connect a USB Keyboard and VGA Monitor

Configure the UCS Hardware

Configure CIMC

Configure the BIOS

Configure the BIOS to Boot from a CD-ROM

Configure Remote Presence

Setting up a UCS C220 for the VDS Service Broker Software

Install the VDS-SB or VDSM 1.1 software

VM Hardware Definition

System Requirements

Deploying the VDS-SB or VDSM Virtual Appliance using vCenter

Replacing Virtual Machines across OVA Releases

Before you Begin

You need the following to install the Cisco Videoscape Distribution Suite Service Broker (VDS-SB) 1.1 software:

VGA monitor

USB keyboard

Minimum of two IP configurations, each with an Ethernet cable attached to a switch—one to the CIMC (UCS Management port) and the other to one of the 6 NICs.


Note The Gigabit Ethernet interfaces are shared between Cisco Integrated Management Controller (CIMC) and UCS for UCS devices. The default values for: duplex, speed, auto negotiation, and advertising must not be changed.



Note The UCS C220 blade server uses the backplane to connect the Ethernet NIC (eNIC) to the internal switch (IOM), and the hardware does not provide an LED to indicate that the NIC is up or connected. So the show_mapping.sh nic script does not make the port LED blink.


Install the Hardware

The first step to getting a UCS platform (blade or server) up and running is to install the it in its physical location. UCS platforms running VDS-SB Release 1.1 software are typically rack-mounted servers, so you are most-likely installing the server to a rack. See the "Installing the Server" section in the Cisco UCS C200 Installation and Service Guide or the "Installing the Server" section of the Cisco UCS C210 Installation and Service Guide for the rack installation procedure for the respective servers.

This document assumes that the following steps have been performed as part of the rack installation process:

Disk bays are populated with disk drives.

Power cable is connected to the server.

For the UCS C220-M3 blade server, see the Cisco UCS C220 M3 Blade Server Installation and Service Note (http://www.cisco.com/en/US/docs/unified_computing/ucs/hw/chassis/install/B200M3.html).

Connect a UCS Management (CIMC) Port

The UCS has an integrated management functionality known as the Cisco Integrated Management Controller (CIMC). CIMC allows you to do the following:

Configure BIOS settings through HTTP.

Remotely power cycle the device.

Control video, mouse and keyboard (KVM) through Java.

Mount a virtual CD-ROM/block device/FDD to the system.

Connect and perform various other operations.

Do the following to access the CIMC:


Step 1 Attach an Ethernet cable to the Management port of the UCS server. The Management port is labeled "M" (the port with the yellow Ethernet cable connection shown below).


Connect a USB Keyboard and VGA Monitor

Do the following to connect a USB keyboard and VGA monitor to initially bring up the CIMC:


Step 1 Attach the USB keyboard cable to the USB port.

Step 2 Attach the VGA monitor cable to the monitor port.


Configure the UCS Hardware

Perform the procedures in the following sections to configure the UCS hardware.

Configure CIMC

Do the following to configure the CIMC:


Step 1 Power on the server and press F8 when the UCS BIOS menu appears on the monitor.

The CIMC configuration screen is displayed.

Step 2 Configure the device with the options shown below:

a. Enter your IP, subnet mask and gateway addresses.

b. Enter and re-enter a default password.

c. Press the Space Bar to apply the new IP configuration.


Note When configuring CIMC, pay close attention to the 'NIC Mode' and 'NIC Redundancy' settings. If these are set incorrectly, CIMC configures itself to use network ports other than the dedicated CIMC port causing issues.


Step 3 Ping the IP address associated with the CIMC port.


Note If you receive an error, verify that the Ethernet cable is physically connected to the CIMC management port.


Step 4 After verifying the CIMC interface is reachable, verify that the CIMC Web Interface is available by pointing your Web-browser to its IP address:

https://<CIMC IP>
 
   

Step 5 Enter admin as the username and the default password you previously set.

Step 6 If successful, the following screen appears. After verifying HTTP access, press F10 in the BIOS settings to save the configuration.


Configure the BIOS

Do the following to configure the BIOS:


Step 1 Login to the CIMC Web Interface with the username as admin and the default password you previously set. The Summary page appears.

Step 2 To configure the BIOS, click BIOS in the left pane.


Configure the BIOS to Boot from a CD-ROM

Do the following to configure the BIOS to boot from the CD-ROM:


Step 1 Navigate to the BIOS section of the CIMC Web Interface, and click Configure Boot Order.

Step 2 Select CD-ROM and HDD and click Add to add both to the Configure Boot Order pane.

Step 3 Use the Up and Down Arrows to place the CD-ROM as the first device to boot from and click Apply.

Step 4 Verify that the changes you made were successfully applied and appear in the 'Configured Boot Order pane and click Save Changes.


Configure Remote Presence

Do the following to configure Remote Presence:


Step 1 Select Remote Presence from the left pane:

a. Select Virtual KVM and check the Enable check box.

b. Set Max Sessions to 4.

c. Set Remote Port to 2068.

d. Click Save Changes.

Step 2 Select Virtual Media:

a. Check the Enabled check box.

b. Click Save Changes.

Step 3 Select Serial Over LAN:

a. Check the Enabled check box.

b. Select Baud Rate value of 9600 bps.

c. Click Save Changes.


Setting up a UCS C220 for the VDS Service Broker Software

UCS C220 can be configured and managed by using the UCS Manager GUI or CLI.


Note For more information, see the Cisco UCS Manager Configuration Guides at: http://www.cisco.com/en/US/products/ps10281/products_installation_and_configuration_guides_list.html.


To configure and manage the UCS C220 by using the UCS Manager GUI, do the following:


Step 1 Connect the UCS to the Fabric Interconnect and power up all the devices.

Step 2 Connect the UCS C220 to the Fabric Interconnect console port and assign the management IP address.

Step 3 Access the Cisco UCS Manager by using your web browser and entering the IP address of the UCS Manager.

Step 4 Click Launch UCS Manager.

Step 5 Enter your user name and password and click Login.

The built-in user name is admin and the initial password is password.

Step 6 Configure the default adapter policy settings with those shown in the following figure. To access the Ethernet Adapter Policy, choose Servers > Policies > Root > Adapter Policies > Create Ethernet Adapter Policy.

Step 7 A blade server requires a service policy to achieve external communication through the mezzanine card. The following steps walk you through configuring a service pool policy.

a. To use a server pool, associate the service profile with the pool. The UCS manager automatically selects an available compute node from the pool.

b. Set the Filter to All.

c. Configure the server pool policy.

d. Name the server pool.

e. Add server to the pool.

Step 8 Server port allows the communication between servers and the fabric interconnect. Configure the server ports.

Step 9 Uplink ports allows communication between the Fabric Interconnect with the backbone network. Configure the Uplink Port.

Step 10 Configure the interface for the Uplink Port.

Step 11 Configure the Service Profile. Select Create Service Profile (expert) and define a profile name.

Step 12 Enter a name for the Service Profile and click Create UUID Suffix Pool.

Step 13 Enter a name for the UUID Suffix Pool.

Step 14 Click Add UUID Blocks.

Step 15 Create a block of UUID Suffixes (UUIDs are designed as globally unique identifiers for each compute node on a network).

Step 16 Add the newly created block of UUID Suffixes.

Step 17 Add the UUID pool to the Service Profile.

Step 18 Configure the Local Disk Policy. Click Storage.


Note CMP application requires Windows 2008 to be installed on the local disk (bare metal installation).


Step 19 Click Create Local Disk Configuration Policy.

Step 20 Enter a name and for Mode, select RAID 0 Striped.

Step 21 Add the Storage Policy to the Service Profile. In the example in the following figure, the Storage Policy is called "VMS-Storage."


Note Make sure to check no VHBAs because the device is not connected to a SAN.


Step 22 Click Networking and for How would you like to configure LAN connectivity, select Expert.

Step 23 Click Add to create a virtual NIC (vNIC).

Step 24 Click Create MAC Pool.


Note The vNIC uses MAC addresses from the MAC pool.


Step 25 Click Add MAC Addresses to assign a block of MAC addresses to the MAC Pool.

Step 26 Click Add to add the block of addresses.

Step 27 Assign the MAC addresses to the vNIC and click OK.

The Networking page displays the MAC address pool.

Step 28 Click Server Boot Order.

Step 29 Configure the Boot Policy. The boot order is CD-Rom then Local Disk.

Step 30 Add the Boot Policy to the Service Profile.

Step 31 Click Maintenance Policy and select the default.

Step 32 Click Server Assignment to assign the server to the Service Profile. Apply the server policy to the Service Profile.

Step 33 The Service Profile has been successfully created.

Step 34 Associate the Service Profile.

Install the VDS-SB or VDSM 1.1 software

This section describes steps to install/deploy Cisco VDS-SB or VDSM Virtual Appliance and includes the following major topics:

1. VM Hardware Definition

2. System Requirements

3. Deploying the VDS-SB or VDSM Virtual Appliance using vCenter

4. Replacing Virtual Machines across OVA Releases

VM Hardware Definition

A common definition of VM hardware is being used for both VDS-SB and VDSM. The following system parameters are the minimum requirements to deploy VDS-SB or VDSM:

CPU: 4 core

RAM: 8GB

Hard Drive: One 100 GB

Network: Ten

Ten para virtualized interfaces (Ten Gig 1/0 to Ten Gig 10/0).10 virtualized interfaces (TenGigEthernet)

The VDS-SB or VDSM virtual appliance is supported for production use on VMware ESXi 5.1 and can be accessed or managed using vSphere client of VMware. The VDS-SB or VDSM virtual appliance is installed using the Open Virtualization Format (OVF) package.

The VMware vSphere client can be connected directly to your ESXi installation, or it can be connected to a vCenter server which in turn is connected to your vSphere installation. Connecting through vCenter provides a number of capabilities that connecting directly to ESXi does not. If a vCenter server is available and associated with the ESXi installation, it should be used.

System Requirements

The system should have enough hardware resources to support the VM Hardware Definition. The system should contain an additional 8 GB RAM for the hypervisor.

Deploying the VDS-SB or VDSM Virtual Appliance using vCenter


Note Before deploying the virtual appliance, verify that your VMware server is running on VMware supported hardware. If you are not sure whether your environment can support a 64-bit guest operating system, you can verify by downloading and running the VMware "CPU Identification Utility" which indicates 64-bit VMware support. This utility can be found on the VMware site at: http://www.vmware.com/download/shared_utilities.html



Note It is assumed that the user is familiar with VMWare VSphere software


To install the VDS-SB virtual appliance, you must first download the correct installation file namely service_broker_rel_01.ova.


Note VCenter based deployment is recommended. There will be two separate OVA files (one for deployment through VCenter, other for deployment without VCenter) provided to the customer.


Before you install a Cisco VDS-SB or VDSM local virtual appliance you must identify the IP address of the regional cluster to which it will connect to receive the license information.

Using vSphere, connect directly to the ESXi installation or the vCenter server, and select the ESXi installation where the OVA is to be deployed.

If you have a vCenter server available, you can connect the ESXi hypervisor to your existing vCenter server and manage it through that vCenter server. Managing all your VMware hypervisors through a common vCenter server provides many benefits.

To deploy VDS-SB or VDSM Virtual Appliance using vCenter:


Step 1 From vSphere menu, choose File > Deploy OVF Template.

The Deploy OVF Template Source window appears.

Step 2 To import the OVA file from hard disk, click Browse and choose the OVA file (.ova) available in the local machine where the vSphere is running, service_broker_rel_01.ova in the directory in which you unzipped the file earlier. You can also enter a URL to download and install the OVA package from the internet.


Note You cannot browse for URLs and you must enter the full path to the .ova file.


Step 3 Click Next.

The OVF Template Details window appears. It displays the product name, the size of the OVA file, and the amount of disk space that needs to be available for the virtual appliance.

Step 4 Verify the OVF template details and click Next.

The Name and Location window appears.

Step 5 Enter the name of the new virtual appliance. If you are using the vCenter to manage the virtual machine, then you have the option of selecting the location of the inventory too. Click Next to continue.

The default name is generic. You may want to change it to something more specific, such as VDS-SB 2.6 Local or VDS-SB 2.6 Regional.


Note You can change the name of the virtual machine running the virtual appliance after the virtual appliance is deployed. However, while the name of the virtual machine will change, the original name (entered in Step 5) continues to be used as the location of the disk files that describe the virtual machine. Thus, confusion may arise in the future as whatever name you enter on this page remains for the life of the virtual machine and the virtual machine name and the disk file names will differ. Thus, choosing a descriptive name now that you will not need to change later will provide some benefits in maintainability of this installation.


Step 6 Choose the destination host on which you want to deploy the virtual machine and click Next.

The Disk Format window appears.

Step 7 Choose the Thick Provision Eager Zeroed format. Click Next to continue.

The Properties window appears.

Step 8 Enter the following details:

Device-Mode: Choose SB if you want to deploy the VM as a Service broker else choose VDSM.

Host name

Set Primary Interface: Select this checkbox if you want the VDS-SB to use the interface details which you provide in the VDSM IP field.


Note The primary interface cannot be assigned if the interface is configured for DHCP. This interface is used only with Static IP address.



Note The customized values chosen in Step 8 will be used to set VM configuration only at first boot of the VM. These values will not be used to overwrite the configuration during successive reboots


VDSM IP: Enter the IP Address if you have chosen Device-Mode as SB.

Networking Parameters


Note The IP Address and Subnet are configured on the first interface in the application. If these details are not entered, the details provided by the DHCP server are used.


Step 9 Verify the options in the Ready to Complete window, then click Finish to start the deployment.


Deploying the VDS-SB or VDSM Virtual Appliance without vCenter

To deploy VDS-SB or VDSM Virtual Appliance without vCenter:


Step 1 From vSphere menu, choose File > Deploy OVF Template.

The Deploy OVF Template Source window appears.

Step 2 To import the OVA file from hard disk, click Browse and choose the OVA file (.ova) available in the local machine where the vSphere is running, service_broker_rel_01.ova in the directory in which you unzipped the file earlier. You can also enter a URL to download and install the OVA package from the internet.


Note You cannot browse for URLs and you must enter the full path to the .ova file.


Step 3 Click Next.

The OVF Template Details window appears. It displays the product name, the size of the OVA file, and the amount of disk space that needs to be available for the virtual appliance.

Step 4 Verify the OVF template details and click Next.

The Name and Location window appears.

Step 5 Enter the name of the new virtual appliance. If you are using the vCenter to manage the virtual machine, then you have the option of selecting the location of the inventory too. Click Next to continue.

The default name is generic. You may want to change it to something more specific, such as VDS-SB 1.1 Local or VDS-SB 1.1 Regional.


Note You can change the name of the virtual machine running the virtual appliance after the virtual appliance is deployed. However, while the name of the virtual machine will change, the original name (entered in Step 5) continues to be used as the location of the disk files that describe the virtual machine. Thus, confusion may arise in the future as whatever name you enter on this page remains for the life of the virtual machine and the virtual machine name and the disk file names will differ. Thus, choosing a descriptive name now that you will not need to change later will provide some benefits in maintainability of this installation.


Step 6 Choose the destination host on which you want to deploy the virtual machine and click Next.

The Disk Format window appears.

Step 7 Choose the Thick Provision Eager Zeroed format.

Step 8 Finish and deploy the OVA.

This will create the VM.

Step 9 Power on the virtual machine by right-clicking the virtual appliance and choosing Power > Power On.

The virtual appliance console appears.

Step 10 Select the "Open Console" and login to the VM using the user admin with the password default.

Step 11 Change the prompt to configuration mode using the following commands.

SB# configure

SB(config)#

Step 12 Enter the Hostname.

SB(config)# hostname name

Step 13 Run the following commands in the configuration mode.

To enter the Interface mode:

SB(config)# interface tenGigabitEthernet 2/0

To configure Interface IP address:

SB(config)# ip address <ip> <subnet>

If you want to use DHCP addresses, enter the following command

SB(config)# ip address dhcp client-id <id>

To configure Default Gateway:

SB(config)# ip default-gateway <ip>

You must ensure that the default gateway is reachable.

To configure VDSM IP address:

SB(config)# vdsm ip <ip>

To enable cms:

SB(config)# cms enable

The configuration is complete. You can launch the VDS-SB or VDSM through web interface.


Replacing Virtual Machines across OVA Releases

The OVA file contains the hardware definition of the VM. Under certain circumstances, the hardware definition could change from one software release to another. For example, the pre-beta OVA defines two hard disks whereas the beta OVA defines four hard drives.

For new releases, software is released both in OVA and image (ruby.bin) formats. The OVA should be used for new VM deployment and the image format should be used for upgrading existing VMs. However, if the OVA's hardware definition has changed in a particular release and the customer would like to move to the newer definition, he/she should follow the steps in the Cisco VDS Service Broker 1.1 Software Configuration Guide under sub-section "Replacing a Device" in the section "Maintaining the VDS-SB".

This section has the following sub sections:

Replacing a VDSM

Replacing an Service Broker

Replacing a VDSM

To replace a VDSM in a CDS, The new VDSM must be added into the network as a standby VDSM. For procedural information, see the "Configuring Primary and Standby VDSMs" topic in VDS-SB configuration guide.


NoteThe new VDSM must be added as standby. Once the standby VDSM has been added, wait at least two polling intervals (10 minutes) for the databases to synchronize before the upgrade procedure can begin.

After the standby VDSM is activated using the primary VDSM web interface and the device is shown as online in the Devices Table page, wait at least two polling intervals (10 minutes) before changing roles to ensure that the standby VDSM has a record of the most recent configuration changes.


To promote the standby VDSM to primary, first stop the primary VDSM using the vdsm role standby command. For procedural information, see the "Configuring Primary and Standby VDSMs" topic in the VDS-SB configuration guide.

After the primary VDSM has been stopped, and the standby VDSM has taken the role of primary, wait at least two polling intervals (10 minutes) before logging in to the new primary VDSM. The new primary VDSM is accessible by entering the IP address of the VDSM with port 8443 in a web browser. For example, if the IP address of VDSM is 192.168.0.236, enter https://192.168.0.236:8443.

It is now safe to deactivate the old primary VDSM in the VDSM web interface and remove it from the CDS network.


Note Do not try to take a backup of the old VDSM database and restore it on the new VDSM. This may lead to problematic issues.


Replacing an Service Broker

To replace an SB, do the following:


Step 1 Open an SSH session to the device being replaced.

Step 2 In global configuration mode, enter the no cms enable command to disable CMS on the device that needs to be replaced.

SB# configure

SB(config)# no cms enable

Step 3 From the VDSM, choose Devices > Devices > Device Activation. The Device Activation page is displayed.

Step 4 Uncheck the Activate check box and click Submit. The page refreshes and displays a Replaceable check box.

Step 5 Check the Replaceable check box and click Submit.

Step 6 Choose System > Configuration > System Properties. The System Properties page is displayed.

Step 7 Click the edit icon next to the System.devivce.recovery.key property. The Modify Config Property page is displayed.

Step 8 In the Value field, enter a key and click Submit. The default value is default.

Step 9 Follow the instructions to configure a device using the setup utility. The instructions can be found in Cisco Content Delivery Engine Hardware Installation Guide that is applicable to the device.


Note When prompted by the setup utility, configure the basic network settings.


a. Use the same hostname of the device being replaced. For example, if the old device has a hostname of "SB1," the new device must have a hostname of "SB1."

b. Configure the IP address of the VDSM in the SB.

Step 10 Open an SSH session to the new device.

Step 11 In EXEC mode, enter the cms recover identity command with the key parameter set in Step 8.

SB# cms recover identity <key>

On successful registration to the VDSM, a message similar to the following is displayed:

DT-7326-4#cms recover identity sb
Registering this node as Service Broker... 
Sending identity recovery request with key sb 
Node successfully registered with id CrConfig_291 
Registration complete. 
 
   

Step 12 Register the device with the VDSM by using the cms enable command in global configuration mode.

SB# configure

SB(config)# cms enable

Step 13 From the VDSM, choose Devices > Devices > Device Activation. The Device Activation page is displayed.

Step 14 Check the Activate check box and click Submit.

After a few minutes, approximately two polling intervals, the device status shows online and all configurations (delivery service assignments, programs, and so on) are the same as those on the device that was replaced.

Step 15 Once the new device is up and running, as noted by the online status, the old device can be removed from the CDS network.


Upgrade Procedure

The process of upgrading Virtual Machines is similar to the upgrade process used in real machines. The CLI "copy http install" can be used for upgrading. The CLI format is

copy http install http-server-ip-addr dir-name filename

Related Documents

Cisco VDS Service Broker 1.1 Release Notes

Cisco VDS Service Broker 1.1 Software Configuration Guide

Cisco VDS Service Broker 1.1 Command Reference

Cisco VDS Service Broker 1.1 Alarms and Errors

Open Sources Used in VDS Service Broker Release 1.1

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

This document is to be used in conjunction with the documents listed in the "Related Documents" section.

Step 1 To import the OVA file from hard disk, click Browse and choose the OVA file (.ova) available in the local machine where the vSphere is running, service_broker_rel_01.ova in the directory in which you unzipped the file earlier. You can also enter a URL to download and install the OVA package from the internet.


Note You cannot browse for URLs and you must enter the full path to the .ova file.


Step 2 Click Next.

The OVF Template Details window appears. It displays the product name, the size of the OVA file, and the amount of disk space that needs to be available for the virtual appliance.

Step 3 Verify the OVF template details and click Next.

The Name and Location window appears.

Step 4 Enter the name of the new virtual appliance. If you are using the vCenter to manage the virtual machine, then you have the option of selecting the location of the inventory too. Click Next to continue.

The default name is generic. You may want to change it to something more specific, such as VDS-SB 1.1 Local or VDS-SB 1.1 Regional.


Note You can change the name of the virtual machine running the virtual appliance after the virtual appliance is deployed. However, while the name of the virtual machine will change, the original name (entered in Step 5) continues to be used as the location of the disk files that describe the virtual machine. Thus, confusion may arise in the future as whatever name you enter on this page remains for the life of the virtual machine and the virtual machine name and the disk file names will differ. Thus, choosing a descriptive name now that you will not need to change later will provide some benefits in maintainability of this installation.


Step 5 Choose the destination host on which you want to deploy the virtual machine and click Next.

The Disk Format window appears.

Step 6 Choose the Thick Provision Eager Zeroed format. Click Next to continue.

The Properties window appears.