Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration

Transcription

1 CHAPTER 4 Deploying Cisco MXE 3500 Release 3.2 in Standalone Configuration Revised: June 3, 2011 This section includes the following topics: About Cisco MXE 3500 Release 3.2, page 4-2 About the Cisco MXE 3500 Standalone Deployment, page 4-2 Guidelines for a Standalone Deployment, page 4-2 How to Configure Cisco MXE 3500 Release 3.2 for a Standalone Deployment, page 4-3 Accessing the Cisco MXE 3500 Web User Interface (Standalone or Resource Manager), page 4-3 Accessing the Cisco MXE 3500 Tools (Standalone and Resource Manager), page 4-4 Installing a License on Cisco MXE 3500 (Standalone or Resource Manager), page 4-4 Configuring the Input and Output Media Directories (Standalone or Resource Manager), page 4-7 Enabling System Administration Notifications (Standalone or Resource Manager), page 4-8 Configuring the Host Settings (Standalone Only), page 4-9 Confirming Service Accounts and Identifying Device Type (Standalone or Resource Manager), page 4-10 Creating a Folder Attendant Directory and Watch (Standalone or Resource Manager), page 4-11 Using Administrative Tools to Configure a Standalone Cisco MXE 3500, page 4-12 Testing a Cisco MXE 3500 Deployment (Standalone or Resource Manager), page 4-24 Obtaining Documentation and Submitting a Service Request, page 4-26 Providing Documentation Feedback, page

2 About Cisco MXE 3500 Release 3.2 Chapter 4 About Cisco MXE 3500 Release 3.2 Cisco MXE 3500 Release 3.2 is a software upgrade. Cisco MXE 3500 V2 Hardware If you have received a new Cisco MXE 3500 V2 appliance, then Release 3.2 software is preinstalled. You need only to complete network and admin user configuration before you configure the software for your deployment. To configure network settings, see the procedures in the Quick Start Hardware Installation Guide for Cisco Media Experience Engine 3500 that shipped with your product or Completing Initial Setup: Network Settings and Admin User Account Configuration section on page 1-6; then, return to this chapter for deployment information. Cisco MXE 3500 V1 Hardware If you are using the Cisco MXE 3500 V1 appliance, then the upgrade is required. To upgrade to Release 3.2, see Chapter 3, Backing Up and Restoring Data for Cisco MXE 3500 Release 3.0 Upgrade to Release 3.2 and Chapter 1, Installing and Configuring System Settings for Cisco MXE 3500 Release 3.2. Then, return to this chapter for deployment information. For purposes of this upgrade, a standalone, Cisco MXE 3500 that is not part of a cluster is considered a Resource Manager. About the Cisco MXE 3500 Standalone Deployment A standalone deployment consists of one or more Cisco MXE 3500s running as individual devices; each device has its own set of user accounts, job profiles, licensed features, and user interfaces. For information about Resource Manager deployments, see Chapter 5, Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration. To enable a licensed feature, you must purchase and install the feature license on the Cisco MXE For information about deploying licensed features, see Chapter 6, Deploying Licensed Features for Cisco MXE Guidelines for a Standalone Deployment The following configuration guidelines and restrictions apply to standalone deployments: Warning The built-in user account, mxe-service, is used to run the Cisco MXE 3500 application services and access all configured UNC paths and shared media folders. Do not delete this account or change the password. Otherwise, the device will not work properly. The Hostname must be unique and can be set as part of the installation process. We recommend that you use Remote Desktop Connection (RDC) to access remotely the Windows virtual machine on a Cisco MXE The IP address must be unique. 4-2

3 How to Configure Cisco MXE 3500 Release 3.2 for a Standalone Deployment Beginning with Release 3.1, all shared directories must be hosted under C:\shared. If you had shared folders or watch folders before to Release 3.1, you should copy them to C:\shared as subdirectories. Manually modify the affected setup, such as profiles, watch folders, and FTP configuration. How to Configure Cisco MXE 3500 Release 3.2 for a Standalone Deployment Release 3.2 requires the following mandatory configuration before using the system. Optional deployment configuration is identified, as well. Mandatory Configuration Completing Initial Setup: Network Settings and Admin User Account Configuration, page 1-6 Installing a License on Cisco MXE 3500 (Standalone or Resource Manager), page 4-4 Configuring the Input and Output Media Directories (Standalone or Resource Manager), page 4-7 Enabling System Administration Notifications (Standalone or Resource Manager), page 4-8 Configuring the Host Settings (Standalone Only), page 4-9 Optional Configuration Confirming Service Accounts and Identifying Device Type (Standalone or Resource Manager), page 4-10 Creating a Folder Attendant Directory and Watch (Standalone or Resource Manager), page 4-11 Testing a Cisco MXE 3500 Deployment (Standalone or Resource Manager), page 4-24 Deploying Licensed Features for Cisco MXE 3500, page 6-1 Accessing the Cisco MXE 3500 Web User Interface (Standalone or Resource Manager) The Cisco MXE 3500 web user interface (web UI) is the main interface that you use to set up encoder server and client preferences, create job profiles, and submit transcoding jobs. For information about Cisco MXE 3500 components, including user interfaces, see the User Guide for Cisco Media Experience Engine 3500 on Cisco.com, or click Help in the UI. Procedure Step 1 Step 2 Using a supported web browser, go to where mxe_ip_address is the hostname or IP address for the Cisco MXE Enter the default credentials: User Name: admin Password: admin 4-3

