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 in near real time. The Reports page is automatically refreshed often and the call activity shows up within 1 minute of availability.
To help with troubleshooting, you can zoom in on data that appears on the graph and isolate to a specific time period.
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.
Total Number of Meetings—Total number of meetings that are hosted on-premises and calls that overflowed to the Cisco Collaboration Cloud for the Cisco Spark organization.
Resources Used for Meetings—Summary of meetings based on where the organization’s calls were hosted.
On Premises—Meeting and participants were hosted on the enterprise clusters.
Cloud—Meeting and participants were hosted on cloud clusters.
Cloud and On-Premises—Meeting and participants cascaded between enterprise and cloud clusters.
Client Types—Summary of common categories of meeting clients that are used in an organization.
The categories include the following client types:
Cisco Spark Desktop—Windows, Mac OSX, web browser.
Others—Any unknown endpoints or clients that don't fit the other categories.
Total Calls (Resources)—The sum total of participants that were on a meeting hosted on premises and participants that were hosted on the Cisco Collaboration Cloud (including overflowed to the cloud) for the Cisco Spark organization
Cloud Calls—Number of calls that did not use enterprise Hybrid Media Nodes, because of no connection to the enterprise network or being subject to enforced policy.
Overflowed to Cloud—Number of calls that were made within an enterprise
but overflowed to a cloud cluster.
On-Premises—Number of calls that are hosted on any of the enterprise clusters.
Overflowed to Cloud—Data on overflowed calls in the last 24 hours: the percentage of overflow, whether there was an increase or decrease, and the number of calls that overflowed.
Clusters in Service—Percentage of clusters that can host calls in the organization.
Client Type Distribution—Provides usage trends of the various client types (for example, mobile, desktop, and other) that are used in your organization.
Total Meetings by Resources Used—Provides a trend of the number of meetings, based on where the meetings were hosted.
Entire meetings hosted in the cloud
Meetings hosted on-premises
Meetings that are cascaded between on-premises and the cloud
Resource 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—Provides a view of the call activity trend across the organization, showing the calls that were hosted on-premises and calls hosted on the cloud. The calls that overflowed to the cloud are represented as dots (insight points) on the cloud call graph. Hover over a dot to show the number of calls that overflowed to the cloud at that instance.
Call Distribution Across On-Premises Clusters—Provides a view of call activity. This information helps you plan your organization's cluster capacity. Calls that cannot be hosted on this specific cluster are redirected to another on-premise cluster. These redirects are represented as dots on the graph. Hover over a dot to show the number of calls redirected from this specific cluster at that instance.
Organization View—Provides a view of how calls are distributed across the different on-premises clusters in the organization. This information helps you plan your organization's cluster capacity.
Cluster View—Provides a view of the call activity trend on a specific cluster.
Clusters in Service (Org View)—Below the overall availability card, you go to a specific cluster view by choosing one from the drop-down.
Below the overall availability card, you go to a specific cluster view by choosing one from the drop-down.
You can click on any of the clusters in the Cluster Availability graph to directly navigate to the Node Availability graph.
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.
Nodes in Service (Cluster View)—Percentage of nodes that are in service to host calls over the selected time period
Green nodes are in service.
Red nodes are not in service.
The following terms are used in Hybrid Media Service reports:
Participant: A person 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.
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 4 Hours
Last 24 Hours
Last Three Months
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
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
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.
Move Hybrid Media Node
You may want to move a node from one cluster to another. For example, you may have a new cluster that you want to redistribute nodes to. Use this procedure to move a Hybrid Media Node. After completing this procedure, your node will only be available to the new resource.Procedure
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.
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.
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.
If needed, click Postpone to postpone the upgrade to the following day.
Under the time zone, the next available upgrade date and time is displayed.
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 cluster from the Cisco Collaboration Cloud. To complete this procedure, you must either move each node to a different cluster or deregister all the nodes. Deregistering all nodes in a cluster permanently removes them and makes them unavailable for use. The only way to make deregistered nodes available again is to reregister them.Procedure
From the list of resources, scroll to the Hybrid Media resource that you want to delete, and then click Edit Cluster Settings.
You can click Media to filter on just Hybrid Media resources.
Click Delete Cluster, 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 Cluster.
Deactivate Hybrid Media Service
Deactivating your Hybrid Media Service removes the ability to have media remain on-premises for your meetings. Also, all in-progress meetings using Hybrid Media Nodes end and future meetings are hosted in the cloud. Once deactivated, the only way to use Hybrid Media Service is to deploy it from the beginning.
Before you deactivate Hybrid Media Service, you will deregister all Hybrid Media Nodes.
Review the list of clusters, read the disclaimer, check the check box to confirm that you understand this action, and then click Deactivate
When you are ready to deactivate your Hybrid Media Service, click Deactivate Service.
All the Hybrid Media Nodes and clusters are removed and Hybrid Media Service is no longer configured.
Manage Hybrid Media Node
Change Hybrid Media Node Network Settings
If your network topology changes, you have to open each Hybrid Media Node and change the network settings. You may see a caution about changing the network settings, but you can still save the changes in case you're making changes to your network after changing Hybrid Media Node settings.
From the main menu of the Hybrid Media Node console, choose option 2 Edit Configuration and then click Select.
Read the prompt that the calls will end on this Hybrid Media Node, and then click Yes.
Click Static, enter the IP address, Mask, Gateway, and DNS values for your network.
Your Hybrid Media Node must have an internal IP address and resolvable DNS name. The node IP address must not belong to the IP address range reserved for Hybrid Media Node internal use. The default reserved IP address range is 172.17.0.0–172.17.255.255, which can be configured in the Diagnostic menu.
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.
To ensure a successful registration to the cloud, use only lowercase characters in the hostname that you set for the Hybrid Media Node. Capitalization is not supported at this time.
When using hostname, you must also enter a valid and resolvable domain. The total length of the FQDN must not exceed 64 characters.
Click Save, and then click Save Changes & Reboot.
During the save, DNS validation is performed if you provided a domain. A warning is displayed if the FQDN (hostname and domain) is not resolvable using the DNS server addresses provided. You may choose to save by ignoring the warning but calls will not work until the FQDN can resolve to the DNS configured on the node. After your Hybrid Media Node reboots, the network configuration changes take effect.
Change the Administrator Passphrase of the Hybrid Media Node
Use this procedure to change the administrator passphrase (password) for your Hybrid Media Node.Procedure
Open and log in to the VMware ESXi console of the VM for your Hybrid Media Node.
In the main menu, choose option 3 Manage Administrator Passphrase, then 1 Change Administrator Passphrase, and then click Enter.
Read the information on the password expired page, click Enter, and then click it again after the password expiry message.
After you're signed out of the console, go back to the sign in screen, and then sign in using the admin login and passphrase (password) that you expired. 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).
Manage Hybrid Media Node Password Expiry
You can view information about the Hybrid Media Node passphrase (password) and expiry policy. You can also modify the numbers of days before a password expires.
Open and log in to the VMware ESXi console of the VM for your Hybrid Media Node.
In the main menu, choose option 3 Manage Administrator Passphrase, then 2 Manage Passphrase Expiry, and then click Enter.
Last Passphrase Change—Shows the date when the password was last changed for the Hybrid Media Node.
Passphrase Expires—Shows the date when the password expires for the Hybrid Media Node.
Expiry Interval (Days)—Sets the lifespan of the password. Enter a different value if you want to change how long a password lasts before it expires, and then click Save.
Run a Ping from Hybrid Media Node
You can run a ping from the Hybrid Media Node. This step tests a destination you enter and sees if the Hybrid Media Node can reach it.
From the Hybrid Media Node console, go to 4 Diagnostics, and then choose Ping.
In the ping field, enter a destination address that you want to test, such as an IP address or hostname, and then click OK.
The test runs and you'll see a ping success or failure message. If you receive a failure, check the destination value that you entered and your network settings.
Enable Debug User Account
If support requires access to the Hybrid Media Node, you can temporarily enable a debug user account so that support can run further troubleshooting.
From the Hybrid Media Node console, go to 4 Diagnostics, choose 2 Enable Debug User Account, and after the prompt, click Yes.
After a message appears that the debug user account was created successfully, click OK to show the encrypted passphrase.
You'll send the encrypted passphrase to support. They use this temporary account and decrypted passphrase to securely access your Hybrid Media Node for troubleshooting. This account expires after 3 days, or you can disable it when support is finished.
Select the start and end of the encrypted data, and copy-paste it into the support ticket or email that you're sending to support.
After you send this information to support, return to the Hybrid Media Node console and press any key to go back to the main menu.
What to Do Next
When support indicates that they finished troubleshooting on the node, you can return the Hybrid Media Node console, go to 4 Diagnostics, and then choose 3 Disable Debug User Account to disable the account before it expires.
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.
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.
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.
You can view the node health directly from the Hybrid Media Node itself. The results are informational, but could aid in troubleshooting steps—for example, if NTP synchronization is not working, you can check the NTP server value in the network settings.
From the Hybrid Media Node console, go to 4 Diagnostics, and then choose 6 Check Node Health to view the following information about the node:
Management Service Container
ETCD (key value store that reliably stores data across a cluster)
Disk Space (Free/Used%)
Configure Container Network on Hybrid Media Node
Hybrid Media Node reserves a subnet range for internal use within the node. The default range is 172.17.0.0–172.17.255.25. The nodes do not respond to any external-to-Hybrid Media Node traffic originating from this range. You may want to change the container bridge IP address to avoid conflicts with other devices in your network.
From the main menu of the Hybrid Media Node console, go to 4 Diagnostics, and then choose 7 Configure Container Network. After the caution that states that active calls will end on the node, click Yes.
Change the values for Container Bridge IP and Network Mask, as needed, and then click Save.
You'll see a screen that shows the container network information, including the IP address range reserved for internal operations on the Hybrid Media Node.
Factory Reset a Hybrid Media Node
As part of deregistration cleanup, you can factory reset the Hybrid Media Node. This step removes any configuration you put in place while the node was active, but does not remove the virtual machine entry. Later, you may want to reregister this node as part of a cluster from scratch.
Before You Begin
You must deregister the Hybrid Media Node from the cluster that's registered in the Cisco Spark Control Hub.
From the Hybrid Media Node console, go to 4 Diagnostics, and then choose 8 Factory Reset.
Ensure that you understand the information in the note that appears, and then click Reset.
The node reboots automatically after the factory reset.