deployment and administration guide for cisco media ... · iii deployment and administration guide...

Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.2June 3, 2011

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

Text Part Number: OL-21554-02

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.2 © 2008-2011 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarks

DeploymenOL-21554-02

C O N T E N T S

C H A P T E R 1 Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2 1-1

About Installing Release 3.2 1-2

Installing Release 3.2 from a DVD 1-2

About the Installation DVDs 1-3

Workflow for Installing the Cisco MXE 3500 Release 3.2 Resource Manager Software 1-3

Workflow for Installing the Cisco MXE 3500 Release 3.2 Resource Node Software 1-4

Installing the Cisco MXE 3500 Installation DVD Software 1-4

Installing the Resource Manager Software 1-5

Installing the Resource Node Software 1-5

Completing Initial Setup: Network Settings and Admin User Account Configuration 1-6

Modifying Network Settings and Admin Password 1-8

Enabling or Disabling the Shared Folder Password 1-9

Restarting and Shutting Down the Cisco MXE Application 1-10

Logging in to the Linux System Command Prompt 1-11

Restoring the Default System Profiles 1-12

C H A P T E R 2 Upgrading Cisco MXE 3500 Release 3.1 to Release 3.2 2-1

Upgrading from Release 3.1 to Release 3.2 2-1

Upgrade Workflow 2-1

Obtain the Release 3.2 Upgrade License 2-2

Download the Release 3.2 Software 2-2

Upgrade the Windows VM from Release 3.1 to Release 3.2 2-3

Upgrade the Linux VM from Release 3.1 to Release 3.2 2-5

Upgrade Hypervisor (ESXi) 2-6

Install the Upgrade License 2-7

Restoring the Linux VM from Release 3.2 to Release 3.1 2-7

Restoring the Widows VM from Release 3.2 to Release 3.1 2-8

C H A P T E R 3 Backing Up and Restoring Data for Cisco MXE 3500 Release 3.0 Upgrade to Release 3.2 3-1

Preparing for Upgrade 3-1

Documenting System Settings Before Performing Backup 3-2

Backing Up User Data to a Network Drive 3-2

Backing Up Shared Directories and Media Files 3-3

iiit and Administration Guide for Cisco Media Experience Engine 3500 Release 3.2

Contents

Backing Up the SQL Database 3-3

Backing Up the Folder Attendant (FA) Configuration 3-5

Migrating a License and Upgrading from Release 3.0 to Release 3.2 3-5

Obtaining the License Migration Tool 3-5

Generating the Migration XML 3-6

Installing the Cisco MXE 3500 Release 3.2 Software 3-8

Obtaining the License Host ID 3-8

Obtaining the License for the Migration 3-8

Obtaining the Release 3.1 to Release 3.2 Upgrade License 3-10

Installing the Licenses 3-10

Importing and Restoring Backed Up Data 3-10

Restoring the User Profile 3-11

Restoring Shared Directories and Media Files 3-11

Restoring the Database 3-12

Restoring the Folder Attendant (FA) Configuration 3-13

Changing the IP Address 3-13

C H A P T E R 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration 4-1

About Cisco MXE 3500 Release 3.2 4-1

About the Cisco MXE 3500 Standalone Deployment 4-2

Guidelines for a Standalone Deployment 4-2

How to Configure Cisco MXE 3500 Release 3.2 for a Standalone Deployment 4-3

Accessing the Cisco MXE 3500 Web User Interface (Standalone or Resource Manager) 4-3

Accessing the Cisco MXE 3500 Tools (Standalone and Resource Manager) 4-4

Installing a License on Cisco MXE 3500 (Standalone or Resource Manager) 4-4

Obtaining the License Host ID 4-4

Obtaining a New, Upgrade, or Feature License 4-5

Installing a License File 4-7

Configuring the Input and Output Media Directories (Standalone or Resource Manager) 4-7

Enabling System Administration E-mail Notifications (Standalone or Resource Manager) 4-8

Configuring the Host Settings (Standalone Only) 4-9

Confirming Service Accounts and Identifying Device Type (Standalone or Resource Manager) 4-10

Creating a Folder Attendant Directory and Watch (Standalone or Resource Manager) 4-11

Creating a Directory 4-12

Creating a Watch 4-12

Using Administrative Tools to Configure a Standalone Cisco MXE 3500 4-12

Host Settings (Standalone Only) 4-13

System Settings 4-16

ivDeployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.2

OL-21554-02

Contents

Input Section (Standalone Only) 4-16

Output Section (Standalone Only) 4-18

General Settings Section (Standalone or Resource Manager) 4-18

Status Settings Section (Standalone or Resource Manager) 4-18

Data Purging Section (Standalone or Resource Manager) 4-19

Audio Capture Section (Standalone or Resource Manager) 4-20

Administrative User Accounts (Standalone or Resource Manager) 4-21

Windows VM 4-21

Linux VM 4-22

User Metadata Settings 4-22

IP Capture (Live Streaming) Settings (Standalone or Resource Manager) 4-22

Configuring User Accounts 4-24

Testing a Cisco MXE 3500 Deployment (Standalone or Resource Manager) 4-24

Test 1: Submit a Job Using File Job Submission 4-24

Test 2: Submit a Job Using Folder Attendant 4-25

Test 3: Verify a Licensed Feature is Enabled 4-25

Providing Documentation Feedback 4-27

C H A P T E R 5 Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration 5-1

About the Cisco MXE 3500 Release 3.2 5-1

About the Resource Manager Deployment 5-2

Guidelines for a Resource Manager Deployment 5-2

How to Configure Cisco MXE 3500 Release 3.2 for a Resource Manager Deployment 5-3

Accessing the Cisco MXE 3500 Web User Interface 5-3

Accessing the Cisco MXE 3500 Tools 5-4

Installing the License 5-4

Configuring the Input and Output Media Directories 5-4

Enabling System Administration E-mail Notifications 5-4

Configuring the Host Settings (Resource Manager Only) 5-4

Confirming Service Accounts and Identifying Device Type 5-6

Creating a Folder Attendant Directory and Watch 5-6

Using Administrative Tools to Configure a Cisco MXE 3500 as a Resource Manager 5-6

Host Settings (Resource Manager Only) 5-7

Understanding Capacity, Expense, and Limit (Resource Manager Only) 5-9

System Settings 5-10

Input Section (Resource Manager Only) 5-11

Output Section (Resource Manager Only) 5-12

General Settings Section 5-13

vDeployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.2

OL-21554-02

Contents

Status Settings Section 5-13

Data Purging Section 5-13

Audio Capture Section 5-13

User Settings (Resource Manager Only) 5-13

Role Settings 5-14

Profile Space Settings 5-15

User Metadata Settings 5-16

IP Capture (Live Streaming) Settings 5-16

Testing a Cisco MXE 3500 Deployment 5-16

C H A P T E R 6 Deploying Licensed Features for Cisco MXE 3500 6-1

Live Streaming (IP Capture) Feature 6-1

Required Components for the Live Streaming Feature 6-1

Ingest (Input) 6-2

Job Profile (Transcode) 6-2

Distribution (Output) 6-2

Live WMV IP Streaming Deployments 6-3

Network Design for Cisco MXE 3500 Deployments with Live WMV IP Streaming 6-3

Configuration Workflow for Cisco MXE 3500 Deployments with Live WMV IP Streaming 6-3

Live Flash 8 and H.264 IP Streaming Deployments 6-4

Network Design for Cisco MXE 3500 Deployments with Live Flash 8 and H.264 IP Streaming 6-4

Configuration Workflow for Cisco MXE 3500 Deployments with Live Flash 8 and H.264 IP Streaming 6-5

Live WMV Stream from Cisco TelePresence Content Server to Cisco MXE 3500 Deployments 6-6

Prerequisites 6-6

Content Server Configuration for a WMV Unicast Stream 6-7

Content Server Configuration for a WMV Multicast Stream 6-14

Live WMV Stream to Cisco Digital Signs Deployments 6-23

Configuring an IP Capture Source on Cisco MXE 3500 6-24

Creating a Job Profile on Cisco MXE 3500 6-24

Starting the Multicast Stream on the Content Server 6-25

Submitting the Live Job on Cisco MXE 3500 6-26

Verifying the Live Job 6-27

Speech-to-Text and Graphics Overlay Features 6-27

Overview of the Speech-to-Text and Graphic Overlay Features 6-28

Required Components for the Speech-to-Text and Graphic Overlay Features 6-28

Configuration Workflow for Speech-to-Text Conversion 6-29

Configuration Workflow for the Graphic Overlay Feature 6-30

Guidelines for Improving the Accuracy of Speech to Text 6-31

viDeployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.2

OL-21554-02

Contents

Speech Input Style 6-31

Multiple Speakers in a Video 6-31

Speech Profiles 6-31

Methods for Acquiring Audio 6-31

Importing a Speech Profile to Cisco MXE 3500 6-32

Simplified User Interface Feature 6-32

Configuring Video Output Formats for the SUI 6-33

Renaming the Job Profiles that Display in the Conversion Interface 6-33

Configuring a Watermark, Bumper, Trailer, and Graphic Overlay for the SUI 6-34

Configuring Watermarking (Preprocessor) for the SUI 6-34

Configuring Show and Share Integration 6-35

Configuring a Wowza or Windows Media Streaming Server 6-36

Configuring E-Mail Notifications 6-37

Configuring SUI User Accounts 6-38

Restoring the Default SUI Profiles 6-38

C H A P T E R 7 Security Best Practices for Cisco MXE 3500 7-1

Security Best Practices for Cisco MXE 3500 7-1

Cisco MXE 3500 Microsoft Hot Fix Release Policy 7-2

Windows Services 7-2

C H A P T E R 8 Troubleshooting Cisco MXE 3500 8-1

Logging 8-1

Troubleshooting 8-1

Troubleshooting Steps 8-2

Troubleshooting FAQs 8-2

Standalone and Resource Manager Deployments 8-2

Resource Manager Deployments 8-3

Contacting Cisco TAC 8-4

Reinstalling the Software 8-4

viiDeployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.2

OL-21554-02

Contents

viiiDeployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.2

OL-21554-02

Deployment and Administration Guide fOL-21554-02

C H A P T E R 1
Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2
Revised: July 11, 2011

This chapter provides procedures for the following tasks:

• Using the DVDs to install Release 3.2 on existing Cisco MXE 3500 V1 hardware running Release 3.0 or Release 3.1

• Using the DVDs to install Release 3.2 on existing Cisco MXE 3500 V2 hardware running Release 3.1

• Configuring Release 3.2 network settings and the password for the admin password on new Cisco MXE 3500 V2 hardware running Release 3.2

• Modifying Release 3.2 network settings and the password for the admin user account

Note For information about upgrading from Release 3.1 to Release 3.2, see Chapter 2, “Upgrading Cisco MXE 3500 Release 3.1 to Release 3.2,” For information about upgrading from Release 3.0 to Release 3.2, see the Chapter 3, “Backing Up and Restoring Data for Cisco MXE 3500 Release 3.0 Upgrade to Release 3.2,”

This chapter includes the following sections:

• About Installing Release 3.2, page 1-2

• Installing Release 3.2 from a DVD, page 1-2

• Completing Initial Setup: Network Settings and Admin User Account Configuration, page 1-6

• Modifying Network Settings and Admin Password, page 1-8

• Enabling or Disabling the Shared Folder Password, page 1-9

• Restarting and Shutting Down the Cisco MXE Application, page 1-10

• Logging in to the Linux System Command Prompt, page 1-11

• Restoring the Default System Profiles, page 1-12

1-1or Cisco Media Experience Engine 3500 Release 3.2

Chapter 1 Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2 About Installing Release 3.2

About Installing Release 3.2When you use the Release 3.2 DVD to install the software, you reimage the Cisco MXE 3500 and restore the device back to factory defaults.

• To upgrade from Release 3.0 to Release 3.2 and to preserve configuration, you must manually back up the data, install Release 3.2 from the DVDs, and then manually restore the data. For information about manually backing up Cisco MXE 3500 V1 hardware running Release 3.0, see Chapter 3, “Backing Up and Restoring Data for Cisco MXE 3500 Release 3.0 Upgrade to Release 3.2.” Then, return to this chapter to install Release 3.2 and configure network settings and the password for the admin user.

• To upgrade from Release 3.1 to Release 3.2 and to preserve configuration, see Chapter 2, “Upgrading Cisco MXE 3500 Release 3.1 to Release 3.2.”

Once you upgrade to Release 3.2, you can use the Backup and Restore feature that is available in the web UI to backup critical system data from the Linux and Windows VMs into a single backup archive file. You can then use this backup archive file to restore Release 3.2 data to a Release 3.2 installation. For more information about this feature, see the User Guide for Cisco MXE 3500 for your release on Cisco.com.

Installing Release 3.2 from a DVDThis section includes the following topics:

• About the Installation DVDs, page 1-3

• Workflow for Installing the Cisco MXE 3500 Release 3.2 Resource Manager Software, page 1-3

• Workflow for Installing the Cisco MXE 3500 Release 3.2 Resource Node Software, page 1-4

• Installing the Cisco MXE 3500 Installation DVD Software, page 1-4

• Installing the Resource Manager Software, page 1-5

• Installing the Resource Node Software, page 1-5

1-2Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.2

OL-21554-02

http://www.cisco.com/en/US/products/ps9892/products_user_guide_list.html

Chapter 1 Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2 Installing Release 3.2 from a DVD

About the Installation DVDsThe following installation Release 3.2 DVDs ship with the Cisco MXE 3500:

Workflow for Installing the Cisco MXE 3500 Release 3.2 Resource Manager Software

Warning If you are configuring Cisco MXE 3500 Release 3.2 as a standalone or Resource Manager device on new Cisco MXE 3500 V2 hardware, proceed to “Completing Initial Setup: Network Settings and Admin User Account Configuration” section on page 1-6. Starting this procedure from “Installing the Cisco MXE 3500 Installation DVD Software” section on page 1-4 reimages the device and removes factory installation.

These DVDs are required to upgrade Cisco MXE 3500 V1 hardware to run Cisco MXE 3500 Release 3.2 Resource Manager software. Install them in the following order:

Installation DVD Description

Cisco MXE 3500, Installation DVD • Installs the common ESXi Hypervisor platform

• Orchestrates the complete Cisco MXE 3500 software installation

• Cisco Resource Manager, DVD 1-2

• Cisco Resource Manager, DVD 2-2

Note For purposes of this upgrade, a standalone, Cisco MXE 3500 that is not part of a cluster is considered a Resource Manager.

• Cisco Resource Node, DVD 1-2

• Cisco Resource Node, DVD 2-2

Contain the Windows and Linux Virtual machines for Resource Manager installations and scripts for setting up networking between VMs and other features the Hypervisor needs for the Cisco MXE 3500

— Installation DVD Resource

Step 1 Cisco MXE 3500 Installation DVD Installing the Cisco MXE 3500 Installation DVD Software, page 1-4

Step 2 Cisco Resource Manager DVD 1-2

Note Use for a standalone or Resource Manager device.

Installing the Resource Manager Software, page 1-5

Step 3 Cisco Resource Manager DVD 2-2

Note Use for a standalone or Resource Manager device.


OL-21554-02


Workflow for Installing the Cisco MXE 3500 Release 3.2 Resource Node Software

Note A Cisco MXE 3500 that is part of a cluster and that a Resource Manager controls via ECS is considered a Resource Node.

Warning If you are configuring Cisco MXE 3500 Release 3.2 as a Resource Node on new Cisco MXE 3500 V2 hardware, proceed to “Completing Initial Setup: Network Settings and Admin User Account Configuration” section on page 1-6. Starting this procedure from “Installing the Cisco MXE 3500 Installation DVD Software” section on page 1-4 reimages the device and removes factory installation.

These DVDs are required to upgrade Cisco MXE 3500 V1 hardware to run Cisco MXE 3500 Release 3.2 Resource Node software. Install them in the following order:

Installing the Cisco MXE 3500 Installation DVD Software

Warning Starting this procedure from Cisco MXE 3500 Installation DVD erases all data on the hard drive.

Procedure

Step 1 Power on the Cisco MXE 3500 standalone or Resource Manager device by the Power On/Off LED/Button on the front panel.

Step 2 Quickly insert Cisco MXE 3500 Installation DVD. The following message displays: Cisco Media eXperience Appliance Install Disk.

Step 3 At the boot prompt, press the Enter key to begin. The installation procedure starts, booting from Cisco MXE 3500 Installation DVD. The following messages display: Starting Installation Stage 2 and then Successfully Mounted. Installation takes approximately 12 minutes to complete.

Step 4 Upon completion, the Cisco MXE 3500 Installation DVD ejects and the following message displays; Please insert Application Software Disk MXEAPPSW-1.

Step 5 Proceed to the “Installing the Resource Manager Software” section on page 1-5.

or

— Installation DVD Resource

Step 1 Cisco MXE 3500, Installation DVD Installing the Cisco MXE 3500 Installation DVD Software, page 1-4

Step 2 Cisco Resource Node DVD 1-2 Installing the Resource Node Software, page 1-5Step 3 Cisco Resource Node DVD 2-2


OL-21554-02


Step 6 Proceed to the “Installing the Resource Node Software” section on page 1-5

Installing the Resource Manager Software

Note Install the Resource Manager DVD 1-2 and 2-2 software only on either a standalone or Resource Manager device. Resource Nodes require different software. See the “Installing the Resource Node Software” section on page 1-5.

Procedure

Step 1 Install the Resource Manager DVD 1-2.

a. Insert the Cisco Resource Manager DVD 1-2. No other action is required; the installation continues. This installation takes approximately 10 minutes to complete.

b. After Cisco Resource Manager DVD 1-2, the system prompts you to insert Cisco Resource Manager DVD 2-2.

Step 2 Install the Resource Manager DVD 2-2.

a. Insert Cisco Resource Manager DVD 2-2. The installation continues on its own.

b. When the installation completes, remove Cisco Resource Manager DVD 2-2. The system powers down.

Step 3 Proceed to the “Completing Initial Setup: Network Settings and Admin User Account Configuration” section on page 1-6.

Installing the Resource Node Software

Note Use this procedure to install only Resource Node software on a Cisco MXE 3500. A standalone or Resource Manager device requires different software. See the “Installing the Resource Manager Software” section on page 1-5.

Procedure

Step 1 Install the Resource Node DVD 1-2.

a. Insert Cisco Resource Node, DVD 1-2. No other action is required: the install will continue. This installation takes approximately 10 minutes to complete.

b. After Cisco Resource Node, DVD 1-2, the system prompts you to insert Cisco Resource Node, DVD 2-2.

Step 2 Install the Resource Node DVD 2.

c. Insert Cisco Resource Node, DVD 2-2. The install procedure continues on its own.


OL-21554-02

Chapter 1 Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2 Completing Initial Setup: Network Settings and Admin User Account Configuration

d. When the installation completes, remove Cisco Resource Node, DVD 2-2 from the machine. The system powers down on its own.

Step 3 Proceed to the “Completing Initial Setup: Network Settings and Admin User Account Configuration” section on page 1-6.

Completing Initial Setup: Network Settings and Admin User Account Configuration

You will complete initial setup from the console. Upon subsequent login, you can use SSH.

When you log in for the first time, the configuration wizard launches automatically and enables you to configure network settings and the admin password.

Note To change these settings after completing initial setup. see the “Modifying Network Settings and Admin Password” section on page 1-8.

Procedure

Step 1 Power on the Cisco MXE 3500 standalone or Resource Manager device by using the front panel Power On/Off LED/Button.

Step 2 Press Alt+F1 and then press Enter.

Step 3 Log in with the following default credentials:

• Username: admin

• Password: change_it

The configuration wizard launches, and the Configure Network Settings screen displays.

Figure 1-1 Configure Network Settings Screen

Step 4 Enter network settings for your deployment. Then, click Next.


OL-21554-02

Chapter 1 Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2 Completing Initial Setup: Network Settings and Admin User Account Configuration

Note Fields marked with an asterisk (*) are required. The system highlights any information errors.

Step 5 Click OK at the Please Wait screen, and click OK at the Success screen. The Configure Hostname and Domain Name screen displays.

Figure 1-2 Configure Hostname and Domain Name

Step 6 (Optional) Enter a hostname and domain name.

Step 7 Press Next. The Configure DNS Server screen displays.

Step 8 (Optional) Enter a DNS Server.

Step 9 Click Next. The Configure NTP Server screen displays.

Step 10 (Optional) Enter an NTP server.

Step 11 Click Next. The Modify and Synchronize Admin Password screen displays.

Figure 1-3 Modify and Synchronize Admin Password Screen

Step 12 Enter and re-enter a new password for the admin user account. Click Next.

Step 13 Click OK at the Please Wait screen, and click OK at the Password Changed screen. The Enable/Disable Shared Folder Password screen displays.


OL-21554-02

Chapter 1 Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2 Modifying Network Settings and Admin Password

Figure 1-4 Enable/Disable Shared Folder Password Screen

Step 14 Press the spacebar to require the shared folder password and then click Next. The Configuration Complete screen displays.

Note If you enable the shared folder password, you must configure the password after you complete initial setup. See the “Enabling or Disabling the Shared Folder Password” section on page 1-9 for information.

Step 15 Click OK to at the Configuration Complete screen. When you log in to the Cisco MXE application as admin, you will use the new password that you set in Step 12.

Note The Cisco MXE application admin account is used to modify system settings, access the system command prompt, and restart the Cisco MXE application.

Modifying Network Settings and Admin PasswordUse this procedure to change the network settings or the admin account password after you complete initial setup.

You can access the Configuration Menu remotely by using SSH or directly by using ESXi through a console connection.

Procedure

Step 1 SSH to mxe_IP_address and then enter the admin password. The Configuration Menu displays.

Tip If you have a physical access to the Cisco MXE 3500, press Alt+F1 and then press Enter when the Welcome to the Media Experience Engine screen displays to log in as admin and access the Configuration Menu.


OL-21554-02

Chapter 1 Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2 Enabling or Disabling the Shared Folder Password

Figure 1-5 Cisco MXE Appliance Configuration Menu

Step 2 Either choose one of the network setting configuration options or choose Change Admin Password.

Step 3 Click OK.

Step 4 When complete, click Exit System and then click OK.

Enabling or Disabling the Shared Folder Password