4 Accessing the Cisco MXE 3500 Tools (Standalone and Resource Manager) We recommend that you change the default password. Accessing the Cisco MXE 3500 Tools (Standalone and Resource Manager) You use the Cisco MXE 3500 web UI for most maintenance and operational tasks. However, you complete the following tasks by using other Cisco MXE 3500 tools: Set independent profile space Preview preprocessor clips Create and edit a QuickTime Encoder Profile Use additional deck control tools For information about Cisco MXE 3500 tools, see the User Guide for Cisco Media Experience Engine 3500 on Cisco.com, or click Help in the UI. Procedure Step 1 Step 2 RDC to mxe_ip_address. See Administrative User Accounts (Standalone or Resource Manager) section on page 4-21 for more information. Click Start > Programs > Cisco > Media Experience Engine > Media Experience Engine Tools. Installing a License on Cisco MXE 3500 (Standalone or Resource Manager) Obtaining the License Host ID, page 4-4 Obtaining a New, Upgrade, or Feature License, page 4-5 Installing a License File, page 4-7 Obtaining the License Host ID Licensing requires that you provide the License Host ID, which is used to generate a license. You use the same License Host ID for all license requests initial or upgrade. 4-4

5 Installing a License on Cisco MXE 3500 (Standalone or Resource Manager) For Resource Manager deployments, you must use the same License Host ID for every RN (Resource Node) or RM (Resource Manager) in your installation. For more information about Resource Manager deployments, see Chapter 5, Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration. Procedure Step 1 Step 2 Step 3 Login to the web UI. Under the Tools tab, click Upload License. Provide the License Host ID to Cisco, as shown in Figure 4-1, when you obtain a new, upgrade, or feature license. Figure 4-1 License Host ID String Obtaining a New, Upgrade, or Feature License Before You Begin You must have an account on Cisco.com to access the license website. Register for an account at the following URL: Obtain the Cisco MXE 3500 License Host ID. See also: Obtaining the License Host ID, page 4-4. Licensing requires that you provide the License Host ID, which is used to generate a license. You use the same License Host ID for all license requests initial or upgrade. 4-5

6 Installing a License on Cisco MXE 3500 (Standalone or Resource Manager) For Resource Manager deployments, you must use the same License Host ID for every RN (Resource Node) or RM (Resource Manager) in your installation. For more information about Resource Manager deployments, see Chapter 5, Deploying Cisco MXE 3500 Release 3.2 in Resource Manager Configuration. Obtain the Product Authorization Key (PAK) for you standalone Cisco MXE 3500 or the Product Authorization Keys (PAKs) for the Resource Manager device and Resource Nodes. The PAK is located on the Software License Claim Certificate that shipped with your device. Ensure that you understand the licensing process for Resource Manager deployments. See also: Guidelines for a Resource Manager Deployment section on page 5-2 and How to Configure Cisco MXE 3500 Release 3.2 for a Resource Manager Deployment section on page 5-3. You must complete the registration of the Resource Manager device first and obtain the license for that registration process before you register the Resource Node(s), completing registration and obtaining the updated license files one at a time. You will install the license that you receive for the final completed registration process on the Resource Manager device. Procedure Step 1 Step 2 Step 3 Step 4 Obtain the Product Authorization Key (PAK), which is located on the Software License Claim Certificate that shipped with your appliance. Go to Enter the PAK. If you are using the Cisco MXE 3500 to access the registration website, press the Enter key; otherwise, click the Submit button. Follow the on-screen prompts. Shortly after registration, you will receive an with the Cisco MXE 3500 license file. If this license file is for a Resource Manager and you have additional Resource Nodes to register, discard this license. Complete the registration process for each Resource Node, ensuring that you use the PAK for the Resource Node and the License Host ID for the Resource Manager. 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: Please have your valid Cisco ID and password available. As an alternative, you may also call one of these numbers: Asia-Pacific: (Australia: ) EMEA:

