RealPresence Platform Director

Transcription

1 RealPresence CloudAXIS Suite Administrators Guide Software ADMINISTRATOR GUIDE Software 1.8 December Rev C RealPresence Platform Director Polycom, Inc. 1

2 Copyright 2014, 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 Trademarks 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. 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. 2

3 Contents About This Guide... 7 Conventions Used in this Guide... 7 Terms Used in this Guide... 7 Information Elements... 8 Typographic Conventions... 9 Help and Technical Support... 9 Polycom Support... 9 Reference Documentation Documentation Feedback Product Overview Product Architecture RealPresence Platform Software RealPresence DMA, Virtual Edition RealPresence Resource Manager, Virtual Edition RealPresence Collaboration Server, Virtual Edition RealPresence Access Director, Virtual Edition RealPresence CloudAXIS Suite Supported RealPresence Virtual Editions Product Requirements... Error! Bookmark not defined. Data Center Requirements... Error! Bookmark not defined. Software License Requirements... Error! Bookmark not defined. Web Browser Requirements... Error! Bookmark not defined. Deploy RealPresence Platform Director in Your VMware Environment VMware Requirements Prepare for the Deployment Deploy the RealPresence Platform Director Image in a vcenter or Supported Virtual Environment Configure the RealPresence Platform Director System Open the Polycom Management Console Stop RealPresence Platform Director Services Configure the Basic Network Configure the DNS Server Settings Set a Host Name for the Instance Generate a Self-Signed Security Certificate Restart RealPresence Platform Director Services Configure Licenses for the RealPresence Platform Director Instance Open the New RealPresence Platform Director Instance Log In to the Polycom Licensing Center Activate Licenses for a RealPresence Platform Director Instance Polycom, Inc. 3

4 Deploy RealPresence System Components Create a New Instance of a Supported RealPresence Product Deployed in a vcenter Add an Instance of a Supported RealPresence Product Deployed Outside vcenter Upgrade an Existing Instance of a RealPresence Product Add an Existing RealPresence Instance for Monitoring Only Create a New Instance and Migrate Data from a Prior Version Manage and Configure the RealPresence Platform Director Environment Manage Providers Add a Provider Edit Provider Details Delete a Provider Manage Zones Add a Zone Edit Zone Details Delete a Zone Manage Resource Groups Add a Resource Group to a Zone Edit a Resource Group View Resource Group Status Delete a Resource Group Manage Virtual Edition Images Add a Component Virtual Edition Image Edit Image Values Delete an Image Manage Instances Create a New Virtual Instance Add an Existing Virtual Instance Add an Existing Appliance Instance Add an Existing (Non-vCenter) Instance View or Edit Instance Details Delete an Instance Manage Service Groups Create a Service Group View or Edit Service Group Details Add a New Instance to a Service Group Remove an Instance from a Service Group Manage RealPresence Product Licenses Online and Offline Mode Allocate Licenses for Polycom RealPresence System Components Monitor the RealPresence Platform Director Environment SNMP Description SNMP Framework Polycom s Use of SNMP SNMP Notifications Polycom, Inc. 4

5 Set Up System Monitoring Enable SNMP for an Instance Alarms Monitored by RealPresence Platform Director View Active Alarms View Alarms by Entity Type Clear Alarms from the System View and Edit Threshold Values View or Edit Thresholds for a Defined Group View or Edit Threshold Details for a Product Instance View or Edit Threshold Details Within a Service Group View Resource and License Data Available Data Monitored System Resources and License Usage Manage Users User Roles in RealPresence Platform Director System Access by User Type Manage System Users Add a User Edit a User Delete a User Reset a User Password Manage Administrator Account Credentials Edit Your Administrator Profile Change Your Administrator Password Manage Platform Settings Manage Certificates Generate Certificates and CSRs View or Delete a Certificate Upload a Certificate or Certificate Chain View and Manage Logs Configure RealPresence Platform Director to use SMTP Enable SNMP in the RealPresence Platform Director Environment Appendix 1: Required VMware Permissions Overview vcenter Permissions VMware APIs in RealPresence Platform Director Instance Management Add a VM Instance Create an Instance Add an Existing Instance Monitor vcenter Resources Recommendations References Polycom, Inc. 5

6 Appendix 2: Network Port Requirements Appendix 3: Troubleshooting Deployment Management Appendix 4: Third-Party Software Offer of Source for Open Source Software Open Source Software Contact information for requesting source code License Information Polycom, Inc. 6

7 About This Guide This administrator guide uses a number of conventions that will aid you in understanding the purpose, functions, and capabilities of the Polycom RealPresence Platform Director system. Conventions Used in this Guide This administrator guide contains terms, graphical elements, and typographic conventions. Familiarizing yourself these will help you administer the RealPresence Platform Director system. Terms Used in this Guide This administrator guide contains various Polycom and telecommunications industry terms and acronyms, graphical icons and elements, and typographical conventions. Understanding these conventions will help you perform administrative tasks in the RealPresence Platform Director. The following terms and acronyms are found in this guide. Terms Used in this Guide Term Apache Tomcat FQDN Image Nginx NTP Server Provider Resource Group Service Group vcenter Definition An open source web server and application container that runs the web-based RealPresence Platform Director application. Fully Qualified Domain Name. A complete domain name for a computer or host on the internet. Example of an FQDN: dma.example.com. RealPresence Platform subcomponents provided as *.ova files, which are uploaded to RealPresence Platform Director to create product instances. An HTTP server used to render static content and delegate requests to Apache Tomcat. Network Time Protocol Server. The NTP server sets the time and date settings for RealPresence components managed within RealPresence Platform Director. Providers supply the RealPresence Platform Director with a virtualized infrastructure for creating instances. VMware is currently the only supported Provider. A position within a zone that includes a group of computers, storage devices, and network resources used to deploy instances. The resource group is available within a zone. An organized collection of Virtual Machines (VMs) and various virtual Instances that make up a video collaboration suite. The VMware vcenter Server is one product from the vsphere suite. It centralizes the management of multiple ESXi hosts as a single virtual environment. Polycom, Inc. 7

8 Term vsphere Virtual Edition VM Zone Definition VMware vsphere is a suite of products, including VMware ESXi hypervisor, VMware vcenter Server, and other optional products and modules, that create a virtualization platform used to deploy and manage the RealPresence Platform Director, RealPresence Platform components, and RealPresence CloudAXIS Suite components. RealPresence Platform Director components as software-based Virtual Machines. Virtual machine. A software-based emulation of a computer. A RealPresence Platform Director-defined encapsulation of the physical location that houses an instance or set of instances. The zone includes a provider, data center, host/cluster, resource pool, data storage, and network resources. Information Elements The icons described in the table below are used to alert you to various types of important information in this guide. Icons Used in this Guide Name Icon Description Note The Note icon highlights information of interest or important information needed to be successful in accomplishing a procedure or to understand a concept. Administrator Tip The Administrator Tip icon highlights techniques, shortcuts, or productivity related tips. Caution Warning Web Info The Caution icon highlights information you need to know to avoid a hazard that could potentially impact device performance, application functionality, or successful feature configuration. The Warning icon highlights an action you must perform (or avoid) to prevent issues that may cause you to lose information or your configuration setup, and/or affect system performance. The Web Info icon highlights supplementary information available online such as documents or downloads on support.polycom.com or other locations. Timesaver The Timesaver icon highlights a faster or alternative method for accomplishing a task or operation. Power Tip The Power Tip icon highlights faster, alternative procedures for advanced administrators already familiar with the techniques being discussed. Troubleshooting The Troubleshooting icon highlights information that may help you solve a relevant problem or to refer you to other relevant troubleshooting resources. Polycom, Inc. 8

9 Name Icon Description Settings The Settings icon highlights settings you may need to choose for a specific behavior, to enable a specific feature, or to access customization options. Typographic Conventions A few typographic conventions, listed next, are used in this guide to distinguish types of in-text information. Typographic Conventions Convention Bold Italics Blue Text Fixed-width font (courier) Description Highlights interface items such as menus, soft keys, file names, and directories. Also used to represent menu selections and text entries. Used to emphasize text, to show example values or inputs, and to show titles of reference documents available from the Polycom Support Web site and other reference sites. Used for references to topics and sections within this document andurl links to external web pages or documents. If you click on blue text, you will be taken to either an external document or web page, or to a reference within this document Used for code fragments and parameter names. Help and Technical Support Help and technical support for the RealPresence Platform Director is available at the Polycom Support Center. The following sections provide links for service and specific products and their documentation. Polycom Support For product support or service, contact your Polycom reseller. For software downloads, product documentation, product licenses, troubleshooting tips, service requests, and more, visit the RealPresence Platform Director support site. Polycom, Inc. 9

10 Reference Documentation The following support and reference documentation is available on the RealPresence Platform Director support site: RealPresence Platform Director Software 1.8 Release Notes RealPresence Platform Director Software 1.8 Administrators Guide RealPresence Platform Director Software 1.8 Getting Started Guide For details on each of the RealPresence Platform products that may be used with the RealPresence Platform Director, visit the Polycom support web site for links to: Polycom RealPresence DMA 7000 Polycom RealPresence Resource Manager Polycom RealPresence Access Director Polycom RealPresence Collaboration Server Polycom RealPresence CloudAXIS Suite (Services Portal and Experience Portal) For details on all Polycom RealPresence CloudAXIS Suite products, visit oudaxis_suite.html. You can find Request for Comments (RFC) documents by entering the RFC number at VMware support and reference documentation is available at (and select documentation for Release 5.1 or Release 5.0 ) For other references, look for the Web Info icon throughout this administrator guide. Documentation Feedback We strive to improve the quality of our documentation, and we appreciate your feedback. Please send your with questions or suggestions to DocumentationFeedback@polycom.com. Polycom, Inc. 10

11 Product Overview RealPresence Platform Director provides the flexibility to deploy the RealPresence Platform and RealPresence CloudAXIS Suite products using general-purpose hardware in a data center or in the cloud. RealPresence Platform Director is required to deploy software and manage licensing for other Polycom RealPresence products. It can support deployments on any virtualized data center running VMware. The RealPresence Platform Director helps you deploy and monitor the Polycom RealPresence Platform and RealPresence CloudAXIS Suite products to enable universal access to enterprise-grade video collaboration to any business (B2B) or consumer (B2C) at the highest quality, reliability, and security. The RealPresence Platform Director system is required for deployment and licensing of the following RealPresence Platform, Virtual Editions. RealPresence Collaboration Server, Virtual Edition RealPresence DMA, Virtual Edition RealPresence Resource Manager, Virtual Edition RealPresence Access Director, Virtual Edition RealPresence CloudAXIS Services Portal and Experience Portal The CloudAXIS Services Portal and Experience Portal can be deployed within or outside the RealPresence Platform Director system. Because the CloudAXIS products do not support SMNP at this time, resource and license monitoring is not available for these products. Product Architecture The following graphic illustrates a deployment scenario in which an organization s data centers are distributed globally. It shows an enterprise infrastructure with a vcenter that has been added as a Provider in the RealPresence Platform Director System. This vcenter controls two data centers, each comprising a zone in the RealPresence Platform Director configuration. Each zone contains at least one resource group that includes resources such as hosts, clusters, and storage locations. Instances are placed into service groups in RealPresence Platform Director for easy monitoring by system administrators. Using RealPresence Platform Director, system administrators for this enterprise can create and manage a RealPresence Platform infrastructure across the entire organization with full control over how and where instances are created. Polycom, Inc. 11

12 RealPresence Platform Director in a typical network RealPresence Platform Software Supported Products are listed below. Go to the Polycom support web site for the currently supported RealPresence product release number. RealPresence DMA, Virtual Edition RealPresence Resource Manager, Virtual Edition RealPresence Collaboration Server, Virtual Edition RealPresence Access Director, Virtual Edition RealPresence CloudAXIS, Services Portal and Experience Portal RealPresence DMA, Virtual Edition The RealPresence DMA, Virtual Edition, can manage a mixed pool of RMX devices and software Multipoint Control Units (MCUs) and distribute multipoint video calls across conference platforms. RealPresence Resource Manager, Virtual Edition The RealPresence Resource Manager, Virtual Edition, is an integrated scheduling and device management platform for video conferencing. This platform: Manages the conferencing system, including the software versions and updates of each managed device, the provisioning of devices, and the monitoring of conference activity. Sets up and maintains scheduled conferences. Polycom, Inc. 12

