Cisco MXE 5000 Series (Media Experience Engines)

Table Of Contents

Quick Start Deployment Guide for the Cisco MXE Video Interoperability Solution 1.0 (Cisco MXE 5600 and Cisco MXE-OS Release 1.0)

Task 1: Prepare for Deployment

Task 2: Install the Cisco MXE 5600 Chassis

Task 3: Connect the Cisco MXE 5600 to the Network and Update the Software to the Latest Version

Task 4: Configure Basic System Management Features for the Cisco MXE 5600

Task 5: Configure the Cisco MXE 5600 for Video Interoperability

Task 6: Configure External Solution Components for Video Interoperability

Task 7: Verify Configuration

Task 8: Troubleshoot Configuration

Quick Start Deployment Guide for the Cisco MXE Video Interoperability Solution 1.0 (Cisco MXE 5600 and Cisco MXE-OS Release 1.0)

---

Revised: May 26, 2010

This document provides information and resources to help you deploy the Cisco MXE 5600 and additional components for the Cisco MXE Video Interoperability Solution.

•Task 1: Prepare for Deployment

•Task 2: Install the Cisco MXE 5600 Chassis

•Task 3: Connect the Cisco MXE 5600 to the Network and Update the Software to the Latest Version

•Task 4: Configure Basic System Management Features for the Cisco MXE 5600

•Task 5: Configure the Cisco MXE 5600 for Video Interoperability

•Task 6: Configure External Solution Components for Video Interoperability

•Task 7: Verify Configuration

•Task 8: Troubleshoot Configuration

Task 1: Prepare for Deployment

This task section explains how to prepare for solution deployment.

Step	Task	Reference
1.	Identify supported components.	Compatibility Matrix for Cisco MXE Video Interoperability Solution
2.	Review installation notes and caveats.	Release Notes for Cisco MXE-OS
3.	Identify supported deployment models.	Deployment Guide for Cisco MXE Video Interoperability Solution •Introducing the Cisco MXE Video Interoperability Solution •Deployment Models for the Cisco MXE Video Interoperability Solution
4.	Review the network infrastructure guidelines, including quality of service (QoS), capacity planning, and scalability.	Deployment Guide for Cisco MXE Video Interoperability Solution •Network Design Considerations for the Cisco MXE Video Interoperability Solution •QoS Guidelines for the Cisco MXE Video Interoperability Solution
5.	Understand the Cisco Unified Communications System's partition and calling search space (CSS) configuration.	Deployment Guide for Cisco MXE Video Interoperability Solution •Configuring Cisco Unified Communications Manager for the Cisco MXE Video Interoperability Solution
6.	See an example solution deployment.	Deployment Guide for Cisco MXE Video Interoperability Solution •Example Solution Deployment
7.	Prepare the dial plan for your deployment.	Deployment Guide for Cisco MXE Video Interoperability Solution •Planning Considerations
8.	Learn about default profiles that you can modify to simplify Cisco MXE-OS configuration.	Deployment Guide for Cisco MXE Video Interoperability Solution •Configuring Cisco MXE-OS for the Cisco MXE Video Interoperability Solution
9.	Learn about site and rack requirements for hardware installation.	Hardware Installation and Reference Guide for Cisco Media Experience Engine 5000 Series •Preparing the Site •Installing the Cisco MXE Chassis

Task 2: Install the Cisco MXE 5600 Chassis

This task section explains how to physically install and power up the Cisco MXE 5600.