7 Configuring the Input and Output Media Directories (Standalone or Resource Manager) USA: You can find a complete list of Cisco TAC contacts at this URL: Installing a License File Use this procedure to install the license that you obtained on the Cisco MXE For Resource Manager deployments, install the license file only on the Resource Manager device. Procedure Step 1 Step 2 Step 3 Log in to the web UI. Under the Tools tab, click Upload License. Click Browse to navigate to and then select the license file. Step 4 Click Upload to install the license file on the Cisco MXE Step 5 Step 6 During first-time installation, check Replace Existing Licenses to replace the default demo license with the base license. Existing licenses will be backed up into a backup directory. Uncheck this option to install an incremental or feature license. License file name does not matter; it will be renamed. On successful upload the License uploaded successfully message displays. Click OK. The Host Administration page displays. Configuring the Input and Output Media Directories (Standalone or Resource Manager) For the Cisco MXE 3500 to obtain input and store output media, you must configure the input and output directories. Before You Begin Ensure that any directories that you are going to configure exist and are shared. Procedure Step 1 Step 2 Step 3 Log into the web UI as an administrator. From the Toolbox, select Administration > System. In the following fields of the Input section, enter the directories where Cisco MXE 3500 will obtain input media, such as \\mxe_ip_address\media. For more information, see the Input Section (Standalone Only) section on page

8 Enabling System Administration Notifications (Standalone or Resource Manager) Step 4 Step 5 Bumper Common Media Watermark In all the fields in the Output section, enter the directories where Cisco MXE 3500 will store output media, such as \\mxe_ip_address\output. For more information, see the Output Section (Standalone Only) section on page Click Save. Enabling System Administration Notifications (Standalone or Resource Manager) For Cisco MXE 3500 to send s for job completion or failure notifications, it must be configured to point to an server that allows s to be relayed from it. The sending of s is not required to complete transcoding jobs. Procedure Step 1 Step 2 Step 3 Login to the web UI as an administrator. Enter the SMTP server and for the system administrator: a. From the Toolbox, click Administration > System. b. In the General Settings section, enter the following settings: In the SMTP Server field, enter the name of the server that will be used to send notification messages. The server must be running the Simple Mail Transport Protocol (SMTP) service. In the in the System Administrator field, enter the address that will be used to contact the System Administrator. This address can be used to send messages to a regular account or to a text- enabled pager or cellular phone. The System Administrator address is used by Notification Profiles when the System Administrator options for From Address or To Address are selected. See also: General Settings Section (Standalone or Resource Manager), page c. Click Save. Create a Notification Profile: a. From the Toolbox, click Profile Management > New Profile. b. From the New Profile pop-up Profile Class drop-down, select Distribution. c. Highlight Notification, and click the New Profile button. The New Notification Profile page displays. d. Enter the following notification settings, and click Save: In the Common section, check the Profile Enabled box. 4-8

9 Configuring the Host Settings (Standalone Only) Step 4 In the Notification Criteria section, choose the status at which a notification is sent. In the Notification section, enter the following settings: Check the Enabled box to enable this profile for job processing. In the From field, select System Administrator. In the To field, select System Administrator. (Optional) Add the Notification Profile to any Job Profile for which you want to receive notifications: a. From the Toolbox, click Profile Management > New Profile or Open Profile. b. From the Profile Class drop-down, select Job, and click New Profile or Open Profile. c. Expand the Notification section. d. Select one or more Notification Profile(s). e. Click Save. Configuring the Host Settings (Standalone Only) Use this procedure to configure the Host settings for a standalone Cisco MXE Procedure Step 1 From the Toolbox, select Administration > Host. See also: Host Settings (Standalone Only), page Step 2 Modify the Host: a. From the Host Administration menu, click the arrow to the right of Host Options > Edit. The Edit Host pop-up displays. b. In the Host Name field, enter the Host name. This name must be a valid computer name that you configured for the standalone Cisco MXE c. In the Temp Directory field, enter the local or UNC path for the temp folder on the Host that you configured in Step b. d. Click Save. The modified Host displays in the Hosts pane. Cisco MXE 3500 does not verify that the Host name and the Temp Directory are valid during Host configuration. If either setting is invalid, errors will occur during operations that require their use. Step 3 Add workers to the Host that you created in Step 2: a. Select each Worker that is assigned to the Host. b. Click Permit or click Permit All. The list of workers displayed is controlled by your license level. If you select the Permit All option, only all non-live workers will be permitted. Live workers require manual entry of additional data. 4-9