Note For Cisco MXE 3500 Release 3.2.1 Maintenance Release and later, see the Shared Folder Access Settings section in the User Guide for Cisco MXE 3500 Release 3.2.

For Cisco MXE 3500 Release 3.2 and earlier releases, use this procedure to enable or disable the shared folder password after you complete initial setup.

Procedure

Step 1 SSH to mxe_IP_address and then enter the admin password. The Configuration Menu displays.

Tip If you have a physical access to the Cisco MXE 3500, press Alt+F1 and then press Enter when the Welcome to the Media Experience Engine screen displays to log in as admin and access the Configuration Menu.


OL-21554-02

http://www.cisco.com/en/US/docs/video/mxe/3500/sw/3_x/3_2/user/guide/ug_mxe3500_32.html

Chapter 1 Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2 Restarting and Shutting Down the Cisco MXE Application

Figure 1-6 Cisco MXE Appliance Configuration Menu

Step 2 Choose Enable/disable Share User Password and then click OK.

Step 3 Enter and re-enter the password and then click OK.

Step 4 Click OK to confirm enabled security.

Step 5 Click OK at the Password Changed screen.

Step 6 When complete, choose Exit System and then click OK.

Restarting and Shutting Down the Cisco MXE ApplicationThis section details the following procedures:

• Restart and Shutdown the MXE Appliance from the Configuration Menu, page 1-10

• Restart the MXE Application After a Shutdown, page 1-11

Note We recommend that you shut down the Cisco MXE application before you power down the Cisco MXE 3500 hardware.

Restart and Shutdown the MXE Appliance from the Configuration Menu

Use this procedure to restart or shut down the Cisco MXE application. Doing so, either shuts down or restarts the Linux and Windows VM.

Step 1 SSH to mxe_IP_address.

Step 2 When the Welcome to the Media Experience Engine screen displays, press Alt+F1 to log in to the Linux administration utility. The Configuration Menu displays.


OL-21554-02

Chapter 1 Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2 Logging in to the Linux System Command Prompt

Step 3 Choose one of the following options from the menu:

• Restart Cisco MXE Application—Restarts the Linux and Windows VMs.

• Shutdown Cisco MXE Application—Shuts down the Linux and Windows VMs.

Note To shut down the Cisco MXE 3500 appliance, console into ESXi, then press F2 on your keyboard. To power on the Cisco MXE 3500 appliance, press the power button on the appliance.

Step 4 Click OK.

Restart the MXE Application After a Shutdown

This porcedure details how to restart the MXE Application after shutdown from the Configuration Menu (blue screen).

Step 1 Assign an IP address to ESXi (if an IP address is not already assigned).

Step 2 Enter the ESXi IP address in a web browser.

Step 3 Download and install the vSphere client.

Step 4 Log into the vSphere client using the ESXi username and password.

In the vSphere Client, on the left hand panel, you will see the Linux and Windows VMs.

Step 5 Right click on each VM and click Start.

The Linux and Windows VMs will boot up. You can monitor the boot up on the vSphere client console.

Step 6 After the Linux and Windows VMs are up, SSH to mxe_IP_address and follow the steps detailed in “Restart and Shutdown the MXE Appliance from the Configuration Menu”.

Logging in to the Linux System Command PromptUse this procedure to log in to the Linux system command prompt and enter commands in the shell.

Procedure


Step 2 When the Welcome to the Media Experience Engine screen displays, press Alt+F1 to log in to the Linux administration utility. The Configuration Menu displays.

Step 3 Click System Command Prompt.

Step 4 Click OK. The Linux shell displays.


OL-21554-02

Chapter 1 Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2 Restoring the Default System Profiles

Restoring the Default System ProfilesThe Cisco MXE 3500 ships with a set of default profiles. Use this procedure to restore the default profiles:

Procedure

Step 1 Go to the Cisco.com software download center at the following URL: http://www.cisco.com/cisco/web/download/index.html

Step 2 Choose Video, Cable and Content Delivery > Media Transformation > Cisco MXE 3000 Series (Media Experience Engines) > Cisco MXE 3500 (Media Experience Engine) > Media Experience Engine Utilities and download the system profiles file to a location where the Cisco MXE 3500 can access the file.

Step 3 RDC to the Cisco MXE 3500 and save the system profiles file to c:\temp.

Step 4 Right-click the .zip file and choose Extract.

Step 5 Follow the on-screen prompts to uncompress the system profiles file to the following Cisco MXE 3500 folder: c:\program files\cisco\media experience engine\profiles.


OL-21554-02


C H A P T E R 2
Upgrading Cisco MXE 3500 Release 3.1 to Release 3.2
Revised: June 3, 2011


• Upgrading from Release 3.1 to Release 3.2, page 2-1

• Restoring the Linux VM from Release 3.2 to Release 3.1, page 2-7

Upgrading from Release 3.1 to Release 3.2 • Upgrade Workflow, page 2-1

• Obtain the Release 3.2 Upgrade License, page 2-2

• Download the Release 3.2 Software, page 2-2

• Upgrade the Windows VM from Release 3.1 to Release 3.2, page 2-3

• Upgrade the Linux VM from Release 3.1 to Release 3.2, page 2-5

• Upgrade Hypervisor (ESXi), page 2-6

• Install the Upgrade License, page 2-7

Upgrade WorkflowTo upgrade a Cisco MXE 3500 Release 3.1 Resource Manager or Resource Node to Release 3.2, you must compete the following steps in the order shown:

1. Obtain the Release 3.2 Upgrade License, page 2-2

2. Download the Release 3.2 Software, page 2-2

3. Upgrade the Windows VM from Release 3.1 to Release 3.2, page 2-3

4. Upgrade the Linux VM from Release 3.1 to Release 3.2, page 2-5

5. Upgrade Hypervisor (ESXi), page 2-6

6. Install the Upgrade License, page 2-7


Chapter 2 Upgrading Cisco MXE 3500 Release 3.1 to Release 3.2 Upgrading from Release 3.1 to Release 3.2

Obtain the Release 3.2 Upgrade LicenseUse this procedure to use eDelivery to order upgrade licenses for each Cisco MXE 3500 in your deployment.

Before You Begin

To log into eDelivery, you need your Cisco username and password.

Procedure

Step 1 Order eDelivery upgrade licenses for each Cisco MXE 3500.

• L-MXE-PAK= and choose the following options:

• L-MXE-3500-LICU (Base software upgrade)

• L-MXE-3500-UILIC (Conversion User Interface)

• L-MXE-3500-LVLICU (Must already have live streaming enabled)

Step 2 Go to https://edelivery.cisco.com/esd/ and then follow the eDelivery process to obtain the Product Authorization Key (PAK).

Step 3 Go to http://www.cisco.com/go/license and then use the PAK and Host ID of Cisco MXE 3500 to obtain the license file.

Step 4 Save the file to a location that the Cisco MXE 3500 can access during license installation.

Download the Release 3.2 SoftwareThe Cisco MXE 3500 Release 3.2 software upgrade is bundled in the following two packages:

• upgrade-rm.zip—contains winos-rm.zip, ncos-rm.zip, and hypervisor.tar.gz

• upgrade-rn.zip—contains winos-rn.zip, ncos-rn.zip, and hypervisor.tar.gz

Note The checksum in located in the description area for each .zip file.

For standalone deployments, download upgrade-rm.zip.

For Resource Manager deployments, download upgrade-rm.zip and upgrade-rn.zip.

Before You Begin

You must have an account on Cisco.com to access the software download website.

Procedure

Step 1 Go to http://www.cisco.com/public/sw-center/index.shtml and log in to Cisco.com.

Step 2 In the Select a Software Product Category area, choose Video, Cable and Content Delivery.

Step 3 Choose Media Transformation > Cisco MXE 3000 Series (Media Experience Engines) > Media Experience Engine Upgrade.


OL-21554-02

http://www.cisco.com/public/sw-center/index.shtml

https://edelivery.cisco.com/esd/

http://www.cisco.com/go/license


Step 4 Click Latest Releases > 3.2. The links to the software are on the right side of the browser window.

Step 5 Save the upgrade files to a temporary media, such as a flash drive, or to a network server that you can access from the Cisco MXE 3500 when you install.

Upgrade the Windows VM from Release 3.1 to Release 3.2

Before You Begin

• For standalone or Resource Manager deployments, unzip winos-rm.zip to obtain winos-rm.zip.

• For Resource Manager deployments, also unzip winos-rn.zip to obtain winos-rn.zip for the Resource Node.

• We recommend that you back up the following files manually:

– Profiles—c:\program files\cisco\media experience engine\profiles (entire directory) and any custom profile spaces

– Media files—c:\media (if you are preserving any media files)

– Folder Attendant Configuration—c:\program files\cisco\media experience engine\Folder Attendant\bin\faConfig.xml

– Licenses—c:\program files\cisco\media experience engine\license (entire directory)

– Database configuration—Use the DbAdmin.exe to export data.

Upgrading the Windows VM on a Resource Manager


To upgrade the Windows VM, complete the following steps on each Resource Manager:

Step 1 RDC to mxe_IP_address.

Step 2 Copy winos-rm.zip to the Windows VM desktop.

Step 3 Unzip winos-rm.zip to temporary directory.

Step 4 Verify that the following files are present:

• updateDNS.bat

• updateDNS.vbs

• updateNTP.bat

• updateNTP.vbs

• Mxe.msi

• BruSetup.msi

• MxeRMUpgrade.bat

Step 5 Execute MxeRMUpgrade.bat to perform the upgrade. The installer upgrades the software, including upgrading the database and preserving existing Folder Attendant configuration.

Step 6 Double-click the Services shortcut on the desktop.


OL-21554-02


Step 7 Manually start the Mxe BRU service.

Step 8 For the Administrator and mxe-service user accounts, disable RDC:

a. Click Control Panel > Administrative Tools > Computer Management > Local Users and Groups > Users.

b. Double-click the user account to view the Properties dialog.

c. In the Terminal Services Profile tab, check Deny this user permissions to log on to any Terminal Server.

Note Do not delete or change the password for the mxe-service account; otherwise, the Cisco MXE 3500 will not work.

Step 9 Log in as admin to the web UI.

Step 10 Verify that the web UI is running with existing user, system, host, IP capture, and watch folder configuration.

Step 11 Verify that jobs can successfully be submitted by using the web UI.

Step 12 (Optional) Restore backed up profiles by copying the profiles to c:\program files\cisco\media experience engine\profiles.

Note Do not overwrite any new Release 3.2 profiles.

Upgrading the Windows VM on a Resource Node

To upgrade the Windows VM, complete the following steps on each Resource Node:

Step 1 Copy winos-rn.zip to the Windows VM desktop.

Step 2 Unzip winos-rn.zip to temporary directory.

Step 3 Verify that the following files are present:

• updateDNS.bat

• updateDNS.vbs

• updateNTP.bat

• updateNTP.vbs

• Mxe.msi

• MxeRNUpgrade.bat

• Audiomining_profile.zip

Step 4 Execute MxeRNUpgrade.bat to perform the upgrade.

Step 5 Extract the Audiomining_profile directory from Audiomining_profile.zip to C:\Documents and Settings\All Users\Application Data\Nuance\Dragon SDK Server Edition10\Users.


OL-21554-02


Step 6 For the Administrator and mxe-service user accounts, disable RDC:

a. Click Control Panel > Administrative Tools > Computer Management > Local Users and Groups > Users.

b. Double-click the user account to view the Properties dialog.

c. In the Terminal Services Profile tab, check Deny this user permissions to log on to any Terminal Server.

Note Do not delete or change the password for the mxe-service account; otherwise, the Cisco MXE 3500 will not work.

Step 7 Verify that jobs can successfully be submitted by using the web UI for the Resource Manager.

Upgrade the Linux VM from Release 3.1 to Release 3.2

Backing Up the Linux VM on a Resource Manager and Resource Node

To back up Release 3.1 Linux VM configuration files before you upgrade a Linux VM to Release 3.2, complete the following steps for each Resource Manager and Resource Node:


Step 2 Enter su - and then run backUp.sh.

A file named backup.tar is created and placed in /mnt/temp or at \\mxe_ip\temp directory.

Step 3 Save the backup.tar file to a remote location that the Cisco MXE 3500 can access.

Upgrading the Linux VM on a Resource Manager and Resource Node


Before You Begin

• For standalone or Resource Manager deployments, unzip ncos-rm.zip to obtain the following installers:

– a2a-installer-3.2.x-y.sh

– linux-rm-installer-3.2.x-y.sh

where x-y are the versions and release numbers of the installers

– upgrade-linux-vm.sh

– back-restore folder that contains backup.sh , restore.sh and backup_filelist.txt

• For Resource Manager deployments, also unzip ncos-rn.zip to obtain the following installers for Resource Nodes:

– linux-rn-installer-3.2.x-y.sh


OL-21554-02


where x-y are the versions and release numbers of the installers

– upgrade-linux-vm.sh

– back-restore folder that contains backup.sh , restore.sh and backup_filelist_RN.txt

To upgrade the Linux VM, complete the following steps for each Resource Manager and Resource Node:


Step 2 Create a directory named installers in the current working directory on the target Linux VM.

Step 3 Use the scp command to copy the following files to the installers directory on the target Linux VM:

For example, enter scp user@host:linux-rm-installer-<x version>-<y release>.sh /home/admin/installers/

Resource Manager

• a2a-installer-3.2.x-y.sh

• linux-rm-installer-3.2.x-y.sh where x-y are the versions and release numbers of the installer

Resource Node

• linux-rn-installer-3.2.x-y.sh

Step 4 Copy upgrade-linux-vm.sh to the current working directory on the target Linux VM.

Step 5 Copy the following files to the /opt/cisco/mxe/scripts/ directory on the target Linux VM:

Resource Manager

• backup.sh

• restore.sh

• backup_filelist.txt

Resource Node

• backup.sh

• restore.sh

• backup_filelist_RN.txt

Note These files contain only Release 3.1 configuration information.

Step 6 Enter su - and then execute ./upgrade-linux-vm.sh to perform the upgrade.

Upgrade Hypervisor (ESXi)

Before You Begin

• Obtain the hypervisor.tar.gz.

• Ensure that the Hypervisor (ESXi) is assigned an IP address. This is done via the ESXi console.

• Upgrade the Windows and Linux VMs to Release 3.2.

• Shut down the Windows and Linux VMs.


OL-21554-02

Chapter 2 Upgrading Cisco MXE 3500 Release 3.1 to Release 3.2 Restoring the Linux VM from Release 3.2 to Release 3.1

Upgrading the Hypervisor (ESXi) on a Resource Manager or Resource Node

To upgrade, complete the following steps for each Resource Manager and Resource Node:

Step 1 Enter the following command to copy hypervisor.tar.gz to the target Cisco MXE 3500:

scp hypervisor.tar.gz root@<ESXi_IP>:/tmp where <ESXi_IP> is the IP address that you assigned to ESXi.

Step 2 SSH as root to ESXi_IP, such as ssh root@<ESXi_ IP>.

Step 3 When prompted, enter the ESXi root password. The default password is empty for Release 3.2.

Step 4 Enter cd /tmp to navigate to the upgrade package.

Step 5 Enter tar -xzvf hypervisor.tar.gz to unpack the upgrade package.

Step 6 Enter cd MXE-Hypervisor-upgrade to navigate to the upgrade script.

Step 7 Enter ./setup.sh to execute the upgrade script.

Step 8 Reboot ESXi from the console.

Install the Upgrade License

Procedure

Step 1 Login to the Cisco MXE 3500 UI.

Step 2 Under the Tools tab, click Upload License.

Step 3 Click Browse to navigate to and then select the license file.

Step 4 Uncheck Replace Existing Licenses to add upgrade license to existing license.

Step 5 Click Upload to install the license file on the Cisco MXE 3500.

Restoring the Linux VM from Release 3.2 to Release 3.1Use this procedure to restore the Linux VM to Release 3.1 from a Release 3.2 upgrade.

Before You Begin

• You must have backed up the Linux VM by using the “Upgrade the Linux VM from Release 3.1 to Release 3.2” section on page 2-5 and have the following files from each of the Release 3.1 Resource Manager, and Resource Node installations:

– backUp.sh

– restore.sh

– backup_filelist.txt

– backup_filelist_RN.txt

• You must have the Release 3.1 installation disks.


OL-21554-02

Chapter 2 Upgrading Cisco MXE 3500 Release 3.1 to Release 3.2 Restoring the Widows VM from Release 3.2 to Release 3.1

Restoring Release 3.1 Linux VM on a Resource Manager and Resource Node

To restore a Release 3.2 Linux VM to Release 3.2, complete the following steps for each Resource Manager and Resource Node that you are restoring:


Step 2 Run /opt/cisco/mxe/scripts/clean-lnx-apps.sh.

Step 3 Use the installation DVDs that shipped to reinstall Release 3.1.

Step 4 Copy backup.tar to \\mxe_IP_address\temp\.

Note If you are restoring the Linux VM on multiple Cisco MXE 3500x, ensure that you copy the correct backup.tar file for that device type.

Step 5 SSH t o mxe_IP_address and enter the following commands:

su - cd /mnt/temp/ ./restore.sh

Restoring the Widows VM from Release 3.2 to Release 3.1Use this procedure to restore the Windows VM to Release 3.1 from a Release 3.2 upgrade.

Note You must have backed up the Windows VM by using the “Upgrade the Linux VM from Release 3.1 to Release 3.2” section on page 2-5 to restore.

To restore Windows VM to Release 3.1, replace the following files manually:

• Profiles—\program files\cisco\media experience engine\profiles (entire directory) and any custom profile spaces

• Media files—c:\media (if you are preserving any media files)

• Folder Attendant Configuration—c:\program files\cisco\media experience engine\Folder Attendant\bin\faConfig.xml

• Licenses—c:\program files\cisco\media experience engine\license (entire directory)

• Database configuration—Use the DbAdmin.exe to export data.


OL-21554-02


C H A P T E R 3
Backing Up and Restoring Data for Cisco MXE 3500 Release 3.0 Upgrade to Release 3.2
Revised: June 3, 2011 This chapter describes how to back up Cisco MXE 3500 Release 3.0 to preserve your data and how to restore the data after upgrading to Release 3.2.

The procedures in this chapter will guide you through installing Release 3.2 software, obtaining the migration license to Release 3.1, and obtaining the upgrade license to Release 3.2. The upgrade license to Release 3.2 is required to use the Conversion User Interface and do live streaming to the Cisco Digital Media Player.

The back up and restore procedures are optional. If you do not want to save Release 3.0 data, you can upgrade the software to Release 3.2 without performing the back up and restore procedures.

Note These procedures are applicable for Cisco MXE 3500 in standalone and Resource Manager (RM) mode. For Resource Node (RN) mode, you need to back up and restore data only in the C:\temp directory.

• Preparing for Upgrade, page 3-1

• Migrating a License and Upgrading from Release 3.0 to Release 3.2, page 3-5

• Importing and Restoring Backed Up Data, page 3-10

Preparing for UpgradeComplete the following tasks to prepare for upgrade.

• Documenting System Settings Before Performing Backup, page 3-2

• Backing Up User Data to a Network Drive, page 3-2

• Backing Up Shared Directories and Media Files, page 3-3

• Backing Up the SQL Database, page 3-3

• Backing Up the Folder Attendant (FA) Configuration, page 3-5


Chapter 3 Backing Up and Restoring Data for Cisco MXE 3500 Release 3.0 Upgrade to Release 3.2 Preparing for Upgrade

Documenting System Settings Before Performing BackupTo retain the Cisco MXE 3500 Release 3.0 system settings, log in through the remote desktop and document the system settings.

Procedure

Step 1 RDC into the Cisco MXE 3500.

Step 2 Open My Computer on the remote system desktop.

Step 3 Right click the Context menu and select Properties.

a. In the System properties dialog box, click the Computer Name tab. Write down this information:

– Full computer name (Host name)

– Assigned Cisco MXE 3500 domain, or the workgroup name

b. Click Cancel when you have recorded this information.

Step 4 From My Network Places, right click the Context menu and select Properties.

a. In the Network Connections window, select the connected Local Area Connection. Right click the Context menu and select View Properties.

b. In the Local Area Connection Properties pane, select Internet Protocol (TCP/IP) and then click Properties.

c. In the Internet Protocol (TCP/IP) Properties pane, write down this information:

– Static IP address

– Subnet mask

– Default Gateway

– Preferred DNS server

– Alternate DNS server

Backing Up User Data to a Network Drive

Procedure

Step 1 Open Windows Explorer and map an external network drive, such as drive W:\.

Step 2 Create a root directory under W:\, such as W:\myMXE3500.

Step 3 In Windows Explorer, complete the following steps:

a. Navigate to C:\Program Files\Cisco\Media Experience Engine.

b. Select the Profiles directory.

c. Right click the Context menu and then select Copy.

Step 4 In Windows Explorer, complete the following steps:

a. Navigate to the external network drive.


OL-21554-02


b. Right click the Context menu and then select Paste. The profile directory is copied to the network drive.

Step 5 Repeat Step 3 and Step 4 to copy all your profile spaces and directories.

Backing Up Shared Directories and Media Files

Procedure

Step 1 In Windows Explorer, copy these directories to the external network drive, such as W:\myMXE3500:

• C:\media

• C:\temp

• C:\output

• C:\watch

Step 2 If you have additional shared directories containing media files, copy the files to the external network drive.

Backing Up the SQL DatabaseUse this procedure to export the database configuration to a set of XML files you can back up, and restore after the Cisco MXE 3500 software upgrade.

Procedure

Step 1 Click Start > Programs > Cisco > Media Experience Engine > Media Experience Engine Configuration. The MXE Admin window displays.


OL-21554-02


Figure 3-1 Selecting the Export Configuration

Step 2 Choose Export and replace the Data Directory name with the backup directory name, such as W:\myMXE3500\config.

Caution You must change the default Data directory name or you will overwrite the installed configuration file.

Step 3 Click the Export button. The configuration tables are exported to separate XML files:

• MxeCaptureTypes.xml

• MxeHosting.xml

• MxeIpCaptureConfiguration.xml

• MxeNodeAttributesDef.xml

• MxePermissions.xml

• MxeProfileSpaces.xml

• MxeRoles.xml