13 Maintains and supports a directory of the system devices and user credentials. RealPresence Collaboration Server, Virtual Edition The RealPresence Collaboration Server, Virtual Edition, is Polycom s software-based multi-point control unit (MCU). RealPresence Access Director, Virtual Edition The RealPresence Access Director, Virtual Edition, provides remote, guest, and business-to-business users with the ability to securely access video services from anywhere. RealPresence CloudAXIS Suite The RealPresence CloudAXIS Services Portal enables users to create and participate in online video conference meetings. Users create meetings by logging into the Services Portal, selecting the type of meeting they want to create, setting the meeting parameters, and entering a list of participants to invite. The RealPresence CloudAXIS Services Portal also provides administrative capabilities for creating and managing users and for configuring the components of the online video conference meetings. The RealPresence CloudAXIS Experience Portal is the conferencing interface that enables users to participate in online enterprise video conferences and control their online video experience. Supported RealPresence Virtual Editions The virtual editions of Polycom RealPresence Platform products supported with current and prior versions of RealPresence Platform Director are listed in the following table. Most earlier versions of RealPresence component products can be monitored within RealPresence Platform Director, although licensing is not supported in those earlier versions. SNMP must be enabled within each component product before RealPresence Platform Director can monitor those instances. Supported Polycom RealPresence Virtual Editions Product Current Version SNMP Monitoring Licensing Earlier Versions SNMP Monitoring DMA 6.1 higher Yes Yes 6.0 lower Yes RealPresence Resource Manager 8.2 higher Yes Yes 8.2 lower Yes RealPresence Access Director 4.0 higher Yes Yes 3.1 lower Yes RealPresence Collaboration Server 8.4 higher Yes Yes 8.3 lower Yes RealPresence CloudAXIS (Services and Experience Portals) RealPresence Content Sharing Suite (CSS) 1.6 higher No Yes 1.5 lower No 1.3 higher No Yes 1.2 lower No Polycom, Inc. 13

14 Deploy RealPresence Platform Director in Your VMware Environment The RealPresence Platform Director requires deployment in a data center equipped with VMware vcenter. After deployment, RealPresence Platform Director can be configured to manage, license, and monitor RealPresence Platform components. The installation package is delivered as a VMware Open Virtual Appliance (*.OVA) file to be deployed in a VMWare environment following deployment procedures. The instructions that follow outline the steps for a first-time setup of RealPresence Platform Director in a working vcenter. VMware Requirements You can deploy the RealPresence Platform Director Virtual Edition software using VMware vcenter or another VMware-compatible environment. If you are installing in a vcenter, before attempting to deploy RealPresence Platform Director, verify that you have the correct permissions to instantiate the virtual instance within vcenter. Refer to appropriate VMware documentation for a description of the required permissions. If you are installing in another VMware-compatible environment, refer to the correct documentation for your VM infrastructure for how to deploy the RealPresence Platform Director *.OVA. Note: VMware requirements RealPresence Platform Director can be deployed with VMware vcenter or any EXSi host or cluster. vcenter is required for RealPresence Platform Director to deploy or monitor your Virtual Machine infrastructure. Prepare for the Deployment Complete the tasks outlined below to prepare to deploy the RealPresence Platform Director in your virtual data center environment. 1 Read the Release Notes for the version of RealPresence Platform Director that you are deploying, and confirm that your system meets the requirements. 2 Obtain the URL and login credentials for the Polycom Licensing Center. Both are contained in the that Polycom sent to your organization to confirm the purchase of license entitlements for RealPresence Platform, Virtual Edition, RealPresence One, or RealPresence CloudAXIS products. 3 Obtain administrator login credentials to the vcenter environment where RealPresence Platform Director is being installed. Running the installation requires a user login that has permission to deploy *.OVA files. Polycom, Inc. 14

15 For a vcenter installation, use an account role with permissions that allow RealPresence Platform Director to deploy and monitor virtual instances. See the appendix to this document regarding required vcenter permissions for more information on specific permissions required for RealPresence Platform Director to run in VMware vcenter. 4 Confirm that the required ports are available in your system. For a list of network ports used in a RealPresence Platform Director installation, see the appendix to this Guide outlining port requirements. 5 Download the RealPresence Platform Director *.OVA file from the Polycom Support web site, and note the location of the file on your network. 6 Allocate an IP address for the RealPresence Platform Director instance, and note the Network Mask and Default Gateway to be used with the address. Although the RealPresence Platform Director can be used in a carefully configured DHCP environment that guarantees an unchanging IP address, Polycom recommends that you allocate and configure a static address for the instance. 7 Obtain the names and IP addresses of the DNS servers on your network that will resolve the domain and other system names for the RealPresence Platform Director instance. 8 Assign a local hostname to identify the RealPresence Platform Director instance within your organization s root domain. The host name and root domain names together constitute the fully qualified domain name (FQDN) that allows users to access the instance and administrator console with a web browser. Configure this FQDN on the appropriate DNS server or servers. Deploy the RealPresence Platform Director Image in a vcenter or Supported Virtual Environment Use the standard VMware deployment procedure to deploy the RealPresence Platform Director *.OVA in your virtual data center. Deploy RealPresence Platform Director in vcenter if you have it; if you do not have vcenter, you can deploy the RealPresence products directly onto the EXSi host, using its console. The vcenter administrator interface guides you through the deployment process. If you are deploying on an EXSi host, consult the EXSi deployment instructions in the appropriate VMware documentation. Note: Time required to deploy new virtual instance varies. The speed of your network determines how quickly the image loads. Completing the RealPresence Platform Director deployment can take as little as five minutes or as long as an hour or more. To deploy the RealPresence Platform Director *.OVA template in a vcenter or supported virtual server environment: 1 Open the vsphere application connecting to your vcenter or vsphere server where the RealPresence Platform Director will be installed. Polycom, Inc. 15

16 2 In the main vcenter menu, go to File > Deploy OVA Template to open the Source selection window. 3 In the Deploy from a file or URL dialog, enter the valid URL or browse to the file where the RealPresence Platform Director *.OVA is located. Then click Next. 4 Select the check box to accept the End User License Agreement (EULA) to continue. The EULA displayed in this screen includes licensing terms for all RealPresence Platform Director Solution components, and it must be acknowledged for all the Polycom products that the RealPresence Platform Director deploys. 5 In the Name and Location window, type a descriptive name for the RealPresence Platform Director instance. Then select an inventory location from the list of those available in your virtual data center. Click Next. 6 In the Host / Cluster window, select an available host or cluster for where the image file will be stored. Then choose a Resource Pool within the Host Cluster. 7 In the Storage window, select an available storage destination for the RealPresence Platform Director virtual machine files. Click Next. 8 In the Disk Format window, select a provisioning policy among those available on the list. This selection is left to the discretion of individual administrators and is dependent upon how disk clusters have been configured in your data center. 9 Verify the selections in the Deploy OVF Template window, and then click Next. 10 Select the Power on after deployment option to restart the server after the deployment is complete, and then click Finish to begin the deployment in your vcenter. Configure the RealPresence Platform Director System Next, configure the RealPresence Platform Director system using the Polycom Management Console. After completing the initial configuration, you can use the new system to deploy other RealPresence Platform products and perform the associated licensing tasks. The initial configuration of RealPresence Platform Director involves the following tasks. Open the Polycom Management Console Stop RealPresence Platform Director Services Configure the Basic Network Configure the DNS Server Settings Set a Host Name for the RealPresence Platform Director Instance Generate a Self-Signed Security Certificate Restart RealPresence Platform Director Services If you choose to configure network settings and use static IP in the configuration, Polycom recommends completing the steps in the order listed to install a new RealPresence Platform Director instance. That order is reflected in the numbering of the tasks on the Polycom Management Console. If you choose to use DHCP to assign IP and related network information to the RealPresence Platform Director instance, Polycom, Inc. 16

17 you can skip the network configuration steps and then generate a security certificate to make the instance available in your network environment. Open the Polycom Management Console When the image deployment is complete, open the appropriate console menu tab to access the Polycom Management Console. This console helps you configure the RealPresence Platform Director instance to run in your virtual environment. The following instructions describe the process for using vcenter to host your RealPresence Platform Director system. Use the console in the EXSi host if you are not deploying in a vcenter. To open the Polycom Management Console: 1 In the main vcenter Administrator menu, select the Console tab to open the vcenter console menu. 2 At the localhost login prompt, type polycom for both the user name and password to open the Polycom Management Console, as shown next. Polycom Management Console From the Polycom Management Console, you can configure the RealPresence Platform Director instance that you deployed in your virtual server environment. It includes a list of the steps required to complete the configuration, along with options for changing the console password, uploading and installing a software patch, using the ping command to verify an IPv4 address or name on your network. With the Polycom Management Console open, you can begin configuring the RealPresence Platform Director instance to run in your virtual environment. Polycom, Inc. 17

18 Note: Change the Polycom Management Console password Polycom recommends changing the Management Console password for the polycom user. To change the password, select option 9 Change Password (for this login). Follow the prompts to change the password. Stop RealPresence Platform Director Services To begin configuring the RealPresence Platform Director instance, you must first stop the RealPresence Platform Director services that are running on the server. To stop the RealPresence Platform Director services:» From the Polycom Management Console, select option 1 Stop RealPresence Platform Director Services. Then select Yes in the confirmation window. You can move to the next step when a message confirms the services have been stopped. Configure the Basic Network You must associate a network card and IP address with the RealPresence Platform Director instance. To configure the network for the RealPresence Platform Director instance: 1 From the Polycom Management Console, select option 3 Configure Network. 2 In the Choose Network Interface window, select a network interface card to control the Ethernet connection to the server. 3 In the Choose Interface Mode window, do one of the following: If you want to set a permanent IP address for the network card, select option 1 Static address setup. Then, in the next window, enter the IP address, network mask, and default gateway. If you want to assign an address dynamically, select option 2 Set DHCP On. Select OK when you have completed the Interface Mode configuration. The system stops the network services and restarts them with the new IP settings. 4 Verify that the network settings are correct in the Current Network Setup window. Then select OK. Configure the DNS Server Settings The DNS server identifies the IP address of the server that RealPresence Platform Director uses to resolve hostnames. While a DNS Server may have been previously specified in the configuration, it should be overwritten with the correct DNS server address for your network. To configure the DNS server settings: 1 From the Polycom Management Console, select option 4 Configure DNS. 2 Verify the Domain, Search Domain, and Name Server settings in the DNS Configuration window. Change them as necessary, and then select OK when the configuration is complete. Polycom, Inc. 18

19 Set a Host Name for the Instance Next, set a domain name for the RealPresence Platform Director instance you are installing. To set the Host Name for RealPresence Platform Director: 1 From the Polycom Management Console, select option 5 Change Host Name. 2 In the Change Host Name window, use the Delete or Backspace key to delete the default localhost.localdomain name setting. Then type the new host name along with your company s domain in the form of the fully qualified domain name to be used to access the RealPresence Platform Director from a web browser. 3 Select OK to return to the Polycom Management Console. Generate a Self-Signed Security Certificate Because RealPresence Platform Director requires HTTPS to secure data transactions, you must generate a self-signed trust certificate before you complete the configuration and open the RealPresence Platform Director administrator interface for the first time. To generate a self-signed security certificate for the RealPresence Platform Director instance:» From the Polycom Management Console, select option 6 Generate Self-Signed Security Certificate. Click Yes in the confirmation window to generate the certificate. When you have completed the configuration, you can create signed certificate requests and upload thirdparty certificates to the server as required. Restart RealPresence Platform Director Services To apply new configuration settings, you must restart the RealPresence Platform Director services. To restart the RealPresence Platform Director services:» From the Polycom Management Console, select option 8 Start RealPresence Platform Director Services. Select Yes in the confirmation window. You can also choose option 7-Reboot Server to reboot the server entirely. After the services have restarted, you can start the RealPresence Platform Director instance and begin configuring licenses for it. Configure Licenses for the RealPresence Platform Director Instance After you have configured a new RealPresence Platform Director instance, open it using a web browser, and create a license server on which to activate licenses that your organization has purchased for the product. After activating the initial license for RealPresence Platform Director, you can allocate individual licenses to it and then begin using the system to add and manage other RealPresence component products. Polycom, Inc. 19