Step	Task	Reference
1.	The Cisco MXE 5600 has special environmental, space, power, cooling, and ambient noise requirements. Choose the rack location and prepare the site to accommodate those requirements.	Hardware Installation and Reference Guide for Cisco Media Experience Engine 5000 Series •Preparing the Site
2.	The Cisco MXE 5600 requires additional tools and equipment for installation that do not ship with the chassis, such as a mechanical lift. Obtain the required tools and equipment and install the rails on the rack. Then, install the chassis on the rails. Note We recommend that at least two people install the chassis.	Hardware Installation and Reference Guide for Cisco Media Experience Engine 5000 Series •Preparing the Site •Installing the Cisco MXE Chassis
3.	The Cisco MXE 5600 requires additional tools and equipment that do not ship with the chassis to ground the chassis, such as a grounding wire. Obtain the required tools and equipment and connect the chassis to the data center earth ground.	Hardware Installation and Reference Guide for Cisco Media Experience Engine 5000 Series •Preparing the Site •Installing the Cisco MXE Chassis
4.	Connect a terminal server to the Cisco MXE NPM (CONSOLE) port.	Hardware Installation and Reference Guide for Cisco Media Experience Engine 5000 Series •Cable and Port Specifications
5.	Connect the power supply modules to AC power and then power on the system. Booting the system takes up to 10 minutes. At the end, a login prompt will appear. Note Transient alarms can display during the boot up process as system components initialize. Example: *** 2010-04-21 10:10:47 Eqpt Minor Chassis Shelf Manager: Redundancy lost *** *** 2010-04-21 10:12:14 Eqpt Cleared Chassis Media Resources: No resources *** . . . Starting GoAhead Infrastructure: nohup: appending output to `nohup.out' Success Node1 login:	Hardware Installation and Reference Guide for Cisco Media Experience Engine 5000 Series •Installing the Cisco MXE 5600 Chassis •Powering On and Verifying Hardware Status
6.	Verify that all Cisco MXE 5600 LEDs are GREEN except the System LED, which will be RED. This alarm occurs because the Ethernet 1/1 and MGT1 interfaces are not yet configured.	Hardware Installation and Reference Guide for Cisco Media Experience Engine 5000 Series •Powering On and Verifying Hardware Status
7.	Connect the Cisco MXE NPM management port (MGT1) and data port (Ethernet 1/1) to Ethernet ports on the network device. These ports uses a 10/100/1000 Ethernet connection with an RJ-45 interface.	Hardware Installation and Reference Guide for Cisco Media Experience Engine 5000 Series •Connecting the Console to the Network

Task 3: Connect the Cisco MXE 5600 to the Network and Update the Software to the Latest Version

This task section explains how to connect the Cisco MXE 5600 to the network through its Ethernet interface and update the Cisco MXE-OS software to the latest version.

Step	Task	Reference
1.	Log in with the following default credentials at the Cisco MXE-OS command prompt: •User ID: admin •Password: admin Example: Node1 login: admin Password:	Configuration Guide for Cisco MXE-OS •Using the Cisco MXE-OS Setup Utility
2.	Check for alarms. Verify that only Link/Interface Down alarms display for the MGT1 and Ethernet 1/1 interfaces. These alarms occur because the interfaces are not yet configured. Note If a Chassis Media Resources: No resources alarm displays, the media resources are still initializing. Wait until the alarm clears; then, verify the alarm status again. Example: *** 2000-03-04 12:49:10 Eqpt Cleared Chassis Media Resources: No resources *** mxe# show facility-alarm status 2 alarms currently active Alarm time Type Severity Description ------------------- ---- -------- ---------------------------------------------- 2000-03-04 12:44:12 Eqpt Major MGT1 : Link/Interface Down 2000-03-04 12:45:33 Eqpt Major ethernet 1/1: Link/Interface Down	Configuration Guide for Cisco MXE-OS •Verifying the Hardware, Operating System, and Media-Processing Interfaces Troubleshooting Guide for Cisco MXE-OS •System Alarms and Recovery Procedures
3.	(Optional) View the default Cisco MXE-OS configuration. mxe# show running-config Generating configuration........ hostname mxe user admin role network-admin password 5 $1$DYzvO3zi$ZR1mkrsQHs325h4YPLuAG0 media service media-processing codec-profile 1 codec-type h264 payload-number 112 codec-profile 2 codec-type aac payload-number 96 ...	Configuration Guide for Cisco MXE-OS •Working with Configuration Files
4.	Configure the IP addresses and default routes for the Ethernet 1/1 and MGT1 interfaces and enable the interfaces. Example: mxe# configure terminal Enter configuration commands, one per line. End with CNTL/Z. mxe(config)# interface eth 1/1 mxe(config-if)# ip addr 10.100.101.250 255.255.255.0 mxe(config-if)# no shutdown mxe(config-if)# ip route 0.0.0.0 0.0.0.0 10.100.101.1 *** 2000-03-04 12:53:03 Eqpt Cleared ethernet 1/1: Link/Interface Down *** mxe(config-if)# exit mxe(config)# interface MGT1 mxe(config-if)# ip addr 10.194.59.250 255.255.255.0 mxe(config-if)# no shutdown *** 2000-03-04 12:53:52 Eqpt Cleared MGT1 : Link/Interface Down *** mxe(config-if)# ip route 0.0.0.0 0.0.0.0 10.194.59.40 mxe(config-if)# end mxe#	Configuration Guide for Cisco MXE-OS •Configuring Basic Interface Parameters
5.	Verify network connectivity to the default gateway. Example: mxe# ping 10.194.59.40 Sending 5 ICMP Echos Packets of size 56-bytes to 10.194.59.40 with timeout 1 Sec.... PING 10.194.59.40 (10.194.59.40) 56(84) bytes of data. 64 bytes from 10.194.59.40: icmp_seq=1 ttl=255 time=4.89 ms 64 bytes from 10.194.59.40: icmp_seq=2 ttl=255 time=0.319 ms ...	Configuration Guide for Cisco MXE-OS •Configuring Basic Interface Parameters
6.	Verify and copy the running configuration to the startup configuration. Example: mxe# show running-config Generating configuration........ hostname mxe ... interface Ethernet 1/1 ip address 10.100.101.243 255.255.255.0 no shutdown no description interface MGT1 ip address 10.194.59.243 255.255.255.0 no shutdown no description ... mxe# copy running-config startup-config	Configuration Guide for Cisco MXE-OS •Working with Configuration Files
7.	Update the Cisco MXE-OS software to the latest release on Cisco.com. Note The Cisco MXE-OS device ships with software that is preinstalled. We strongly recommend that you install the latest Release 1.0 software update. You must obtain the software and copy it to a remote server that the Cisco MXE-OS device can access. The software update can take up to 90 minutes. Example: mxe# ping 10.194.59.143 mxe# upgrade software sftp You are using the software upgrade feature. ... IMPORTANT: All Active sessions will be dropped during the upgrade process Please CTRL+C to abort the upgrade SFTP Server: 10.194.59.143 The upgrade requires a file with the updates to be installed. Please specify the filename including the full path relative from the server root. Upgrade File: /tftpboot/mxe1.0.0-69/mxe-1.0.0-69.tar.gz You have selected a protocol that may require authentication. Please input the requested credentials. User Name: user_ID Password: Trying to download /tftpboot/mxe1.0.0-69/mxe-1.0.0-69.tar.gz Successfully downloaded. Uncompressing ... Starting the software update. Updating software on Network Processing Module 1.11.0.1. ... Starting GoAhead Infrastructure: nohup: appending output to `nohup.out' Success Node1 login: *** 2000-03-04 14:09:21 Eqpt Cleared Chassis Media Resources: No resources *** Node1 login:	Software Upgrade Guide for Cisco MXE-OS