• MxeStatisticsTypes.xml

• MxeSystemSettings.xml

• MxeTimedSubmissions.xml

• MxeUserDefinedMetaData.xml

• MxeUsers.xml

• MxeWorkerTypes.xml


OL-21554-02

Chapter 3 Backing Up and Restoring Data for Cisco MXE 3500 Release 3.0 Upgrade to Release 3.2 Migrating a License and Upgrading from Release 3.0 to Release 3.2

Backing Up the Folder Attendant (FA) ConfigurationIn Windows Explorer, copy the following directory to the external network drive, such as W:\myMXE3500:

C:\program files\cisco\media experience engine\Folder Attendant\bin\faConfig.xml

Migrating a License and Upgrading from Release 3.0 to Release 3.2

These procedures are to upgrade Cisco MXE 3500 V1 hardware with Release 3.0 or earlier software to Release 3.2. You must migrate its license after installing the Release 3.1 software. You will obtain a migration license for Release 3.1 and upgrade license for Release 3.2.

Some of the following procedures are better performed on a computer separate from the Cisco MXE 3500. Others can only be performed only on the Cisco MXE 3500.

• Obtaining the License Migration Tool, page 3-5

• Generating the Migration XML, page 3-6

• Installing the Cisco MXE 3500 Release 3.2 Software, page 3-8

• Obtaining the License Host ID, page 3-8

• Obtaining the License for the Migration, page 3-8

• Obtaining the Release 3.1 to Release 3.2 Upgrade License, page 3-10

• Installing the Licenses, page 3-10

Obtaining the License Migration ToolUse this procedure to obtain the LicenseMigration.zip file, which is required for license migration.

Before You Begin

You will need an account on Cisco.com. If you do not have an account, you can create one by clicking the Register link at http://www.cisco.com/.

Procedure

Step 1 Using a separate computer, go to this location on Cisco.com: http://www.cisco.com/cisco/software/type.html?mdfid=282815279

Step 2 Enter your Cisco.com username and password when prompted. The Download Software page appears.

Step 3 In the Select a Software Type panel, click Media Experience Engine Upgrades.

Step 4 Under All Releases > 3 > 3.1.0, download and save the MXELicenseMigration.zip file.

Step 5 RDC into the Cisco MXE 3500 and copy the ZIP file to one of its shared directories, such as \\mxe-ip\\temp.

Step 6 Move the ZIP file to the desktop and unzip it. No special software is necessary to unzip the archive.

Step 7 After you unzip the archive, you should see the following files:


OL-21554-02

http://www.cisco.com/

http://www.cisco.com/cisco/software/type.html?mdfid=282815279


• ReadMe.txt

• LicenseMigration.exe, a utility.

• LicenseMigration.exe.config, a configuration file.

• Cisco_Media_Experience_Engine.cer, an - x509 certificate file.

Step 8 Proceed to “Generating the Migration XML” section on page 3-6.

Generating the Migration XML

Procedure

Step 1 Run LicenseMigration.exe on the Cisco MXE 3500. The migration tool uses the installed Cisco MXE 3500 Release 3.0 license file and x509 certificate to generate the migration XML.

Step 2 The MXE License File path should populate automatically. Verify that the path in MXE License File points to a valid mxe.lic file.


OL-21554-02


Figure 3-2 License Migration Tool

Step 3 Click the Generate XML button. The XML is generated in the text box.

Step 4 Click the Copy to Clipboard button.

Step 5 Create a new text file, and paste the XML copied from the tool.

Step 6 Name the text file anything suitable, such as migration.xml, and save the file that you created on a computer other than the Cisco MXE 3500.

Warning Be sure to save the licence XML on a drive or computer other than the MXE 3500. The install will wipe all data on the MXE you are upgrading.

Step 7 Proceed to “Installing the Cisco MXE 3500 Release 3.2 Software” section on page 3-8.


OL-21554-02


Installing the Cisco MXE 3500 Release 3.2 Software

Procedure

Step 1 Install the Cisco MXE 3500 Release 3.2 software by using the installation information in Chapter 4, “Workflow for Installing the Cisco MXE 3500 Release 3.2 Resource Manager Software” section on page 1-3.

Step 2 Proceed to “Obtaining the License Host ID” section on page 3-8.

Obtaining the License Host ID

Before You Begin

Install the Cisco MXE 3500 Release 3.2 software.

Procedure

Step 1 After Release 3.2 software installation, log in to the Cisco MXE 3500 web UI.

Step 2 Under the Tools tab, click Upload License. The License Host ID displays.

Step 3 Proceed to “Obtaining the License for the Migration” section on page 3-8.

Obtaining the License for the Migration

Procedure

Step 1 Go to www.cisco.com/go/license.

Step 2 Login using your CCO credentials.

Step 3 Scroll down to bottom and click Register for Upgrade/Migrate License.

Step 4 Select Cisco Media Experience Engine v3.1 Migration from the product drop-down box.

Step 5 Click the Goto Upgrade/Migration License Portal button. The Product License Registration page displays.


OL-21554-02


Figure 3-3 The SWIFT Registration Tool

Step 6 In the Host ID field, enter the License Host ID that you obtained when completing the “Obtaining the License Host ID” procedure on page 3-8.

Step 7 In the text box under the Host ID field, copy and paste the contents of your migration.xml file.

Step 8 Click the box to accept conditions of the EULA.

Step 9 Enter Registrant Information, ensuring that the licensee can receive messages at the e-mail given.

Step 10 Click Continue. The License Key will be sent to the Registrant e-mail approximately one hour after submitting the form. Save it to a location that the Cisco MXE 3500 can access during license installation.

Step 11 Proceed to the “Obtaining the Release 3.1 to Release 3.2 Upgrade License” section on page 3-10.


OL-21554-02

Chapter 3 Backing Up and Restoring Data for Cisco MXE 3500 Release 3.0 Upgrade to Release 3.2 Importing and Restoring Backed Up Data

Obtaining the Release 3.1 to Release 3.2 Upgrade LicenseUse this procedure to use eDelivery to order upgrade licenses for each Cisco MXE 3500 in your deployment.

Before You Begin

To log into eDelivery, you need your Cisco username and password.

Procedure

Step 1 Order eDelivery upgrade licenses for each Cisco MXE 3500.

• L-MXE-PAK= and choose the following options:

• L-MXE-3500-LICU (Base software upgrade)

• L-MXE-3500-UILIC (Conversion User Interface)

• L-MXE-3500-LVLICU (Must already have live streaming enabled)

Step 2 Go to https://edelivery.cisco.com/esd/ and then follow the eDelivery process to obtain the Product Authorization Key (PAK).

Step 3 Go to http://www.cisco.com/go/license and then use the PAK and Host ID of Cisco MXE 3500 to obtain the license file.

Step 4 Save the file to a location that the Cisco MXE 3500 can access during license installation.

Installing the Licenses

Procedure

Step 1 Login to the Cisco MXE 3500 UI.


Step 3 Click Browse to navigate to and then select the Release 3.1 migration license file.


Step 5 Check Replace Existing Licenses to replace the default demo license with the base license. Existing licenses will be backed up into a backup directory.

Step 6 Repeat the upload process with the upgrade license but now uncheck Replace Existing Licenses to add upgrade license to the existing license.

Step 7 Proceed to the “Importing and Restoring Backed Up Data” section on page 3-10.

Importing and Restoring Backed Up DataComplete the following tasks to import and restore backed up data after migration:

• Restoring the User Profile, page 3-11


OL-21554-02

https://edelivery.cisco.com/esd/



• Restoring Shared Directories and Media Files, page 3-11

• Restoring the Database, page 3-12

• Restoring the Folder Attendant (FA) Configuration, page 3-13

• Changing the IP Address, page 3-13

Restoring the User Profile

Procedure

Step 1 RDC and log in to the upgraded Cisco MXE 3500 by using the previously recorded IP address.

Step 2 Open Windows Explorer and navigate to C:\Program Files\Cisco\Media Experience Engine.

a. Select the Profiles directory. Make a copy.

b. Paste the copied directory to a new folder named Original-profiles.

Note The Release 3.1 software upgrade changes some default profiles. Restoring Release 3.0 profiles from your backup might override some Release 3.1 profiles. Creating a backup copy of the Release 3.1 profiles enables you to restore the original profiles.

Step 3 Open Windows Explorer and navigate to the network drive used for backup, such as W:\myMXE3500.

Step 4 Make sure all the backed up directories are present.

a. Select the Profile directory. Right mouse click and select Copy.

b. Go to C:\Program Files\Cisco\Media Experience Engine. Right mouse click and select Paste.

c. Confirm you want to overwrite all the destination files.

Restoring Shared Directories and Media Files

Note Beginning with Release 3.1, all shared directories must be hosted under C:\shared. If you had shared folders or watch folders before to Release 3.1, you should copy them to C:\shared as subdirectories. Manually modify the affected setup, such as profiles, watch folders, and FTP configuration.

Procedure

Step 1 For each of the following directories, right-click Context menu and select Copy.

• temp

• media

• output

• watch


OL-21554-02


Step 2 Navigate to C:\ and select Paste.

Restoring the DatabaseUse this procedure to recreate the Cisco MXE 3500 database with exported configuration values.

Procedure

Step 1 Go to Start > All Programs > Administrative Tools > Services to launch Windows Services application.

Step 2 Stop the ECS and CAM Windows services.

Step 3 From the Windows desktop, launch Media Experience Engine Configuration.

Step 4 Select Import from the navigation pane.

a. In the Data Directory field, enter the path used for backup.

b. Enter the SysAdmin password (the default for Release 3.2 is Cisco1).

c. Click the Import button.

Figure 3-4 Import Database Configuration Screen

Step 5 Go to the Windows desktop. Double-click to launch Windows Services application.

Step 6 Restart the ECS and CAM Windows services.


OL-21554-02


Restoring the Folder Attendant (FA) Configuration

Procedure

Step 1 In Windows Explorer, go to the backup directory, such as W:\myMXE3500.

Step 2 Copy the Folder Attendant configuration file, faConfig.xml, to the following directory:

C:\program files\cisco\media experience engine\Folder attendant\bin\

Step 3 From Windows desktop, start Windows services.

Step 4 Restart the MXE Folder Attendant service.

Changing the IP Address

Note Use this procedure if you changed the Cisco MXE 3500 IP address during the migration.

Procedure

Step 1 Log in to the web UI.

Step 2 Change the Host IP to the new the IP.

a. Go to Administration/Host, select a host from Configured Hosts. Double click to edit.

b. Click Save.

c. Click the Apply Configuration button and confirm you want to apply the changes.

Step 3 Click Administration/System. Replace all fields which contain the previous IP address with the new IP address. Click Save.

Step 4 Change Webcast distribution profile(s). Each webcast distribution profile contains a reference to the previous IP address.

a. Open each of the Webcast profiles, change the IP address and save the profile.

Step 5 If you restored any webcast distribution profiles for Windows Media Services (WMS) from a previous Cisco MXE 3500, you must perform these steps:

a. Open each webcast profile in the Cisco MXE 3500 UI and make sure the port number is between 9,000 and 10,000.

b. Change the port number if it is not within the range and save the webcast profile.

Note You must reconfigure your WMS publishing point to continue using this profile for WMS live streaming.


OL-21554-02



OL-21554-02


C H A P T E R 4
Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration

This section includes the following topics:

• About Cisco MXE 3500 Release 3.2, page 4-1

• About the Cisco MXE 3500 Standalone Deployment, page 4-2

• Guidelines for a Standalone Deployment, page 4-2

• How to Configure Cisco MXE 3500 Release 3.2 for a Standalone Deployment, page 4-3

• Accessing the Cisco MXE 3500 Web User Interface (Standalone or Resource Manager), page 4-3

• Accessing the Cisco MXE 3500 Tools (Standalone and Resource Manager), page 4-4

• Installing a License on Cisco MXE 3500 (Standalone or Resource Manager), page 4-4

• Configuring the Input and Output Media Directories (Standalone or Resource Manager), page 4-7

• Enabling System Administration E-mail Notifications (Standalone or Resource Manager), page 4-8

• Configuring the Host Settings (Standalone Only), page 4-9

• Confirming Service Accounts and Identifying Device Type (Standalone or Resource Manager), page 4-10

• Creating a Folder Attendant Directory and Watch (Standalone or Resource Manager), page 4-11

• Using Administrative Tools to Configure a Standalone Cisco MXE 3500, page 4-12

• Testing a Cisco MXE 3500 Deployment (Standalone or Resource Manager), page 4-24

• Providing Documentation Feedback, page 4-27

About Cisco MXE 3500 Release 3.2Cisco MXE 3500 Release 3.2 is a software upgrade.

Cisco MXE 3500 V2 Hardware

If you have received a new Cisco MXE 3500 V2 appliance, then Release 3.2 software is preinstalled. You need only to complete network and admin user configuration before you configure the software for your deployment. To configure network settings, see the procedures in the Quick Start Hardware


Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration About the Cisco MXE 3500 Standalone Deployment

Installation Guide for Cisco Media Experience Engine 3500 that shipped with your product or “Completing Initial Setup: Network Settings and Admin User Account Configuration” section on page 1-6; then, return to this chapter for deployment information.


If you are using the Cisco MXE 3500 V1 appliance, then the upgrade is required. To upgrade to Release 3.2, see Chapter 3, “Backing Up and Restoring Data for Cisco MXE 3500 Release 3.0 Upgrade to Release 3.2” and Chapter 1, “Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2.” Then, return to this chapter for deployment information.


About the Cisco MXE 3500 Standalone Deployment • A standalone deployment consists of one or more Cisco MXE 3500s running as individual devices;

each device has its own set of user accounts, job profiles, licensed features, and user interfaces. For information about Resource Manager deployments, see Chapter 5, “Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration.”

• To enable a licensed feature, you must purchase and install the feature license on the Cisco MXE 3500. For information about deploying licensed features, see Chapter 6, “Deploying Licensed Features for Cisco MXE 3500.”

Guidelines for a Standalone DeploymentThe following configuration guidelines and restrictions apply to standalone deployments:

Warning The built-in user account, mxe-service, is used to run the Cisco MXE 3500 application services and access all configured UNC paths and shared media folders. Do not delete this account or change the password. Otherwise, the device will not work properly.

• The Hostname must be unique and can be set as part of the installation process.

• We recommend that you use Remote Desktop Connection (RDC) to access remotely the Windows virtual machine on a Cisco MXE 3500.

• The IP address must be unique.

• Beginning with Release 3.1, all shared directories must be hosted under C:\shared. If you had shared folders or watch folders before to Release 3.1, you should copy them to C:\shared as subdirectories. Manually modify the affected setup, such as profiles, watch folders, and FTP configuration.


OL-21554-02

Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration How to Configure Cisco MXE 3500 Release 3.2 for a Standalone Deployment

How to Configure Cisco MXE 3500 Release 3.2 for a Standalone Deployment

Release 3.2 requires the following mandatory configuration before using the system. Optional deployment configuration is identified, as well.

Mandatory Configuration


• Installing a License on Cisco MXE 3500 (Standalone or Resource Manager), page 4-4


• Enabling System Administration E-mail Notifications (Standalone or Resource Manager), page 4-8

• Configuring the Host Settings (Standalone Only), page 4-9

Optional Configuration

• Confirming Service Accounts and Identifying Device Type (Standalone or Resource Manager), page 4-10

• Creating a Folder Attendant Directory and Watch (Standalone or Resource Manager), page 4-11

• Testing a Cisco MXE 3500 Deployment (Standalone or Resource Manager), page 4-24

• Deploying Licensed Features for Cisco MXE 3500, page 6-1

Accessing the Cisco MXE 3500 Web User Interface (Standalone or Resource Manager)

Note The Cisco MXE 3500 web user interface (web UI) is the main interface that you use to set up encoder server and client preferences, create job profiles, and submit transcoding jobs. For information about Cisco MXE 3500 components, including user interfaces, see the User Guide for Cisco Media Experience Engine 3500 on Cisco.com, or click Help in the UI.

Procedure

Step 1 Using a supported web browser, go to http://mxe_IP_address/MxeUI where mxe_IP_address is the hostname or IP address for the Cisco MXE 3500.

Step 2 Enter the default credentials:

• User Name: admin

• Password: admin

Note We recommend that you change the default password.


OL-21554-02


Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Accessing the Cisco MXE 3500 Tools (Standalone and Resource Manager)

Accessing the Cisco MXE 3500 Tools (Standalone and Resource Manager)

You use the Cisco MXE 3500 web UI for most maintenance and operational tasks. However, you complete the following tasks by using other Cisco MXE 3500 tools:

• Set independent profile space

• Preview preprocessor clips

• Create and edit a QuickTime Encoder Profile

• Use additional deck control tools

Note For information about Cisco MXE 3500 tools, see the User Guide for Cisco Media Experience Engine 3500 on Cisco.com, or click Help in the UI.

Procedure

Step 1 RDC to mxe_IP_address. See “Administrative User Accounts (Standalone or Resource Manager)” section on page 4-21 for more information.

Step 2 Click Start > Programs > Cisco > Media Experience Engine > Media Experience Engine Tools.

Installing a License on Cisco MXE 3500 (Standalone or Resource Manager)

• Obtaining the License Host ID, page 4-4

• Obtaining a New, Upgrade, or Feature License, page 4-5

• Installing a License File, page 4-7

Obtaining the License Host IDLicensing requires that you provide the License Host ID, which is used to generate a license. You use the same License Host ID for all license requests—initial or upgrade.

Note For Resource Manager deployments, you must use the same License Host ID for every RN (Resource Node) or RM (Resource Manager) in your installation. For more information about Resource Manager deployments, see Chapter 5, “Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration.”


OL-21554-02


Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Installing a License on Cisco MXE 3500 (Standalone or Resource Manager)

Procedure

Step 1 Login to the web UI.


Step 3 Provide the License Host ID to Cisco, as shown in Figure 4-1, when you obtain a new, upgrade, or feature license.

Figure 4-1 License Host ID String

Obtaining a New, Upgrade, or Feature License

Before You Begin

• You must have an account on Cisco.com to access the license website. Register for an account at the following URL: http://www.cisco.com/web/siteassets/account/index.html

• Obtain the Cisco MXE 3500 License Host ID. See also: Obtaining the License Host ID, page 4-4.

Note Licensing requires that you provide the License Host ID, which is used to generate a license. You use the same License Host ID for all license requests—initial or upgrade.

Note For Resource Manager deployments, you must use the same License Host ID for every RN (Resource Node) or RM (Resource Manager) in your installation. For more information about Resource Manager deployments, see Chapter 5, “Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration.”


OL-21554-02

http://www.cisco.com/web/siteassets/account/index.html

Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Installing a License on Cisco MXE 3500 (Standalone or Resource Manager)

• Obtain the Product Authorization Key (PAK) for you standalone Cisco MXE 3500 or the Product Authorization Keys (PAKs) for the Resource Manager device and Resource Nodes. The PAK is located on the Software License Claim Certificate that shipped with your device.

• Ensure that you understand the licensing process for Resource Manager deployments. See also: “Guidelines for a Resource Manager Deployment” section on page 5-2 and “How to Configure Cisco MXE 3500 Release 3.2 for a Resource Manager Deployment” section on page 5-3. You must complete the registration of the Resource Manager device first and obtain the license for that registration process before you register the Resource Node(s), completing registration and obtaining the updated license files one at a time. You will install the license that you receive for the final completed registration process on the Resource Manager device.

Procedure

Step 1 Obtain the Product Authorization Key (PAK), which is located on the Software License Claim Certificate that shipped with your appliance.

Step 2 Go to http://www.cisco.com/go/license.

Step 3 Enter the PAK. If you are using the Cisco MXE 3500 to access the registration website, press the Enter key; otherwise, click the Submit button.

Step 4 Follow the on-screen prompts. Shortly after registration, you will receive an e-mail with the Cisco MXE 3500 license file.

Note If this license file is for a Resource Manager and you have additional Resource Nodes to register, discard this license. Complete the registration process for each Resource Node, ensuring that you use the PAK for the Resource Node and the License Host ID for the Resource Manager.

Note We recommend that you save the license file. If the license file is lost, it can take up to one business day to get another copy.

Troubleshooting Tips

If you experience problems with the registration websites or if you have additional questions, for a prompt response, please open a Service Request using the TAC Service Request Tool at:

http://tools.cisco.com/ServiceRequestTool/create/DefineProblem.do.

Please have your valid Cisco ID and password available. As an alternative, you may also call one of these numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)

EMEA: +32 2 704 55 55

USA: 1 800 553-2447

You can find a complete list of Cisco TAC contacts at this URL:

http://www.cisco.com/techsupport/contacts


OL-21554-02


http://tools.cisco.com/ServiceRequestTool/create/DefineProblem.do


Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Configuring the Input and Output Media Directories (Standalone or Resource Manager)

Installing a License FileUse this procedure to install the license that you obtained on the Cisco MXE 3500.

Note For Resource Manager deployments, install the license file only on the Resource Manager device.

Procedure

Step 1 Log in to the web UI.


Step 3 Click Browse to navigate to and then select the license file.


• During first-time installation, check Replace Existing Licenses to replace the default demo license with the base license. Existing licenses will be backed up into a ‘backup’ directory.

• Uncheck this option to install an incremental or feature license.

• License file name does not matter; it will be renamed.

Step 5 On successful upload the License uploaded successfully message displays.

Step 6 Click OK. The Host Administration page displays.

Configuring the Input and Output Media Directories (Standalone or Resource Manager)

For the Cisco MXE 3500 to obtain input and store output media, you must configure the input and output directories.

Before You Begin

Ensure that any directories that you are going to configure exist and are shared.

Procedure

Step 1 Log into the web UI as an administrator.

Step 2 From the Toolbox, select Administration > System.

Step 3 In the following fields of the Input section, enter the directories where Cisco MXE 3500 will obtain input media, such as \\mxe_IP_Address\media. For more information, see the “Input Section (Standalone Only)” section on page 4-16.

• Bumper

• Common

• Media

• Watermark


OL-21554-02

Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Enabling System Administration E-mail Notifications (Standalone or Resource Manager)

Step 4 In all the fields in the Output section, enter the directories where Cisco MXE 3500 will store output media, such as \\mxe_IP_Address\output. For more information, see the “Output Section (Standalone Only)” section on page 4-18.

