Have an account?

  •   Personalized content
  •   Your products and support

Need an account?

Create an account

Deployment Guide for Cisco Webex Video Mesh

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Deployment Guide for Cisco Webex Video Mesh

Chapter Title

Manage and Troubleshoot Webex Video Mesh

Results

Updated:
February 9, 2021

Chapter: Manage and Troubleshoot Webex Video Mesh

Manage and Troubleshoot Webex Video Mesh

Webex Video Mesh Analytics

Analytics provide information about how you use your on-premises Webex Video Mesh nodes and clusters in your Cisco Webex organization. With the historical data in the metrics view, you can more effectively manage your Webex 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 Webex Video Mesh nodes to a cluster or creating new clusters, for example. Webex Video Mesh analytics can be found in Cisco Webex 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

Webex 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 Cisco Webex 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 Webex Video Mesh Analytics

Webex Video Mesh metric reports are available on the Analytics page of Cisco Webex Control Hub (https://admin.webex.com), once Webex Video Mesh is active and has a cluster with at least one registered Webex 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 fì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 Webex Video Mesh Troubleshooting Reports

Webex Video Mesh troubleshooting reports are available on the Troubleshooting page of Cisco Webex Control Hub (https://admin.webex.com), once Webex Video Mesh is active and has a cluster with at least one registered Webex 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 fì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

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):

  • PNG

  • JPG

  • PDF

  • CSV

  • XLSX

Available Analytics

Engagement

Call Join Activity and Overview

This chart provides a summary and historical trend of call join activity based on where the organization's calls were hosted. The chart gives an overall perspective of the number of calls hosted on the cloud compared to the number of calls that were hosted on on-premises clusters in an organization.

  • Cloud Calls —Number of call joins that could not use the Video Mesh Nodes, because of no connection to the enterprise network or the calls being subject to enforced policy.

  • Overflowed to Cloud—Number of call joins made within an enterprise network but overflowed to a cloud node.

  • On-Premises —Number of calls hosted on any of the enterprise nodes.

Client Type Usage and Overview

This report provides a summary and historical trend of common categories of meeting clients that are used in the organization. This data helps you have access to the most popular categories of client types and assess utilization in the organization.

Common meeting type clients include the following:

  • Webex Teams for mobile (iPad, iPhone, Android)

  • Webex Teams for desktop (Windows, Mac, web)

  • Webex Devices (Room/Desk/Board, Video Endpoints)

  • Webex Meetings for desktop (Windows, Mac, Web)

  • Webex Meetings for Mobile (iPad, iPhone, Android)

  • Webex Meetings Center (Windows, Mac)

  • Jabber for desktop (Windows, Mac)

  • Jabber for mobile (iOS, Android)

  • PSTN Dial In

  • SIP Devices

  • Desk Phones

Meeting Details and Resources

This report provides a summary and historical trend of the number meetings events at a specific point in time and 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

Resources

Node Availability Per Cluster, Total Node Availability, and Overflow to Cloud

This report shows a percentage of node availability for each cluster that can host calls, an overview of the percentage of clusters that can host calls, and an overview of the calls that overflowed to a cloud cluster. This data helps you gain an overall perspective of offending clusters at the organization level. Click on any of these clusters to filter all the associated graphs to show details that are related to the selected cluster.  

Node Availability Across On-Premises Clusters and Nodes in Service

The chart (below on the left) provides a historical trend of node availability for each cluster that can host calls in the organization. After you choose at least one cluster in the left chart, the Nodes in Service chart on the right updates and provides a view of the number of nodes that are in service to host calls over the selected time period.

Overflow to Cloud

This chart shows a trend of calls that overflowed to the cloud. This can happen for a number of reasons—for example, a node exceeds its capacity, is being upgraded, has network connectivity issue, or the Webex site is not properly enabled for Video Mesh. This metric helps you pinpoint potential reasons for overflow and do the capacity planning at the organization level.

The Reason for Overflow column shows error states and provides suggestions for how to troubleshoot the issue.

Call Redirects and Call Redirect Details

This report provides details about the redirected calls and a trend of the number of calls that were not hosted on clusters—typically because of high CPU usage or network capacity being full. These calls redirected to another Video Mesh cluster that was able to host the call. This data helps you gain an overall perspective of the utilization of the clusters in the organization, so that you can better do capacity planning.

For example, after trying a maximum number of nodes in a cluster and all attempts getting rejected, the cloud tries to place the call in another cluster, if available, in the same organization based on the configuration. 16 calls were rejected from San Jose cluster.

The Reason for Redirect column shows error states and provides suggestions for how to troubleshoot the issue.

Call Distribution Across On-Premises Clusters

The chart shows a trend and the donut graph shows a summary of how calls are distributed across the different on-premises clusters in your organization. This report lets you compare the data about calls that are hosted across the various clusters in the organization over time.

Resource Utilization

The chart provides a trend and the donut graph provides a summary of the average resource utilization for the media services used in the Video Mesh clusters (organization view) or a selected cluster compared to other clusters (cluster view).


Note

The CPU utilization is directly proportional to the number of participants that land on an on-premises cluster and how many cloud participants are in the meeting.

Bandwidth Usage

This chart shows the trend of total bandwidth used across all Webex Video Mesh clusters when cascades are established between on-premises and the cloud.The value appears in Mbps.

When you choose a cluster on the graph, you see a breakdown of the cascade bandwidth usage for transmitted and received data and the cascade bandwith usage across streams (audio, video, and content share).

Recent Resource Usage

Total Calls, Overflow to Cloud, and Clusters in Service

The overview cards provide an at-a-glance view of your Video Mesh deployment.

Total Calls

The sum total of participants that were on a meeting hosted on-premises and participants that were hosted on the Cisco Webex cloud (including overflowed to the cloud) for the Cisco Webex organization

  • Cloud Calls—Number of calls that could not utilize enterprise Video Mesh Nodes, because of no connection to the enterprise network or being subject to enforced policy.

  • Overflowed to Cloud—Number of calls made within an enterprise but overflowed to a cloud cluster.

  • On-Premises—Number of calls hosted on any of the enterprise clusters.

Overflow to Cloud

The number of calls that were made within an enterprise but overflowed to a cloud cloud, and a percentage calculation of the increased or decreased overflow trend in the time period that you select.

The overflow to cloud percentage is calculated by this formula: (Number of overflow calls / Total number of on-premises and overflow calls x 100)

Clusters in Service

Percentage of clusters that can host calls in the organization.

Resource Utilization

A recent view of average CPU utilization trend for all clusters in an organization (organization view) or a selected cluster compared to other clusters (cluster view).

Call Activity

Provides a recent 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 recent 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.

Cluster Cascade Bandwidth Usage

Shows a recent view of the total bandwidth used across all Webex Video Mesh clusters when cascades are established between on-premises and the cloud. Regardless of the time period that you select on the Analytics page, this data updates every 10 minutes.

The bandwidth value appears in Mbps. The graph shows a breakdown of either or both the transmitted (Tx) and received (Rx) bandwidth.

When you choose a cluster on the graph, you see a breakdown of the cascade bandwidth usage (received and trasmitted bandwidth) and the streams bandwidth usage (audio, video, and content share).

Clusters in Service

A recent view of the number of clusters that were in service to host calls over the selected time period.

  • Green—Clusters that have all nodes in service.

  • Amber—Clusters that have 1 or more nodes that are not in service.

  • Red—Clusters that have no available nodes in service.

  • Grey—Data not available.

Click a cluster name to navigate to the Nodes in Service graph.

Enable 1080p High-Definition Video for On-Premises SIP Devices in Webex 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 being a lower meeting capacity. Participants that join a meeting that is hosted in a Webex Video Mesh Node can use 1080p 30fps video if they are all inside the corporate network and they're using an on-premises registered high definition-capable SIP device. The setting applies to all clusters that contain Webex 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, and then click Settings on the Video Mesh card.

Step 2

Toggle the Video Quality setting on.

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

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

Deregister Webex Video Mesh Node

Use this procedure to remove a Webex Video Mesh from the Cisco 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, and then click Resources under Video Mesh.

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 Webex 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 Webex 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, and then choose Resources under Video Mesh.

Step 2

From the list of clusters, go to the cluster that contains the node that you want to move, click the node and then click Perform actions on this Node.

Step 3

From the Actions drop-down, click Move Node.

Step 4

Choose one:

  • Create a new cluster by entering a name.
  • Choose an existing cluster.
Step 5

Click Move Node.

Your node is moved to the new cluster.

Set Webex 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 Webex 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, and then click Resources > View all under Video Mesh.

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 Webex 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

  1. The node makes periodic requests to the cloud to see if an update is available.

  2. 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.

  3. The node pulls updates over a secure channel.

  4. 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).

  5. The upgrade is installed.

  6. The cloud only triggers the upgrade for a percentage of nodes at a time in a cluster.