Task 4: Configure Basic System Management Features for the Cisco MXE 5600

This task section explains how to change the default password, install software licenses, and configure a syslog and NTP server for the Cisco MXE 5600.

Step	Task	Reference
1.	Change the Cisco MXE-OS default password. Example: mxe# configure terminal mxe(config)# user admin mxe(config-usr)# password 7uj88343kl	Configuration Guide for Cisco MXE-OS •Configuring User Accounts and RBAC
2.	(Optional) Install the permanent license and verify its status. Note Cisco MXE-OS ships with a 60 day, 10-port evaluation license. If you have obtained the permanent license, you must copy it to and install it from a TFTP server that the Cisco MXE-OS device can access. If you do not install the permanent license, the License Type displays as Evaluation. Example: mxe# configure terminal mxe(config)# license install tftp://10.10.1.1/license.lic mxe(config)# do show license detail Index: 1 Feature: mxe-interop Version: 1.0 License Type: Permanent License State: Active, Not in Use License Count: Non-Counted License Priority: Medium Store Index: 0 Store Name: Primary License Storage ... Index: 3 Feature: mxe-port Version: 1.0 License Type: Permanent License State: Active, Not in Use License Count: 30 / 0 License Priority: Medium Store Index: 1 Store Name: Primary License Storage	Configuration Guide for Cisco MXE-OS •Installing and Managing Licenses
3.	Configure an external syslog server and verify its status. Example: mxe# configure terminal mxe(config)# logging server 10.194.59.143 5 mxe(config)# do show logging server Logging server: enabled IP - 10.194.59.143, Severity - NOTICE	Configuration Guide for Cisco MXE-OS •System Management Overview •Configuring System Message Logging
4.	Verify and save the Cisco MXE-OS configuration. mxe# show running-config ... mxe# copy running-config startup-config	Configuration Guide for Cisco MXE-OS •Working with Configuration Files
5.	Manually set the device clock or configure an NTP server. Note If you configure an NTP server, you must reboot the system. Rebooting the system can take up to 15 minutes. Example: mxe# config t mxe(config) clock set 01:42:29 29 Apr 2010 mxe(config) copy running-config start-up config Example: mxe# config t mxe(config)# ntp sync ipaddr 10.68.10.80 29 Apr 01:41:50 ntpdate[30470]: step time server 10.68.10.80 offset 320321630.715814 sec mxe(config)# ntp enable mxe(config)# ntp server 10.68.10.80 mxe(config)# do show clock Thu Apr 29 01:42:29 UTC 2010 mxe(config)# end mxe# reload *** Warning: All active calls will be disconnected *** This command will reboot the system? (Yes/[N]o) : y Copy running configuration to startup configuration? ([Y]es/No) : y	Configuration Guide for Cisco MXE-OS •Configuring NTP •Basic Device Management
6.	Log in and verify that there are no alarms. Note Do not proceed to Task 5: Configure the Cisco MXE 5600 for Video Interoperability until all alarms have been cleared. Example: Node1 login: *** 2010-04-29 01:50:06 Eqpt Cleared Chassis Media Resources: No resources *** Node1 login: admin Password: mxe# show facility-alarm status There are no alarms in the system.	Configuration Guide for Cisco MXE-OS •Verifying the Hardware, Operating System, and Media-Processing Interfaces Troubleshooting Guide for Cisco MXE-OS •System Alarms and Recovery Procedures
7.	(Optional) Connect to Cisco MXE-OS through SSH over the MGMT 1 interface or proceed to the next task to continue configuration through the console connection.	Configuration Guide for Cisco MXE-OS •Configuring SSH and Telnet