Step 5 Click Save.

Enabling System Administration E-mail Notifications (Standalone or Resource Manager)

For Cisco MXE 3500 to send e-mails for job completion or failure notifications, it must be configured to point to an e-mail server that allows e-mails to be relayed from it.

Note The sending of e-mails is not required to complete transcoding jobs.

Procedure

Step 1 Login to the web UI as an administrator.

Step 2 Enter the SMTP server and e-mail for the system administrator:

a. From the Toolbox, click Administration > System.

b. In the General Settings section, enter the following settings:

• In the SMTP Server field, enter the name of the server that will be used to send e-mail notification messages. The server must be running the Simple Mail Transport Protocol (SMTP) service.

• In the in the System Administrator Email field, enter the e-mail address that will be used to contact the System Administrator. This e-mail address can be used to send messages to a regular e-mail account or to a text- enabled pager or cellular phone. The System Administrator e-mail address is used by Notification Profiles when the System Administrator options for From Email Address or To Email Address are selected. See also: General Settings Section (Standalone or Resource Manager), page 4-18.

c. Click Save.

Step 3 Create a Notification Profile:

a. From the Toolbox, click Profile Management > New Profile.

b. From the New Profile pop-up Profile Class drop-down, select Distribution.

c. Highlight Notification, and click the New Profile button. The New Notification Profile page displays.

d. Enter the following notification settings, and click Save:

• In the Common section, check the Profile Enabled box.

• In the Notification Criteria section, choose the status at which a notification is sent.

• In the Email Notification section, enter the following settings:

Check the Enabled box to enable this profile for job processing.

In the From field, select System Administrator.


OL-21554-02

Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Configuring the Host Settings (Standalone Only)

In the To field, select System Administrator.

Step 4 (Optional) Add the Notification Profile to any Job Profile for which you want to receive notifications:

a. From the Toolbox, click Profile Management > New Profile or Open Profile.

b. From the Profile Class drop-down, select Job, and click New Profile or Open Profile.

c. Expand the Notification section.

d. Select one or more Notification Profile(s).

e. Click Save.

Configuring the Host Settings (Standalone Only)Use this procedure to configure the Host settings for a standalone Cisco MXE 3500.

Procedure

Step 1 From the Toolbox, select Administration > Host. See also: Host Settings (Standalone Only), page 4-13.

Step 2 Modify the Host:

a. From the Host Administration menu, click the arrow to the right of Host Options > Edit. The Edit Host pop-up displays.

b. In the Host Name field, enter the Host name. This name must be a valid computer name that you configured for the standalone Cisco MXE 3500.

c. In the Temp Directory field, enter the local or UNC path for the temp folder on the Host that you configured in Step b.

d. Click Save. The modified Host displays in the Hosts pane.

Note Cisco MXE 3500 does not verify that the Host name and the Temp Directory are valid during Host configuration. If either setting is invalid, errors will occur during operations that require their use.

Step 3 Add workers to the Host that you created in Step 2:

a. Select each Worker that is assigned to the Host.

b. Click Permit or click Permit All.

Note The list of workers displayed is controlled by your license level. If you select the Permit All option, only all non-Live workers will be permitted. Live workers require manual entry of additional data.

Step 4 Configure the Limit, Expense, and live capture information for each worker:

a. Click each Worker and click Edit. The Edit worker pop-up displays.

b. Enter the Limit and the Expense.

c. For live captures, enter Capture Name, Capture Type, Video CH, and Audio CH.


OL-21554-02

Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Confirming Service Accounts and Identifying Device Type (Standalone or Resource Manager)

d. Click Save.

Step 5 At the top of the page, click Apply Configuration.

Confirming Service Accounts and Identifying Device Type (Standalone or Resource Manager)

This step is not required, but you may choose to confirm that your service accounts are enabled and have access to network locations. The service accounts are accounts that are local administrators on the Cisco MXE 3500. The accounts can be local computer accounts or domain accounts.

Tip You can quickly determine the Cisco MXE 3500 device type (standalone/Resource Manager, or Resource Node) by verifying which services are started. See Table 4-1.

Procedure

Step 1 RDC to mxe_IP_address.

Step 2 Open Services by double-clicking the Services icon on your desktop or from the Control Panel.

Step 3 Select the MXE services for your device type one at a time, as shown in Figure 4-2.

Note Table 4-1 lists the services for each Cisco MXE 3500 device type.

Table 4-1 Status of Services for Cisco MXE 3500 Device Types

ServiceStandalone or Resource Manager Resource Node

IIS Admin Service Started Service does not exist

Mxe CAM Started Service does not exist

Mxe ECS Started Service does not exist

Mxe Encoder Started Started

Mxe Folder Attendant Started Service does not exist

Mxe Log Service Started Started


OL-21554-02

Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Creating a Folder Attendant Directory and Watch (Standalone or Resource Manager)

Figure 4-2 Selecting a Service Account

Step 4 Double-click each service—except IIS Admin Service— and then select the Log On tab. The service account can be changed from the default on this page.

Note • This action is not required for Cisco MXE 3500 to function. Your system is shipped with a default service account that has the correct permissions to run the default configuration.

• For certain functions across the network, such as copying output files to a different computer, Cisco MXE 3500 uses the service accounts to authenticate and access those network resources. You must make sure that these service accounts have appropriate access.

Creating a Folder Attendant Directory and Watch (Standalone or Resource Manager)

One of the key features of Folder Attendant is its ability to monitor directories and automatically initiate job processing when new or updated media/XML files appear. When a new or updated file, meeting the specified criteria, appears in a directory being monitored, Folder Attendant automatically initiates job processing based on the configured job parameter settings, such as profile and priority.

You must first define directories to be watched on the Folder Attendant Administration page. Then, multiple watches can be configured per directory.

Note For detailed field and setting descriptions and instructions on how to create, edit, and delete directories and watches, see the User Guide for Cisco Media Experience Engine 3500 on Cisco.com or by clicking Help from the main menu of the Folder Attendant user interface.


OL-21554-02


Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Using Administrative Tools to Configure a Standalone Cisco MXE 3500


• Creating a Directory, page 4-12

• Creating a Watch, page 4-12

Creating a Directory

Procedure

Step 1 From the Toolbox, click Folder Attendant.

Step 2 From the Directory drop-down, click Add.

Step 3 Enter the appropriate information in each of the fields, and click Save.

Note If the Directory Path points to a network location, make sure that the service accounts have appropriate access to that network location.

Creating a Watch

Procedure

Step 1 From the Toolbox, click Folder Attendant.

Step 2 Highlight the Directory for which you want to add a watch, and from the Watch drop-down, click Add. The Folder Attendant Administration page displays Directory, Watch, Custom Metadata, and Override System Settings each of which contains a series of fields.

Step 3 Expand each section, and enter the appropriate information in each field.

Step 4 Save the Watch.

Using Administrative Tools to Configure a Standalone Cisco MXE 3500

Note Although all possible configuration options are presented here, your system and user settings come preconfigured; moreover, some settings are not configurable for standalone Cisco MXE 3500 deployments. The only initial configuration required of you for standalone configuration is enabling system administration e-mail notifications. No other changes are necessary. However, we recommend that you add passwords or change the default user accounts.

The Administration section of the Toolbox allows you to configure the following settings:


OL-21554-02


• Host Settings (Standalone Only), page 4-13

• System Settings, page 4-16

• Administrative User Accounts (Standalone or Resource Manager), page 4-21

• User Metadata Settings, page 4-22

• IP Capture (Live Streaming) Settings (Standalone or Resource Manager), page 4-22

Note You must have Admin Tools permission to configure these settings.

Host Settings (Standalone Only)The Host Administration page allows administrators to configure the Cisco MXE 3500 to work with computers on the network. Host is simply another word for the computer or system that runs the Cisco MXE 3500. The Host Administration page is used to tell the Enterprise Control System (ECS) what the Hosts are capable of running (what the load capacity of the machine is and what software is installed).

From the Toolbox, click Administration > Host to display the Host Administration page and view summary information about workers configured on that Host along with a limited number of editable fields.

Figure 4-3 shows the Host Administration page.


OL-21554-02


Figure 4-3 Host Administration Page and Settings

Table 4-2 describes the Host settings.

Table 4-2 Host Settings and Descriptions

Setting Description

Host This is the name of the machine running the Cisco MXE 3500 LCS. The computer name and the Host name must match exactly.

To verify the computer name of a Windows Server computer, right-click the My Computer icon on either your desktop or in your Start Menu, select Properties, then select the Computer Name. For an NT computer, right-click Network Neighborhood, select Properties, and select the Identification tab. Alternately, type the hostname command at the command prompt to display the computer name.

Status Displays the status of the Host: Enabled or Disabled.

To change the status, right-click the Host or click Host Options, and select Enabled or Disabled.

Note If the status is disabled, jobs will not schedule on that Cisco MXE 3500 node.

Port TCP port that the LCS is listening on. The default is 3500.


OL-21554-02


Capacity Reflects a numeric value (0-99) assigned for the total available processing capacity of the displayed Host.

Capacity can be any number for a given Host, but it is important that all Hosts be numbered according to the same standards. For example, for one particular Host it will not matter if the total capacity is set at 5 or at 10. However, if there is another Host that has twice the capacity, the capacity of both Hosts should be listed in common terms. So, a Host that is twice as powerful would have a capacity of 10 if the first Host was 5, or 20 if the first Host was 10.

Capacity is directly related to processor capacity, but may also be affected by drive speed, network congestion, and other factors. All of the factors that affect the amount of work a particular Host can do efficiently should be considered when assigning a capacity value.

Note Numbers between 5 and 30 are typically best. Setting this to a high number > 30 can make the system status monitor hard to read.

Temp Directory (UNC Name)

Specifies the directory where temporary files and preprocessor output will be store, such as \\mxe_IP_Address\temp.

Unless the Preprocessor box in the Output Profile is checked to specify that Preprocessor files should be saved, files written to the Temp Directory will be deleted automatically when encoding is complete.

Permitted? • Green checkmark: Indicates that the worker listed to the right is configured to run on the displayed Host and that it is currently online and available to process tasks.

• Red X: Indicates either:

– The worker listed to the right is configured to run on the displayed Host but is currently offline and cannot be contacted by the ECS.

or

– The worker is not enabled or configured.

Worker Displays a list of all workers that have been configured to run on the displayed Host.

The Name, DV, DVCAM, Video Channel, and Audio Channel fields appear only for Live capture workers and define the location of the capture card on the Host. Channels are numbered sequentially from 0.

Licensed Indicates the number of concurrent instances of this worker type (example: prefilter, encoder, distribution) that can be running on the system (all nodes controlled by that ECS). This value is defined in the Cisco MXE 3500 license file.

Limit Displays the maximum number of a particular worker that can be run simultaneously on the displayed host.

Limit is a fixed setting in the Cisco MXE 3500 to return the best possible performance.

Expense The expense of a worker is expressed as a portion of Host capacity.

Expense is a fixed setting in the Cisco MXE 3500 to return the best possible performance.

Capture Name This setting is not available in Cisco MXE 3500.

Defines the name associated with a live capture worker. Because Hosts can have more than a single video capture card and can be configured to run more than one Live capture worker, the Capture Name is required in order to identify the specific capture card used by the worker. This is only displayed for Live capture workers.



OL-21554-02


System Settings System Administration is used to define locations and parameters for files and directories used with the Cisco MXE 3500. It also includes settings for other system-wide parameters.

Access this page from the Toolbox by clicking Administration > System.


The System page is made up of the following sections:

• Input Section (Standalone Only), page 4-16

• Output Section (Standalone Only), page 4-18

• General Settings Section (Standalone or Resource Manager), page 4-18

• Status Settings Section (Standalone or Resource Manager), page 4-18

• Data Purging Section (Standalone or Resource Manager), page 4-19

• Audio Capture Section (Standalone or Resource Manager), page 4-20

Input Section (Standalone Only)

Figure 4-4 shows the Input section settings.

Figure 4-4 Input Settings

Table 4-3 describes the settings.

Capture Type This setting is not available in Cisco MXE 3500.

Type of capture card (DV, DVCAM, AJA-SDI, Custom, etc.). Selection of a non-custom value will predefine the audio and video channel.

Video CH/Audio CH

This setting is not available in Cisco MXE 3500.

Displays Video Channel and Audio Channel for each Live-capture worker.



OL-21554-02


Table 4-3 Input Settings and Descriptions

Setting Description

Bumper/Trailer Directory

Defines the location of files that can be used as bumpers or trailers to clips encoded with the Cisco MXE 3500. The Bumper/Trailer Directory controls the directory path where the Cisco MXE 3500 searches for files displayed in the Bumper Source and Trailer Source fields in the Preprocessing Profile page.

The Bumper/Trailer Directory value can be entered either as a UNC path to a network share or to a mapped drive in the case of a deployment using a storage area network (SAN) or a single node deployment. The Bumper/Trailer Directory location must be accessible to all hosts.

Common Directories

Defines the directories where media files will be stored. Multiple directories can be defined. A semi-colon is used to separate directory entries.

The Common Directory values can be entered either as a UNC path to a network share or to a mapped drive in the case of a deployment using a storage area network (SAN) or a single node deployment. The Common Directory locations must be accessible to all hosts.

Media Directory Defines the directory where media files that will be submitted to the Cisco MXE 3500 are stored. The Media Directory controls the directory path where the Cisco MXE 3500 searches for files displayed in the Source box on the File Submission page.

The Media Directory value can be entered either as a UNC path to a network share or to a mapped drive in the case of a deployment using a storage area network (SAN) or a single node deployment. The Media Directory location must be shared and accessible to all Hosts.

The System Administration page will give a warning if the value entered is not a UNC path, which is recommended. If using a mapped drive, all nodes configured to work with the Cisco MXE 3500 must have the location mapped as the same drive.

Profile Directory Defines the default path the ECS will use to search for Job Profiles when processing a submitted job.

Valid Input Extensions

Defines the list of valid extensions for files in Common Directories. Only files with extensions listed in this field will be displayed in the Selection List window in the Input section of the File Job Submission form. A semi-colon is used to separate file-extension entries.

Watermark Directory

Defines the location of files that can be used as watermarks for clips encoded with the Cisco MXE 3500. The Watermark controls the directory path where the Cisco MXE 3500 searches for files displayed in the Source drop-down in the Watermark section of the Preprocessing Profile page.

The Watermark Directory value can be entered either as a UNC path to a network share or to a mapped drive in the case of a deployment using a storage area network (SAN) or a single node deployment. The Watermark Directory location must be accessible to all hosts.


OL-21554-02


Output Section (Standalone Only)

Output Directories define the location the Cisco MXE 3500 will use to save files of each encoding format supported by the licensing levels of your Cisco MXE 3500 system. Encoded files will be saved to the defined directories when either no Distribution > Output Profile is included in the Job Profile or when the checkbox in the Save Local File section of the Output Profile has been checked.

The Microsoft Output Directory value can be entered either as a UNC path to a network share or to a mapped drive in the case of a deployment using a storage area network (SAN) or a single node deployment.

General Settings Section (Standalone or Resource Manager)


Status Settings Section (Standalone or Resource Manager)

Figure 4-5 shows the Status Settings section.

Table 4-4 General Settings and Descriptions

Setting Description

Default Copyright Defines the default copyright information populated to the copyright field in all job submission pages. The Default Copyright is a system-wide setting. The value entered can be overwritten by the user when jobs are submitted by typing over the default information displayed.

LCS Disconnect Notifications

If yes, the Cisco MXE 3500 generates an e-mail (sent to the System Administrator) when an LCS disconnects from the ECS.

LCS Notification Frequency

Frequency in seconds in which an LCS disconnect e-mail will be generated if multiple disconnects occur.

License Expiration Warning

Defines the period, in days, ahead of the license expiration date that an e-mail will be sent to the e-mail address defined in the System Administrator Email field.

Restart IP Capture/Webcast on Failure

• yes: restart IP Capture on failure

• no: do not restart IP Capture on failure

Simultaneous Node Restart Limit

Defines the number of times an IP Capture job may restart due to problems encountered during capture and/or streaming before the job will fail.

SMTP Server Identifies the e-mail server used to send notification messages. The server identified must be running the Simple Mail Transport Protocol (SMTP) service to enable processing of e-mail messages.

System Administrator Email

Stores an e-mail address used to contact the System Administrator. This e-mail address can be used to send messages to a regular e-mail account or to a text-enabled pager or cellular phone. The System Administrator e-mail address is used by Notification Profiles when the System Administrator options for From Email Address or To Email Address are selected.


OL-21554-02


Figure 4-5 Status Settings


Data Purging Section (Standalone or Resource Manager)

Over time, job data, such as job, task, executioncontext, executioncontextlog, and related tables, grow and fill up disk space. The Data Purging section allows you to configure automated system purging, which physically deletes the appropriate records.

Note After initial or reset of Data Purging values, restart the CAM service to enable this feature or for changes to take place immediately.

Figure 4-6 shows the Data Purging section.

Table 4-5 Status Settings and Descriptions

Setting Description

Monitor Window Display

This setting only applies in Console mode. If set to on, some workers (like preprocessor and encoders) will display a monitor window

which displays the video being processed.

Note This option does use system resources (such as CPU cycles, memory) and will slow down overall job processing. It may be used for debugging purposes or viewing encoded output.

Auto Reap (Minutes)

Defines the Auto Reap interval used to clear job information from monitoring pages. The time defined for Auto Reap determines how long information on a job will be displayed in monitoring pages before it expires. The Auto Reap interval is counted from the time the job completes.

Include Failed Jobs in Auto Reap

• yes: include failed jobs in Auto Reap

• no: do not include failed jobs in Auto Reap


OL-21554-02


Figure 4-6 Data Purging Settings


Audio Capture Section (Standalone or Resource Manager)

Figure 4-7 shows the Audio Capture section.

Figure 4-7 Audio Capture Settings


Table 4-6 Data Purging Settings and Descriptions

Setting Description

Purge Enabled • yes: purge enabled

• no: purge not enabled

Job Completion Duration

In minutes, how long after the job was completed, before it is deleted.

Purge Batch Size This setting limits the number of jobs to be deleted.

Time to Execute Purge Configures the time of day the purge occurs.

Purge Interval Configures the number of days between purges.


OL-21554-02


Administrative User Accounts (Standalone or Resource Manager)The following two virtual machines (VMs) comprise the Cisco MXE 3500 application (MXE application):

• Windows VM, page 4-21—Hosts the Cisco MXE 3500 Release 3.2 software.

• Linux VM, page 4-22—Provides external services, such as FTP and HTTP, and acts as a proxy to services on the Windows VM for added security.

Note Hypervisor (ESXi) also ships with Cisco MXE 3500. You cannot access ESXi remotely. The default root login password is blank.

Windows VM

Table 4-7 Audio Capture Settings and Descriptions

Setting Description

Drift Compensation

From the drop-down, select on to enable audio and video synchronization. This is only necessary when capturing clips longer than 5 minutes that use an analog audio capture card. It is not necessary when using digital audio input (embedded SDI, AES/EBU, or DV).

Note When capturing long analog audio clips, the Cisco MXE 3500 will insert or remove frames to maintain audio sync over a long time period. The effect of this compensation is not easily visible in typical streaming media output (320x240 @15fps, or anything smaller in size or frame rate). However, a user may see a ‘skipping’ effect on D1 clips, for example, when encoding long clips into MPEG2 format. The only work-around is to switch to digital audio input.

Sample Rate Sets audio sampling rate to trade off audio quality and transmission bandwidth and file size limitations.

Table 4-8 Predefined Windows User Accounts

Account Default Password Function

Windows VM

mxe-service Cisco1 Used to access shared folders and for Cisco MXE 3500 applications

Note Do not delete or change the password for this account; otherwise, the Cisco MXE 3500 will not work properly.

admin change_it • Used to perform Windows administrator functions

• Used to RDC and log in to the Windows VM

Note The Linux configuration wizard that launches during first boot requires you to change this password. The configuration synchronizes the Windows VM admin and Linux VM admin passwords.


OL-21554-02


Linux VM

User Metadata SettingsThis User Metadata Administration page allows you to create custom name/value pairs that can be submitted with each job (and each task in the job). This custom metadata is returned in detailed job status including the HTTP POST job-status XML. This metadata (if submitted) is also stored in the database for each job and can be used for reporting purposes (like tracking which organization submitted which jobs) or (via HTTP POST) where it is passed back to other systems (like Velocity).

The Data Type can be defined as Integer, String, Decimal, or Enum (Enumeration). This type is used for validation when entering the user metadata values on the Job Submission pages.

Access the User Metadata Administration page from the Toolbox by clicking Administration > User Metadata. The New or Edit User Metadata e pop-up displays and allows you to create and modify user metadata settings.

IP Capture (Live Streaming) Settings (Standalone or Resource Manager)Cisco MXE 3500 enables ingest of live MPEG-2 Transport streams over UDP/IP with management, configuration, and status that enable general use of this feature. IP captures are limited to transport streams with MPEG2 video and AC3/Layer2/AES3 audio essences.

Windows MXE Web UI (Web UI)

admin admin Used to log in to the Cisco MXE 3500 Web UI

Note We recommend that you change the admin password immediately. You change this password in the Web UI.

Table 4-9 Predefined Linux User Accounts


mxe-service Cisco1 Used for communication between Linux and Windows VMs

Note Do not delete or change the password for this account; otherwise, the Cisco MXE 3500 will not work properly.

mxe-user — Used to access default shared folders

Note This account is disabled by default. When you enable access to shared folders in the Linux configuration utility, you are prompted to enter a password.

admin change_it Used to perform system admin functions

Note The Linux configuration wizard that launches during first boot requires you to change this password.

root C1sco!23 Used to perform root functions

Table 4-8 Predefined Windows User Accounts



OL-21554-02


The IP Capture Configuration page is used by administrators to add, edit, or delete an IP capture source.

Access this page from the Toolbox by clicking Administration > IP Capture.

The New or Edit IP Capture Source pop-up, shown in Figure 4-8, allows you to create and modify profile spaces.

Figure 4-8 IP Capture Source Settings


Note Before submitting a job, you must

1. Add an IP capture source.

2. Configure the ipCapturePrefilter Worker on the Host Administration page. See also: Host Settings (Standalone Only), page 4-13.