10 Confirming Service Accounts and Identifying Device Type (Standalone or Resource Manager) Step 4 Step 5 Configure the Limit, Expense, and live capture information for each worker: a. Click each Worker and click Edit. The Edit worker pop-up displays. b. Enter the Limit and the Expense. c. For live captures, enter Capture Name, Capture Type, Video CH, and Audio CH. d. Click Save. At the top of the page, click Apply Configuration. Confirming Service Accounts and Identifying Device Type (Standalone or Resource Manager) This step is not required, but you may choose to confirm that your service accounts are enabled and have access to network locations. The service accounts are accounts that are local administrators on the Cisco MXE The accounts can be local computer accounts or domain accounts. Tip You can quickly determine the Cisco MXE 3500 device type (standalone/resource Manager, or Resource Node) by verifying which services are started. See Table 4-1. Procedure Step 1 RDC to mxe_ip_address. Step 2 Open Services by double-clicking the Services icon on your desktop or from the Control Panel. Step 3 Select the MXE services for your device type one at a time, as shown in Figure 4-2. Table 4-1 lists the services for each Cisco MXE 3500 device type. Table 4-1 Status of Services for Cisco MXE 3500 Device Types Service Standalone or Resource Manager Resource Node IIS Admin Service Started Service does not exist Mxe CAM Started Service does not exist Mxe ECS Started Service does not exist Mxe Encoder Started Started Mxe Folder Attendant Started Service does not exist Mxe Log Service Started Started 4-10

11 Creating a Folder Attendant Directory and Watch (Standalone or Resource Manager) Figure 4-2 Selecting a Service Account Step 4 Double-click each service except IIS Admin Service and then select the Log On tab. The service account can be changed from the default on this page. This action is not required for Cisco MXE 3500 to function. Your system is shipped with a default service account that has the correct permissions to run the default configuration. For certain functions across the network, such as copying output files to a different computer, Cisco MXE 3500 uses the service accounts to authenticate and access those network resources. You must make sure that these service accounts have appropriate access. Creating a Folder Attendant Directory and Watch (Standalone or Resource Manager) One of the key features of Folder Attendant is its ability to monitor directories and automatically initiate job processing when new or updated media/xml files appear. When a new or updated file, meeting the specified criteria, appears in a directory being monitored, Folder Attendant automatically initiates job processing based on the configured job parameter settings, such as profile and priority. You must first define directories to be watched on the Folder Attendant Administration page. Then, multiple watches can be configured per directory. For detailed field and setting descriptions and instructions on how to create, edit, and delete directories and watches, see the User Guide for Cisco Media Experience Engine 3500 on Cisco.com or by clicking Help from the main menu of the Folder Attendant user interface. This section includes the following topics: 4-11

12 Using Administrative Tools to Configure a Standalone Cisco MXE 3500 Chapter 4 Creating a Directory, page 4-12 Creating a Watch, page 4-12 Creating a Directory Procedure Step 1 Step 2 Step 3 From the Toolbox, click Folder Attendant. From the Directory drop-down, click Add. Enter the appropriate information in each of the fields, and click Save. If the Directory Path points to a network location, make sure that the service accounts have appropriate access to that network location. Creating a Watch Procedure Step 1 Step 2 Step 3 Step 4 From the Toolbox, click Folder Attendant. Highlight the Directory for which you want to add a watch, and from the Watch drop-down, click Add. The Folder Attendant Administration page displays Directory, Watch, Custom Metadata, and Override System Settings each of which contains a series of fields. Expand each section, and enter the appropriate information in each field. Save the Watch. Using Administrative Tools to Configure a Standalone Cisco MXE 3500 Although all possible configuration options are presented here, your system and user settings come preconfigured; moreover, some settings are not configurable for standalone Cisco MXE 3500 deployments. The only initial configuration required of you for standalone configuration is enabling system administration notifications. No other changes are necessary. However, we recommend that you add passwords or change the default user accounts. The Administration section of the Toolbox allows you to configure the following settings: Host Settings (Standalone Only), page

13 Using Administrative Tools to Configure a Standalone Cisco MXE 3500 System Settings, page 4-16 Administrative User Accounts (Standalone or Resource Manager), page 4-21 User Metadata Settings, page 4-22 IP Capture (Live Streaming) Settings (Standalone or Resource Manager), page 4-22 You must have Admin Tools permission to configure these settings. Host Settings (Standalone Only) The Host Administration page allows administrators to configure the Cisco MXE 3500 to work with computers on the network. Host is simply another word for the computer or system that runs the Cisco MXE The Host Administration page is used to tell the Enterprise Control System (ECS) what the Hosts are capable of running (what the load capacity of the machine is and what software is installed). From the Toolbox, click Administration > Host to display the Host Administration page and view summary information about workers configured on that Host along with a limited number of editable fields. Figure 4-3 shows the Host Administration page. 4-13

14 Using Administrative Tools to Configure a Standalone Cisco MXE 3500 Chapter 4 Figure 4-3 Host Administration Page and Settings Table 4-2 describes the Host settings. Table 4-2 Host Settings and Descriptions Setting Host Status Description This is the name of the machine running the Cisco MXE 3500 LCS. The computer name and the Host name must match exactly. To verify the computer name of a Windows Server computer, right-click the My Computer icon on either your desktop or in your Start Menu, select Properties, then select the Computer Name. For an NT computer, right-click Network Neighborhood, select Properties, and select the Identification tab. Alternately, type the hostname command at the command prompt to display the computer name. Displays the status of the Host: Enabled or Disabled. To change the status, right-click the Host or click Host Options, and select Enabled or Disabled. If the status is disabled, jobs will not schedule on that Cisco MXE 3500 node. Port TCP port that the LCS is listening on. The default is

