Polycom RealPresence Video DualManager 400 System

Transcription

1 Ep RELEASE NOTES August B8 Polycom RealPresence Video DualManager 400 System

2 Polycom RealPresence Video DualManager 400 System Release Notes About the RealPresence Video DualManager 400 System Polycom is pleased to announce this first release of the Polycom RealPresence Video DualManager 400 system. These release notes describe the important information about this release. The RealPresence Video DualManager system is an enterprise management solution for small- to midsized video collaboration networks that require call server functionality. It is also the primary replacement product for the Polycom CMA 4000 system. The RealPresence Video DualManager system includes virtual instances of two of the major Polycom RealPresence Platform management systems on a single system. The two components it includes are: An instance of the Polycom RealPresence Resource Manager system The RealPresence Resource Manager system provides administrators centralized management application tools to implement, integrate, monitor, manage and report on the video network. This centralized solution puts the administrator in control of the network in real time, allowing them to understand exactly the current health and status of all video conferencing services. Administrators can use the RealPresence Resource Manager system to centrally provision, monitor and manage the video network. Through dynamic provisioning, the system automatically configures and maintains video clients at pre-determined software baselines while built-in reports, application dashboards, and drill-down tabs ensure administrators can access troubleshooting and operational metrics. An instance of the Polycom RealPresence DMA system The RealPresence DMA system has built in H.323 gatekeeper and SIP Proxy/Registrar functionality that provides administrators the flexibility of integrating the video conferencing network into leading Unified Communications platforms, making video conferencing easy for end users without complex and costly re-configurations. The RealPresence DMA system also simplifies and unifies dialing so that making a video call can be as easy as making a telephone call. Also note that the intended deployment of the RealPresence Video DualManager system is internal to the enterprise network with the appropriate firewalls to the DMZ and Internet. Component System Configurations Again, the RealPresence Video DualManager system includes virtual instances of the RealPresence Resource Manager and DMA systems. After the initial set up of these two component systems, you should carefully read the component system documentation, assess your video conferencing needs, and implement system configurations on the two component systems that meet those needs. As you do so: Assess the ramifications of the configuration setting changes to ensure you understand the outcome of the changes. Assess the logic and compatibility of the configuration setting changes across the two component systems to ensure they will interact in an expected and predictable manner.

3 Ensure that you understand the System Differences and/or Limitations when operating the component systems in a RealPresence Video DualManager system environment as compared to how they operated independently. The two component systems RealPresence Resource Manager and DMA systems while designed to work in tandem have configuration settings that may conflict. System Differences and/or Limitations While the RealPresence Video DualManager system has most of the functionality of its component RealPresence Resource Manager and DMA systems, it does have the following differences and limitations: IMPORTANT While the RealPresence Resource Manager and DMA systems do not support the following features, their user interfaces may not prevent you from enabling or configuring these features. Be very careful to review this document and the component Operations Guides. No Redundancy or Superclustering RealPresence Resource Manager system redundancy and DMA system redundancy and superclustering are not supported as part of a RealPresence Video DualManager system. IMPORTANT While the RealPresence Video DualManager network design does not support redundancy or clustering, the RealPresence Resource Manager and DMA systems user interfaces do not prevent it. System Access Although the RealPresence Video DualManager system will display a console and login prompt, direct console access to any part of the system is prohibited by the system. There are no login credentials for direct console access. Remote console access to the component RealPresence Resource Manager and DMA systems via SSH as configured separately in each product is fully supported. Also, while the RealPresence Video DualManager system server has four physical NICs, only the first physical NIC (eth0) is active and provides limited access to the system. For that reason, the DMA system component does not support split networking or multi-nic (multiple network interface card) configurations. IMPORTANT While the RealPresence Video DualManager system network design does not support split networking or multi-nic configuration, the DMA system s user interface does not prevent it. As a note, the USB configuration utility for the DMA system is also not supported. The only method for configuring the network settings for the component systems is by using a browser to access the systems user interface at their default IP address. Their default IP addresses are: RealPresence Resource Manager = DMA systems = Polycom, Inc. 3