3. On the Live Submission page, set the Video Format to IP Capture, select the IP Capture Source that you defined, Start and Stop Trigger Types. To view the Live Submission Page, from the Toolbox, expand Submission and click Live.

Table 4-10 IP Capture Source Settings and Descriptions

Setting Description

Name Unique IP Capture Source name.

Protocol Source protocol: UDP, RTP, MMS, or HTTP

IP Address For MPEG2 sources: the multicast IP address of the source MPEG-2 Transport Stream. The IP addresses reserved for this purpose are from 224.0.0.0 to 239.255.255.255. For Windows Media sources: the source stream URL.

Port The multicast port to bind to. Values range from 0 to 65535 (only applicable for UDP and RTP sources).

Program Map PID Specifies the Program Map Table Packet ID (PMT PID) of the desired program in an MPEG-2 Multi-Program Transport Stream (MPTS).

For MPEG-2 Single Program Transport Streams (SPTS) or if not specified, the first program listed in the Program Map Table is used automatically. Valid values range from 16 to 8190. (Only applicable for UDP and RTP sources.)


OL-21554-02

Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Configuring User Accounts

Configuring User AccountsIn a standalone Cisco MXE 3500 configuration, there is a single administrative user, and there is no option to create additional web UI users. User management, including defining roles and restricting user access to web UI features, is available in Resource Manager configuration. For more information about user management, see the “User Settings (Resource Manager Only)” section on page 5-13.

Testing a Cisco MXE 3500 Deployment (Standalone or Resource Manager)

To ensure your system has been correctly deployed and configured, perform the following tests:

• Test 1: Submit a Job Using File Job Submission, page 4-24

• Test 2: Submit a Job Using Folder Attendant, page 4-25

• Test 3: Verify a Licensed Feature is Enabled, page 4-25

Test 1: Submit a Job Using File Job Submission

Before You Begin

In the \\Resource_Manager_IP_Address\media folder, look for any sample media file, e.g., within \SpeechToTextFiles, or copy an existing media file to the \\Resource_Manager_IP_Address\media directory.

Procedure


Step 2 From the Toolbox, select: Submission > File. The File Job Submission page should appear.

Step 3 In the Profile section, choose Cable_Broadband.job.awp.

Step 4 In the Input section, complete the following tasks:

a. Select Browse

b. Select the file’s source directory, for example, \\Resource_Manager_IP_Address\media\.

Step 5 From the toolbox, select Monitoring > Job Status.

Step 6 Continue watching the Job Status window to make sure the job completes.

Step 7 Browse to the \\Resource_Manager_IP_Address\Output folder, and locate Sample.Cable_Broadband.Cable_Broadband.wmv, and play the file. Accept any warning messages or alerts Windows Media Player may display.


OL-21554-02

Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Testing a Cisco MXE 3500 Deployment (Standalone or Resource Manager)

Test 2: Submit a Job Using Folder Attendant

Before You Begin

If you completed Test 1: Submit a Job Using File Job Submission, delete the media files from the \\Resource_Manager_IP_Address\media and \\Resource_Manager_IP_Address\output folders.

Procedure


Step 2 Add a directory for the Folder Attendant to monitor:

a. From the Toolbox, select Folder Attendant.

b. From the Directory drop-down menu, select Add. The Directory fields display on the Folder Attendant Administration page.

c. In the Directory Path field, enter \\Resource_Manager_IP_Address\media and complete other fields as needed.

Step 3 Add a watch for the directory:

a. From the Toolbox, click Folder Attendant.

a. Highlight the Directory for which you want to add a watch, and from the Watch drop-down, click Add. The Watch fields display on the Folder Attendant Administration page.

b. In the Watch Extensions field, enter MPEG-4.

c. In the Job Profile field, select Cable_Broadband.

d. Complete other fields as needed.

Step 4 From the Toolbox, select Monitoring > Job Status.

Step 5 Select any media file from your collection and copy it to the media directory (\\Resource_Manager_IP_Address\Media) folder.

Step 6 Watch the Job Status pane to make sure the job starts and completes.

Step 7 Browse to the \\Resource_Manager_IP_Address\Output folder, and locate the Sample.Cable_Broadband.Cable_Broadband.wmv file.

Step 8 If you created another version of the file in “Test 1: Submit a Job Using File Job Submission” section on page 4-24, check that the time stamp is current to verify that the file was recreated, and play the file.

Test 3: Verify a Licensed Feature is Enabled • To verify that the Live Ingest feature is enabled after you install a feature license, see the following

sections:

– Configuration Workflow for Cisco MXE 3500 Deployments with Live WMV IP Streaming, page 6-3

– Configuration Workflow for Cisco MXE 3500 Deployments with Live Flash 8 and H.264 IP Streaming, page 6-5

• To verify that the Speech to Text or Graphics Overlay feature is enabled after you install a feature license, see the following sections:


OL-21554-02

Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Testing a Cisco MXE 3500 Deployment (Standalone or Resource Manager)

– Configuration Workflow for Speech-to-Text Conversion, page 6-29

– Configuration Workflow for the Graphic Overlay Feature, page 6-30


OL-21554-02

Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Providing Documentation Feedback

Providing Documentation FeedbackTo provide feedback on this document, or to report an error or omission, you can use the online, Embedded Feedback form that appears on the upper-right side of the screen of each chapter in this document.

Alternatively, you can send feedback to [email protected].

You can access the most current version of this document at the following URL:


Obtaining Documentation and Submitting a Service RequestFor 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 an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.


OL-21554-02

mailto:[email protected]


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

Chapter 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Providing Documentation Feedback


OL-21554-02


C H A P T E R 5
Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration


• About the Resource Manager Deployment, page 5-2

• Guidelines for a Resource Manager Deployment, page 5-2

• How to Configure Cisco MXE 3500 Release 3.2 for a Resource Manager Deployment, page 5-3

• Accessing the Cisco MXE 3500 Web User Interface, page 5-3

• Accessing the Cisco MXE 3500 Tools, page 5-4

• Installing the License, page 5-4

• Configuring the Input and Output Media Directories, page 5-4

• Enabling System Administration E-mail Notifications, page 5-4

• Configuring the Host Settings (Resource Manager Only), page 5-4

• Confirming Service Accounts and Identifying Device Type, page 5-6

• Creating a Folder Attendant Directory and Watch, page 5-6

• Using Administrative Tools to Configure a Cisco MXE 3500 as a Resource Manager, page 5-6

• Testing a Cisco MXE 3500 Deployment, page 5-16

About the Cisco MXE 3500 Release 3.2Cisco MXE 3500 V2 Hardware

If you have received new Cisco MXE 3500 V2 appliances, then Release 3.2 Resource Manager and Resource Node software is preinstalled. You need only to complete network and admin user account configuration before you configure the software for your deployment. To configure network settings, see the procedures in the Quick Start Hardware Installation Guide for Cisco Media Experience Engine 3500 that shipped with your product or “Completing Initial Setup: Network Settings and Admin User Account Configuration” section on page 1-6; then, return to this chapter for deployment information.


If you are using the Cisco MXE 3500 V1 appliances, then the upgrade is required.


Chapter 5 Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration About the Resource Manager Deployment

To upgrade to Release 3.2, see Chapter 3, “Backing Up and Restoring Data for Cisco MXE 3500 Release 3.0 Upgrade to Release 3.2” and Chapter 1, “Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2.” Then, return to this chapter for deployment information.

About the Resource Manager DeploymentA Cisco MXE 3500 Resource Manager (RM or Resource Manager) deployment consists of one or more Cisco MXE 3500 devices running as a single group with one set of user accounts, job profiles, licensed features, and user interfaces. Resource Manager also provides user-management functionality, such as the ability to create users with specific roles and access to specific sections of the web UI.

There are two types of Cisco MXE 3500 devices in a Resource Manager deployment: a single Resource Manager and up to nine Resource Nodes.

• Resource Manager—Runs the Enterprise Control System (ECS), Configuration and Monitoring (CAM) service, and Local Control System (LCS) components on the same Cisco MXE 3500 device and is aware of all Resource Nodes in the group. The Resource Manager functions as a multinode manager by assigning various transcoding jobs to Resource Nodes, balancing the job loads uniformly based on the Capacity, Limit, and Expense values that you configure in the Resource Manager for each Resource Node.

• Resource Node—Runs only the LCS component and performs transcoding jobs. A single Resource Manager device can support up to 10 Resource Nodes, including itself as a one node. Be aware that because the Resource Manager also runs LCS, it functions also as a Resource Node and can process jobs.

Note For information about Cisco MXE 3500 components, see the User and Admin Guide for Cisco Media Experience Engine 3500 on Cisco.com, or click Help in the UI.

Guidelines for a Resource Manager DeploymentThe following configuration guidelines and restrictions apply to Resource Manager deployments:

• To obtain a license for a Resource Manager deployment that includes all the Resource Nodes you purchased, you must complete the product license registration, as described in the “Installing a License File” section on page 4-7.

• All paths that you configure on the Resource Manager must be UNC paths, not local paths, because all nodes must be able to read across the network.

Warning The built-in user account, mxe-service, is used to run the Cisco MXE 3500 application services and to access all configured UNC paths and shared media folders. Do not delete this account or change the password. Otherwise, the device will not work properly.

• We recommend that the Resource Manager and Resource Nodes remain on the same LAN because of the transfer of media files. If there are network delays, job timeouts and failures can occur.

• If a Resource Node fails, the Resource Manager transfers jobs to other available Resource Nodes without job loss; however, if the Resource Manager fails, no failover occurs.


OL-21554-02


Chapter 5 Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration How to Configure Cisco MXE 3500 Release 3.2 for a Resource Manager Deployment

• To enable a licensed feature, you must install the feature license on the Resource Manager. For information about deploying licensed features, see Chapter 6, “Deploying Licensed Features for Cisco MXE 3500.”

• Beginning with Release 3.1, all shared directories must be hosted under C:\shared. If you had shared folders or watch folders before to Release 3.1, you should copy them to C:\shared as subdirectories. Manually modify the affected setup, such as profiles, watch folders, and FTP configuration.

How to Configure Cisco MXE 3500 Release 3.2 for a Resource Manager Deployment

Release 3.2 requires the following mandatory configuration before using the system. Optional deployment configuration is identified, as well.

Mandatory Configuration


• Installing the License, page 5-4


• Enabling System Administration E-mail Notifications, page 5-4

• Configuring System Settings, page 5-10

• Configuring User Settings (Resource Manager Only), page 5-13

Optional Configuration

• Confirming Service Accounts and Identifying Device Type, page 5-6

• Creating a Folder Attendant Directory and Watch, page 5-6

• Testing a Cisco MXE 3500 Deployment, page 5-16

• Deploying Licensed Features for Cisco MXE 3500, page 6-1

Accessing the Cisco MXE 3500 Web User InterfaceFor information about accessing the user interfaces on the Resource Manager device, see the “Accessing the Cisco MXE 3500 Web User Interface (Standalone or Resource Manager)” section on page 4-3 in Chapter 4, “Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration.”

Note • You can access Cisco MXE 3500 user interface only on the Resource Manager device and not on Resource Nodes.

• A graphic with either “Resource Manager” or “Resource Node” is present on the desktop of each appliance to identify its Cisco MXE 3500 device type. We recommend that you do not remove the desktop background image. You can also determine the function of a node by its enabled services. See also: Confirming Service Accounts and Identifying Device Type (Standalone or Resource Manager), page 4-10.


OL-21554-02

Chapter 5 Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration Accessing the Cisco MXE 3500 Tools

Accessing the Cisco MXE 3500 ToolsYou use the Cisco MXE 3500 web UI for most maintenance and operational tasks. However, you complete a few other tasks by using other Cisco MXE 3500 tools, such as previewing preprocessor clips and creating or editing a QuickTime Encoder Profile.

For more information, see the “Accessing the Cisco MXE 3500 Tools (Standalone and Resource Manager)” section on page 4-4.

Installing the License To obtain the license for a Resource Manager deployment through the Cisco.com website, you must first register the Resource Manager device; then, register each Resource Node that you purchased by using the License Host ID address of the Resource Manager device. This registration process is required to associate the number of Resource Nodes that you purchased with the License Host ID address of the Resource Manager device; this association results in multiple licenses being sent to the e-mail address that you use for registration.

For Resource Manager deployments, you install the license only on the Resource Manager device. Resource Nodes do not require license installation, but you must register each node in the group to obtain a Resource Manager license that supports all the nodes that you purchased.

For more information, see the “Installing a License on Cisco MXE 3500 (Standalone or Resource Manager)” section on page 4-4.

Configuring the Input and Output Media Directories For the Resource Manager to manage input and output media, you must configure the input and output directories. For more information, see the “Configuring the Input and Output Media Directories (Standalone or Resource Manager)” section on page 4-7.

Enabling System Administration E-mail Notifications For information about configuring e-mail notifications on the Resource Manager device, “Enabling System Administration E-mail Notifications (Standalone or Resource Manager)” section on page 4-8.

Note We recommend that you configure an e-mail server so that you receive job completion or failure notifications.

Configuring the Host Settings (Resource Manager Only)Use this procedure to configure the Hosts settings for all the nodes in your Resource Manager deployment, including the Resource Manager device.

See also: Understanding Capacity, Expense, and Limit (Resource Manager Only), page 5-9 and Host Settings (Resource Manager Only), page 5-7.


OL-21554-02

Chapter 5 Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration Configuring the Host Settings (Resource Manager Only)

Before You Begin

1. Ensure that you change the TCP/IP Host name to a unique name on each Cisco MXE 3500 device. You will use these names during Hosts settings configuration.

2. Hosts settings configuration is required for both the Resource Manager device and each Resource Node.

3. Configure the Hosts settings for the Resource Manager device before you configure the settings for the Resource Nodes.

Procedure

Step 1 From the Toolbox, click Administration > Host. See also: User Settings (Resource Manager Only), page 5-13.

Step 2 Create a new Host:

a. From the Host Administration menu, click the arrow to the right of Host Options > New. The New Host pop-up displays.

Note Configure the Host settings for Resource Manager device first; then, configure the settings for the Resource Nodes.

b. In the Host Name field, enter the Host name. This name must be a valid computer name that you configured for the Resource Manager device or the Resource Node if you have configured the Resource Manager.

c. Enter the Capacity.

d. In the Temp Directory field, enter the UNC path for the temp folder on the Host that you configured in Step b., as follows: \\host_name\\temp.

e. Click Create. The new Host displays in the Hosts pane.

Step 3 Add workers to the Host that you created in Step 2:

a. Select each Worker that is assigned to the Host.

b. Click Permit or click Permit All.

Note The list of workers displayed is controlled by your license level. If you select the Permit All option, only all non-Live workers will be permitted. Live workers require manual entry of additional data.

Step 4 Configure the Limit, Expense, and live capture information for each worker:

a. Click each Worker and click Edit. The Edit worker pop-up displays.

b. Enter the Limit and the Expense.

c. For live captures, enter Capture Name, Capture Type, Video CH, and Audio CH.

d. Click Save.

Step 5 At the top of the page, click Apply Configuration.

Step 6 (Optional) Verify that the node is successfully added by selecting Monitoring > System Status from the Toolbox. Host names display in the first column of the System Status Monitor.


OL-21554-02

Chapter 5 Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration Confirming Service Accounts and Identifying Device Type

Step 7 Repeat Step 2 through Step 5 for each node that you purchased.

Confirming Service Accounts and Identifying Device TypeFor information about service accounts on the Resource Manager or Resource Node, see the “Confirming Service Accounts and Identifying Device Type (Standalone or Resource Manager)” section on page 4-10 in Chapter 4, “Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration.”

Note User mxe-service must have read/write access to all configured UNC paths and to IIS.

Tip You can determine the Cisco MXE 3500 device type (Resource Manager or Resource Node) by verifying which services are enabled.

Creating a Folder Attendant Directory and WatchFor information about creating a Folder Attendant directory and watch on the Resource Manager device, see the “Creating a Folder Attendant Directory and Watch (Standalone or Resource Manager)” section on page 4-11 in Chapter 4, “Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration.”

Note Make sure that the service accounts have appropriate access to the UNC path that you configure as the Directory Path for the Folder Attendant directory. See also: Confirming Service Accounts and Identifying Device Type (Standalone or Resource Manager), page 4-10.

Using Administrative Tools to Configure a Cisco MXE 3500 as a Resource Manager

The Administration section of the Toolbox allows you to configure the following settings:

• Host Settings (Resource Manager Only), page 5-7

• System Settings, page 5-10

• User Settings (Resource Manager Only), page 5-13

• Role Settings, page 5-14

• Profile Space Settings, page 5-15

• User Metadata Settings, page 5-16

• IP Capture (Live Streaming) Settings, page 5-16



OL-21554-02

Chapter 5 Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration Using Administrative Tools to Configure a Cisco MXE 3500 as a Resource Manager

Host Settings (Resource Manager Only)The Host Administration page allows administrators to configure Cisco MXE 3500 to work with computers on the network. Host is simply another word for the computer or system that runs Cisco MXE 3500. The Host Administration page is used to tell the Enterprise Control System (ECS) what the Hosts are capable of running (what the load capacity of the machine is and what software is installed).

Access this page from the Toolbox by clicking Administration > Host. Select a Host to display summary information about workers configured on that Host, delete a Host, or edit the configuration of a Host.

See also: System Settings, page 5-10 and Understanding Capacity, Expense, and Limit (Resource Manager Only), page 5-9

Figure 5-1 shows the Hosts settings.

Figure 5-1 Host Settings for Resource Manager Deployments

Table 5-1 Table 5-2 describes the Hosts settings.


OL-21554-02


Table 5-2 Hosts Settings and Descriptions for Resource Manager Deployments

Setting Description

Host This is the hostname or computer name of the Resource Manager or Resource Node device. The computer name and the Host name must match exactly.

Note The Resource Manager and each Resource Node in the group must have unique names.

Tip To verify the computer name of a Windows Server computer, right-click the My Computer icon on either your desktop or in your Start Menu, select Properties, then select the Computer Name. Alternately, type the hostname command at the command prompt to display the computer name.

Status Displays the status of the Host: Enabled or Disabled.

To change the status, right-click the Host or click Host Options, and select Enabled or Disabled.

Note If the status is disabled, jobs will not schedule on that Cisco MXE 3500 node.

Port TCP port that the LCS is listening on. The default is 3500.

Capacity Reflects a numeric value assigned for the total available processing capacity of the displayed Host.

Valid values are 0-99.

Capacity can be any number for a given Host, but it is important that all Hosts be numbered according to the same standards. For example, for one particular Host it will not matter if the total capacity is set at 5 or at 10. However, if there is another Host that has twice the capacity, the capacity of both Hosts should be listed in common terms. So, a Host that is twice as powerful would have a capacity of 10 if the first Host was 5, or 20 if the first Host was 10.

Capacity is directly related to processor capacity, but may also be affected by drive speed, network congestion, and other factors. All of the factors that affect the amount of work a particular Host can do efficiently should be considered when assigning a capacity value.

Note Numbers between 5 and 30 are typically best. Setting this to a high number > 30 can make the system status monitor hard to read.

See also: Understanding Capacity, Expense, and Limit (Resource Manager Only), page 5-9 and Figure 5-1, Host Settings for Resource Manager Deployments

Temp Directory (UNC Name)

Specifies the directory where temporary files and preprocessor output will be stored while the job is processing.

This must be a UNC path, not a local path, so that other Hosts will be able to access files written to this directory.

User mxe-service must also have read/write access to this directory.

Note Unless the Preprocessor box in the Output tab is checked to specify that preprocessor files should be saved, files written to the Temp Directory will be deleted automatically when encoding has completed.


OL-21554-02


Understanding Capacity, Expense, and Limit (Resource Manager Only)

Note For information about Cisco MXE 3500 components, such as workers and ECS, see the User Guide for Cisco Media Experience Engine 3500 on Cisco.com, or click Help in the UI.

See also: Host Settings (Resource Manager Only), page 5-7.

The ECS uses capacity and expense to assign tasks to specific workers on specific Hosts to keep jobs moving through the encoding process efficiently and to ensure that no single Host is over-burdened, thereby preventing bottlenecks.

Worker Status

• Green checkmark: Indicates that the worker listed to the right is configured to run on the displayed Host and that it is currently online and available to process tasks.

• Red X: Indicates either:

– The worker listed to the right is configured to run on the displayed Host but is currently offline and cannot be contacted by the ECS.

or

– The worker is not enabled or configured.

Worker Displays a list of all workers that have been configured to run on the displayed Host.

Licensed Indicates the number of concurrent instances of this worker type (example: prefilter, encoder, distribution) that can be running on the system (all nodes controlled by that ECS). This value is defined in the Cisco MXE 3500 license file.

Limit Displays the maximum number of a particular worker that can be run simultaneously on the displayed Host.



Expense The expense of a worker is expressed as a portion of Host capacity.



Capture Name

This setting is not available in Cisco MXE 3500 Release 3.1.

Defines the name associated with a live capture worker. Because Hosts can have more than a single video capture card and can be configured to run more than one Live capture worker, the Capture Name is required in order to identify the specific capture card used by the worker. This is only displayed for Live capture workers.

Capture Type This setting is not available in Cisco MXE 3500 Release 3.1.

Type of capture card (DV, DVCAM, AJA-SDI, Custom, etc.). Selection of a non-custom value will predefine the audio and video channel.

Video CH/Audio CH

This setting is not available in Cisco MXE 3500 Release 3.1.

Displays Video Channel and Audio Channel for each Live-capture worker.

Table 5-2 Hosts Settings and Descriptions for Resource Manager Deployments (continued)


OL-21554-02



Capacity is directly related to processor capacity but may also be affected by drive speed, network congestion, and other factors. All the factors that affect the amount of work a particular Host can do efficiently should be considered when assigning a capacity value.

Capacity can be any number for a given Host, but all Hosts should be numbered by using the same standards. For example, it does not matter that the total capacity is set to 5 or 10 for one particular Host. However, if there is another Host that has twice the capacity, then the capacity of both Hosts should be listed in common terms. That is, a Host that is twice as powerful should have a capacity of 10 if the first Host is 5 or a capacity of 20 if the first Host is 10. In practical terms, numbers between 5 and 30 are better.

