About the Cisco TelePresence MCU 5300 Series3
Package contents3
Port and LEDlocation3
Front panel LEDbehavior3
Rear panel LEDbehavior4
Connecting the MCU 53x05
Before you start5
Task 1: Connect power5
Task 2: Connect to Ethernet Port A5
Configuring the MCU 53x06
Task 3: Connect to the console port6
Task 4: Configure Ethernet Port A settings6
Task 5: (Optional) Assign an IP address to the MCU 53x06
Task 6: Discover the IP address of the MCU 53x07
Task 7: Log in to the MCU 53x07
(Optional) Clustering MCU 53x0s8
Before you start8
Task 1: Connect the devices using the stacking cable8
Task 2: Configure the master device8
Task 3: Configure the slave device8
Task 4: (Optional) Register the master with Cisco VCS Control9
Task 5: (Optional) Configure Cisco TMSto recognize the cluster9
Remove a slave from Cisco TMS9
Add the master to Cisco TMS9
Checking for updates11
Troubleshooting and technical support information12
Using the event log to help solve a problem12
Getting more help12
Technical specifications13
Power requirements13
Over-current protection13
Operating environment13
Anti-static precautions13
Cisco TelePresence MCU5300 Series Installation GuidePage 2 of 14
LinkNet A Net B
General information
General information
About the Cisco TelePresence MCU 5300 Series
The Cisco TelePresence MCU 5300 Series is a range of technologically advanced and powerful Multipoint
Control Units (MCU). They are designed to combine continuous presence at high definition and the highest
possible voice quality.
Package contents
The following items are included with the MCU 53x0. Verify that you have these items, in addition to the
MCU 53x0 itself, before installing the device:
n Console cable (blue)
n Power cable
n Rack mounting kit
If you intend to cluster MCU 53x0s, a Cisco TelePresence MCU 5300 Series Stacking Cable must be
ordered separately. Please contact your reseller or go to www.cisco.com.
Port and LEDlocation
The following diagrams show the positions of ports and LEDs on the MCU 53x0.
Figure 1: MCU 53x0 front panel
Figure 2: MCU 53x0 rear panel
Front panel LEDbehavior
The following table describes the behavior of the front panel LEDs.
Table 1: MCU 53x0 front panel LEDbehavior
LEDColorIndicates
StatusGreenThe MCU 53x0 is operating normally
Cisco TelePresence MCU5300 Series Installation GuidePage 3 of 14
General information
LEDColorIndicates
AlarmRedThe MCU 53x0 is booting or has developed a fault, for example:
n temperature is outside normal limits
n fan failure
n battery failure of the internal clock
Refer to the web interface for more information about the problem (go to Status > Health)
PowerBlueThe MCU 53x0 is receiving power
LinkGreenIlluminated when the link between stacked MCU 53x0s is active
Net AGreenIlluminated when there is activity on network Port A
Net BGreenIlluminated when there is activity on network Port B
Rear panel LEDbehavior
The following table describes the behavior of the rear panel LEDs.
Table 2: MCU 53x0 rear panel LEDbehavior
LEDColorIndicates
LinkGreenIlluminated when the link between stacked MCU 53x0s is active
Net AGreen/OrangeLeft LED illuminated green when the interface has established a link
Right LED illuminated orange when there is activity on the interface
Net BGreen/OrangeLeft LED illuminated green when the interface has established a link
Right LED illuminated orange when there is activity on the interface
Cisco TelePresence MCU5300 Series Installation GuidePage 4 of 14
i
Connecting the MCU 53x0
Connecting the MCU 53x0
Before you start
IMPORTANT: Before installing the MCU 53x0, you must read the safety information at
http://www.cisco.com/go/telepresence/safety.
Task 1: Connect power
Connect the power connector on the rear of the unit to the power supply using the supplied power cable.
(There is no On/Off switch.)
Task 2: Connect to Ethernet Port A
Connect an Ethernet cable from Ethernet Port A to an Ethernet switch.
Failing to configure both sides of the Ethernet connection in the same way can result in packet loss,
leading to poor audio and video quality.
Only connect to Ethernet Port B if you need to connect the MCU to a second subnet.
Cisco TelePresence MCU5300 Series Installation GuidePage 5 of 14
i
i
Configuring the MCU 53x0
Configuring the MCU 53x0
Task 3: Connect to the console port
1. Ensure power is connected to the MCU 53x0 and the Status LED is green.
2. Connect the console port of the unit to the serial port of your PC using the RJ45 to DB9 cable supplied.
3. Use a serial terminal program, such as Secure CRT or HyperTerminal, to connect to the unit. Set your
terminal software to the following settings:
l Baud rate: 38400
l Data bits: 8
l Parity: none
l Stop bits: 1
l Flow control: none
4. Press Enter and the following command prompt appears on the terminal:
MCU:>
Task 4: Configure Ethernet Port A settings
The default setting for the MCU 53x0 Ethernet ports is auto-sensing mode. If the switch port to which you
connect the MCU 53x0 is not also set to auto-sensing mode, then you need to configure the device's
Ethernet ports to use the same speed and duplex mode.
Only connect to Ethernet Port B if you need to connect the MCU 53x0 to a second subnet.
Both ends of the Ethernet connection must be configured in the same way. For example, either
configure both ends of the link to be auto-sensing or configure both ends to operate at the same speed
and duplex.
Note:To establish a 1000Mbps connection, both ends of the link must be configured as auto-sensing.
n To configure Ethernet Port A, enter the following for auto-sensing mode:
ethertype A auto
or to configure a speed and duplex, use the following command:
ethertype A <10 | 100> <half | full>
For example, to configure a full-duplex 100 Mbps link, enter:
ethertype A 100 full
n To display the current configuration and status of the Ethernet ports, enter:
status
Task 5: (Optional) Assign an IP address to the MCU 53x0
The default setting for the MCU 53x0 is to use DHCP to obtain an IP address. You can assign a static IP
address if you prefer, or if a DHCP server is not available. If you want the IP address of the MCU 53x0 to be
assigned by your DHCP server, omit this step.
n To assign a static IPv4 address to Port A, use the following command:
static A <IP address> <netmask> [<default gateway address>]
Cisco TelePresence MCU5300 Series Installation GuidePage 6 of 14
i
Configuring the MCU 53x0
For example, to assign an address of 192.168.1.2 where the default gateway is at 192.168.1.1, enter:
static A 192.168.1.2 255.255.255.0 192.168.1.1
n To manually specify a DNS server, use this command:
dns <DNS server address> [<secondary DNS server>][<domain>]
n To revert to using DHCP after setting a static IPv4 address, use the following command:
dhcp -4 A
For information on assigning a static IPv6 address type help static. For information on assigning an
automatic IPv6 address type help dhcp or else see the online help.
Task 6: Discover the IP address of the MCU 53x0
1. To display the current status of the IP address, enter: status
If you have DHCP enabled on your network and you are allowing the MCU 53x0 to acquire its address
using DHCP, the IP address that has been acquired by Ethernet Port A will be shown; if you have
assigned a static IP address, that is the address that will be shown.
2. Make a note of the IP address. You will use this to access the web interface of the unit.
Note:When your MCU 53x0 has an IPaddress, you can add an entry for it on your DNSserver and use a
hostname to access the device's web interface.
Task 7: Log in to the MCU 53x0
To log in to the web interface of the device:
1. Use your browser to navigate to the IP address or hostname of the unit.
2. Enter the user name admin with no password, and click Log in.
The Home page is displayed.
Note: We recommend that you change the admin account to use a password as soon as possible. To do
that, go to Home and click Change password.
Cisco TelePresence MCU5300 Series Installation GuidePage 7 of 14
(Optional) Clustering MCU 53x0s
(Optional) Clustering MCU 53x0s
Before you start
Up to two MCU 53x0s can be clustered to increase capacity. One of the MCU 53x0s acts as the master unit
and the second as a slave, and the cluster will provide the sum of the conferencing capacity of the individual
units.
For example, if you cluster two MCU 5320s, which each support up to ten 1080p participants, your cluster
will support up to twenty 1080p participants.
You may combine an MCU5310 with an MCU5320 in the cluster, provided that they are running identical
software versions. In this case, the MCU5320 must be configured as the master.
You will also need a Cisco TelePresence MCU 5300 Series Stacking Cable which must be ordered
separately. Please contact your reseller or go to www.cisco.com.
Task 1: Connect the devices using the stacking cable
1. If your stacking cable has protective tapes or caps on the ends, remove them so that the metal conductors
are visible within the plug.
2. Plug the ends of the stacking cable into the Link sockets on the rear of the MCU 53x0s. Check the
orientation of the plug when inserting it into the Link socket.
3. To remove the cable, pull the release mechanism to detach the plug. Do not pull directly on the plug.
Task 2: Configure the master device
One of the MCU 53x0s must be configured as the master device and the other as a slave.
1. Log in to the web interface of the device you have selected as the master.
In a mixed cluster, you must use the MCU5320 as the master.
2. Go to Settings > Media ports.
3. Select Master from the Cluster mode drop down menu.
4. Click Apply changes.
5. Click OK to restart the device and apply the changes.
6. Go to Status > Cluster to confirm that the device has been correctly configured as the master.
Task 3: Configure the slave device
1. Log in to the web interface of the other device.
2. Go to Settings > Media ports.
3. Select Slave from the Cluster mode drop down menu.
4. Click Apply changes.
5. Click OK to restart the device and apply the changes.
6. Go to Status > Cluster to confirm that the device has been correctly configured as the slave.
Cisco TelePresence MCU5300 Series Installation GuidePage 8 of 14
(Optional) Clustering MCU 53x0s
When you have configured the units as master and slave, do not use the web interface of the slave unit for
normal operations. The slave web interface is only used for upgrading software and for network configuration.
Task 4: (Optional) Register the master with Cisco VCS
Control
You can use a cluster of MCUs with a Cisco TelePresence Video Communication Server (Cisco VCS
Control), just as you would use a single MCU. To do this you must register the master MCU with the Cisco
VCS Control.
The Cisco VCS will not indicate that the MCU is part of a cluster; the device type will continue to show as
MCU.
To display the status of registered devices on the Cisco VCS Control, go to Status > Registrations > By
device.
Task 5: (Optional) Configure Cisco TMSto recognize the
cluster
You can manage a cluster of MCUs through the Cisco TelePresence Management Suite (Cisco TMS) as you
would manage a single MCU. To do this, only the master needs to be added to Cisco TMS.
Note:There are some issues with managing slave MCUs in Cisco TMS. To prevent these issues:
n Do not add new slave MCUs to Cisco TMS.
n Completely remove from Cisco TMS any MCU that you wish to configure as a slave. You will need to
reconfigure any conferences that were scheduled to run on that device to run on the master instead.
Remove a slave from Cisco TMS
For any MCU that is or will be configured as a slave:
1. Log in to Cisco TMS.
2. Go to Systems > Purge Systems.
3. Select the devices you want to delete.
4. Click Purge Systems.
Add the master to Cisco TMS
There is no specific configuration needed to add a new master MCU to Cisco TMS; you can add it as you
would do for a single MCU.
However, if you reconfigure an MCU that Cisco TMS already manages, to become the master in a cluster,
then Cisco TMS will not recognize the increased conferencing capacity until you force a refresh on Cisco
TMS.
1. Log in to Cisco TMS.
2. Go to Systems > Navigator.
3. Click on your MCU in the left hand pane.
4. Go to Settings.
Cisco TelePresence MCU5300 Series Installation GuidePage 9 of 14
(Optional) Clustering MCU 53x0s
5. Click Force Refresh.
Cisco TMS refreshes its details of the device and the Max Number of Video Calls will increase to show
the increased port count.
Note: Refreshing an MCU that has been configured as a slave will not cause Cisco TMS to decrease its
record of that device's port count. You must remove the slave from Cisco TMS and refresh the master.
Cisco TelePresence MCU5300 Series Installation GuidePage 10 of 14
Checking for updates
Checking for updates
It is a good idea to regularly check for updates to the device's main software image on the Cisco web site.
This section describes how to upgrade the device using the web interface.
To check for, and download, updates:
1. Log in to the web interface and go to Status > General.
2. Make a note of the software version that is currently installed.
3. Go to the support section of the web site and check if a more recent release is available.
4. If a more recent release is available, download it and save it locally.
To upgrade the software application:
1. Unzip the software release file that you downloaded.
2. In the web interface, go to Settings > Upgrade.
3. In the Main software image section, browse to and locate the unzipped file.
4. Click Upload software image.
The browser begins uploading the file to the device, and a new browser window opens to indicate the
progress of the upload. When finished, the browser window refreshes and indicates that the software
upgrade is complete.
5. Go to Settings > Shutdown to shut down and restart the device.
Note:Shutting down the device will disconnect all participants.
Cisco TelePresence MCU5300 Series Installation GuidePage 11 of 14
Troubleshooting and technical support information
Troubleshooting and technical support
information
Using the event log to help solve a problem
You can use the event log to produce debugging information to assist technical support in solving any
problems. Event logging capture filter topics are set by default to Errors, warnings and information. Do
not change the capture filter topic level without the guidance of technical support.
Getting more help
If you experience any problems when configuring or using the MCU 53x0, consult the online help available
from the user interface.
If you cannot find the answer you need in the documentation, check the web site at
http://www.cisco.com/cisco/web/support/index.html where you will be able to:
n Make sure that you are running the most up-to-date software.
n Get help from the Cisco Technical Support team.
Make sure you have the following information ready before raising a case:
n Identifying information for your product, such as model number, firmware version, and software version
(where applicable).
n Your contact email address or telephone number.
n A full description of the problem.
To view a list of Cisco TelePresence products that are no longer being sold and might not be supported, visit
http://www.cisco.com/en/US/products/prod_end_of_life.html and scroll down to the TelePresence section.
Cisco TelePresence MCU5300 Series Installation GuidePage 12 of 14
Technical specifications
Technical specifications
Power requirements
Table 3: MCU 53x0 ratings
RatingValue
Current rating6AMaximum
Supply voltage range100 to 240V 50/60 Hz
Over-current protection
Ensure the supply to this unit is protected by a branch circuit protector rated by a maximum of 20A.
CAUTION: Over-current devices must meet applicable national and local electrical safety codes and be
approved for the intended application.
Operating environment
The device must only be used within the following environmental conditions:
Table 4: Operating environment
EnvironmentTemperatureHumidity
Operating environment0°C to 35°C10% to 95%
(non-condensing)
Non-operating environment-10°C to 60°C10% to 95%
(non-condensing)
Optimum operating environment21°C to 23°C45% to 50%
(non-condensing)
Anti-static precautions
When servicing or removing components or connections, first attach an anti-static wrist strap to an
appropriate earth point.
Cisco TelePresence MCU5300 Series Installation GuidePage 13 of 14
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.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE
OF THESE SUPPLIERS ARE PROVIDED "AS IS" WITH ALL FAULTS. CISCO AND THE ABOVENAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING,
WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE
PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL,
CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST
PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS
MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other
countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party
trademarks mentioned are the property of their respective owners. The use of the word partner does not imply
a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual
addresses and phone numbers. Any examples, command display output, network topology diagrams, and
other figures included in the document are shown for illustrative purposes only. Any use of actual IP
addresses or phone numbers in illustrative content is unintentional and coincidental.