Task 5: Configure the Cisco MXE 5600 for Video Interoperability

This task section explains how to configure the Cisco MXE 5600 for video interoperability.

Step	Task	Reference
1.	(Optional) Modify default application, media, codec, or stream profiles for your deployment, as needed. Note Application, media, codec, and stream profiles define the capabilities that Cisco MXE-OS uses to negotiate sessions with media-enabled devices (videoconferencing endpoints). Cisco MXE-OS ships with default profiles that support video interoperability between Cisco TelePresence Systems and supported third-party videoconferencing endpoints. These profiles do not normally require additional configuration. Example: mxe# show media-processing ? application-profile Show application-profile information codec-profile Show codec-profile information media-profile Show media-profile information stream-profile Show stream-profile information mxe# show media-processing application-profile id mxe-interop ApplicationProfile Id = mxe-interop, CTSMediaProfId = 1, VCMediaProfId = 2, Action = Query,	Deployment Guide for Cisco MXE Video Interoperability Solution •Configuring Cisco MXE-OS for the Cisco MXE Video Interoperability Solution
2.	Configure the calling party information and destination patterns for the media-service dial peer for Cisco TelePresence System calls and the media-service dial peer for videoconferencing endpoint calls. Note Cisco MXE-OS ships with default configuration for two media-service dial peers: ID 1 for Cisco TelePresence System incoming and outgoing calls and ID 2 for videoconferencing endpoint incoming and outgoing calls. The media-service dial peers require only calling party ID or name and destination pattern configuration. Tip Command line parameters are limited to 80 characters. Break up the patterns into separate groups (IDs), as needed. Example: mxe# show dial-peer media-service id 1 DialPeerProfile Id = 1, CallingPartyID = , CallingPartyName = , DestinationPattern = , ApplicationProfile = mxe-interop, MediaProfileId = 1, QosDscpValue = 0, Protocol = SIPV2, Preference = 10, Description = CTS calling and called dial-peer, mxe# configure terminal mxe(config)# dial-peer media-service 1 mxe(config-dial-peer)# calling-party-info id ^(98800012|40855559) mxe(config-dial-peer)# destination-pattern ^(98800012|40855559) mxe(config-dial-peer)# exit mxe(config)# dial-peer media-service 2 mxe(config-dial-peer)# calling-party-info id ^(98800011|40855558) mxe(config-dial-peer)# destination-pattern ^(98800011|40855558)	Deployment Guide for Cisco MXE Video Interoperability Solution •Configuring Cisco MXE-OS for the Cisco MXE Video Interoperability Solution
3.	Copy the running configuration to the startup configuration. Example: mxe# copy running-config startup-config	Configuration Guide for Cisco MXE-OS •Working with Configuration Files

