Manage and Troubleshoot Video Mesh

Video Mesh Analytics

Analytics provide information about how you use your on-premises Video Mesh nodes and clusters in your Webex organization. With the historical data in the metrics view, you can more effectively manage your Video Mesh resources by monitoring the capacity, utilization, and availability of your on-premises resources. You can use this information to make decisions about adding more Video Mesh nodes to a cluster or creating new clusters, for example. Video Mesh analytics can be found in Control Hub under Analytics > Video Mesh and Troubleshooting > Recent Resource Usage.

To help with analyzing the data in your organization, you can zoom in on data that appears on the graph and isolate a specific time period. For Analytics, you can also slice and dice reports to show more granular details.

Note

Video Mesh analytics and troubleshooting reports show data in the time zone that is set for the local browser.

Analytics

Video Mesh analytics provide a long-term trend (up to 3 months of data) in the categories of engagement, resource usage, and bandwidth usage.

Recent Resource Usage

The recent resource usage view under troubleshooting provides a near-realtime view of activity in your organization: up to 1 minute aggregation and the ability to view the last 4 hours or 24 hours on all clusters or specific clusters. The page in Control Hub is automatically refreshed—every 1 minute for the last 4 hours and every 10 minutes for the last 24 hours.

Access, Filter, and Save Video Mesh Analytics