4 SNMP Monitoring At this time SNMP monitoring is not supported for the RealPresence Video DualManager system. While SNMP monitoring can be enabled on the virtualized instances of the RealPresence Resource Manager and DMA systems (by default it is disabled), the results are not standard nor predictable. Dial Rules and Simplified Dialing The Polycom DMA system does not support Least Cost Routing, which was required on CMA systems to implement Simplified Dialing. This is important if you are migrating CMA 4000 systems. On DMA systems the rules for simplified dialing may be different, and so the functionality may be correspondingly different. No Multi-tenancy As part of the RealPresence Video DualManager system, the component RealPresence Resource Manager system cannot be licensed to support multi-tenancy, although the option may be available in the user interface. No Support for Maximum Security Mode As part of the RealPresence Video DualManager system, the component RealPresence Resource Manager and DMA systems do not support the official Maximum Security Mode setting. No IPv6 Support As part of the RealPresence Video DualManager system, the component RealPresence Resource Manager and DMA systems do not support IPv6. While the RealPresence Video DualManager system network design does not support IPv6 networking, the RealPresence Resource Manager and DMA systems user interfaces do not prevent you from implementing it. Where to Get the Latest Product Information To view the latest Polycom product documentation, visit the following support pages at the Polycom Support website, click here. Polycom, Inc. 4

5 System Requirements For best reliability, deploy the RealPresence Video DualManager system into a good-quality IP network with low latency and very little packet loss. When integrating with Microsoft Active Directory, the network between the RealPresence Video DualManager system and Active Directory should have less than 200 ms round-trip latency and less than 4% round-trip packet loss. The network between the RealPresence Video DualManager system and all MCUs should have less than 200 ms round-trip latency and less than 2% round-trip packet loss. Since this network carries only signaling traffic (the RTP stream goes directly from the endpoint to the MCU), bandwidth is not an issue. The network between the RealPresence Video DualManager system and video endpoints should have less than 200 ms round-trip latency and less than 6% round-trip packet loss. Computers used to access the component RealPresence Resource Manager and DMA systems user interfaces should have 1280x1024 minimum display resolution (wide screen, 1680x1050 or greater, recommended). NTP Server Required Please note that the RealPresence Video DualManager requires integration with a Network Time Server (NTP) as the operating system used for deployment does not support a local clock. For best results, browser minimum requirements are Microsoft Internet Explorer 8.0 or Google Chrome 11 (with Adobe Flash plug in, not built-in Flash support). The RealPresence Resource Manager and DMA systems user interfaces requires Adobe Flash Player. For stability and security reasons, we recommend always using the latest version of Flash Player. System Capabilities and Constraints The following capabilities and constraints apply to the RealPresence Video DualManager component systems. The RealPresence Resource Manager system may be licensed to manage up to 400 devices The Polycom DMA system: May be licensed to support up to 150 concurrent SIP and/or H.323 calls Can support up to 400 registered endpoints Can support up to 25 sites Can support up to 5 MCUs For other system capabilities and constraints, see the Release Notes for the component RealPresence Resource Manager and DMA systems. Polycom, Inc. 5

6 Products Tested with this Release Polycom RealPresence Video DualManager systems are tested with a wide range of products. UPGRADE NOTICE Do not upgrade the DMA system instance to version 6.2. The following Resource Manager and DMA system version combinations are supported. You are encouraged to upgrade your Polycom Video DualManager system to the latest supported software combination. Resource Manager DMA 8.0.x x x x x x 8.3.x x where x To see the list of specific products tested with each of the RealPresence Video DualManager component systems, see the Release Notes for the version of the component system installed. To see the current Polycom Supported Products matrix, go to Installation Information Installation of new RealPresence Video DualManager systems is managed through Polycom Global Services. For more information, please contact your Polycom representative. Reserved IP Address Please note that the RealPresence Video DualManager reserves IP address for internal use. Please ensure that IP address is not used within the network in which the RealPresence Video DualManager is deployed. NTP Server Required Please note that the RealPresence Video DualManager requires integration with a Network Time Server (NTP) as the operating system used for deployment does not support a local clock. Polycom, Inc. 6