20 Caution: Activate licenses before using the system. Licenses for RealPresence Platform Director must be activated and validated before you can use RealPresence Platform Director to manage your RealPresence solution system. Setting up licenses for RealPresence Platform Director involves the following steps: Open the New RealPresence Platform Director Instance Log In to the Polycom Licensing Center Activate Licenses for the RealPresence Platform Director Open the New RealPresence Platform Director Instance To begin setting up licenses, log in to the new RealPresence Platform Director instance using a supported web browser. For a list of supported web browsers, see Web Browser Requirements. When you first log in to the RealPresence Platform Director as an administrator, only the LICENSE MANAGEMENT tab is available. You must complete the license activation process before you have access to the all of the functions available on the Administrator menu. To open a RealPresence Platform Director instance: 1 In the address bar of a supported web browser, type the address of the main login page using the IP address of the instance, as follows: address for the RealPresence Platform Director instance] The RealPresence Platform Director login screen opens, as shown. RealPresence Platform Director login screen 2 Do one of the following: If this is your first time logging in to this instance, type admin as the User ID and Polycom12#$ as the Password. Select the checkbox to accept the End User License Agreement (EULA), and then follow the prompt to change the admin password. If this is not your first time logging in to this instance, enter the correct admin user name and password for this instance. Polycom, Inc. 20

21 The initial login may take a minute or more. On the first login, the menu available includes only the License Management function. The full menu is made available after licensing for RealPresence Platform Director has been activated. 3 From the RealPresence Platform Director Administrator menu, go to LICENSE MANAGEMENT. On the LICENSE SETUP page, a message indicates that the system is not licensed or the license has expired, as shown next. License Management page with System Identifier Note the System Identifier number listed on the page, and keep the page open so that you can refer to it again in the next steps. When you begin activating RealPresence system licenses on the Polycom Licensing Center site, you will copy and paste the unique number listed on this page to begin activating system licenses. Log In to the Polycom Licensing Center When your organization purchased licensing for RealPresence Platform Director or later, Polycom sent an containing a URL and login to the Polycom Licensing Center. Use that information to log in to the Polycom Licensing Center to set up a license server and manage your Polycom RealPresence licenses. If your RealPresence Platform Director instance does not have direct access to the internet, you can log in to the Polycom Licensing Center from a computer that does have internet access and then use the offline process to activate the license. With the offline process, you can download a license file from the Licensing Center and then upload it into the virtual Platform Director environment. To log in to the Polycom Licensing Center: 1 Paste or type the URL for the Polycom Licensing Center into the address bar of a web browser. 2 On the login page, type the Login ID and Password that Polycom provided to your organization with the organization s entitlement information. A successful login opens the Polycom Licensing Center page as shown next. Polycom, Inc. 21

22 Polycom Licensing Center landing page 3 On the Polycom Licensing Center page, click Create Server to open the Create Server page and create a license server for your RealPresence products. Enter information in the text and drop-down lists as outlined in the following table. Polycom License Center Create Server page Field License Server ID Backup Device ID Alias Site Name Value/Description Copy and paste the System Identifier number from the License Management page that appeared when you first logged in to the RealPresence Platform Director instance. Currently not supported. Leave this field blank. (Optional) A unique name for your license server, if you wish to assign one. (Optional) A descriptive name for your Polycom RealPresence license management site. 4 After completing the information in the text and drop-down boxes, click Create. When the license server has been created successfully, a View Server page displays your valid License Server ID, ID Type, and Site Name, as shown next. Polycom, Inc. 22

23 View Server page showing a successful license activation Next, you map and generate available licenses to your RealPresence system. See Activate Licenses for the RealPresence Platform Director. Activate Licenses for a RealPresence Platform Director Instance After setting up your license server, you must activate available licenses for the RealPresence Platform Director. You can manage licenses for individual components of your RealPresence system after those instances have been added to the system. NOTE: License activation may require 5-10 minutes to take effect in the system. Activating licenses for Polycom RealPresence components requires communications between Polycom RealPresence instances in your system and may require 5-10 minutes to take effect across the network. If you do not see the licensing information you expect to see on the License Management page after activating RealPresence licenses, refresh the browser or the page, or navigate away from the License Management page and then return to it to refresh the data. For more information on how to manage licenses in your RealPresence environment, see Manage Licenses. To activate licenses for the RealPresence Platform Director: 1 On the Polycom Licensing Center View Server page, click the Map Add-Ons link to show a list of available units for features your organization has purchased, as shown next. Polycom, Inc. 23

24 Partial sample list of available add-on features for licensing 2 In the Qty to Add column for the listed RP1 Uni-Concurrent Connect Lic, enter the number of licenses of those available to allocate to the RealPresence Platform Director instance. If your organization is installing a single RealPresence Platform Director instance, allocate all of the available licenses to it. If your organization is using two or more RealPresence Platform Director instances, allocate only a portion of the available licenses to the current instance so that the licenses will be available for subsequent instances when they are installed. 3 Click Map Add-Ons to allocate the licenses. If your RealPresence Platform Director instance does not have access to the internet, click Download Capability Response to download a local copy of the license file. This download allows you to manage RealPresence system licenses offline. Note the location of the license file when you download it to your local computer. You will upload this file to the RealPresence Platform Director instance to activate the licensing. If your RealPresence Platform Director system has access to the internet, you must use the online method to license the system and its components. The offline method for managing licenses is not an option when internet access is available. The View Server page displays a list of available licenses, along with their status, expiration date, and other information. The status indicates whether the license has been generated. A license must be generated to allow the corresponding system component to operate within your RealPresence system. Polycom, Inc. 24

25 Allocated license Add-Ons showing License not generated status 4 Return to the License Setup page, and do one of the following: Click Online if your virtual environment has access to the Internet and can use the online method for managing licenses. Click Offline if your virtual environment does not have access to the Internet and therefore requires use of the offline, file-based method for managing licenses. The screen prompts will guide you through the offline update process using the license file previously downloaded from the Polycom Licensing Center. 5 Click Update to complete the license activation process, as shown next. License Setup dialog prior to updating the RealPresence Platform Director license A successful activation produces an active license notation, as shown next. After clicking UPDATE, you may need to refresh the browser screen to show the activated license. License setup showing valid, active license Polycom, Inc. 25

26 After a successful license update for RealPresence Platform Director licensing, the full menu and dashboard become available for managing the system and its components. After the RealPresence Platform Director instance has been activated, you can begin adding other RealPresence components to the RealPresence Platform Director system. Full RealPresence Platform Director Administrator menu Polycom, Inc. 26

27 Deploy RealPresence System Components When you add RealPresence system components to the RealPresence Platform Director, it can manage licensing and monitor alarms for the component products. Polycom RealPresence Platform products listed below require the RealPresence Platform Director to monitor the instances and manage licensing for them. RealPresence Collaboration Sever RealPresence Distributed Media Application RealPresence Access Director RealPresence Resource Manager RealPresence CloudAXIS Service Portal and Experience Portal Most fully supported versions of RealPresence products can be both licensed and monitored in RealPresence Platform Director. Many unsupported versions can be monitored but not licensed through it. See the list of Supported RealPresence Virtual Editions to determine whether the instance you are adding can be licensed and/or monitored through RealPresence Platform Director. Adding component instances to Real Presence Platform Director can be accomplished in several different ways, depending on whether the instances are being deployed into a vcenter or another supported VMware environment, and the level of permissions the administrative user performing the installation has for the VMware environment. The following table describes the differences in functionality that are available in various environments with administrator to less-than-administrator-level permissions. RealPresence Platform Director functionality based on VM infrastructure VMWare Environment vcenter (with appropriate permissions, see the appendix to this document regarding vcenter permissions) vcenter with read-only permissions RealPresence Platform Director Functionality Full PD functionality Cannot use Create a new instance Cannot power on, power off or delete instances vcenter with no permissions Cannot use Create a new instance or Add new virtual instance Cannot monitor VM infrastructure Cannot power on, power off or delete instances Non-vCenter environment Cannot use Create a new instance or Add new virtual instance Cannot monitor VM infrastructure Cannot power on, power off or delete instances Polycom, Inc. 27

28 Scenarios for adding a new instance of a component product into a RealPresence Platform Director system are outlined in the following list. Follow the links to instructions for completing the outlined tasks. Create a new instance of a supported version of a vcenter-deployed RealPresence component product. Add an existing instance of a supported product in a vcenter. Add an existing instance of a supported version of a RealPresence Platform Director system without using vcenter. Upgrade an existing instance of a component product to one fully supported by the RealPresence Platform Director release and adding it as an existing instance within RealPresence Platform Director. Add an existing instance of prior version of product to RealPresence Platform Director for monitoring purposes only. Create a new instance of a RealPresence product with the intention of migrating data from a previous version of a RealPresence product that supports migration. (Currently, only CloudAXIS Services Portal and Experience Portal support such a migration of data and configuration settings.) Before you begin to install a new instance or upgrade an existing instance of a RealPresence product, do the following: Obtain the IP address, Network Mask, and Default Gateway if you are using a static IP configuration. If you are deploying in a vcenter, verify that a provider has been set up for the system. If one has not been set up, follow the instructions to Add a Provider to the vcenter environment. If RealPresence Platform Director will deploy or monitor your VMware infrastructure, a provider is necessary. Set up a zone and service group in which the instance will reside within your Polycom RealPresence system. After adding a new instance or upgrading an existing product, all licensing and monitoring for the RealPresence component product is accomplished through the RealPresence Platform Director administrator interface. Configuration of the network settings for the product are completed during the initial setup of the instance. Following are general instructions for completing the previously mentioned tasks. Detailed instructions are referenced and linked within the general instructions. Create a New Instance of a Supported RealPresence Product Deployed in a vcenter You can create an all-new instance of a component product version that is supported by the RealPresence Platform Director version running in your vcenter environment. Check the current Release Notes for both products to ascertain which versions are compatible. Complete the following tasks to create a new instance of a supported RealPresence product within your RealPresence Platform Director environment: 1 Create a new instance from the image in RealPresence Platform Director. Polycom, Inc. 28

29 2 Follow the instructions for configuring the IP address, time zone, NTP server, default time zone and other network information for the new instance. 3 Allocate counted capabilities to the new component product. Follow the procedure for allocating licenses for new system components. Add an Instance of a Supported RealPresence Product Deployed Outside vcenter You can add an instance of a RealPresence product that has been deployed in a supported virtual environment that is not a vcenter. Complete the following tasks to add an instance of a supported RealPresence product that is deployed in an environment other than vcenter: 1 Add an Existing (Non-vCenter) Instance of the RealPresence product from the supported virtual environment. 2 Follow the instructions for configuring the network information for the newly added instance. Upgrade an Existing Instance of a RealPresence Product You can upgrade an existing instance to an instance fully supported by the RealPresence Platform Director Release for a product already running within a RealPresence Platform Director environment. Setting up an instance in this way allows for licensing and monitoring through RealPresence Platform Director. To upgrade an existing instance RealPresence product to RealPresence Platform Director: 1 Follow the upgrade instructions in the Installation or Administrator Guide for the RealPresence product you want to upgrade. 2 If you are upgrading from an instance version that does not support licensing through RealPresence Platform Director, delete the instance from RealPresence Platform Director, and then follow the instructions in this guide to add an existing instance so that licenses for the instance can be managed through RealPresence Platform Director. Add an Existing RealPresence Instance for Monitoring Only You can add prior versions of RealPresence component products to RealPresence Platform Director if you want to monitor them along with other RealPresence products. Prior versions of RealPresence products cannot be licensed through RealPresence Platform Director but can be monitored along with other virtual RealPresence products. To add an existing instance of a prior product version to RealPresence Platform Director:» Follow the instructions in this guide to add an existing instance in RealPresence Platform Director. Then set up monitoring for the instance as needed. Polycom, Inc. 29