Delete Webex Video Mesh Cluster

You can permanently delete a Webex Video Mesh cluster from the Cisco 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, and then click All Resources.

Step 2

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

Tip 

You can click Video Mesh to filter on just Webex 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 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 Webex Video Mesh

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

Before you begin

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

Procedure

Step 1

From the customer view in https://admin.webex.com , go to Services, choose Settings under Video Mesh, and then click Deactivate.

Step 2

Review the list of clusters, read the disclaimer, check the check box to confirm that you understand this action, and then click Deactivate
Step 3

When you are ready to deactivate your Webex Video Mesh, click Deactivate Service.

All the Webex Video Mesh nodes and clusters are removed and Webex Video Mesh is no longer configured.

Troubleshoot Webex Video Mesh Node Registration

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

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

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

Manage Webex Video Mesh Node From the Web Interface

Before you can make any network changes to Webex 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.

Access Overview of Webex Video Mesh Node From Web Interface

Within the Webex Video Mesh node web interface, you can access a high-level summary of the node that includes calls status, node health, network settings, cloud connectivity, and so on.

Procedure

Step 1

Open the Webex Video Mesh node web interface using one of the following methods:

  • 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.

    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.

  • 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.
    Note 

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

Step 2

Go to Overview (the default page).

The following cards appear:

  • 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 Webex 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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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 Webex 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 Webex 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 Webex 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 Webex 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 Webex 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 Webex 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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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 Webex 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 Webex 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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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 Webex 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 Webex Video Mesh Node.

  • Access the Webex Video Mesh Node through the ESXi console