7 New RealPresence Video DualManager systems ship with the following component systems. The RealPresence Resource Manager system 8.0 The Polycom DMA system Migration Information Polycom customers with qualified models of Polycom CMA 4000 systems (those on Dell R610 servers) can migrate their CMA systems to the new RealPresence Video DualManager. This migration process, which does not require a Polycom Global Services engagement, has been carefully engineered to protect and migrate customer data. The migration process is documented in the Polycom CMA 4000 System to RealPresence Video DualManager System Migration Guide. As part of the migration process, you will be required to: Work with your Polycom representative to order the two required Migration DVD and Migration Hard Drive Kits. Apply the required Migration Patch to your CMA system to prepare it for backup and migration. The Migration Patch will allow the export of the CMA 4000 data in a format compatible with the RealPresence Resource Manager system. Additionally, it exports several CSV-formatted files containing information about the H.323 gatekeeper and dial rule configurations that are useful when configuring the DMA system call manager. The Migration Patches are specific to the version of CMA system being migrated. Specifically: CMA 6.2.x Migration Patch- Apply this patch only on CMA systems with 6.2.x installed CMA Migration Patch- Apply this patch only on CMA systems with installed You may need to bring your CMA systems to the required version level before applying the Migration Patch. Archive your system data so the data can be migrated correctly. Unplug all network cables connected to the NICs before starting the migration. There are multiple network initialization paths that will fail if the system is migrated when active links are detected during the process. If there is such a failure, the only recovery is a full system installation with the NICs disconnected. You must then perform first-time setup procedures on both component systems using a crossover cable attached to the system server. Replace the 73GB hard drive within the system with the new 146GB hard drive included in the Migration Hard Drive Kit. You must use this new146 GB hard drive for the migration process; smaller hard drives are not acceptable. Install and complete first time setup of the component system software. Polycom, Inc. 7

8 Upload the CMA system archive into the RealPresence Resource Manager system. Finish configuration of the component system software. Reserved IP Address Please note that the RealPresence Video DualManager reserves IP address for internal use. Please ensure that IP address is not used within the network in which the RealPresence Video DualManager is deployed. And as a general rule, the CMA 4000 system migration process can be accomplished in less than 90 minutes. Variations in system experience and the amount of data being migrated will affect migration times. Upgrade Information Supported RealPresence Resource Manager and DMA system upgrades are documented in the following sections. Upgrade RealPresence Resource Manager System to To upgrade the RealPresence Resource Manager system instance to 8.4.0: 1 On your PC, open a command prompt. 2 In the command prompt, run the command ping t <IP address> where <IP address> is the IP address of the RealPresence Resource Manager system instance. This command starts a continuous ping of the system instance, which helps verify when it is safe to restart. There is no visual feedback from the server LCD screen or monitor (if attached). 3 Go to the Admin > Maintenance > Server Software Upgrade page. 4 Click the Upload upgrade file to Server button. A file chooser dialog appears. 5 Use the file chooser dialog to select the upgrade package ("rprm xxxxxx.bin ) downloaded previously. 6 Click Open. A File Upload dialog appears. 7 When the system indicates the File Upload is Complete, click OK. 8 Click the Upgrade button and start the timer. 9 During the upgrade process, monitor the system ping responses. Note: Several times during the upgrade process, the system will stop responding to ping requests. Only continue on to the server shutdown and restart step when the system does not respond to pings for more than 3 minutes. 10 When the system does not respond to pings after more than 3 minutes, shut down the server by pressing and holding the server power button. 11 Power on the server and wait for it to respond to pings. Polycom, Inc. 8

9 12 After approximately 1 hour has elapsed, the system should again respond to pings. If no pings are seen, repeat steps 9, 10 and 11 a second and third time. 13 If a ping is still not seen, backup the RPRM system database, and re-image the VDM back to 1.0. See Back up system data on page 17 and Reinstall the system software on page 18. After re-imaging, you must upgrade the RPRM software to RPRM Using a web browser, log in to the Real Presence Resource Manager system instance. Check the Real Presence Resource Manager is upgraded to RPRM GA build. Upgrade a RealPresence DMA System to Note that interim upgrades may be required to reach the desired final release goal. IMPORTANT INFORMATION TO THE SUCCESS OF YOUR UPGRADES Do not upgrade the DMA system instance on a RealPresence Virtual DualManager system to (6.2.1 is fully supported.) The RealPresence Resource Manager and DMA system upgrades MUST be performed SERIALLY (one at a time). If you upgrade both system components, do not attempt to start another upgrade procedure until the first is complete. The upgrade procedures in this section will affect the operation of the component RealPresence Resource Manager and DMA systems. Follow these upgrade instructions exactly to ensure that the RealPresence Video DualManager 400 system will not need to be re-imaged. Upgrade RealPresence Resource Manager System to These upgrade instructions describe how to upgrade a RealPresence Resource Manager system instance on a RealPresence Video DualManager 400 system to The following table identifies the interim upgrade paths required to upgrade to 8.4.0: 8.2.x Two RealPresence Resource Manager system upgrade processes are documented here: Upgrade Resource Manager System Instance to Upgrade Resource Manager System 8.2.x Instance to To upgrade a 8.0.x or 8.1.x RealPresence Resource Manager system to 8.4.0, you must first perform an interim system upgrade to 8.2, then perform the upgrades documented here. Please see the RealPresence Resource Manager System Release Notes for 8.2 for the earlier upgrade procedures. TIMER MECHANISM REQUIRED Some steps of this procedure are time-dependent. Before you begin, gather a stopwatch or a smartphone with a timer application. Polycom, Inc. 9

10 PHYSICAL SYSTEM ACCESS As part of the upgrade procedure, you must have physical access to the RealPresence Video DualManager 400 system server so that you can manually power cycle the server at specific intervals. Polycom recommends performing this procedure near the server, using a laptop connected to the same network the RealPresence Video DualManager 400 system is using. Upgrade Resource Manager System Instance to To upgrade a RealPresence Resource Manager System Instance to 8.4.0: 1 Download the required upgrade packages as documented on page Back up system data as documented on page Upgrade RealPresence Resource Manager system instance to as documented on page 12. Upgrade Resource Manager System 8.2.x Instance to To upgrade a RealPresence Resource Manager System 8.2.x Instance to 8.4.0: 1 Download the required upgrade packagesas documented on page Back up system data as documented on page Upgrade RealPresence Resource Manager system instance to as documented on page Upgrade RealPresence Resource Manager system instance to as documented on page 12 Download the required upgrade packages To download the upgrade packages: 1 On your PC, download the RealPresence Resource Manager system upgrade package from Note: The upgrade package will be available in the Appliance Edition Software Downloads section of the support page. The upgrade package link will be identify by the upgrade path, for example, RealPresence Resource Manager System Upgrade Software for The upgrade package will have a filename like "rprm xxxxxx.bin. 2 Also download the RealPresence Resource Manager system upgrade package (the upgrade package will have a filename like "rprm-8.4.x-xxxxxx.bin ) from the same location. 3 Verify both packages are available on your local system. Back up system data To backup system data: 1 Using a web browser, log in to the RealPresence Resource Manager system instance. Polycom, Inc. 10