30 Create a New Instance and Migrate Data from a Prior Version You can create a new instance of a RealPresence product that is compatible with RealPresence Platform Director and then migrate data from the existing instance into the upgrade instance of the product. Review the Administrator s Guide for the product to find out whether a migration of this type is supported. Complete the following tasks to create a new product instance and migrate data from a previous version: 1 Upgrade the product instance according to the upgrade instructions provided with the software download or in the Administrator s Guide for that product. 2 Add the instance to the system, following the instructions to add an existing instance in RealPresence Platform Director. 3 Allocate counted capabilities to the new component product. Follow the procedure for allocating licenses for new system components. After counted capabilities have been allocated to the new RealPresence system component, the instance can begin operating in the RealPresence Platform Director environment. Polycom, Inc. 30

31 Manage and Configure the RealPresence Platform Director Environment RealPresence Platform Director operates within a vcenter or supported virtual server that manages a vsphere environment containing the Polycom RealPresence video system infrastructure. Within the vsphere environment, RealPresence Platform Director can create, deploy, manage, and monitor new instances and monitor existing virtual instances and hardware instances of RealPresence product components. This versatility enables an administrator to manage all Polycom RealPresence products in one place. Manage Providers The Provider imparts the information required to access a vcenter, and RealPresence Platform Director works with it to create, manage, and monitor virtual RealPresence instances. If you are using vcenter to manage RealPresence virtual software editions, the RealPresence Platform Director environment must include at least one provider. Add a Provider The Provider includes a URL for the VMware Data Center and user account credentials required to create new instances and manage existing ones. To add a Provider in the RealPresence Platform Director configuration: 1 Log in to the RealPresence Platform Director interface as an administrator or equivalent super-user with administrator privileges. 2 From the RealPresence Platform Director Administrator menu, go to SYSTEM > Providers to display the PROVIDERS page. 3 Click + PROVIDER to open the Add a Provider page. 4 Enter the Provider details as outlined in the following table. Provider Details descriptions Field Name Provider Type URL Value/Description A unique name (80 characters maximum) for the Provider. Select VMware. Only VMware is supported. The URL for the vcenter server. The syntax for a VMware provider URL is as follows: address of data center>/sdk In place of the IP address, you can use the fully qualified domain name (FQDN) for the vcenter. Polycom, Inc. 31

32 Field Username Password Ignore Certificate Value/Description The username, with full access rights, for accessing the VMware vcenter. See the appendix to this Administrator Guide for a detailed description of required vcenter access rights. The password for the user. Select Yes to ignore certificate validation when accessing the vcenter. Adding certificate trust chains to RealPresence Platform Director for your vcenter certificate is highly recommended; however, you may choose to ignore certificate validation to establish communications with the vcenter. 5 Click ADD to add the Provider. Edit Provider Details You can edit the Provider details and view current and past alarms in the Provider page. For more information about alarms, see View Alarms. To edit Provider details: 1 From the RealPresence Platform Director Administrator menu, go to SYSTEM > Providers to open the PROVIDERS page. 2 Click next to the name of the provider whose details you want to edit. 3 On the Provider Details tab, edit the provider information in the applicable text fields. See Add a Provider for definitions of each available field. 4 When you have finished editing applicable details for the provider, do one of the following: Click UPDATE to accept all of the new field values, or Click RESET to return to the previous field values. Caution: Updating details Clicking the UPDATE button makes changes permanent. After you have updated details, you cannot use the RESET button to revert to the original values. Delete a Provider You can delete a provider when it is no longer applicable to your RealPresence Platform Director configuration. A RealPresence Platform Director system within a vcenter requires at least one provider. To delete a Provider:» Click next to the provider you want to delete, and follow the instructions in the confirmation dialog. Polycom, Inc. 32

33 Manage Zones A zone is a RealPresence Platform Director concept that encompasses a time zone, one or more Network Time Protocol (NTP) servers, and a collection of resource groups that help you configure and manage your Polycom video collaboration environment. RealPresence Platform Director associates each virtual machine instance that it manages with a zone. New instances in the zone are configured to use the NTP servers that have been defined for that zone. See Manage Resource Groups for more information on how to configure and work with resource groups in a RealPresence collaboration environment. Note: Configuring NTP servers in your RealPresence environment While RealPresence Platform Director allows for the use of many NTP servers in a Polycom RealPresence environment, most of the subcomponents at this time support only two NTP servers. Because of this limitation, we recommend referencing no more than two separate NTP servers within your Polycom RealPresence system. Add a Zone Each RealPresence Platform Director system must contain at least one zone. To add a zone: 1 From the RealPresence Platform Director Administrator menu, click SYSTEM > Zones to open a list of current zones. 2 Click + ZONE to display the Add a New Zone dialog. 3 Enter the zone details, as outlined in the following table. Zone Details Configuration Field Name Description Time Zone NTP Server Value/Description Enter a name (80 or fewer characters) for the zone. Enter a brief description (100 or fewer characters) for this zone. Choose a default time zone for this RealPresence Platform Director zone. Enter one or more NTP servers to synchronize time between RealPresence instances in this zone. 4 Click ADD to add the new zone to the RealPresence Platform Director system. 5 Follow the prompt in the alert that directs you to add a resource group to the zone, as shown next. Polycom, Inc. 33

34 6 Do one of the following: Click ADD RESOURCE GROUP to open the Add a new resource group page (see Resource Groups). A resource group is necessary only if you are using vcenter. Instances running on an EXSi host do not require a resource group. Click ADD LATER to display a list of available zones. Edit Zone Details From the zone editing page, you can edit details, edit current and past alarms, and add or edit resource groups. Note: Updating the time zone and NTP server list Updating the time zone and NTP server list applies to newly created instances but does not modify those settings for existing instances. To edit details for an existing zone: 1 From the RealPresence Platform Director Administrator menu, click SYSTEM > Zones to open a list of zones available in your system. 2 Click next to the zone you want to edit. 3 Click the Details tab, and then update the Name, Description, Time Zone, or NTP Server fields. 4 When you have finished editing, do one of the following: Click UPDATE to accept all of the new field values, or Click RESET to return to the previous field values. Caution: Updating details Clicking UPDATE makes changes permanent. After you click UPDATE to change the details for a zone, you cannot click the RESET button to revert to the original field values. Delete a Zone Delete a zone when it is no longer applicable in the RealPresence Platform Director system configuration. Polycom, Inc. 34

35 To delete a zone: 1 Click next to the zone to be deleted. 2 Click DELETE to remove the zone from the RealPresence Platform Director configuration. Manage Resource Groups A resource group is another logical grouping of virtual resources that you can use to more effectively manage your virtual environment. As an example, you may want to allocate all of your compute- and memory-intensive instances to be deployed to particular clusters or hosts in your virtual environment because those hosts have ample capacity to support those needs. You can create one or more resource groups to encompass those resources and then monitor them separately to ensure appropriate capacity and performance. Resource Groups are required only in vcenter environments. Add a Resource Group to a Zone A resource group operates within a zone in a RealPresence Platform Director system. You can add a resource group to any defined zone. To add a resource group to a zone: 1 From the RealPresence Platform Director Administrator menu, go to SYSTEM > Zones. 2 Click next to the appropriate zone, and then select the Resource Groups tab. 3 Click + RESOURCE GROUP to open the Add a new resource group page. 4 Enter a unique Name and select a Provider for the resource group. 5 In the Computer Resource section, select a Data Center, Host/Cluster, and optional Resource Pool from the lists of those available. After you have made a selection in the Host/Cluster drop-down list, the + STORAGE and + NETWORK buttons appear. 6 Click + STORAGE to open the Add Storage Resources dialog showing a list of available storage resources and the amount of space available on each. A sample dialog is shown next. Polycom, Inc. 35

36 7 Select a checkbox to use one or more storage resources, and then click ADD. To select all resource options in the list, click the checkbox at the top of the column. 8 Click + NETWORK to open the Add Network Resources dialog showing a list of available virtual networks. 9 Select one or more of the available network resources, and then click ADD. To add all resource options in the list, select the checkbox at the top of the column. 10 From the Default Network drop-down list, select a default network. You can select a default network only after you have chosen at least one network resource. 11 Enter a value in the Inventory Path text field. The system adds a value based on the criteria you have selected. You can keep this value or enter a new value. The path you enter in this field must exist in the vcenter and contain the name of the data center, followed by /vm. If the data center has folders, a folder path can be appended to the end of the inventory path value. New virtual instances will be deployed to the last folder in the path. For example, in the inventory path named NewYorkDataCenter/vm/[folder1]/[subfolder], new virtual machines will be deployed to [subfolder] within the data center called NewYorkDataCenter. 12 Click CREATE to add the new resource group to the system. After you have created a resource group, you can begin adding supported versions of RealPresence product instances to your RealPresence Platform Director system. Edit a Resource Group As your organization s capacity needs grow, or when you need to take a host out of service for maintenance, you may need to add or remove resources from a defined resource group. To edit a resource group: 1 From the RealPresence Platform Director Administrator menu, go to SYSTEM > Zones. 2 Click next to the appropriate zone, and then select the Resource Groups tab. Then click next to the resource group you want to edit. 3 Click on the Details tab to edit the resource group details or threshold percentages, as follows. On the Details tab, you can edit the resource group details including the name, storage resource, network resource, or default network. Other detail options are not editable. For more information, see Resource Groups. On the Threshold tab, you can edit threshold values for this resource group and choose whether or not to enable alarms for threshold values including CPU utilization, storage, and memory. View Resource Group Status You can view the status of any resource group in your RealPresence Platform Director environment. To view the status of a resource group: 1 From the RealPresence Platform Director Administrator menu in RealPresence Platform Director, go to SYSTEM > Zones. Polycom, Inc. 36

37 2 Click next to the appropriate zone, and then select the Resource Groups tab. 3 Click next to the Resource Group you want to view. Then select the Status tab on the Resource Groups page. After the system initializes, the Status page displays usage information, as shown in the following example. If you view the status before any data has been collected, the system reports status as in progress. Resource Group status 4 Do any of the following: Click the CPU, Memory, or Storage or other available rows to the left of the graph to change the monitoring information being displayed. At the bottom of the screen, select a time period between one day and 18 months for which you want to view data. Click STOP to stop monitoring the resource group data. Click START to start or resume monitoring data for the resource group. Delete a Resource Group You can delete a resource group that is no longer relevant to your RealPresence Platform Director system. To delete a resource group: 1 From the RealPresence Platform Director Administrator menu, go to SYSTEM > Zones. 2 Click next to the appropriate zone, and then select the Resource Groups tab. 3 Click next to the resource group you want to delete, and follow the prompts to complete the deletion. Polycom, Inc. 37

38 A resource group can be deleted only if no instance is associated with it. Manage Virtual Edition Images RealPresence Platform Director creates, manages, and monitors RealPresence Platform and RealPresence CloudAXIS component images. These Virtual Edition images must be loaded into your RealPresence Platform Director environment using the RealPresence Platform Director administrator interface. This section describes how to upload an image for a compatible RealPresence Platform component product. Note: Download the *.OVA file from the Polycom Support Site Before you can add an image to a RealPresence Platform Director system you must download the appropriate *.OVA file from the Polycom Support Site and save it to your local system. Add a Component Virtual Edition Image RealPresence Platform Director can create new virtual machine instances that run RealPresence Platform and RealPresence CloudAXIS Suite components. You must add compatible versions of these component images within the RealPresence Platform Director administrator interface to enable the creation of virtual machine components. Before adding an image in RealPresence Platform Director, download a compatible *.OVA file from the Polycom support web site. Store it on a local drive until you are ready to upload the image into RealPresence Platform Director. You can upload Virtual Edition images to RealPresence Platform Director from an FTP server or other storage device that is accessible as a URL. Note: Browser requirements for uploading *.OVA image files Use a Chrome or Firefox browser to upload *.OVA image files. The file upload APIs in Internet Explorer are not fully supported for the current RealPresence Platform Director software release. To add a component virtual edition image to the RealPresence Platform Director system: 1 From the RealPresence Platform Director Administrator menu, select SYSTEM > Image Repository to open a list of available images. 2 Click + IMAGE to open an Add a new Image page. 3 Enter or select values in text and drop down lists as outlined in the following table. Polycom, Inc. 38