15 Using Administrative Tools to Configure a Standalone Cisco MXE 3500 Table 4-2 Host Settings and Descriptions Capacity Temp Directory (UNC Name) Reflects a numeric value (0-99) assigned for the total available processing capacity of the displayed Host. Capacity can be any number for a given Host, but it is important that all Hosts be numbered according to the same standards. For example, for one particular Host it will not matter if the total capacity is set at 5 or at 10. However, if there is another Host that has twice the capacity, the capacity of both Hosts should be listed in common terms. So, a Host that is twice as powerful would have a capacity of 10 if the first Host was 5, or 20 if the first Host was 10. Capacity is directly related to processor capacity, but may also be affected by drive speed, network congestion, and other factors. All of the factors that affect the amount of work a particular Host can do efficiently should be considered when assigning a capacity value. Numbers between 5 and 30 are typically best. Setting this to a high number > 30 can make the system status monitor hard to read. Specifies the directory where temporary files and preprocessor output will be store, such as \\mxe_ip_address\temp. Unless the Preprocessor box in the Output Profile is checked to specify that Preprocessor files should be saved, files written to the Temp Directory will be deleted automatically when encoding is complete. Permitted? Green checkmark: Indicates that the worker listed to the right is configured to run on the displayed Host and that it is currently online and available to process tasks. Red X: Indicates either: The worker listed to the right is configured to run on the displayed Host but is currently offline and cannot be contacted by the ECS. or The worker is not enabled or configured. Worker Displays a list of all workers that have been configured to run on the displayed Host. The Name, DV, DVCAM, Video Channel, and Audio Channel fields appear only for Live capture workers and define the location of the capture card on the Host. Channels are numbered sequentially from 0. Licensed Indicates the number of concurrent instances of this worker type (example: prefilter, encoder, distribution) that can be running on the system (all nodes controlled by that ECS). This value is defined in the Cisco MXE 3500 license file. Limit Displays the maximum number of a particular worker that can be run simultaneously on the displayed host. Limit is a fixed setting in the Cisco MXE 3500 to return the best possible performance. Expense The expense of a worker is expressed as a portion of Host capacity. Expense is a fixed setting in the Cisco MXE 3500 to return the best possible performance. Capture Name This setting is not available in Cisco MXE Defines the name associated with a live capture worker. Because Hosts can have more than a single video capture card and can be configured to run more than one Live capture worker, the Capture Name is required in order to identify the specific capture card used by the worker. This is only displayed for Live capture workers. 4-15

16 Using Administrative Tools to Configure a Standalone Cisco MXE 3500 Chapter 4 Table 4-2 Host Settings and Descriptions Capture Type This setting is not available in Cisco MXE Type of capture card (DV, DVCAM, AJA-SDI, Custom, etc.). Selection of a non-custom value will predefine the audio and video channel. Video This setting is not available in Cisco MXE CH/Audio CH Displays Video Channel and Audio Channel for each Live-capture worker. System Settings System Administration is used to define locations and parameters for files and directories used with the Cisco MXE It also includes settings for other system-wide parameters. Access this page from the Toolbox by clicking Administration > System. You must have Admin Tools permission to configure these settings. Input Section (Standalone Only) The System page is made up of the following sections: Input Section (Standalone Only), page 4-16 Output Section (Standalone Only), page 4-18 General Settings Section (Standalone or Resource Manager), page 4-18 Status Settings Section (Standalone or Resource Manager), page 4-18 Data Purging Section (Standalone or Resource Manager), page 4-19 Audio Capture Section (Standalone or Resource Manager), page 4-20 Figure 4-4 shows the Input section settings. Figure 4-4 Input Settings Table 4-3 describes the settings. 4-16