11 2 Go to the Admin > Maintenance > Backup/Restore System Settings page. 3 Click Create and Download a Backup Archive. The system creates a backup archive and displays a confirmation dialog when complete. 4 Download and save the newly created backup archive. Upgrade RealPresence Resource Manager system instance to To upgrade the RealPresence Resource Manager system instance to 8.3.0: 1 On your PC, open a command prompt. 2 In the command prompt, run the command ping t <IP address> where <IP address> is the IP address of the RealPresence Resource Manager system instance. This command starts a continuous ping of the system instance, which helps verify when it is safe to restart. There is no visual feedback from the server LCD screen or monitor (if attached). 3 Go to the Admin > Maintenance > Server Software Upgrade page. 4 Click the Upload upgrade file to Server button. A file chooser dialog appears. 5 Use the file chooser dialog to select the upgrade package ("rprm xxxxxx.bin ) downloaded previously. 6 Click Open. A File Upload dialog appears. 7 When the system indicates the File Upload is Complete, click OK. 8 Click the Upgrade button and start the timer. 9 During the upgrade process, monitor the system ping responses. Note: Several times during the upgrade process, the system will stop responding to ping requests. Only continue on to the server shutdown and restart step when the system does not respond to pings for more than 3 minutes. 10 When the system does not respond to pings after more than 3 minutes, shut down the server by pressing and holding the server power button. 11 Power on the server and wait for it to respond to pings. 12 After approximately 1 hour has elapsed, the system should again respond to pings. If no pings are seen, repeat steps 9, 10 and 11 a second and third time. 13 If a ping is still not seen, backup the RPRM system database, and re-image the VDM back to 1.0. See Back up system data on page 17 and Reinstall the system software on page 18. After re-imaging, you must upgrade the RPRM software to RPRM 8.2.x. 14 Using a web browser, log in to the Real Presence Resource Manager system instance. Check the Real Presence Resource Manager is upgraded to RPRM GA build. Polycom, Inc. 11

12 Upgrade RealPresence Resource Manager system instance to To upgrade the RealPresence Resource Manager system instance to 8.4.0: 1 On your PC, open a command prompt. 2 In the command prompt, run the command ping t <IP address> where <IP address> is the IP address of the RealPresence Resource Manager system instance. This command starts a continuous ping of the system instance, which helps verify when it is safe to restart. There is no visual feedback from the server LCD screen or monitor (if attached). 3 Go to the Admin > Maintenance > Server Software Upgrade page. 4 Click the Upload upgrade file to Server button. A file chooser dialog appears. 5 Use the file chooser dialog to select the upgrade package ("rprm xxxxxx.bin ) downloaded previously. 6 Click Open. A File Upload dialog appears. 7 When the system indicates the File Upload is Complete, click OK. 8 Click the Upgrade button and start the timer. 9 During the upgrade process, monitor the system ping responses. Note: Several times during the upgrade process, the system will stop responding to ping requests. Only continue on to the server shutdown and restart step when the system does not respond to pings for more than 3 minutes. 10 When the system does not respond to pings after more than 3 minutes, shut down the server by pressing and holding the server power button. 11 Power on the server and wait for it to respond to pings. 12 After approximately 1 hour has elapsed, the system should again respond to pings. If no pings are seen, repeat steps 9, 10 and 11 a second and third time. 13 If a ping is still not seen, backup the RPRM system database, and re-image the VDM back to 1.0. See Back up system data on page 17 and Reinstall the system software on page 18. After re-imaging, you must upgrade the RPRM software to RPRM Using a web browser, log in to the Real Presence Resource Manager system instance. Check the Real Presence Resource Manager is upgraded to RPRM GA build. Polycom, Inc. 12

13 Upgrade a RealPresence DMA System to Three RealPresence DMA system upgrade processes are documented here: Upgrade RealPresence DMA System x or greater to on page 1415 Upgrade RealPresence DMA System to x and then on page 15 Upgrade RealPresence DMA System to x and then on page 17 These upgrade instructions describe how to upgrade a RealPresence DMA system instance on a RealPresence Video DualManager 400 system to (6.2.0 is NOT a supported upgrade version). The following table identifies the interim upgrade paths required to upgrade the system instance to 6.3.0: Supported Upgrade Paths and Required Files Current Version Intermediate Version Intermediate Version Final Upgrade Use Upgrade Package Ending with x rppufconv.bin (6.1.2.x) full.bin (6.3.0) (reinstallation required) x rppufconv.bin x full.bin TIMER MECHANISM REQUIRED Some steps of these procedures are time-dependent. Before you begin, gather a stopwatch or a smartphone with a timer application. PHYSICAL SYSTEM ACCESS As part of the upgrade procedure, you must have physical access to the RealPresence Video DualManager 400 system server so that you can manually power cycle the server at specific intervals. Polycom recommends performing this procedure near the server, using a laptop connected to the same network the RealPresence Video DualManager 400 system is using. Polycom, Inc. 13

14 Upgrade RealPresence DMA System x or greater to These upgrade instructions describe how to upgrade a RealPresence DMA system x or greater instance on a RealPresence Video DualManager 400 system to (6.2.0 is NOT a supported upgrade version). To upgrade RealPresence DMA System x or greater to 6.3.0: 1 Download the upgrade package as documented on page Back up system data as documented on page Upgrade RealPresence DMA system instance to as documented on page 14. Download the upgrade package To download the upgrade package:» Download the RealPresence DMA system upgrade package from Note: The upgrade package is available in the Appliance Edition Software Downloads section of the support page. The upgrade package link is identified by the upgrade path and has a filename ending in "full.bin. Back up system data To backup system data: 1 Using a web browser, log in to the RealPresence DMA system instance. 2 Go to the Maintenance > Backup and Restore page. 3 Click Create New (Full). The system creates a backup archive and displays a confirmation dialog when complete. 4 Download and save the newly created backup archive. Upgrade RealPresence DMA system instance to To upgrade the system software to 6.3.0: 1 Using a web browser, log in to the RealPresence DMA system instance. 2 On your PC, open a command prompt. 3 In the command prompt, run the command ping t <IP address> where <IP address> is the IP address of the RealPresence DMA system instance. This command starts a continuous ping of the system instance, which helps verify when it is safe to restart. There is no visual feedback from the server LCD screen or monitor (if attached). 4 Go to the Maintenance > Software Upgrade page. Polycom, Inc. 14

15 5 Click the Upload button. A file chooser dialog appears. 6 Use the file chooser dialog to select the upgrade package. 7 Click Open. A progress dialog appears. 8 Click the Upgrade button and start a timer. 9 After 12 minutes have elapsed, ensure that the system instance is no longer resonding to ping requests. Do not proceed until the system has not responded to ping requests for at least 40 seconds. 10 Power off the server using the power button. 11 Once the server is powered off, press the power button again to power it back on. 12 Once the server is powered on, allow at least 25 minutes for the upgrade to complete. 13 Using a web browser, log in to the RealPresence DMA system instance. 14 Go to Help > About DMA 7000 to ensure that the system instance has been upgraded. Upgrade RealPresence DMA System to x and then These upgrade instructions describe how to upgrade a RealPresence DMA system instance on a RealPresence Video DualManager 400 system to x (where x is the most current posted patch release). Perform the following tasks to upgrade the RealPresence DMA system instance from to x: 1 Download the required upgrade package as documented on page 15 2 Back up system data as documented on page Upgrade RealPresence DMA system to x as documented on page Upgrade RealPresence DMA System x Instance to as documented on page 17. Download the required upgrade package To download the upgrade package:» Download the RealPresence DMA system upgrade package from Note: The upgrade package will be available in the Appliance Edition Software Downloads section of the support page. The upgrade package link is identified by the upgrade path and has a filename ending in "rppufconv.bin. Polycom, Inc. 15

16 Back up system data To backup system data: 1 Using a web browser, log in to the RealPresence DMA system instance. 2 Go to the Maintenance > Backup and Restore page. 3 Click Create New (Full). The system creates a backup archive and displays a confirmation dialog when complete. 4 Download and save the newly created backup archive. Upgrade RealPresence DMA system to x To upgrade the system to x: 1 On your PC, open a command prompt. 2 In the command prompt, run the command ping t <IP address> where <IP address> is the IP address of the RealPresence DMA system instance. This command starts a continuous Ping of the system instance, which helps verify when it is safe to restart. There is no visual feedback from the server LCD screen or monitor (if attached). 3 Go to the Maintenance > Software Upgrade page. 4 Click the Upload button. A file chooser dialog appears. 5 Use the file chooser dialog to select the x upgrade package. 6 Click Open. A progress dialog appears. 7 Click the Upgrade button and start a timer. 8 After at least eight minutes have elapsed, ensure that the system instance is no longer resonding to ping requests. Do not proceed until the system has not responded to ping requests for at least 40 seconds. 9 Press and hold the server s power button, located on the front of the system. 10 Once the server is powered off, press the power button again to power it back on. 11 After 22 total minutes have elapsed, ensure that the system instance is no longer resonding to ping requests. Do not proceed until the system has not responded to ping requests for at least 40 seconds. 12 Power off the server using the power button. 13 Once the server is powered off, press the power button again to power it back on. 14 Once the server is powered on, allow at least 40 minutes for the upgrade to complete. 15 Using a web browser, log in to the RealPresence DMA system instance. Polycom, Inc. 16

17 16 Go to Help > About DMA 7000 to ensure that the system instance has been upgraded. Upgrade RealPresence DMA System x Instance to To upgrade the DMA system x instance to 6.3.0:» Follow the steps in Upgrade RealPresence DMA system instance to on page 14 to complete the final upgrade. Upgrade RealPresence DMA System to x and then These upgrade instructions describe how to upgrade a through RealPresence DMA system instance on a RealPresence Video DualManager 400 system to x (where x is the most current posted patch release). Perform the following tasks to upgrade your system instance to x: 1 Download the upgrade package. 2 Back up the system data. 3 Reinstall the system instance software. 4 Upgrade the software to x. 5 Restore the system instance data. 6 Go to the section Upgrade RealPresence DMA system instance to on page 14. Download the upgrade package To download the upgrade package:» Download the RealPresence DMA system upgrade package from Note: The upgrade package will be available in the Appliance Edition Software Downloads section of the support page. The upgrade package link is identified by the upgrade path and has a filename ending in "rppufconv.bin. Back up system data To backup system data: 1 Using a web browser, log in to the RealPresence Resource Manager system instance. 2 Perform a system backup. Refer to the Polycom RealPresence Resource Manager Operations Guide or online help for details on creating a system backup. 3 Log in to the RealPresence DMA system instance. 4 Go to the Maintenance > Backup and Restore page. Polycom, Inc. 17

18 5 Click Create New (Full). The system creates a backup archive and displays a confirmation dialog when complete. 6 Download and save the newly created backup archive. Reinstall the system software To reinstall the system software: 1 Insert the RealPresence Video DualManager 400 system software DVD into the system server DVD-ROM drive. 2 Power off the server using the power button. 3 Once the server is powered off, press the power button again to power it back on. The system boots from DVD and begins writing the new software image, which takes roughly 40 minutes to complete. When installation is complete, the system will eject the DVD and reboot twice. Once installation is finished, the system is ready for initial network configuration. 4 Configure basic network settings for both the RealPresence DMA system and RealPresence Resource Manager system components. Refer to the RealPresence Video DualManager 400 System Getting Started Guide (available on the Polycom support site) for initial configuration instructions. Polycom recommends that you configure only basic network settings, which will allow you to continue the upgrade. Upgrade RealPresence DMA system instance to x To upgrade the system software to x: 1 Using a web browser, log in to the RealPresence DMA system instance. 2 On your PC, open a command prompt. 3 In the command prompt, run the command ping t <IP address> where <IP address> is the IP address of the RealPresence DMA system instance. This command starts a continuous ping of the system instance, which helps verify when it is safe to restart. There is no visual feedback from the server LCD screen or monitor (if attached). 4 Go to the Maintenance > Software Upgrade page. 5 Click the Upload button. A file chooser dialog appears. 6 Use the file chooser dialog to select the x upgrade package. 7 Click Open. A progress dialog appears. 8 Click the Upgrade button and start a timer. Polycom, Inc. 18

19 9 After eight minutes have elapsed, ensure that the system instance is no longer resonding to ping requests. Do not proceed until the system has not responded to ping requests for at least 40 seconds. 10 Press and hold the server s power button, located on the front of the system. 11 Once the server is powered off, press the power button again to power it back on. 12 After 22 total minutes have elapsed, ensure that the system instance is no longer resonding to ping requests. Do not proceed until the system has not responded to ping requests for at least 40 seconds. 13 Power off the server using the power button. 14 Once the server is powered off, press the power button again to power it back on. 15 Once the server is powered on, allow at least 40 minutes for the upgrade to complete. 16 Using a web browser, log in to the RealPresence DMA system instance. 17 Go to Help > About DMA 7000 to ensure that the system instance has been upgraded. Restore the RealPresence DMA system backup To restore the system backup: 1 Using a web browser, log in to the RealPresence DMA system instance. 2 Go to the Maintenance > Backup and Restore page. 3 Click Upload. 4 Use the file chooser dialog to select the backup archive you created earlier. 5 Click Open. 6 Select the uploaded backup archive in the archive list. 7 Click Restore Selected. A confirmation dialog appears. 8 Click OK. The backup is restored, and the system restarts. Upgrade RealPresence DMA System x or greater to To upgrade the system software to 6.3.0:» Follow the steps in Upgrade RealPresence DMA system instance to on page 14 to complete the upgrade. Polycom, Inc. 19

20 System Shutdown and Restart If one of the component RealPresence Resource Manager or DMA systems is accidentally or intentionally shutdown from its user interface, you will be required to shutdown and restart the entire RealPresence Video DualManager system. The only way to shutdown the full RealPresence Video DualManager system is via the physical console. To shutdown (power off) the RealPresence Video DualManager system server 1 If possible, first initiate a Shutdown of the active component RealPresence Resource Manager or DMA systems. Initiating a Shutdown through the systems user interfaces will terminate all calls and will log out all current users. 2 Connect a keyboard and monitor (optional) to the RealPresence Video DualManager system server and, even without a login shell, issue a Ctl-Alt-Del key combination. The system will attempt to gracefully shutdown (and then forcibly shutdown) the component systems if they do not respond within a time period. Finally, the server will power down. To restart (power on) the RealPresence Video DualManager system server Note: This procedure does not require a keyboard or monitor, although a monitor is useful to view the status of the system restart.» Power on the RealPresence Video DualManager system server. Upon restart, all systems will restart. Frequently Asked Questions Installation, Upgrades and Maintenance How do I upgrade my RealPresence Video DualManager system? Can I upgrade my RealPresence Resource Manager and DMA systems independently? Supported RealPresence Resource Manager and DMA system upgrades can be performed from the component systems user interface as documented in the Upgrade Information section on page 8. However, be sure to check the Products Tested with this Release section on page 6 for compatibility information. Note: If a major version upgrade requires re-imaging of an installed system, this may require a new installation of the RealPresence Video DualManager system. If I am migrating a CMA system, how does my licensing change? Your CMA system licensing and service entitlements transition to individual licenses for the component RealPresence Resource Manager and DMA systems. However, you will get new serial numbers. Polycom, Inc. 20

21 Will there be RealPresence Video DualManager system-specific guides for the RealPresence Resource Manager and DMA systems? There are no RealPresence Video DualManager system-specific versions of the component RealPresence Resource Manager and DMA systems documentation. Can the RealPresence Video DualManager system run on a Dell 1950 server? No, the RealPresence Video DualManager system runs only on the Dell R610 or R620 servers purchased through Polycom. Troubleshooting What is the username and password for the console? When the RealPresence Video DualManager system boots, the console is displayed (if a monitor is attached), but there is no supported access to this console. Remote console access to the component RealPresence Resource Manager and DMA systems via SSH as configured separately in each product is fully supported. No remote console access to the hypervisor is available. When performing a packet capture on the component RealPresence Resource Manager and DMA systems, can you see the traffic on the component system? You can only capture the packets that are specific to or from the component system on which you are running the capture. This will include packets from the other component system, but only when those packets are directed to or from the component system on which you are running. I shutdown my RealPresence Resource Manager and DMA systems from its web user interface. How can I restart it? You cannot without restarting the other still running component system. See System Shutdown and Restart on page 20. How can I troubleshoot the RealPresence Video DualManager system and its component products? Use standard techniques available through the component system user interface or remote SSH to troubleshoot the component RealPresence Resource Manager and DMA systems. No direct access or troubleshooting of the hyper visor is available. Migration Can a CMA 5000 system be migrated to RealPresence Video DualManager system via this new migration process? No, not currently. Polycom, Inc. 21

22 Copyright 2015, Polycom, Inc. All rights reserved. No part of this document may be reproduced, translated into another language or format, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc America Center Drive San Jose, CA USA Polycom, the Polycom logo and the names and marks associated with Polycom products are trademarks and/or service marks of Polycom, Inc. and are registered and/or common law marks in the United States and various other countries. All other trademarks are property of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, for any purpose other than the recipient's personal use, without the express written permission of Polycom. Java is a registered trademark of Oracle America, Inc., and/or its affiliates. End User License Agreement By installing, copying, or otherwise using this product, you acknowledge that you have read, understand and agree to be bound by the terms and conditions of the End User License Agreement for this product. Patent Information The accompanying product may be protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. Open Source Software Used in this Product This product may contain open source software. You may receive the open source software from Polycom up to three (3) years after the distribution date of the applicable product or software at a charge not greater than the cost to Polycom of shipping or distributing the software to you. To receive software information, as well as the open source software code used in this product, contact Polycom by at OpenSourceVideo@polycom.com. Disclaimer While Polycom uses reasonable efforts to include accurate and up-to-date information in this document, Polycom makes no warranties or representations as to its accuracy. Polycom assumes no liability or responsibility for any typographical or other errors or omissions in the content of this document. Limitation of Liability Polycom and/or its respective suppliers make no representations about the suitability of the information contained in this document for any purpose. Information is provided as is without warranty of any kind and is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall Polycom and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss of business information), even if Polycom has been advised of the possibility of such damages. Customer Feedback We are striving to improve our documentation quality and we appreciate your feedback. your opinions and comments to DocumentationFeedback@polycom.com. Visit the Polycom Support Center for End User License Agreements, software downloads, product documents, product licenses, troubleshooting tips, service requests, and more. Polycom, Inc. 22