39 Add a New Image Details Field Instance Type Value/Description From the dropdown list, select the Polycom RealPresence component product that represents the image being uploaded. Choose File (*.ova) Click to browse to the *.OVA file you want to use. Then click Open. Name Version Credentials Enter a unique name for the image. The version number is automatically populated based on the name of the image file but can be entered manually if necessary. The version of the RealPresence component must be compatible with the RealPresence Platform Director version running in your environment. Select the default credentials (recommended), or select Custom and enter the proper credentials for the system and application users. Custom credentials are not necessary for any products currently supported in the RealPresence Platform Director release. Configuration of virtual machine instances fails in RealPresence Platform Director if credentials are incorrect. 4 Click UPLOAD to begin uploading the image into your RealPresence Platform Director system. Depending on the speed of your network connection and the size of the image file, the upload can take several minutes to an hour or more. Caution: Upload only one image at a time. Wait until the image upload is complete before you begin another upload. Do not log out of RealPresence Platform Director or close the browser while the image is uploading; otherwise, the upload fails, and you must delete the image and upload it again. Edit Image Values You can edit any of the system values associated with an image. To edit image values: 1 From the RealPresence Platform Director Administrator menu, select SYSTEM > Image Repository to open a list of available images. 2 Click next to the image to be edited to display the details for the image. 3 Click in the appropriate text box, or use the drop-down menu to edit the Instance Type, Name, Version, or Credentials for the image. All are required. 4 When you have finished editing the image information, do one of the following: Click UPDATE to accept the new field values, or Click RESET to return to the previous field values. Polycom, Inc. 39

40 Delete an Image Delete an image when it is no longer required in your RealPresence Platform Director system. Note: Deleting images An image can be deleted only if RealPresence Platform Director contains no instances created from it. So long as RealPresence Platform Director contains an instance, the associated image must remain in place. To delete an image: 1 From the RealPresence Platform Director Administrator menu, select SYSTEM > Image Repository to open a list of available images. 2 Click next to the Image to be deleted. 3 Click YES in the Delete Image confirmation dialog to delete the image. Manage Instances An instance is a Virtual Edition of a component system that runs on a virtual machine or a hardware appliance and becomes part of the Polycom RealPresence video infrastructure. RealPresence Platform Director can do the following: Create, manage, and monitor new virtual machine instances; Manage previously deployed virtual machine instances for supported versions of component products; and Monitor but not manage appliances and older versions of components running on virtual machines. You can create and add instances using the Instances selection on the SERVICE menu. Appliance instances are indicated with a hardware icon next to the instance name. Refer to Supported RealPresence Virtual Editions in this Guide for a list of Polycom products supported in this version of RealPresence Platform Director. The INSTANCES screen shows all instances installed within the RealPresence Platform Director system. You can filter the instance list to show available instances of specific component systems. Use the Type menu to filter the list to display the types of instances you want to view. To filter the instance list: 1 Click on Type: ALL INSTANCES. 2 From the drop-down list, select the type of instance you want to display. Create a New Virtual Instance The first time you add an instance for a RealPresence Platform Director component, you configure the network settings for the instance, including the IP address, subnet mask, and gateway to allow users to access the instances on your network. You can also choose to assign those network settings using DHCP. Polycom, Inc. 40

41 Troubleshooting: Instance not properly created. Creation of a new virtual instance can fail for a variety of reasons, including incorrect application credentials entered for the provider or insufficient resources (disk space or memory) on the host/cluster where the instance is being created. If a new instance fails to be correctly created and enters an Error state, delete the instance from both the RealPresence Platform Director and the Host/Cluster where the instance was targeted. Resolve the issue before attempting to add the instance again. When you add a new instance using static IP settings, have available the following information: The IP address (IP version 4), subnet mask, and gateway for the component system. The time zone in which you want to run the new instance. Note: Making network changes after an instance has been created The network settings and time zone options are available only when a new virtual instance is being created. To revise network settings after the instance has been created, log in to the Administrator interface for the individual system component, and follow instructions for changing settings as outlined in that product s Administrator s Guide. The RealPresence Platform Director must have at least one defined zone into which you place a new instance. Follow the instructions to Add a Zone if necessary before creating a new virtual instance. To create a new virtual instance for a Polycom RealPresence system component: 1 From the RealPresence Platform Director Administrator menu, go to SERVICE > Instances. 2 On the Instances screen, click + INSTANCE, and then select Create New Virtual Instance to open the Create New Virtual Instance page. 3 Complete the information in text and drop-down lists, as outlined in the following table. Create New Virtual Instance Page Field Name Instance Type Image Zone Resource Group Customize Network & Storage Service Group Value/Description Enter a unique name (80 characters maximum) for the instance. Select the appropriate RealPresence component type from the drop-down list. Select an available image from those listed in the drop-down list. Select a zone in which the instance will operate. Select a resource group from those defined in your RealPresence Platform Director environment for the selected zone. Select the checkbox to choose from available storage and network devices. (Optional) Select a Service Group for the instance. Polycom, Inc. 41

42 Field Network Settings Value/Description Select one of the two options for assigning an IP address to the instance: Use Static IP Use DHCP* *Because some of the system component instances rely on an IP address that remains constant, Polycom highly recommends that if you use DHCP to allocate addresses for RealPresence components, you also reserve a DHCP IP address on your DHCP server for the MAC address of the system component. Static IP Subnet Mask Gateway Time Zone Enter the IP address for the instance if you opted to use a static IP address. Enter the subnet mask for the IP address. Enter the IP address of the default gateway. Select the time zone for the instance. If a time zone is not specified, the instance inherits the time zone that has been configured for the selected zone in RealPresence Platform Director. 4 Click CREATE to create the new virtual instance in your RealPresence Platform Director environment. The system displays a list of instances being managed or monitored by the RealPresence Platform Director. Depending on the size of the component image and the speed of the network, creating a new virtual instance can take as long as 90 minutes. View the status field for the new instance to determine the current status: Creating, Powering On, Running, or Configuring. 5 After the instance has been created, open the main Administrator menu, and then go to SERVICE > Instances to view the list of instances currently running in your RealPresence Platform Director environment. Look for the instance you created to verify that it is running. 6 After a new instance of DMA, RPRM, RPAD, or Collaboration server has been created, log in to the instance and enable SNMP so that RealPresence Platform Director can monitor it. Follow the instructions for enabling SNMP in the Administrator or Getting Started Guide for that product. 7 Then follow the instructions to allocate licenses to the instance. Add an Existing Virtual Instance Supported virtual editions of existing RealPresence products can be added to the RealPresence Platform Director system for licensing, provisioning, and monitoring. Older product versions can be added to the RealPresence Platform Director system for monitoring only. See the list of supported RealPresence Platform editions to determine which current and prior versions of component products are supported with RealPresence Platform Director. You can use this procedure to add an existing virtual instance to your RealPresence Platform Director system in the following circumstances: To add an older version of a RealPresence system component already running in your virtual data center. Polycom, Inc. 42

43 To add an instance that has been previously created in and then removed from RealPresence Platform Director but not removed from your virtual data center. To add an instance that has been deployed through your virtual data center, rather than through RealPresence Platform Director. Caution: Verify that the IP address is valid for the instance being added. When adding an existing virtual instance to RealPresence Platform Director, verify that the selected IP address matches the IP address configured for the RealPresence virtual instance. Selecting an incorrect IP address for a RealPresence instance will result in the inability to allocate available feature licenses to the instance. To add an existing virtual instance to the RealPresence Platform Director environment: 1 From the RealPresence Platform Director Administrator menu, go to SERVICE > Instances. 2 On the Instances page, click + INSTANCE, and then select Add Existing Virtual Instance. 3 In the Add Existing Virtual Instance page, select the appropriate information from the drop-down menus, as outlined in the following tables. Add Existing Virtual Instance Field Instance Type Image Version Zone Value/Description From the drop-down list, select the Polycom RealPresence component that is running on the existing virtual machine. Enter the software version for the image. The image version is automatically populated from the name of the *.OVA file. To ensure that the version number correctly reflects the version of the software being installed, retain the original file names of all downloaded *.OVA files. Select an available zone from the drop-down list. Use Existing Resource Group (Not Selected) Field Provider Data Center Host / Cluster Resource pool Instance Service Group Value/Description Select the Provider configured for your data center. Select a data center from those available. Select the IP address or name of the Host or Cluster you want to use. (Optional) Select a resource pool. This drop-down list can be selected only if resource pools have been defined for the selected Host/Cluster and if the Host/Cluster for the virtual data center is accessible. Select an instance from the list of available instances in the drop-down list. (Optional) Select a Service Group for the instance. Polycom, Inc. 43

44 Field Application Admin Username Application Admin Password Value/Description Type the instance admin username for the application user interface. The default is usually admin. Type the admin password for the instance application user interface. The credentials must be correct. If the password or username do not match the password and user name set up in the instance, RealPresence Platform Director cannot manage it. Use Existing Resource Group (Selected) Field Resource group Instance Service Group Value/Description Select the resource group for the existing instance. Select an instance from the list of available instances in the drop-down list. (Optional) Select a Service Group for the instance. 4 Click ADD to add the instance to the RealPresence Platform Director system. Adding, configuring, and licensing an existing instance can take five to fifteen minutes. 5 After the instance has been added, go to SERVICE > Instances on the main Administrator menu to view the list of instances currently running in the RealPresence Platform Director environment. Verify that the instance you added is running. Next, you can begin allocating features for the added instance. See Allocate Licenses for Polycom RealPresence System Components. Add an Existing Appliance Instance You can add any supported Polycom RealPresence appliance to your RealPresence Platform Director system for monitoring and management. Note: Enable SNMP before adding an appliance instance Until SNMP is enabled on an appliance instance, that instance will be reported in RealPresence Platform Director as unreachable. As a result, Polycom recommends that SNMP be enabled in any appliance instance before it is added to RealPresence Platform Director. To add an existing appliance instance: 1 From the RealPresence Platform Director Administrator menu, go to SERVICE > Instances. 2 On the Instances screen, click + INSTANCE and select Add Existing Appliance Instance. 3 Add the hardware instance information in the dropdown and text boxes, as outlined in the following table. Polycom, Inc. 44

45 Add Existing Appliance Instance Field Name Instance Type Image Version Zone IP Address Service Group Value/Description Type a descriptive name (80 or fewer characters) for the appliance instance. From the dropdown menu, select the RealPresence component that is running on the appliance. Enter the version number of the RealPresence component that is running on the appliance. Select the zone in which the instance will operate. Enter the IP address of the appliance. (Optional) Select a Service Group for the instance. 4 Click ADD to add the instance to the RealPresence Platform Director system. 5 Go to SERVICE > Instances to verify that the appliance you added has been added. A successfully added new hardware instance should appear in the list of instances with next to the instance name. Add an Existing (Non-vCenter) Instance You can add an instance of a RealPresence component product deployed in a supported virtual environment that does not include vcenter. You can also add an instance that has been deployed in a vcenter to which you may not have administrator privileges. Adding an instance in this way allows RealPresence Platform Director to manage and license the RealPresence instance outside the vcenter management platform. Before you add an instance in this way, verify that it is running and accessible from its own user interface. An instance that is not in a running state will not function correctly when added to the RealPresence Platform Director. To add an existing (non-vcenter) instance to RealPresence Platform Director: 1 From the RealPresence Platform Director Administrator menu, go to SERVICE > Instances. 2 On the Instances screen, click + INSTANCE and select Add Existing Virtual (Non-vCenter). 3 Add the instance information in the dropdown and text boxes, as outlined in the following table. Add Existing Virtual Instance (Non-vCenter) Field Name Instance Type Image Version Value/Description Type a descriptive name (80 or fewer characters) for the appliance instance. From the dropdown menu, select the RealPresence component that is running on the appliance. Enter the version number of the RealPresence component that is running on the appliance. Polycom, Inc. 45