17 Using Administrative Tools to Configure a Standalone Cisco MXE 3500 Table 4-3 Input Settings and Descriptions Setting Bumper/Trailer Directory Common Directories Media Directory Profile Directory Valid Input Extensions Watermark Directory Description Defines the location of files that can be used as bumpers or trailers to clips encoded with the Cisco MXE The Bumper/Trailer Directory controls the directory path where the Cisco MXE 3500 searches for files displayed in the Bumper Source and Trailer Source fields in the Preprocessing Profile page. The Bumper/Trailer Directory value can be entered either as a UNC path to a network share or to a mapped drive in the case of a deployment using a storage area network (SAN) or a single node deployment. The Bumper/Trailer Directory location must be accessible to all hosts. Defines the directories where media files will be stored. Multiple directories can be defined. A semi-colon is used to separate directory entries. The Common Directory values can be entered either as a UNC path to a network share or to a mapped drive in the case of a deployment using a storage area network (SAN) or a single node deployment. The Common Directory locations must be accessible to all hosts. Defines the directory where media files that will be submitted to the Cisco MXE 3500 are stored. The Media Directory controls the directory path where the Cisco MXE 3500 searches for files displayed in the Source box on the File Submission page. The Media Directory value can be entered either as a UNC path to a network share or to a mapped drive in the case of a deployment using a storage area network (SAN) or a single node deployment. The Media Directory location must be shared and accessible to all Hosts. The System Administration page will give a warning if the value entered is not a UNC path, which is recommended. If using a mapped drive, all nodes configured to work with the Cisco MXE 3500 must have the location mapped as the same drive. Defines the default path the ECS will use to search for Job Profiles when processing a submitted job. Defines the list of valid extensions for files in Common Directories. Only files with extensions listed in this field will be displayed in the Selection List window in the Input section of the File Job Submission form. A semi-colon is used to separate file-extension entries. Defines the location of files that can be used as watermarks for clips encoded with the Cisco MXE The Watermark controls the directory path where the Cisco MXE 3500 searches for files displayed in the Source drop-down in the Watermark section of the Preprocessing Profile page. The Watermark Directory value can be entered either as a UNC path to a network share or to a mapped drive in the case of a deployment using a storage area network (SAN) or a single node deployment. The Watermark Directory location must be accessible to all hosts. 4-17

18 Using Administrative Tools to Configure a Standalone Cisco MXE 3500 Chapter 4 Output Section (Standalone Only) Output Directories define the location the Cisco MXE 3500 will use to save files of each encoding format supported by the licensing levels of your Cisco MXE 3500 system. Encoded files will be saved to the defined directories when either no Distribution > Output Profile is included in the Job Profile or when the checkbox in the Save Local File section of the Output Profile has been checked. The Microsoft Output Directory value can be entered either as a UNC path to a network share or to a mapped drive in the case of a deployment using a storage area network (SAN) or a single node deployment. General Settings Section (Standalone or Resource Manager) Table 4-4 describes the settings. Table 4-4 General Settings and Descriptions Setting Default Copyright LCS Disconnect Notifications LCS Notification Frequency License Expiration Warning Restart IP Capture/Webcast on Failure Simultaneous Node Restart Limit SMTP Server System Administrator Description Defines the default copyright information populated to the copyright field in all job submission pages. The Default Copyright is a system-wide setting. The value entered can be overwritten by the user when jobs are submitted by typing over the default information displayed. If yes, the Cisco MXE 3500 generates an (sent to the System Administrator) when an LCS disconnects from the ECS. Frequency in seconds in which an LCS disconnect will be generated if multiple disconnects occur. Defines the period, in days, ahead of the license expiration date that an will be sent to the address defined in the System Administrator field. yes: restart IP Capture on failure no: do not restart IP Capture on failure Defines the number of times an IP Capture job may restart due to problems encountered during capture and/or streaming before the job will fail. Identifies the server used to send notification messages. The server identified must be running the Simple Mail Transport Protocol (SMTP) service to enable processing of messages. Stores an address used to contact the System Administrator. This address can be used to send messages to a regular account or to a text-enabled pager or cellular phone. The System Administrator address is used by Notification Profiles when the System Administrator options for From Address or To Address are selected. Status Settings Section (Standalone or Resource Manager) Figure 4-5 shows the Status Settings section. 4-18

19 Using Administrative Tools to Configure a Standalone Cisco MXE 3500 Figure 4-5 Status Settings Table 4-5 describes the settings. Table 4-5 Setting Monitor Window Display Auto Reap (Minutes) Include Failed Jobs in Auto Reap Status Settings and Descriptions Description This setting only applies in Console mode. If set to on, some workers (like preprocessor and encoders) will display a monitor window which displays the video being processed. This option does use system resources (such as CPU cycles, memory) and will slow down overall job processing. It may be used for debugging purposes or viewing encoded output. Defines the Auto Reap interval used to clear job information from monitoring pages. The time defined for Auto Reap determines how long information on a job will be displayed in monitoring pages before it expires. The Auto Reap interval is counted from the time the job completes. yes: include failed jobs in Auto Reap no: do not include failed jobs in Auto Reap Data Purging Section (Standalone or Resource Manager) Over time, job data, such as job, task, executioncontext, executioncontextlog, and related tables, grow and fill up disk space. The Data Purging section allows you to configure automated system purging, which physically deletes the appropriate records. After initial or reset of Data Purging values, restart the CAM service to enable this feature or for changes to take place immediately. Figure 4-6 shows the Data Purging section. 4-19

