Cisco Cisco TelePresence MCU 4510 Maintenance Manual
Advanced topics
Cisco TelePresence MCU 4.3 Product administration guide
Page 222 of 242
1. Ensure that FTP is enabled on the
Network > Services
page.
2. Connect to the MCU using an FTP client. When asked for a user name and password, enter the same
ones that you use to log in to the MCU's web interface as an administrator.
You will see a file called configuration.xml. This contains the complete configuration of your MCU.
You will see a file called configuration.xml. This contains the complete configuration of your MCU.
3. Copy this file and store it somewhere safe.
The backup process is now complete.
To restore the configuration using FTP:
1. Locate the copy of the configuration.xml file that you want to restore.
2. Ensure that FTP is enabled on the
Network > Services
page.
3. Connect to the MCU using an FTP client. When asked for a user name and password, use the same ones
that use to log in to the MCU's web interface as an administrator.
4. Upload your configuration.xml file to the MCU, overwriting the existing file on the MCUs.
The restore process is now complete.
Note: that the same process can be used to transfer a configuration from one MCU to another of the same
model number. However, before doing this, be sure to keep a copy of the original feature keys from the MCU
whose configuration is being replaced.
model number. However, before doing this, be sure to keep a copy of the original feature keys from the MCU
whose configuration is being replaced.
If you are using the configuration file to configure a duplicate MCU, for example in a network where you have
more than one, be aware that if the original MCU was configured with a static address, you will need to
reconfigure the IP address on any other MCUs on which you have used the configuration file.
more than one, be aware that if the original MCU was configured with a static address, you will need to
reconfigure the IP address on any other MCUs on which you have used the configuration file.
Network connectivity testing
The Network connectivity page can be used for troubleshooting issues that arise because of problems in the
network between the MCU and a remote video conferencing device being called (or a device from which a
user is attempting to call the MCU).
network between the MCU and a remote video conferencing device being called (or a device from which a
user is attempting to call the MCU).
The Network connectivity page enables you to attempt to 'ping' another device from the MCU's web interface
and perform a 'traceroute' of the network path to that device. The results show whether or not you have
network connectivity between the MCU and another device. You can see from which port the MCU will route
to that address. For a hostname, the IP address to which it has been resolved will be displayed.
and perform a 'traceroute' of the network path to that device. The results show whether or not you have
network connectivity between the MCU and another device. You can see from which port the MCU will route
to that address. For a hostname, the IP address to which it has been resolved will be displayed.
To test connectivity with a remote device, go to
Network > Connectivity
. In the text box, enter the IP
address or hostname of the device to which you want to test connectivity and click Test connectivity. Note
that IPv6 addresses must be enclosed in square brackets.
that IPv6 addresses must be enclosed in square brackets.
For each successful 'ping', the time taken for the ICMP echo packet to reach the host and for the reply
packet to return to the MCU is displayed in milliseconds (the round trip time). The TTL (Time To Live) value
on the echo reply is also displayed.
packet to return to the MCU is displayed in milliseconds (the round trip time). The TTL (Time To Live) value
on the echo reply is also displayed.
For each intermediate host (typically routers) on the route between the MCU and the remote device, the
host's IP address and the time taken to receive a response from that host is shown. Not all devices will
respond to the messages sent by the MCU to analyse the route; routing entries for non-responding devices is
shown as <unknown>. Some devices are known to send invalid ICMP response packets (e.g. with invalid
host's IP address and the time taken to receive a response from that host is shown. Not all devices will
respond to the messages sent by the MCU to analyse the route; routing entries for non-responding devices is
shown as <unknown>. Some devices are known to send invalid ICMP response packets (e.g. with invalid