The expense of a worker is expressed as a portion of Host capacity, as shown in the following examples:

Expense will be different for different types of workers, and the processing power that is required by a particular type of worker may not always be the same. For example, MPEG encoding is more labor-intensive than Microsoft encoding, so an MPEG worker is given a higher expense than a Microsoft worker.

Limit is used with Capacity and Expense to accommodate expense differences. For example, running one particular type of worker takes a certain expense amount, and running two may require double that amount. However, when a certain number is exceeded, the efficiency may degrade: Everything is fine until the fourth instance of the same worker is triggered. After this, the Host bogs down and performance suffers. Setting the Limit for this particular worker to three will prevent the ECS from triggering the fourth worker even if there is sufficient capacity to accommodate the normal expense of the fourth instance. Because the expense would dramatically increase if the fourth worker were triggered, setting the Limit to three creates a threshold for the normal expense of a worker and sets an upper limit on the number of instances that can run at the same time.

System SettingsThe Administration section of the Toolbox is used to configure the Cisco MXE 3500 Resource Manager device. You must have Admin Tools permission to configure these settings.

Access this page from the Toolbox by clicking Administration > System.

The System page is made up of the following sections:

• Input Section (Resource Manager Only), page 5-11

• Output Section (Resource Manager Only), page 5-12

• General Settings Section, page 5-13

• Status Settings Section, page 5-13

• Data Purging Section, page 5-13

• Audio Capture Section, page 5-13

Host CapacityPortion of Total Processing Power Required Worker Expense

100 Half 50

6 Half 3

9 One third 3

6 One third 2


OL-21554-02


Input Section (Resource Manager Only)

Note Directory values must be UNC paths to a network share.

Figure 5-2 shows Input section settings.

Figure 5-2 Input Settings

Table 5-3 describes the Input section settings.

Table 5-3 Input Settings and Descriptions for Resource Manager Deployments

Setting Description

Bumper/Trailer Directory

Defines the location of files that can be used as bumpers or trailers to clips encoded with the Cisco MXE 3500. The Bumper/Trailer Directory controls the directory path where the Cisco MXE 3500 searches for files displayed in the Bumper Source and Trailer Source fields in the Preprocessing Profile page.

Directory values must be UNC paths to a network share.

The Bumper/Trailer Directory location must be accessible to all hosts.

Common Directories

Defines the directories where media files will be stored. Multiple directories can be defined. A semi-colon is used to separate directory entries.


Media Directory Defines the directory where media files that will be submitted to the Cisco MXE 3500 are stored. The Media Directory controls the directory path where the Cisco MXE 3500 searches for files displayed in the Source box on the File Submission page.

The Media Directory value can be entered either as a UNC path to a network share or to a mapped drive in the case of a deployment using a storage area network (SAN) or a single node deployment. The Media Directory location must be shared and accessible to all Hosts.


Profile Directory Defines the default path the ECS will use to search for Job Profiles when processing a submitted job.


OL-21554-02


Output Section (Resource Manager Only)

Output Directories define the location the Cisco MXE 3500 will use to save files of each encoding format supported by the licensing levels of your Cisco MXE 3500 system. Encoded files will be saved to the defined directories when either no Distribution > Output Profile is included in the Job Profile or when the checkbox in the Save Local File section of the Output Profile has been checked.

Note All directory values must be a UNC path to a network share.

Figure 5-3 shows the Output section settings.

Figure 5-3 Output Settings

Valid Input Extensions

Defines the list of valid extensions for files in Common Directories. Only files with extensions listed in this field will be displayed in the Selection List window in the Input section of the File Job Submission form. A semi-colon is used to separate file-extension entries.

Watermark Directory

Defines the location of files that can be used as watermarks for clips encoded with the Cisco MXE 3500. The Watermark controls the directory path where the Cisco MXE 3500 searches for files displayed in the Source drop-down in the Watermark section of the Preprocessing Profile page.

Directory values must be UNC paths to a network share. The Watermark Directory location must be accessible to all hosts.

Table 5-3 Input Settings and Descriptions for Resource Manager Deployments


OL-21554-02


General Settings Section

For information about General Settings configuration on the Resource Manager device, see the “General Settings Section (Standalone or Resource Manager)” section on page 4-18 in Chapter 4, “Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration.”

Status Settings Section

For information about Status Settings configuration on the Resource Manager device, see the “Status Settings Section (Standalone or Resource Manager)” section on page 4-18 in Chapter 4, “Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration.”

Data Purging Section

For information about Data Purging Settings configuration on the Resource Manager device, see the “Data Purging Section (Standalone or Resource Manager)” section on page 4-19 in Chapter 4, “Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration.”

Audio Capture Section

For information about Audio Capture Settings configuration on the Resource Manager device, see the “Audio Capture Section (Standalone or Resource Manager)” section on page 4-20 in Chapter 4, “Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration.”

User Settings (Resource Manager Only)

Note This section describes only the user management feature for the Resource Manager that you can access with the predefined admin user. For a list of all system user accounts, see the “Administrative User Accounts (Standalone or Resource Manager)” section on page 4-21 in Chapter 4, “Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration.”. Upon receipt of your system, the predefined admin user is the only user who can perform Folder Attendant administrative tasks such as creating users, assigning roles, deleting users, and denying or removing user permissions. Do not delete the predefined admin user until you have created at least one new admin user.

The User Administration page is used by administrators to set user access and permissions.

Access this page from the Toolbox by clicking Administration > User.

The top pane of User Administration displays users that have been created. The lower pane displays the permissions for each user. The New or Edit Users pop-up allows you to create and modify system users.

Table 5-4 describes the User settings.


OL-21554-02


Role SettingsEach Cisco MXE 3500 user is assigned a role that controls their level of access to the various system features.

Access the Role Administration page from the Toolbox by clicking Administration > Role.

The top pane of the Role Administration page displays roles that have been created. The lower pane displays the permissions for each role.

There are three predefined roles:

• admin: Set up with permission to access all features

• operator: Set up with permission to access Job Profile editing but not task profile editing features

• user: Set up with permission to access all features, except administrative

The New or Edit Role pop-up, shown in Figure 5-4, allows you to create and modify system users.

Figure 5-4 Role Settings

After creating a role, the System Administrator sets permissions for that role. Each role is allowed or denied permission to use the following Cisco MXE 3500 features:

• Admin Tools: Provides access to the Cisco MXE 3500 administrative tools

• Folder Attendant: Provides access to Folder Attendant

Table 5-4 User Settings and Descriptions

Setting Description

User Name From the menu bar, click New, or select the user and then click Edit. The New or Edit User pop-up displays.

Enter a name for the user.

Password Enter a password for the new user.

Confirm Password Re-enter the password to confirm it.

First Name Enter the first name of the user.

Last Name Enter the last name of the user.

E-mail Enter the e-mail address of the user.

Role Select the role from the drop-down menu. The role defines the level of access the user has to Folder Attendant functions.

Roles are defined at the time of deployment and are normally: Administrator and User.


OL-21554-02


• Job Profile Editing: Provides access to Job Profile editing functionality

• Monitoring: Provides access to Monitoring functionality

• Monitoring (Advanced): Allows a user to reschedule, stop, delete, etc.

• Reporting: Provides access to reporting functionality

• Submission: Provides access to submission tools

• Task Profile Editing: Provides access to profile editing functionality

The permissions for a selected role are displayed at the bottom of the Role Administration page.

Table 5-5 describes the columns in the permissions table.

The red X indicates that permissions for that feature are denied, and the green check mark indicates that the selected user has permissions to access the feature.

Profile Space SettingsThe Profile Administration page allows you to manage multiple profile directories within the system. The Cisco MXE 3500 is shipped with a single profile directory. The initial database setting for profiledir is:

C:\Program Files\Cisco\Media Experience Engine\profiles

The Cisco MXE 3500 uses the system setting-configured profile directory to access the list of Job Profiles. However, you may want to maintain separate profile directories for separate groups or for separate customers.

You can create as many Profile Spaces as you need, but the Cisco MXE 3500 will check to see that each profile directory exists at the time of creation.

Your Cisco MXE 3500 session links to one Profile Space at a time, thereby determining the profiles that you can view from the Profile Browser.

Access the Profile Administration page from the Toolbox by clicking Administration > User.

Tip You can change your working Profile Space at any time by clicking Tools > Select Profile Space.

The New or Edit Profile Space pop-up, shown in Figure 5-5, allows you to create and modify profile spaces.

Table 5-5 Role Settings and Descriptions

Setting Description

Default Shows the default value for the permissions that are shipped with the Cisco MXE 3500.

Role Shows the permissions set for the Role. Permissions set for the role override the Default permissions. The Role permissions specified in this column are set from the Role Administration page.

User Shows the permissions set for the selected user. Permission set for the user override the Role permissions.

Allow The actual permissions set for the selected user.


OL-21554-02

Chapter 5 Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration Testing a Cisco MXE 3500 Deployment

Figure 5-5 Profile Space Settings


User Metadata SettingsThis User Metadata Administration page allows you to create custom name/value pairs that can be submitted with each job (and each task in the job). This custom metadata is returned in detailed job status including the HTTP POST job-status XML. This metadata (if submitted) is also stored in the database for each job and can be used for reporting purposes (like tracking which organization submitted which jobs) or (via HTTP POST) where it is passed back to other systems (like Velocity).

For information about User Metadata settings configuration on the Resource Manager device, see the “User Metadata Settings” section on page 4-22 in Chapter 4, “Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration.”

IP Capture (Live Streaming) SettingsCisco MXE 3500 enables ingest of Live MPEG2 Transport streams over UDP/IP with management, configuration, and status that enables general use of this feature. IP captures are limited to transport streams with MPEG2 video and AC3/Layer2/AES3 audio essences.

The IP Capture Configuration page is used by administrators to add, edit, or delete an IP capture source.

For information about IP Capture settings configuration on the Resource Manager device, see the “IP Capture (Live Streaming) Settings (Standalone or Resource Manager)” section on page 4-22.

Testing a Cisco MXE 3500 DeploymentFor information about tests that you can perform to verify that your system has been correctly deployed, see the “Testing a Cisco MXE 3500 Deployment (Standalone or Resource Manager)” section on page 4-24.

Table 5-6 Profile Space Settings and Descriptions

Setting Description

Name Enter a unique name.

Directory Enter a verifiable directory.


OL-21554-02


C H A P T E R 6
Deploying Licensed Features for Cisco MXE 3500
Revised: June 8, 2011, OL-21554-02


• Live Streaming (IP Capture) Feature, page 6-1

• Speech-to-Text and Graphics Overlay Features, page 6-27

• Simplified User Interface Feature, page 6-32

Live Streaming (IP Capture) FeatureThe Live Streaming (IP capture) feature enables the Cisco MXE 3500 to ingest live feeds and repurpose the live content so that it can be viewed on a variety of endpoints.

Activation To use this feature, you must purchase and install the feature license on the standalone Cisco MXE 3500 or the Resource Manager device.


• Required Components for the Live Streaming Feature, page 6-1

• Live WMV IP Streaming Deployments, page 6-3

• Live Flash 8 and H.264 IP Streaming Deployments, page 6-4

• Live WMV Stream from Cisco TelePresence Content Server to Cisco MXE 3500 Deployments, page 6-6

• Live WMV Stream to Cisco Digital Signs Deployments, page 6-23

Required Components for the Live Streaming FeatureIn addition to a Live Streaming feature license, the following components are required:

1. Ingest (Input), page 6-2

2. Job Profile (Transcode), page 6-2

3. Distribution (Output), page 6-2


Chapter 6 Deploying Licensed Features for Cisco MXE 3500 Live Streaming (IP Capture) Feature

Note See the Release Notes for Cisco MXE 3500 for information about supported ingest formats and the maximum number of supported streams.

Ingest (Input)

The Cisco MXE 3500 can ingest MPEG-2 single- or multi-program streams or both from a multicast network through Protocol Independent Multicast (PIM) enabled routers. Incoming streams must have the following characteristics:

• MPEG-2 TS packaging

• MPEG-2 encoded payload

• AC3 or Layer 2 audio

• UDP/IP transport (RTP is not supported)

• (Optional) EIA 608 and 708 closed captions

The following sources can provide streamed content:

• Cable or satellite feeds that are groomed and distributed through a head-end setup

• Direct output(s) from MPEG-2 encoders that comply with Cisco MXE 3500 input requirements

Job Profile (Transcode)

The Cisco MXE 3500 can transcode incoming MPEG-2 TS to Windows Media Video (WMV), Flash 8, or H.264 streaming formats in real time. Transcoding (file conversion) requires a suitable job profile in Cisco MXE 3500.

Distribution (Output)

The Cisco MXE 3500 can perform limited HTTP streaming. We recommend that you deploy a separate streaming server for RTSP streaming and an optimized stream distribution network for efficient streaming to remote clients over WAN. Otherwise, the Cisco MXE 3500 performance and capacity will be degraded and impair the streaming experience.

We recommend the following streaming servers:

• Windows Media Video (WMV)—Windows Media Streaming Server contained in Microsoft Windows 2008 Server Enterprise Edition

• Flash 8 and H.264—Adobe Flash Media Server (FMS)

We recommend the following stream distribution network solutions:

• WMV—Cisco WAN Application Acceleration Solution (WAAS)

• Flash8 and H.264—Commercial Content Delivery Network (CDN) services available from the following sources:

– Akamai

– Limelight

– Internap


OL-21554-02

http://www.cisco.com/en/US/products/ps9892/prod_release_notes_list.html


Live WMV IP Streaming Deployments • Network Design for Cisco MXE 3500 Deployments with Live WMV IP Streaming, page 6-3\

• Configuration Workflow for Cisco MXE 3500 Deployments with Live WMV IP Streaming, page 6-3

Network Design for Cisco MXE 3500 Deployments with Live WMV IP Streaming

Figure 6-1 shows an example solution network for a Cisco MXE 3500 deployment with WMV IP streaming and Cisco Wide Area Application Services (WAAS).

Figure 6-1 Example Solution Network for WMV IP Streaming Using Cisco WAAS

Configuration Workflow for Cisco MXE 3500 Deployments with Live WMV IP Streaming

Note For information about using the web UI, see the User and Admin Guide for Cisco MXE 3500.

The preprocessor and encoder profile settings are the same as file-to-file transcoding.

1. If you have a Resource Manager deployment with more than one Cisco MXE 3500 host, restrict all Windows Media encoding to a single Cisco MXE 3500.

For each Cisco MXE 3500 host—other than the one host that you want to perform all Windows Media encoding— remove the following workers:

• microsoftAudioStream

• microsoftStream

See also: “Removing Workers from a Host” in the user guide.

Cisco WAASCentral

Manager

Cisco WAE 612

Cisco 574WAE

VLAN

Client PULLsStream

Client PULLsStream

Client PULLsStream

Multicast VideoStream

CiscoMXE3500

Windows2008

EnterpriseServer

StreamingServerPULLsStream

LAN

2777

92

WAN

WAAS WANAcceleration

V

Client

Client

Client


OL-21554-02


http://preview.cisco.com/en/US/products/ps9892/products_user_guide_list.html


2. Create a new Webcast Profile. Webcast Profiles are used to define the parameters for streaming encoded output live to the Internet.

a. Create a new Profile.

b. Choose Profile Class: Distribution and Webcast.

3. Configure the following Webcast Profile settings:

• Profile: Select the Windows encoder profile that is part of the job.

• Server: Enter the Cisco MXE 3500 IP address.

• Port: Enter a port number that is not in use.

• Filename: Enter a filename for the stream. This field is required. Because this setting is used to generate the name of the file that is streamed, enter a meaningful filename, CNNStream for example.

Figure 6-2 Example Stream Configuration: WMV streaming

4. Add the Webcast Profile to a Job Profile under the Distribution: Webcast setting.

5. Submit the Job Profile as a live job on the Submission > Live page.

6. On the Windows Media streaming server, add a new publishing point. Enter the Cisco MXE 3500 IP address for the encoder and the port number from Step 3.

7. For distribution setup, configure Cisco WAAS as described in the Microsoft Windows Server on Cisco WAAS Deployment Guide at the following URL: http://www.cisco.com/en/US/products/ps6870/prod_white_papers_list.html

8. On a client PC, open the Windows Media Player and enter the URL, as follows: mms: //streaming server/publishing_point.

Live Flash 8 and H.264 IP Streaming Deployments • Network Design for Cisco MXE 3500 Deployments with Live Flash 8 and H.264 IP Streaming,

page 6-4\

• Network Design for Cisco MXE 3500 Deployments with Live Flash 8 and H.264 IP Streaming, page 6-4

Network Design for Cisco MXE 3500 Deployments with Live Flash 8 and H.264 IP Streaming

Figure 6-3 shows an example solution network for a Cisco MXE 3500 deployment with Flash 8 IP streaming and a content distribution network (CDN).


OL-21554-02

http://www.cisco.com/en/US/products/ps6870/prod_white_papers_list.html


Figure 6-3 Example Solution Network for Flash 8 and H.264 IP streaming Using CDN

Configuration Workflow for Cisco MXE 3500 Deployments with Live Flash 8 and H.264 IP Streaming

Note For information about using the web UI, see the User Guide for Cisco MXE 3500.

Preprocessor and encoder profile settings remain the same as file-to-file transcoding.

1. Create a new Webcast Profile. Webcast Profiles are used to define the parameters for streaming encoded output live to the Internet.


b. Choose Profile Class: Distribution and Webcast.

2. Configure the following Webcast Profile settings:

• Profile: Select the Flash 8 or H.264 encoder profile that is part of the job.

• Server: Enter the Flash streaming server IP address, such as rtmp://Streaming Server IP address/publishing point.

• Port: Enter 80 or 1935.

• Filename: Enter a filename for the stream. This field is required. Because this setting is used to generate the name of the file that is streamed, enter a meaningful filename, CNNStream for example.

VCDN

VLAN

Client PULLsStream

Client PULLsStream

Client PULLsStream

Multicast VideoStream

CiscoMXE3500

AdobeFMS

StreamingServer

PUSHesStream toStreaming

Server

LAN

2777

91

Client

Client

Client


OL-21554-02



Figure 6-4 Example Stream Configuration for Flash 8 Streaming

3. Add the Webcast Profile to a Job Profile under the Distribution: Webcast setting.

4. Submit the Job Profile as a live job on the Submission > Live page.

5. On the Flash streaming server, add the server publishing point.

6. On a client PC, open a Flash player that can support RTMP, and enter the URL, as follows: rtmp://StreamingServerIPaddress/live/FileName.

Live WMV Stream from Cisco TelePresence Content Server to Cisco MXE 3500 Deployments

You can configure the Cisco TelePresence Content Server (Content Server) to record and stream WMV to a Cisco MXE 3500, which will transcode to H.264 and multicast to Cisco DMPs.

This section provides instructions to configure the Content Server for recording and automatically unicasting or multicasting a WMV stream for Cisco MXE 3500 Release 3.2 to transcode to H.264 for digital signage solution.

• Prerequisites, page 6-6

• Content Server Configuration for a WMV Unicast Stream, page 6-7

• Content Server Configuration for a WMV Multicast Stream, page 6-14

Note The figures in this document are provided as examples only. See the Content Server documentation on Cisco.com for configuration details, such as valid characters and parameters.

Prerequisites

• Cisco MXE 3500 software requirements

– Release 3.2

• Cisco TCS software requirements:

– TCS Release 5.0 or later


OL-21554-02

http://www.cisco.com/en/US/products/ps11347/tsd_products_support_series_home.html


Content Server Configuration for a WMV Unicast Stream

• Configuring the Publishing Point for a WMV Unicast Stream, page 6-7

• Configuring the Media Server for a WMV Unicast Stream, page 6-7

• Configuring the Recording Alias and Template for a WMV Unicast Stream, page 6-8

• Testing the Configuration for a WMV Unicast Stream, page 6-12

Configuring the Publishing Point for a WMV Unicast Stream

Before You Begin

Make sure that you have administrator login credentials for the Content Server.

Step 1 Open a Remote Desktop session and log in to the Content Server.

Step 2 Click Start > All Programs > Administrative Tools >Windows Media Services.

Step 3 From Windows Media Services window, navigate to Publishing Points > TCSUnicastTemplate.

Step 4 Right-click TCSunicastTemplate, select Duplicate.

Step 5 Enter mxe-unicast as the new Publishing Point Name. You have now created a new static publishing point called mxe-unicast.

Step 6 Go to the “Configuring the Media Server for a WMV Unicast Stream” section on page 6-7.

Configuring the Media Server for a WMV Unicast Stream

Step 1 Open up a browser session and log in as administrator to the Content Server.

Step 2 Click the Management tab.

Step 3 Click Recording Setup > Media Server Configurations.

Step 4 Click + Add Windows Media Streaming Server Configuration.

Step 5 Enter the unique name.

Step 6 In the Server Settings section, click Support Live Unicast Streaming. The Live Unicast Streaming Settings section displays below the Server Settings section.


OL-21554-02


Figure 5 Media Server Configuration for a Unicast Stream

Step 7 In the Live Unicast Streaming Settings section, enter the following information:

a. For Server Push port, enter 8080.

b. For the Publishing Point, click Use Existing.

c. Enter the new publishing point mxe-unicast.

d. Click Save.

Step 8 Go to the “Configuring the Recording Alias and Template for a WMV Unicast Stream” section on page 6-8.

Configuring the Recording Alias and Template for a WMV Unicast Stream

Step 1 Click on Management tab.

Step 2 Click Recording Setup > Recording Aliases.

Step 3 Click + Add Recording Alias.


OL-21554-02


Figure 6 Add/Edit Recording Alias

Step 4 On the Add recording alias page, enter the following information:

a. In the Recording alias section, enter a Name for the recording alias, such as TCS-3500 Live WMV, and choose Personal for the Recording alias type. Make sure that the System Administrator owns this recording alias.

b. In the dialing properties section, enter the H323ID, e164alias, SIP URI, and SIP display name.

c. Click Save.

Step 5 In the Recordings Settings section, click Add at the end of the Template line. The add template window appears.


OL-21554-02


Figure 7 Add/Edit Template: Name and Outputs to View Configuration


OL-21554-02


Figure 8 Add/Edit Template: On Demand and Live Stream Configuration

Step 6 On the Add a template page, enter the following information:

a. In the Template section, enter a template name, such as TCS-3500 Live Template, and check Viewable in the Content Server web interface.

b. In the Outputs to view in the Content Server web interface section, choose Switching, Windows Media as the On-demand Format, and Large as the Size.

c. In the On demand media server configuration settings section, select Local Windows Media Streaming Server in the Windows Media dropdown list.

d. In the Live Stream section, click the Live Stream box to enable Live streaming and then select Windows Media as the Format and Large as the Size.

e. In the Live media server configuration settings section, select mxe-unicast as the media server configuration. This is the media server that you created in the “Configuring the Media Server for a WMV Unicast Stream” section on page 6-7.

f. Click Save and then click Return. The Recording Alias page displays the TCS-3500 WMV Live recording alias that was being configured before creating a template.

Step 7 Make sure the newly added template is selected in the Template dropdown list.

Step 8 Check Show countdown before recording option.

Step 9 In the Default recording information, enter a name and a description.

Step 10 In the Default recording permissions section, check Automatically publish finished recordings and Allow access to all users, including guests.

Step 11 Scroll to the top or bottom and click Save and then click Return.


OL-21554-02


Step 12 Go to “Testing the Configuration for a WMV Unicast Stream” section on page 6-12.

Testing the Configuration for a WMV Unicast Stream

Step 1 Create a recording.

a. Open up a browser session and log in as administrator to the Content Server

b. Click on Management tab.

c. Click on Recording Setup > Create Recording.

Figure 9 Create Recording

d. In Create Recording section, select the recording alias that you created for unicast.

e. Enter a dial number. This can be a conference bridge or a endpoint linking to a video source player.

f. Click +Advanced Call Settings and choose the appropriate values for bandwidth and call type.

g. Click Place call button.

Step 2 Make sure that the publishing point has started automatically.

a. Open a Remote Desktop session and log in to the Content Server.

b. Launch Windows Media Services window, and verify that the unicast publishing point has started.


OL-21554-02


Figure 10 Publishing Point is Started

Step 3 Make sure that you can view the stream from an external device.

a. From your local PC, launch Windows Media Player.

b. Press Ctrl-U to open Open URL dialog.

c. Enter the Content Server unicast publishing point URL as follows: mms://tcs-ip-or-hostname/<publishingpoint-name>, such as mms://tcs-ip-or-hostame/mxe-unicast

Step 4 Verify the video quality.

a. Press Alt to bring up the menu bar for Windows Media Player, select View/Statistics.

b. Click the Advanced tab and then make sure that there is no packet loss and the video quality is good.


OL-21554-02


Figure 11 Media Player Statistics

Content Server Configuration for a WMV Multicast Stream

• Configuring the Publishing Point for a Multicast Stream, page 6-14

• Configuring the Media Server for a Multicast Stream, page 6-16

• Configuring the Recording Alias and Template for a Multicast Stream, page 6-17

• Testing the Configuration for a Multicast Stream, page 6-21

Configuring the Publishing Point for a Multicast Stream

Before You Begin

Make sure that you have administrator login credentials for the Content Server.

Step 1 Open a Remote Desktop session and log in to the Content Server.

Step 2 Click Start > All Programs > Administrative Tools >Windows Media Services.

Step 3 From Windows Media Services window, navigate to Publishing Points > TCSmulticastTemplate.

Step 4 Right-click TCSmulticastTemplate, select Duplicate.


OL-21554-02


Figure 12 Duplicate TCSmulticast Template

Step 5 Enter mxe-multicast as the new Publishing Point Name. You have now created a new static publishing point called mxe-multicast.

Step 6 Select the newly added multicast publishing point and then select the Properties tab.


OL-21554-02


Figure 13 Enable Buffering for a Multicast Publishing Point

Step 7 From the Category pane, select Networking

Step 8 From Property pane, select Enable buffering and then double-click Enable buffering to bring up the Enable Buffering Properties dialog box.

Step 9 Choose Buffer content (reduces startup latency for clients).

Step 10 Click OK.

Step 11 Go to the “Configuring the Media Server for a Multicast Stream” section on page 6-16.

Configuring the Media Server for a Multicast Stream

Step 1 Open up a browser session and log in as administrator to the Content Server.

Step 2 Click the Management tab.

Step 3 Click Recording Setup > Media Server Configurations.

Step 4 Click + Add Windows Media Streaming Server Configuration.


OL-21554-02


Figure 14 Media Server Configuration for a Multicast Stream

Step 5 Enter the name mxe-multicast.

Step 6 In the Server Settings section, click Support Live Multicast Streaming. The Live Multicast Streaming Settings section displays below the Server Settings section.

Step 7 In the Live Multicast Streaming Settings section, enter the following information:

a. For Server Push port, enter 8080.

b. For the Publishing Point, click Use Existing.

c. Enter the new publishing point mxe-multicast.

d. Click Save.

Step 8 Go to “Configuring the Recording Alias and Template for a Multicast Stream” section on page 6-17.

Configuring the Recording Alias and Template for a Multicast Stream

Step 1 Click on Management tab.

Step 2 Click Recording Setup > Recording Aliases.

Step 3 Click + Add Recording Alias.


OL-21554-02


Figure 15 Add/Edit Recording Alias

Step 4 On the Add recording alias page, enter the following information:

a. In the Recording alias section, enter a Name for the recording alias, such as TCS-3500 Live WMV, and choose Personal for the Recording alias type. Make sure that the System Administrator owns this recording alias.

b. In the dialing properties section, enter the H323ID, E.164alias, SIP URI, and SIP display name.

c. Click Save.

Step 5 In the Recordings Settings section, click Add at the end of the Template line. The add template window appears.


OL-21554-02


Figure 16 Add/Edit Template: Name and Outputs to View Configuration


OL-21554-02


Figure 17 Add/Edit Template: On Demand and Live Stream Configuration

Step 6 On the Add a template page, enter the following information:

a. In the Template section, enter a template name, such as TCS-3500 Live Template, and check Viewable in the Content Server web interface.

b. In the Outputs to view in the Content Server web interface section, choose Switching, Windows Media as the On-demand Format, and Large as the Size.

c. In the On demand media server configuration settings section, select Local Windows Media Streaming Server in the Windows Media dropdown list.

d. In the Live Stream section, click the Live Stream box to enable Live streaming and then select Windows Media as the Format and Large as the Size.

e. In the Live media server configuration settings section, select mxe-multicast as the media server configuration. This is the media server that you created in the “Configuring the Media Server for a Multicast Stream” section on page 6-16.

f. Click Save and then click Return. The Recording Alias page displays the TCS-3500 WMV Live recording alias that was being configured before creating a template.

Step 7 Make sure the newly added template is selected in the Template dropdown list.

Step 8 Check Show countdown before recording option.

Step 9 In the Default recording information, enter a name and a description.

Step 10 In the Default recording permissions section, check Automatically publish finished recordings and Allow access to all users, including guests.

Step 11 Scroll to the top or bottom and click Save and then click Return.


OL-21554-02


Step 12 Go to “Testing the Configuration for a Multicast Stream” section on page 6-21.

Testing the Configuration for a Multicast Stream


a. Open up a browser session and log in as administrator to the Content Server.

b. Click the Management tab.

c. Click Recording Setup > Create Recording.

Figure 18 Create Recording

d. In Create Recording section, select the recording alias that you created for multicast.

e. Enter a dial number. This can be a conference bridge or a endpoint linking to a video source player.





b. Launch Windows Media Services window, and verify that the multicast publishing point has started.


OL-21554-02



Step 3 Make sure that you can view the stream from an external device.

a. Make sure that your network is multicast enabled and then from a PC on the multicast enabled network, launch Windows media player.

b. Press Ctrl-U to open Open URL dialog.

c. Enter the Content Server multicast publishing point URL as follows: http://tcs-IP-or-hostname/tcs/data/_tcs-multicast-publishing-point-name.nsc

Figure 20 Multicast Publishing Point URL

Step 4 Verify the video quality.

a. Press Alt to bring up the menu bar for Windows Media Player, select View/Statistics.

b. Click the Advanced tab and then make sure that there is no packet loss and the video quality.


OL-21554-02


Figure 21 Media Player Statistics

Live WMV Stream to Cisco Digital Signs DeploymentsCisco MXE 3500 expands the Cisco Digital Media Suite solution and adds additional digital signage capabilities. The MXE 3500 ingests live video streams from virtually any video device or endpoint and delivers direct to digital signs, transforming a static digital sign into a portal for live event coverage, employee training sessions, inter-organization communications, public safety alerts and more.

This section describes how to configure Cisco MXE 3500 for live WMV ingest and use the Content Server to send the live MPEG-2 TS to a Cisco Digtial Signs (Digital Media Player).

Note For information about Cisco Digital Signs configuration, see the Guide to Documentation for Cisco Digtal Media Suite at http://www.cisco.com/en/US/products/ps6681/products_documentation_roadmaps_list.html

• Configuring an IP Capture Source on Cisco MXE 3500, page 6-24

• Creating a Job Profile on Cisco MXE 3500, page 6-24

• Starting the Multicast Stream on the Content Server, page 6-25

• Submitting the Live Job on Cisco MXE 3500, page 6-26

• Verifying the Live Job, page 6-27


OL-21554-02

http://www.cisco.com/en/US/products/ps6681/products_documentation_roadmaps_list.html


Configuring an IP Capture Source on Cisco MXE 3500

Procedure

Step 1 From the Toolbox, expand Administration, and click IP Capture.

Step 2 Click New.

Figure 22 Create IP Capture Source Pop-up

Step 3 Enter the following information:

• Name—Enter a unique name.

• Protocol—Choose HTTP.

• Address—Enter the URL for the unicast stream or the path for the .nsc file for the multicast stream.

• Port—Enter the multicast port.

Step 4 Click Create.

Creating a Job Profile on Cisco MXE 3500

Procedure

Step 1 From the Toolbox, expand Profile Management, and click New Profile. The New Profile pop-up displays.

Step 2 From the Profile Class drop-down, select Job, and click the New Profile button. The New Job Profile page displays.

Step 3 Expand the Preprocessing section, and from the drop-down, select a Preprocessor Profile. Preprocessor profile settings remain the same as file-to-file transcoding.

Step 4 Expand the Encoding section, and choose an H.264 profile. Define the following parameters as necessary:

• FPS

• Bitrate

• Dimensions


OL-21554-02


Tip If you set Width to 0 and Height to 0, the Smart Ingest feature is enabled, and the dimensions are obtained from the input stream automatically.

Step 5 Expand the Distribution section, and select the IP Stream. Define the following parameters:

• H.264 encoder profile (.awp)

• Multicast IP address and port

Note You will specify the same IP address and port for the DMP so that the DMP can ingest the multicast stream from this IP address and then export the stream to digital signage.

Step 6 Click Save.

Starting the Multicast Stream on the Content Server

Procedure


a. Open up a browser session and log in as administrator to the Content Server.

b. Click the Management tab.

c. Click Recording Setup > Create Recording.

d. In Create Recording section, select a recording alias.

e. Enter a dial number for a conference bridge.



Step 2 To start the live stream, dial in to the same conference bridge by using a video enabled endpoint.



b. Launch Windows Media Services window, and verify that the publishing point has started.


OL-21554-02



Submitting the Live Job on Cisco MXE 3500

Procedure

Step 1 From the Toolbox, click Submission > Live.

Choose a job profile for the live job.

Enter the following information and then submit the job:

• Base name—Enter a meaningful name.

• Video Format—Choose IP capture.

• IP Capture Source—Choose the unicast or multicast stream.

• Start trigger—Choose now.

• Stop trigger—Choose IP.

Step 2 Click Submit.


OL-21554-02

Chapter 6 Deploying Licensed Features for Cisco MXE 3500 Speech-to-Text and Graphics Overlay Features

Verifying the Live Job

Once a Live Job has been submitted, it will appear in the Job Status window. When the capture station selected for the job becomes available, the job is displayed in green, indicating that the capture station is reserved and the job can be started.

Tip To verify a WMV Live Job, open the Windows Media Player on a client PC, and enter a URL that corresponds to the publishing point, such as mms: //streaming server/publishing_point.

Figure 24 Job Status Monitor Upper Pane

Speech-to-Text and Graphics Overlay FeaturesThe Speech-to-Text feature enables the Cisco MXE 3500 to create text transcripts from videos.

The Graphics Overlay feature enables the Cisco MXE 3500 to embed the transcripts as text captions in the video: it enables the graphic overlay that can be applied to the bumper, trailer, and content. Note that watermarks, bumpers, and trailers themselves are not licensed features; they are part of the basic Cisco MXE 3500 feature set.

Activation To use either of these features, you must purchase and install the feature license on the standalone Cisco MXE 3500 or the Resource Manager device.


• Overview of the Speech-to-Text and Graphic Overlay Features, page 6-28

• Required Components for the Speech-to-Text and Graphic Overlay Features, page 6-28

• Configuration Workflow for Speech-to-Text Conversion, page 6-29

• Configuration Workflow for the Graphic Overlay Feature, page 6-30

• Guidelines for Improving the Accuracy of Speech to Text, page 6-31

• Importing a Speech Profile to Cisco MXE 3500, page 6-32


OL-21554-02


Overview of the Speech-to-Text and Graphic Overlay FeaturesThe Cisco MXE 3500 speech-to-text feature supports the following functionality:

• Speech-to-text conversion—Cisco MXE 3500 can extract an audio track from a video and convert it to text by using a speech-to-text transcription engine from Nuance, which is included with the Cisco MXE 3500.

• Speech-to-text graphic overlay function (graphics and captioning)—As part of a separate job, the Cisco MXE 3500 can overlay the text that is produced as part of the speech-to-text conversion on the input video and produce a single video output that includes the text as subtitles.

Figure 6-25 illustrates the process that the Cisco MXE 3500 uses for speech-to-text conversion and the overlay function.

Figure 6-25 Process for the Speech-to-Text Conversion and Graphic Overlay Function

Note The speech-to-text conversion and the graphic overlay function require separate job profiles.

Required Components for the Speech-to-Text and Graphic Overlay FeaturesThe following components are required for the speech-to-text and graphics overlay features:

• Speech-to-Text feature license

• Graphics Overlay feature license

• Input video—You can use any video with audio that Cisco MXE 3500 supports.

• Job Profile for the speech-to-text conversion function

• Job Profile for the graphics overlay function

Prefilter STTWorker

2777

95.FLVSource

NUANCE

Nuance SpeakerProfile

NuanceVocabulary

Graphics Template.xml

Prefilter Flash8Worker

Source

Content SWFTemplate

Content XMLScript

.WAV

.TXT

.XML

Speech-To-Text Job: Extracts audio and creates STT files

Graphics Overlay/Captioning Job: Creates output with STT transcriptoverlaid as a graphic


OL-21554-02


Configuration Workflow for Speech-to-Text ConversionThe following workflow describes how to set up a job to get the STT text output and the XML file to use as a graphic overlay.

Note For information about using the web UI, see the User and Admin Guide for Cisco MXE 3500 Release 3.1.

Preprocessor and encoder profile settings remain the same as file-to-file transcoding.

1. Create a new STT Encoder Profile. Encoder Profiles to set parameters that identify how uncompressed preprocessor output will be compressed for distribution.


b. Choose Profile Class: Encoder and Speech To Text.

2. Configure the following settings for the STT Encoder Profile:

• Choose the output file format. Cisco MXE 3500 can generate up to three files during the conversion:

– Audio Output—Produces a .WAV audio file with audio converted to WAVE format.

– Text Output—Produces a text only output of converted speech (audio).

– Overlay Output—Produces a time-coded, XML file with text, using the font and formatting information specified in the Graphics Template file. The XML file is a metadata file that the speech-to-text graphics overlay function uses.

• Nuance Speaker Profile: Choose the STT speaker profile. The STT Engine uses this profile to improve the accuracy of the transcribed data.

• STT Topic Vocabulary: Choose the STT vocabulary. The STT Engine uses this vocabulary to improve the accuracy of the transcribed data.

• Graphics Template: Choose Graphics Template. The Cisco MXE 3500 uses this template to format of the XML file that will be generated for later use by the speech-to-text graphic overlay function. You define parameters such as font style, font size, and formatting in this file. Cisco MXE 3500 ships with the following three sample template files that you can modify, as needed. These files are in the C:\media\SpeechToTextFiles folder.

– DemoTemplate.xml

– IntroductionTemplate.xml

– SubTitleTemplate.xml


OL-21554-02



Figure 6-26 Speech-to-Text Encoder Settings

Configuration Workflow for the Graphic Overlay FeatureThe following workflow describes how to set up a job to use a XML STT output file from a video as a graphic overlay on that video.

Note For information about using the web UI, see the User and Admin Guide for Cisco MXE 3500 Release 3.1.

Preprocessor and encoder profile settings are the same as file-to-file transcoding. The encoder profile can be any video encoder profile that Cisco MXE 3500 supports.

1. Configure the settings for the Preprocessor Profile as a job submission parameter or File Job settings in the Submission > File page.

For the Preprocessor Profile, configure the following settings:

• Enabled: Check the Enable checkbox in the Graphics Overlay Content area.

• Template File: Specify the content Flash SWF template that contains the graphic elements to be used for overlaying the text as subtitles on the video. A sample SWF file ships with Cisco MXE 3500.

• Metadata File/URL: Specify the time-coded XML file that the speech-to-text conversion function generated.

For a File Job, configure the following settings:

• Content XML Script: Specify the time-coded XML file that the speech-to-text conversion function generated.

• Content SWF Template: Specify the content Flash SWF template that contains the graphic elements to be used for overlaying the text as subtitles on the video. Cisco MXE 3500 ships with three sample template files for customer to use and modify as required. The following sample files are in the C:\media\SpeechToTextFiles folder:

– corporate-r09_1080.swf

– corporate-r09-bigwatermark.swf

– corporate-r09-iphone.swf


OL-21554-02



Guidelines for Improving the Accuracy of Speech to TextThis section includes the following topics:

• Speech Input Style, page 6-31

• Multiple Speakers in a Video, page 6-31

• Speech Profiles, page 6-31

• Methods for Acquiring Audio, page 6-31

Speech Input Style

For a higher degrees of accuracy for speech-to-text output, we recommend that a speaker uses the following guidelines:

• Speaks in a consistent tone.

• Uses a consistent rate (no drastic changes in the pace).

• Speaks without intentionally pausing after each word. A flow that is closest to natural speech is preferred by the system.

• Records the speech in a quiet environment.

• Pronounces each word clearly, but does not try to separate each syllable within the word.

Multiple Speakers in a Video

The speech-to-text system does not perform well for recordings in which there are multiple speakers in the video. Multiple speakers adversely affects accuracy because each speaker has his or her own associated speaking style, accent, and so on, and switching between multiple speakers throws off the system’s ability to adapt any one speaker.

Speech Profiles

You can obtain a speaker-independent speech profile on Cisco.com in the Video, Cable and Content Delivery > Media Transformation > Cisco MXE 3000 Series (Media Experience Engines) > Cisco MXE 3500 (Media Experience Engine) > Media Experience Engine Utilities in the software download area. See also: Importing a Speech Profile to Cisco MXE 3500, page 6-32.

Methods for Acquiring Audio

A speaker has the ability to dramatically improve speech-to-text accuracy by using appropriate equipment to generate the audio track on the video. We recommend the following methods:

• Video originating in the studio: Generally, the audio on video tracks recorded in the studio is of optimal quality and does not need enhancement. However, accuracy will be impacted when background sounds are induced into the video, such as music or multiple speakers.

• Training videos, corporate communications content, or lectures recorded on a camcorder: We recommended that the audio input is via a direct microphone /lapel microphone connection (LINE IN) to the camcorder/recording device. It is imperative that the video recording is carried out with quiet surroundings (low ambient noise).


OL-21554-02

http://www.cisco.com/cisco/web/download/index.html


Chapter 6 Deploying Licensed Features for Cisco MXE 3500 Simplified User Interface Feature

• Desktop video creation and video blogging: When recording media for desktop video, use a noise-cancelling headset.

Importing a Speech Profile to Cisco MXE 3500You can obtain an additional speaker-independent speech profile on Cisco.com and import (copy) it to Cisco MXE 3500.

Before You Begin

For Resource Manager configuration, you must import a speech profile separately on each Resource Manager and Resource Node in your deployment.

Procedure

Step 1 Go to the Cisco.com software download center at the following URL: http://www.cisco.com/cisco/web/download/index.html

Step 2 Choose Video, Cable and Content Delivery > Media Transformation > Cisco MXE 3000 Series (Media Experience Engines) > Cisco MXE 3500 (Media Experience Engine) > Media Experience Engine Utilities and download the speaker independent profile to a location where the Cisco MXE 3500 can access the file.

Step 3 RDC to the Cisco MXE 3500 and save the speaker profile to CiscoMXE3500_IP_Address\temp.


Step 5 Follow the on-screen prompts to uncompress the speech profile file to the following Cisco MXE 3500 folder: \\CiscoMXE3500_IP_Address\Documents and Settings\All Users\Application Data\Nuance\Dragon SDK Server Edition10\Users\. A new folder that includes additional folders and files will be created.

Simplified User Interface Feature

Activation To use this feature, you must purchase and install the SUI feature license on the standalone Cisco MXE 3500 or the Resource Manager device.

The SUI feature enables you to configure an easy-to-use interface, called the Video Conversion Interface, so that users convert a video file to selected formats, enhance the video file with predefined content, download and share the video file, or automatically upload to Cisco Show and Share.


• Configuring Video Output Formats for the SUI, page 6-33

• Configuring a Watermark, Bumper, Trailer, and Graphic Overlay for the SUI, page 6-34

• Configuring Show and Share Integration, page 6-35

• Configuring a Wowza or Windows Media Streaming Server , page 6-36

• Configuring E-Mail Notifications, page 6-37


OL-21554-02



• Configuring SUI User Accounts, page 6-38

• Restoring the Default SUI Profiles, page 6-38

Configuring Video Output Formats for the SUIThe SUI uses the specific sui profile space to manage the set of job profiles for the SUI. This space is accessible in the Web UI by clicking Tools > Select Profile Space and then choosing the sui profile space. Once you access this profile space, you can add, remove, or edit Job Profiles to specify the output formats that display to users in the SUI.

