Deployment Guide for Cisco Spark Hybrid Media Service

Transcription

1 First Published: Last Modified: Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA Tel: NETS (6387) Fax:

2 2017 Cisco Systems, Inc. All rights reserved.

3 CONTENTS Preface CHAPTER 1 New and Changed Information v Hybrid Media Service Overview 1 Quality of Service on Hybrid Media Nodes 1 Hybrid Media Node Demo Software 2 CHAPTER 2 Prepare Your Environment 3 Hybrid Media Clusters 3 Hybrid Media Cluster Deployment 4 Cisco Spark Device Registers with Cisco Collaboration Cloud 5 Round-trip Delay Tests Cloud Device Fails to Reach On-Premises Cluster 6 Round-trip Delay Tests Cloud Device Successfully Reaches On-Premises Cluster 6 On-Premises and Cloud Call 7 On-Premises Call with Different Cluster Affinities 8 Cisco Spark Cloud Device Connects to Cloud 8 Cisco Spark On-Premises Device Connects to On-Premises Cluster 9 Cisco Spark On-Premises Device Connects to Cloud 9 Requirements for Hybrid Media Service 10 Call Capacity on Hybrid Media Node Platforms 11 Deployment Models Supported by Hybrid Media Service 11 Ports and Protocols Used by Hybrid Media Service 11 Bandwidth Requirements for Hybrid Media Service 15 Complete the Preinstallation Checklist for Hybrid Media Service 16 CHAPTER 3 Deploy Hybrid Media Service 19 Install Hybrid Media Service Software 19 Log in to the Hybrid Media Node Console 20 iii

4 Contents Set the Network Configuration of the Hybrid Media Node 21 Register the Hybrid Media Node to the Cisco Collaboration Cloud 22 Troubleshoot the Hybrid Media Node Registration 23 CHAPTER 4 Manage Hybrid Media Service 25 View Hybrid Media Service Reports 25 Available Reports 25 Reporting Definitions 26 Filtering Reports 27 Exporting Reports 27 Deregister Hybrid Media Node 27 Move Hybrid Media Node 28 Set Hybrid Media Cluster Upgrade Schedule 28 Delete Hybrid Media Cluster 29 Deactivate Hybrid Media Service 29 Send Logs from Hybrid Media Node 30 Change the Administrator Passphrase of the Hybrid Media Node 30 iv

5 New and Changed Information Date Change November 2, 2017 In Requirements for Hybrid Media Service, on page 10, added the following information on the subnet range used by Hybrid Media Nodes: Hybrid Media Nodes do not respond to any internal traffic originating from the /16 IP range, because this subnet is used by internal services on Hybrid Media Nodes. As a result, Hybrid Media Nodes do not communicate with external devices or clients on this subnet. October 11, 2017 Updated bandwidth diagrams with cascading information. Revised the statement on using the same VLAN or subject for nodes in a cluster. August 15, 2017 Added port 22 (SSH) to Ports and Protocols Used by Hybrid Media Service, on page 11. July 19, 2017 Added requirements and an overview for the Hybrid Media Node demo software image. v

6 New and Changed Information vi