Video Mesh metric reports are available on the Analytics page of Control Hub (https://admin.webex.com), once Video Mesh is active and has a cluster with at least one registered Video Mesh node.

Procedure

Step 1

From the customer view in https://admin.webex.com, choose Analytics, and then click Video Mesh on the upper-right side of the screen.

Step 2

Click a category, depending on the type of data you're looking for:

Engagement
Resources
Bandwidth Usage

Tip

Click info to get a short description of the donut graph or chart. When done reading, click info again to flip back to the graph view.

Step 3

From the drop-down on the right, choose an option to fìlter on how far back in time you want to show data.

Last 7 Days (Default)—Changes the horizontal axis to every 1 hour.
Last 24 Hours—Changes the horizontal axis to every 10 minutes.
Last 30 Days—Changes the horizontal axis to every 3 hours.
Last 90 Days—Changes the horizontal axis to every 8 hours.

Step 4

Interact with the charts or donut graphs by using the following options as needed:

Click one or more segments on the donut graph or chart view and then click to update the donut view and the corresponding chart view.
On a specific graph or overview, click maximize if you want to increase the view. The other graphs and overviews won't appear. Click minimize to zoom back out to the defaul analytics view.
Choose legend items on the graph or overview to update the view on that specific legend item and then click . For example, after you select the legend item Cloud and On-Premises, the line graph updates with that data highlighted.
Choose the lasso tool and use it to draw a freehand selection across the data that you want to filter on and then click .
On a graph that shows data in a time range, narrow down to a specific time range by clicking on the left and dragging your mouse to the right and then clicking . (This action affects all the related data that appears on the analytics page.)

Tip

Hover over sections of a donut, lines on a graph, or insight points on a graph to view more information on the specific point in time of the data.

Note

To start over from within the same graph or overview, click .

To start over by exiting out of the graph or overview and returning to the main analytics view, click Clear selection.

The filtered view opens in a new tab. If you want to return to the view before the filter that you created, you can click the X in the tab name to clear the selection.

Step 5

After you've filtered data in the reports, click more , and then choose a file format option, which saves a local copy of the report so you can use it offline (for example, in an internally created report):

PDF
PNG
CSV

Step 6

Click Clear all if you'd like to reset the analytics view.

Access, Filter, and Save Video Mesh Troubleshooting Reports

Video Mesh troubleshooting reports are available on the Troubleshooting page of Control Hub (https://admin.webex.com), once Video Mesh is active and has a cluster with at least one registered Video Mesh node.

Procedure

Step 1

From the customer view in https://admin.webex.com, choose Troubleshooting, then Status, then click View Details on the Video Mesh card.

Tip

Click info to get a short description of the donut graph or chart. When done reading, click info again to flip back to the graph view.

Step 2

From the drop-down on the right, choose an option to fìlter on how far back in time you want to show data.

Last 4 Hours (Default)—When you choose this option, the graph data refreshes every 1 minute.
Last 24 Hours—When you choose this option, the graph data refreshes every 10 minutes.

Note

You can also choose All Clusters or a specific cluster to change the filtered view.

Step 3

Interact with the charts or donut graphs by using the following options as needed:

Hover over segments on the donut graph or chart view to view information about that specific data point.
Click legend items on the graph or overview to update the view on the other legend items. For example, after you select the legend item On-Premises, the line graph updates to exclude On-Premises and only include the data for the other legend items.
On a graph that shows data in a time range, narrow down to a specific time range by clicking on the left and dragging your mouse to the right. (This action affects all the related data that appears on the analytics page.)

Tip

Hover over sections of a donut, lines on a graph, or insight points on a graph to view more information on the specific point in time of the data.

Step 4

PNG
JPG
PDF
CSV
XLSX

Available analytics for Video Mesh

For details of the available analytics in Control Hub, see the Video Mesh section of Analytics for Your Cloud Collaboration Portfolio.

Monitoring Tool for Video Mesh

When you run a test, the tool creates a simulated meeting. After the test finishes, you see a simple pass or fail result with inline troubleshooting tips in the report. You can schedule the test to run periodically or run the test on demand. For more information, see https://help.webex.com/en-us/article/npgz5ph/Media-Health-Monitoring-for-Video-Mesh.

Run an Immediate Test

Use this procedure to run an on-demand media health monitoring test on all Video Mesh nodes that are in clusters registered to your Control Hub organization. The results are captured in Control Hub.

Procedure

Step 1	From the customer view in https://admin.webex.com, go to Troubleshooting, click Status, and then under the Video Mesh section, choose View Details next to Monitoring Tool.
Step 2	Mouse over or click Configure Test, and then click Run-Now.
Step 3	Click Ok to start the test.

What to do next

The results appear as data in the monitoring tool overview page in Control Hub. You can hover over the dots on the timeline to see the test results. You can also see the test results for each node.

Configure Hourly Tests

Use this procedure to configure and start hourly media health monitoring tests. You can run these tests at cluster-wide, cluster-specific, or node-specific levels. The results are captured in Control Hub.

Procedure

Step 1	From the customer view in https://admin.webex.com, go to Troubleshooting, click Status, and then under the Video Mesh section, choose View Details next to Monitoring Tool.
Step 2	Mouse over or click Configure Test, and then click Hourly.
Step 3	Choose an option: Check All Clusters if you want to run the test on all Video Mesh nodes that are in clusters registered to your Control Hub organization. Check individual cluster names if you want to run the test on all Video Mesh nodes that are in specific clusters registered to your Control Hub organization. Any unchecked cluster entries are excluded from the test. Within individual clusters, check individual node names that are in specific clusters registered to your Control Hub organization. Any unchecked node entries are excluded from the test.
Step 4	Click Next.
Step 5	Review the list of clusters and nodes that will run hourly tests. If you are satisfied, click Configure to schedule the current configuration.

What to do next

The results appear as data in the monitoring tool overview page in Control Hub. You can hover over the dots on the timeline to see the test results. You can also see the test results for each node.

Enable 1080p HD Video for On-Premises SIP Devices in Video Mesh Node Meetings

This setting allows your organization to favor 1080p high-definition video for on-premises registered SIP endpoints, with a trade off of lower meeting capacity. A Video Mesh Node must host the meeting. Participants can use 1080p 30fps video provied that:

They're all inside the corporate network.
They're using an on-premises registered high definition-capable SIP device.

The setting applies to all clusters that contain Video Mesh nodes.

Note

Cloud-registered devices continue to send and receive 1080p streams, regardless of this setting being turned on or off.

Procedure

Step 1

From the customer view in https://admin.webex.com, go to Services > Hybrid, and then click Settings on the Video Mesh card.

Step 2

Toggle on Video Quality.

If this setting is off, the default is 720p.

For video resolutions that the Webex App supports, see Video Specifications for Calls and Meetings.

Private Meetings

The Private Meeting feature enhances the security of your meeting by terminating the media on your premises. When you schedule a private meeting, the media always terminates on the Video Mesh nodes inside your corporate network with no cloud cascade.

As shown here, private meetings never cascade to the cloud. The media terminates entirely on your Video Mesh clusters. Your Video Mesh clusters can only cascade with each other.

Private meetings isolate all media to your network through Video Mesh. Unlike normal meetings, if the local nodes are full, the media does not cascade to the Webex cloud. But, by default, private meetings can cascade to different Video Mesh clusters on your network. For private meetings across geographic locations, your Video Mesh clusters must have direct connectivity to each other to allow intercluster cascades, like HQ1_VMN to Remote1_VMN in the previous figure.

All participants in a private meeting must belong to your organization. They can join using the Webex App or an authenticated video system. Participants with VPN or MRA access to your network can join a private meeting. But nobody can join a private meeting from outside your network.

You can reserve a Video Mesh cluster for private meetings. When the reserved cluster is full, the private meeting media cascades out to your other Video Mesh clusters. When the reserved cluster is full, private meetings and non-private meetings share the resources of your remaining clusters.

Non-private meetings won’t use a reserved cluster, reserving those resources for the private meetings. If a non-private meeting runs out of resources on your network, it cascades out to the Webex cloud instead.

Note

The Webex App with the Full Featured Webex Experience enabled is incompatible with Video Mesh. For details, see Clients and Devices That Use Video Mesh Node.

Support and Limitations for Private Meetings

Video Mesh supports private meetings as follows:

Private meetings are available on Webex Version 40.12 and above.
You have to schedule a meeting to use the private meeting type. See the Schedule a Cisco Webex Private Meeting article for details.
Private meetings always use the native Webex App. They never cross launch a Webex meeting.
You can use any current Video Mesh supported device.
Your nodes can use any current image: 72vCPU, 48vCPU, and 23vCPU.

Private meeting logic doesn’t create any gaps in metrics. We collect the same metrics for Control Hub as for non-private meetings.

Note

Because there're users who don't activate this feature, the analytics reports for private meetings don't appear if your org hasn't had a private meeting in 90 days.

Private meetings support 1-Way Whiteboarding from a video endpoint.

Limitations

Private meetings have these limitations:

Private meetings only support VoIP for audio. They don’t support Webex Edge Audio or PSTN.
You can’t use a personal meeting room (PMR) for a private meeting.
Private meetings don’t support Webex features that require a connection to the cloud, such as, Cloud Recording, Transcription, and Webex Assistant.
You can’t join a private meeting from an unauthenticated video system, even one with the Webex App on it.

Use Private Meetings as the Default Meeting Type

In Control Hub, you can specify that future scheduled meetings for your organization be private meetings.

Procedure

Step 1	From the customer view in https://admin.webex.com, go to Services > Hybrid.
Step 2	Click Edit settings from the Video Mesh card. Scroll to Private Meetings and enable the setting.
Step 3	Save your change.

When you enable this setting, it applies to all meetings for your organization, even those previously scheduled.

(Optional) Reserve a Cluster for Private Meetings

Private and non-private meetings normally use the same Video Mesh resources. But, because private meetings must keep media local, they can’t set up overflows to the cloud when the local resources are exhausted. To mitigate that possibility, you can set up a Video Mesh cluster to host only private meetings.

In Control Hub, you configure the cluster exclusively for hosting private meetings. This setting prevents non-private meetings from using that cluster. Private meetings default to using that cluster. If the cluster runs out of resources, private meetings cascade only to your other Video Mesh clusters.

We recommend that you provision a private cluster to handle your expected peak usage from private meetings.

Important

You can't use the short video address format (meet@your_site) if you reserve all Video Mesh clusters for private meetings. These calls currently fail without a proper error message. If you leave some clusters unreserved, calls with the short video address format can connect through those clusters.

Procedure

Step 1	From the customer view in https://admin.webex.com, go to Services > Hybrid and click Show all on the Video Mesh card.
Step 2	Select your Video Mesh cluster from the list and click Edit cluster settings.
Step 3	Scroll to Private Meetings and enable the setting.
Step 4	Save your change.

Error Messages for Private Meetings

This table lists the possible errors that users might see when joining a private meeting.


Error Message	User Action	Reason
External Network Access Denied You need to be on the corporate network to attend the Private Meeting. Paired Webex devices located outside the corporate network would not be able to join the meeting, in such a scenario try connecting your laptop, mobile to the corporate network and join the meeting in unpaired mode.	An external user joins from outside the corporate network without VPN or MRA.	To join a private meeting, external users need access to the corporate network through a VPN or MRA.
	An external user is on VPN, but they're paired to an unauthenticated device.	Device media doesn't tunnel to the corporate network through the VPN. The device can't join a private meeting. Instead, after connecting to VPN, the remote user should join a private meeting in device unpaired mode from their desktop or mobile client.
No Available Clusters The clusters hosting this private meeting are at peak capacity, unreachable, offline, or not registered. Please contact your IT admin for assistance.	A user is on the corporate network (on-premises or remote by VPN), but can’t join a private meeting.	Your Video Mesh clusters are: At capacity Unreachable Offline Not registered
Not Authorized You are not authorized to attend this Private meeting as you are not a member of the Host Organization. Please reach out to the Host of the meeting.	A user from a different org than the host org tries to join the private meeting.	Only users belonging to the host org can join a private meeting.
	A device from a different org than the host org tries to join the private meeting.	Only devices belonging to the host org can join a private meeting.

Keep your media on Video Mesh for all external Webex meetings

When your media runs through your local Video Mesh nodes, you get better performance and use less internet bandwidth.

In previous releases, you controlled the use of Video Mesh for meetings only for your internal sites. For meetings that are hosted on external Webex sites, those sites controlled if Video Mesh could cascade to Webex. If an external site didn't allow Video Mesh cascades, your media always used the Webex cloud nodes.

With the Prefer Video Mesh for All External Webex Meetings setting, if your Webex site has available Video Mesh nodes, your media runs through those nodes for meetings on external sites. This table summarizes the behavior for your participants joining Webex meetings:


Setting is...	Meeting on internal Webex site with Video Mesh cascades enabled	Meeting on internal Webex site with Video Mesh cascades disabled	Meeting on external Webex site with Video Mesh cascades enabled	Meeting on external Webex site with Video Mesh cascades disabled
Enabled	Media uses your Video Mesh nodes.	Media uses cloud nodes.	Media uses your Video Mesh nodes.	Media uses your Video Mesh nodes.
Disabled	Media uses your Video Mesh nodes.	Media uses cloud nodes.	Media uses your Video Mesh nodes.	Media uses cloud nodes.

This setting is off by default, which maintains the behavior from previous releases. In those releases, your Video Mesh didn’t cascade to Webex and your participants joined through the Webex cloud nodes.

Procedure

	Command or Action	Purpose
Step 1	In the customer view in https://admin.webex.com, go to Services > Hybrid and click Show all on the Video Mesh card.
Step 2	Select your Video Mesh cluster in the list and click Edit settings.
Step 3	Scroll to Prefer Video Mesh for All External Webex Meetings and enable the setting.
Step 4	Save your change.

Deregister Video Mesh Node

Use this procedure to remove a Video Mesh from the Webex 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

From the customer view in https://admin.webex.com, go to Services > Hybrid, and then click Show all on the Video Mesh card.

Step 2

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.

Step 3

After you read and understand the message, click Deregister Node.

Move Video Mesh 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 Video Mesh node. After completing this procedure, your node will only be available to the new resource.

Procedure

Step 1	From the customer view in https://admin.webex.com, go to Services > Hybrid, and then choose Show all on the Video Mesh card.
Step 2	From the list, select the node that you want to move and then click Actions (the vertical ellipsis).
Step 3	Select Move Node.
Step 4	Choose the appropriate radio button for where you want to move the node: Select an existing cluster—Choose an existing cluster from the drop-down list. Create a new cluster—Enter a name for the new cluster in the field.
Step 5	Click Move Node. Your node moves to the new cluster.

Set Video Mesh Cluster Upgrade Schedule

You can set a specific upgrade schedule or use the default schedule of 3 a.m. Daily United States: America/Los Angeles. You can also choose to postpone an upcoming upgrade, if necessary.

Software upgrades for Video Mesh are done automatically at the cluster level, which ensures that all nodes are always running the same software version. Upgrades are done according to the upgrade schedule for the cluster. When a software upgrade becomes available, you have can manually upgrade the cluster before the scheduled upgrade time.

Before you begin

Note

Urgent upgrades are applied as soon as they are available.

Procedure

Step 1

From the customer view in https://admin.webex.com, go to Services > Hybrid, and then click View all on the Video Mesh card.

Step 2

Click a media resource and then click Edit cluster settings.

Step 3

On the Settings page, scroll to Upgrade, and then choose the time, frequency, and time zone for the upgrade schedule.

Note

Upgrades may take longer than a few minutes if the Video Mesh 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.

Step 4

(Optional) If needed, click Postpone to defer the upgrade one time, until the subsequent window.

Under the time zone, the next available upgrade date and time are displayed.

Upgrade Behavior

The node makes periodic requests to the cloud to see if an update is available.
The cloud does not make the upgrade available until the cluster's upgrade window arrives. Once the upgrade window arrives, the update information is given to the node during its next periodic update request to the cloud.
The node pulls updates over a secure channel.
Existing services are gracefully shut down so that no new calls are routed to the node, and existing calls have time to complete (up to 2 hours).
The upgrade is installed.
The cloud only triggers the upgrade for a percentage of nodes at a time in a cluster.

Delete Video Mesh Cluster

You can permanently delete a Video Mesh cluster from the Webex 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

Step 1

From the customer view in https://admin.webex.com, go to Services > Hybrid, and then click View all.

Step 2

From the list of resources, scroll to the Video Mesh resource that you want to delete, and then click Edit Cluster Settings.

Tip

You can click Video Mesh to filter on just Video Mesh resources.

Step 3

Click Delete Cluster, and then choose one:

Click Move All Nodes. For each node, either create a new resource by choosing an existing resource from the drop-down list or entering a new name, and then click Continue.
Click Deregister All Nodes, check the check box, and then click Delete Cluster.

Deactivate Video Mesh

Deactivating Video Mesh removes the ability to have media remain on-premises for your meetings. Also, all in-progress meetings using Video Mesh nodes end and future meetings are hosted in the cloud. Once deactivated, the only way to use Video Mesh is to deploy it from the beginning.

Before you begin

Before you deactivate Video Mesh, you will deregister all Video Mesh nodes.

Procedure

Step 1	From the customer view in https://admin.webex.com, go to Services > Hybrid, choose Settings on the Video Mesh card.
Step 2	Click Deactivate.
Step 3	Review the list of clusters and read the disclaimer in the dialog.
Step 4	Check the check box to confirm that you understand this action, and click Deactivate on the dialog.
Step 5	When you are ready to deactivate your Video Mesh, click Deactivate Service. Deactivation removes all Video Mesh nodes and clusters. Video Mesh is no longer configured.

Troubleshoot Video Mesh Node Registration

This section contains possible errors you may encounter during registration of your Video Mesh node to the Webex 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 Video Mesh node are not correct.

Solution Sign in to the console of your Video Mesh 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 Video Mesh node cannot connect to the Webex cloud.

Solution Make sure your network allows connectivity on the ports required for Video Mesh. For details, see Ports and Protocols Used by Video Mesh.

Manage Video Mesh Node From the Web Interface

Before you can make any network changes to Video Mesh nodes that are registered to the cloud, you must use Control Hub to put them in maintenance mode. For more information and a procedure to follow, see Move a Node Into Maintenance Mode.

Caution

Maintenance mode is intended solely to prepare a node for shutdown or reboot so that you can make certain networking setting changes (DNS, IP, FQDN) or prepare for hardware maintenance such as replace RAM, hard drive, and so on.

When you place a node into maintenance mode, it does a graceful shutdown of calling services (stops accepting new calls and waits up to 2 hours for existing calls to complete). The purpose of the graceful shutdown of calling services is to allow reboot or shutdown of the node without causing dropped calls.

How to access the Video Mesh overview

You can open the web interface in either of these ways:

If you are a Full Administrator and you already registered the node to the cloud, you can access the node from Control Hub.

From the customer view in https://admin.webex.com, go to Services > Hybrid. Under Resources on the Video Mesh card, click View all. Click on the cluster, and then click on the node that you want to access. Click Go to Node.

Only a Full Administrator for your Webex organization can use this feature. Other administrators, including Partner and External Full Administrators, don't have the Go To Node option for the Video Mesh resources.
In a browser tab, navigate to <IP address>/setup, for example, https://192.0.2.0/setup. Enter the admin credentials that you set up for the node, and then click Sign In.

If the admin account has been disabled, this method is not available. See the "Disable or Re-enable the Local Admin Account from Web Interface" section.

The overview is the default page and has the following information:

Call Status—Provides the number of ongoing calls through the node.
Node Details—Provides the node type, software image, software version, OS version, QoS status, and maintenance mode status.
Node Health—Provides usage data (CPU, memory, disk), and service status (Management Service, Messaging Service, NTP Sync).
Network Settings—Provides network information: hostname, interface, IP, gateway, DNS, NTP, and whether dual IP is enabled.
Registration Details—Provides registration status, organization name, org ID, cluster the node is a part of, and cluster ID.

Cloud Connectivity—Runs a series of tests from the node to the Webex cloud and third party destinations that the node needs to access to run properly.

Three types of tests are run: DNS resolution, server response time, and bandwidth.

Note

DNS tests validate that the node can resolve a particular domain. These tests report as failed if the server does not respond within 10 seconds. They show as "Passed" with an orange "warning color" if the response time is between 1.5 and 10 seconds. The periodic DNS checks on the node generate alarms if the DNS response time is longer than 1.5 seconds.
Connect tests validate that the node can connect to a particular HTTPS URL and receive a response (responses other than proxy or gateway errors are accepted as evidence of connection).
The list of tests run from the overview page are not exhaustive and do not include port 444 or websocket tests.
The node sends alarms if calling processes cannot complete websocket connections to the cloud or connect to call-related services.

A Pass or Fail result appears next to each test; you can hover over this text to see more information about what was checked when the test ran.

As shown in the screenshot that follows, alarm notifications can also appear in the side panel, if any alarms were generated by the node. These notifications identify potential issues on the node and make suggestions for how you can troubleshoot or resolve these issues. If no alarms were generated, the notification panel does not appear.

Figure 1. Example of the Overview Page in the Video Mesh Node Web Interface

Configure Network Settings From Video Mesh Node Web Interface

If your network topology changes, you can use the web interface for each Webex Video Mesh node and change the network settings there. 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 Webex Video Mesh node settings.

Procedure

Step 1

Open the Webex Video Mesh node interface.

Step 2

Go to Network.

The current network settings for the node appear.

Step 3

Change the following settings for Host and Network Configuration as needed:

Under Edit Hostname and Domain, change the Hostname and Domain values.
An error is displayed if the FQDN (hostname and domain) does not have the correct format.
Under Network Mode, Enable DHCP is listed, but DHCP is not supported. You must set a static IP address, subnet mask, and gateway.

Under Edit Network Configuration, change the IP Address (for the internal interface), Subnet Mask, and Gateway(a network node that serves as an access point to another network) values.

Note

The Video Mesh 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 Video Mesh Node internal use. The default reserved IP address range is 172.17.42.0–172.17.42.63, which can be configured later in the Diagnostic menu in the node console. This IP address range is for communication within the Video Mesh Node and between the software containers which hold the different components of the node—for example, SIP interface and media transcoding.

Under Edit DNS Servers, change the DNS server entries, which handle translating domain names to numeric IP addresses. You can enter up to 4 DNS servers.

Step 4

Click Save Host and Network Configuration, and after the popup appears that says the node needs to reboot, click Save and Reboot.

During the save, all fields are validated on the server side. Warnings that appear generally indicate that the server isn't reachable or a valid response wasn't returned when queried—for example, if the FQDN 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. Another possible error state is if the gateway address is not in the same subnet as the IP address. After the Video Mesh Node reboots, the network configuration changes take effect.

Step 5

Change the following settings for NTP Servers as needed:

Under Edit NTP Servers, change the values for the NTP server entries, which are used in your organization to synchronize time to the node.

Step 6

Click Save NTP Servers.

If the NTP server is an FQDN and that isn’t resolvable, a warning is returned. If the NTP server FQDN is resolved but the resolved IP can't be queried for NTP time, a warning is returned.

Set The External Network Interface From The Video Mesh Node Web Interface

If your network topology changes, you can use the web interface for each Webex Video Mesh node and change the network settings there. You may see a caution about changing the network settings. However, you can still save the changes in case you're making changes to your network after changing Webex Video Mesh node settings.

You can configure the external network interface if you're deploying the Video Mesh Node in your network's DMZ so that you can isolate the enterprise (internal) traffic from the outside (external) traffic.

Procedure

Step 1	Open the Webex Video Mesh node interface.
Step 2	Go to Network. The current network settings for the node appear.
Step 3	Click Advanced.
Step 4	Toggle on Enable External Network and then click Ok to enable the external IP address options on the node.
Step 5	Enter the External IP Address, External Subnet Mask, and External Gateway values.
Step 6	Click Save External Network Configuration.
Step 7	Click Save and Reboot to confirm the change. The node reboots to enable the dual IP address, and then automatically configures the basic static routing rules. These rules determine that traffic to and from a private class IP address uses an internal interface; traffic to and from a public class IP address uses an external interface. Later, you can create your own routing rules—For example, if you need to configure an override and allow access to an external domain from the internal interface.
Step 8	If there are errors, click Ok to close the error dialog box, fix the errors, and click Save External Network Configuration again.

What to do next

To validate the internal and external IP address configuration, do the steps in Run a Ping from Video Mesh Node Web Interface.

Test an external destination (example, cisco.com); if successful, the results show that the destination was accessed from the external interface.
Test an internal IP address; if successful, the results show that the address was accessed from the internal interface.

Add Internal and External Routing Rules From Video Mesh Node Web Interface

In a dual network interface (NIC) deployment, you can fine tune the routing for Video Mesh nodes by adding user-defined route rules for external and internal interfaces. The default routes are added to the nodes, but you can make exceptions—for example, external subnets or host addresses that need to be accessed through the internal interface, or internal subnets or host addresses that need to be accessed from the external interface. Perform the following steps as needed.

Before you begin

To configure routing rules, you must first enable and configure the external network interface.

Procedure

Step 1

Open the Webex Video Mesh node interface.

Step 2

Go to Network.

The current network settings for the node appear. If you have configured the external network, the Routing Rules tab appears.

Step 3

Click the Routing Rules tab.

The first time you open this page, the default system routing rules appear in the list. By default, all internal traffic goes through the internal interface and external traffic through the external interface.

You can add manual overrides to these rules in the next steps.

Step 4

To add a rule, click Add Routing Rule, then choose one of the following option:.

For Network Type, click Internal, and then enter the external subnet or host IP address to use for the internal route.
For Network Type, click External, and then enter the internal subnet or host IP address to use for the external route.

Step 5

Click Add Routing Rule.

As you add each rule, they appear in the routing rule list, categorized as user defined rules.

Step 6

To delete one or more user-defined rules,check the check box in the column to the left of the rules and then click Delete Routing Rule(s).

Note

The default routes cannot be deleted, but you can delete any user-defined overrides that you configured.

Caution

Custom routing rules may create potential for conflicts with other routing. For example, you may define a rule that freezes your SSH connection to the Video Mesh Node interface. If this happens, do one of the following and then remove or modify the routing rule:

Open an SSH connection to the public IP address of the Video Mesh Node.
Access the Video Mesh Node through the ESXi console

Configure Container Network From Video Mesh Node Web Interface

Video Mesh node reserves a subnet range for internal use within the node. The default range is 172.17.42.0–172.17.42.63. The nodes do not respond to any external-to-Video Mesh node traffic originating from this range. You may want to use the node console to change the container bridge IP address to avoid conflicts with other devices in your network.

Procedure

Step 1	Open the Webex Video Mesh node interface.
Step 2	Go to Network. The current network settings for the node appear.
Step 3	Click Advanced.
Step 4	Change the values for Container IP Address and Container Subnet Mask, as needed, and then click Save Container Network Configuration.
Step 5	Click Save and Reboot to confirm the change.
Step 6	If there are errors, click Ok to close the error dialog box, fix the errors, and click Save Container Network Configuration again.

Set the Network Interface MTU Sizes

All Webex Video Mesh nodes have path MTU (PMTU) discovery enabled by default. With PMTU, the node can detect MTU issues and adjust the MTU size automatically. When PMTU fails because of firewall or network issues, the node can have connectivity issues to the cloud because packets larger than the MTU drop. Manually setting a lower MTU size can fix this issue.

Before you begin

If you've already registered the node, you must put the node in maintenance mode before you can change the MTU settings.

Procedure

Step 1	Open the Webex Video Mesh node interface.
Step 2	Go to Network. The current network settings for the node appear.
Step 3	Click Advanced.
Step 4	In the Interface MTU Settings section, enter an MTU value between 1280 and 9000 bytes in the applicable field(s). If you have enabled the external interface, you can set both the internal and external interface MTU sizes separately.

The node reboots to apply the MTU changes.

What to do next

If you put the node in maintenance mode to change the MTU, turn off maintenance mode.

Enable or Disable DNS Caching

If DNS responses to your Video Mesh nodes regularly take more than 750 ms, or if the Cisco TAC recommends it, you can enable DNS caching. With DNS caching on, the node caches DNS responses locally. With the cache, requests are less prone to delay or timeouts that can lead to connectivity alarms, call drops, or call quality issues. DNS caching can also reduce the load on your DNS infrastructure.

Before you begin

Move the node to maintenance mode. When the maintenance mode status is On (active calls have completed or have dropped at the end of the pending period), you can enable or disable DNS caching.

Procedure

Step 1	Open the Webex Video Mesh node interface.
Step 2	Go to Network. The current network settings for the node appear.
Step 3	Click Advanced.
Step 4	In the DNS Caching Configuration section, toggle Enable DNS Caching on or off.
Step 5	In the confirmation dialog, click Save and Reboot.
Step 6	After the node reboots, reopen the Webex Video Mesh node interface and confirm that the connectivity checks are succeeding on the Overview page.

When you enable DNS caching, the DNS Cache Statistics displays the following statistics:


Statistic	Description
Cache Entries	The number of previous DNS resolutions that the DNS Cache server has stored
Cache Hits	The number of times since the cache reset that the cache handled a DNS request from Video Mesh, without querying the customer DNS server
Cache Misses	The number of times since the cache reset that the customer DNS server handled a DNS request from Video Mesh rather than through the cache
Cache Hit Percent	The percent of DNS requests from Video Mesh that the cache handled without querying the customer DNS server
Cache Server Outbound DNS queries	The number of DNS queries that the Video Mesh DNS cache server made against the customer DNS servers
Cache Server Inbound DNS queries	The number of DNS queries that Video Mesh made against its internal DNS Cache server
Outbound to Inbound Query Ratio	The ratio of DNS queries made by Video Mesh against the customer DNS server to the queries made by Video Mesh against its internal DNS Cache server
Inbound Queries Per Second	The average number of DNS queries per second that Video Mesh made against its internal DNS Cache server
Outbound Queries Per Second	The average number of DNS queries per second that Video Mesh made against the customer DNS servers
Outbound DNS Latency [time range]	The percent of DNS queries that Video Mesh made against the customer DNS servers where the response time fell into the described time range

Use the Wipe DNS Cache button to reset the DNS cache when TAC requests. After wiping the DNS cache, you see a higher Outbound to Inbound Query Ratio as the cache replenishes. You don't need to place the node in maintenance mode to wipe the cache.

What to do next

Move the node out of maintenance mode. Then repeat the task on any other nodes that require a change.

Upload Security Certificates

Set up a trust relationship between the node and an external server, such as a syslog server.

Note

In a clustered environment, you must install CA and server certificates on each node individually.

Procedure

Step 1

Open the Webex Video Mesh node interface.

Step 2

When setting up TLS with another server, such as a syslog server, we recommend for security reasons that you use a CA signed certificate on your Video Mesh nodes instead of the node's default self-signed certificate. To create and upload the certificate and key pairs on the Video Mesh node, go to Server Certificates, and follow these steps:

If you need a certificate issued from a certified provider, click Create a Certificate Signing Request. Fill out the required information (including the Subject Alternative Name(s), which are FQDNs that must contain the common name). Then, generate and download the CSR to submit the request to the provider. You can create multiple CSRs. The provider returns the certificate authority (CA) signed certificate. (The CSR creation step already generated the private key.)

Note

The common name is not a URL. It doesn’t include any protocol (e.g. http:// or https://), port number, or pathname. The commonName field in the X.509 certificate specification technically represents the common name. For https://www.example.com, the correct value is example.com.

When you have the certificate and key, click Upload a Server Certificate (.crt or .pem file), choose the certificate file, then click Upload a Private Key (.key file) and enter a passphrase if you have one.

The private key is already in place when a CSR is generated. You only need to upload a private key if you do not use the CSR creation step.
After you get the certificate, go to the first Video Mesh node in a cluster, click Install Server Certificate, read the prompt, click Install, then click OK.

A Video Mesh node that's registered to the cloud waits up to 2 hours for any calls to end and puts itself into a temporary inactive state (quiesces). Once either the existing calls finish or 2 hours pass (whichever comes first), this node completes the certificate installation. A prompt appears when the server certificate installation completes, and you can then reload the page to view the new certificate and key entry.
Click Download next to the certificate and key files to save a local copy.

Save the files somewhere that's easy to remember and leave the instance open in the browser tab.
Go to the second Video Mesh node in the cluster, fill in the passphrase, and then upload the private key file. Then click Upload a Server Certificate and then choose Install Server Certificate, read the prompt, click Install, then click OK.
Repeat these steps on every other Video Mesh node in the same cluster.

Step 3

Choose an option depending on how the external server's CA certificate is signed:

If the server's CA certificate is signed by a generally recognized organization, such as DigiCert, GeoTrust, or GlobalSign, the Video Mesh node will trust it based on the list of root certificates from the Video Mesh node's host OS, which are updated periodically. Skip to Step Step 6.
If the server's CA certificate is signed by an internal enterprise CA root certificate, the root certificate from that authority must be added to the Video Mesh node. Continue with the next step.

Step 4

Get the certificate or certificate trust list (CTL) that the external server uses.

As with the Video Mesh node certificate, save the external server file somewhere that's easy to remember.

Step 5

Go back to the Webex Video Mesh node interface tab, click Trust Store & Proxy, then choose an option:

To install a single CA certificate, click Upload a Root Certificate or End Entity Certificate (.crt or .pem file), and then choose the certificate file from your computer, click Install All Certificates into the Trust Store, read the prompt, click Install, and then reboot the node.
To install a certificate chain, upload the root CA certificate and intermediate CA certificate, and then click Install All Certificates into the Trust Store, read the prompt, and then click Install.

A Video Mesh node that's registered to the cloud waits up to 2 hours for any calls to end and puts itself into a temporary inactive state (quiesces). To install the certificate, the node must reboot and does so automatically. When it comes back online, a prompt appears when the certificate is installed on the Video Mesh node, and you can then reload the page to view the new certificate.

Step 6

Repeat the certificate or certificate chain upload on every other Video Mesh node in the same cluster.

Generate Video Mesh Logs for Support

You may be instructed to send logs directly to Cisco, or you can download them yourself to attach to a case. Use this procedure from the web interface to generate logs and send them to Cisco or download them from any Video Mesh nodes. The generated log package contains media logs, system logs, and container logs. The bundle provides useful information for connectivity to Webex, platform issues, and call setup or media, so that Cisco can troubleshoot your Video Mesh node deployment for you.

Procedure

Step 1

Open the Webex Video Mesh node interface.

Step 2

Go to Troubleshooting, and then choose an option next to Send Logs:

Click Send Logs to Cisco to generate a log bundle from the node and send the bundle directly to Cisco in one step. You'll see a status indicator that changes as the logs are compressed, zipped, and uploaded.
Click Download to generate a long bundle from the node that you can save locally or attach to a case later.

Generated logs are historically stored on the node and remain on the node even after reboots. An upload identifier shows on the page. Support uses this value to identify your uploaded logs.

Step 3

When you open a case or interact with the Cisco TAC, include the upload identifier value so that your support engineer can access the logs.

If you submitted the log to Cisco directly, you don't need to upload the log bundle to the TAC case.

What to do next

While logs are uploading to Cisco or being downloaded, you can run a packet capture from the same screen.

Generate Video Mesh Packet Captures for Support

You can run a packet capture (PCAP) and submit it to Cisco for further analysis. A packet capture takes a snapshot of data packets that go through the node's network interfaces. After packets are captured and submitted, Cisco can analyze the submitted capture and help with troubleshooting your Video Mesh node deployment.

Before you begin

Caution

The packet capture functionality is intended for debugging purposes only. If you run a packet capture on a live Video Mesh node that is hosting active calls, the packet capture may affect the performance of the node and the generated file might be overwritten. This causes a loss of captured data. We recommend that you run the packet capture only during off peak hours or when the call count is less than 3 on the node.

Procedure

Step 1	Open the Webex Video Mesh node interface.
Step 2	Go to Troubleshooting. You can start the packet capture and upload logs at the same time.
Step 3	(Optional) In the Packet Capture section, you can limit the capture to packets on a specific interface, filter by packets to or from specific hosts, or filter by packets on one or more ports.
Step 4	To begin the process, toggle on the Start Packet Capture setting.
Step 5	When you are done, toggle off the Start Packet Capture setting.
Step 6	Choose one: Click Send PCAP to Cisco to send the packet capture from the node directly to Cisco. You'll see a status indicator that changes as the packet capture is uploaded. Click Download to save a local copy of the packet capture from the node. You can attach it to a case later. After a package capture is uploaded, an upload identifier shows on the page. Support uses this value to identify your uploaded packet capture. The maximum size for packet captures is 2 GB.
Step 7	When you open a case or interact with the Cisco TAC, include the upload identifier value so that your support engineer can access the packet capture.

Run a Ping from Video Mesh Node Web Interface

You can run a ping from the Video Mesh node web interface. This step tests a destination you enter and sees if the Video Mesh node can reach it.

Procedure

Step 1

Open the Webex Video Mesh node interface.

Step 2

Go to Troubleshooting, scroll to Ping, and then enter a destination address that you want to test in the FQDN or IP Address field under Test Connectivity Using Ping.

Step 3

Click Ping.

The test runs and you'll see a ping success or failure message. The test does not have a timeout limit. If you receive a failure or the test runs indefinitely, check the destination value that you entered and your network settings.

Run a Trace Route from Video Mesh Web Interface

You can run a traceroute from the Video Mesh node web interface. This step shows the route taken by packets from the node towards the destination that you enter. Viewing the traceroute information helps you determine why a particular connection might be poor and can help you identify problems.

Procedure

Step 1

Open the Webex Video Mesh node interface.

Step 2

Go to Troubleshooting, scroll to Traceroute, and then enter a destination address that you want to test in the FQDN or IP Address field under Trace Route to Host.

The test runs and you'll see trace route success or failure message. The test times out at 16 seconds. If you receive a failure or the test times out, check the destination value that you entered and your network settings.

Check NTP Server from Video Mesh Node Web Interface

You can enter a FQDN or IP address of a network time protocol (NTP) server to confirm that the Video Mesh node can access the server. This test is helpful if you notice time synchronization issues and want to rule out the reachability of the NTP server.

Procedure

Step 1

Open the Webex Video Mesh node interface.

Step 2

Go to Troubleshooting, scroll to Check NTP Server, and then enter a destination address that you want to test in the FQDN or IP Address field under View SNTP Query Response.

The test runs and you'll see a query success or failure message. The test does not have a timeout limit. If you receive a failure or the test runs indefinitely, check the destination value that you entered and your network settings.

Identify Port Issues With Reflector Tool in the Web Interface

The reflector tool (a combination of a server on the Video Mesh node and client through a Python script) is used to verify whether the required TCP/UDP ports are open from Video Mesh nodes.

Before you begin

Download a copy of the Reflector Tool Client (a Python script) from https://github.com/CiscoDevNet/webex-video-mesh-reflector-client
For the script to work properly, ensure that you're running Python 2.7.10 or later in your environment.
Currently, this tool supports SIP endpoints to Video Mesh nodes and intracluster verification.

Procedure

Step 1	From the customer view in https://admin.webex.com, enable maintenance node for the Video Mesh Node by following these instructions.
Step 2	Wait for the node to show a 'Ready for maintenance' status in Control Hub.
Step 3	Open the Webex Video Mesh node interface. For instructions, see Manage Video Mesh Node From the Web Interface.
Step 4	Scroll to Reflector Tool, and then start either the TCP Reflector Server or UDP Reflector Server, depending on what protocol you want to use.
Step 5	Click Start Reflector Server, and then wait for the server to start successfully. You'll see a notice when the server starts.
Step 6	From a system (such as a PC) on a network that you want Video Mesh nodes to reach, run the script with the following command: `$ python <local_path_to_client_script>/reflectorClient.py --ip <ip address of the server> --protocol <tcp or udp>` At the end of the run, the client shows a success message if all the required ports are open: The client shows a failed message if any required ports are not open:
Step 7	Resolve any port issues on the firewall and then rerun the above steps.
Step 8	Run the client with --help to get more details.

Enable Debug User Account From Video Mesh Node Web Interface

If support requires access to the Webex Video Mesh node, you can temporarily enable a debug user account so that support can run further troubleshooting.

Procedure

Step 1

Open the Webex Video Mesh node interface.

Step 2

Go to Troubleshooting, and then toggle on the Enable Debug User setting.

An encrypted passphrase appears that you can provide to Cisco support.

Step 3

Copy the passphrase, paste it in the support ticket or directly to the support engineer, and then click OK when you have it saved.

The debug user account is valid for 3 days, after which it expires.

What to do next

You can disable the account before it expires if you return to the Troubleshooting page and then toggle off the Enable Debug User setting.

Factory Reset a Video Mesh Node From The Web Interface

As part of deregistration cleanup, you can factory reset the Video Mesh node from the web interface. 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 another cluster that you build from scratch.

Before you begin

You must use Control Hub to deregister the Video Mesh node from the cluster that's registered in Control Hub.

Procedure

Step 1

Open the Webex Video Mesh node interface.

Step 2

Go to Troubleshooting, scroll to Factory Reset, and then click Reset Node.

Step 3

Ensure that you understand the information in the warning prompt that appears, and then click Reset and Reboot.

The node reboots automatically after the factory reset.

Disable or Re-enable the Local Admin Account From Web Interface

When you install a Webex Video Mesh node, you initially sign in using a built-in local account with the user name "admin." Once you register the node to the Webex cloud, you can use your Webex organization administration credentials to manage your Video Mesh nodes from Control Hub. This way, the administrator account policy and management processes that apply to Control Hub also apply to your Video Mesh nodes. For further control, you can disable the built-in "admin" account so that Control Hub handles all administrator authentication and management.

Use these steps after you have registered the node to the cloud to disable (or later re-enable) the admin user account. When you disable the admin account, you must use Control Hub to access the node web interface.

Important

Only a Full Administrator for your Webex organization can use this feature. Other administrators, including Partner and External Full Administrators, don't have the Go To Node option for the Video Mesh resources.

Procedure

Step 1

From the customer view in https://admin.webex.com, go to Services > Hybrid.

Step 2

Under Resources on the Video Mesh card, click View all.

Step 3

Click on the cluster and then click on the node that you want to access. Click Go to Node.

Step 4

Go to Administration.

Step 5

Toggle the Enable Admin User switch off to disable the account, or on to re-enable it.

Note

You can't disable the admin account until you've registered the node to the cloud.

Step 6

On the confirmation screen, click Disable or Enable to complete the change.

Once you disable the admin user, you can't sign in to the Video Mesh node through the WebUI or the CLI launched from SSH. However, you can sign in using the admin user credentials through a CLI launched from the VMware ESXi console.

Change Admin Passphrase From Web Interface

Use this procedure to change the administrator passphrase (password) for your Webex Video Mesh node by using the web interface.

Procedure

Step 1	Open the Webex Video Mesh node interface.
Step 2	Go to Administration, and next to Change Passphrase, click Change.
Step 3	Enter the Current Passphrase, and then enter a new passphrase value in both New Passphrase and Confirm New Passphrase.
Step 4	Click Save Passphrase. A "password changed" message appears and then you go back to the sign in screen.
Step 5	Sign in using your new admin login and passphrase (password).

Change Passphrase Expiry Interval From the Web Interface

Use this procedure to change the default passphrase expiry interval of 90 days by using the web interface. When the interval is up, you are prompted to enter a new passphrase when you sign into the Video Mesh node.

Procedure

Step 1

Open the Webex Video Mesh node interface.

Step 2

Go to Administration, and next to Change Passphrase Expiry, enter a new value for Expiry Interval (Days) (up to 365 days), and then click Save Passphrase Expiry Interval.

A success screen appears, and you can then click OK to finish.

The Administration page also shows dates for the last passphrase change and the next time the password expires.

Set External Logging to a Syslog Server

Note

This feature is currently available only for FedRamp deployments.

If you have a syslog server, you can set your Webex Video Mesh node to log to the external server audit trail information, such as:

Details on administrator sign-ins
Configuration changes (including turning maintenance mode on or off)
Software updates

The node aggregates the logs, if any, and sends them to the server every ten minutes.

Procedure

Step 1	Open the Webex Video Mesh node interface.
Step 2	Go to Administration.
Step 3	Next to External Logging, toggle on Enable External Logging.
Step 4	For Syslog Server Details, enter the host IP address or fully-qualified domain name and the syslog port. If the server isn’t DNS-resolvable from the node, use an IP address in the Host field.
Step 5	Choose the Protocol—UDP or TCP. To use TLS encryption, choose TCP and then toggle on Enable TLS. Make sure that you also upload and install the security certificates required for TLS communication between the node and the syslog server. If no certificates are installed, the node defaults to using its self-signed certificates. For help, see Upload Security Certificates.
Step 6	Click Save External Logging Configuration.

The properties of the log message follow this format: Priority Timestamp Hostname Tag Message.


Property	Description
Priority	The value is always 131, based on the formula: Priority = (Facility Code * 8) + Severity. The facility code is 16 for "local0". The severity is 3 for "notice".
Timestamp	The timestamp format is "Mmm dd hh:mm:ss".
Hostname	The hostname for the Video Mesh node.
Tag	The value is always syslogAuditMsg.
Message	The message is a JSON string of at least 1KB. Its size depends on the number of aggregated events in the ten minute interval.

Here is an example message:

{
  "events": [
    {
      "event": "{\hostname\": \"test-machine\", \"event_type\": \"login_success\",
       \"event_category\": \"node_events\", \"source\": \"mgmt\", \"session_data\":
       {\"session_id\": \"j02wH5uFTKB22SqdYCrzPrqDWkXIAKCz\", \"referer\":
       \"https://IP address/signIn.html?%2Fsetup\", \"url\":
       \"https://IP address/api/v1/auth/signIn\", \"user_name\": \"admin\",
       \"remote_address\": \"IP address\", \"user_agent\": \"Mozilla/5.0
       (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko)
       Chrome/87.0.4280.67 Safari/537.36\"}, \"event_data\": {\"type\": \"Conf_UI\"},
       \"boot_id\": \"6738705b-3ae3-4978-8502-13b74983e999\", \"timestamp\":
       \"2020-12-07 22:40:27 (UTC)\", \"uptime\": 358416.23, \"description\":
       \"Log in to Console or Web UI successful\"}"
    },
    {
      "event": "{\hostname\": \"test-machine\", \"event_type\":
       \"software_update_completed\", \"event_category\": \"node_events\", \"source\":
       \"mgmt\", \"event_data\": {\"release_tag\": \"2020.12.04.2332m\"}, \"boot_id\":
       \"37a8d17a-69d8-4b8c-809d-3265aec56b53\", \"timestamp\":
       \"2020-12-07 22:17:59 (UTC)\", \"uptime\": 137.61, \"description\":
       \"Completed software update\"}"
    }
  ]
}

Deployment Guide for Video Mesh

Bias-Free Language

Results

Chapter: Manage and Troubleshoot Video Mesh

Manage and Troubleshoot Video Mesh

Video Mesh Analytics

Analytics

Recent Resource Usage

Access, Filter, and Save Video Mesh Analytics

Procedure

Access, Filter, and Save Video Mesh Troubleshooting Reports

Procedure

Available analytics for Video Mesh

Monitoring Tool for Video Mesh

Run an Immediate Test

Procedure

What to do next

Configure Hourly Tests

Procedure

What to do next

Enable 1080p HD Video for On-Premises SIP Devices in Video Mesh Node Meetings

Procedure

Private Meetings

Support and Limitations for Private Meetings

Limitations

Use Private Meetings as the Default Meeting Type

Procedure

(Optional) Reserve a Cluster for Private Meetings

Procedure

Error Messages for Private Meetings

Keep your media on Video Mesh for all external Webex meetings

Procedure

Deregister Video Mesh Node

Procedure

Move Video Mesh Node

Procedure

Set Video Mesh Cluster Upgrade Schedule

Before you begin

Procedure

Delete Video Mesh Cluster

Procedure

Deactivate Video Mesh

Before you begin

Procedure

Troubleshoot Video Mesh Node Registration

The domain could not be resolved

Could not connect to site using port 443 via SSL

Manage Video Mesh Node From the Web Interface

How to access the Video Mesh overview

Configure Network Settings From Video Mesh Node Web Interface

Procedure

Set The External Network Interface From The Video Mesh Node Web Interface

Procedure

What to do next

Add Internal and External Routing Rules From Video Mesh Node Web Interface

Before you begin

Procedure

Configure Container Network From Video Mesh Node Web Interface

Procedure

Set the Network Interface MTU Sizes

Before you begin

Procedure

What to do next

Enable or Disable DNS Caching

Before you begin

Procedure

What to do next

Upload Security Certificates

Procedure

Generate Video Mesh Logs for Support

Procedure

What to do next

Generate Video Mesh Packet Captures for Support

Before you begin

Procedure

Run a Ping from Video Mesh Node Web Interface

Procedure

Run a Trace Route from Video Mesh Web Interface

Procedure

Check NTP Server from Video Mesh Node Web Interface