46 Field Zone IP Address Service Group Application Admin Username Application Admin Password Value/Description Select the zone in which the instance will operate. Enter the IP address of the virtual machine. (Optional) Select a Service Group for the instance. Type the instance admin username for the application user interface. The default is usually admin. Type the admin password for the instance application user interface. The credentials must be correct. If the password or username do not match the password and user name set up in the instance, RealPresence Platform Director cannot manage it. 4 Click ADD to add the instance to the RealPresence Platform Director system. Adding, configuring, and licensing an existing instance can take five to fifteen minutes. 5 After the instance has been added, go to SERVICE > Instances on the main administrator menu to view the list of instances currently running in the RealPresence Platform Director environment. Verify that the instance you added is running. Next, you can begin allocating features for the added instance. See Allocate Licenses for Polycom RealPresence System Components. View or Edit Instance Details An instance is any Polycom RealPresence virtual machine or Polycom hardware appliance running in a RealPresence Platform Director environment. From the Instances menu, you can view information about any instance, including system, error, and network information. You can also view or edit application credentials, SNMP settings, and alarm thresholds from this page. To view or edit instance details: 1 From the RealPresence Platform Director Administrator menu, go to SERVICE > Instances. 2 On the INSTANCES page, click the next to the instance that you want to view or edit. 3 Click the Details tab, and then do one or more of the following: Select Details to view or edit detailed information about the instance. Select Credentials to view or edit the Admin user name for the instance or to change the Admin Username or password. Polycom recommends consulting a member of our support team before editing these fields. Select SNMP to view or edit the monitoring configuration for the instance. Select Threshold to view or edit threshold values or enable alarms for resources that are available for monitoring. 4 If you edit information on any of the four pages listed previously, do one of the following: Click UPDATE to save the new settings, or Polycom, Inc. 46

47 Click RESET TO DEFAULT to restore default settings. You must click UPDATE to save settings on a page before opening another page. If you move to another page without clicking UPDATE, the new values will not be saved. Delete an Instance You can delete an instance when it is no longer applicable to your RealPresence Platform Director configuration. When you delete an instance from the RealPresence Platform Director environment, its licenses are automatically allocated back to the pool of available licenses for the system. Note: Power-off an instance before deleting it. Only instances that have been powered off can be deleted from the vcenter. To delete an instance: 1 From the RealPresence Platform Director Administrator menu, go to SERVICE > Instances. 2 On the Instances page, click next to the instance you want to delete. A dialog prompts you to confirm the deletion from MyProvider, where MyProvider is the name of the RealPresence Platform Director Provider that is used to access the vcenter or host system where the Virtual Machine exists. If you select Delete instance from MyProvider, a confirmation dialog appears. After you confirm the deletion, the instance is deleted from the RealPresence Platform Director system and the virtual machine is deleted from the vcenter host. If you do not select Delete instance from MyProvider, the instance is removed from the RealPresence Platform Director system, but the virtual machine remains available within the host system or vcenter. When deleting a CloudAXIS Services Portal instance, RealPresence Platform Director attempts to revert the Services Portal license configuration back to its original default setting. Manage Service Groups A Service Group is a logical collection of hardware appliances and/or virtual machine instances that can be a combination of such as RealPresence Collaboration Server, CloudAXIS Service Portal and CloudAXIS Experience Portal, DMA, and others. The instances in a Service Group are typically configured to work together to provide video collaboration services to the users of various Polycom audio and video collaboration systems in your organization s locales. A Service Group could represent a service provider creating a group that serves a particular enterprise, one campus of an enterprise, a division or geographical locale within a company, or any other group recognized by your organization. With these related instances placed in a logical group, they can be monitored as a unit and measured to determine usage statistics. With a Service Group, you can manage and monitor multiple types of instances on a single window and view a graphical representation of their usage. Polycom, Inc. 47

48 Caution: Assign only related instances to a common service group. Include in a service group only virtual and appliance instances that are configured to work together in service of the same RealPresence system, for example Collaboration Servers and DMA systems. Unrelated sets of instances added into a service group may create invalid monitoring data, or may fail to produce data that is useful in the management of your video collaboration environment. Create a Service Group Create a service group to designate appliance and virtual instances that together provide a distinct service within your organization. To add a new service group to the RealPresence Platform Director system: 1 From the RealPresence Platform Director Administrator menu, go to SERVICE > Service Group to display a list of available service groups. 2 Click + SERVICE GROUP to display the Add New Service Group screen. 3 Enter a Name and Description for the new service group. 4 Click ADD to add the new service group to the list. After the new service group has been added to the system, you can add the virtual product editions and appliance instances that will operate within it. View or Edit Service Group Details You can edit the name and/or description of an existing service group or view details related to it. To view or edit service group details: 1 From the RealPresence Platform Director Administrator menu, go to SERVICE > Service Group to display a list of available service groups. 2 Click next to the Service Group you want to edit. 3 Select the Details tab, and then click the Details row on the left of the screen to open the Service Group details window. 4 Update the Name and Description fields as necessary. 5 When you have finished editing the Service Group, do one of the following: Click UPDATE to accept all of your new field values, or Click RESET to return to all of your previous field values. Caution: Updating Service Group details Clicking UPDATE makes the change permanent. After you have updated Service Group details, you cannot use the RESET button to revert to the original field values.. Polycom, Inc. 48

49 Add a New Instance to a Service Group You can add a new instance to RealPresence Platform Director through the service group you want it to associate it with. NOTE: A Service Group must contain a DMA or MCU instance. A Service Group must contain either a DMA or MCU instance to be shown on the RealPresence Platform Director dashboard. To add a new Instance to a Service Group: 1 From the RealPresence Platform Director Administrator menu, go to SERVICE > Service Group to display the SERVICE GROUPS page. 2 Click next to the Service Group to which you want to add the instance. 3 Select the Instances tab to display a list of available instances. 4 Click + INSTANCE to display a menu of options from which to add the instance. Select one of the following options, and then follow the instructions to add the instance to the existing service group. From Common Pool Select an available instance from the Add to Service Group dialog. Create New Virtual Instance Follow the instructions to Create a New Virtual Instance from an existing image. Add Existing Virtual Instance Follow the instructions to Add an Existing Virtual Instance to the Service Group. Add Existing Virtual Instance (non-vcenter) Follow the instructions to Add an Existing (Non-vCenter) Instance. Add Existing Appliance Instance Follow the instructions to Add an Existing Appliance Instance to the Service Group. 5 Click ADD to add the instance to the selected Service Group. The name of the instance now appears in the list of instances for that Service Group. Remove an Instance from a Service Group You can remove an instance from a service group at any time. Note that the instance remains available in RealPresence Platform Director after being removed from a service group. To remove an instance from a service group:» Select the check box next to the instance you want to remove from the service group, and then click REMOVE. Polycom, Inc. 49

50 Manage RealPresence Product Licenses RealPresence Platform Director manages licenses for Virtual Editions of all RealPresence system components. For the following products, you must use RealPresence Platform Director to manage licenses. RealPresence DMA RealPresence Resource Manager RealPresence Collaboration Server RealPresence Access Director RealPresence CloudAXIS Services Portal and Experience Portal If you have RealPresence CloudAXIS Services Portal and Experience Portal in your system, you can run those instances one of two ways. By installing the instances outside RealPresence Platform Director and manage licenses using the existing license management process, or By adding CloudAXIS instances to your RealPresence Platform Director system to manage them. See the CloudAXIS Administrator Guide for instructions on how to associate the Services Portal and Experience Portal and to set up licensing for those two products within RealPresence Platform Director. Note: License allocation not fully supported for CSS at this time Licenses features for Content Sharing Server (Base License for RealPresence ; Content Sharing Suite and CSS ; High Availability) are displayed on the License Management page as uncounted licenses when you select the Allocate by view. The license count shows 0 Instances regardless of how many CSS instances are available. RealPresence Platform Director does not display maximum concurrent calls available (Max Number Recorded Calls for Content Sharing Suite ), regardless of whether your organization has purchased a license for those calls. Online and Offline Mode Licenses for Polycom RealPresence system components can be managed in online or offline mode. If the data center where the RealPresence Platform Director system is located has connectivity to the Internet, you must use online mode to manage licenses. If the data center does not have Internet connectivity, you can manage the RealPresence system components in offline mode. The RealPresence Platform Director system also monitors usage of allocated licenses for supported RealPresence virtual instances. See View System Resource and License Usage for instructions on how to view data related to licensed and allocated features for RealPresence product instances. Polycom, Inc. 50

51 Allocate Licenses for Polycom RealPresence System Components After setting up the license server and activating RealPresence system licenses within RealPresence Platform Director, you can begin to allocate licenses for individual components of your RealPresence system. All license allocations for individual RealPresence products are managed through the RealPresence Platform Director Administrator menu. A system component must be online, active, and running within the RealPresence Platform Director system before licenses can be successfully allocated to it. In addition, the credentials for the system user configured for the component within RealPresence Platform Director must match the credentials for the system user as configured within the component system. Troubleshooting: License allocation errors for a newly added RealPresence instance If a license allocation fails for a newly added Polycom RealPresence virtual instance, verify that the IP address configured in RealPresence Platform Director is the address assigned to the virtual instance to which you are attempting to allocate licenses. A feature license allocation will fail if the IP address selected for a virtual instance does not match the instance type to which features are allocated. To allocate licenses to a RealPresence system component: 1 From the main menu in RealPresence Platform Director, go to LICENSE MANAGEMENT > Allocation to view a summary of licenses available for allocation within your RealPresence system. 2 Do one of the following: Select Allocate By: TYPE to view only those product instances that you have configured RealPresence Platform Director to use. When you select a product instance, both counted and uncounted features are viewable, and you can allocate features to a specific device. Select Allocate By: FEATURE to view a list of licensable features and capabilities, such as concurrent calls, regardless of whether they are associated with a product instance. When you click on the license feature, you can view all of the product instances that have that license feature. Then you can allocate the feature to a specific product instance. 3 Select the product for which you want to allocate new licenses. A status window opens on the right, showing details for the licensing associated with the selected product, including status, claimed and available features, and other capabilities, as shown next. Polycom, Inc. 51

52 License feature allocation details 4 Click in the spin box at the right of the screen, shown next. Then click the up arrow or type a number to indicate the number of feature licenses you want to claim for the product. Allocate feature licenses 5 Click SAVE to save the new license feature allocation settings. After allocating the new licenses, you can go to the license settings page within the specific product you have just licensed to verify that the new licenses have been made available to the product. See the Administrator Guide for your product for instructions on how to view licensing information. Polycom, Inc. 52

53 NOTE: Reboot SMCU and RealPresence Access Director after allocating licenses. For Polycom SMCU and RealPresence Access Director products, license allocation changes take effect only after those systems have been rebooted. After either of these products has been installed, RealPresence Platform Director generates an alarm indicating that they must be rebooted. Polycom, Inc. 53

54 Monitor the RealPresence Platform Director Environment SNMP Description RealPresence Platform Director uses the SNMP application-layer protocol to monitor instances of Polycom RealPresence products that support SNMP monitoring. An instance must be in a Running state with SNMP enabled to be monitored in RealPresence Platform Director. SNMP Framework The SNMP framework has three parts: The SNMP manager is the system used to control and monitor the activities of network hosts using SNMP. A variety of network management applications are available for use with SNMP. It is important to note that you should understand how your SNMP management system is configured to properly configure your Polycom system SNMP transport protocol requirements, SNMP version requirements, SNMP authentication requirements, and SNMP privacy requirements. For information on using SNMP management systems, see the appropriate documentation for your application. The SNMP agent is the software component within the Polycom system that maintains the data for the system and reports these data, as needed, to managing systems. The agent and Management Information Base (MIB) reside on the same system. The Management Information Base (MIB) is a virtual information storage area for network management information, which consists of collections of managed network objects. You can configure the SNMP agent for a particular system MIB. The agent gathers data from the MIB, the repository for information about system parameters and network data. Polycom systems include Polycom-specific MIBs with every system as well as third-party MIBs. Polycom MIBs are selfdocumenting, including information about the purpose of specific traps and inform notifications. Third-party MIBs accessible through the Polycom system may include both hardware and software system MIBs. Polycom s Use of SNMP Polycom supports two versions of SNMP: SNMPv2c Polycom implements SNMPv2c, a sub-version of SNMPv2, which uses a communitybased form of security. The community of SNMP managers able to access the agent MIB is defined by an IP-based Access Control List and password. Because SNMPv2c does not encrypt communications between the management system and SNMP agents, it is subject to packet sniffing of the clear text community string from the network traffic. Polycom, Inc. 54