7 CHAPTER 1 Hybrid Media Service Overview Cisco Spark Hybrid Media Service dynamically finds the optimal mix of on-premises and cloud conferencing resources. On-premises conferences stay on premises when there are enough local resources. When local resources are exhausted, conferences then expand to the cloud. Cisco Spark Hybrid Media Node is software that is installed on a Cisco UCS server and managed in Cisco Spark Control Hub. Cisco Spark (basic and advanced) meetings and Cisco Spark app calls (between two people) can be routed to the local, on-net Cisco Spark Hybrid Media node. Cisco Spark Hybrid Media Service selects the most efficient way to use the available resources. Cisco Spark Hybrid Media Service provides these benefits: Improves quality and reduces latency by allowing you to keep your calls on premises. Extends your calls transparently to the cloud when on-premises resources have reached their limit or are unavailable. Manage your Hybrid Media Nodes from the cloud with a single interface: Cisco Spark Control Hub ( Optimize resources and scale capacity, as needed. Combines the features of cloud and on-premises conferencing in one seamless user experience. Reduces capacity concerns, because the cloud is always available when additional resources are needed. Provides advanced reporting on capacity and usage in Quality of Service on Hybrid Media Nodes, page 1 Hybrid Media Node Demo Software, page 2 Quality of Service on Hybrid Media Nodes For Quality of Service (QoS), Hybrid Media Nodes natively mark all traffic (audio, video, content, ix, BFCP, and so on) with DSCP AF41. 1

8 Hybrid Media Node Demo Software Hybrid Media Service Overview Hybrid Media Node Demo Software Use the demo image for Hybrid Media Nodes only for demo purposes. We recommend that you avoid adding a demo image to an existing production cluster. The demo cluster accepts fewer calls than production and expires 90 days from registration to the cloud. Note The Hybrid Media Node demo software is not supported by Cisco TAC. Specifications See Requirements for Hybrid Media Service, on page 10 for the supported platforms and specifications for hybrid media node software. Capacity See Call Capacity on Hybrid Media Node Platforms, on page 11. Use Cases for the Hybrid Media Node Demo Software Media Anchored to On-Premises Deploy and configure the node with the demo software. Run a meeting that includes the following participants: a Cisco Spark app participant, Cisco Spark endpoint participant, and a Cisco Spark Board. After the meeting is over, from the customer view in go to Reports to access the Hybrid Media reports. In the reports, you can see that the media stayed on-premises. Meeting with Cloud and On-Premises Participants Run another meeting with a couple of Cisco Spark participants on-premises and one in the cloud. Observe that all participants can seamlessly join and participate in the meeting. Known Issue DNS works, but may fail to save network configuration under certain conditions when you use FQDN for hostname and NTP servers. As a workaround, use IP addresses only so that you can save the initial configuration. Related Topics Requirements for Hybrid Media Service, on page 10 2

9 CHAPTER 2 Prepare Your Environment Hybrid Media Clusters, page 3 Requirements for Hybrid Media Service, page 10 Call Capacity on Hybrid Media Node Platforms, page 11 Deployment Models Supported by Hybrid Media Service, page 11 Ports and Protocols Used by Hybrid Media Service, page 11 Bandwidth Requirements for Hybrid Media Service, page 15 Complete the Preinstallation Checklist for Hybrid Media Service, page 16 Hybrid Media Clusters Hybrid Media Nodes are deployed in clusters. A cluster defines Hybrid Media Nodes with similar attributes, such as network proximity. Cisco Spark participants are directed to use a particular cluster or the cloud, depending on the following conditions: A client on a corporate network that can reach an on-premises cluster will connect to it the primary preference for clients that are on the corporate network. A client that cannot reach an on-premises cluster will connect to the cloud the case for a mobile device that is not connected to the corporate network. Each cluster contains logic that cascades meetings across other clusters, as needed. Cascading provides data path for media between clients in their meetings. Meetings are distributed across nodes and the clients land on the most efficient node nearest to them, depending on factors such as network topology, WAN link, and resource utilization. Reachability is determined by the client's ability to "ping" media nodes. A variety of potential connection mechanisms such as UDP and TCP are used during an actual call. Before the call, the Cisco Spark device registers with the Cisco Collaboration Cloud, which provides a list of cluster candidates for the call. 3

10 Hybrid Media Cluster Deployment Prepare Your Environment Hybrid Media Cluster Deployment Create fewer clusters when resources have similar network proximity (affinity). Whererever possible when creating clusters, add nodes that are in the same geographical region and the same data center. Typically, deploy clusters in enterprises that host frequent localized meetings. Plan where you place clusters on the bandwidth available at various WAN locations inside the enterprise. Over time, you can deploy and grow cluster-by-cluster based on observed user patterns. Clusters located in different time zones can effectively serve multiple geographies by taking advantage of different peak/busy hour calling patterns. If you have two hybrid media nodes in two separate data centers (EU and NA, for example), and you have endpoints join through each data center, the nodes in each data center would cascade to a single media node in the cloud. Theses cascades would go over the Internet. If there is a cloud participant (that joins before one of the HMN participants), the nodes would be cascaded through the cloud participant s media node. Time Zone Diversity Time zone diversity can allow clusters to be shared during off-peak times. For example: A company with a Northern California cluster and a New York cluster might find that overall network latency is not that high between the two locations that serve a geographically diverse user population. When resources are at peak usage in the Northern California cluster, the New York cluster is likely to be off peak and have additional capacity. The same applies for the Northern California cluster, during peak times in the New York cluster. These aren't the only mechanisms used for effective deployment of resources, but they are the two main ones. Overflow to the Cloud When the capacity of all on-premises clusters are reached, an on-premises participant overflows to the Cisco Collaboration Cloud. This does not mean that all calls will be hosted in the cloud. Only those participants that are either remote or can't connect to an on-premises cluster will be directed to the cloud. In a call with both on-premises and cloud participants, the on-premises cluster is bridged (cascaded) to the cloud to combine all participants into a single call. 4

11 Prepare Your Environment Cisco Spark Device Registers with Cisco Collaboration Cloud Cisco Spark Device Registers with Cisco Collaboration Cloud In addition to determining reachability, the clients also perform periodic round-trip delay tests using Simple Traversal of UDP through NAT (STUN). STUN round-trip (SRT) delay is an important factor when selecting potential resources during an actual call. When multiple clusters are deployed, the primary selection criteria are based on the learned SRT delay. Reachability tests are performed in the background, initiated by a number of factors including network changes, and do not introduce delays that affect call setup times. The following two examples show possible reachability test outcomes. 5

12 Round-trip Delay Tests Cloud Device Fails to Reach On-Premises Cluster Prepare Your Environment Round-trip Delay Tests Cloud Device Fails to Reach On-Premises Cluster Round-trip Delay Tests Cloud Device Successfully Reaches On-Premises Cluster 6

13 Prepare Your Environment On-Premises and Cloud Call Learned reachability information is provided to the Cisco Collaboration Cloud every time a call is set up. This information allows the cloud to select the best resource (cluster or cloud), depending on the relative location of the client to available clusters and the type of call. If no resources are available in the preferred cluster, additional clusters are tested for availability based on SRT delay. A preferred cluster is chosen with the lowest SRT delay. Calls are served on premises from a secondary cluster when the primary cluster is busy. Local reachable Hybrid Media resources are tried first, in order of lowest SRT delay. When all local resources are exhausted, the participant connects to the cloud. Cluster definition and location is critical for a deployment that provides the best overall experience for participants. Ideally, a deployment should provide resources where the clients are located. If not enough resources are allocated where the clients make the majority of calls, more internal network bandwidth is consumed to connect users to distant clusters. On-Premises and Cloud Call On-premises Spark devices that have the same cluster affinity (preference, based on proximity to the cluster) connect to the same cluster for a call. On-premises Spark devices with different on-premises cluster affinities, connect to different clusters and the clusters then bridged to the cloud to combine the two environments into a single call. 7

14 On-Premises Call with Different Cluster Affinities Prepare Your Environment On-Premises Call with Different Cluster Affinities The Spark device connects to either on-premises cluster or cloud based upon its reachability. The following show examples of the most-common scenarios. Cisco Spark Cloud Device Connects to Cloud 8

15 Prepare Your Environment Cisco Spark On-Premises Device Connects to On-Premises Cluster Cisco Spark On-Premises Device Connects to On-Premises Cluster Cisco Spark On-Premises Device Connects to Cloud 9

16 Requirements for Hybrid Media Service Prepare Your Environment Requirements for Hybrid Media Service Table 1: Configuration Requirements for Hybrid Media Node Software Hardware Configuration Cisco Multiparty Media 410v server Specifications for Production Software Image 48vCPUs 60 GB main memory 250 GB local hard disk space Specifications for Demo Software Image Common Requirements VMware ESXi 6 or vsphere 6 or later 2 vcpus Hyperthreading enabled Cisco Meeting Server 1000 Note We do not support the first generation MM400v server. 72vCPUs 60 GB main memory 250 GB local hard disk space Specifications-based Configuration 48vCPUs 60 GB main memory 250 GB local hard disk space 2.6 GHz Intel Xeon E5-2600v3 or later processor 12vCPUs 8 GB main memory 20 GB local hard disk space 2.0 GHz or later processor The applications for Hybrid Media Service need a dedicated CPU. As a result, Hybrid Media Node is not supported as a coresident instance with other applications. Note Hybrid Media Nodes do not respond to any internal traffic originating from the /16 IP range, because this subnet is used by internal services on Hybrid Media Nodes. As a result, Hybrid Media Nodes do not communicate with external devices or clients on this subnet. Related Topics Hybrid Media Node Demo Software, on page 2 10

17 Prepare Your Environment Call Capacity on Hybrid Media Node Platforms Call Capacity on Hybrid Media Node Platforms If all the meetings hosted on a given Hybrid Media Node have Cisco Spark apps and devices, then the server can scale up to 50 participants at 720p. Server MM410v Maximum Simultaneous High Definition Calls Per Server (Cisco Spark) 50 participants CMS 1000 Demo software 50 participants 5-10 participants Deployment Models Supported by Hybrid Media Service The following are supported in a Hybrid Media Service deployment: You can deploy a Hybrid Media Node in either a data center (preferred) or demilitarized zone (DMZ). For guidance, see Ports and Protocols Used by Hybrid Media Service, on page 11. The following types of address translation are supported: IPv4 Dynamic Network Address Translation (NAT) using an IP pool Dynamic Port Address Translation (PAT) Other forms of NAT should work as long as the correct ports and protocols are used, but we do not officially support them because they have not been tested. Static IP address for the Hybrid Media Node The following are not supported in a Hybrid Media Service deployment: IPv6 DHCP for the Hybrid Media Node Dual network interfaces (NICs) This capability is not used for Hybrid Media Service. Ports and Protocols Used by Hybrid Media Service To ensure a successful deployment of Hybrid Media Service, make sure you open the following ports for use with the protocols. See this document to understand network requirements for Cisco Spark services. See the Cisco Spark Firewall Traversal Whitepaper for more information about firewall and network practices for Cisco Spark services. 11

18 Ports and Protocols Used by Hybrid Media Service Prepare Your Environment To mitigate potential DNS query issues, follow the DNS Best Practices, Network Protections, and Attack Identification documentation when you configure your enterprise firewall. Figure 1: Ports and Protocols for Management The Hybrid Media Nodes in a cluster should be in the same VLAN or subnet mask. Purpose Source Destination Source IP Source Port Transport Protocol Destination IP Destination Port Management Management computer Hybrid Media Node As required Any TCP, HTTPS Hybrid Media Node 443 SSH for access to Hybrid Media admin console Management computer Hybrid Media Node As required Any TCP Hybrid Media Node 22 Management Hybrid Media Node Cisco Collaboration Cloud As required Any UDP, NTP UDP, DNS Any TCP, HTTPS (Websockets) Cascade Signaling Hybrid Media Node Cisco Collaboration Cloud Any Any TCP Any 444 Management Hybrid Media Node Cisco Collaboration Cloud As required Any TCP, HTTPS *.docker.io *.wbx2.com *.webex.com

19 Prepare Your Environment Ports and Protocols Used by Hybrid Media Service Purpose Source Destination Source IP Source Port Transport Protocol Destination IP Destination Port Management Hybrid Media Node (1) Hybrid Media Node (2) Hybrid Media Node (1) Any TCP, HTTPS (Websockets) Hybrid Media Node (2) The default configuration in the OVA is configured for NTP and DNS. The OVA requires that you open those ports outbound to the internet. If you configure a local NTP and DNS server, then ports 53 and 123 are not required to be opened through the firewall. Figure 2: Ports and Protocols for Cisco Spark Meetings Purpose Source Destination Source IP Source Port Transport Protocol Destination IP Destination Port Calling to meeting Apps (Cisco Spark mobile, web and desktop apps) Spark room device Hybrid Media Node As required Any UDP and TCP (Used by the Cisco Spark app) SRTP (Any) Any 5004, 5006 Cascade Hybrid Media Node Cisco Collaboration Cloud As required UDP, SRTP (Any)** Any 5004 Cascade Hybrid Media Node Hybrid Media Node As required UDP, SRTP (Any)** Any 5004, 5006 ** TCP is also supported, but not preferred because it may affect media quality. 13

20 Ports and Protocols Used by Hybrid Media Service Prepare Your Environment For the best experience using Cisco Spark in your organization, configure your firewall to allow all outbound TCP and UDP traffic that is destined toward ports 5004 as well as any inbound replies to that traffic. The port requirements listed above assume that Hybrid Media Nodes are deployed either in the LAN (preferred) or in a DMZ and that Cisco Spark apps are in the LAN. 14

21 Prepare Your Environment Bandwidth Requirements for Hybrid Media Service Bandwidth Requirements for Hybrid Media Service Figure 3: One-to-One Local Call Bandwidth Requirements Figure 4: One-to-One Local-Remote Call Bandwidth Requirements Figure 5: Multiparty Local Call Bandwidth Requirements 15

22 Complete the Preinstallation Checklist for Hybrid Media Service Prepare Your Environment Figure 6: Multiparty Local-Remote Call Bandwidth Requirements Complete the Preinstallation Checklist for Hybrid Media Service Use this checklist to ensure you are ready to install and configure your Hybrid Media Node. 16

23 Prepare Your Environment Complete the Preinstallation Checklist for Hybrid Media Service Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Ensure the following is in place: Meet the minimum system requirements described in Requirements for Hybrid Media Service, on page 10 Understand the call capacity levels described in Call Capacity on Hybrid Media Node Platforms, on page 11 Understand the supported deployment models described in Deployment Models Supported by Hybrid Media Service, on page 11. Ensure that your network allows connectivity on the ports and using the protocols described in Ports and Protocols Used by Hybrid Media Service, on page 11 Ensure that your network supports the bandwidth requirements described in Bandwidth Requirements for Hybrid Media Service, on page 15 Acquire the following information from your network administrator to assign to your Hybrid Media Node: IP address Network mask Gateway IP address DNS servers NTP servers (Optional) Choose the hostname to be configured on the Hybrid Media Node. Note If you plan to configure Hybrid Media Node with FQDN, you must create both forward- and reverse-dns (A- and PTR-records) in the DNS configuration. Before starting installation, make sure your Cisco Spark organization is enabled for Hybrid Media Service. This service is available for organizations with certain paid Cisco Spark subscriptions as documented in Requirements for Hybrid Media Service, on page 10. Contact your Cisco partner or account manager for assistance. Choose a supported hardware or specifications-based configuration for your Hybrid Media Node, as described in Requirements for Hybrid Media Service, on page 10. Note Only one network interface card (NIC) is supported. Make sure your server is running VMware ESXi 6 (or later) and vsphere 6 (or later) with a VM host operational. What to Do Next Install Hybrid Media Service Software, on page 19 17

24 Complete the Preinstallation Checklist for Hybrid Media Service Prepare Your Environment 18

25 CHAPTER 3 Deploy Hybrid Media Service Install Hybrid Media Service Software, page 19 Log in to the Hybrid Media Node Console, page 20 Set the Network Configuration of the Hybrid Media Node, page 21 Register the Hybrid Media Node to the Cisco Collaboration Cloud, page 22 Troubleshoot the Hybrid Media Node Registration, page 23 Install Hybrid Media Service Software Use this procedure to deploy a Hybrid Media Node to your host server running VMware ESXi. Before You Begin Read the Virtualization Software Requirements documentation to understand supported harware, coresidency inforormation, supported network configuration, supported VMWare versions and features. Make sure you have these required items: A computer with: VMware vsphere client 6.0 or later For a list of supported operating systems, refer to VMware documentation. Hybrid Media Service software OVA file downloaded Download the latest Hybrid Media Service software From the customer view inhttps:// admin.ciscospark.com, and go to Services > Hybrid Media > Set Up > Settings. There, you can access both the production and demo software images. A supported server with VMware ESXi 6.0 or later installed and running 19

26 Log in to the Hybrid Media Node Console Deploy Hybrid Media Service Procedure Step 1 Step 2 Step 3 Step 4 Using your computer, open the VMware vsphere client and sign in to the ESXi system on the server. Go to File > Deploy OVF Template. On the Source page, identify where the OVA file is located, and then click Next. On the OVF Template Details page, click Next, choose the type of deployment configuration, and then click Next. MM410v CMS 1000 The options are listed in the order of increasing resource requirements. Step 5 Step 6 Step 7 Step 8 Step 9 On the Name and Location page enter a Name for this Hybrid Media Node (for example, "Hybrid_Media_Node_1"), and then click Next. On the Disk Format page, ensure that the default disk format of Thick Provision Lazy Zeroed is selected and then click Next. On the Network Mapping page, choose the network option from the list of entries to provide the desired connectivity to the VM. On the Ready to Complete page, click Finish. After deployment of the OVA is complete, your Hybrid Media Node appears in the list of VMs. Right-click the Hybrid Media Node VM, and then choose Power > Power On. The Hybrid Media Service software is installed as a guest on the VM Host. You are now ready to sign in to the console and configure your Hybrid Media Node. Troubleshooting Tips You may experience a delay of a few minutes before the node containers come up. A bridge firewall message appears on the console during first boot, during which you can't sign in. What to Do Next Log in to the Hybrid Media Node Console, on page 20 Log in to the Hybrid Media Node Console Procedure Step 1 Step 2 From the VMware vsphere client, go to your Hybrid Media Node VM, and then choose Console. The Hybrid Media Node VM boots up and a login prompt appears. If the login prompt does not appear, press Enter. Use the following default login and password to log in: a) Login: admin b) Password: cisco 20

27 Deploy Hybrid Media Service Set the Network Configuration of the Hybrid Media Node Step 3 Step 4 Step 5 Step 6 Because you are logging in to your Hybrid Media Node for the first time, you must change the administrator passphrase (password). For (current) password, enter the default password (from above), and then press Enter. For new password, enter a new passphrase, and then press Enter. For retype new password, retype the new passphrase, and then press Enter. A"Password successfully changed" message appears, and then the initial Cisco Hybrid Media Node screen appears with a message about unauthorized access being prohibited. Press Enter to load the main menu. What to Do Next Set the Network Configuration of the Hybrid Media Node, on page 21 Set the Network Configuration of the Hybrid Media Node Use this procedure to configure a static IP address for your Hybrid Media Node, as well as change the hostname and NTP servers, if needed. DHCP is not currently supported. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 From the main menu of the Hybrid Media Node console, choose option 2 Edit Configuration and then press Enter. In the screen that describes the effect of changes to the Hybrid Media Node, press Enter. Select Static and press Enter. The Configure Hybrid Media Node page appears. Enter the IP address, Mask, Gateway and DNS information. Your Hybrid Media Node must have an internal IP address and resolvable DNS name. Deploy all the devices on the same subnet or VLAN, so that all devices in a cluster are reachable from wherever the clients reside in your network. (Optional) Change the hostname, domain or NTP server(s), if required. Note When using hostname, you must also enter a valid and resolvable domain. The total length of the FQDN must not exceed 64 characters. Press Tab to choose Save, and then press Enter. When you are prompted to reboot the system for the changes to take effect, press Enter. When a message appears that indicates node changes may require that components be reconfigured, press Enter. After your Hybrid Media Node reboots, the network configuration changes take effect. The node shows as "Registered." In the background, the node updates the software and changes to "Active" when completely updated and ready to use. This process can take up to 5 minutes. 21

28 Register the Hybrid Media Node to the Cisco Collaboration Cloud Deploy Hybrid Media Service What to Do Next Register the Hybrid Media Node to the Cisco Collaboration Cloud, on page 22 Register the Hybrid Media Node to the Cisco Collaboration Cloud Use this procedure to register your first Hybrid Media Node to the Cisco Collaboration Cloud. When you use Cisco Spark Control Hub to register your first node, you create a cluster to which the node is assigned. A cluster contains one or more media nodes that serve users in a specific geographic region. Before You Begin Once you begin registration of a node, you must complete it within 60 minutes or you have to start over. Ensure that any popup blockers in your browser are disabled or that you allow an exception for admin.ciscospark.com. For best results, deploy all nodes of a cluster in the same data center. See Hybrid Media Clusters, on page 3 for how they work and best practices. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 From the customer view in go to Services, and then click Set Up from the Hybrid Media card. Make sure you have installed and configured your Hybrid Media Node, and then click Add Resource. In the first field, enter a name for the cluster to which you want to assign your Hybrid Media Node. Tip We recommend that you name a cluster based on where the nodes of the cluster are located geographically. Examples: "San Francisco" or "New York" or "Dallas." In the second field, enter the FQDN or internal IP address of your Hybrid Media Node and then click Next. Enter the same internal IP address that you used to configure the node from the console. A message appears indicating you can register your node to the Cisco Collaboration Cloud. Click Go to Node. A new browser tab opens and a warning message appears about the website certificate being invalid. This is normal. Click Continue in the warning message. After a few moments, you are redirected to the Hybrid Media Node connectivity tests for Cisco Collaboration Cloud services. If all tests are successful, the Enable Hybrid Services page appears. There, you confirm that you want to register your Hybrid Media Node with your Cisco Spark organization. Click Allow. Your account is validated, your Hybrid Media Node is registered and the message "Registration Complete" appears indicating your Hybrid Media Node is now registered to the Cisco Collaboration Cloud. Click the portal link or close the tab to go back to the Media Service page. 22

29 Deploy Hybrid Media Service Troubleshoot the Hybrid Media Node Registration On the Media Service page, you now see the new cluster that contains the Hybrid Media Node that you registered. Your Hybrid Media Node is ready for use in your Cisco Spark organization. To register additional Hybrid Media Nodes, go to the Media Service page, click Add Resource and follow Steps 4 9. When you deploy a new Hybrid Media Node, Cisco Spark apps and room devices won't recognize the new node for up to 2 hours. The clients check for node reachability during startup, a network change, or cache expiration. You can wait for 2 hours or, as a workaround, restart your Cisco Spark app or reboot the Cisco Spark room or desk device. Afterwards, call activity is captured in the Hybrid Media reports in Cisco Spark Control Hub. Troubleshoot the Hybrid Media Node Registration This section contains possible errors you may encounter during registration of your Hybrid Media Node to the Cisco Collaboration Cloud and suggested steps to correct them. The domain could not be resolved. Possible Cause This message appears if the DNS settings configured on your Hybrid Media Node are not correct. Solution Sign in to the console of your Hybrid Media Node and make sure the DNS settings are correct. Could not connect to site using port 443 via SSL Possible Cause This message appears if your Hybrid Media Node cannot connect to the Cisco Collaboration Cloud. Solution Make sure your network allows connectivity on the ports required for Hybrid Media Service. For details, see Ports and Protocols Used by Hybrid Media Service, on page

30 Troubleshoot the Hybrid Media Node Registration Deploy Hybrid Media Service 24

31 CHAPTER 4 Manage Hybrid Media Service View Hybrid Media Service Reports, page 25 Deregister Hybrid Media Node, page 27 Move Hybrid Media Node, page 28 Set Hybrid Media Cluster Upgrade Schedule, page 28 Delete Hybrid Media Cluster, page 29 Deactivate Hybrid Media Service, page 29 Send Logs from Hybrid Media Node, page 30 Change the Administrator Passphrase of the Hybrid Media Node, page 30 View Hybrid Media Service Reports Hybrid Media Service reports are available on the Reports page of Cloud Collaboration Management, once Hybrid Media Service is active and has a cluster with at least one registered Hybrid Media Node. From the Overview page, select Reports from the menu on the left side of the screen and then, on the Reports page, click Hybrid Media Service on the upper-right side of the screen. Reports provide information about how you use your on-premises Hybrid Media Nodes and clusters in your Cisco Spark organization. With this information, you can more effectively manage your Hybrid Media resources by monitoring the capacity, utilization, and availability of your on-premises resources. You can use this information to make decisions about adding more Hybrid Media Nodes to a cluster or creating new clusters, for example. Data in the reports is collected every 10 minutes and the Reports page is automatically refreshed every 5 minutes. Available Reports Hybrid Media Service reports provide information through cards and graphs. The cards provide a snapshot of the critical metrics over a given period of time. The graphs provide a detailed trend of these metrics over the same period of time. You can view the information for all clusters of your organization or an individual cluster. 25

32 Reporting Definitions Manage Hybrid Media Service Cards Total Calls Total number of calls that are hosted on premises and calls that overflowed to the Cisco Collaboration Cloud for the Cisco Spark organization Hosted On-Premises Number of calls hosted by on-premises clusters Overflowed to Cloud Number of calls on all clusters that overflowed to the cloud, because on-premises cluster capacity was exceeded Redirected by this Cluster Number of calls on a cluster that were redirected to another cluster or to the Cisco Collaboration Cloud because the cluster capacity was exceeded Graphs Percentage Utilization Average CPU utilization trend of all clusters in an organization (organization view) or a selected cluster compared to other clusters (cluster view). Call Activity: Number of active calls over a period of time. Each line represents a snapshot of the aggregate number of active calls in that cluster or organization. Cluster Availability: Percentage of clusters that are available to host calls over time. Green clusters have all nodes in service. Yellow clusters have 1 or more nodes that are not in service. Red clusters have no nodes in service. Node Availability: Percentage of nodes that are available to host calls over time Green nodes are available. Red nodes are not available. Reporting Definitions The following terms are used in Hybrid Media Service reports: Call: A participant who initiates or receives a media (audio or audio and video) channel to participate in a meeting. Meeting: A group of 1 or more calls collaborating together. Hybrid Media Node: A basic media processing engine deployed on premises, which provides conferencing service. Hybrid Media Cluster: A collection of 1 or more Hybrid Media Nodes grouped together, usually based on geographic location. Organization: In this context, it refers a collection of all the clusters in your Cisco Spark organization. 26

33 Manage Hybrid Media Service Filtering Reports Filtering Reports The following filtering options are available in Hybrid Media Service reports: Cluster: At the upper-left side of the page, you can filter reports to display information for All Clusters or a specific cluster. Time: At the upper-right side of the page, you can filter the time range of the information. Available options are: Last 24 Hours Last Week Last Month Last Three Months Exporting Reports You can click the 3 dots ( ) at the upper-right corner of each Hybrid Media Service report to export the report in one of the following formats: Save As:.PNG or.jpg PDF Export:.CSV or.xlsx Deregister Hybrid Media Node Use this procedure to remove a Hybrid Media Node from the Cisco Colloboration Cloud. After completing this procedure, your node is removed from its cluster and is unavailable for use. After deregistering a node, the only way to make it available again is to reregister it. Procedure Step 1 Step 2 Step 3 From the customer view in go to Services, and then click Resources under Hybrid Media. From the list of resources, go to the cluster that contains the node you want to deregister, choose the node, and then click Action > Deregister Node. A message appears asking you to confirm that you want to delete the node. After you read and understand the message, click Deregister Node. 27

34 Move Hybrid Media Node Manage Hybrid Media Service Move Hybrid Media Node Use this procedure to move a Hybrid Media Node from its current resource to a new one. After completing this procedure, your node will only be available to the new resource. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 From the customer view in go to Services, and then choose Resources under Hybrid Media. From the list of resources, go to the resource that contains the node that you want to move, and then click the node. In the Overview panel, click Move Node. Choose one: Create a new cluster by entering a name for the resource. Choose an existing resource. Click Move Node. Your node is moved to the new cluster. Related Topics Move a Node in to Maintenance Mode Set Hybrid Media Cluster Upgrade Schedule You can set a specific upgrade schedule or use the default schedule of 3:00 AM Daily United States: America/Los Angeles. You can also choose to postpone an upcoming upgrade, if necessary. Software upgrades for Hybrid Media Service are done automatically at the resource level, which ensures that all nodes are always running the same software version. Upgrades are done according to the upgrade schedule for the resource. When a software upgrade becomes available, you have can manually upgrade the cluster before the scheduled upgrade time. Procedure Step 1 Step 2 Step 3 Step 4 From the customer view in go to Services, and then click Resources under Hybrid Media. Go to a media resource, scroll to Cluster Settings, and then choose the resource name. On the Settings page, scroll to Upgrade, and then choose the time and time zone for the upgrade schedule. Note Upgrades may take longer than a few minutes if the Hybrid Media Node is waiting for active calls to end before the upgrade begins. For a more immediate upgrade process, we recommend that you schedule the automatic upgrade window outside of your regular business hours. (Optional) If needed, click Postpone to postpone the upgrade to the following day. 28

35 Manage Hybrid Media Service Delete Hybrid Media Cluster Under the time zone, the next available upgrade date and time is displayed. Step 5 (Optional) Choose a release channel, which allows you to select the type of software version to which you want to upgrade: Stable Provides the current release software version (this is the default and usually the best choice for most customers) Beta (if enabled by Cisco) Provides an upcoming software version (this is for customers who want to try out upcoming features and are willing to accept there may be known issues or defects) Delete Hybrid Media Cluster You can permanently delete a Hybrid Media resource from the Cisco Collaboration Cloud. To complete this procedure, you must either move each node to a different resource or deregister all nodes first. Deregistering all nodes in a resource permanently removes them and makes them unavailable for use. The only way to make deregistered nodes available again is to reregister them. Procedure Step 1 Step 2 Step 3 From the customer view in go to Services, and then click All Resources. From the list of resources, scroll to the Hybrid Media resource that you want to delete, and then click Settings. Tip You can click Media to filter on just Hybrid Media resources. Click Delete Resource, and then choose one: Click Move All Nodes. For each node, either create a new resource by entering a name or choose an existing resource from the drop-down list, and then click Continue. Click Deregister All Nodes, check the check box, and then click Delete Resource. Deactivate Hybrid Media Service Deactivating your Hybrid Media Service removes the ability to host meetings on premises. In addition, all in-progress meetings will end and future meetings will be hosted in the cloud. Once deactivated, the only way to use Hybrid Media Service is to reactivate it. Before you deactivate Hybrid Media Service, you will deregister all Hybrid Media Nodes. 29

36 Send Logs from Hybrid Media Node Manage Hybrid Media Service Procedure Step 1 Step 2 Step 3 From the customer view in go to Services, choose Settings under Hybrid Media, and then click Deactivate. In the Deactivate Service window, review the list of resources that will deactivated (scroll the window to the bottom, if needed), select the I'm ready to deregister these resources checkbox and then click Continue. A message appears asking you to confirm that you want to deactivate your Hybrid Media Service. When you are ready to deactivate your Hybrid Media Service, click Deactivate Service. Note You can keep your Hybrid Media Service active by clicking Cancel. If you do this, you must register at least one Hybrid Media Node to make the service fully functional. Send Logs from Hybrid Media Node You may be instructed to send logs directly to Cisco or to a supported FTP server. Use this procedure to send logs directly from any Hybrid Media Nodes that you registered to the cloud. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Open and log in to the VMware ESXi console of the VM for your Hybrid Media Node. In the main menu, click option 4 Diagnostics and then press Enter. Click 4 Export Log Files, provide feedback if you want, and then click Next. Choose an option: Send Logs to FTP Server, and then enter the details of the FTP server. Send Logs to Cisco, and then confirm the export of the logs. Choose OK to return to the Hybrid Media Node main menu. (Optional) Choose 5 Check Status of Log Files Sent to Cisco if you sent the logs to Cisco. What to Do Next After you send logs, we recommend that you send feedback directly from the Cisco Spark app so that your support contacts have all the information that they need to help you. Related Topics Send Feedback in the Cisco Spark App Change the Administrator Passphrase of the Hybrid Media Node Use this procedure to change the administrator passphrase (password) for your Hybrid Media Node. 30

37 Manage Hybrid Media Service Change the Administrator Passphrase of the Hybrid Media Node Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Open and log in to the VMware ESXi console of the VM for your Hybrid Media Node. In the main menu, choose option 3 Change Administrator Passphrase and then press Enter. From the password expired page, make sure Yes is selected, and then press Enter, and then press it again after the password expiry message. Press Enter. After you're signed out of the console, go back to the sign in screen, and then sign in using the current admin login and passphrase (password). You are prompted to change your password. For Old password, enter the current passphrase, and then press Enter. For New password, enter a new passphrase, and then press Enter. For Re-enter new password, retype the new passphrase, and then press Enter. A "password changed" message appears and then you go back to the sign in screen. Sign in using your new admin login and passphrase (password). 31

38 Change the Administrator Passphrase of the Hybrid Media Node Manage Hybrid Media Service 32