Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Deployment and Administration Guide for
Cisco Media Experience Engine 3500
Release 3.0
January 26, 2010
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-21554-01
F C S D r a ft 1 / 5 / 10 - - C i s c o C o n f i d e n t i a l
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.0
© 2008-2010 Cisco Systems, Inc. All rights reserved.
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
CONTENTS
Preface
vii
Purpose
Audience
vii
vii
Obtaining Documentation and Submitting a Service Request
Providing Documentation Feedback
CHAPTER
1
viii
viii
Deploying Cisco MXE 3500 in Standalone Configuration
About Cisco MXE 3500 Standalone Deployments
Guidelines for Standalone Deployments
1-1
1-1
1-2
Identifying Steps to Deploy Cisco MXE 3500
1-2
Accessing the Cisco MXE 3500 Web User Interface
1-2
Installing the License on Cisco MXE 3500 1-3
Obtaining the MAC Address 1-3
Obtaining a New, Upgrade, or Feature License 1-4
Installing a New, Upgrade, or Feature License 1-5
Configuring the Input and Output Media Directories
1-6
Enabling System Administration E-mail Notifications
Configuring the Host Settings
1-7
1-8
Confirming Service Accounts and Identifying Device Type
Creating a Folder Attendant Directory and Watch
Creating a Directory 1-11
Creating a Watch 1-12
Accessing the Cisco MXE 3500 Tools
1-8
1-10
1-14
Using Administrative Tools to Configure Cisco MXE 3500
Host Settings 1-15
System Settings 1-18
Input Section 1-18
Output Section 1-20
General Settings Section 1-21
Status Settings Section 1-22
Data Purging Section 1-22
Audio Capture Section 1-23
User Settings 1-24
1-15
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
iii
Contents
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
User Metadata Settings 1-24
IP Capture (Live Streaming) Settings
1-25
Verifying Cisco MXE 3500 Deployment 1-26
Test 1: Submit a Job Using File Job Submission 1-27
Test 2: Submit a Job Using Folder Attendant 1-27
Test 3: Verify a Licensed Feature is Enabled 1-28
CHAPTER
2
Deploying Cisco MXE 3500 in Resource Manager Configuration
About Cisco MXE 3500 Resource Manager Deployments
Guidelines for Resource Manager Deployments
2-1
2-1
2-2
Identifying Steps for Resource Manager Deployments 2-2
Example Workflow for a Three-Node Resource Manager Deployment
Accessing Cisco MXE 3500 User Interfaces
2-3
2-5
Installing the License on the Resource Manager Device 2-5
Obtaining the Resource Manager MAC Address 2-5
Obtaining the License for the Resource Manager 2-6
Installing the License on the Resource Manager 2-8
Configuring the Input and Output Media Directories
2-8
Enabling System Administration E-mail Notifications
Confirming Service Accounts
2-9
2-9
Creating a Folder Attendant Directory and Watch
2-9
Using Administrative Tools to Configure the Resource Manager Device 2-9
Host Settings for Resource Manager Deployments 2-10
Understanding Capacity, Expense, and Limit 2-13
Configuring Hosts Settings for Resource Manager Deployments 2-14
System Settings for Resource Manager Deployments 2-15
Input Section 2-16
Output Section 2-17
General Settings Section 2-18
Status Settings Section 2-18
Data Purging Section 2-18
Audio Capture Section 2-18
User Settings 2-19
Role Settings 2-20
Profile Space Settings 2-21
User Metadata Settings 2-22
IP Capture Settings 2-22
Verifying Resource Manager Deployment
2-22
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
iv
OL-21554-01
Contents
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Test 1: Submit a Job Using File Job Submission 2-22
Test 2: Submit a Job Using Folder Attendant 2-23
Test 3: Verify a Licensed Feature is Enabled 2-24
CHAPTER
3
Deploying Licensed Features for Cisco MXE 3500
3-1
Live Streaming (IP Capture) Feature 3-1
Required Components for the Live Streaming Feature 3-2
Ingest (Input) 3-2
Job Profile (Transcode) 3-2
Distribution (Output) 3-2
Network Design for Cisco MXE 3500 Deployments with Live WMV IP Streaming 3-3
Configuration Workflow for Cisco MXE 3500 Deployments with Live WMV IP Streaming 3-3
Network Design for Cisco MXE 3500 Deployments with Live Flash 8 and H.264 IP Streaming 3-4
Configuration Workflow for Cisco MXE 3500 Deployments with Live Flash8 and H.264 IP
Streaming 3-5
Speech-to-Text and Graphics Overlay Features 3-6
Overview of the Speech-to-Text and Graphic Overlay Features 3-6
Required Components for the Speech-to-Text and Graphic Overlay Features
Configuration Workflow for Speech-to-Text Conversion 3-7
Configuration Workflow for the Graphic Overlay Feature 3-9
Guidelines for Improving the Accuracy of Speech to Text 3-9
Speech Input Style 3-9
Multiple Speakers in a Video 3-10
Speech Profiles 3-10
Methods for Acquiring Audio 3-10
Importing a Speech Profile to Cisco MXE 3500 3-10
CHAPTER
4
Security Best Practices and Backup Guidelines for Cisco MXE 3500
Security Best Practices for Cisco MXE 3500
4-1
4-1
Cisco MXE 3500 Microsoft Hot Fix Release Policy
Windows Services
3-7
4-2
4-2
Backup Guidelines for Cisco MXE 3500 4-5
Backing Up Cisco MXE 3500 4-6
Backing Up the Folder Attendant Database 4-6
Backing Up Cisco MXE 3500 Files 4-6
Restoring Cisco MXE 3500 Configuration 4-7
Recovering Cisco MXE 3500 4-7
Restoring the Folder Attendant Database 4-7
Restoring Other Cisco MXE 3500 Files 4-8
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
v
Contents
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
CHAPTER
5
Upgrading Cisco MXE 3500 from a Standalone Device
Guidelines for Upgrades
CHAPTER
6
5-1
5-1
Upgrading Cisco MXE 3500 from a Standalone to Resource Manager Device
Preparing for Upgrade 5-2
Obtaining a License for the Upgrade to Resource Manager 5-3
Upgrading the Resource Manager Device 5-3
Obtaining the Upgrade Software 5-3
Performing the Upgrade to Resource Manager 5-4
Completing Resource Manager Upgrade Configuration 5-5
5-1
Upgrading a Cisco MXE 3500 from a Standalone to a Resource Node Device
Preparing for Upgrade 5-6
Obtaining a License for the Upgrade to Resource Node 5-8
Upgrading the Resource Node Device 5-9
5-6
Adding a New Resource Node to an Existing Resource Manager Deployment
5-10
Troubleshooting Cisco MXE 3500
Logging
6-1
6-1
Troubleshooting 6-1
Troubleshooting Steps 6-2
Troubleshooting FAQs 6-2
Standalone and Resource Manager Deployments
Resource Manager Deployments 6-3
CHAPTER
7
Recovering Cisco MXE 3500
Preparing for Recovery
6-2
7-1
7-1
Recovering the Cisco MXE 3500 7-2
Disabling the Quiet Boot Setting and Configuring the Hard Drive as RAID-0
Installing the Cisco MXE 3500 Software to Recover the Appliance 7-4
Restoring the Configuration 7-4
Standalone or Resource Manager Configuration
Resource Node Configuration 7-6
7-3
7-5
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
vi
OL-21554-01
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Preface
Revised: January 26, 2010, OL-21554-01
This section includes the following topics:
•
Purpose, page vii
•
Audience, page vii
•
Obtaining Documentation and Submitting a Service Request, page viii
•
Providing Documentation Feedback, page viii
Purpose
This guide describes the installation and configuration tasks that system administrators must complete
before deploying a Cisco MXE 3500 in a standalone or Resource Manager configuration.
This guide does not describe how to use the Cisco MXE 3500; see the User Guide for Cisco MXE 3500
for this information.
Audience
This guide is for the system administrator who is responsible for deploying Cisco MXE 3500; this guide
is not for end users.
For changes that occurred to this product after the publication date of this guide, see the release notes at
this URL:
http://www.cisco.com/en/US/products/ps9892/prod_release_notes_list.html
The release notes include important information about system requirements, product limitations,
restrictions, caveats, and documentation updates.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
vii
Preface
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as 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.
Providing Documentation Feedback
To provide feedback on this Cisco MXE 3500 document, or to report an error or omission, you can use
the online, Embedded Feedback form. The form appears when you click the “Give us Feedback” link
that is located at the top right of each chapter in this guide, which you can access at the following URL:
http://www.cisco.com/en/US/docs/video/mxe/3500/sw/3_x/3_0/deployment/guide/ag_mxe30.html
You can also send feedback to [email protected].
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
viii
OL-21554-01
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
CH A P T E R
1
Deploying Cisco MXE 3500 in Standalone
Configuration
Revised: January 26, 2010, OL-21554-01
This section includes the following topics:
•
About Cisco MXE 3500 Standalone Deployments, page 1-1
•
Guidelines for Standalone Deployments, page 1-2
•
Identifying Steps to Deploy Cisco MXE 3500, page 1-2
•
Accessing the Cisco MXE 3500 Web User Interface, page 1-2
•
Installing the License on Cisco MXE 3500, page 1-3
•
Enabling System Administration E-mail Notifications, page 1-7
•
Confirming Service Accounts and Identifying Device Type, page 1-8
•
Creating a Folder Attendant Directory and Watch, page 1-10
•
Accessing the Cisco MXE 3500 Tools, page 1-14
•
Using Administrative Tools to Configure Cisco MXE 3500, page 1-15
•
Verifying Cisco MXE 3500 Deployment, page 1-26
About Cisco MXE 3500 Standalone Deployments
•
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 2, “Deploying Cisco MXE 3500 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 3, “Deploying
Licensed Features for Cisco MXE 3500.”
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
1-1
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Guidelines for Standalone Deployments
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Guidelines for Standalone Deployments
The following configuration guidelines and restrictions apply to standalone deployments:
•
You can configure directories as local paths or UNC paths to a network share. Mapped drives can
only be used in deployments using a storage area network (SAN). Directory locations must be
accessible to all Hosts.
•
MXE-Service is the default user account that is used to log in to all mxe-services. MXE-Service
must have read/write access to all configured UNC paths and to IIS. Do not delete or modify this
account; otherwise, the Cisco MXE 3500 may not work.
•
The Cisco MXE 3500 ships with the Host name mxe3500. Before you configure Hosts Settings, you
must change the Host name to a unique name on the device.
•
The Cisco MXE 3500 ships with DHCP enabled. If you use static IP addresses, disable DHCP and
assign an IP address on the device before you configure Hosts Settings.
Identifying Steps to Deploy Cisco MXE 3500
Cisco MXE 3500 comes from the factory requiring you to perform only the following steps before using
the system. Optional deployment instructions are included, as well.
Mandatory Deployment Steps
•
Installing the License on Cisco MXE 3500, page 1-3
•
Configuring the Input and Output Media Directories, page 1-6
•
Enabling System Administration E-mail Notifications, page 1-7
•
Configuring the Host Settings, page 1-8
Optional Deployment Steps
•
Confirming Service Accounts and Identifying Device Type, page 1-8
•
Creating a Folder Attendant Directory and Watch, page 1-10
•
Verifying Cisco MXE 3500 Deployment, page 1-26
•
Deploying Licensed Features for Cisco MXE 3500, page 3-1
Accessing the Cisco MXE 3500 Web User Interface
Note
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.
The Cisco MXE 3500 web user interface (UI) is the main interface that you use to set up encoder server
and client preferences, create job profiles, submit jobs, and so on. For information about using the UI,
see the User Guide for Cisco Media Experience Engine 3500 on Cisco.com, or click Help in the UI.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
1-2
OL-21554-01
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Installing the License on Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Procedure
Step 1
Access the Cisco MXE 3500 web UI by using the following methods:
•
Click the icon, shown in Figure 1-1, on the desktop of the Cisco MXE 3500 (standalone or
Resource Manager device), and enter the default credentials to log on.
•
From any PC or server with network connectivity, open a supported web browser, and enter
http://TCP-IP-name-or-address/Mxeui, where TCP-IP-name-or-address is the TCP/IP name or IP
address of the Cisco MXE 3500. Enter the default credentials to log on.
Figure 1-1
Step 2
Note
User Interface Desktop Icon
Enter the default credentials:
•
Login User Name: admin
•
Password: admin
We recommend that you change the default credentials.
Installing the License on Cisco MXE 3500
This section includes the following topics:
•
Obtaining the MAC Address, page 1-3
•
Obtaining a New, Upgrade, or Feature License, page 1-4
•
Installing a New, Upgrade, or Feature License, page 1-5
Obtaining the MAC Address
Note
Licensing requires that you provide either of the two Cisco MXE 3500 Ethernet MAC addresses and
that, once you choose a MAC address to provide, you use the same MAC address for all license
requests—initial or upgrade.
Procedure
Step 1
Boot the appliance.
Step 2
Browse to C:\Program Files\Cisco\Media Experience Engine\bin.
Step 3
Double-click lmtools.exe.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
1-3
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Installing the License on Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Step 4
Select the System Settings tab, shown in Figure 1-2.
Figure 1-2
Step 5
Copy one of the Ethernet addresses that display between quotes in Ethernet Address field. You will use
this number to generate a Cisco MXE 3500 license. See also: Obtaining a New, Upgrade, or Feature
License, page 1-4.
Tip
Step 6
System Settings Tab
You can find the MAC addresses and statuses of the Ethernet adapters by running the command
prompt (double-click the Command Prompt shortcut on your desktop) and executing the
command ipconfig /all. The command output shows each Ethernet adapter's status and the MAC
address (under Physical Address).
Close the LMTOOLS window.
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
the following URL: http://www.cisco.com/web/siteassets/account/index.html
•
Obtain the Cisco MXE 3500 MAC address. See also: Obtaining the MAC Address, page 1-3.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
1-4
OL-21554-01
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Installing the License on Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Note
•
Licensing requires that you provide either of the two Cisco MXE 3500 Ethernet MAC addresses
and that, once you choose a MAC address to provide, you use the same MAC address for all
license requests—initial or upgrade.
Obtain the Product Authorization Key (PAK), which is located on the Software License Claim
Certificate that shipped with your appliance.
Procedure
Step 1
Go to http://www.cisco.com/go/license.
Step 2
Enter the PAK.
Step 3
If you are using 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
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 the
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
Installing a New, Upgrade, or Feature License
Before You Begin
Obtain the Cisco MXE 3500 license file. See also: Obtaining a New, Upgrade, or Feature License,
page 1-4.
Procedure
Step 1
On the standalone Cisco MXE 3500 or the Resource Manager, copy the generated mxe.lic file into the
license directory: C:\Program Files\Cisco\Media Experience Engine\license
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
1-5
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Configuring the Input and Output Media Directories
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Step 2
Reboot the device.
Step 3
Log in to the device.
Step 4
Log into the UI at http://localhost/mxeUI or by clicking the Cisco MXE Web Interface icon on the
desktop.
Step 5
Reset the license cache by clicking Tools > Reset License Cache.
What to Do Next
To Complete This Task
Complete standalone Cisco MXE 3500
deployment
See This Section
1.
Configuring the Input and Output Media
Directories, page 1-6
2.
Enabling System Administration E-mail
Notifications, page 1-7
Upgrade from standalone to Resource Manager
configuration
Upgrading Cisco MXE 3500 from a Standalone
Device, page 5-1
Test a new feature license on a standalone or
Resource Manager Cisco MXE 3500
Deploying Licensed Features for
Cisco MXE 3500, page 3-1
Configuring the Input and Output Media Directories
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 UI at http://localhost/mxeUI or click the Cisco MXE Web Interface icon on the desktop.
Step 2
From the Toolbox, click 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 \\localhost\media. For more information, see the “Input Section” section on
page 1-18.
•
Bumper
•
common
•
Media
•
Watermark
Step 4
In all the fields in the Output section, enter the directories where Cisco MXE 3500 will store output
media, such as \\localhost\output. For more information, see the “Output Section” section on page 1-20.
Step 5
Click Save.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
1-6
OL-21554-01
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Enabling System Administration E-mail Notifications
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Enabling System Administration E-mail Notifications
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.
The sending of e-mails is not required to complete transcoding jobs.
Procedure
Step 1
Log into the UI at http://localhost/mxeUI or click the Cisco MXE Web Interface icon on the desktop.
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, page 1-21.
c.
Step 3
Click Save.
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.
– 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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
1-7
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Configuring the Host Settings
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Configuring the Host Settings
Use this procedure to configure the Host settings for a standalone Cisco MXE 3500.
Procedure
Step 1
From the Toolbox, click Administration > Host. See also: Host Settings, page 1-15.
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
Step 3
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.
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
Step 4
Step 5
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.
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.
At the top of the page, click Apply Configuration.
Confirming Service Accounts and Identifying Device Type
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
1-8
OL-21554-01
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Confirming Service Accounts and Identifying Device Type
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
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 1-1.
Procedure
Step 1
Open Services by double-clicking the Services icon on your desktop or from the Control Panel.
Step 2
Select the MXE services for your Cisco MXE 3500 device type one at a time, as shown in Figure 1-3.
Note
Table 1-1 lists the services for each Cisco MXE 3500 device type.
Table 1-1
Statuses of Services for Cisco MXE 3500 Device Types
Service
Standalone 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
Figure 1-3
Step 3
Selecting a Service Account
Double-click each service—except IIS Admin Service— and then select the Log On tab, as shown
Figure 1-4. The service account can be changed from the default on this page.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
1-9
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Creating a Folder Attendant Directory and Watch
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
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.
Figure 1-4
Service Log On Tab
Creating a Folder Attendant Directory and Watch
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
1-10
OL-21554-01
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Creating a Folder Attendant Directory and Watch
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
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.
This section includes the following topics:
•
Creating a Directory, page 1-11
•
Creating a Watch, page 1-12
Creating a Directory
Procedure
Step 1
From the Toolbox, click Folder Attendant.
Step 2
From the Directory drop-down, click Add, as shown in Figure 1-5. The Directory fields, shown in
Figure 1-6, display on the Folder Attendant Administration page.
Figure 1-5
Adding a Directory
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
1-11
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Creating a Folder Attendant Directory and Watch
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Figure 1-6
Step 3
Directory Fields
Enter the appropriate information in each of the fields, and click Save.
Note
If the Directory Path, shown in Figure 1-6, 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,
as shown in Figure 1-7.
Figure 1-7
Select the Directory and Add a Watch
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
1-12
OL-21554-01
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Creating a Folder Attendant Directory and Watch
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
The Folder Attendant Administration page displays Directory, Watch, Custom Metadata, and Override
System Settings sections, shown Figure 1-8, Figure 1-9, and Figure 1-10, each of which contains a series
of fields.
Figure 1-8
Complete Watch Fields
Figure 1-9
Complete Custom Metadata Fields
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
1-13
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Accessing the Cisco MXE 3500 Tools
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Figure 1-10
Complete Override System Settings Fields
Step 3
Expand each section, and enter the appropriate information in each field.
Step 4
Save the Watch.
Accessing the Cisco MXE 3500 Tools
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
Access these tools only by logging in directly to the Cisco MXE 3500, instead of a web browser, and
clicking Start > Cisco > Media Experience Engine > Media Experience Engine 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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
1-14
OL-21554-01
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Using Administrative Tools to Configure Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Figure 1-11
Cisco Media Experience Engine Tools
Using Administrative Tools to Configure 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:
Note
•
Host Settings, page 1-15
•
System Settings, page 1-18
•
User Settings, page 1-24
•
User Metadata Settings, page 1-24
•
IP Capture (Live Streaming) Settings, page 1-25
You must have Admin Tools permission to configure these settings.
Host Settings
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
1-15
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Using Administrative Tools to Configure Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Figure 1-12 shows the Host Administration page.
Figure 1-12
Host Administration Page and Settings
Table 1-2 describes the Host settings.
Table 1-2
Setting
Host
Host Settings and Descriptions
Description
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
Port
If the status is disabled, jobs will not schedule on that Cisco MXE 3500 node.
TCP port that the LCS is listening on. The default is 3500.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
1-16
OL-21554-01
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Using Administrative Tools to Configure Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 1-2
Host Settings and Descriptions
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
Temp
Directory
(UNC Name)
Permitted?
Numbers between 5 and 30 are typically best. Setting this to a high number >
30 can make the system status monitor hard to read.
Specifies the directory where temporary files and preprocessor output will be store,
such as C:\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.
•
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 Release 3.0.
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
1-17
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Using Administrative Tools to Configure Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 1-2
Host Settings and Descriptions
Capture Type
This setting is not available in Cisco MXE 3500 Release 3.0.
Type of capture card (DV, DVCAM, AJA-SDI, Custom, etc.). Selection of a
non-custom value will predefine the audio and video channel.
Video
This setting is not available in Cisco MXE 3500 Release 3.0.
CH/Audio CH
Displays Video Channel and Audio Channel for each Live-capture worker.
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.
Note
You must have Admin Tools permission to configure these settings.
The System page is made up of the following sections:
•
Input Section, page 1-18
•
Output Section, page 1-20
•
General Settings Section, page 1-21
•
Status Settings Section, page 1-22
•
Data Purging Section, page 1-22
•
Audio Capture Section, page 1-23
Input Section
Figure 1-13 shows the Input section settings.
Figure 1-13
Input Settings
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
1-18
OL-21554-01
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Using Administrative Tools to Configure Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 1-3 describes the settings.
Table 1-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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
1-19
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Using Administrative Tools to Configure Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Output Section
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.
Figure 1-14 shows the Output section settings.
Figure 1-14
Output Settings
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
1-20
OL-21554-01
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Using Administrative Tools to Configure Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
General Settings Section
Figure 1-15 shows the General Settings section.
Figure 1-15
General Settings
Table 1-4 describes the settings.
Table 1-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.
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
1-21
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Using Administrative Tools to Configure Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Status Settings Section
Figure 1-16 shows the Status Settings section.
Figure 1-16
Status Settings
Table 1-5 describes the settings.
Table 1-5
Setting
Monitor
Window
Display
Status Settings and Descriptions
Description
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
Auto Reap
(Minutes)
Include
Failed Jobs in
Auto Reap
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.
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.
•
yes: include failed jobs in Auto Reap
•
no: do not include failed jobs in Auto Reap
Data Purging Section
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
1-22
OL-21554-01
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Using Administrative Tools to Configure Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Figure 1-17 shows the Data Purging section.
Figure 1-17
Data Purging Settings
Table 1-6 describes the settings.
Table 1-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.
Audio Capture Section
Figure 1-18 shows the Audio Capture section.
Figure 1-18
Audio Capture Settings
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
1-23
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Using Administrative Tools to Configure Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 1-7 describes the settings.
Table 1-7
Setting
Audio Capture Settings and Descriptions
Description
Drift
From the drop-down, select on to enable audio and video synchronization. This is only
Compensation 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
Sample Rate
When capturing long analog audio clips, theCisco 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.
Sets audio sampling rate to trade off audio quality and transmission bandwidth and file
size limitations.
User Settings
The Cisco MXE 3500 comes with one predefined user:
•
Note
admin: The default password is also admin. We recommend that you change the admin password
immediately.
In standalone Cisco MXE 3500 configuration, there is a single administrative user, and there is no option
to create additional users. User management, including defining roles and restricting user access to web
UI features, is available in Resource Manager configuration.
User Metadata Settings
This 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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
1-24
OL-21554-01
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Using Administrative Tools to Configure Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
The New or Edit User Metadata e pop-up, shown in Figure 1-19, allows you to create and modify user
metadata settings.
Figure 1-19
User Metadata Settings
IP Capture (Live Streaming) Settings
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.
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
1-25
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Verifying Cisco MXE 3500 Deployment
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
The New or Edit IP Capture Source pop-up, shown in Figure 1-20, allows you to create and modify
profile spaces.
Figure 1-20
IP Capture Source Settings
Table 1-8 describes the settings.
Table 1-8
IP Capture Source Settings and Descriptions
Setting
Description
Name
Unique IP Capture Source name.
IP Address
The multicast IP address of the source UDP non-RTP MPEG2 TS stream.
The IP addresses reserved for this purpose are from 224.0.0.0 to
239.255.255.255.
Port
The multicast port to bind to. Values range from 0 to 65535.
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.
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,
page 1-15.
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.
Verifying Cisco MXE 3500 Deployment
To ensure your system has been correctly deployed and configured, perform the following tests:
•
Test 1: Submit a Job Using File Job Submission, page 1-27
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
1-26
OL-21554-01
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Verifying Cisco MXE 3500 Deployment
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
•
Test 2: Submit a Job Using Folder Attendant, page 1-27
•
Test 3: Verify a Licensed Feature is Enabled, page 1-28
Test 1: Submit a Job Using File Job Submission
Before You Begin
In the C:\ProgramFiles\QuickTime folder, select Sample.mov, and copy the file to the C:\Media
folder.
Procedure
Step 1
Access the UI. See also: Accessing the Cisco MXE 3500 Web User Interface, page 1-2.
Step 2
From the Toolbox, expand Submission, and click File. The File Job Submission page displays.
Step 3
In the Profile section, choose Cable_Broadband.job.awp.
Step 4
In the Input section, complete the following tasks:
a.
Click Browse
b.
Select C:\Media\Sample.mov.
c.
Click Add File(s) to move files from your media directory to the Media Source box.
Step 5
Click Submit.
Step 6
From the toolbox, select View > Monitoring > Job Status.
Step 7
Continue watching the Job Status window to make sure the job completes.
Step 8
Browse to the C:\Output folder, locate Sample.Cable_Broadband.Cable_Broadband.wmv, and play
the file. Accept any warning messages or alerts Windows Media Player may display.
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
C:\media and C:\output folders.
Procedure
Step 1
Access Folder Attendant. See also: Accessing the Cisco MXE 3500 Web User Interface, page 1-2.
Step 2
Add a directory for the Folder Attendant to monitor.
a.
From the Toolbox, click 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 C:\media and complete other fields as needed.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
1-27
Chapter 1
Deploying Cisco MXE 3500 in Standalone Configuration
Verifying Cisco MXE 3500 Deployment
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
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
In the C:\ProgramFiles\QuickTime folder, select Sample.mov, and copy the file to the C:\Media
folder.
Step 6
Watch the Job Status pane to make sure the job starts and completes.
Step 7
Browse to the C:\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 1-27, 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 3-3
– Configuration Workflow for Cisco MXE 3500 Deployments with Live Flash8 and H.264 IP
Streaming, page 3-5
•
To verify that the Speech to Text or Graphics Overlay feature is enabled after you install a feature
license, see the following sections:
– Configuration Workflow for Speech-to-Text Conversion, page 3-7
– Configuration Workflow for the Graphic Overlay Feature, page 3-9
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
1-28
OL-21554-01
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
CH A P T E R
2
Deploying Cisco MXE 3500 in Resource Manager
Configuration
Revised: January 26, 2010, OL-21554-01
This section includes the following topics:
•
About Cisco MXE 3500 Resource Manager Deployments, page 2-1
•
Guidelines for Resource Manager Deployments, page 2-2
•
Identifying Steps for Resource Manager Deployments, page 2-2
•
Accessing Cisco MXE 3500 User Interfaces, page 2-5
•
Installing the License on the Resource Manager Device, page 2-5
•
Enabling System Administration E-mail Notifications, page 2-9
•
Confirming Service Accounts, page 2-9
•
Creating a Folder Attendant Directory and Watch, page 2-9
•
Using Administrative Tools to Configure the Resource Manager Device, page 2-9
•
Verifying Resource Manager Deployment, page 2-22
About Cisco MXE 3500 Resource Manager Deployments
A Cisco MXE 3500 Resource Manager (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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
2-1
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Guidelines for Resource Manager Deployments
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
•
Note
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.
For information about Cisco MXE 3500 components, see the User Guide for Cisco Media Experience
Engine 3500 on Cisco.com, or click Help in the UI.
Guidelines for Resource Manager Deployments
The 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 follows:
1.
Complete the product license registration, ensuring you have entered a MAC address for the
Resource Manager device. The registration is complete when you receive a license by e-mail.
Do not install this license because there are no Resource Nodes associated with it.
2.
Complete the product license registration for a Resource Node, ensuring that you enter the same
MAC address that you entered for the Resource Manager. If you have only one
Resource Node, you will install this license. Otherwise, discard the license.
3.
Complete the registration process for the all the Resource Nodes in the group one by one:
register and obtain the license for that registration before registering the next Resource Node.
When you have obtained the license file for the final registration process, save the license file.
This is the license that you will install in the Resource Manager.
•
Resource Manager and Resource Nodes ship with the same Host name, mxe3500. Before you
configure Hosts Settings, you must change the Host name to a unique name on each device.
•
Resource Manager and Resource Nodes ship with DHCP enabled. If you use static IP addresses,
disable DHCP and assign an IP address on each device before you configure Hosts Settings.
•
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.
•
MXE-Service is the default user account that is used to log in to all mxe-services. MXE-Service
must have read/write access to all configured UNC paths and to IIS. Do not delete or modify this
account; otherwise, the Cisco MXE 3500 may not work.
•
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.
•
To enable a licensed feature, you must install the feature license on the Resource Manager. For
information about deploying licensed features, see Chapter 3, “Deploying Licensed Features for
Cisco MXE 3500.”
Identifying Steps for Resource Manager Deployments
Cisco MXE 3500 comes from the factory requiring you to perform the following mandatory steps before
using the system. Optional deployment instructions are included, as well.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
2-2
OL-21554-01
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Identifying Steps for Resource Manager Deployments
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Note
Before you begin deployment, see the “Example Workflow for a Three-Node Resource Manager
Deployment” section on page 2-3 for an example deployment workflow.
Mandatory Deployment Steps
•
Installing the License on the Resource Manager Device, page 2-5
•
Configuring the Input and Output Media Directories, page 2-8
•
Enabling System Administration E-mail Notifications, page 2-9
•
Configuring System Settings for Resource Manager Deployments, page 2-15
•
Configuring User Settings, page 2-19
Optional Deployment Steps
•
Confirming Service Accounts, page 2-9
•
Creating a Folder Attendant Directory and Watch, page 2-9
•
Verifying Resource Manager Deployment, page 2-22
•
Deploying Licensed Features for Cisco MXE 3500, page 3-1
Example Workflow for a Three-Node Resource Manager Deployment
The following table provides an example workflow that identifies the mandatory steps that you must
complete for a new, three-node Resource Manager deployment, which includes the Resource Manager
node and two Resource Nodes.
—
Task
Resource
Step 1
Set up the Resource Manager device:
Quick Start Hardware Installation Guide for
Cisco Media Experience Engine 3500
Step 2
a.
Configure a unique TCP/IP Host name.
b.
If using static IP addresses, disable DHCP and
assign an IP address.
Set up the Resource Nodes:
a.
Configure unique TCP/IP Host names.
b.
If using static IP addresses, disable DHCP and
assign IP addresses.
Quick Start Hardware Installation Guide for
Cisco Media Experience Engine 3500
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
2-3
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Identifying Steps for Resource Manager Deployments
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
—
Task
Step 3
Obtain the Resource Manager license:
Step 4
1.
Obtain a Resource Manager MAC address. Note:
You must use the same MAC address for each
license that you request.
2.
Get the PAK for the Resource Manager device.
3.
Register the Resource Manager device on
Cisco.com.
4.
Obtain the Resource Manager license by e-mail.
This license is valid only for the
Resource Manager device as a single node.
Discard this license.
Obtain the updated Resource Manager license that
includes two additional Resource Nodes:
1.
Obtain the Resource Manager MAC address that
you used to obtain the Resource Manager license.
2.
Get the PAK for the Resource Node.
3.
Using the same MAC address for the
Resource Manager device, register the
Resource Node on Cisco.com.
4.
Obtain the updated Resource Manager license by
e-mail. This license is valid only for the
Resource Manager node and one Resource Node
for a total of two licensed nodes. Discard this
license.
5.
Repeat Step 1 through Step 3 for the second
Resource Node, ensuring that you use the correct
PAK and MAC address.
6.
Obtain the updated Resource Manager license by
e-mail. This license is valid for the
Resource Manager and two Resource Nodes for a
total of three licensed nodes. This is the license
you will install on the Resource Manager device.
Step 5
Install the license on the Resource Manager device.
Step 6
Configure the mandatory settings on the
Resource Manager device:
•
Input and output directories
•
E-mail server
•
System Settings
•
Hosts Settings
Resource
•
Software License Claim Certificate
•
Product Authorization Key (PAK) for the
Resource Manager
•
Obtaining the Resource Manager MAC
Address, page 2-5
•
Obtaining the License for the
Resource Manager, page 2-6
•
Software License Claim Certificate
•
PAK for the Resource Node
•
Obtaining the Resource Manager MAC
Address, page 2-5
•
Obtaining the License for the
Resource Manager, page 2-6
Installing the License on the
Resource Manager, page 2-8
•
Configuring the Input and Output Media
Directories, page 2-8
•
Enabling System Administration E-mail
Notifications, page 2-9
•
Configuring System Settings for
Resource Manager Deployments,
page 2-15
•
Configuring User Settings, page 2-19
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
2-4
OL-21554-01
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Accessing Cisco MXE 3500 User Interfaces
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Accessing Cisco MXE 3500 User Interfaces
For information about accessing the user interfaces on the Resource Manager device, see the “Accessing
the Cisco MXE 3500 Web User Interface” section on page 1-2 in Chapter 1, “Deploying
Cisco MXE 3500 in Standalone Configuration.”
Note
•
You can access Cisco MXE 3500 user interfaces 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 and facilitate identification. 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,
page 1-8.
Installing the License on the Resource Manager Device
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 you purchased.
This section includes the following topics:
•
Obtaining the Resource Manager MAC Address, page 2-5
•
Obtaining the License for the Resource Manager, page 2-6
•
Installing the License on the Resource Manager, page 2-8
Obtaining the Resource Manager MAC Address
Note
Licensing requires that you provide either of the two Cisco MXE 3500 Ethernet MAC addresses and
that, once you choose a MAC address to provide, you use the same MAC address for all license
requests—initial or upgrade.
Procedure
Step 1
Tip
Boot the Resource Manager device.
The desktop image of this device shows Resource Manager.
Step 2
Browse to C:\Program Files\Cisco\Media Experience Engine\bin.
Step 3
Double-click lmtools.exe.
Step 4
Select the System Settings tab, shown in Figure 2-1.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
2-5
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Installing the License on the Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Figure 2-1
Step 5
System Settings Tab
Copy one of the Ethernet addresses that display between quotes in Ethernet Address field. You will use
this number to generate a Cisco MXE 3500 Resource Manager license. See also: Obtaining the License
for the Resource Manager, page 2-6.
Tip
You can find the MAC addresses and statuses of the Ethernet adapters by running the command
prompt (double-click the Command Prompt shortcut on your desktop) and executing the
command ipconfig /all. The command output shows each Ethernet adapter's status and the MAC
address (under Physical Address).
Obtaining the License for the Resource Manager
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 MAC address of the Resource Manager device.
This registration process is required to associate the number of Resource Nodes that you purchased with
the MAC address of the Resource Manager device; this association results in multiple licenses being sent
to the e-mail address that you use for registration.
Note
Licensing requires that you provide either of the two Cisco MXE 3500 Ethernet MAC addresses and
that, once you provide a MAC address, you must provide the same MAC address for all license
requests—both initial or upgrade.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
2-6
OL-21554-01
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Installing the License on the Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
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.
Before You Begin
•
You must have an account on Cisco.com to access the license website.
•
Obtain the Cisco MXE 3500 MAC address of the Resource Manager device. See also: Obtaining the
Resource Manager MAC Address, page 2-5.
•
Obtain the Product Authorization Keys (PAKs) for the Resource Manager device and
Resource Nodes, which is located on the Software License Claim Certificates that shipped with your
devices.
•
Ensure that you understand the licensing process for Resource Manager deployments. See also:
Guidelines for Resource Manager Deployments, page 2-2.
Procedure
Step 1
Go to http://www.cisco.com/go/license.
Step 2
Enter the PAK for the Resource Manager device, or if you have already licensed the Resource Manager,
enter the PAK for the Resource Node.
Step 3
If you are using the Resource Manager device to access the registration website, press the Enter key;
otherwise, click the Submit button.
Step 4
Follow the on-screen prompts and ensure that you use the MAC address from the Resource Manager
device when prompted.
Step 5
After registration, you will receive an e-mail with a license file.
a.
If the license file is only for the Resource Manager device, discard this license. Return to Step 1 and
complete the registration process for a Resource Node, ensuring that you use the PAK for the
Resource Node.
b.
If this license file is for a Resource Node and you have additional Resource Nodes to register,
discard this license. Return to Step 1 and complete the registration process for another
Resource Node, ensuring that you use the PAK for the Resource Node.
c.
If this license file is for the final Resource Node, save the license file; you will install this license
on the Resource Manager device, as it includes a valid license for the Resource Manager device and
each Resource Node in the group.
Note
We recommend that you save the license file in a secure location. 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 the
these numbers:
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
2-7
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Configuring the Input and Output Media Directories
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
•
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
Installing the License on the Resource Manager
Before You Begin
•
Obtain the Cisco MXE 3500 license file for the Resource Manager device. See also: Obtaining the
License for the Resource Manager, page 2-6.
•
Only install the license file on the Resource Manager device.
Procedure
Step 1
Log in to the Resource Manager device.
Step 2
Copy the generated mxe.lic file into the license directory: C:\Program Files\Cisco\Media Experience
Engine\license
Step 3
Reboot the Resource Manager device.
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.
Before You Begin
Ensure that any directories that you are going to configure exist and are shared.
Procedure
Step 1
Log into the UI at http://localhost/mxeUI on the Resource Manager or click the Cisco MXE Web
Interface icon on its desktop.
Step 2
From the Toolbox, click Administration > System.
Step 3
In the following fields of the Input section, enter the directories where nodes will obtain input media.
For more information, see the “Input Section” section on page 2-16.
Step 4
•
Bumper
•
common
•
Media
•
Watermark
In all the fields in the Output section, enter the directories where nodes will store output media. For
more information, see the “Output Section” section on page 2-17.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
2-8
OL-21554-01
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Enabling System Administration E-mail Notifications
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Step 5
Click Save.
Enabling System Administration E-mail Notifications
For information about configuring e-mail notifications on the Resource Manager device, see the
“Enabling System Administration E-mail Notifications” section on page 1-7 in Chapter 1, “Deploying
Cisco MXE 3500 in Standalone Configuration.”
Note
We recommend that you configure an e-mail server so that you receive job completion or failure
notifications.
Confirming Service Accounts
For information about service accounts on the Resource Manager or Resource Node, see the
“Confirming Service Accounts and Identifying Device Type” section on page 1-8 in Chapter 1,
“Deploying Cisco MXE 3500 in Standalone Configuration.”
Note
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 Watch
For information about creating a Folder Attendant directory and watch on the Resource Manager device,
see the “Creating a Folder Attendant Directory and Watch” section on page 1-10 in Chapter 1,
“Deploying Cisco MXE 3500 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, page 1-8.
Using Administrative Tools to Configure the Resource Manager
Device
The Administration section of the Toolbox allows you to configure the following settings:
•
Host Settings for Resource Manager Deployments, page 2-10
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
2-9
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Using Administrative Tools to Configure the Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Note
•
System Settings for Resource Manager Deployments, page 2-15
•
User Settings, page 2-19
•
Role Settings, page 2-20
•
Profile Space Settings, page 2-21
•
User Metadata Settings, page 2-22
•
IP Capture Settings, page 2-22
You must have Admin Tools permission to configure these settings.
Host Settings for Resource Manager Deployments
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: Configuring Hosts Settings for Resource Manager Deployments, page 2-14 and Understanding
Capacity, Expense, and Limit, page 2-13
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
2-10
OL-21554-01
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Using Administrative Tools to Configure the Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Figure 2-2 shows the Hosts settings.
Figure 2-2
Host Settings for Resource Manager Deployments
Table 2-1 describes the Hosts settings.
Table 2-1
Setting
Host
Hosts Settings and Descriptions for Resource Manager Deployments
Description
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
2-11
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Using Administrative Tools to Configure the Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 2-1
Status
Hosts Settings and Descriptions for Resource Manager Deployments (continued)
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, page 2-13 and Figure 2-2, Host
Settings for Resource Manager Deployments
Temp
Specifies the directory where temporary files and preprocessor output will be stored
Directory
while the job is processing.
(UNC Name)
This must be a UNC path, not a local path, so that other Hosts will be able to access
files written to this directory.
MXE-Service must also have read/write access to this directory.
Note
Worker
Status
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.
•
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
2-12
OL-21554-01
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Using Administrative Tools to Configure the Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 2-1
Limit
Hosts Settings and Descriptions for Resource Manager Deployments (continued)
Displays the maximum number of a particular worker that can be run simultaneously on
the displayed Host.
Valid values are 0-99.
See also: Understanding Capacity, Expense, and Limit, page 2-13 and Figure 2-2, Host
Settings for Resource Manager Deployments
Expense
The expense of a worker is expressed as a portion of Host capacity.
Valid values are 0-99.
See also: Understanding Capacity, Expense, and Limit, page 2-13 and Figure 2-2, Host
Settings for Resource Manager Deployments
Capture
Name
This setting is not available in Cisco MXE 3500 Release 3.0.
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.0.
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.0.
Displays Video Channel and Audio Channel for each Live-capture worker.
Understanding Capacity, Expense, and Limit
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 for Resource Manager Deployments, page 2-10.
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.
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:
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
2-13
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Using Administrative Tools to Configure the Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Host Capacity
Portion of Total Processing
Power Required
Worker Expense
100
Half
50
6
Half
3
9
One third
3
6
One third
2
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.
Configuring Hosts Settings for Resource Manager Deployments
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, page 2-13 and Host Settings for
Resource Manager Deployments, page 2-10.
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, page 2-19.
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
2-14
OL-21554-01
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Using Administrative Tools to Configure the Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Note
Step 3
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.
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
Step 4
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.
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.
Step 7
Repeat Step 2 through Step 5 for each node that you purchased.
System Settings for Resource Manager Deployments
The 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, page 2-16
•
Output Section, page 2-17
•
General Settings Section, page 2-18
•
Status Settings Section, page 2-18
•
Data Purging Section, page 2-18
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
2-15
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Using Administrative Tools to Configure the Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
•
Data Purging Section, page 2-18
Input Section
Note
Directory values must be UNC paths to a network share.
Figure 2-3 shows Input section settings.
Figure 2-3
Input Settings
Table 2-2 describes the Input section settings.
Table 2-2
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.
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.
Directory values must be UNC paths to a network share.
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.
Directory values must be UNC paths to a network share.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
2-16
OL-21554-01
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Using Administrative Tools to Configure the Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 2-2
Input Settings and Descriptions for Resource Manager Deployments
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.
Directory values must be UNC paths to a network share. The Watermark Directory
location must be accessible to all hosts.
Output Section
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
2-17
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Using Administrative Tools to Configure the Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Figure 2-4 shows the Output section settings.
Figure 2-4
Output Settings
General Settings Section
For information about General Settings configuration on the Resource Manager device, see the “General
Settings Section” section on page 1-21 in Chapter 1, “Deploying Cisco MXE 3500 in Standalone
Configuration.”
Status Settings Section
For information about Status Settings configuration on the Resource Manager device, see the “Status
Settings Section” section on page 1-22 in Chapter 1, “Deploying Cisco MXE 3500 in Standalone
Configuration.”
Data Purging Section
For information about Data Purging Settings configuration on the Resource Manager device, see the
“Data Purging Section” section on page 1-22 in Chapter 1, “Deploying Cisco MXE 3500 in Standalone
Configuration.”
Audio Capture Section
For information about Audio Capture Settings configuration on the Resource Manager device, see the
“Audio Capture Section” section on page 1-23 in Chapter 1, “Deploying Cisco MXE 3500 in Standalone
Configuration.”
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
2-18
OL-21554-01
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Using Administrative Tools to Configure the Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
User Settings
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 Cisco MXE 3500 comes with one predefined user:
•
Note
admin: The default password is also admin. We recommend that your Administrator
immediately change the admin password.
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 New or Edit Users pop-up, shown in Figure 2-5, allows you to create and modify system users.
Figure 2-5
User Settings
Table 2-3 describes the settings.
Table 2-3
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
2-19
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Using Administrative Tools to Configure the Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 2-3
User Settings and Descriptions
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.
Role Settings
Each 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 2-6, allows you to create and modify system users.
Figure 2-6
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
•
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
2-20
OL-21554-01
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Using Administrative Tools to Configure the Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 2-4 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.
Table 2-4
Setting
Role Settings and Descriptions
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.
Profile Space Settings
The 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 2-7, allows you to create and modify profile
spaces.
Figure 2-7
Profile Space Settings
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
2-21
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Verifying Resource Manager Deployment
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 2-5 describes the settings.
Table 2-5
Setting
Profile Space Settings and Descriptions
Description
Name
Enter a unique name.
Directory
Enter a verifiable directory.
User Metadata Settings
This 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 1-24 in Chapter 1, “Deploying Cisco MXE 3500 in
Standalone Configuration.”
IP Capture Settings
Cisco 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” section on page 1-25 in Chapter 1, “Deploying Cisco MXE 3500 in
Standalone Configuration.”
Verifying Resource Manager Deployment
To ensure your system has been correctly deployed and configured, perform the following tests:
•
Test 1: Submit a Job Using File Job Submission
•
Test 2: Submit a Job Using Folder Attendant
•
Test 3: Verify a Licensed Feature is Enabled
Test 1: Submit a Job Using File Job Submission
Before You Begin
•
In the C:\ProgramFiles\QuickTime folder, select Sample.mov, and copy the file to the C:\Media
folder.
•
In the C:\media folder, make one copy of the Sample.mov file for each Resource Node in the group.
For example, if you have four nodes, make four copies.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
2-22
OL-21554-01
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Verifying Resource Manager Deployment
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Procedure
Step 1
Access the UI. See also: Accessing the Cisco MXE 3500 Web User Interface.
Step 2
From the Toolbox, expand Submission, and click File. The File Job Submission page displays.
Step 3
In the Profile section, choose Cable_Broadband.job.awp.
Step 4
In the Input section, complete the following tasks:
a.
Click Browse.
b.
Browse to \\Resource_Mananger_IP_Address\media and select all the copies of the Sample.mov
file.
c.
Click Add File(s) to move files from your media directory to the Media Source box.
Step 5
Click Submit.
Step 6
From the toolbox, select View > Monitoring > Job Status.
Step 7
Continue watching the Job Status window to make sure the job completes.
Step 8
Browse to \\Resource_Mananger_IP_Address\output, locate the multiple
FileName.Sample.Cable_Broadband.Cable_Broadband.wmv files, and play the files. Accept any
warning messages or alerts Windows Media Player may display.
Step 9
To determine which transcoding job a Resource Node has completed, log in to a Resource Node and
browse to the C:\ProgramFiles\Cisco\Media Experience Engine\log folder. Then, Open the LCS log
for the current date, and search for “PP Input” to see the files were transcoded by that particular
Resource Node.
Test 2: Submit a Job Using Folder Attendant
Before You Begin
•
In the C:\ProgramFiles\QuickTime folder, select Sample.mov, and copy the file to the C:\Media
folder.
•
In the C:\media folder, make one copy of the Sample.mov file for each Resource Node in the group.
For example, if you have four nodes, make four copies.
Procedure
Step 1
Access Folder Attendant. See also: Accessing the Cisco MXE 3500 Tools.
Step 2
Add a directory for the Folder Attendant to monitor.
Step 3
a.
From the Toolbox, click 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 C:\media and complete other fields as needed.
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
2-23
Chapter 2
Deploying Cisco MXE 3500 in Resource Manager Configuration
Verifying Resource Manager Deployment
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
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
Drag all the copies of the Sample.mov file from the C:\media folder to the
\\Resource_Mananger_IP_Address\watch folder.
Step 6
Watch the Job Status pane to make sure the job starts and completes.
Step 7
Browse to \\Resource_Mananger_IP_Address\output, locate the multiple
FileName.Sample.Cable_Broadband.Cable_Broadband.wmv files, and play the files. Accept any
warning messages or alerts Windows Media Player may display.
Step 8
To determine which transcoding job a Resource Node has completed, log in to a Resource Node and
browse to the C:\ProgramFiles\Cisco\Media Experience Engine\log folder. Then, Open the LCS log
for the current date, and search for “PP Input” to see the files were transcoded by that particular
Resource Node.
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 3-3
– Configuration Workflow for Cisco MXE 3500 Deployments with Live Flash8 and H.264 IP
Streaming, page 3-5
•
To verify that the Speech to Text or Graphics Overlay feature is enabled after you install a feature
license, see the following sections:
– Configuration Workflow for Speech-to-Text Conversion, page 3-7
– Configuration Workflow for the Graphic Overlay Feature, page 3-9
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
2-24
OL-21554-01
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
CH A P T E R
3
Deploying Licensed Features for Cisco MXE 3500
Revised: April 26, 2011, OL-21554-01
This chapter includes the following sections:
•
Live Streaming (IP Capture) Feature, page 3-1
•
Speech-to-Text and Graphics Overlay Features, page 3-6
Live Streaming (IP Capture) Feature
The Live Streaming (IP capture) feature enables the Cisco MXE 3500 to ingest live enterprise TV and
IPTV 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.
This section includes the following topics:
•
Required Components for the Live Streaming Feature, page 3-2
•
Network Design for Cisco MXE 3500 Deployments with Live WMV IP Streaming, page 3-3
•
Configuration Workflow for Cisco MXE 3500 Deployments with Live WMV IP Streaming,
page 3-3
•
Network Design for Cisco MXE 3500 Deployments with Live Flash 8 and H.264 IP Streaming,
page 3-4
•
Configuration Workflow for Cisco MXE 3500 Deployments with Live Flash8 and H.264 IP
Streaming, page 3-5
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
3-1
Chapter 3
Deploying Licensed Features for Cisco MXE 3500
Live Streaming (IP Capture) Feature
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Required Components for the Live Streaming Feature
In addition to a Live Streaming feature license, the following components are required:
Note
1.
Ingest (Input), page 3-2
2.
Job Profile (Transcode), page 3-2
3.
Distribution (Output), page 3-2
See the Release Notes for Cisco MXE 3500 Release 3.0 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)
TheCisco 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)
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
3-2
OL-21554-01
Chapter 3
Deploying Licensed Features for Cisco MXE 3500
Live Streaming (IP Capture) Feature
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
•
Flash8 and H.264—Commercial Content Delivery Network (CDN) services available from the
following sources:
– Akamai
– Limelight
– Internap
Network Design for Cisco MXE 3500 Deployments with Live WMV IP Streaming
Figure 3-1 shows an example solution network for a Cisco MXE 3500 deployment with WMV IP
streaming and Cisco Wide Area Application Services (WAAS).
Figure 3-1
Example Solution Network for WMV IP Streaming Using Cisco WAAS
Client PULLs
Stream
Client
Client PULLs
Stream
Client
Client PULLs
Stream
Client
WAN
LAN
Multicast Video
Stream
Windows
2008
Cisco
MXE Streaming Enterprise
Server
Server
3500
PULLs
Stream
V
LAN
V
277792
WAAS WAN
Acceleration
Cisco WAAS
Central
Manager
Cisco
WAE 612
Cisco 574
WAE
Configuration Workflow for Cisco MXE 3500 Deployments with Live WMV IP
Streaming
Note
For information about using the web UI, see the User Guide for Cisco MXE 3500 Release 3.0.
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:
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
3-3
Chapter 3
Deploying Licensed Features for Cisco MXE 3500
Live Streaming (IP Capture) Feature
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
•
microsoftAudioStream
•
microsoftStream
See also: “Removing Workers from a Host” in the user guide.
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 3-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.
Network Design for Cisco MXE 3500 Deployments with Live Flash 8 and H.264
IP Streaming
Figure 3-3 shows an example solution network for a Cisco MXE 3500 deployment with Flash 8 IP
streaming and a content distribution network (CDN).
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
3-4
OL-21554-01
Chapter 3
Deploying Licensed Features for Cisco MXE 3500
Live Streaming (IP Capture) Feature
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Figure 3-3
Example Solution Network for Flash8 and H.264 IP streaming Using CDN
Client PULLs
Stream
Client
Client PULLs
Stream
Client
Client PULLs
Stream
Client
CDN
LAN
Multicast Video
Stream
Cisco
MXE
3500
LAN
V
277791
V
Adobe
FMS
PUSHes Streaming
Stream to Server
Streaming
Server
Configuration Workflow for Cisco MXE 3500 Deployments with Live Flash8 and
H.264 IP Streaming
Note
For information about using the web UI, see the User Guide for Cisco MXE 3500 Release 3.0.
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.
a. Create a new Profile.
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
3-5
Chapter 3
Deploying Licensed Features for Cisco MXE 3500
Speech-to-Text and Graphics Overlay Features
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Figure 3-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.
Speech-to-Text and Graphics Overlay Features
The Speech-to-Text feature enables the Cisco MXE 3500 to create text transcripts from videos, and the
Graphics Overlay feature enables the Cisco MXE 3500 to embed the transcripts as text captions in the
video.
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.
This section includes the following topics:
•
Overview of the Speech-to-Text and Graphic Overlay Features, page 3-6
•
Required Components for the Speech-to-Text and Graphic Overlay Features, page 3-7
•
Configuration Workflow for Speech-to-Text Conversion, page 3-7
•
Configuration Workflow for the Graphic Overlay Feature, page 3-9
•
Guidelines for Improving the Accuracy of Speech to Text, page 3-9
•
Importing a Speech Profile to Cisco MXE 3500, page 3-10
Overview of the Speech-to-Text and Graphic Overlay Features
The 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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
3-6
OL-21554-01
Chapter 3
Deploying Licensed Features for Cisco MXE 3500
Speech-to-Text and Graphics Overlay Features
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
•
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 3-5 illustrates the process that the Cisco MXE 3500 uses for speech-to-text conversion and the
overlay function.
Figure 3-5
Process for the Speech-to-Text Conversion and Graphic Overlay Function
NUANCE
Nuance Speaker
Profile
Nuance
Vocabulary
Content SWF
Template
Graphics Template
.xml
Content XML
Script
Source
Prefilter
STT
Worker
.TXT
Source
Prefilter
Flash8
Worker
.FLV
277795
.WAV
.XML
Speech-To-Text Job:
Extracts audio and creates STT files
Note
Graphics Overlay/Captioning Job:
Creates output with STT transcript
overlaid as a graphic
The speech-to-text conversion and the graphic overlay function require separate job profiles.
Required Components for the Speech-to-Text and Graphic Overlay Features
The 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
Configuration Workflow for Speech-to-Text Conversion
The 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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
3-7
Chapter 3
Deploying Licensed Features for Cisco MXE 3500
Speech-to-Text and Graphics Overlay Features
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Note
For information about using the web UI, see the User Guide for Cisco MXE 3500 Release 3.0.
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.
a. Create a new Profile.
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
Figure 3-6
Speech-to-Text Encoder Settings
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
3-8
OL-21554-01
Chapter 3
Deploying Licensed Features for Cisco MXE 3500
Speech-to-Text and Graphics Overlay Features
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Configuration Workflow for the Graphic Overlay Feature
The 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 Guide for Cisco MXE 3500 Release 3.0.
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
Guidelines for Improving the Accuracy of Speech to Text
This section includes the following topics:
•
Speech Input Style, page 3-9
•
Multiple Speakers in a Video, page 3-10
•
Speech Profiles, page 3-10
•
Methods for Acquiring Audio, page 3-10
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).
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
3-9
Chapter 3
Deploying Licensed Features for Cisco MXE 3500
Speech-to-Text and Graphics Overlay Features
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
•
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 3-10.
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).
•
Desktop video creation and video blogging: When recording media for desktop video, use a
noise-cancelling headset.
Importing a Speech Profile to Cisco MXE 3500
You 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
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
3-10
OL-21554-01
Chapter 3
Deploying Licensed Features for Cisco MXE 3500
Speech-to-Text and Graphics Overlay Features
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
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 4
Right-click the .zip file and choose Extract.
Step 5
Follow the on-screen prompts to uncompress the speaker 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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
3-11
Chapter 3
Deploying Licensed Features for Cisco MXE 3500
Speech-to-Text and Graphics Overlay Features
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
3-12
OL-21554-01
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
CH A P T E R
4
Security Best Practices and Backup Guidelines
for Cisco MXE 3500
Revised: March 12, 2010, OL-21554-01
This section includes the following topics:
•
Security Best Practices for Cisco MXE 3500, page 4-1
•
Windows Services, page 4-2
•
Backup Guidelines for Cisco MXE 3500, page 4-5
Security Best Practices for Cisco MXE 3500
Cisco MXE 3500 ships with Windows 2003 Server settings that ensure 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 Microsoft Hot
Fix Release Policy, page 4-2.
•
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. See also: Backing Up Cisco MXE 3500, page 4-6.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
4-1
Chapter 4
Security Best Practices and Backup Guidelines for Cisco MXE 3500
Cisco MXE 3500 Microsoft Hot Fix Release Policy
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Cisco MXE 3500 Microsoft Hot Fix Release Policy
Microsoft 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 Services
Table 4-1 lists Cisco MXE 3500 Windows 2003 Server services and startup types.
Note
Configuration of only the DHCP Client service is supported.
Table 4-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
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
4-2
OL-21554-01
Chapter 4
Security Best Practices and Backup Guidelines for Cisco MXE 3500
Windows Services
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 4-1
Windows 2003 Server Services on the Cisco MXE 3500 (continued)
Service Name
Startup Type
DHCP Client
Automatic
Note
Administrators can configure
the DHCP Client service.
Distributed File System
Manual—Not started
Distributed Link Tracking Client
Automatic
Distributed Link Tracking Server
Disabled
Distributed Transaction Coordinator
Automatic
DNS Client
Automatic
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
Net Logon
Manual
Net .tcp port Sharing 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
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
4-3
Chapter 4
Security Best Practices and Backup Guidelines for Cisco MXE 3500
Windows Services
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 4-1
Windows 2003 Server Services on the Cisco MXE 3500 (continued)
Service Name
Startup Type
Performance Logs and Alerts
Automatic
Plug and Play
Automatic
Portable Media Serial Number Service
Manual
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
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
4-4
OL-21554-01
Chapter 4
Security Best Practices and Backup Guidelines for Cisco MXE 3500
Backup Guidelines for Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 4-1
Windows 2003 Server Services on the Cisco MXE 3500 (continued)
Service Name
Startup Type
Virtual Shadow Copy
Manual
WebClient
Disabled
Windows Audio
Automatic
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
Backup Guidelines for Cisco MXE 3500
Cisco MXE 3500 ships with a recovery DVD that enables you to restore the software to its default
factory configuration by performing a system recovery; however, the following changes are lost during
the recovery process:
Note
•
Folder Attendant configuration, including Watch settings
•
Changes made to default profiles
•
New profiles
•
Media files that are stored in input, output, and watch directories
•
License file
•
Custom speaker profiles
•
Custom graphic overlay files
Currently, you cannot back up automatically any configuration changes that you make at the
http://host/mxeUI/ URL, including—but not limited to—new user accounts, licenses, limit and threshold
configuration, input and output directory locations, the SMTP server address, and administrator e-mail
accounts. You should write down any changes that you make.
We recommend that you back up periodically. Backup frequency depends on how often you use
Cisco MXE 3500: you must determine the optimal frequency for your organization to avoid losing
valuable data. At a minimum, we recommend that you back up at least once a month because a recovery
will require restoring Cisco MXE 3500 to its factory image,
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
4-5
Chapter 4
Security Best Practices and Backup Guidelines for Cisco MXE 3500
Backup Guidelines for Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Backing Up Cisco MXE 3500
This section includes the following topics:
•
Backing Up the Folder Attendant Database, page 4-6
•
Backing Up Cisco MXE 3500 Files, page 4-6
Backing Up the Folder Attendant Database
To ensure that configuration changes are saved, use this procedure to back up the Folder Attendant
configuration database, which is named NCS, by using SQL Server Management Studio Express. SQL
Server Management Studio Express Version 2005 comes installed on Cisco MXE 3500.
Procedure
Step 1
Log in to Cisco MXE 3500.
Step 2
Click Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio Express
and connect to the Cisco MXE 3500 that you want to back up.
Step 3
In Object Explorer area, double-click Databases.
Step 4
Right-click NCS and choose Tasks > Back Up. The General page in the Back Up Database window
appears.
Step 5
Identify the source and destination for the backup:
Step 6
a.
In the Source area, verify that NCS appears in Database field; then, choose Full as the Backup type.
b.
In the Destination area, choose Disk or Tape.
c.
Click Add. The Select Backup Destination dialog appears. We recommend that you do not change
the default path.
d.
Enter a file name with a .bak extension, such as NCS.bak.
e.
Click OK..
Choose the overwrite and reliability settings:
a.
In the Select a page area, click Options.
b.
In the Overwrite media area, choose Overwrite all existing backup sets.
c.
In the Reliability area, check Verify backup once finished.
Step 7
Click OK to start the backup. A dialog box displays the status of the backup.
Step 8
When complete, exit Microsoft SQL Management Studio Express.
Backing Up Cisco MXE 3500 Files
Use this procedure to back up the files that are not contained in the Folder Attendant configuration
database.
Procedure
Step 1
Log in to Cisco MXE 3500.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
4-6
OL-21554-01
Chapter 4
Security Best Practices and Backup Guidelines for Cisco MXE 3500
Backup Guidelines for Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Step 2
Back up all the files in the license directory. The default location is C:\Program Files\Cisco\media
Experience Engine\license.
Step 3
Back up all the files in the profiles directory. The default location is C:\Program Files\Cisco\media
Experience Engine\profiles.
Step 4
Back up any custom speech-to-text speaker profile folders. The default location is C:\Documents and
Settings\All Users\Application Data\Nuance\Dragon SDK Server Edition10\Users\.
Step 5
Back up any custom graphic overlay files (SWF files) and content XML scripts for speech to text. The
default location is C:\media\SpeechToTextFiles.
Step 6
Launch Internet Explorer and log in to the WebUI at http://host/MxeUI/.
Step 7
Choose Administration > System. The System Settings Administration page displays.
Step 8
Note the locations of the directories in the Input and Output sections.
Step 9
Back up the files in those directories.
Restoring Cisco MXE 3500 Configuration
This section includes the following topics:
•
Recovering Cisco MXE 3500, page 4-7
•
Restoring the Folder Attendant Database, page 4-7
•
Restoring Other Cisco MXE 3500 Files, page 4-8
Recovering Cisco MXE 3500
Recover the Cisco MXE 3500 by following the recovery process in Chapter 7, “Recovering
Cisco MXE 3500.”
Restoring the Folder Attendant Database
Use this procedure to restore a previously backed up Folder Attendant database by using SQL Server
Management Studio Express Version 2005, which comes installed on Cisco MXE 3500.
Before You Begin
The backup file that you use to restore must be from a backup that was taken from the same
Cisco MXE 3500. To restore a backup from a different Cisco MXE 3500, contact Cisco Technical
Support.
Procedure
Step 1
Log in to Cisco MXE 3500.
Step 2
Stop and disable Cisco MXE Services:
a.
Click Start > Settings > Control Panel > Administrative Tools > Services. The Services window
appears.
b.
Right-click MXE Folder Attendant and choose Stop.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
4-7
Chapter 4
Security Best Practices and Backup Guidelines for Cisco MXE 3500
Backup Guidelines for Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
c.
Right-click MXE Folder Attendant and choose Properties.
d.
In the Startup type drop-down list, choose Disable.
e.
Click OK.
f.
Repeat Step b to Step e for the MXE CAM, MXE ECS, MXE Log Service, and MXE Encoder
services.
g.
Close the Control Panel.
Step 3
Click Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio Express
and connect to the Cisco MXE 3500 that you want to restore.
Step 4
Delete the existing Folder Attendant database:
Step 5
a.
In Object Explorer area, double-click Databases.
b.
Right-click NCS and choose Delete.
c.
Click OK in the Delete Object window.
Restore the Folder Attendant database from the backup file:
a.
In the Object Explorer area, right-click Databases and choose Restore Database. The General page
in the Restore Database window appears.
b.
In the Destination for restore area, choose or enter NCS in the To database field.
c.
In the Source for restore area, choose From Device and click the ... button. A Specify Back Up
window appears.
d.
From the Backup media drop-down menu, choose File.
e.
Click Add, navigate to the backup file from which to restore, and click OK.
f.
Click OK in the Specify Backup window.
g.
In the Select the backup sets to restore area, check the checkbox next to the file.
h.
Click OK in the Restore Database window. When complete, a completed successfully message
appears.
Step 6
Exit Microsoft SQL Management Studio Express.
Step 7
Enable Cisco MXE 3500 services:
a.
Click Start > Settings > Control Panel > Administrative Tools > Services. The Services window
appears.
b.
Right-click MXE Folder Attendant and choose Start.
c.
Right-click MXE Folder Attendant and choose Properties.
d.
In the Startup type drop-down list, choose Enable.
e.
Click OK.
f.
Repeat Step b to Step e for the MXE CAM, MXE ECS, MXE Log Service, and MXE Encoder
services.
g.
Close the Control Panel.
Restoring Other Cisco MXE 3500 Files
Use this procedure to restore other files that are not contained in the Folder Attendant database.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
4-8
OL-21554-01
Chapter 4
Security Best Practices and Backup Guidelines for Cisco MXE 3500
Backup Guidelines for Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Procedure
Step 1
Log in to Cisco MXE 3500.
Step 2
Restore the most recently backed up license file to the license directory. The default location is
C:\Program Files\Cisco\Media Experience Engine\license.
Step 3
Restart Cisco MXE 3500.
Step 4
Restore the most recently backed up profiles to the profiles directory. The default location is C:\Program
Files\Cisco\Media Experience Engine\profiles.
Step 5
Restore the most recently backed up custom speech-to-text speaker profile folders. The default location
is C:\Documents and Settings\All Users\Application Data\Nuance\Dragon SDK Server
Edition10\Users\.
Step 6
Restore the most recently backed up custom graphic overlay files (SWF files) and content XML scripts
for speech to text. The default location is C:\media\SpeechToTextFiles.
Step 7
Launch Internet Explorer and log in to the WebUI at http://host/MxeUI/.
Step 8
Choose Administration > System. The System Settings Administration page displays.
Step 9
Enter the locations for the directories in the Input and Output sections.
Step 10
Restore the contents of all those directories from the most recent backup.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
4-9
Chapter 4
Security Best Practices and Backup Guidelines for Cisco MXE 3500
Backup Guidelines for Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
4-10
OL-21554-01
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
CH A P T E R
5
Upgrading Cisco MXE 3500 from a Standalone
Device
Revised: January 26, 2010, OL-21554-01
Caution
We recommend that you copy any files that you want to keep to a location outside of the
Cisco MXE 3500 before you upgrade.
This section includes the following topics:
•
Guidelines for Upgrades, page 5-1
•
Upgrading Cisco MXE 3500 from a Standalone to Resource Manager Device, page 5-1
•
Upgrading a Cisco MXE 3500 from a Standalone to a Resource Node Device, page 5-6
•
Adding a New Resource Node to an Existing Resource Manager Deployment, page 5-10
Guidelines for Upgrades
Before you upgrade, consider the following guidelines:
•
Before you upgrade, save any locally stored source content to a location that is not on your
Cisco MXE 3500.
•
If you want to return a Cisco MXE 3500 back to its original device type, you must perform a
software recovery on the device, and if returning back to standalone or Resource Manager device,
you must reinstall the original license. See also: Recovering Cisco MXE 3500, page 7-1.
•
Before you upgrade, save your original license to a location that is not on your Cisco MXE 3500.
This license is required to re-enable features on your standalone or Resource Manager device if you
return the Cisco MXE 3500 back to its original device type.
Upgrading Cisco MXE 3500 from a Standalone to
Resource Manager Device
This section includes the following topics:
•
Preparing for Upgrade, page 5-2
•
Obtaining a License for the Upgrade to Resource Manager, page 5-3
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
5-1
Chapter 5
Upgrading Cisco MXE 3500 from a Standalone Device
Upgrading Cisco MXE 3500 from a Standalone to Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
•
Upgrading the Resource Manager Device, page 5-3
•
Completing Resource Manager Upgrade Configuration, page 5-5
Preparing for Upgrade
Note
Ensure that you understand the configuration differences between standalone and Resource Manager
deployments. See also: Guidelines for Resource Manager Deployments, page 2-2.
It is important to back up the Job Profiles, license file, and content that is on the device before upgrading
your system. To prepare for upgrade, complete the tasks in Table 5-1.
Table 5-1
Preparation Tasks for Upgrading from Standalone to Resource Manager Deployment
To Back Up ...
Complete This Task
Job Profiles
Copy the profile directory to a location that is not on your Cisco MXE 3500.
The profile directory is located here: C:\Program Files\Cisco\Media
Experience Engine\profiles
License File
Copy the mxe.lic file to a location that is not on your Cisco MXE 3500.
The license file is located here: C:\Program Files\Cisco\Media Experience
Engine\license\mxe.lic
Note
Source Content
Back up the license to use if you return Cisco MXE 3500 to a
standalone deployment. Be aware that as part of the upgrade process
you obtain a new license and install it on the Resource Manager device.
Copy all watermark files and video files to a location that is not on your
Cisco MXE 3500.
The Cisco MXE 3500 was configured originally so that source content files are
located in the C:\media directory.
Output Content
Copy all watermark files and video files to a location that is not on your
Cisco MXE 3500.
The Cisco MXE 3500 was configured so that encoded files are located in the
C:\output directory.
E-mail Server
Settings
Folder Attendant
Configuration
Open the System Settings Administration page (from the Toolbox, click
Administration > System) and note the following settings:
•
E-mail Settings
•
SMTP Server Settings
Copy the faConfig.xml file to a location that is not on your Cisco MXE 3500.
The faConfig.xml file is located here: C:\Program Files\Cisco\Media
Experience Engine\Folder Attendant\bin\
Note
All watch directories that are located on the Cisco MXE 3500 device
will be deleted as part of the upgrade process.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
5-2
OL-21554-01
Chapter 5
Upgrading Cisco MXE 3500 from a Standalone Device
Upgrading Cisco MXE 3500 from a Standalone to Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 5-1
Preparation Tasks for Upgrading from Standalone to Resource Manager Deployment
To Back Up ...
Complete This Task
Services
Open each of the following Cisco MXE 3500 Services, and view each user
account the system is running under. If any account has changed from the
default, MXE-Service, note the name of the user account.
•
IIS Admin Service
•
Mxe CAM
•
Mxe ECS
•
Mxe Encoder
•
Mxe Folder Attendant
•
Mxe Log Service
Temp Directory
All of the files in the C:\temp directory can be discarded. Deleting all files in
the Temp directory is a normal maintenance step.
Speech-to-Text Files
Copy any custom speaker profiles to a location that is not on your
Cisco MXE 3500.
Speaker profiles are located here: C:\Documents and Settings\All
Users\Application Data\Nuance\Dragon SDK Server Edition10\Users\
Graphic Overlay Files Copy any custom graphics templates, content XML scripts, and SWF templates
to a location that is not on your Cisco MXE 3500.
These files are located here: C:\media\SpeechToTextFiles
Obtaining a License for the Upgrade to Resource Manager
When you upgrade a standalone Cisco MXE 3500 to a Resource Manager device, you must use the
same MAC address of the standalone Cisco MXE 3500 that you used to obtain the original license.
After you obtain a new license for the Resource Manager and its Resource Nodes, you will install the
license on the Resource Manager.
For information about obtaining a Resource Manager license and licensing requirements, see the
“Obtaining the License for the Resource Manager” section on page 2-6.
Upgrading the Resource Manager Device
This section includes the following topics:
•
Obtaining the Upgrade Software, page 5-3
•
Performing the Upgrade to Resource Manager, page 5-4
Obtaining the Upgrade Software
The software to upgrade a standalone Cisco MXE 3500 Release 3.0 configuration to either a
Resource Manager or Resource Node configuration is contained in a single software package. When you
perform the upgrade, you will choose the Cisco MXE 3500 configuration to which you are upgrading.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
5-3
Chapter 5
Upgrading Cisco MXE 3500 from a Standalone Device
Upgrading Cisco MXE 3500 from a Standalone to Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
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 Processing > Cisco MXE 3500 Software (Media Experience Engine).
Step 4
Click Latest Releases > 3.0.0 > MXE 3500 Release 3.0.0 Resource Manager Upgrade. The links to
the software are on the right side of the browser window.
Step 5
Save MXE3K-R3-0-UPG.zip 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 upgrade.
Step 6
Proceed to the “Performing the Upgrade to Resource Manager” procedure on page 5-4.
Performing the Upgrade to Resource Manager
Use this procedure to upgrade a standalone Cisco MXE 3500 Release 3.0 configuration to a
Resource Manager configuration.
Before You Begin
•
Complete the “Preparing for Upgrade” procedure on page 5-2.
•
Complete the “Obtaining the Upgrade Software” procedure on page 5-3.
•
Close any applications that are running on the Cisco MXE 3500 you are upgrading.
Procedure
Step 1
Log in to the Cisco MXE 3500 that you are upgrading.
Step 2
Create a new folder from where you will perform the upgrade, such as C:\upgrade, which is used as an
example in this procedure.
Step 3
Copy MXE3K-R3-0-UPG.zip to the folder that you created in Step 2.
Step 4
Right click MXE3K-R3-0-UPG.zip and click Extract All.
Step 5
Click Next twice.
Step 6
Click Finish.
Step 7
Open a command prompt window.
Step 8
At the command prompt, enter cd C:\upgrade\MXE3K-R3-0-UPG and then enter Upgrade-Patch.bat.
Step 9
At the command prompt, enter RM. The upgrade process proceeds and shows a “RM upgrade patch
installation complete” message when through.
After the upgrade process completes, the Cisco MXE 3500 shows a dialog box that informs you about
an automatic restart. Do not click or type anything; wait for the restart to complete. Then, the software
upgrade is finished.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
5-4
OL-21554-01
Chapter 5
Upgrading Cisco MXE 3500 from a Standalone Device
Upgrading Cisco MXE 3500 from a Standalone to Resource Manager Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Step 10
Step 11
If you installed the original Cisco MXE 3500 standalone configuration license file, mxe.lic, in
C:\Program Files\Cisco\Media Experience Engine\license (default file name and installation location),
the upgrade process creates a new folder and moves that original license to C:\Program
Files\Cisco\Media Experience Engine\license\OldStandaloneLicense. If you changed either the default
file name or the installation location, you must complete the following steps to avoid incorrect operation:
a.
Rename or save the current standalone license file to another folder.
b.
When you install the license on the Resource Manager, ensure that you place the Resource Manager
configuration license file to the same location with the same name as the changed license
configuration.
Proceed to the “Completing Resource Manager Upgrade Configuration” procedure on page 5-5.
Completing Resource Manager Upgrade Configuration
To complete the upgrade configuration, complete the tasks in Table 5-2. After you complete these steps,
your Cisco MXE 3500 Resource Manager will be ready to use.
Table 5-2
Tasks for Upgrade
To Configure ...
Complete This Task
Job Profiles
On the Resource Manager device, ensure that all your profiles are unchanged.
Otherwise, copy the backed up profiles here: C:\Program Files\Cisco\Media
Experience Engine\profiles
You may wish to run some test jobs first by using one of your original Job
Profiles.
License File
1.
Obtain a Resource Manager license. See also: Obtaining a License for the
Upgrade to Resource Manager, page 5-3.
2.
Install the Resource Manager license. See also: Installing the License on
the Resource Manager, page 2-8.
Your Cisco MXE 3500 will not run without a license file.
Note
E-mail Server
Settings
1.
Log into the UI on the Resource Manager device by using the following
credentials:
•
Login User Name: admin
•
Password: admin
See also: Accessing the Cisco MXE 3500 Web User Interface, page 1-2.
2.
Services
Open the System Settings Administration page (from the Toolbox, click
Administration > System) and confirm or correct the SMTP server and
e-mail information you documented when preparing for upgrade.
Confirm that all the Cisco MXE 3500 Services are running under an account
documented in the “Preparing for Upgrade” procedure on page 5-2.
Note
MXE Service must have read/write access to all configured UNC paths
and to IIS.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
5-5
Chapter 5
Upgrading Cisco MXE 3500 from a Standalone Device
Upgrading a Cisco MXE 3500 from a Standalone to a Resource Node Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 5-2
Tasks for Upgrade (continued)
To Configure ...
Folder Attendant
Configuration
Complete This Task
1.
On the Resource Manager device, copy the backed up Folder Attendant
configuration file faConfig.xml to the directory: C:\Program
Files\Cisco\Media Experience Engine\Folder Attendant\bin\
2.
If the directories do not appear online, confirm that the user account the
Cisco MXE 3500 Folder Attendant service is running under has
permissions to read and write to the watch directory.
Note
3.
The Folder Attendant may not function correctly until you restore all
of your encoding profiles and watch directories that are on the system.
After you have installed the license file and the Folder Attendant
configuration file, reboot the Cisco MXE 3500.
See also: Creating a Folder Attendant Directory and Watch, page 1-10.
Resource Manager
Configuration
On the Resource Manager device, configure the System settings and Hosts
settings for the Resource Manager deployment.
See also: Using Administrative Tools to Configure the Resource Manager
Device, page 2-9.
Source Content
Copy the backed up source content to the UNC path that you configured in the
System settings Input section on the Resource Manager device.
See also: Input Section, page 2-16.
Speech-to-Text Files
Copy any custom speaker profiles to this directory: C:\Documents and
Settings\All Users\Application Data\Nuance\Dragon SDK Server
Edition10\Users\
Graphic Overlay Files Copy any custom graphics templates, content XML scripts, and SWF templates
this directory: C:\media\SpeechToTextFiles
Upgrading a Cisco MXE 3500 from a Standalone to a
Resource Node Device
This section includes the following topics:
•
Preparing for Upgrade, page 5-6
•
Obtaining a License for the Upgrade to Resource Node, page 5-8
•
Upgrading the Resource Node Device, page 5-9
Preparing for Upgrade
Note
Ensure that you understand the configuration differences between standalone and Resource Manager
deployments. See also: Guidelines for Resource Manager Deployments, page 2-2.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
5-6
OL-21554-01
Chapter 5
Upgrading Cisco MXE 3500 from a Standalone Device
Upgrading a Cisco MXE 3500 from a Standalone to a Resource Node Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
It is important to back up the Job Profiles, license file, and content that is on the device before upgrading
your system. To prepare for upgrade, complete the tasks in Table 5-1.
Table 5-3
Preparation Tasks for Upgrading from Standalone to Resource Node
To Back Up ...
Complete This Task
Job Profiles
Copy the profile directory to a location that is not on your Cisco MXE 3500.
The profile directory is located here: C:\Program Files\Cisco\Media
Experience Engine\profiles
License File
Copy the mxe.lic file to a location that is not on your Cisco MXE 3500.
The license file is located here: C:\Program Files\Cisco\Media Experience
Engine\license\mxe.lic
Note
Source Content
Back up the license to use if you return Cisco MXE 3500 to a
standalone deployment. Be aware that you must obtain a new license
for this deployment and install it on the Resource Manager device.
Copy all watermark files and video files to a location that is not on your
Cisco MXE 3500.
The Cisco MXE 3500 was configured originally so that source content files are
located in the C:\media directory.
Output Content
Copy all watermark files and video files to a location that is not on your
Cisco MXE 3500.
The Cisco MXE 3500 was configured so that encoded files are located in the
C:\output directory.
E-mail Server
Settings
Folder Attendant
Configuration
Open the System Settings Administration page (from the Toolbox, click
Administration > System) and note the following settings:
•
E-mail Settings
•
SMTP Server Settings
Copy the faConfig.xml file to a location that is not on your Cisco MXE 3500.
The faConfig.xml file is located here: C:\Program Files\Cisco\Media
Experience Engine\Folder Attendant\bin
Note
Services
Temp Directory
All watch directories that are located on the Cisco MXE 3500 device
will be deleted as part of the upgrade process.
Open each of the following Cisco MXE 3500 Services, and view each user
account the system is running under. If any account has changed from the
default, MXE-Service, note the name of the user account.
•
IIS Admin Service
•
Mxe CAM
•
Mxe ECS
•
Mxe Encoder
•
Mxe Folder Attendant
•
Mxe Log Service
All of the files in the C:\temp directory can be discarded. Deleting all files in
the Temp directory is a normal maintenance step.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
5-7
Chapter 5
Upgrading Cisco MXE 3500 from a Standalone Device
Upgrading a Cisco MXE 3500 from a Standalone to a Resource Node Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 5-3
Preparation Tasks for Upgrading from Standalone to Resource Node (continued)
To Back Up ...
Complete This Task
Speech-to-Text Files
Copy any custom speaker profiles to a location that is not on your
Cisco MXE 3500.
Speaker profiles are located here: C:\Documents and Settings\All
Users\Application Data\Nuance\Dragon SDK Server Edition10\Users\
Graphic Overlay Files Copy any custom graphics templates, content XML scripts, and SWF templates
to a location that is not on your Cisco MXE 3500.
These files are located here: C:\media\SpeechToTextFiles
Obtaining a License for the Upgrade to Resource Node
When you upgrade a standalone Cisco MXE 3500 to a Resource Node, you must use the same MAC
address of the Resource Manager device that you used to obtain the original license. After you obtain
a new license, you will install it on the Resource Manager to integrate the Resource Node into the group.
Before You Begin
•
You must have an account on Cisco.com to access the license website.
•
Obtain the Cisco MXE 3500 MAC address of the Resource Manager device. You must use the same
MAC address of the Resource Manager device that you used to obtain the original license. See
also: Obtaining the MAC Address, page 1-3.
•
Obtain the Product Authorization Key (PAK) for the Resource Node, which is located on the
Software License Claim Certificates that shipped with your devices.
Procedure
Step 1
Go to http://www.cisco.com/go/license.
Step 2
Enter the PAK for the Resource Node.
Step 3
If you are using the Resource Manager device to access the registration website, press the Enter key;
otherwise, click the Submit button.
Step 4
Follow the on-screen prompts and ensure that you use the MAC address from the Resource Manager
device when prompted.
Step 5
After registration, you will receive an e-mail with the license file.
Step 6
Save the license file; you will install this license on the Resource Manager device, as it includes a valid
license for the Resource Manager device and each Resource Node in the group. For information about
installing the license, see the “Installing the License on the Resource Manager” section on page 2-8.
Note
We recommend that you save the license file in a secure location. If the license file is lost, it can
take up to one business day to get another copy.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
5-8
OL-21554-01
Chapter 5
Upgrading Cisco MXE 3500 from a Standalone Device
Upgrading a Cisco MXE 3500 from a Standalone to a Resource Node Device
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Upgrading the Resource Node Device
Use this procedure to install the Resource Node software on the Cisco MXE 3500; obtain and install a
new license on the Resource Manager device; and configure the Resource Node on the
Resource Manager device. After you complete these steps, your Resource Node will be ready to use.
Before You Begin
•
Complete the “Preparing for Upgrade” procedure on page 5-6.
•
Complete the “Obtaining a License for the Upgrade to Resource Node” procedure on page 5-8.
•
Complete the “Obtaining the Upgrade Software” procedure on page 5-3.
•
Close any applications that are running on the Cisco MXE 3500 you are upgrading.
Procedure
Step 1
Log in to the Cisco MXE 3500 that you are upgrading.
Step 2
Create a new folder from where you will perform the upgrade, such as C:\upgrade, which is used as an
example in this procedure.
Step 3
Copy MXE3K-R3-0-UPG.zip to the folder that you created inStep 2.
Step 4
Right click MXE3K-R3-0-UPG.zip and click Extract All.
Step 5
Click Next twice.
Step 6
Click Finish.
Step 7
Open a command prompt window.
Step 8
At the command prompt, enter cd C:\upgrade\MXE3K-R3-0-UPG and then enter Upgrade-Patch.bat.
Step 9
At the command prompt, enter RN. The upgrade process proceeds and shows a “RN upgrade patch
installation complete” message when through.
After the upgrade process completes, the Cisco MXE 3500 shows a dialog box that informs you about
an automatic restart. Do not click or type anything; wait for the restart to complete. Then, the software
upgrade is finished.
If you installed the original Cisco MXE 3500 standalone configuration license file, mxe.lic, in
C:\Program Files\Cisco\Media Experience Engine\license (default file name and installation location),
the upgrade process creates a new folder and moves that original license to C:\Program
Files\Cisco\Media Experience Engine\license\OldStandaloneLicense. If you changed either the default
file name or the installation location, the license file remains unchanged.
Step 10
To install the license on the Resource Manager, and configure the Resource Node on the
Resource Manager device, complete the steps in the “Adding a New Resource Node to an Existing
Resource Manager Deployment” section on page 5-10.
Step 11
(Optional) To use the backed up Cisco MXE 3500 standalone configuration on the Resource Manager
device—except the license file that you installed in Step 10—complete the steps in the “Completing
Resource Manager Upgrade Configuration” section on page 5-5.
Note
Do not reinstall the original license file for the standalone Cisco MXE 3500.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
5-9
Chapter 5
Upgrading Cisco MXE 3500 from a Standalone Device
Adding a New Resource Node to an Existing Resource Manager Deployment
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Adding a New Resource Node to an Existing
Resource Manager Deployment
To add a Resource Node to an existing Resource Manager deployment, complete the tasks in Table 5-4.
Table 5-4
Tasks for Adding a Resource Node
To Configure ...
Description
Resource Node
Complete these steps to prepare the new Resource Node for Resource Manager
deployment.
License File
1.
Resource Nodes ship with the same TCP/IP Host name. Change the
TCP/IP Host name to a unique name on this device.
2.
Resource Nodes ship with DHCP enabled. If you use static IP addresses,
disable DHCP and assign an IP address on this device.
Note
Ensure that you understand how Resource Manager licensing works
before you request a new license. See also: Obtaining the License for
the Resource Manager, page 2-6.
Complete these steps to back up the existing license file and to obtain and
install the new license on the Resource Manager device.
1.
Copy the mxe.lic file to a location that is not on your Cisco MXE 3500.
Back up the license to use if you return Cisco MXE 3500 to a standalone
deployment.
The license file is located here: C:\Program Files\Cisco\Media Experience
Engine\license\mxe.lic
2.
Obtain a new Resource Manager license that enables you to configure
another Resource Node. See also: Obtaining a License for the Upgrade to
Resource Node, page 5-8.
3.
Install the new Resource Manager license on the Resource Manager
device. See also: Installing the License on the Resource Manager,
page 2-8.
Note
Resource Manager
Your Cisco MXE 3500 will not enable you to configure this node
without a new license file.
Configure the Hosts settings for this Resource Node on the Resource Manager.
device.
See also: Configuring Hosts Settings for Resource Manager Deployments,
page 2-14.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
5-10
OL-21554-01
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
CH A P T E R
6
Troubleshooting Cisco MXE 3500
Revised: January 26, 2010, OL-21554-01
This section includes the following topics:
•
Logging, page 6-1
•
Troubleshooting, page 6-1
Logging
The 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 6-2
•
Troubleshooting FAQs, page 6-2
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
6-1
Chapter 6
Troubleshooting Cisco MXE 3500
Troubleshooting
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Troubleshooting Steps
To 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 6-1.
2.
Review error messages/codes to identify the problem, file name, and location.
3.
With available logging information, answer the following questions:
4.
•
Is the problem intermittent or consistent?
•
For Resource Manager deployments, does the problem affect only one or all nodes?
Review the following information to isolate the problem:
If the Problem is ...
Consistent
Intermittent
Then, the problem is likely...
One Node
All Nodes
X
—
Local node issue
X
Network or Resource Manager issue
X
X
X
X
X
System-side issue
Local node issue
X
Network issue (connectivity)
See also: Troubleshooting FAQs, page 6-2.
Troubleshooting FAQs
This section includes the following topics:
•
Standalone and Resource Manager Deployments, page 6-2
•
Resource Manager Deployments, page 6-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.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
6-2
OL-21554-01
Chapter 6
Troubleshooting Cisco MXE 3500
Troubleshooting
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
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. Yes. The upgrade requires new software and a new license. See also: Upgrading Cisco MXE 3500
from a Standalone Device, page 5-1.
Q. Why are the Resource Nodes not transcoding after I copied the software license file to the correct
folder on the Resource Manager device?
A. After copying the license file, you must configure all the nodes as Hosts in the Resource Manager.
See also: Configuring Hosts Settings for Resource Manager Deployments, page 2-14.
Q. How can I verify that Resource Manager and Resource Node software is installed properly and that
hardware and software requirements are met?
A. There is PostInstallation.bat file in the C:\Cisco-Batch-Files folder. You can go to command prompt
and run PostInstallation.bat file for PASS/FAIL results.
Q. Can Resource Manager function as Resource Node and execute a trancoding task?
A. Resource Manager does function as one of the Resource Nodes in a group. Resource Manager
executes trancoding 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,
page 1-2.
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 trancoding jobs can run on any
Resource Node. You cannot choose files on a local machine (C:\media). See also: Input Section,
page 2-16.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
6-3
Chapter 6
Troubleshooting Cisco MXE 3500
Troubleshooting
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
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?
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, page 2-19.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
6-4
OL-21554-01
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
CH A P T E R
7
Recovering Cisco MXE 3500
Revised: January 26, 2010, OL-21554-01
Caution
This recovery process resets your Cisco MXE 3500 to the same state and configuration in which it was
delivered to you. All changes and content that has been copied to Cisco MXE 3500 will be deleted. The
recovery process should not be implemented unless all other troubleshooting options have failed.
This section includes the following topics:
•
Preparing for Recovery, page 7-1
•
Recovering the Cisco MXE 3500, page 7-2
•
Restoring the Configuration, page 7-4
Preparing for Recovery
It is important to back up the Job Profiles, license file, and content that is on the device before recovering
your system. To prepare for recovery, complete the tasks in Table 7-1.
Caution
Any files that you want to keep must be copied to a location outside of the Cisco MXE 3500. All files
will be deleted during the restore process.
Table 7-1
Preparation Tasks for Recovery
To Back Up ...
Complete This Task
Job Profiles
Copy the profile directory and any profiles in a personal profile directory to a
location that is not on your Cisco MXE 3500.
The profile directory is located here: C:\Program Files\Cisco\Media
Experience Engine\profiles
License File
Copy the mxe.lic file to a location that is not on your Cisco MXE 3500.
The license file is located here: C:\Program Files\Cisco\Media Experience
Engine\license\mxe.lic
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
7-1
Chapter 7
Recovering Cisco MXE 3500
Recovering the Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 7-1
Preparation Tasks for Recovery
To Back Up ...
Complete This Task
Source Content
Copy all watermark files and video files to a location that is not on your
Cisco MXE 3500.
The Cisco MXE 3500 was configured originally so that source content files are
located in the C:\media directory.
Output Content
Copy all watermark files and video files to a location that is not on your
Cisco MXE 3500.
The Cisco MXE 3500 was configured so that encoded files are located in the
C:\output directory.
E-mail Server
Settings
Folder Attendant
Configuration
Open the System Administration page (from the Toolbox, click
Administration > System) and note the following settings:
•
E-mail Server Settings
•
SMTP Server Settings
Copy the faConfig.xml file to a location that is not on your Cisco MXE 3500.
The faConfig.xml file is located here: C:\Program Files\Cisco\Media
Experience Engine\Folder Attendant\bin
Note
Services
All watch directories that are located on the Cisco MXE 3500 device
will be deleted as part of the recovery process.
Open each of the following Cisco MXE 3500 Services, and view each user
account the system is running under. If any account has changed from the
default, MXE-Service, note the name of the user account.
•
IIS Admin Service
•
Mxe CAM
•
Mxe ECS
•
Mxe Encoder
•
Mxe Folder Attendant
•
Mxe Log Service
Temp Directory
All of the files in the C:\temp directory can be discarded. Deleting all files in
the Temp directory is a normal maintenance step.
Speech-to-Text Files
Copy any custom speech-to-text speaker profile folders to a location that is not
on your Cisco MXE 3500.
Speaker profiles are located here: C:\Documents and Settings\All
Users\Application Data\Nuance\Dragon SDK Server Edition10\Users\
Graphic Overlay Files Copy any custom graphic overlay files (SWF files) and content XML scripts
for speech to text to a location that is not on your Cisco MXE 3500.
These files are located here: C:\media\SpeechToTextFiles
Recovering the Cisco MXE 3500
This section includes the following topics:
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
7-2
OL-21554-01
Chapter 7
Recovering Cisco MXE 3500
Recovering the Cisco MXE 3500
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
•
Disabling the Quiet Boot Setting and Configuring the Hard Drive as RAID-0, page 7-3
•
Installing the Cisco MXE 3500 Software to Recover the Appliance, page 7-4
Disabling the Quiet Boot Setting and Configuring the Hard Drive as RAID-0
Use this procedure to disable quiet boot in the BIOS and configure the hard drive as RAID-0.
Procedure
Step 1
Power on the Cisco MXE 3500.
Step 2
Press F2 to enter BIOS Setup. If you miss the option to press F2, reboot the Cisco MXE 3500.
Step 3
In the Main tab, verify that the Quiet Boot setting is Disabled.
Step 4
Step 5
Step 6
•
If the Quiet Boot setting is Disabled, proceed to Step 5 to exit BIOS Setup.
•
If the Quiet Boot setting is Enabled, proceed to Step 4 to disable the setting.
Disable the Quiet Boot setting:
a.
Press the Enter key to display the Quite Boot menus.
b.
Use the arrow key to select Disabled and press Enter.
c.
Press F10.
d.
When the Save and Reset menu displays, use the arrow key to select Yes.
e.
Press Enter. The Cisco MXE 3500 reboots.
f.
Proceed to Step 6
Exit BIOS Setup:
a.
Press the Esc key.
b.
When the Exit Without Saving menu displays, use the arrow key to select Yes.
c.
Press Enter.
d.
Reboot the Cisco MXE 3500.
e.
Proceed to Step 6
Configure Hard Drive as RAID-0:
a.
When prompted at the first boot message, press Ctrl-C to enter the LSI Corp Config Utility.
b.
Press Enter when the Adapter List window displays.
c.
Navigate to RAID Properties by using the arrow keys and press Enter.
d.
Press Enter for the Manage Array option.
e.
Navigate to Delete Array and press Enter.
f.
Press Y. The system deletes the array and automatically exits to the Adaptor Properties window.
g.
Navigate to RAID Properties by using the arrow keys and press Enter.
h.
Navigate to Create IS Volume by using the arrow keys and press Enter. The Create New Array
window displays.
i.
Navigate to No in the Raid Disk column and press the space bar to change the value to Yes in the
Slot 0 row.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
7-3
Chapter 7
Recovering Cisco MXE 3500
Restoring the Configuration
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
j.
Press the down arrow and press the space bar to change the value to Yes in the Slot 1 row.
k.
Press C to create the array.
l.
Navigate to Save changes then exit this menu and press Enter. When the system completes
processing, the Adaptor Properties window displays automatically.
m.
Step 7
Press Esc until you are prompted to exit, navigate to Exit the Configuration Utility and Reboot,
and press Enter. The system reboots and the harddisks are configured to RAID0 configuration.
Proceed to the “Installing the Cisco MXE 3500 Software to Recover the Appliance” procedure on
page 7-4.
Installing the Cisco MXE 3500 Software to Recover the Appliance
Use this procedure to install the Cisco MXE 3500 software and reimage the appliance.
Before You Begin
•
Complete the “Disabling the Quiet Boot Setting and Configuring the Hard Drive as RAID-0”
procedure on page 7-3.
•
Ensure that the Cisco MXE 3500 is powered down.
Procedure
Step 1
Insert the boot disk DVD in the DVD drive.
Step 2
Power on the Cisco MXE 3500. The appliance boots from the DVD.
Step 3
When prompted, click Restore.
Step 4
Remove the DVD.
Step 5
Press the Exit button to continue with installation.
The Cisco MXE 3500 boots twice automatically and goes through the Windows setup.
Step 6
When the dosapp.fon file missing message displays, press Cancel. The installation continues and the
Welcome to Windows logon prompt displays.
Step 7
Enter Administrator as the UserID and press the Enter key for the password.
Step 8
Proceed to the “Restoring the Configuration” section on page 7-4.
Restoring the Configuration
This section includes the following topics:
•
Standalone or Resource Manager Configuration, page 7-5
•
Resource Node Configuration, page 7-6
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
7-4
OL-21554-01
Chapter 7
Recovering Cisco MXE 3500
Restoring the Configuration
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Standalone or Resource Manager Configuration
To restore the configuration on a standalone Cisco MXE 3500 or Resource Manager, complete the tasks
in Table 7-2. After you complete these steps, your Cisco MXE 3500 will be ready to use.
Table 7-2
Tasks for Restoring a Cisco MXE 3500 Standalone or Resource Manager
Configuration
To Restore ..
Complete This Task
Job Profiles
Copy the backed up profiles here: C:\Program Files\Cisco\Media Experience
Engine\profiles
You may wish to run some test jobs first using the default Job Profiles that are
provided with the Cisco MXE 3500. When you copy the profiles that were
backed up in the preparation step, the default profiles may be modified.
License File
Copy the backed up mxe.lic license file into the directory: C:\Program
Files\Cisco\Media Experience Engine\license
Your Cisco MXE 3500 will not run without a license file.
Note
Source Content
Server Settings
Folder Attendant
Configuration
Copy the backed up source content into the C:\Media directory.
1.
•
Login User Name: admin
•
Password: admin
2.
Open the System Administration page (from the Toolbox, click
Administration > System) and enter the SMTP server information you
documented in Preparing for Recovery, page 7-1.
3.
If you have a Resource Manager deployment, configure the
Resource Manager device. See also: Using Administrative Tools to
Configure the Resource Manager Device, page 2-9.
1.
Copy the backed up Folder Attendant configuration file faConfig.xml to
the directory: C:\Program Files\Cisco\Media Experience Engine\Folder
Attendant\bin
2.
If the directories do not appear online, confirm that the user account the
Cisco MXE 3500 Folder Attendant service is running under has
permissions to read and write to the watch directory.
Note
3.
Services
Log into the UI at http://localhost/mxeUI by using the following
credentials:
The Folder Attendant may not function correctly until you restore all
of your encoding profiles and watch directories that are on the system.
After you have restored the license file and the Folder Attendant
configuration file, reboot the Cisco MXE 3500.
If any of the Cisco MXE 3500 Services were running under an account other
than the default, MXE-Service, change the services Logon account to the
service account documented in the prepare step.
See also: Preparing for Recovery, page 7-1.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
OL-21554-01
7-5
Chapter 7
Recovering Cisco MXE 3500
Restoring the Configuration
Se n d d o c u m e n t f e e d b a ck t o m xe - d o c @ c i s c o . c o m .
Table 7-2
Tasks for Restoring a Cisco MXE 3500 Standalone or Resource Manager
Configuration (continued)
To Restore ..
Complete This Task
Speech-to-Text Files
Copy any custom speech-to-text speaker profile folders to the directory:
C:\Documents and Settings\All Users\Application Data\Nuance\Dragon SDK
Server Edition10\Users\
Graphic Overlay Files Copy any custom graphic overlay files (SWF files) and content XML scripts
for speech to text to the directory: C:\media\SpeechToTextFiles
Resource Node Configuration
To restore a Resource Node, complete the tasks in Table 7-3.
Table 7-3
To Restore ...
Tasks for Restoring a Resource Node
Complete This Task
Resource Node using Resource Manager recognizes a Resource Node by Host name and UNC path,
the original TCP/IP
and that information is stored in the Resource Manager. If you configure the
Host name
original Host name and change only the IP address of the restored
Resource Node, then you do not need to modify the Resource Manager
configuration.
Complete these steps to restore a Resource Node in a Resource Manager
deployment.
1.
Resource Nodes ship with the default TCP/IP Host name. Change the
TCP/IP Host name back to the original name that you assigned this device
and configured as a Host in Resource Manager.
2.
Resource Nodes ship with DHCP enabled. If you use static IP addresses,
disable DHCP and assign an IP address on this device.
Resource Node using Complete these steps to restore a Resource Node in a Resource Manager
a new TCIP/IP Host
deployment.
name
1. Resource Nodes ship with the same TCP/IP Host name. Change the
TCP/IP Host name to a unique name on this device.
2.
Resource Nodes ship with DHCP enabled. If you use static IP addresses,
disable DHCP and assign an IP address on this device.
3.
Delete the original Host name for this Resource Node. See also: User
Settings, page 2-19.
4.
Configure the Hosts settings for this Resource Node. See also:
Configuring Hosts Settings for Resource Manager Deployments,
page 2-14.
Deployment and Administration Guide for Cisco Media Experience Engine 3500 Release 3.0
7-6
OL-21554-01