Configure Container Network From Webex Video Mesh Node Web Interface

Webex 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-Webex 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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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:

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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 Webex 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 Webex 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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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 Webex 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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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 Webex Video Mesh Node Web Interface

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

Procedure

Step 1

Open the Webex Video Mesh node interface.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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 Webex Video Mesh Web Interface

You can run a traceroute from the Webex 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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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 Webex Video Mesh Node Web Interface

You can enter a FQDN or IP address of a network time protocol (NTP) server to confirm that the Webex 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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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 Webex Video Mesh node and client through a Python script) is used to verify whether the required TCP/UDP ports are open from Webex Video Mesh nodes.

Before you begin

  • Download a copy of the Reflector Tool Client (Python script) and then unzip the file to a location that's easy to find. The zip file contains the script and a readme file.

  • 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 Webex 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 Access Overview of Webex Video Mesh Node From 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 Webex 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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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 Webex Video Mesh Node From The Web Interface

As part of deregistration cleanup, you can factory reset the Webex 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 Webex Video Mesh node from the cluster that's registered in Cisco Webex Control Hub.

Procedure

Step 1

Open the Webex Video Mesh node interface.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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

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.

For instructions, see Access Overview of Webex Video Mesh Node From Web 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\"}"
    }
  ]
}

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

Related Cisco Community Discussions

About Us
Contact Us
Work with Us