20 Using Administrative Tools to Configure a Standalone Cisco MXE 3500 Chapter 4 Figure 4-6 Data Purging Settings Table 4-6 describes the settings. Table 4-6 Data Purging Settings and Descriptions Setting Description Purge Enabled yes: purge enabled no: purge not enabled Job Completion In minutes, how long after the job was completed, before it is deleted. Duration Purge Batch Size This setting limits the number of jobs to be deleted. Time to Execute Purge Configures the time of day the purge occurs. Purge Interval Configures the number of days between purges. Audio Capture Section (Standalone or Resource Manager) Figure 4-7 shows the Audio Capture section. Figure 4-7 Audio Capture Settings Table 4-7 describes the settings. 4-20

21 Using Administrative Tools to Configure a Standalone Cisco MXE 3500 Table 4-7 Setting Drift Compensation Sample Rate Audio Capture Settings and Descriptions Description From the drop-down, select on to enable audio and video synchronization. This is only necessary when capturing clips longer than 5 minutes that use an analog audio capture card. It is not necessary when using digital audio input (embedded SDI, AES/EBU, or DV). When capturing long analog audio clips, the Cisco MXE 3500 will insert or remove frames to maintain audio sync over a long time period. The effect of this compensation is not easily visible in typical streaming media output or anything smaller in size or frame rate). However, a user may see a skipping effect on D1 clips, for example, when encoding long clips into MPEG2 format. The only work-around is to switch to digital audio input. Sets audio sampling rate to trade off audio quality and transmission bandwidth and file size limitations. Administrative User Accounts (Standalone or Resource Manager) Windows VM The following two virtual machines (VMs) comprise the Cisco MXE 3500 application (MXE application): Windows VM, page 4-21 Hosts the Cisco MXE 3500 Release 3.2 software. Linux VM, page 4-22 Provides external services, such as FTP and HTTP, and acts as a proxy to services on the Windows VM for added security. Table 4-8 Predefined Windows User Accounts Account Default Password Function Windows VM mxe-service Cisco1 Used to access shared folders and for Cisco MXE 3500 applications Do not delete or change the password for this account; otherwise, the Cisco MXE 3500 will not work properly. admin change_it Used to perform Windows administrator functions Used to RDC and log in to the Windows VM The Linux configuration wizard that launches during first boot requires you to change this password. The configuration synchronizes the Windows VM admin and Linux VM admin passwords. 4-21

22 Using Administrative Tools to Configure a Standalone Cisco MXE 3500 Chapter 4 Table 4-8 Predefined Windows User Accounts Account Default Password Function Windows MXE Web UI (Web UI) admin admin Used to log in to the Cisco MXE 3500 Web UI We recommend that you change the admin password immediately. You change this password in the Web UI. Linux VM Table 4-9 Predefined Linux User Accounts Account Default Password Function mxe-service Cisco1 Used for communication between Linux and Windows VMs Do not delete or change the password for this account; otherwise, the Cisco MXE 3500 will not work properly. mxe-user Used to access default shared folders This account is disabled by default. When you enable access to shared folders in the Linux configuration utility, you are prompted to enter a password. admin change_it Used to perform system admin functions The Linux configuration wizard that launches during first boot requires you to change this password. root C1sco!23 Used to perform root functions User Metadata Settings This User Metadata Administration page allows you to create custom name/value pairs that can be submitted with each job (and each task in the job). This custom metadata is returned in detailed job status including the HTTP POST job-status XML. This metadata (if submitted) is also stored in the database for each job and can be used for reporting purposes (like tracking which organization submitted which jobs) or (via HTTP POST) where it is passed back to other systems (like Velocity). The Data Type can be defined as Integer, String, Decimal, or Enum (Enumeration). This type is used for validation when entering the user metadata values on the Job Submission pages. Access the User Metadata Administration page from the Toolbox by clicking Administration > User Metadata. The New or Edit User Metadata e pop-up displays and allows you to create and modify user metadata settings. IP Capture (Live Streaming) Settings (Standalone or Resource Manager) Cisco MXE 3500 enables ingest of live MPEG-2 Transport streams over UDP/IP with management, configuration, and status that enable general use of this feature. IP captures are limited to transport streams with MPEG2 video and AC3/Layer2/AES3 audio essences. 4-22