55 SNMPv3 Polycom implements the newest version of SNMP, whose primary feature is enhanced security. SNMPv3 provides secure access to systems with a combination of authenticating and encrypting packets over the network. The contextengineid in SNMPv3 uniquely identifies each SNMP entity and is used to generate the key for authenticated messages. Polycom implements SNMPv3 communication with authentication and privacy. Authentication is used to ensure that traps are read by only the intended recipient. As messages are created, they are given a special key that is based on the contextengineid of the entity. The key is shared with the intended recipient and used to receive the message. Privacy encrypts the SNMP message to ensure that it cannot be read by unauthorized users. Message integrity ensures that a packet has not been tampered with in transit. SNMP Notifications A key feature of SNMP is the ability to generate notifications from an SNMP agent. Notifications are sent, unsolicited and asynchronous, to the SNMP manager from the Polycom system. Notifications can indicate improper user authentication, restarts, the closing of a connection, loss of connection to another system, or other significant events. They are generated as informs or trap requests. Traps are messages alerting the SNMP manager to a system or network condition change. Inform requests (informs) are traps that include a request for a confirmation receipt from the SNMP manager. Traps are less reliable than informs because the SNMP manager does not send any acknowledgment when it receives a trap. However, informs consume more system and network resources. Traps are discarded as soon as they are sent. An inform request is held in memory until a response is received or the request times out. Traps are sent only once, while informs may be retried several times. The retries increase traffic and contribute to a higher overhead on the network. Thus, traps and inform requests provide a trade-off between reliability and network resources. Set Up System Monitoring In addition to managing RealPresence Platform component instances, RealPresence Platform Director also monitors the system health of those instances. The MONITORING page allows you to view the state of RealPresence Platform Director alarms and configure alarm thresholds. First, you must set default values for SNMP settings. To set values for system monitoring: 1 From the RealPresence Platform Director Administrator menu, select SETTINGS > Application Settings. Then click MONITORING. 2 Enter values in the text boxes on the SNMP Settings page as outlined in the following table. Monitoring Settings Page Field Retry count Value/Description Enter the number of times to automatically monitor your Instances between timeouts. Valid values are 2 to 5. The default is 2. Polycom, Inc. 55

56 Field Timeout Scan Interval Value/Description Enter the amount of time (in milliseconds) before the RealPresence Platform Director Portal times out due to inactivity. Valid values are 1000 to The default is Set a higher timeout value if the instances are employed in a different geographical location from the RealPresence Platform Director instance. Enter the periodic time that the Monitoring module can scan for instances to monitor. 3 Click UPDATE to save the new settings. Enable SNMP for an Instance You must enable SNMP on each RealPresence Platform Director Instance that you want to monitor. SNMP settings are set only at the instance level. To edit SNMP settings: 1 From the RealPresence Platform Director Administrator menu, go to SERVICE > Instances. 2 On the INSTANCES screen for the instance you are editing, click. 3 Select the Details tab, and then click SNMP at the left of the screen. 4 Update the SNMP instance monitoring configuration using the guidelines shown in the following table. 5 Select the SNMP version. SNMP can be implemented over one of two transport protocol versions. If you choose v2c, the SNMP version, Transport, Port, and Community fields appear. SNMPv2c is appropriate for standard communication models and uses community-based authentication. If you choose v3, the SNMP version, Transport, Port, Security User, Authentication type, Authentication password, Encryption type, and Encryption password fields appear. SNMPv3c is appropriate for high-security models and requires a security user for notifications. SNMP Instance Monitoring Configuration Field Transport Port Value/Description The transport protocol to be used. RealPresence Platform Director supports only UDP at this time. (Spell out UDP at first instance.) UDP requires fewer network resources and is suited for repetitive, lowpriority functions like alarm monitoring, although message delivery is not assured and does not always occur in the order in which messages are sent. The instance port on which the SNMP agent is running. Polycom, Inc. 56

57 Field Community Security User Authentication type Value/Description The context for the information, or the SNMP group to which the devices and management stations running SNMP belong. This field appears only when SNMPv2c is chosen. The RealPresence Platform Director system contains only one valid context, public, which is identified by the Community name. RealPresence Platform Director does not respond to requests from systems belonging to any other community. For SNMPv3 only. Specifies the security name required to access a monitored MIB object. Specifies the authentication protocol. These protocols are used to create unique fixed-sized message digests of a variable length message. Possible values for authentication protocol are: MD5 Creates a digest of 128 bits (16 bytes). SHA Creates a digest of 160 bits (20 bytes). Both methods include the authentication key with the SNMPv3 packet and then generate a digest of the entire SNMPv3 packet. Authentication password Encryption type For SNMPv3 only. Specifies the authentication password that is appended to the authentication key before it is computed into the MD5 or SHA message digest. For SNMPv3 only. Specifies the privacy protocol for the connection between the RealPresence Platform Director system and the SNMP agent. The RealPresence Access Director system implements communication with authentication and privacy (the authpriv security level as defined in the USM MIB). Possible values for privacy protocol are: No encryption DES Uses a 56-bit key with a 56-bit salt to encrypt the SNMPv3 packet. AES Uses a 128-bit key with a 128-bit salt to encrypt the SNMPv3 packet. Encryption password For SNMPv3 only. Specifies the password to be associated with privacy protocol. 6 When you have finished editing the SNMP values, do one of the following: Click UPDATE to accept all of your new field values, or Click RESET to return to all of your previous field values. Polycom, Inc. 57

58 Alarms Monitored by RealPresence Platform Director You can view the current state of alarms monitored by the RealPresence Platform Director on the ALARMS page. The initial ALARMS screen shows all alarms across Instances, Resource Groups, Service Groups, Zones, and Providers. Note: Troubleshooting undefined failure conditions A RealPresence Platform Director instance may experience various failure conditions when a host or cluster executing RealPresence Platform Director becomes overloaded. If unexplained failure conditions occur in RealPresence Platform Director, check the configuration of the host system or vcenter to determine whether an overloaded host or cluster may be the cause of failures. The Unresolved Alarms box in the upper-right corner of the Alarms window provides a color-coded view of the number and severity of the alarms. The alarm colors correspond to the following threshold levels: Gray System has reached the Warning Value threshold. Yellow System has reached a one-third increase in percentage between the Warning and Critical values. Orange System has reached a two-thirds increase in percentage between the Warning and Critical values. Red System has reached the Critical Value threshold. Alarms included in the RealPresence Platform Director system are outlined in the following table. RealPresence Platform Director Alarm Types Alarm Type Description Corrective Action Configuration Alarm License Change Alarm System Reachability Alarm A problem was detected during the configuration phase that involves either creating a new instance or adding an existing instance. The system has detected a change in licensing status for a product that requires a reboot of the system. A system entity is unreachable by the RealPresence Platform Director. The entity may be a provider, resource group, or an instance that may have been powered off, given a new IP address, or deleted from the vcenter. Typically, this is a problem with the application credentials. Delete the instance from RealPresence Platform Director, and then add it again using the correct credentials. Reboot or restart the affected system. Either delete or power up the entity. Polycom, Inc. 58

59 Alarm Type Description Corrective Action Provider Login Failure Alarm Total CPU Usage Memory Usage Storage Disk Usage Video Ports Usage Voice Ports Usage NW Interface Usage A login failure prevented a connection to the Provider. This may have happened if the system credentials were changed in the affected instance but not in RealPresence Platform Director. Generated when a CPU threshold has been reached. Generated when a memory threshold has been reached. Generated when a disk storage threshold has been reached. Generated when an application threshold for video port usage has been reached. Generated when an application threshold for voice port usage has been reached. Generated when a disk storage threshold has been reached. Add the correct application credentials to the Provider details. Refer to documentation for the entity initiating the alarm. Refer to documentation for the entity initiating the alarm. Refer to documentation for the entity initiating the alarm. Allocate more licenses to the entity. Allocate more licenses to the entity. Refer to documentation for the entity initiating the alarm. View Active Alarms The default view shows all alarms that are active in the system. You can filter the view to show alarms by Instance, Resource Group, Zone, Service Group, or Provider. Selections for viewing alarms are defined in the following table. Alarm Status Selections Field Show Active Acknowledged New Cleared Value/Description Alarms that have occurred that have not been cleared. Both New and Acknowledged alarms are displayed. Marks an alarm as being grayed out on the Show Active alarm; indicates that an admin is aware of the alarm. Alarms that are active but not yet acknowledged. Alarm condition has been resolved. To view active system alarms: 1 From the RealPresence Platform Director Administrator menu, go to MONITORING > Alarms to display a list of current alarms, as shown next. Polycom, Inc. 59

60 RealPresence Platform Director Alarms page 2 Select either Clear or Acknowledge from the Actions menu. 3 Select Show Active, New, Acknowledge, or Cleared to filter the alarms you want to clear or acknowledge. 4 Select the left-pointing arrow at the right to show details about the selected alarms. View Alarms by Entity Type You can view alarms in groups by entity type, including by Instance, Resource Group, Zone, Service Group, or Provider. To view Alarms for any entity: 1 From the RealPresence Platform Director Administrator menu, go to MONITORING > Alarms to display a list of current alarms 2 In the Type drop-down list, select one of the following entity types: Instance View alarms related to RealPresence Platform Director component instances. Resource Group View alarms related to Resource Groups. Zone View alarms related to Zones. Service Group View alarms related to Service Groups. Provider View alarms related to a Provider. 3 Select the status of the alarms you want to show, as follows: Show Active Show all active alarms. New Show only new alarms. Acknowledged Show only acknowledged alarms. Cleared Show only cleared alarms. 4 Click to the right of any displayed alarm to show further details about the alarm. Polycom, Inc. 60

61 Clear Alarms from the System You can clear alarms for Providers, Zones, Instances, or Service Groups. To clear any alarm, start at the RealPresence Platform Director page for that entity, and select the available entity for which you want to clear an alarm. To clear an active alarm: 1 Go to one of the following: SYSTEM > Providers SYSTEM > Zones SERVICE > Instances SERVICE > Service Group 2 Click for the Provider, Zone, Instance, or Service Group whose alarm you want to edit. Then click the Alarms tab. 3 Select the check box next to the alarm you want to clear, and select either Acknowledge or Clear from the Actions drop-down list. After you acknowledge or clear an alarm, it is removed from the active alarms list. You can review the alarm by selecting the appropriate option from the Show Active drop-down list. View and Edit Threshold Values You can view the current default threshold values for RealPresence Platform Director alarms for each product. When a monitored metric exceeds a threshold, an alarm is raised. Thresholds are set to default values for RealPresence Platform Director product groups but can be changed within individual product instances. View or Edit Thresholds for a Defined Group You can view and edit Threshold values for Instances, Zones, or Resource Groups. Resources available for editing depend upon entity type. To view or edit alarm thresholds for Instances in a RealPresence Platform Director product group: 1 On the RealPresence Platform Director Administrator menu, go to MONITORING > Threshold to display details for each of the installed RealPresence Platform Director system products, as shown next. Polycom, Inc. 61

62 Threshold details for RealPresence Platform Director components 2 Click on one of the component types listed in the rows at the left of the screen. The Resources column displays the resources that are available and being monitored for the selected component. 3 Change applicable Critical Value in % and Warning Value in % fields for each resource on the selected component. 4 Select or clear the Enable Alarm check box to control whether RealPresence Platform Director shows the alarm for the given resource threshold. 5 Click UPDATE to save the new alarm threshold values. View or Edit Threshold Details for a Product Instance You can view and edit threshold details for any individual product instances. To view or edit threshold details for a specific product Instance: 1 From the RealPresence Platform Director Administrator menu, go to SERVICE > Instances to edit threshold details for a specific instance. 2 Click next to the instance whose details you want to edit. 3 Click the Details tab, and then click Threshold at the left of the screen. The same data fields are shown for both hardware and software Instances. 4 Update the threshold information for any of the following resources: CPU utilization, Storage, Memory, Network, Video Ports, or Audio Ports. 5 Do one of the following: Click UPDATE to set the new values. Click RESET TO DEFAULT to return the values to the system defaults. Polycom, Inc. 62