Note Before you modify the default Job Profiles in the sui profile space, we recommend that you back up the profiles. For information about the backup and restore feature, see the User Guide for Cisco MXE 3500 at http://www.cisco.com/en/US/products/ps9892/products_user_guide_list.html.

Each SUI job profile uses a special sui preprocessor profile that is configured to support variable aspect ratios and percentage-based watermarks and to define a default bumper, trailer, watermark, and graphic overlay that users can enable or disable in the SUI. See the “Configuring a Watermark, Bumper, Trailer, and Graphic Overlay for the SUI” section on page 6-34 for more information.

Renaming the Job Profiles that Display in the Conversion Interface

Procedure

Step 1 Log in to the Web UI.

Step 2 Click Tools > Select Profile Space and then choose the sui profile space.

Step 3 Click Search in the Profile Browser to display all Job Profiles for the sui profile space.

Step 4 Select the Job Profile that you want to rename by double clicking it. The Edit Job Profile pane for the selected profile displays.

Step 5 Click Save As, and enter the name to display in the Conversion Interface.

Figure 6-27 Edit Job Profile Pane


OL-21554-02



Step 6 Click Save. A Job Profile with that name will appear in the Profile Browser when refreshed and will also show in the Conversion Interface output type list.

Step 7 Delete the original profile from the Profile Browser by double-clicking it again and then clicking Delete in the Edit Job Profile pane.

Tip Alternatively, you can RDC to mxe_IP_address, navigate to the SUI profile directory (C:\mxe\profile\spaces\sui), and right-click to rename profiles as desired. To remove profiles from the SUI profile directly, copy them to a different folder and then delete the profiles from the SUI profile directory.

Configuring a Watermark, Bumper, Trailer, and Graphic Overlay for the SUIEach sui job profile uses a special sui Preprocessor Profile that specifies the default bumper, trailer, watermark, and graphic overlay that users can enable or disable in the SUI. The following media asset files for these defaults are located in c:\media\assets directory:

• watermark.psd - watermark

• bumper.mov – bumper video

• trailer.mov – trailer video

• overlay.swf – content graphics overlay Flash template

• overlay.xml – content graphics overlay XML

You can upload customized versions of these files to the media assets directory in the SUI Administration page (Toolbox > Administration > SUI Admin) in the Web UI.

Note We recommend that you do not rename the media asset files.

The bumper, trailer, and watermark files can be any format that Cisco MXE 3500 supports. If the new media asset files have a different file name, such as mybumper.wmv, you must ensure that the new file names are reflected in the sui preprocessor profile. For information about configuring the bumper, trailer, watermark or graphic overlay files, see the User Guide for Cisco MXE 3500 at http://www.cisco.com/en/US/products/ps9892/products_user_guide_list.html.

You can also edit the default or create a custom graphic overlay file from the original (overlay.swf). This file is designed to use the following variable names that are specified in the SUI: speaker-name and speaker-subject.

Configuring Watermarking (Preprocessor) for the SUI

When configuring watermarking for a Preprocessor Profile, you must specify the watermark size and placement (X Distance and Y Distance) in terms of source pixels, requiring a separate Preprocessor Profile for every watermark size and source dimension. The Smart Ingest feature for the SUI provides an automatic watermarking functionality that enables users to apply a watermark without having to know its source footage dimensions. This feature also allows the use of the same preprocessor profile for different watermarks and sources.


OL-21554-02



All the profiles that ship with the SUI are configured to use Smart Ingest. If you configure a new Preprocessor Profile for the SUI, use the settings in Table 6-1. For information about configuring or editing Preprocessor Profiles, see the User Guide for Cisco MXE 3500 at http://www.cisco.com/en/US/products/ps9892/products_user_guide_list.html.

Configuring Show and Share IntegrationYou can configure and enable/disable the Cisco Show and Share integration for the SUI on the SUI Administration page (Toolbox > Administration > SUI Admin) in the Web UI. Table 6-3 describes the settings.

Note When the transcoding job finishes, SUI users can upload the file to Cisco Show and Share. This upload requires that SUI users also have Cisco Show and Share user accounts.

Table 6-1 Required Configuration for a SUI Preprocessor Profile

Field Required Setting

Aspect Ratio Conversion

Mode Letterbox, Curtains

Note Smart ingest preserves aspect ratio through letterboxing/curtaining and allows specifying watermark coverage area in % as opposed to pixels. It does not preserve source video dimensions or frame rates.

Input Pixel Auto

Output Pixel Auto

Watermarking

Units Percent

Set additional parameters as needed.

Audio

Add Silent Audio Track Check the checkbox to enable

Table 6-2 Show and Share Settings for the SUI

Field Description

Enabled Checkbox that enables or disables Show and Share integration for SUI users

Authentication URL IP address and port for the Show and Share server, such as https://show_and_share_server:8443

Admin UserId Valid Show and Share administrator user ID

Admin Password Password for the Show and Share administrator user ID

End Point https://show_and_share_server:8443/vportal/services/xml/api


OL-21554-02



Note Cisco MXE 3500 ships with encoder profiles that are configured for the Cisco Show and Share integration. These profiles must have the User Data field set to SNS.

Example 6-1 Encoder Profile for Cisco Show and Share Integration

Configuring a Wowza or Windows Media Streaming Server Output video that is produced by using the SUI can be delivered to a supported streaming server. When SUI users select one of the profiles that you create by using this procedure, the SUI will provide watch links for viewing the streamed video output. Users can access the Watch link in the Watch column on the SUI Job Status page.

Note Users can use the Watch link to view a video on a Mac or PC with an appropriate viewer or on an iPhone or iPad if in a supported video format. The Download link that displays in the Your Results page, only downloads the video to the user’s computer hard drive for viewing. Users wanting to view a downloaded video on an iPhone or iPad need to download and then transfer the video to the device.

Procedure

Step 1 Log in to the Web UI.

Step 2 Click Tools > Select Profile Space and then choose the sui profile space.

Upload URL http://show_and_share_server:8080/vportal/GenericFileUpload

Automatically Approve Video

Checkbox that specifies whether videos require a Show and Share Video Publisher to approve the video before publication

Table 6-2 Show and Share Settings for the SUI

Field Description


OL-21554-02


Step 3 Choose the job profiles that will have video output delivered to the streaming server and determine the encoder output type, such as H.264 or Windows Media, for each job profile. Obtain this information by double-clicking the name of the Job Profile in the Profile Browser and looking at the Type column for the encoder profile.

Step 4 Create a new delivery profile to deliver the encoder output to the streaming server.

a. In the Toolbox, click Profile Management > New Profile.

b. Choose Profile Class: Distribution and then Delivery

c. Click New Profile.

d. In the Delivery Formats area, check the checkbox next to the encoder output type, such as H.264 or Windows Media, for each of the job profiles that you chose in Step 2.

e. In the Delivery Method area, specify the FTP/SFTP parameters for the streaming server’s FTP server.

f. Enter the streaming URL template. For example, enter the following URL for a Wowza server: http://10.194.193.135:1935/vod/mp4:{filename}/playlist.m3u8 where the {filename} macro will be substituted with the actual video filename when the job is submitted.

Step 5 For each chosen job profile, add the delivery profile that you created in Step 4.

a. Open the chosen job profile to edit it.

b. Add the delivery profile to the job profile.

c. Save the edited job profile.

Step 6 Ensure that the streaming server is enabled for the SUI.

a. Click Toolbox > Administration > SUI Admin.

b. In the Stream Server section, check the Enabled checkbox.

Configuring E-Mail NotificationsYou can configure an e-mail server so that Cisco MXE 3500 can send e-mails to SUI users that include the status of a job transcode or a temporary password if a password is forgotten.

Click Administration > SUI Admin and then enter the following information in the General Settings area:

• Admin User ID—Enter the name that you want displayed as the e-mail sender, such as no-reply.

• Email server—Enter the hostname for the e-mail server.


OL-21554-02


Configuring SUI User AccountsYou can configure SUI user account settings on the SUI Administration page (Toolbox > Administration > SUI Admin) in the Web UI. Table 6-3 describes the settings.

After providing the URL to the SUI and new user access code, users can create an account by accessing the SUI and clicking the Create an account button.

SUI user accounts are created with a special noaccess role that disables access to Web UI functionality and are added to the user database. You can edit or delete all user accounts on the User Administration page (Toolbox > Administration > User) in the Web UI.

Restoring the Default SUI ProfilesFollow this procedure to restore the default SUI profiles.

Procedure

Step 1 Go to the Cisco.com software download center at the following URL: http://www.cisco.com/cisco/web/download/index.html.

Step 2 Choose Video, Cable and Content Delivery > Media Transformation > Cisco MXE 3000 Series (Media Experience Engines) > Cisco MXE 3500 (Media Experience Engine) > Media Experience Engine Utilities and download the SUI profiles file to a location where the Cisco MXE 3500 can access the file.

Step 3 RDC to the Cisco MXE 3500 and save the SUI profiles file to c:\temp.


Step 5 Follow the on-screen prompts to uncompress the system profile file to the following Cisco MXE 3500 folder: c:\mxe\profiles\spaces\sui.

Table 6-3 User Account Settings for the SUI

Field Description

Maximum provisioned users Maximum number of user accounts that can be created

New user access code Access code for creating a new SUI account

Total Disk Space Quota (GB) Total disk space available for storing output videos for all SUI user accounts

The total disk space quota must be a non-zero, positive integer.

User DiskSpace Quota (GB) Individual SUI user disk quota for storing output videos


OL-21554-02


C H A P T E R 7
Security Best Practices for Cisco MXE 3500
Revised: June 3, 2011 This section includes the following topics:

• Security Best Practices for Cisco MXE 3500, page 7-1

• Cisco MXE 3500 Microsoft Hot Fix Release Policy, page 7-2

• Windows Services, page 7-2

Security Best Practices for Cisco MXE 3500Cisco MXE 3500 ships with Windows 2003 Server settings, which ensures a high level of security. Though administrators can modify Windows settings, we suggest that you refrain from doing so unless Cisco TAC recommends a modification and that you follow these best practices:

• Do not install additional software, applications, or firmware on Cisco MXE 3500 unless Cisco recommends that you do so in the product documentation. See also: Cisco MXE 3500 Hot Fix Release Policy, below.

• Do not use Cisco MXE 3500 for any purpose other than those we specify in the product documentation.

• Do not use Cisco MXE 3500 as a general purpose Windows device.

• Do not browse to any Internet site on Cisco MXE 3500 other than www.cisco.com and www.microsoft.com to download product documentation and patches.

• Do not modify Windows components from the configured defaults.

• Do not change the Services startup types except for supported changes that are documented in the product documentation.

• Back up Cisco MXE 3500 regularly.


Chapter 7 Security Best Practices for Cisco MXE 3500 Cisco MXE 3500 Microsoft Hot Fix Release Policy

Cisco MXE 3500 Microsoft Hot Fix Release PolicyMicrosoft releases a list of security hot fixes Every 2nd Tuesday of the month. Every 3rd Tuesday of the month, excluding holidays, Cisco will release a technical bulletin with the Microsoft security bulletin hot fix identifiers that Cisco recommends you install on Cisco MXE 3500, at which time you should compete the following tasks:

1. Download and read the Cisco technical bulletin for each recommended hot fix.

2. Download and read the Microsoft security bulletin.

3. Download each recommended Microsoft hot fix.

4. Follow the procedures that Microsoft provides to install the hot fixes on Cisco MXE 3500.

If Microsoft releases a security hot fix for a catastrophic problem outside of the monthly cycle, Cisco will release a corresponding technical bulletin.

You can access Cisco MXE 3500 technical bulletins at the following URL: http://www.cisco.com/en/US/products/ps10631/index.html

Windows ServicesTable 7-1 lists Cisco MXE 3500 Windows 2003 Server services and startup types.

Table 7-1 Windows 2003 Server Services on the Cisco MXE 3500

Service Name Startup Type

.NET Runtime Optimization Manual—Not started

Alerter Disabled

Application Experience Lookup Automatic

Application Layer Gateway Manual—Not started

Application Management Manual—Not started

ASP .NET State Manual—Not started

Automatic Updates Manual

Background Intelligent Transfer Service Automatic started

ClipBook Disabled

COM+ Event System Automatic

COM+ System Application Manual—Not started

Computer Browser Automatic

Cryptographic Services Automatic

DCOM Server Process Launcher Automatic

Distributed File System Manual—Not started

Distributed Link Tracking Client Automatic

Distributed Link Tracking Server Disabled

Distributed Transaction Coordinator Automatic

DNS Client Automatic


OL-21554-02

http://www.cisco.com/en/US/products/ps10631/index.html

Chapter 7 Security Best Practices for Cisco MXE 3500 Windows Services

Error Reporting Service Automatic

Event Log Automatic

File Replication Manual—Not started

Help and Support Automatic

HID Input Service Automatic

HTTP SSL Manual—Not started

IIS Admin Service Automatic

IMAPI-CD Burning COM Service Disabled

Indexing Service Disabled

Internet Connection Sharing Disabled

Intersite Messaging Disabled

IPSEC Services Automatic

IPSEC Policy Agent Automatic

Kerberos Key Distribution Center Disabled

License Logging Service Disabled

Logical Disk Manager Automatic

Logical Disk Manager Administrative Service Manual

Messenger Disabled

Microsoft Software Shadow Copy Provider Manual—Not started

MXE CAM Automatic

MXE ECS Automatic

MXE Encoder Automatic

MXE Folder Attendant Automatic

MXE Log Service Automatic

Net Logon Manual

Net .tcp port Sharing Disabled

Netmeeting Remote Desktop Sharing Disabled

Network Connections Manual

Network DDE Disabled

Network DDE DSDM Disabled

Network Location Awareness Manual—Not started

Network Provisioning Service Manual

NT LM Security Support Provider Manual

Performance Logs and Alerts Automatic

Plug and Play Automatic

Portable Media Serial Number Service Manual

Table 7-1 Windows 2003 Server Services on the Cisco MXE 3500 (continued)



OL-21554-02


Print Spooler Automatic

Protected Storage Automatic

Remote Access Auto Connection Manager Manual

Remote Access Connection Manager Manual

Remote Desktop Help Session Manager Automatic

Remote Procedure Call (RPC) Automatic

Remote Procedure Call (RPC) Locator Disabled

Remote Registry Service Automatic

Removable Storage Manual

Resultant Set of Policy Provider Manual

Routing and Remote Access Disabled

Secondary Logon Automatic

Security Accounts Manager Automatic

Server Automatic

Shell Hardware Detection Automatic

Smart Card Manual

Special Administration Console Helper Manual

SQL Server (MSSQLSERVER) Automatic

SQL Server Active Directory Helper Disabled

SQL Server Browser Disabled

SQL Server VSS Writer Automatic

SNMP Service Automatic

SNMP Trap Service Manual

System Event Notification Automatic

Task Scheduler Automatic

TCP/IP NetBIOS Helper Service Automatic

Telephony Manual

Telnet Disabled

Terminal Services Manual

Terminal Services Session Directory Manual

Themes Disabled

Uninterruptible Power Supply Manual

Virtual Disk Service Manual

Virtual Shadow Copy Manual

WebClient Disabled

Windows Audio Automatic




OL-21554-02


Windows Firewall/Internet Connection Sharing (ICS) Disabled

Windows Cardspace Manual

Windows Image Acquisition (WIA) Disabled

Windows Installer Manual

Windows Management Instrumentation Automatic

Windows Management Instrumentation Driver Extensions Manual

Windows Time Automatic

Windows Presentation Foundation Font Cache 3.0.0.0 Manual

Windows User mode Driver Framework Manual

WinHTTP Web Proxy Auto-Discovery Service Manual

Wireless Configuration Automatic

World Wide Web Publishing Service Automatic




OL-21554-02



OL-21554-02


C H A P T E R 8
Troubleshooting Cisco MXE 3500
Revised: June 3, 2011This section includes the following topics:

• Logging, page 8-1

• Troubleshooting, page 8-1

LoggingThe ECS and LCS components are configured to log all informational, warning, and error messages to a rolling daily log file in the [MXE install directory]/logs directory, for example: C:\Program Files\Cisco\Media Experience Engine\logs.

Log files are local to each node. The files will be ECS01.log or LCS01.log. For Resource Manager deployments, the Resource Manager device will have both ECS and LCS log files, and the Resource Nodes will have only LCS log files. For standalone deployments, Cisco MXE 3500 will have both ECS and LCS log files.

A new log file is created each day with the date. For example, ECS01.log will be the ECS log for the first day of the month, and ECS02.log will be the ECS log for the second day of the month, and so on. Each month, the log files are overwritten during the course of the month.

To view the log files:

Navigate to the appropriate directory path on the node, and click the log file to open it.

Note Use a text editor to open the file. The extension may need to be mapped for the file to open with the selected text editor.

Troubleshooting This section includes the following topics:

• Troubleshooting Steps, page 8-2

• Troubleshooting FAQs, page 8-2

• Contacting Cisco TAC, page 8-4

• Reinstalling the Software, page 8-4


Chapter 8 Troubleshooting Cisco MXE 3500 Troubleshooting

Troubleshooting StepsTo isolate an issue, complete the following initial troubleshooting steps:

1. Review the log files. For Resource Manager deployments, each node has its own log files. See also: Logging, page 8-1.

2. Review error messages/codes to identify the problem, file name, and location.

3. With available logging information, answer the following questions:

• Is the problem intermittent or consistent?

• For Resource Manager deployments, does the problem affect only one or all nodes?

4. Review the following information to isolate the problem:

See also: Troubleshooting FAQs, page 8-2.

Troubleshooting FAQsThis section includes the following topics:

• Standalone and Resource Manager Deployments, page 8-2

• Resource Manager Deployments, page 8-3

Standalone and Resource Manager Deployments

Q. How do I determine if a problem is related to a decode or an encode?

A. If the error is occurring on a prefilter, the problem is a decode error. If the error is occurring on an encoder, the problem is an encode error.

Q. Why can I not see the Hosts page when I log in to the Resource Manager or standalone Cisco MXE 3500 as Administrator?

A. This issue is due to Internet security settings. Open Internet Explorer, click Tools > Internet Options > Security > Local intranet. Choose "Medium" security level and apply the settings. Then, access the Hosts page again.

If the Problem is: Then, the problem is likely:

Consistent Intermittent One Node All Nodes —

X Local node issue

X Network or Resource Manager issue

X X System-side issue

X X Local node issue

X X Network issue (connectivity)


OL-21554-02


Resource Manager Deployments

About Installation, Upgrade, and Licensing

Q. Can I upgrade a standalone Cisco MXE 3500 to a Resource Manager or Resource Node?

A. No. There is no patch available to do this in Release 3.1.

Q. Why are the Resource Nodes not transcoding after I upload the software license file to the RM device?

A. After uploading the license file to all nodes, you must configure all the nodes as Hosts in the Resource Manager. See also: System Settings, page 5-10.

Q. Can Resource Manager function as Resource Node and execute a transcoding task?

A. Resource Manager does function as one of the Resource Nodes in a group. Resource Manager executes transcoding jobs, as well as load balancing and distributing jobs across the group.

About System Status

Q. How can I find out what jobs are running on the Resource Nodes?

A. Log in to the UI. From the Toolbox, select Monitoring > System Status to see the jobs that are running on each Resource Node. See also: Accessing the Cisco MXE 3500 Web User Interface (Standalone or Resource Manager), page 4-3.

Q. How do I know if a Resource Node is down?

A. When the Resource Node goes down or disconnects from the network, Resource Manager sends an e-mail to the system administrator if a valid SMTP server and e-mail address are configured in the System page.

About Configuration

Q. Can I create a watch on a Resource Node?

A. You can create a watch on any Resource Node, but the watch must be accessible to the Resource Manager and all other nodes in the group.

Q. Why do I get an error when I choose a media file in the UI that is local to the Resource Manager device (C:\media)?

A. Media files must be in a shared folder with UNC path because transcoding jobs can run on any Resource Node. You cannot choose files on a local machine (C:\media). See also: Input Section (Resource Manager Only), page 5-11.

About Nodes That Have Gone Down

Q. If a Resource Node goes down while executing a particular job, can another Resource Node execute the remaining sub-jobs?

A. When a Resource Node goes down, the Resource Manager redistributes its remaining jobs. Another Resource Node will start executing a sub-job from the beginning; it will not start from the middle of sub-job.

Q. If the Resource Manager goes down and is brought up, do I need to resubmit all the media files?


OL-21554-02


A. Yes, you must submit all the media files again.

Q. If a Resource Node goes down and is brought up, do I need to reconfigure it?

A. No. The Resource Node will automatically become a part of the group, and the Resource Manager will start distributing jobs when it finds that the Resource Node is up.

About Jobs That Have Failed or Are Not Executing

Q. Why are workers failing?

A. If a worker is failing on one node but running on others, the problem is likely a local node issue. If a worker is failing across all nodes, the problem is likely a network or Resource Manager issue.

Q. Why is a Resource Node that is configured as a Host in the Resource Manager not executing jobs?

A. There are two possibilities:

• The Resource Node is not on the network.

• There may be a configuration issue. If you configured an SMTP server and provided an e-mail address on the Systems page, you should have received an e-mail specifying the node that is down. If that Resource Node is up and the Resource Manager is accessible to that Resource Node, then it could be configuration problem. Go to the Hosts page and verify that the “permit all” checkbox is checked for that node. See also: User Settings (Resource Manager Only), page 5-13.

Contacting Cisco TACIf attempts to rectify a problem fail, or if you have additional questions, please open a Service Request using the TAC Service Request Tool at:

http://tools.cisco.com/ServiceRequestTool/create/DefineProblem.do.

Please have your valid Cisco ID and password available. As an alternative, you may also call one of these numbers:

• Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)

• EMEA: +32 2 704 55 55

• USA: 1 800 553-2447

You can find a complete list of Cisco TAC contacts at this URL:


Reinstalling the SoftwareIf you need to reinstall the software to recover the Cisco MXE 3500, we recommend that you back up first if possible. Follow the backup procedures in Chapter 3, “Backing Up and Restoring Data for Cisco MXE 3500 Release 3.0 Upgrade to Release 3.2.” Then, follow the installation procedures in Chapter 1, “Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2.”


OL-21554-02