23 Using Administrative Tools to Configure a Standalone Cisco MXE 3500 The IP Capture Configuration page is used by administrators to add, edit, or delete an IP capture source. Access this page from the Toolbox by clicking Administration > IP Capture. The New or Edit IP Capture Source pop-up, shown in Figure 4-8, allows you to create and modify profile spaces. Figure 4-8 IP Capture Source Settings Table 4-10 describes the settings. Table 4-10 IP Capture Source Settings and Descriptions Setting Name Protocol IP Address Port Program Map PID Description Unique IP Capture Source name. Source protocol: UDP, RTP, MMS, or HTTP For MPEG2 sources: the multicast IP address of the source MPEG-2 Transport Stream. The IP addresses reserved for this purpose are from to For Windows Media sources: the source stream URL. The multicast port to bind to. Values range from 0 to (only applicable for UDP and RTP sources). Specifies the Program Map Table Packet ID (PMT PID) of the desired program in an MPEG-2 Multi-Program Transport Stream (MPTS). For MPEG-2 Single Program Transport Streams (SPTS) or if not specified, the first program listed in the Program Map Table is used automatically. Valid values range from 16 to (Only applicable for UDP and RTP sources.) Before submitting a job, you must 1. Add an IP capture source. 2. Configure the ipcaptureprefilter Worker on the Host Administration page. See also: Host Settings (Standalone Only), page On the Live Submission page, set the Video Format to IP Capture, select the IP Capture Source that you defined, Start and Stop Trigger Types. To view the Live Submission Page, from the Toolbox, expand Submission and click Live. 4-23

24 Configuring User Accounts Chapter 4 Configuring User Accounts In a standalone Cisco MXE 3500 configuration, there is a single administrative user, and there is no option to create additional web UI users. User management, including defining roles and restricting user access to web UI features, is available in Resource Manager configuration. For more information about user management, see the User Settings (Resource Manager Only) section on page Testing a Cisco MXE 3500 Deployment (Standalone or Resource Manager) To ensure your system has been correctly deployed and configured, perform the following tests: Test 1: Submit a Job Using File Job Submission, page 4-24 Test 2: Submit a Job Using Folder Attendant, page 4-25 Test 3: Verify a Licensed Feature is Enabled, page 4-25 Test 1: Submit a Job Using File Job Submission Before You Begin In the \\Resource_Manager_IP_Address\media folder, look for any sample media file, e.g., within \SpeechToTextFiles, or copy an existing media file to the \\Resource_Manager_IP_Address\media directory. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Login to the web UI. From the Toolbox, select: Submission > File. The File Job Submission page should appear. In the Profile section, choose Cable_Broadband.job.awp. In the Input section, complete the following tasks: a. Select Browse b. Select the file s source directory, for example, \\Resource_Manager_IP_Address\media\. From the toolbox, select Monitoring > Job Status. Continue watching the Job Status window to make sure the job completes. Browse to the \\Resource_Manager_IP_Address\Output folder, and locate Sample.Cable_Broadband.Cable_Broadband.wmv, and play the file. Accept any warning messages or alerts Windows Media Player may display. 4-24

25 Testing a Cisco MXE 3500 Deployment (Standalone or Resource Manager) Test 2: Submit a Job Using Folder Attendant Before You Begin If you completed Test 1: Submit a Job Using File Job Submission, delete the media files from the \\Resource_Manager_IP_Address\media and \\Resource_Manager_IP_Address\output folders. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Login to the web UI. Add a directory for the Folder Attendant to monitor: a. From the Toolbox, select Folder Attendant. b. From the Directory drop-down menu, select Add. The Directory fields display on the Folder Attendant Administration page. c. In the Directory Path field, enter \\Resource_Manager_IP_Address\media and complete other fields as needed. Add a watch for the directory: a. From the Toolbox, click Folder Attendant. a. Highlight the Directory for which you want to add a watch, and from the Watch drop-down, click Add. The Watch fields display on the Folder Attendant Administration page. b. In the Watch Extensions field, enter MPEG-4. c. In the Job Profile field, select Cable_Broadband. d. Complete other fields as needed. From the Toolbox, select Monitoring > Job Status. Select any media file from your collection and copy it to the media directory (\\Resource_Manager_IP_Address\Media) folder. Watch the Job Status pane to make sure the job starts and completes. Browse to the \\Resource_Manager_IP_Address\Output folder, and locate the Sample.Cable_Broadband.Cable_Broadband.wmv file. If you created another version of the file in Test 1: Submit a Job Using File Job Submission section on page 4-24, check that the time stamp is current to verify that the file was recreated, and play the file. Test 3: Verify a Licensed Feature is Enabled To verify that the Live Ingest feature is enabled after you install a feature license, see the following sections: Configuration Workflow for Cisco MXE 3500 Deployments with Live WMV IP Streaming, page 6-3 Configuration Workflow for Cisco MXE 3500 Deployments with Live Flash 8 and H.264 IP Streaming, page 6-5 To verify that the Speech to Text or Graphics Overlay feature is enabled after you install a feature license, see the following sections: 4-25

26 Providing Documentation Feedback Chapter 4 Configuration Workflow for Speech-to-Text Conversion, page 6-29 Configuration Workflow for the Graphic Overlay Feature, page 6-30 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: Subscribe to the What s New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0. Providing Documentation Feedback To provide feedback on this Cisco MXE 3500 document, or to report an error or omission, you can use the online, Embedded Feedback form. The form appears when you click the Give us Feedback link that is located at the top right of each chapter in this guide, which you can access at the following URL: You can also send feedback to mxe-doc@cisco.com. 4-26