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 3000
Release 2.0
June 8, 2009
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-16998-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 .
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.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco StackPower,
Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flip Video, Flip Video (Design),
Flipshare (Design), Flip Ultra, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Store, and Flip Gift Card are
service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the
Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without
Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study,
IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar,
PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath,
WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0907R)
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 3000 Release 2.0
© 2008-2009 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 3000 in Standalone Configuration
About Cisco MXE 3000 Standalone Deployments
Guidelines for Standalone Deployments
1-1
1-1
1-1
Identifying Steps to Deploy Cisco MXE 3000
1-2
Accessing Cisco MXE 3000 User Interfaces 1-2
Accessing the Client User Interface (CLUI) 1-2
Accessing the Folder Attendant User Interface 1-3
Access the Web User Interface (WebUI) 1-3
Installing the License on Cisco MXE 3000
Obtaining the MAC Address 1-4
Obtaining the License 1-5
Installing the License 1-6
Configuring the E-mail Server
1-4
1-6
Confirming Service Accounts and Identifying Device Type
Creating a Folder Attendant Directory and Watch
Creating a Directory 1-10
Creating a Watch 1-11
1-7
1-9
Configuring Cisco MXE 3000 1-12
System Settings 1-13
Input Section 1-13
Output Section 1-14
General Settings Section 1-15
Status Settings Section 1-16
Single Node Mode Section 1-17
Hosts Settings 1-18
Users Settings 1-20
Verifying Cisco MXE 3000 Deployment
1-21
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-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 .
Test 1: Submit a Job Using the CLUI 1-21
Test 2: Submit a Job Using Folder Attendant
CHAPTER
2
1-22
Deploying Cisco MXE 3000 in Resource Manager Configuration
About Cisco MXE 3000 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 3000 User Interfaces
2-3
2-4
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 E-mail Server
2-8
Confirming Service Accounts
2-8
Creating a Folder Attendant Directory and Watch
2-9
Configuring the Resource Manager Device 2-9
System Settings for Resource Manager Deployments 2-9
Input Section 2-9
Output Section 2-11
General Settings Section 2-11
Status Settings Section 2-11
Single Node Mode Section 2-12
Grid Computing Section 2-13
Hosts Settings 2-13
Understanding Capacity, Expense, and Limit 2-16
Configuring Hosts Settings for Resource Manager Deployments
Users Settings 2-18
Verifying Resource Manager Deployment 2-18
Test 1: Submit a Job Using the CLUI 2-18
Test 2: Submit a Job Using Folder Attendant
CHAPTER
3
Upgrading Cisco MXE 3000
Guidelines for Upgrades
2-17
2-19
3-1
3-1
Upgrading Cisco MXE 3000 from a Standalone to Resource Manager Device
Preparing for Upgrade 3-2
Obtaining a License for the Upgrade to Resource Manager 3-3
Upgrading the Resource Manager Device 3-3
3-1
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
iv
OL-16998-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 .
Obtaining the Upgrade Software 3-3
Performing the Upgrade to Resource Manager 3-4
Completing Resource Manager Upgrade Configuration 3-5
CHAPTER
4
Upgrading a Cisco MXE 3000 from a Standalone to a Resource Node Device
Preparing for Upgrade 3-6
Obtaining a License for the Upgrade to Resource Node 3-7
Upgrading the Resource Node Device 3-8
3-6
Adding a New Resource Node to an Existing Resource Manager Deployment
3-10
Security Best Practices and Backup Guidelines for Cisco MXE 3000
Security Best Practices for Cisco MXE 3000
4-1
4-1
Cisco MXE 3000 Microsoft Hot Fix Release Policy
4-2
Backup Guidelines for Cisco MXE 3000 4-2
Backing Up Cisco MXE 3000 4-2
Backing Up the Folder Attendant Database 4-3
Backing Up Cisco MXE 3000 Files 4-3
Restoring Cisco MXE 3000 Configuration 4-4
Recovering Cisco MXE 3000 4-4
Restoring the Folder Attendant Database 4-4
Restoring Other Cisco MXE 3000 Files 4-5
CHAPTER
5
Running Reports for Cisco MXE 3000
Introduction to Reports
5-1
5-1
Custom Report Options 5-3
Include JobTask Statistics 5-5
Setting Job Id Criteria 5-5
Setting Job Submit Time Criteria 5-6
Setting Job Stop Time Criteria 5-7
Setting Priority Criteria 5-7
Setting Title Criteria 5-8
Setting Author Criteria 5-9
Understanding Reported Information
Running Predefined Reports
5-10
5-11
Available Predefined Reports 5-11
Worker Summary Report 5-12
Worker by Id Statistics Report 5-13
Worker Id Health Statistics Report 5-14
Worker Type Health Statistics Report 5-15
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-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 .
Total Worker Hours Summary Report
5-16
Viewing Report Output in Excel 5-17
Saving the Report Output 5-17
Viewing the Report in Excel 5-17
CHAPTER
6
Troubleshooting Cisco MXE 3000
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 3000
Preparing for Recovery
6-2
7-1
7-1
Recovering the Cisco MXE 3000 7-2
Preparing the Boot Disk DVD by Using Symantec Ghost Software
Using the Boot Disk DVD to Recover the Appliance 7-3
Restoring the Configuration 7-4
Standalone or Resource Manager Configuration
Resource Node Configuration 7-6
7-2
7-4
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
vi
OL-16998-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: June 8, 2009, OL-16998-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 3000 in a standalone configuration or a Cisco MXE 3000
Resource Manager and Cisco MXE 3000 Resource Nodes in a Resource Manager configuration.
This guide does not describe how to use the Cisco MXE 3000; see the User Guide for Cisco MXE 3000
for this information.
Audience
This guide is for the system administrator who is responsible for deploying Cisco MXE 3000; 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 3000 Release 2.0
OL-16998-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 a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS Version 2.0.
Providing Documentation Feedback
To provide feedback on this Cisco MXE 3000 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/2_x/2.0/deployment/administration/
guide/ag_mxe20.html
Alternatively, you can send feedback to [email protected].
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
viii
OL-16998-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 3000 in Standalone
Configuration
Revised: June 8, 2009, OL-16998-01
This section includes the following topics:
•
About Cisco MXE 3000 Standalone Deployments, page 1-1
•
Guidelines for Standalone Deployments, page 1-1
•
Identifying Steps to Deploy Cisco MXE 3000, page 1-2
•
Accessing Cisco MXE 3000 User Interfaces, page 1-2
•
Installing the License on Cisco MXE 3000, page 1-4
•
Configuring the E-mail Server, page 1-6
•
Confirming Service Accounts and Identifying Device Type, page 1-7
•
Creating a Folder Attendant Directory and Watch, page 1-9
•
Configuring Cisco MXE 3000, page 1-12
•
Verifying Cisco MXE 3000 Deployment, page 1-21
About Cisco MXE 3000 Standalone Deployments
A standalone deployment consists of one or more Cisco MXE 3000s 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 3000 in
Resource Manager Configuration.”
Guidelines for Standalone Deployments
The following configuration guidelines and restrictions apply to standalone deployments:
•
Cisco MXE 3000 system, host, and user settings come preconfigured. The only initial system
configuration required is the SMTP server on the System Settings page so that you receive job
completion or failure notifications.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
1-1
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Identifying Steps to Deploy Cisco MXE 3000
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 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. We recommend that you do not
delete this account; otherwise, the Cisco MXE 3000 may not work.
Identifying Steps to Deploy Cisco MXE 3000
Cisco MXE 3000 comes from the factory requiring you to perform only the following two steps before
using the system. Optional deployment instructions are included, as well.
Mandatory Deployment Steps
•
Installing the License on Cisco MXE 3000
•
Configuring the E-mail Server
Optional Deployment Steps
•
Confirming Service Accounts and Identifying Device Type
•
Creating a Folder Attendant Directory and Watch
•
Verifying Cisco MXE 3000 Deployment
Accessing Cisco MXE 3000 User Interfaces
This section includes the following topics:
Note
•
Accessing the Client User Interface (CLUI), page 1-2
•
Accessing the Folder Attendant User Interface, page 1-3
•
Access the Web User Interface (WebUI), page 1-3
For information about Cisco MXE 3000 components, including user interfaces, see the User Guide for
Cisco Media Experience Engine 3000 on Cisco.com, or click Help in the CLUI.
Accessing the Client User Interface (CLUI)
The CLUI is the standard Cisco MXE 3000 interface that you use to set up encoder server and client
preferences, create job profiles, submit jobs, and so on.
Note
For information about using CLUI, see the User Guide for Cisco Media Experience Engine 3000 on
Cisco.com, or click Help in the CLUI.
To access the CLUI, click the icon, shown in Figure 1-1, on the desktop of the Cisco MXE 3000
(standalone or Resource Manager device).
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
1-2
OL-16998-01
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Accessing Cisco MXE 3000 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 .
Figure 1-1
Client User Interface Desktop Icon
Accessing the Folder Attendant User Interface
The Folder Attendant is an interface through which you can monitor directories for new media files and
submit jobs to the Cisco MXE 3000 encoder(s) based on profiles assigned to each directory.
Note
For information about using Folder Attendant, see the User Guide for Cisco Media Experience
Engine 3000 on Cisco.com, or click Help in the Folder Attendant user interface.
Procedure
Step 1
To access Folder Attendant from Cisco MXE 3000 (standalone or Resource Manager device), enter
http://localhost/MxeUI in the Windows Explorer address bar.
or
To access Folder Attendant from another computer, enter http://IP_Address/MXEUI in the address bar
of a web browser.
Note
Step 2
The localhost address works only from the Cisco MXE 3000 (standalone or Resource Manager device).
Log in by using the following default credentials:
•
User Name: admin
•
Password: admin
Access the Web User Interface (WebUI)
The web user interface (WebUI) is the administrative interface for Cisco MXE 3000.
Note
This guide provides information about performing tasks through WebUI.
Procedure
Step 1
Note
Enter http://localhost/mxe or enter http://IP_Address/mxe in the Windows Explorer address bar.
The localhost address works only from the Cisco MXE 3000 (standalone or Resource Manager device).
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
1-3
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Installing the License on Cisco MXE 3000
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
Log in by using the following default credentials:
•
User Name: admin
•
Password: Leave this field blank.
Installing the License on Cisco MXE 3000
This section includes the following topics:
•
Obtaining the MAC Address, page 1-4
•
Obtaining the License, page 1-5
•
Installing the License, page 1-6
Obtaining the MAC Address
Note
Licensing requires that you provide either of the two Cisco MXE 3000 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.
Step 4
Select the System Settings tab, shown in Figure 1-2.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
1-4
OL-16998-01
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Installing the License on Cisco MXE 3000
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-2
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 3000 license. See also: Obtaining the License.
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
Before You Begin
•
You must have an account on Cisco.com to access the license website.
•
Obtain the Cisco MXE 3000 MAC address. See also: Obtaining the MAC Address.
Note
•
Licensing requires that you provide either of the two Cisco MXE 3000 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.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
1-5
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Configuring the E-mail Server
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
Go to http://www.cisco.com/go/license.
Step 2
Enter the PAK.
Step 3
If you are using Cisco MXE 3000 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 3000 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 the License
Before You Begin
Obtain the Cisco MXE 3000 license file. See also: Obtaining the License.
Procedure
Step 1
On the standalone Cisco MXE 3000 or the Resource Manager, copy the generated mxe.lic file into the
license directory: C:\Program Files\Cisco\Media Experience Engine\license
Step 2
Reboot the device.
Configuring the E-mail Server
For Cisco MXE 3000 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.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
1-6
OL-16998-01
Chapter 1
Deploying Cisco MXE 3000 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 .
The sending of e-mails is not required to complete transcoding jobs.
Procedure
Step 1
Log into the WebUI at http://localhost/mxe by entering the following default credentials:
•
Login User Name: admin
•
Password: Leave this field blank.
The System Settings page displays.
Step 2
Scroll down to the General Settings section, and complete the fields, as shown in Figure 1-3. See also:
General Settings Section.
Figure 1-3
Step 3
Configuring an E-mail Server
Scroll down to the bottom of the page, and click Save.
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 3000. The accounts can be local computer accounts or domain accounts.
Tip
You can quickly determine the Cisco MXE 3000 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 3000 device type one at a time, as shown in Figure 1-4.
Note
Table 1-1 lists the services for each Cisco MXE 3000 device type.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
1-7
Chapter 1
Deploying Cisco MXE 3000 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 .
Table 1-1
Statuses of Services for Cisco MXE 3000 Device Types
Service
Standalone or
Resource Manager
Resource Node
IIS Admin Service
Started
Disabled
MxeControl
Started
Disabled
MxeEncoder
Started
Started
MXE Folder Attendant Service
Started
Disabled
Figure 1-4
Step 3
Note
Selecting a Service Account
Double-click each service, and then select the Log On tab, as shown Figure 1-5. The service account can
be changed from the default on this page.
•
This action is not required for Cisco MXE 3000 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 3000 uses the service accounts to authenticate and access those network resources. You
must make sure that these service accounts have appropriate access.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
1-8
OL-16998-01
Chapter 1
Deploying Cisco MXE 3000 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-5
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.
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 3000 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-10
•
Creating a Watch, page 1-11
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
1-9
Chapter 1
Deploying Cisco MXE 3000 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 .
Creating a Directory
Procedure
Step 1
From the Folder Attendant Toolbox, click Folder Attendant.
Step 2
From the Directory drop-down, click Add, as shown in Figure 1-6. The Directory fields, shown in
Figure 1-7, display on the Folder Attendant Administration page.
Figure 1-6
Adding a Directory
Figure 1-7
Directory Fields
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
1-10
OL-16998-01
Chapter 1
Deploying Cisco MXE 3000 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 .
Step 3
Enter the appropriate information in each of the fields, and click Save.
Note
If the Directory Path, shown in Figure 1-7, 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 Folder Attendant Toolbox, click Folder Attendant.
Step 2
Select the directory for which you want to add a watch, and from the Watch drop-down, select Add, as
shown in Figure 1-8.
Figure 1-8
Select the Directory and Add a Watch
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
1-11
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Configuring Cisco MXE 3000
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 three sections, shown in Figure 1-9: Directory,
Watch, and Override System Settings, each of which contains a series of fields.
Figure 1-9
Complete Watch Fields
Step 3
Expand each section, and enter the appropriate information in each field.
Step 4
Save the Watch.
Configuring Cisco MXE 3000
Note
Although all possible configuration options are presented here, your system, host, and user settings come
preconfigured. The only initial configuration required of you is the SMTP server on the System Settings
page. No other changes are necessary. We recommend that you add passwords or change the default
user accounts.
This section includes the following topics:
•
System Settings, page 1-13
•
Hosts Settings, page 1-18
•
Users Settings, page 1-20
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
1-12
OL-16998-01
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Configuring Cisco MXE 3000
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 .
System Settings
The WebUI System page is used to configure the Cisco MXE 3000. This page is accessible only to users
who have been granted administrative permission. The System page is made up of the following sections:
•
Input Section
•
Output Section
•
General Settings Section
•
Status Settings Section
•
Single Node Mode Section
Input Section
Figure 1-10 shows the Input section settings.
Figure 1-10
Input Settings
Table 1-2 describes the settings.
Table 1-2
Input Settings and Descriptions
Setting
Description
Media Directory
Defines the directory where media files that are submitted to the Cisco MXE 3000
are stored. The Media Directory also identifies the directory path where the
Cisco MXE 3000 searches for files displayed in the source box on the File Job tab.
The Media Directory value can be entered either as a local path or a UNC path to a
network share. Mapped drives can only be used in deployments using a storage area
network (SAN).
Note
Profile Directory
The System Page gives a warning if the value entered is not a UNC path,
which is recommended.
Defines the default path the Cisco MXE 3000 Folder Attendant will use to search
for Job Profiles when processing a submitted job.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
1-13
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Configuring Cisco MXE 3000
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
Profile URL
Input Settings and Descriptions
Defines the default path the Cisco MXE 3000 Folder Attendant will use to search
for Job Profiles when searching in the Browser interface.
Note
Care should be taken when changing the default profile locations for the
Cisco MXE 3000 Client UI (CLUI) and Folder Attendant. If the directories
are not the same, new profiles or modifications made to existing profiles by
using the CLUI will not be detected by the Folder Attendant. However, it is
a best practice to experiment with new profiles by changing the profile
directory location in the CLUI so that production profiles are not affected.
Bumper/Trailer
Directory
Defines the location of files that can be used as bumpers or trailers.
Watermark
Directory
Defines the location of files that can be used as watermarks.
Valid Input
Extensions
Defines the list of valid extensions for files in Common Directories.
Common
Directories
Defines the directories where media files will be stored. Multiple directories can be
defined. A semicolon is used to separate directory entries.
The Bumper/Trailer Directory value can be entered either as a local path or a UNC
path to a network share. Mapped drives can only be used in deployments using a
storage area network (SAN).
The Watermark Directory value can be entered either as a local path or a UNC path
to a network share. Mapped drives can only be used in deployments using a storage
area network (SAN). The Watermark Directory location must be accessible to all
Hosts.
The Common Directory values can be entered either as a local path or a UNC path
to a network share. Mapped drives can only be used in deployments using a storage
area network (SAN). The Common Directory locations must be accessible to all
Hosts.
Output Section
Output directories define the locations the Cisco MXE 3000 will use to save files of each encoding
format. Encoded files are saved to the defined directories when no Output tab is included in the Job
Profile.
The Microsoft Output Directory value can be entered either as a UNC path to a network share if the
service accounts have a write permission at the network share or to a mapped drive in the case of a
deployment using a storage area network (SAN).
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
1-14
OL-16998-01
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Configuring Cisco MXE 3000
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 shows the Output section settings.
Figure 1-11
Output Settings
General Settings Section
Figure 1-12 shows the General Settings section.
Figure 1-12
General Settings
Table 1-3 describes the settings.
Table 1-3
Setting
General Settings and Descriptions
Description
Default Copyright Defines the default copyright information for all jobs. The value entered can be
overwritten on a per-job basis by entering copyright information in the Metadata
section of the File Job tab.
License File
Defines the location of the license file Cisco MXE 3000 will use when starting the
system.
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
1-15
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Configuring Cisco MXE 3000
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
General Settings and Descriptions
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
appears when you select Email on the Notification tab.
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.
Profile MultiSelect Size
This setting has no effect and does not apply to the Cisco MXE 3000.
Status Settings Section
Figure 1-13 shows the Status Settings section.
Figure 1-13
Status Settings
Table 1-4 describes the settings.
Table 1-4
Setting
Monitor
Window
Display
Status Settings and Descriptions
Description
Controls whether windows will be opened to display preprocessor and encoder progress
as the job runs. This setting applies only when the Cisco MXE 3000 is set to run in
console mode. The MXEControl and MXEEncoder can be run from a command prompt.
This configuration is used only for Debug purposes.
To run the executables from a command prompt, stop the services, and open two
command prompts.
•
C:\Program Files\Cisco\Media Experience Engine\bin\ecs
•
C:\Program Files\Cisco\Media Experience Engine\bin\lcs
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
1-16
OL-16998-01
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Configuring Cisco MXE 3000
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-4
Status Settings and Descriptions
Auto Reap
(Minutes)
Defines the Auto Reap interval used to clear job information from monitoring pages. The
time defined for the Auto Reap determines how long information on a job will be
displayed in the Job Status window before it expires. The Auto Reap interval is counted
from the time the job completes.
DB Data
Purge
Defines whether the system will purge records from the database that are older than the
selected time period. It is recommended these settings be left at the default values.
Changing these settings will result in a system that no longer functions after a period of
time.
•
delete: Records older than the specified number of days will be deleted from the
database.
•
disabled: The DB Data Purge feature is not active.
•
data older than: Defines the number of days to use as a threshold for the deletion of
database records.
Single Node Mode Section
Note
You cannot change the Single Node Mode Settings in Cisco MXE 3000 Release 2.0.
For users in bandwidth-sensitive environments, such as educational institutions and corporations, Single
Node Mode provides greater control and ability to confine encoding for a job to a single node.
Single Node Mode limits the disk writes to local drives, thereby reducing the amount of data sent over
the network.
When you submit a job, the system will attempt to select the best node, based on the tasks that are part of the job.
Figure 1-14 shows the Single Node Mode section.
Figure 1-14
Single Node Mode Settings
Table 1-5 describes the settings.
Table 1-5
Setting
Single Node Mode Settings and Descriptions
Description
Enabled
Yes: Indicates that Single Node Mode is currently enabled.
Mode
Soft Single Node Mode is enabled. Tasks will run on a single node unless the Timeout
value is exceeded, in which case tasks that have not started will be reassigned to available
encoding nodes with the appropriate resources.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
1-17
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Configuring Cisco MXE 3000
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-5
Single Node Mode Settings and Descriptions
Timeout
Determines the length of time, in seconds, the system will wait in Soft mode before
attempting to reassign unstarted tasks to other nodes.
Queue
Limit
Specifies the maximum number of jobs that can be queued to a specific node.
Hosts Settings
Note
You cannot change the Host Settings in Cisco MXE 3000 Release 2.0.
From the Select Host drop-down, select a Host to display summary information about workers
configured on that Host along with a limited number of editable fields.
Figure 1-15 shows the Host settings.
Figure 1-15
Host Settings
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
1-18
OL-16998-01
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Configuring Cisco MXE 3000
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-6 describes the Host settings.
Table 1-6
Setting
Host
Host Settings and Descriptions
Description
Displays the name of the Host. This must be the name assigned to the computer in its
network identification properties. The computer name and the Host name must match
exactly. Localhost is the default and preferred name of the Cisco MXE 3000.
Type the hostname command at the command prompt, and the computer name will be
returned.
Temp
Specifies the directory where temporary files and preprocessor output will be stored
Directory
while the job is processing.
(UNC Name)
Note
Do not change the default setting of C:\Temp.
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.
Capacity
Reflects a numeric value assigned for the total available processing capacity of the
displayed Host. Capacity is a fixed setting in the Cisco MXE 3000 to return the best
possible performance.
Available
License
Package
Specifies which license package is associated with the displayed Host.
Permit
Indicates which workers are configured to run on the displayed Host.
Worker Type Displays the types of workers that have been configured to run on the displayed host.
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 3000 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 3000 to return the best possible performance.
Name
This setting is not available in Cisco MXE 3000 Release 2.0.
DV
This setting is not available in Cisco MXE 3000 Release 2.0.
DVCAM
This setting is not available in Cisco MXE 3000 Release 2.0.
Video
Channel
This setting is not available in Cisco MXE 3000 Release 2.0.
Audio
Channel
This setting is not available in Cisco MXE 3000 Release 2.0.
Save and
Activate
Changes
Saves changes made to the Host since it was last saved.
A Host can be modified while it is in use, but modifications will not be applied until
the Host is deactivated and reactivated. When you click Save, the Host automatically
resets.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
1-19
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Configuring Cisco MXE 3000
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 .
Users Settings
The Users page, shown in Figure 1-16, allows you to create, modify, and suspend WebUI users.
Figure 1-16
Users Settings
Table 1-7 describes the settings.
Table 1-7
User Settings and Descriptions
Setting
Description
User
The Select User drop-down displays users available for editing.
Password
Allows the administrator to assign a password used for validation when a user
logs in. Passwords can be left blank or may follow rules to ensure minimum
complexity depending on the security requirements in a given environment.
Passwords are case sensitive. Passwords should be alphanumeric and can be
up to 20 characters.
Confirm Password
Requires the administrator to type the password a second time to ensure the
entered value has been typed correctly.
Email
Stores the user’s e-mail address. This e-mail address will display if you select
this user in the Email section of the Notification tab. E-mail addresses can be
up to 50 characters.
E-mail addresses can also be used to send messages to a pager or a cellular
phone.
Grant administration
privileges
Controls user access to the System administration page.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
1-20
OL-16998-01
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Verifying Cisco MXE 3000 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 1-7
User Settings and Descriptions
Grant administer user
privileges
Controls access to the Users administration page.
Grant profile privileges
Controls user access to the Job Profile creation pages.
Grant live privileges
This setting is not available in Cisco MXE 3000 Release 2.0.
Administrators should be selective in allowing users access to the Users
administration page. Because account information about other users can be
changed from the users page and because access to the system can be granted
from this page, access should be limited to those users who have a thorough
understanding of the Cisco MXE 3000 and of users roles and responsibilities.
Verifying Cisco MXE 3000 Deployment
To ensure your system has been correctly deployed and configured, perform the following tests:
•
Test 1: Submit a Job Using the CLUI
•
Test 2: Submit a Job Using Folder Attendant
Test 1: Submit a Job Using the CLUI
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 CLUI. See also: Accessing the Client User Interface (CLUI).
Step 2
Click File > Open Job Profile and choose Cable_Broadband.job.awp.
Step 3
Click Select File Set.
Step 4
In the C:\Media folder, select the Sample.mov file.
Step 5
Click Add file to job log.
Step 6
Highlight the Sample.mov job.
Step 7
Click Submit.
Step 8
Click View > Job Status.
Step 9
Continue watching the Job Status window to make sure the job completes.
Step 10
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
1-21
Chapter 1
Deploying Cisco MXE 3000 in Standalone Configuration
Verifying Cisco MXE 3000 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
Before You Begin
•
If you completed Test 1: Submit a Job Using the CLUI, delete the media files from the C:\media
and C:\output folders.
•
In the C:\ProgramFiles\QuickTime folder, select Sample.mov, and copy the file to the C:\Media
folder.
Procedure
Step 1
Access Folder Attendant. See also: Accessing the Folder Attendant User Interface.
Step 2
Highlight the watch created in Test 1: Submit a Job Using the CLUI.
Step 3
Next to Watch Extensions, click Select.
Step 4
Scroll down to MPEG-4, and press Ctrl+Click to add that extension to the list.
Step 5
Click Set Extensions.
Step 6
Click Job Profile, select Cable_Broadband, and click Save.
Step 7
In the Toolbox under Monitoring, click Job Status.
Step 8
Drag a copy of the Sample.mov file to the watch folder.
Step 9
Watch the Job Status pane to make sure the job starts and completes.
Step 10
Browse to the C:\Output folder, and locate the Sample.Cable_Broadband.Cable_Broadband.wmv
file.
Step 11
If you created another version of the file in Test 1: Submit a Job Using the CLUI, check that the time
stamp is current to verify that the file was recreated, and play the file.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
1-22
OL-16998-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 3000 in Resource Manager
Configuration
Revised: June 8, 2009, OL-16998-01
This section includes the following topics:
•
About Cisco MXE 3000 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 3000 User Interfaces, page 2-4
•
Installing the License on the Resource Manager Device, page 2-5
•
Configuring the E-mail Server, page 2-8
•
Confirming Service Accounts, page 2-8
•
Creating a Folder Attendant Directory and Watch, page 2-9
•
Configuring the Resource Manager Device, page 2-9
•
Verifying Resource Manager Deployment, page 2-18
About Cisco MXE 3000 Resource Manager Deployments
A Cisco MXE 3000 Resource Manager (Resource Manager) deployment consists of one or more
Cisco MXE 3000 devices running as a single group with one set of user accounts, job profiles, licensed
features, and user interfaces.
There are two types of Cisco MXE 3000 devices in a Resource Manager deployment: a single
Resource Manager and up to nine Resource Nodes.
•
Resource Manager—Runs both the Enterprise Control System (ECS) and Local Control System
(LCS) components on the same Cisco MXE 3000 device and is aware of all Resource Nodes in the
group. The Resource Manager functions as a multinode manager by assigning various transcoding
jobs to Resource Nodes, balancing the job loads uniformly based on the Capacity, Limit, and
Expense values that you configure in the Resource Manager for each Resource Node.
•
Resource Node—Runs only the LCS component and performs transcoding jobs. A single
Resource Manager device can support up to 10 Resource Nodes, including itself as a one node. Be
aware that because the Resource Manager also runs LCS, it functions also as a Resource Node and
can process jobs.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
2-1
Chapter 2
Deploying Cisco MXE 3000 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
For information about Cisco MXE 3000 components, see the User Guide for Cisco Media Experience
Engine 3000 on Cisco.com, or click Help in the CLUI.
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 TCP/IP Host name, MXE 3000. Before
you configure Hosts Settings, you must change the TCP/IP 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. We recommend that you do not
delete this account; otherwise, the Cisco MXE 3000 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.
Identifying Steps for Resource Manager Deployments
Cisco MXE 3000 comes from the factory requiring you to perform the following mandatory steps before
using the system. Optional deployment instructions are included, as well.
Note
For an example deployment workflow, see the “Example Workflow for a Three-Node Resource Manager
Deployment” section on page 2-3.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
2-2
OL-16998-01
Chapter 2
Deploying Cisco MXE 3000 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 .
Mandatory Deployment Steps
•
Installing the License on the Resource Manager Device
•
Configuring the E-mail Server
•
Configuring System Settings for Resource Manager Deployments
•
Configuring Hosts Settings
Optional Deployment Steps
•
Confirming Service Accounts
•
Creating a Folder Attendant Directory and Watch
•
Verifying Resource Manager Deployment
Example Workflow for a Three-Node Resource Manager Deployment
The following table provides an example workflow that identifies the mandatory steps 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 3000
Step 2
Step 3
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.
Obtain the Resource Manager license:
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.
Quick Start Hardware Installation Guide for
Cisco Media Experience Engine 3000
•
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
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
2-3
Chapter 2
Deploying Cisco MXE 3000 in Resource Manager Configuration
Accessing Cisco MXE 3000 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 .
—
Task
Step 4
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:
•
E-mail server
•
System Settings
•
Hosts Settings
Resource
•
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 E-mail Server
•
Configuring System Settings for
Resource Manager Deployments
•
Configuring Hosts Settings
Accessing Cisco MXE 3000 User Interfaces
For information about accessing the user interfaces on the Resource Manager device, see the “Accessing
Cisco MXE 3000 User Interfaces” section on page 1-2 in Chapter 1, “Deploying Cisco MXE 3000 in
Standalone Configuration.”
Note
•
You can access Cisco MXE 3000 user interfaces only on the Resource Manager device—not its
Resource Nodes.
•
A graphic with either “Resource Manager” or “Resource Node” displays on the desktop of each
node to identify its Cisco MXE 3000 device type and facilitate identification. We recommend that
you do not remove the graphic. You can also determine the function of a node by its enabled services.
See also: Confirming Service Accounts and Identifying Device Type, page 1-7.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
2-4
OL-16998-01
Chapter 2
Deploying Cisco MXE 3000 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 .
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 3000 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 3000 Release 2.0
OL-16998-01
2-5
Chapter 2
Deploying Cisco MXE 3000 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 3000 Resource Manager license. See also: Obtaining the License
for the Resource Manager.
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 3000 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 3000 Release 2.0
2-6
OL-16998-01
Chapter 2
Deploying Cisco MXE 3000 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 3000 MAC address of the Resource Manager device. See also: Obtaining the
Resource Manager MAC Address.
•
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 3000 Release 2.0
OL-16998-01
2-7
Chapter 2
Deploying Cisco MXE 3000 in Resource Manager Configuration
Configuring the E-mail Server
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 3000 license file for the Resource Manager device. See also: Obtaining the
License for the Resource Manager.
•
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 E-mail Server
For information about configuring the e-mail server on the Resource Manager device, see the
“Configuring the E-mail Server” section on page 1-6 in Chapter 1, “Deploying Cisco MXE 3000 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-7 in Chapter 1,
“Deploying Cisco MXE 3000 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 3000 device type (Resource Manager or Resource Node) by
verifying which services are enabled.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
2-8
OL-16998-01
Chapter 2
Deploying Cisco MXE 3000 in Resource Manager 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 .
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-9 in Chapter 1, “Deploying
Cisco MXE 3000 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-7.
Configuring the Resource Manager Device
Note
We recommend that you add passwords or change the default user accounts.
This section includes the following topics:
•
System Settings for Resource Manager Deployments, page 2-9
•
Hosts Settings, page 2-13
•
Users Settings, page 2-18
System Settings for Resource Manager Deployments
The WebUI System page is used to configure the Cisco MXE 3000 Resource Manager device. This page
is accessible only to users who have been granted administrative permission. The System page is made
up of the following sections:
•
Input Section
•
Output Section
•
General Settings Section
•
Status Settings Section
•
Single Node Mode Section
•
Grid Computing Section
Input Section
Note
Directory values must be UNC paths to a network share.
Figure 2-2 shows Input section settings.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
2-9
Chapter 2
Deploying Cisco MXE 3000 in Resource Manager Configuration
Configuring 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
Input Settings
Table 2-1 describes the Input section settings.
Table 2-1
Input Settings and Descriptions for Resource Manager Deployments
Setting
Description
Media Directory
Defines the directory where media files that are submitted to the
Resource Manager are stored.
The Media Directory also identifies the directory path where the
Resource Manager searches for files displayed in the source box on the File Job
tab.
Profile Directory
Defines the default path the Folder Attendant will use to search for Job Profiles
when processing a submitted job.
Profile URL
Defines the default path the Folder Attendant will use to search for Job Profiles
when searching in the Browser interface.
Note
Care should be taken when changing the default profile locations for the
Client UI (CLUI) and Folder Attendant. If the directories are not the same,
new profiles or modifications made to existing profiles by using the CLUI
will not be detected by the Folder Attendant. However, it is a best practice
to experiment with new profiles by changing the profile directory location
in the CLUI so that production profiles are not affected.
Bumper/Trailer
Directory
Defines the location of files that can be used as bumpers or trailers.
Watermark
Directory
Defines the location of files that can be used as watermarks.
Valid Input
Extensions
Defines the list of valid extensions for files in Common Directories.
Common
Directories
Defines the directories where media files will be stored. Multiple directories can
be defined. A semicolon is used to separate directory entries.
The Watermark Directory location must be accessible to all Hosts.
The Common Directory locations must be accessible to all Hosts.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
2-10
OL-16998-01
Chapter 2
Deploying Cisco MXE 3000 in Resource Manager Configuration
Configuring 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 .
Output Section
Output directories define the locations the Resource Manager will use to save files of each encoding
format. Encoded files are saved to the defined directories when no Output tab is included in the Job
Profile.
Note
All directory values must be a UNC path to a network share.
Figure 2-3 shows the Output section settings.
Figure 2-3
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-15 in Chapter 1, “Deploying Cisco MXE 3000 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-16 in Chapter 1, “Deploying Cisco MXE 3000 in Standalone
Configuration.”
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
2-11
Chapter 2
Deploying Cisco MXE 3000 in Resource Manager Configuration
Configuring 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 .
Single Node Mode Section
For users in bandwidth-sensitive environments, such as educational institutions and corporations, Single
Node Mode provides greater control. This mode provides the ability to confine encoding for a job to a
single Resource Node by forcing all job processing tasks to a single encoder node rather then distributing
tasks across the system. This mode effectively reduces the amount of network traffic between the nodes
of the system because it limits disk writes to local drives.
When you submit a job, the system will attempt to select the best node based on the tasks that are part
of the job.
Figure 2-4 shows the Single Node Mode section.
Figure 2-4
Single Node Mode Settings
Table 2-2 describes the settings.
Table 2-2
Setting
Enabled
Single Node Mode Settings and Descriptions
Description
Yes: Indicates Single Node Mode is currently enabled.
Enabling Single Node Mode forces job processing to a single node: all the sub-parts of a
transcoding job are forced to run on the same node. The preprocessing, encoding, and
distribution all take place on the same node so that the temporary (intermediate) files are
not transferred between sub-jobs to other nodes across the network.
No: Indicates Single Node Mode is currently disabled.
Disabling Single Node Mode turns on the load balancing capabilities of the
Resource Manager: the sub-parts of a transcoding job are distributed among available
nodes based on the load on each node. The preprocessing can occur on one node, encoding
on another node, and so on.
Mode
Soft: Indicates Soft Single Node Mode is enabled.
Enabling Soft mode means that the Single Node Mode restriction is waived when jobs
exceed the Queue Limit (too many jobs in the queue) or Timeout value (jobs have been
waiting too long), at which time jobs that have not started will be reassigned to available
encoding nodes with the appropriate resources. The Single Node Mode restriction is
enforced again when the Timeout and Queue Limit are below the configured values.
Hard: Indicates Hard Single Node Mode is enabled.
Enabling Hard mode means that the Single Node Mode restriction is enforced even if the
Queue Limit or Timeout value is exceeded.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
2-12
OL-16998-01
Chapter 2
Deploying Cisco MXE 3000 in Resource Manager Configuration
Configuring 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
Timeout
Single Node Mode Settings and Descriptions
Determines the length of time, in seconds, the system will wait in Soft mode before
attempting to reassign unstarted tasks to other nodes.
The Timeout can be as large as necessary. The value should be set relative to the average
or maximum job length for your Resource Manager deployment. As a guideline, tasks
should flow to another node if the wait is going to be longer than the processing time and
if other nodes are available.
Timeout has no range limit. The value needs to be positive integers. The default is 3600
seconds.
Queue
Limit
Specifies the maximum number of jobs that can be queued to a specific node.
The Queue Length is set to a value that allows tasks to move to nodes that have a smaller
queue. This value should be set relative to the average peak queue length for your
Resource Manager deployment. If the value is less than what normally occurs,
performance will decrease.
Queue Limit has no range limit. The value needs to be positive integers. The default is 25.
Grid Computing Section
Note
Cisco MXE 3000 does not support grid-enable encodes. This value will be ignored.
Grid Computing specifies the number of segments that a file will be split into for decode/encode.
Figure 2-5 shows the Grid Computing section.
Figure 2-5
Grid Computing Settings
Hosts Settings
From the Select Host drop-down, 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-17 and Understanding
Capacity, Expense, and Limit, page 2-16
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
2-13
Chapter 2
Deploying Cisco MXE 3000 in Resource Manager Configuration
Configuring 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-6 shows the Hosts settings and the recommended values for these settings.
Figure 2-6
Host Settings and Recommended Values for Resource Manager Deployments
Table 2-3 describes the Hosts settings.
Table 2-3
Setting
Host
Hosts Settings and Descriptions for Resource Manager Deployments
Description
Displays the name of the Host. This must be the name assigned to the computer in its
network identification properties. 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.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
2-14
OL-16998-01
Chapter 2
Deploying Cisco MXE 3000 in Resource Manager Configuration
Configuring 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
Hosts Settings and Descriptions for Resource Manager Deployments (continued)
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, because the other nodes need to read across
the network.
MXE-Service must also have read/write access to this directory and IIS.
Note
Capacity
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.
Reflects a numeric value assigned for the total available processing capacity of the
displayed Host.
Valid values are 0-99.
See also: Understanding Capacity, Expense, and Limit, page 2-16 and Figure 2-6, Host
Settings and Recommended Values for Resource Manager Deployments
Available
License
Package
Specifies which license package is associated with the displayed Host.
Permit
Indicates which workers are configured to run on the displayed Host.
Installed licenses for available nodes display.
Worker Type Displays the types of workers that have been configured to run on the displayed Host.
Limit
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-16 and Figure 2-6, Host
Settings and Recommended Values 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-16 and Figure 2-6, Host
Settings and Recommended Values for Resource Manager Deployments
Name
This setting is not available in Release 2.0.
DV
This setting is not available in Release 2.0.
DVCAM
This setting is not available in Release 2.0.
Video
Channel
This setting is not available in Release 2.0.
Audio
Channel
This setting is not available in Release 2.0.
Save and
Activate
Changes
Saves changes made to the Host since it was last saved.
A Host can be modified while it is in use, but modifications will not be applied until the
Host is deactivated and reactivated. When you click Save, the Host automatically resets.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
2-15
Chapter 2
Deploying Cisco MXE 3000 in Resource Manager Configuration
Configuring 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 .
Understanding Capacity, Expense, and Limit
Note
•
See also: Figure 2-6, Host Settings and Recommended Values for Resource Manager Deployments
for recommended values for Capacity, Expense, and Limit
•
For information about Cisco MXE 3000 components, such as workers and ECS, see the User Guide
for Cisco Media Experience Engine 3000 on Cisco.com, or click Help in the CLUI.
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:
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
2-16
OL-16998-01
Chapter 2
Deploying Cisco MXE 3000 in Resource Manager Configuration
Configuring 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 .
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-16, Table 2-3, Hosts Settings and
Descriptions for Resource Manager Deployments, and Figure 2-6, Host Settings and Recommended
Values for Resource Manager Deployments for recommended values for Capacity, Expense, and Limit.
Before You Begin
1.
Ensure that you change the TCP/IP Host name to a unique name on each Cisco MXE 3000 device.
You will use these names during Hosts settings configuration.
2.
Configure the Hosts settings for the Resource Manager device before you configure the settings for
the Resource Nodes.
3.
Configure the Resource Manager device as node1 in the Available License Package.
Procedure
Step 1
From the WebUI, click Administer > Hosts. See also: Hosts Settings, page 2-13.
Step 2
Click the New button.
Note
Configure the Host settings for Resource Manager device first; then, configure the settings for the
Resource Nodes.
Step 3
In the Host 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.
Step 4
In the Temp Directory field, enter the UNC path for the temp folder on the Host that you configured in
Step 3, as follows: \\host_name\\temp.
Step 5
Enter the Capacity.
Step 6
Select an Available License Package from the drop-down menu. The number of options that display is
equal to the number of Resource Nodes that are licensed (the Resource Manager device plus
Resource Nodes).
Note
Configure the Resource Manager device as node1.
Step 7
Configure Limit and Expense for each of the workers.
Step 8
Click Save and Activate Changes. The Host name that you configured in Step 3 is verified and changes
are saved.
Step 9
Repeat Step 2 through Step 8 for each node that you purchased.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
2-17
Chapter 2
Deploying Cisco MXE 3000 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 .
Users Settings
For information about User settings configuration on the Resource Manager device, see the “Users
Settings” section on page 1-20 in Chapter 1, “Deploying Cisco MXE 3000 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 the CLUI
•
Test 2: Submit a Job Using Folder Attendant
Test 1: Submit a Job Using the CLUI
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 the CLUI. See also: Accessing the Client User Interface (CLUI).
Step 2
Click File > Open Job Profile and choose Cable_Broadband.job.awp.
Step 3
Click Select File Set.
Step 4
Browse to \\Resource_Mananger_IP_Address\media and select all the copies of the Sample.mov file.
Step 5
Click Add file to job log.
Step 6
Highlight all the file jobs.
Step 7
Click Submit.
Step 8
Click View > Job Status.
Step 9
Continue watching the Job Status window to make sure the job completes.
Step 10
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 11
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
2-18
OL-16998-01
Chapter 2
Deploying Cisco MXE 3000 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 .
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 Folder Attendant User Interface.
Step 2
Highlight the watch created in Test 1: Submit a Job Using the CLUI.
Step 3
Next to Watch Extensions, click Select.
Step 4
Scroll down to MPEG-4, and press Ctrl+Click to add that extension to the list.
Step 5
Click Set Extensions.
Step 6
Click Job Profile, select select Cable_Broadband, and click Save.
Step 7
In the Toolbox under Monitoring, click Job Status.
Step 8
Drag all the copies of the Sample.mov file from the C:\media folder to he to the
\\Resource_Mananger_IP_Address\watch folder.
Step 9
Watch the Job Status pane to make sure the job starts and completes.
Step 10
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 11
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.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
2-19
Chapter 2
Deploying Cisco MXE 3000 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 .
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
2-20
OL-16998-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
Upgrading Cisco MXE 3000
Revised: July 22, 2009, OL-16998-01
Caution
We recommend that you copy any files that you want to keep to a location outside of the
Cisco MXE 3000 before you upgrade.
This section includes the following topics:
•
Guidelines for Upgrades, page 3-1
•
Upgrading Cisco MXE 3000 from a Standalone to Resource Manager Device, page 3-1
•
Upgrading a Cisco MXE 3000 from a Standalone to a Resource Node Device, page 3-6
•
Adding a New Resource Node to an Existing Resource Manager Deployment, page 3-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 3000.
•
If you want to return a Cisco MXE 3000 device back to its original 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 3000.
•
Before you upgrade, save your original license to a location that is not on your Cisco MXE 3000.
This license is required to re-enable features on your standalone or Resource Manager device if you
return the Cisco MXE 3000 device back to its original type.
Upgrading Cisco MXE 3000 from a Standalone to
Resource Manager Device
This section includes the following topics:
•
Preparing for Upgrade, page 3-2
•
Obtaining a License for the Upgrade to Resource Manager, page 3-3
•
Upgrading the Resource Manager Device, page 3-3
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
3-1
Chapter 3
Upgrading Cisco MXE 3000
Upgrading Cisco MXE 3000 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 .
•
Completing Resource Manager Upgrade Configuration, page 3-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 3-1.
Table 3-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 3000.
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 3000.
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 3000 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 3000.
The Cisco MXE 3000 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 3000.
The Cisco MXE 3000 was configured so that encoded files are located in the
C:\output directory.
E-mail Server
Settings
Folder Attendant
Configuration
Open the WebUI System settings page at http://localhost/mxe/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 3000.
The faConfig.xml file is located here: C:\Program Files\Cisco\MXE Folder
Attendant Service\bin\
Note
All watch directories that are located on the Cisco MXE 3000 device
will be deleted as part of the upgrade process.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
3-2
OL-16998-01
Chapter 3
Upgrading Cisco MXE 3000
Upgrading Cisco MXE 3000 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 3-1
Preparation Tasks for Upgrading from Standalone to Resource Manager Deployment
To Back Up ...
Complete This Task
Services
Open each of the three Cisco MXE 3000 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. Check each of the following
services:
Temp Directory
•
MXE Folder Attendant
•
MXEControl
•
MXEEncoder
•
All Other Files
All of the files in the Temp directory can be discarded. Deleting all files in the
Temp directory is a normal maintenance step.
Obtaining a License for the Upgrade to Resource Manager
When you upgrade a standalone Cisco MXE 3000 to a Resource Manager device, you must use the
same MAC address of the standalone Cisco MXE 3000 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 3-3
•
Performing the Upgrade to Resource Manager, page 3-4
Obtaining the Upgrade Software
The software to upgrade a standalone Cisco MXE 3000 Release 2.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 3000 configuration to which you are upgrading.
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 3000 Software (Media Experience Engine).
Step 4
Click Latest Releases > 2.0.0 > MXE 3000 Release 2.0.0 Resource Manager Upgrade. The links to
the software are on the right side of the browser window.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
3-3
Chapter 3
Upgrading Cisco MXE 3000
Upgrading Cisco MXE 3000 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 5
Save MXE3K-R2-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 3000 when you upgrade.
Step 6
Proceed to the “Performing the Upgrade to Resource Manager” procedure on page 3-4.
Performing the Upgrade to Resource Manager
Use this procedure to upgrade a standalone Cisco MXE 3000 Release 2.0 configuration to a
Resource Manager configuration.
Before You Begin
•
Complete the “Preparing for Upgrade” procedure on page 3-2.
•
Complete the “Obtaining the Upgrade Software” procedure on page 3-3.
•
Close any applications that are running on the Cisco MXE 3000 you are upgrading.
Procedure
Step 1
Log in to the Cisco MXE 3000 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-R2-0-UPG.zip to the folder that you created in Step 2.
Step 4
Right click MXE3K-R2-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-R2-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 3000 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.
Step 10
Step 11
If you installed the original Cisco MXE 3000 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 3-5.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
3-4
OL-16998-01
Chapter 3
Upgrading Cisco MXE 3000
Upgrading Cisco MXE 3000 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 .
Completing Resource Manager Upgrade Configuration
To complete the upgrade configuration, complete the tasks in Table 3-2. After you complete these steps,
your Cisco MXE 3000 Resource Manager will be ready to use.
Table 3-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 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 3-3.
2.
Install the Resource Manager license. See also: Installing the License on
the Resource Manager, page 2-8.
Your Cisco MXE 3000 will not run without a license file.
Note
E-mail Server
Settings
1.
Log into the WebUI on the Resource Manager device at
http://localhost/mxe by using the following credentials:
•
Login User Name: admin
•
Password: leave this field blank
The System Settings page displays.
2.
Services
Confirm that all the Cisco MXE 3000 Services are running under an account
documented in the “Preparing for Upgrade” procedure on page 3-2.
Note
Folder Attendant
Configuration
Scroll down to the General Settings section, and confirm or correct the
SMTP server and e-mail information you documented when preparing for
upgrade.
MXE Service must have read/write access to all configured UNC paths
and to IIS.
1.
On the Resource Manager device, copy the backed up Folder Attendant
configuration file faConfig.xml to the directory: C:\Program
Files\Cisco\MXE Folder Attendant Service\bin\
2.
If the directories do not appear online, confirm that the user account the
Cisco MXE 3000 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 3000.
See also: Creating a Folder Attendant Directory and Watch, page 1-9.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
3-5
Chapter 3
Upgrading Cisco MXE 3000
Upgrading a Cisco MXE 3000 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 3-2
Tasks for Upgrade (continued)
To Configure ...
Complete This Task
Resource Manager
Configuration
On the Resource Manager device, configure the System settings and Hosts
settings for the Resource Manager deployment.
See also: Configuring 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-9.
Upgrading a Cisco MXE 3000 from a Standalone to a
Resource Node Device
This section includes the following topics:
•
Preparing for Upgrade, page 3-6
•
Obtaining a License for the Upgrade to Resource Node, page 3-7
•
Upgrading the Resource Node Device, page 3-8
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 3-1.
Table 3-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 3000.
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 3000.
The license file is located here: C:\Program Files\Cisco\Media Experience
Engine\license\mxe.lic
Note
Back up the license to use if you return Cisco MXE 3000 to a
standalone deployment. Be aware that you must obtain a new license
for this deployment and install it on the Resource Manager device.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
3-6
OL-16998-01
Chapter 3
Upgrading Cisco MXE 3000
Upgrading a Cisco MXE 3000 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 3-3
Preparation Tasks for Upgrading from Standalone to Resource Node (continued)
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 3000.
The Cisco MXE 3000 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 3000.
The Cisco MXE 3000 was configured so that encoded files are located in the
C:\output directory.
E-mail Server
Settings
Folder Attendant
Configuration
Open the WebUI System settings page at http://localhost/mxe/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 3000.
The faConfig.xml file is located here: C:\Program Files\Cisco\MXE Folder
Attendant Service\bin\
Note
Services
Temp Directory
All watch directories that are located on the Cisco MXE 3000 device
will be deleted as part of the upgrade process.
Open each of the three Cisco MXE 3000 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. Check each of the following
services:
•
MXE Folder Attendant
•
MXEControl
•
MXEEncoder
•
All Other Files
All of the files in the Temp directory can be discarded. Deleting all files in the
Temp directory is a normal maintenance step.
Obtaining a License for the Upgrade to Resource Node
When you upgrade a standalone Cisco MXE 3000 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 3000 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-4.
•
Obtain the Product Authorization Key (PAK) for the Resource Node, which is located on the
Software License Claim Certificates that shipped with your devices.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
3-7
Chapter 3
Upgrading Cisco MXE 3000
Upgrading a Cisco MXE 3000 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 .
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.
Upgrading the Resource Node Device
Use this procedure to install the Resource Node software on the Cisco MXE 3000; 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 3-6.
•
Complete the “Obtaining a License for the Upgrade to Resource Node” procedure on page 3-7.
•
Complete the “Obtaining the Upgrade Software” procedure on page 3-3.
•
Close any applications that are running on the Cisco MXE 3000 you are upgrading.
Procedure
Step 1
Log in to the Cisco MXE 3000 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-R2-0-UPG.zip to the folder that you created inStep 2.
Step 4
Right click MXE3K-R2-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-R2-0-UPG and then enter Upgrade-Patch.bat.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
3-8
OL-16998-01
Chapter 3
Upgrading Cisco MXE 3000
Upgrading a Cisco MXE 3000 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 .
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 3000 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 3000 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 3-10.
Step 11
(Optional) To use the backed up Cisco MXE 3000 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 3-5.
Note
Do not reinstall the original license file for the standalone Cisco MXE 3000.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
3-9
Chapter 3
Upgrading Cisco MXE 3000
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 3-4.
Table 3-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 3000.
Back up the license to use if you return Cisco MXE 3000 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 3-7.
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 3000 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.
Note
After you install the new license, an available node displays in the
Available License Package drop-down, enabling you to assign it to this
Resource Node and configure its Hosts settings.
See also: Configuring Hosts Settings for Resource Manager Deployments,
page 2-17.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
3-10
OL-16998-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 3000
Revised: October 8, 2009, OL-16998-01
This section includes the following topics:
•
Security Best Practices for Cisco MXE 3000, page 4-1
•
Backup Guidelines for Cisco MXE 3000, page 4-2
Security Best Practices for Cisco MXE 3000
Cisco MXE 3000 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 3000 unless Cisco
recommends that you do so in the product documentation. See also: Cisco MXE 3000 Microsoft Hot
Fix Release Policy, page 4-2.
•
Do not use Cisco MXE 3000 for any purpose other than those we specify in the product
documentation.
•
Do not use Cisco MXE 3000 as a general purpose Windows device.
•
Do not browse to any Internet site on Cisco MXE 3000 other than www.cisco.com and
www.microsoft.com to download product documentation and patches.
•
Do not modify Windows components from the preconfigured defaults.
•
Do not change the Services startup types except for supported changes that are documented in the
product documentation.
•
Back up Cisco MXE 3000 regularly. See also: Backing Up Cisco MXE 3000, page 4-2.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
4-1
Chapter 4
Security Best Practices and Backup Guidelines for Cisco MXE 3000
Cisco MXE 3000 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 3000 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 3000, 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 3000.
If Microsoft releases a security hot fix for a catastrophic problem outside of the monthly cycle, Cisco
will release a corresponding technical bulletin, as well.
You can access Cisco MXE 3000 technical bulletins at the following URL:
http://www.cisco.com/en/US/products/ps9892/prod_bulletins_list.html
Backup Guidelines for Cisco MXE 3000
Cisco MXE 3000 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
Currently, you cannot back up automatically any configuration changes that you make at the
http://localhost/mxe/ 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 3000: 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 3000 to its factory image,
Backing Up Cisco MXE 3000
This section includes the following topics:
•
Backing Up the Folder Attendant Database, page 4-3
•
Backing Up Cisco MXE 3000 Files, page 4-3
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
4-2
OL-16998-01
Chapter 4
Security Best Practices and Backup Guidelines for Cisco MXE 3000
Backup Guidelines for Cisco MXE 3000
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 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 DCS, by using SQL Server Management Studio Express. SQL
Server Management Studio Express Version 2005 comes installed on Cisco MXE 3000.
Procedure
Step 1
Log in to Cisco MXE 3000.
Step 2
Click Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio Express
and connect to the Cisco MXE 3000 that you want to back up.
Step 3
In Object Explorer area, double-click Databases.
Step 4
Right-click DCS 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 DCS 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 DCS.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 3000 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 3000.
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
Launch Internet Explorer and log in to the WebUI at http://localhost/mxe/. The Administer > System
page appears.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
4-3
Chapter 4
Security Best Practices and Backup Guidelines for Cisco MXE 3000
Backup Guidelines for Cisco MXE 3000
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
Note the locations of the directories in the Input and Output sections.
Step 6
Back up the files in those directories.
Restoring Cisco MXE 3000 Configuration
This section includes the following topics:
•
Recovering Cisco MXE 3000, page 4-4
•
Restoring the Folder Attendant Database, page 4-4
•
Restoring Other Cisco MXE 3000 Files, page 4-5
Recovering Cisco MXE 3000
Recover the Cisco MXE 3000 by following the recovery process in Chapter 7, “Recovering
Cisco MXE 3000.”
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 3000.
Procedure
Step 1
Log in to Cisco MXE 3000.
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.
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 Control 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 3000 that you want to restore.
Step 4
Delete the existing Folder Attendant database:
a.
In Object Explorer area, double-click Databases.
b.
Right-click DCS and choose Delete.
c.
Click OK in the Delete Object window.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
4-4
OL-16998-01
Chapter 4
Security Best Practices and Backup Guidelines for Cisco MXE 3000
Backup Guidelines for Cisco MXE 3000
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
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 DCS 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 3000 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 Control and MXE Encoder services.
g.
Close the Control Panel.
Restoring Other Cisco MXE 3000 Files
Use this procedure to restore other files that are not contained in the Folder Attendant database.
Procedure
Step 1
Log in to Cisco MXE 3000.
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 3000.
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
Launch Internet Explorer and log in to the WebUI at http://localhost/mxe/. The Administer > System
page appears.
Step 6
Note the locations of the directories in the Input and Output sections.
Step 7
Restore the contents of all those directories from the most recent backup.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
4-5
Chapter 4
Security Best Practices and Backup Guidelines for Cisco MXE 3000
Backup Guidelines for Cisco MXE 3000
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 3000 Release 2.0
4-6
OL-16998-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
Running Reports for Cisco MXE 3000
Revised: June 8, 2009, OL-16998-01
This section includes the following topics:
•
Introduction to Reports, page 5-1
•
Custom Report Options, page 5-3
•
Understanding Reported Information, page 5-10
•
Running Predefined Reports, page 5-11
•
Available Predefined Reports, page 5-11
•
Viewing Report Output in Excel, page 5-17
Introduction to Reports
The Reports page, shown in Figure 5-1, enables users and administrators to run reports on
Cisco MXE 3000 activity.
To create a report from the WebUI, click Reports.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
5-1
Chapter 5
Running Reports for Cisco MXE 3000
Introduction to Reports
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 5-1
Reports Page
Reports may include predefined criteria and/or custom report options. The Reports page defaults to the
Job Custom Report view that allows users to select criteria for the report, which then returns Job
Summary, Task Summary, and Tasks Type Summary information.
At the top of the Reports page, the Select Report drop-down allows you to choose from the predefined
reports described in Table 5-1.
Table 5-1
Reports and Descriptions
Field Name
Description
Worker Summary
Displays information on each worker defined, including the Host on which the
worker runs, Limit and Expense for the worker, and information on the status
of the worker in the current configuration. See also: Worker Summary Report.
Worker By Id
Statistics
Displays information on workers including the Host, the name and ID number
of the worker, and the number and total duration of tasks run by that worker.
This report will not display information on workers that have been defined but
have not yet been assigned tasks. See also: Worker by Id Statistics Report.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
5-2
OL-16998-01
Chapter 5
Running Reports for Cisco MXE 3000
Custom Report Options
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
Reports and Descriptions
Worker Id Health
Statistics
Displays information on workers including the Host, the name and ID number
of the worker, and the total number of tasks run by each worker, the number that
failed to complete successfully, and rate of failure as a percentage of total tasks
run. This report is a text representation of the information displayed in the
Health view of the Status page. This report will not display information on
workers that have been defined but have not yet been assigned tasks. See also:
Worker Id Health Statistics Report.
Worker Type Health Displays summary information by type of worker, the total number of tasks run
Statistics
per type, the number that failed to complete successfully, and rate of failure as
a percentage of total tasks run. This report will not display information on
workers that have been defined but have not yet been assigned tasks. See also:
Worker Type Health Statistics Report.
Total Worker Hours Displays summary information on the amount of work done by each type of
Summary
worker calculated by comparing the start time and end time of each task run by
the worker. See also: Total Worker Hours Summary Report.
Max Queue Length
Displays the number of jobs submitted but not executed over a given time
interval (the number of pending jobs).
Custom Report Options
When the Reports page is initially opened, the Job Custom Report options display. From the Select
Report drop-down, click Job Custom Report or Task Custom Report. A job is composed of two or
more tasks, for example prefilter and H.264 encoder.
The Enter Conditions section, shown in Figure 5-2, lets you specify the search parameters for the report.
Figure 5-2
Enter Conditions Section
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
5-3
Chapter 5
Running Reports for Cisco MXE 3000
Custom Report Options
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 describes the fields.
Table 5-2
Query Builder Fields and Descriptions
Field
Description
Field
The Field drop-down allows you to define the type of data used as the selection
criteria for the report. The value selected in this field determines what displays in the
Condition and Value fields.
•
Job Id—Selects records based on the Job Id created when the job is submitted.
Every job submitted has a unique Job Id. The Job Id can be seen on the Job Status
window. See also: Setting Job Id Criteria.
•
Job Submit Time—Selects records based on the date and time the job was
submitted. See also: Setting Job Submit Time Criteria.
•
Job Stop Time—Selects records based on the date and time the job completed.
See also: Setting Job Stop Time Criteria.
•
Priority—Selects records based on the Priority assigned. Priority for a job can be
set in the Job Log or Job Status window. See also: Setting Priority Criteria.
•
Title—Selects records based on the Title value entered in the Title metadata field
on the File Job tab. Title information can also be viewed on the Job Log or Job
Status window. See also: Setting Title Criteria.
•
Author—Selects records based on the Author value entered in the Author
metadata field on the File Job tab. By default, the Author value will display the
username of the user logged in when the job was submitted. Author information
can also be viewed on the Job Log or Job Status window. See also: Setting
Author Criteria.
•
Failed—Selects records with a completion status of failed.
See also: Understanding Reported Information.
Condition
Defines the condition that must be met in order for the record to be selected. The
values on this drop-down will be determined by the value selected for Field. Each
Field value will cause the Condition options to be updated to match the type of
information stored in that Field.
Value
Allows you to enter a numeric value, date, or text string to be compared against
records in order for the selection to be made. Value is always a data entry field, but
the format of the field will change to match each Field selection. Rows where no value
is entered will be ignored when the report is run.
Join
Determines how rows of criteria will be compared with or against each other in
selecting data from the database. Join values are always the same.
•
And: Selects records meeting all criteria of rows connected by the Join.
•
Or: Selects records meeting the criteria of any of the rows connected by the Join.
Records are not required to contain values in more than one row.
The Custom Report views only allow simple Joins. Mixing Joins or defining multiple
lines of criteria can return unexpected results. Currently, it is not possible to nest
selection criteria.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
5-4
OL-16998-01
Chapter 5
Running Reports for Cisco MXE 3000
Custom Report Options
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 .
Include JobTask Statistics
Below the condition fields, several job statistic (Figure 5-3) or task statistic (Figure 5-4) checkboxes
display. These checkboxes correspond to metadata entries made on various CLUI job submission tabs.
These metadata serve to override various settings such as CGMS-A (Line 21 data) and graphics overlay
functionality. You may choose to check any, all, or none of the boxes to include this metadata in the
report.
Figure 5-3
Job Statistics
Figure 5-4
Task Statistics
Setting Job Id Criteria
Job Id is a numeric value. When the Field drop-down is set to Job Id, as shown in Figure 5-5, the
Condition and Value fields are modified to reflect values appropriate for numeric data.
Figure 5-5
Field Set to Job Id
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
5-5
Chapter 5
Running Reports for Cisco MXE 3000
Custom Report Options
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 describes the settings.
Table 5-3
Condition and Value Settings
Condition
Value
Equal to: Selects only records that have a Job Id that
exactly matches the Value entered to the right.
Value should always be a Job Id number.
Not equal to: Selects any record that does not match the
Value entered to the right. All records other than the one
identified by that Job Id will be included in the report.
Greater than: Selects all records with Job Ids that are
higher numbers than the Value entered to the right.
Because Job Ids are assigned in sequence, this is a useful
way to select a range of records.
Less than: Selects all records with Job Ids that are lower
numbers than the Value entered to the right.
Setting Job Submit Time Criteria
Job Submit Time is the date and time that the job was submitted. When the Field drop-down is set to Job
Submit Time, as shown in Figure 5-6, the Condition and Value fields are modified to reflect values
appropriate for date and time.
Figure 5-6
Field Set to Job Submit Time
Table 5-4 describes the settings.
Table 5-4
Condition and Value Settings
Condition
Value
Is: Selects only records that have a Job Submit
time that matches the Value entered to the right.
Value is modified to accept a date and to include
a tip about the format for how the date should be
Is not: Selects any record that does not match the entered. The time information indicated in the
Value entered to the right. All records that were format tip is shown in brackets, indicating that
submitted at any other time will be included in the specifying the exact time that the job was entered
is optional. Records will be selected correctly
report.
only if date criteria is entered.
Greater than: Selects all records that were
The format for date information will vary
submitted after the Value entered to the right.
depending on the database in use. For Microsoft
Less than: Selects all records that were submitted SQL Server databases, the mm/dd/yy format is
before the Value entered to the right.
used. For Oracle databases, enter dates in
dd-mon-yy format, where mon is the three
character abbreviation for the month.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
5-6
OL-16998-01
Chapter 5
Running Reports for Cisco MXE 3000
Custom Report Options
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 .
Setting Job Stop Time Criteria
Job Stop Time is the date and time that the job was submitted. When the Field drop-down is set to Job
Stop Time, as shown in Figure 5-7, the Condition and Value fields are modified to reflect values
appropriate for date and time.
Figure 5-7
Field Set to Job Stop Time
Table 5-5 describes the settings.
Table 5-5
Condition and Value Settings
Condition
Value
Is: Selects only records that have a Job Stop time Value is modified to accept a date and to include
that matches the Value entered to the right.
a tip about the format for how the date should be
Is not: Selects any record that does not match the entered. The time information indicated in the
format tip is shown in brackets, indicating that
Value entered to the right. All records that
specifying the exact time that the job was entered
completed at any other time will be included in
is optional. Records will be selected correctly
the report.
only if date criteria is entered.
Greater than: Selects all records that completed
The format for date information will vary
after the Value entered to the right.
depending on the database in use. For Microsoft
Less than: Selects all records that completed
SQL Server databases, the mm/dd/yy format is
before the Value entered to the right.
used. For Oracle databases, enter dates in
dd-mon-yy format, where mon is the three
character abbreviation for the month.
Setting Priority Criteria
Job Priority is the level of importance assigned in the Job Log or Job Status window. When the Field
drop-down is set to Priority, as shown in Figure 5-8, the Condition and Value fields are modified to
reflect values appropriate for Priority.
Figure 5-8
Field Set to Priority
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
5-7
Chapter 5
Running Reports for Cisco MXE 3000
Custom Report Options
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-6 describes the settings.
Table 5-6
Condition and Value Settings
Condition
Description
Equal to: Selects only records that have a Priority Value is changed to a drop-down of valid Priority
that matches the Value entered to the right.
values:
Not equal to: Selects any record that does not
match the Value entered to the right. Records with
any other Priority assigned will be selected.
Greater than: Selects all records with a higher
Priority than the Value entered to the right.
•
High: 1
•
Medium: 2
•
Low: 3
Less than: Selects all records with a lower Priority
than the Value entered to the right.
Setting Title Criteria
Title is metadata entered on the File Job tab. When the Field drop-down is set to Title, as shown in
Figure 5-9, the Condition and Value fields are modified to reflect values appropriate for text string data.
Figure 5-9
Field Set to Title
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
5-8
OL-16998-01
Chapter 5
Running Reports for Cisco MXE 3000
Custom Report Options
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-7 describes the settings.
Table 5-7
Condition and Value Settings
Condition
Description
Is: Selects only records where the Title is an exact The Value field allows you to type some or all of
match of the Value entered to the right.
the Title to be used for selection. Values are case
sensitive.
Is not: Selects any record where Title does not
match the Value entered to the right. Records with When Contains, Begin with, or Ends with are
any other Title will be selected.
used, it is not necessary to type wild card or other
Contains: Selects records where the Value entered special characters in the Value filed. Necessary
wildcards will be added automatically based on
to the right exists anywhere in the Title. This
allows users to report on records when only part the Condition selected.
of the title is known or to report on records where
all titles have a certain word or phrase in common.
Begin with: Selects records where the Title starts
with the Value entered to the right. All records
that begin with the characters, word, or phrase
entered in the Value field will be included in the
report.
Ends with: Selects records where the Title ends
with the Value entered to the right. All records
that end with the characters, word, or phrase
entered in the Value field will be included in the
report.
Setting Author Criteria
Author is metadata entered when the job is submitted. By default the Author value on the Submission
pages will be the username of the user logged in when the job is submitted. When the Field drop-down
is set to Author, as shown in Figure 5-10, the Condition and Value fields are modified to reflect values
appropriate for text string data.
Figure 5-10
Field Set to Author
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
5-9
Chapter 5
Running Reports for Cisco MXE 3000
Understanding Reported Information
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-8 describes the settings.
Table 5-8
Condition and Value Settings
Condition
Description
Is: Selects only records where the Author is an
exact match of the Value entered to the right.
The Value field allows users to type some or all of
the Author to be used for selection. Values are
case sensitive.
Is not: Selects any record where Author does not
match the Value entered to the right. Records with When Contains, Begin with, or Ends with are
any other Author will be selected.
used, it is not necessary to type wild card or other
Contains: Selects records where the Value entered special characters in the Value field. Necessary
wildcards will be added automatically based on
to the right exists anywhere in the Author field.
This allows users to report on records when only the Condition selected.
part of the author's name is known or to report on
records where authors share a common first or last
name.
Begin with: Selects records where the Author
starts with the Value entered to the right. All
records that begin with the characters or name
entered in the Value field will be included in the
report.
Ends with: Selects records where the Author ends
with the Value entered to the right. All records
that end with the characters or name entered in the
Value field will be included in the report.
Understanding Reported Information
Table 5-9 describes report results. Data displayed varies by report.
Table 5-9
Report and Data Descriptions
Data
Description
id
Displays the Job Id.
start time
Displays the earliest start time for all jobs included in the report.
stop time
Displays the last completion time of all jobs included in the report.
priority
1-3. 1 is highest. 3 is lowest.
title
Job Title entered at the time of job submission.
author
Author value entered at the time of job submission. By default, the Author
value will display the username of the user logged in when the job was
submitted.
task count
Displays the total number of tasks included in the report. Tasks that were
submitted but did not start because another task in the job failed will not be
included in the task count.
failed
Displays jobs that have failed.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
5-10
OL-16998-01
Chapter 5
Running Reports for Cisco MXE 3000
Running Predefined Reports
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 .
Running Predefined Reports
All of the predefined reports are run by selecting the desired report from the Select Report drop-down,
shown in Figure 5-11, and clicking the Run Report button.
See also: Available Predefined Reports.
Figure 5-11
Select Report Drop-Down
Location Filename Requirements
•
The Filename can be entered as a standard path, beginning with a lettered drive, or can be entered
as a UNC name.
•
The location selected for the report output:
– Must exist
– Must include a filename and extension, usually .CSV
– Must be accessible to the IUSR account used by the web server
– Must be accessible to the user in order to retrieve the file
Available Predefined Reports
This section includes the following topics:
•
Worker Summary Report, page 5-12
•
Worker by Id Statistics Report, page 5-13
•
Worker Id Health Statistics Report, page 5-14
•
Worker Type Health Statistics Report, page 5-15
•
Total Worker Hours Summary Report, page 5-16
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
5-11
Chapter 5
Running Reports for Cisco MXE 3000
Available Predefined Reports
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 .
Worker Summary Report
The Worker Summary Report, shown in Figure 5-12, displays the following information:
•
Each enabled worker
•
The Host on which the worker runs
•
Limit and Expense for the worker
•
The status of the worker in the current configuration
Figure 5-12
Worker Summary Report
Table 5-10 describes report results.
Table 5-10
Report Headings and Descriptions
Heading
Description
Host
Displays the Host that the worker is running on.
Type
Displays the type of worker identified in this row of the report.
Limit
Displays the Limit set for the worker on the listed Host. Limit is the maximum
number of workers that will run on a Host concurrently, and is set on the Host
Administration page.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
5-12
OL-16998-01
Chapter 5
Running Reports for Cisco MXE 3000
Available Predefined Reports
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-10
Report Headings and Descriptions
Heading
Description
Status
Displays the status of the worker at the time that the report was run.
•
Online: The worker is available to receive task assignments from the
Cisco MXE 3000.
•
Offline: The worker is not available to receive task assignments form the
Cisco MXE 3000.
Expense
Displays the Expense set for the worker on the Host Administration page. The
Expense is the work required by the worker expressed in relation to the overall
Capacity of the Host.
Active
Displays whether or not the Host is currently running.
VideoChannel
This value does not apply.
Worker by Id Statistics Report
This Worker by Id Statistics report, shown in Figure 5-13, displays the following information:
Note
•
Workers running on the Host
•
The number of tasks run by the worker
•
Total duration of tasks run by that worker
This report will not display information on workers that have been enabled but have not yet been
assigned tasks.
Figure 5-13
Worker By Id Statistics Report
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
5-13
Chapter 5
Running Reports for Cisco MXE 3000
Available Predefined Reports
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-11 describes report results.
Table 5-11
Report Headings and Descriptions
Heading
Description
Host
Displays the Host that the worker is running on.
Type
Displays the type of worker identified in this row of the report.
Id
Displays the unique ID number of the worker.
Total Tasks
Displays a count of the total number of tasks assigned to the worker.
Total Time
Displays the total amount of work done by the worker, measured in seconds.
Worker Id Health Statistics Report
The Worker Id Health Statistics Report, shown in Figure 5-14, displays the following information:
Note
•
The total number of tasks run by each worker
•
The number of tasks that failed to complete
•
The rate of failure as a percentage of total tasks run
This report will not display information on workers that have been enabled but have not yet been
assigned tasks.
Figure 5-14
Worker Id Health Statistics Report
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
5-14
OL-16998-01
Chapter 5
Running Reports for Cisco MXE 3000
Available Predefined Reports
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-12 describes report results.
Table 5-12
Report Headings and Descriptions
Heading
Description
Host
Displays the Host that the worker is running on.
Type
Displays the type of worker identified in this row of the report.
Id
Displays the unique ID number of the worker.
Failed Tasks
Displays a count of the number of tasks for this worker (by Host) that failed
to complete successfully.
Total Tasks
Displays a count of the total number of tasks assigned to the worker.
Percent
Displays a rate of failure calculated from the number of failed tasks
compared to the total task assignments.
Worker Type Health Statistics Report
The Worker Type Health Statistics report, shown in Figure 5-15, displays the following information:
Note
•
Total number of tasks run per type
•
The number that failed to complete successfully
•
The rate of failure as a percentage of total tasks run
This report will not display information on workers that have been enabled but have not yet been
assigned tasks.
Figure 5-15
Worker Type Health Statistics Report
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
5-15
Chapter 5
Running Reports for Cisco MXE 3000
Available Predefined Reports
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-13 describes report results.
Table 5-13
Report Headings and Descriptions
Heading
Description
Type
Displays the type of worker identified in this row of the report.
Failed Tasks
Displays a count of system-wide failures for this type of worker.
Total Tasks
Displays a count of the total number of tasks assigned to the worker
system-wide.
Percent
Displays a rate of failure calculated from the number of failed tasks
compared to the total task assignments.
Total Worker Hours Summary Report
The Total Worker Hours report, shown in Figure 5-16, displays high level summary information on the
amount of work done by each type of worker as measured in total time elapsed.
Figure 5-16
Total Worker Hours Summary Report
Table 5-14 describes report results.
Table 5-14
Report Headings and Descriptions
Heading
Description
Worker Name
Lists workers by name.
Days
Displays the number of 24-hour days worth of work completed by all
instances of the worker displayed to the left.
Hours
Displays the number of hours less than a full day completed by all instances
of the worker displayed to the left.
Minutes
Displays the number of minutes less than an hour completed by all instances
of the worker displayed to the left.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
5-16
OL-16998-01
Chapter 5
Running Reports for Cisco MXE 3000
Viewing Report Output in Excel
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-14
Report Headings and Descriptions
Heading
Description
Seconds
Displays the number of seconds less than a minute completed by all
instances of the worker displayed to the left.
Total Time
Displays the total amount of work done by the worker, measured in seconds.
Viewing Report Output in Excel
Output from the reports can also be saved to a tab delimited text file. This allows the report to be opened
for use in other applications, such as Word® or Excel®. The report will always display in the browser
window, even if it is also saved to a file.
This section includes the following topics:
•
Saving the Report Output, page 5-17
•
Viewing the Report in Excel, page 5-17
Saving the Report Output
Procedure
Step 1
From the Select Report drop-down, choose the desired report.
Step 2
Check the Output Results to Tab Separated File box, and enter path, file name, and file extension (such
as .txt), as shown in Figure 5-17.
Figure 5-17
Step 3
Enter Report Location
Click Run Report. The Output File Successfully Written message displays.
Viewing the Report in Excel
Procedure
Step 1
Browse to the location where you saved the file.
Step 2
Right-click the file, and select Open.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
5-17
Chapter 5
Running Reports for Cisco MXE 3000
Viewing Report Output in Excel
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
From the list of available applications, select Microsoft Excel. The file will open with report data
displayed in an Excel spreadsheet. Headings are not included in the exported output.
Step 4
Using standard Excel functionality, sort data as needed.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
5-18
OL-16998-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 3000
Revised: June 8, 2009, OL-16998-01
This section includes the following topics:
•
Logging, page 6-1
•
Troubleshooting, page 6-1
Logging
The ECS and LCS components are preconfigured 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 3000 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 3000 Release 2.0
OL-16998-01
6-1
Chapter 6
Troubleshooting Cisco MXE 3000
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 3000 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 3000 Release 2.0
6-2
OL-16998-01
Chapter 6
Troubleshooting Cisco MXE 3000
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 3000 to a Resource Manager or Resource Node?
A. Yes. The upgrade requires new software and a new license. See also: Upgrading Cisco MXE 3000,
page 3-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-17.
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 Folder Attendant and click System Status to see the jobs that are running on each
Resource Node. See also: Accessing the Folder Attendant User Interface, page 1-3.
Q. How do I know if a Resource Node is down?
A. When the Resource Node goes down or disconnects from the network, Resource Manager sends an
e-mail to the system administrator if a valid SMTP server and e-mail address are configured in the
System page.
About Configuration
Q. Can I create watch on 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 CLUI 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-9.
Q. Why is the Resource Manager not distributing sub-jobs among the Resource Nodes? Why are
Resource Nodes executing whole jobs?
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
6-3
Chapter 6
Troubleshooting Cisco MXE 3000
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 .
A. Resource Manager distributes sub-jobs to Resource Nodes when Single Node mode is disabled or
when Single Node mode is enabled in Soft mode. To disable Single Node mode, go to the System
page. Note that in Soft mode. the Resource Manager will start distributing sub-jobs when a
Resource Node reaches the Queue/Timeout limit. See also: Single Node Mode Section, page 2-12.
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: Hosts Settings, page 2-13.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
6-4
OL-16998-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 3000
Revised: June 8, 2009, OL-16998-01
Caution
This recovery process resets your Cisco MXE 3000 to the same state and configuration in which it was
delivered to you. All changes and content that has been copied to Cisco MXE 3000 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 3000, 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.
Table 7-1
Preparation Tasks for Recovery
To Back Up ...
Complete This Task
Job Profiles
Copy the profile directory to a location that is not on your Cisco MXE 3000.
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 3000.
The license file is located here: C:\Program Files\Cisco\Media Experience
Engine\license\mxe.lic
Source Content
Copy all watermark files and video files to a location that is not on your
Cisco MXE 3000.
The Cisco MXE 3000 was configured originally so that source content files are
located in the C:\media directory.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
7-1
Chapter 7
Recovering Cisco MXE 3000
Recovering the Cisco MXE 3000
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
Output Content
Copy all watermark files and video files to a location that is not on your
Cisco MXE 3000.
The Cisco MXE 3000 was configured so that encoded files are located in the
C:\output directory.
E-mail Server
Settings
Folder Attendant
Configuration
Open the WebUI System settings page at http://localhost/mxe/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 3000.
The faConfig.xml file is located here: C:\Program Files\Cisco\MXE Folder
Attendant Service\bin\
All watch directories that are located on the Cisco MXE 3000 device
will be deleted as part of the recovery process.
Note
Services
Open each of the three Cisco MXE 3000 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. Check each of the following
services:
•
MXE Folder Attendant
•
MXEControl
•
MXEEncoder
•
All Other Files
Caution
Temp Directory
Any files that you want to keep must be copied to a location outside
of the Cisco MXE 3000. All files will be deleted during the restore
process.
All of the files in the Temp directory can be discarded. Deleting all files in the
Temp directory is a normal maintenance step.
Recovering the Cisco MXE 3000
This section includes the following topics:
•
Preparing the Boot Disk DVD by Using Symantec Ghost Software, page 7-2
•
Using the Boot Disk DVD to Recover the Appliance, page 7-3
Preparing the Boot Disk DVD by Using Symantec Ghost Software
Use this procedure to create the boot disk DVD. You will use the disk to recover the Cisco MXE 3000
in the “Using the Boot Disk DVD to Recover the Appliance” procedure on page 7-3.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
7-2
OL-16998-01
Chapter 7
Recovering Cisco MXE 3000
Recovering the Cisco MXE 3000
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
•
Verify that the MXE3000 recovery disk, which was shipped to you, includes the following files:
– MXE3K.GHO
– MXE3K001.GHS
•
Note
Obtain the Symantec Ghost Solution Suite 2.5 Software CD.
Cisco does not provide this software.
•
Obtain a Windows PC on which to install the Symantec Ghost Boot wizard software.
•
Obtain an empty DVD on which Symantec Ghost software will burn the recovery files.
Procedure
Step 1
On the PC, install the Symantec Boot Wizard from Symantec Ghost Solution Suite software.
Step 2
From the recovery disk that was shipped to you, copy the MXE3K.GHO and MXE3K001.GHS files to
any folder on the PC.
Step 3
Run Symantec Boot Wizard software and complete the following steps to create the boot disk DVD:
Step 4
a.
Choose WinPE as the Pre-OS option and click Next.
b.
Choose Standard Ghost Boot Disk as the boot image type and click Next.
c.
Choose Symantec Ghost and click Next
d.
Leave blank the Client Settings and Mapped Drive settings and click Next.
e.
Select DHCP and click Next.
f.
Select CD/DVD ROM and click Next.
g.
Click Add, select the MXE3K.GHO and MXE3K001.GHS files from the folder where you copied
them, and click Next.
h.
Click Next. The image is created and the files are burned to the DVD. When Finish displays, the
DVD is ejected and ready to use.
Proceed to the “Using the Boot Disk DVD to Recover the Appliance” procedure on page 7-3.
Using the Boot Disk DVD to Recover the Appliance
Before You Begin
•
Complete the “Preparing the Boot Disk DVD by Using Symantec Ghost Software” procedure on
page 7-2.
•
Ensure that the Cisco MXE 3000 is powered down.
Procedure
Step 1
Insert the boot disk DVD in the DVD drive.
Step 2
Turn on the Cisco MXE 3000 and press F9 when it starts.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
7-3
Chapter 7
Recovering Cisco MXE 3000
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 .
Step 3
Choose Boot order and select CD-ROM as boot option 1.
Step 4
Press F10 to exit from BIOS.
The Cisco MXE 3000 boots from the DVD, loads Windows, and runs Ghost32.
Step 5
In the Ghost screen, click OK and then select Disk > From Image.
Step 6
Browse to the MXE3K.GHO file and select the file.
Ghost software loads the MXE3K.GHO file and exits with the command prompt.
Step 7
Remove the DVD.
Step 8
At the command prompt, enter the restart command.
The Cisco MXE 3000 boots twice automatically, goes through the Windows setup, and presents the
Windows Logon prompt.
Step 9
As the User ID, enter Administrator and press the Enter key for the password.
After booting, some product personalization occurs in the top left corner of the screen, after which time
the software completes installation and the Cisco MXE 3000 is ready for use.
Restoring the Configuration
This section includes the following topics:
•
Standalone or Resource Manager Configuration, page 7-4
•
Resource Node Configuration, page 7-6
Standalone or Resource Manager Configuration
To restore the configuration on a standalone Cisco MXE 3000 or Resource Manager, complete the tasks
in Table 7-2. After you complete these steps, your Cisco MXE 3000 will be ready to use.
Table 7-2
Tasks for Restoring a Cisco MXE 3000 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 3000. 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
Note
Source Content
Your Cisco MXE 3000 will not run without a license file.
Copy the backed up source content into the C:\Media directory.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
7-4
OL-16998-01
Chapter 7
Recovering Cisco MXE 3000
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 3000 Standalone or Resource Manager
Configuration (continued)
To Restore ..
Server Settings
Complete This Task
1.
Log into the WebUI at http://localhost/mxe by using the following
credentials:
•
Login User Name: admin
•
Password: leave this field blank
The System Settings page displays.
Folder Attendant
Configuration
2.
Scroll down to the General Settings section, and enter the SMTP server
information you documented in Preparing for Recovery.
3.
If you have a Resource Manager deployment, configure the
Resource Manager device. See also: Configuring 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\MXE Folder Attendant Service\bin\
2.
If the directories do not appear online, confirm that the user account the
Cisco MXE 3000 Folder Attendant service is running under has
permissions to read and write to the watch directory.
Note
3.
Services
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 3000.
If any of the Cisco MXE 3000 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.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
OL-16998-01
7-5
Chapter 7
Recovering Cisco MXE 3000
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 .
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: Hosts
Settings, page 2-13.
4.
Configure the Hosts settings for this Resource Node. See also:
Configuring Hosts Settings for Resource Manager Deployments,
page 2-17.
Deployment and Administration Guide for Cisco Media Experience Engine 3000 Release 2.0
7-6
OL-16998-01