Task 6: Configure External Solution Components for Video Interoperability

This task section explains how to configure solution components to route video interoperability calls to and from the Cisco MXE 5600 and supported endpoints.

Step	Step	Reference
1.	Configure the Cisco IOS gatekeeper to route video interoperability calls between Cisco Unified Communications Manager and videoconferencing endpoints.	Deployment Guide for Cisco MXE Video Interoperability Solution •Configuring the Gatekeeper for the Cisco MXE Video Interoperability Solution
2.	Configure Cisco Unified Communications Manager to include the Cisco MXE 5600 in the path for all calls between Cisco TelePresence Systems (CTS)/Cisco TelePresence Multipoint Switch (CTMS) and videoconferencing endpoints and to route calls to CTS/CTMS through SIP lines and trunks.	Deployment Guide for Cisco MXE Video Interoperability Solution •Configuring Cisco Unified Communications Manager for the Cisco MXE Video Interoperability Solution

Task 7: Verify Configuration

This task section explains how to verify that you can make video interoperability calls.

Step	Step	Reference
1.	Verify that the Cisco MXE 5600 is ready for video interoperability calls by ensuring that there are no major or critical alarms. Example: mxe# show facility-alarm status There are no alarms in the system.	Troubleshooting Guide for Cisco MXE-OS •System Alarms and Recovery Procedures
2.	Ensure that the videoconferencing endpoints and Cisco Unified Communication Manager are set to the desired audio and video resolution.	—
3.	Verify multipoint video interoperability. Dial the static conference number that you configured for your deployment from a CTS and from a supported videoconferencing endpoint.	—
4.	Verify point-to-point video interoperability. Dial the phone number of a CTS from a supported videoconferencing endpoint and vice versa.	—
5.	(Optional) View call details. Example: mxe# show call-summary CallID CallingParty CalledParty State StartTime ---------------------------------------------------------------- 11 4085555861 4085555974 ESTABLISHED Thu Apr 29 01:59:28 2010 14 4085555823 4085555953 ESTABLISHED Thu Apr 29 02:09:29 2010	Troubleshooting Guide for Cisco MXE-OS •Troubleshooting Media Processing

Task 8: Troubleshoot Configuration

This task section explains how to perform basic troubleshooting for your deployment.

Step	Step	Reference
1.	Troubleshoot any errors shown on the Cisco MXE 5600 LEDs.	Hardware Installation and Reference Guide for Cisco Media Experience Engine 5000 Series •Hardware Troubleshooting •Chassis LEDs
2.	Troubleshoot any errors shown on the system alarms.	Troubleshooting Guide for Cisco MXE-OS •System Messages •System Alarms and Recovery Procedures
3.	Troubleshoot video interoperability calls: 1. Verify the network connectivity by pinging the Cisco IOS gatekeeper and Cisco Unified Communications Manager. 2. Verify the videoconferencing endpoints' registration with the Cisco IOS gatekeeper. 3. Verify the Cisco Unified Communications Manager configuration. 4. Verify that the Cisco MXE-OS MGT1 and Ethernet 1/1 interfaces are assigned valid IP addresses/netmask; the default gateway is configured; and the Ethernet 1/1 interface is enabled by entering the by entering the show running-config command. 5. Verify the Cisco MXE-OS media-service dial peer configuration by entering the show running-config command. 6. Check the Cisco MXE-OS and Cisco Unified Communications Manager syslogs for SIP error messages.	Troubleshooting Guide for Cisco MXE-OS •Troubleshooting Overview •Troubleshooting Media Processing