Zoom Mesh Dashboard

The Zoom Mesh Dashboard is a central hub for Zoom Mesh diagnostics, analytics, and events. From the Zoom Mesh Dashboard, admins or authorized users can review detailed statistics, diagnostic information, user information, or user warnings for participants within a mesh network. The Zoom Mesh Dashboard is available from the web portal under the Advanced sub-section and selecting Zoom Mesh.

The Zoom Mesh Dashboard information provided includes:

• Average Quality of Service (QoS)

• Total Mesh Participants

• Mesh Parent-to-Child Ratio

• Bandwidth Saved

• Average Parent Client CPU Utilization

• Mesh Member Errors

• Mesh Event Duration

• Client Health Warnings

• List of Mesh Parents

• List of Children Associated to a Parent

• Active Mesh Events

• Mesh Parents Per-Event

• Mesh Participants Per-Event

• Cloud Attendees Per-Event

• Mesh Data Transferred Per-Event

• Average Latency

Admins can review current and historical events data and analytics from the Zoom Mesh Dashboard

Admins or authorized users can review current and historical data for Zoom Mesh events from the Zoom Mesh Dashboard, with up to 90 days of historical data in a single report.

Inspecting a Zoom Mesh event provides detailed information about the event’s network performance, parent and child clients, device health, and more

Inspecting a current or historical Zoom Mesh event provides a summary of the event, including network performance, parent and child client relationships, device health, event duration, Mesh data transfer totals, and saved bandwidth.

The Zoom Mesh Dashboard displays a list of Top Mesh Parents to identify commonly used devices and includes utilization and health reports

The Zoom Mesh Dashboard displays a list of Top Mesh Parents within the dashboard’s defined time duration. The summary includes the number of children clients associated with each parent, average latency, number of events served, duration of service, data transferred, and any health reports.

Devices connected to a Zoom Mesh event can be dynamically set as as parent or child client from the Zoom Mesh Dashboard

Devices connected to a Zoom Mesh-enabled event can be dynamically assigned as a parent or child client from the Zoom Mesh Dashboard under the Devices tab. This functionality does not require a device to be registered with Zoom Device Management.

Admins can enable Zoom Mesh from the Settings tab within the Zoom Mesh Dashboard

Admins or authorized users can enable Zoom Mesh from the Settings tab within the Zoom Mesh Dashboard. This setting is disabled by default.

Admins can decide where users can connect to a mesh network

Within the Zoom Mesh Settings tab, account admins can define How the mesh will be setup to determine where users can connect to a mesh network across various locations.

If the setting for Mesh will be set up globally across all locations is enabled, user devices will attempt to make a mesh network connection wherever they are, whenever they are outside of a defined IP location. This setting does not require defining a location or subnet-unique IP settings and is default behavior when unmodified.

Alternatively, if the setting for Mesh will be set up within specified locations is enabled, users will only attempt to create a mesh network within the defined IP list. If an IP location list is not defined, users will never attempt to form a mesh network connection.

(Optional) Zoom Mesh can be configured by location, public IP, and subnet ranges

An admin or authorized user can configure Zoom Mesh for locations by public IP and subnet ranges, including maximum bandwidth allocation available for parent clients. These settings allow for granular control over which user subnets can participate in Zoom Mesh, and can prevent bandwidth oversubscription from parent clients. Admins can define this setting by clicking the View button when enabling Zoom Mesh from the Settings tab within the Zoom Mesh Dashboard.

(Optional) Configured locations can be marked for allowlisting, or blocklisting

When adding a specific location by IP for Mesh configuration, the location can be marked to block devices within the designated IP range from being included in a mesh network. Alternatively, if this setting is not checked, Zoom Mesh will attempt to create a mesh network between users within the defined IP range.

(Optional) Configured locations can created manually, or bulk imported via CSV

When configuring a mesh network by location, account admins can configure Zoom Mesh IP locations manually through the web interface, or by bulk importing locations through a CSV file.

(Optional) If Zoom Mesh is not configured for a location, the Cloud Orchestration Service will attempt to create a natural mesh within the network

If a location is not configured within the Zoom Mesh Dashboard settings, the COS will attempt to create a natural mesh within the network based on device performance and metrics.

Accounts can optimize their Zoom Mesh network configuration to fit their needs

An admin or authorized user can configure Zoom Mesh to suit their network or infrastructure needs from the Settings tab within the Zoom Mesh Dashboard using the Mesh optimizer setting.

• Default configuration attempts to pair approximately 30 child clients to each parent client.

• Set max bandwidth allocation defines the maximum amount of bandwidth available for each parent client across an account’s locations. This value also pairs with a location’s bandwidth allocation setting. For example, if a location has a maximum bandwidth allocation of 50 Mbps, and this setting is set to 1 Mbps, there are a maximum of 50 possible parent clients on a 1 Mbps connection.

• Smart configuration allows admins or authorized users to choose on a sliding scale between Efficiency and Stability.

  • Efficiency delegates a higher parent-to-child ratio, of approximately 1:50.

  • Stability delegates a lower parent-to-child ratio, of approximately 1:10.

• Restrictions for joining mesh allows admins or authorized users to define settings that restrict users from joining a mesh network for quality purposes.

  • If round trip time (RTT) exceeds a certain latency in milliseconds, users won’t join a mesh network.

  • If a device is connected via WiFi, the device can also be excluded.\

    
• The Zoom Mesh dashboard data retention policy defines how long Zoom will store your Zoom mesh performance data. This is customizable from as little as 6 months to up to 10 years of time.