63 View or Edit Threshold Details Within a Service Group Threshold details are available for any service group that has been defined within your RealPresence Platform Director system. You can view and edit details for the entire group. To edit Threshold details within a Service Group: 1 From the RealPresence Platform Director Administrator menu, go to SERVICE > Zones. 2 Click next to the zone containing the resource group whose details you want to edit. 3 Select the Resource Groups tab, and then click next to the appropriate resource group. 4 Select the Details tab, and then click Threshold at the left of the screen. 5 Change the warning values for any available resource, and select the Enable Alarm check box to enable the alarm for that resource. 6 Do one of the following: Click UPDATE to set the new values. Click RESET TO DEFAULT to return the values to the system defaults. To edit Threshold details on a Resource Group within a Zone: 1 From the RealPresence Platform Director Administrator menu, go to SYSTEM > Zones. 2 Click Details next to the zone containing the resource group whose details you want to edit. 3 Select the Details tab, and then click Threshold at the left of the screen. 4 Change the warning values for any available resource, and select the Enable Alarm check box to enable the alarm for that resource. 5 Do one of the following: Click UPDATE to set the new values. Click RESET TO DEFAULT to return the values to the system defaults. View Resource and License Data You can view the operational status of system resources by Resource Group, Instance, or Service Group for entities enabled with SNMP. Available Data Monitored system resources include CPU, memory, storage, and network. RealPresence Platform Director also monitors and displays your system s usage of licensed features that have been purchased and allocated to the Polycom RealPresence instances that are managed by your RealPresence Platform Director. Graphs show system usage for both resources and licensed features along with minimum, maximum, and average capacity over the selected time period. License usage information is available in the Instance view; it is not available for Resource or Service Groups. See the Administrator Guide for the specific RealPresence product for descriptions of the licensed features that can be allocated for it. Polycom, Inc. 63

64 For the resources and license features being monitored, you can select data from today through one of several available time periods including 1 month, 3 months, 6 months, 12 months, or 18 months. Monitored System Resources and License Usage Resource and License Data available for each monitored RealPresence product is outlined in the following table. Note that because RealPresence CloudAXIS Experience Portal and Service Portal do not support SNMP, system resource and license information is not available for either those products. Monitored System Resources and License Usage RPAD SMCU XMA DMA CPU Yes Yes Yes Yes Memory Yes Yes Yes Yes Storage Yes Yes Yes Yes Network Yes Yes Yes Yes Call Service Yes No No No Active Calls Yes No No No Video Ports No Yes No Yes Audio Ports No Yes No Yes Active Participants No Yes No Yes Active Conferences No Yes No Yes Active Calls No No No Yes Active Audio Calls No Yes No No Active Video Calls No Yes No No Used Ports No Yes No No Completed Adhoc Conferences No No Yes No Active Adhoc Conferences No No Yes No Active Scheduled Conferences No No Yes No Future Scheduled Conferences No No Yes No Managed Endpoints No No Yes No To view system resource and/or license data for a Resource Group, Instance, or Service Group: 1 From the RealPresence Platform Director Administrator menu, go to one of the following: Polycom, Inc. 64

65 SERVICE > Instances to select a specific instance. SERVICE > Service Group to select a service group. SYSTEM > Zones to select a Zone, and then select the Resource Groups tab to display a list of available Resource Groups. 2 Click next to the instance, service group, or resource group whose status you want to view. 3 Select the Status tab to view usage information for available monitoring data. Data available depends upon the type of entity you have selected, as shown in the preceding table. 4 Do any of the following: Select the tabs to the left of the graph to change the information being displayed. At the bottom of the screen, select a time period between Today and 18 months for which you want to view data. Click DOWNLOAD to download a.csv file containing the raw data displayed in the graph. Click STOP to stop monitoring the selected data. Click START to resume monitoring. The instance details screen shows the resources and license features being monitored by the system for that instance, as shown in the following screen example. Instance Status Screen Polycom, Inc. 65

66 Manage Users This chapter provides details for managing users of RealPresence Platform Director through their user profiles. Users of the RealPresence Platform Director are created and managed locally and comprise various types of system administrators. User Roles in RealPresence Platform Director Available user roles are described in the table below. RealPresence Platform Director System Users User Type Super Admin Data Center Admin Video Network Admin Read-Only Admin Access granted in RealPresence Platform Director This user role has the highest privileges and permits the administrator to perform all system configurations and manage all data centers housed within RealPresence Platform Director vcenter or host system. Only Super Admins can add, delete, or edit users. This user role is intended for a data center administrator who can choose to add, edit, and remove resources being used inside a zone. This role has the ability to arrange instances within a data center to optimize available resources. This user role is intended for an administrator responsible for maintaining a Service Group. The administrator can add images and create or delete instances from Service Groups as required. This user can read, but not edit, the system configuration. This user type is intended for someone responsible for monitoring the system and reporting issues. System Access by User Type The level of access each user type has to the RealPresence Platform Director system is outlined in the following table. RealPresence Platform Director System Access by User Type Super Admin Data Center Admin Video Network Admin Read-Only Admin Receive alarm s Yes No No No Alarms Read/Write Read/Write Read/Write Read Thresholds Read/Write Read Read Read Download logs Yes Yes Yes Yes User management Read/Write No access No access No access Polycom, Inc. 66

67 Super Admin Data Center Admin Video Network Admin Read-Only Admin Instance operations Read/Write Read Read/Write Read Service Groups Read/Write Read Read Read Resource Groups Read/Write Read Read Read Images Read/Write Read Read/Write Read Zones Read/Write Read Read Read Start/stop monitoring Yes Yes Yes No System settings Read/Write Read* Read* Read* *All of these have read access to logs and Application settings (Monitoring and SNMP) but nothing else under SETTINGS. Manage System Users The USERS page on the Administrator menu offers a view of system users and their assigned roles.» Select USER MANAGEMENT > Users to display a list of users of the RealPresence Platform Director system similar to the one shown. Sample List of System Users Add a User Only Super Admin users can add other users to the system. Any time RealPresence Platform Director is configured with SMTP settings, the user password is always ed to the new user. Even if SMTP is disabled, the system attempts to send the password via . To add a User: 1 From the RealPresence Platform Director Administrator menu, go to USER MANAGEMENT > Users. 2 On the USERS page, click + USER to open the Add a user dialog. 3 Complete the text fields in the Add a user dialog. Fields marked with * are required. Polycom, Inc. 67

68 4 Select a user type from the User Role drop-down list. Descriptions for available user types are listed in the following table. 5 Click ADD to create the new user. Edit a User A Super Admin user can edit details for any user of the RealPresence Platform Director system. To edit User details: 1 From the RealPresence Platform Director Administrator menu, go to USER MANAGEMENT > Users. 2 On the USERS page, click next to the names of the user you want to edit. 3 From the User Details tab, do one of the following: Click in the appropriate text box to edit the details you want to edit. Enable or disable the user by selecting or clearing the Enable User check box. 4 Click SAVE when you complete all edits. Delete a User To delete a User: 1 From the RealPresence Platform Director Administrator menu, go to USER MANAGEMENT > Users. 2 Click next to the row for the user that you want to delete. 3 In the Delete this User confirmation box, click DELETE. Reset a User Password A Super Admin user can reset a password for any other system user. Settings: Reset password and SMTP settings If you do not have SMTP settings configured in the Platform Settings section, the user will not receive notification of a changed password. For information on configuring STMP settings, see Configure SMTP. To reset a user password: 1 From the RealPresence Platform Director Administrator menu, go to USER MANAGEMENT > Users. 2 On the USERS page, click next to the user whose password you want to reset. 3 Select the Reset Password tab. 4 Enter the new password in the Password and Confirm Password fields. Polycom, Inc. 68

69 5 Click UPDATE. Manage Administrator Account Credentials You can edit or change your user account credentials after logging in to the RealPresence Platform Director. Access your account settings through the Admin drop-down list in the upper-right corner of the RealPresence Platform Director Home screen to change either your user profile or password. Edit Your Administrator Profile To edit your user profile: 1 From the Account Settings drop-down list, select Edit Profile. 2 Make the necessary changes in the profile settings Note that the Address field is required. 3 Click UPDATE. Change Your Administrator Password You are required to change your password after logging in for the first time, but you can also change your password at any time through the Account Settings drop-down list. To change your password: 1 From the Account Settings drop-down list, select Change Password to open the Change Password dialog. 2 Type your current password and a new password, and retype the new password. 3 Click CHANGE to change your password. 4 Sign out and return to the login screen to login to RealPresence Platform Director with your new credentials. Polycom, Inc. 69

70

71 Manage Platform Settings In the Platform Settings page of RealPresence Platform Director, you can set specific settings for the platform and for specific applications. Manage Certificates RealPresence Platform Director requires the use of Secure Socket Layer (SSL) connections to access its User Interface. When a browser establishes a secure connection with RealPresence Platform Director, it receives a certificate identifying the RealPresence Platform Director server. The browser uses this certificate, which may be self-signed or signed by a third party Certificate Authority (CA), to determine whether the server is safely and securely accessed. This section shows you how to complete the following tasks: Generate Certificates and CSRs View or Delete a Certificate Upload Certificates or a Certificate Chain While self-signed certificates provide encryption for SSL connections, they are less secure than certificates signed by a CA. Most browsers display warning messages and advise against accessing any site that uses a self-signed certificate. To avoid these warnings without compromising your browser security, you can either import the self-signed certificate as a trusted certificate into your web browser, or use a certificate signed by a CA to identify the RealPresence Platform Director server. To use a certificate signed by a CA, you must do the following: Generate a certificate signing request (CSR). Submit that request to a CA (either local to your organization or public). Upload the signed certificate received from the CA to the RealPresence Platform Director, along with the certificate s trust chain. Generate Certificates and CSRs This section describes how to either generate a self-signed certificate or generate a CSR that can be sent to a third-party CA. For details on uploading certificates, see Upload Certificates or a Certificate Chain. Caution: Overwrite warning Verify that a new certificate or CSR is necessary before following this procedure. Generating a new certificate or CSR overwrites the previous one. To generate a certificate or CSR: 1 From the RealPresence Platform Director Administrator menu, go to SETTINGS > Platform Settings. Then click CERTIFICATE. Polycom, Inc. 71

72 2 On the Certificate Settings page, click the Generate CSR/Certificate tab to display the CSR/Certificate settings, as shown. Generate CSR/Certificate settings dialog 3 Enter information in the fields as shown in the following table. Generate CSR/Certificate settings Field Operation Type Type Organization Organizational Unit Country State Location Sub Alternate Name Value/Description Choose one of the following options from the drop-down list: CSR Generates a Certificate Signing Request Certificate Generates a self-signed certificate Choose the type of certificate The name of your organization Any details that help identify the entity requesting the certificate The two-letter ISO code for the country in which your organization operates List the full state name, no abbreviations City or other location for the organization List of host names protected by this certificate (the host names must be separated by commas) 4 Click GENERATE to generate the certificate or CSR. Then do one of the following: If you generated a CSR, view it by selecting the View button on the Certificate List screen. Follow the instructions to copy the contents to the clipboard and paste it into a text document to send to the CA. Polycom, Inc. 72

73 If you generated a self-signed certificate, restart the RealPresence Platform Director server so that it will recognize the certificate. View or Delete a Certificate From the certificate list, you can view available certificates, confirm if a certificate is required, or delete an obsolete certificate. This section shows you how to view and delete certificates in the RealPresence Platform Director. To view or delete a certificate or CSR: 1 On the RealPresence Platform Director administrator menu, go to SETTINGS > Platform Settings., and then click the Certificate list tab to view a list of existing certificates, as shown. Certificate list settings 2 Do one of the following: Click VIEW to view and/or download the certificate. When you view a certificate, you can also copy the certificate information to send to a third-party CA for signing. Copy the entire hash from BEGIN CERTIFICATE to END CERTIFICATE. Paste the text in to a text file. Save the file with a.cer extension and send it for signing. Click DELETE to delete the certificate. This option is available only to WebApp-trust certificates. Webserver certificates can only be regenerated or uploaded as a CA-signed certificate. For generating WebApp certificates, see Generate Certificates and CSRs. Caution: Deleting trust certificates Be careful when deleting any trust certificate. Deleting a certificate from a certificate chain produces an incomplete chain. If a chain is incomplete, any certificate that was signed or issued by the CA in that chain will no longer be trusted by the system. Upload a Certificate or Certificate Chain You can upload either of two types of required certificates. Those include: Polycom, Inc. 73