NetQ UI Card Reference

This reference describes the cards available with the NetQ 3.2 graphical user interface (NetQ UI). Each item and field on the four sizes of cards is shown.

Network Health Card

As with any network, one of the challenges is keeping track of all of the moving parts. With the NetQ GUI, you can view the overall health of your network at a glance and then delve deeper for periodic checks or as conditions arise that require attention. For a general understanding of how well your network is operating, the Network Health card workflow is the best place to start as it contains the highest view and performance roll-ups.

The small Network Health card displays:

ItemDescription
Indicates data is for overall Network Health
Health trendTrend of overall network health, represented by an arrow:
  • Pointing upward and green: Health score in the most recent window is higher than in the last two data collection windows, an increasing trend
  • Pointing downward and bright pink: Health score in the most recent window is lower than in the last two data collection windows, a decreasing trend
  • No arrow: Health score is unchanged over the last two data collection windows, trend is steady

The data collection window varies based on the time period of the card. For a 24 hour time period (default), the window is one hour. This gives you current, hourly, updates about your network health.

Health score

Average of health scores for system health, network services health, and interface health during the last data collection window. The health score for each category is calculated as the percentage of items which passed validations versus the number of items checked.

The collection window varies based on the time period of the card. For a 24 hour time period (default), the window is one hour. This gives you current, hourly, updates about your network health.

Health ratingPerformance rating based on the health score during the time window:
  • Low: Health score is less than 40%
  • Med: Health score is between 40% and 70%
  • High: Health score is greater than 70%
ChartDistribution of overall health status during the designated time period

The medium Network Health card displays the distribution, score, and trend of the:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for overall Network Health.
Health trendTrend of system, network service, and interface health, represented by an arrow:
  • Pointing upward and green: Health score in the most recent window is higher than in the last two data collection windows, an increasing trend.
  • Pointing downward and bright pink: Health score in the most recent window is lower than in the last two data collection windows, a decreasing trend.
  • No arrow: Health score is unchanged over the last two data collection windows, trend is steady.

The data collection window varies based on the time period of the card. For a 24 hour time period (default), the window is one hour. This gives you current, hourly, updates about your network health.

Health scorePercentage of devices which passed validation versus the number of devices checked during the time window for:
  • System health: NetQ Agent health, Cumulus Linux license status, and sensors
  • Network services health: BGP, CLAG, EVPN, NTP, OSPF, and VXLAN health
  • Interface health: interfaces MTU, VLAN health.

The data collection window varies based on the time period of the card. For a 24 hour time period (default), the window is one hour. This gives you current, hourly, updates about your network health.

ChartDistribution of overall health status during the designated time period.

The large Network Health card contains three tabs.

The System Health tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for System Health.
Health trendTrend of NetQ Agents, Cumulus Linux licenses, and sensor health, represented by an arrow:
  • Pointing upward and green: Health score in the most recent window is higher than in the last two data collection windows, an increasing trend.
  • Pointing downward and bright pink: Health score in the most recent window is lower than in the last two data collection windows, a decreasing trend.
  • No arrow: Health score is unchanged over the last two data collection windows, trend is steady.

The data collection window varies based on the time period of the card. For a 24 hour time period (default), the window is one hour. This gives you current, hourly, updates about your network health.

Health score

Percentage of devices which passed validation versus the number of devices checked during the time window for NetQ Agents, Cumulus Linux license status, and platform sensors.

The data collection window varies based on the time period of the card. For a 24 hour time period (default), the window is one hour. This gives you current, hourly, updates about your network health.

ChartsDistribution of health score for NetQ Agents, Cumulus Linux license status, and platform sensors during the designated time period.
TableListing of items that match the filter selection:
  • Most Failures: Devices with the most validation failures are listed at the top.
  • Recent Failures: Most recent validation failures are listed at the top.
Show All ValidationsOpens full screen Network Health card with a listing of validations performed by network service and protocol.

The Network Service Health tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for Network Protocols and Services Health.
Health trendTrend of BGP, CLAG, EVPN, NTP, OSPF, and VXLAN services health, represented by an arrow:
  • Pointing upward and green: Health score in the most recent window is higher than in the last two data collection windows, an increasing trend.
  • Pointing downward and bright pink: Health score in the most recent window is lower than in the last two data collection windows, a decreasing trend.
  • No arrow: Health score is unchanged over the last two data collection windows, trend is steady.

The data collection window varies based on the time period of the card. For a 24 hour time period (default), the window is one hour. This gives you current, hourly, updates about your network health.

Health score

Percentage of devices which passed validation versus the number of devices checked during the time window for BGP, CLAG, EVPN, NTP, and VXLAN protocols and services.

The data collection window varies based on the time period of the card. For a 24 hour time period (default), the window is one hour. This gives you current, hourly, updates about your network health.

ChartsDistribution of passing validations for BGP, CLAG, EVPN, NTP, and VXLAN services during the designated time period.
TableListing of devices that match the filter selection:
  • Most Failures: Devices with the most validation failures are listed at the top.
  • Recent Failures: Most recent validation failures are listed at the top.
Show All ValidationsOpens full screen Network Health card with a listing of validations performed by network service and protocol.

The Interface Health tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for Interface Health.
Health trendTrend of interfaces, VLAN, and MTU health, represented by an arrow:
  • Pointing upward and green: Health score in the most recent window is higher than in the last two data collection windows, an increasing trend.
  • Pointing downward and bright pink: Health score in the most recent window is lower than in the last two data collection windows, a decreasing trend.
  • No arrow: Health score is unchanged over the last two data collection windows, trend is steady.

The data collection window varies based on the time period of the card. For a 24 hour time period (default), the window is one hour. This gives you current, hourly, updates about your network health.

Health score

Percentage of devices which passed validation versus the number of devices checked during the time window for interfaces, VLAN, and MTU protocols and ports.

The data collection window varies based on the time period of the card. For a 24 hour time period (default), the window is one hour. This gives you current, hourly, updates about your network health.

ChartsDistribution of passing validations for interfaces, VLAN, and MTU protocols and ports during the designated time period.
TableListing of devices that match the filter selection:
  • Most Failures: Devices with the most validation failures are listed at the top.
  • Recent Failures: Most recent validation failures are listed at the top.
Show All ValidationsOpens full screen Network Health card with a listing of validations performed by network service and protocol.

The full screen Network Health card displays all events in the network.

ItemDescription
TitleNetwork Health.
Closes full screen card and returns to workbench.
Default TimeRange of time in which the displayed data was collected.
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
Network protocol or service tabDisplays results of that network protocol or service validations that occurred during the designated time period. By default, the requests list is sorted by the date and time that the validation was completed (Time). This tab provides the following additional data about all protocols and services:
  • Validation Label: User-defined name of a validation or Default validation
  • Total Node Count: Number of nodes running the protocol or service
  • Checked Node Count: Number of nodes running the protocol or service included in the validation
  • Failed Node Count: Number of nodes that failed the validation
  • Rotten Node Count: Number of nodes that were unreachable during the validation run
  • Warning Node Count: Number of nodes that had errors during the validation run

The following protocols and services have additional data:

  • BGP
    • Total Session Count: Number of sessions running BGP included in the validation
    • Failed Session Count: Number of BGP sessions that failed the validation
  • EVPN
    • Total Session Count: Number of sessions running BGP included in the validation
    • Checked VNIs Count: Number of VNIs included in the validation
    • Failed BGP Session Count: Number of BGP sessions that failed the validation
  • Interfaces
    • Checked Port Count: Number of ports included in the validation
    • Failed Port Count: Number of ports that failed the validation.
    • Unverified Port Count: Number of ports where a peer could not be identified
  • Licenses
    • Checked License Count: Number of licenses included in the validation
    • Failed License Count: Number of licenses that failed the validation
  • MTU
    • Total Link Count: Number of links included in the validation
    • Failed Link Count: Number of links that failed the validation
  • NTP
    • Unknown Node Count: Number of nodes that NetQ sees but are not in its inventory an thus not included in the validation
  • OSPF
    • Total Adjacent Count: Number of adjacencies included in the validation
    • Failed Adjacent Count: Number of adjacencies that failed the validation
  • Sensors
    • Checked Sensor Count: Number of sensors included in the validation
    • Failed Sensor Count: Number of sensors that failed the validation
  • VLAN
    • Total Link Count: Number of links included in the validation
    • Failed Link Count: Number of links that failed the validation
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

Event Cards

Events|Alarms Card

You can easily monitor critical events occurring across your network using the Alarms card. You can determine the number of events for the various system, interface, and network protocols and services components in the network.

The small Alarms card displays:

ItemDescription
Indicates data is for all critical severity events in the network.
Alarm trendTrend of alarm count, represented by an arrow:
  • Pointing upward and bright pink: alarm count is higher than the last two time periods, an increasing trend
  • Pointing downward and green: alarm count is lower than the last two time periods, a decreasing trend
  • No arrow: alarm count is unchanged over the last two time periods, trend is steady
Alarm scoreCurrent count of alarms during the designated time period.
Alarm ratingCount of alarms relative to the average count of alarms during the designated time period:
  • Low: Count of alarms is below the average count; a nominal count
  • Med: Count of alarms is in range of the average count; some room for improvement
  • High: Count of alarms is above the average count; user intervention recommended
ChartDistribution alarms received during the designated time period and a total count of all alarms present in the system.

The medium Alarms card displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for all critical events in the network.
CountTotal number of alarms received during the designated time period.
Alarm scoreCurrent count of alarms received from each category (overall, system, interface, and network services) during the designated time period.
ChartDistribution of all alarms received from each category during the designated time period.

The large Alarms card has one tab.

The Alarm Summary tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for all system, trace and interface critical events in the network.
Alarm Distribution

Chart: Distribution of all alarms received from each category during the designated time period:

  • NetQ Agent
  • BTRFS Information
  • CL Support
  • Config Diff
  • CL License
  • Installed Packages
  • Link
  • LLDP
  • MTU
  • Node
  • Port
  • Resource
  • Running Config Diff
  • Sensor
  • Services
  • SSD Utilization
  • TCA Interface Stats
  • TCA Resource Utilization
  • TCA Sensors
The categories are displayed in descending order based on total count of alarms, with the largest number of alarms is shown at the top, followed by the next most, down to the chart with the fewest alarms.

Count: Total number of alarms received from each category during the designated time period.

TableListing of items that match the filter selection for the selected alarm categories:
  • Events by Most Recent: Most recent event are listed at the top
  • Devices by Event Count: Devices with the most events are listed at the top
Show All EventsOpens full screen Events | Alarms card with a listing of all events.

The full screen Alarms card provides tabs for all events.

ItemDescription
TitleEvents | Alarms
Closes full screen card and returns to workbench.
Default TimeRange of time in which the displayed data was collected.
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
All AlarmsDisplays all alarms received in the time period. By default, the requests list is sorted by the date and time that the event occurred (Time). This tab provides the following additional data about each request:
  • Source: Hostname of the given event
  • Message: Text describing the alarm or info event that occurred
  • Type: Name of network protocol and/or service that triggered the given event
  • Severity: Importance of the event-critical, warning, info, or debug
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

Events|Info Card

You can easily monitor warning, info, and debug severity events occurring across your network using the Info card. You can determine the number of events for the various system, interface, and network protocols and services components in the network.

The small Info card displays:

ItemDescription
Indicates data is for all warning, info, and debug severity events in the network
Info countNumber of info events received during the designated time period
Alarm countNumber of alarm events received during the designated time period
ChartDistribution of all info events and alarms received during the designated time period

The medium Info card displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for all warning, info, and debug severity events in the network.
Types of InfoChart which displays the services that have triggered events during the designated time period. Hover over chart to view a count for each type.
Distribution of InfoInfo Status
  • Count: Number of info events received during the designated time period.
  • Chart: Distribution of all info events received during the designated time period.
Alarms Status
  • Count: Number of alarm events received during the designated time period.
  • Chart: Distribution of all alarm events received during the designated time period.

The large Info card displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for all warning, info, and debug severity events in the network.
Types of InfoChart which displays the services that have triggered events during the designated time period. Hover over chart to view a count for each type.
Distribution of InfoInfo Status
  • Count: Current number of info events received during the designated time period.
  • Chart: Distribution of all info events received during the designated time period.
Alarms Status
  • Count: Current number of alarm events received during the designated time period.
  • Chart: Distribution of all alarm events received during the designated time period.
TableListing of items that match the filter selection:
  • Events by Most Recent: Most recent event are listed at the top.
  • Devices by Event Count: Devices with the most events are listed at the top.
Show All EventsOpens full screen Events | Info card with a listing of all events.

The full screen Info card provides tabs for all events.

ItemDescription
TitleEvents | Info
Closes full screen card and returns to workbench.
Default TimeRange of time in which the displayed data was collected.
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
All EventsDisplays all events (both alarms and info) received in the time period. By default, the requests list is sorted by the date and time that the event occurred (Time). This tab provides the following additional data about each request:
  • Source: Hostname of the given event
  • Message: Text describing the alarm or info event that occurred
  • Type: Name of network protocol and/or service that triggered the given event
  • Severity: Importance of the event-critical, warning, info, or debug
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

Inventory Cards

Inventory|Devices Card

The small Devices Inventory card displays:

ItemDescription
Indicates data is for device inventory
Total number of switches in inventory during the designated time period
Total number of hosts in inventory during the designated time period

The medium Devices Inventory card displays:

ItemDescription
Indicates data is for device inventory
TitleInventory | Devices
Total number of switches in inventory during the designated time period
Total number of hosts in inventory during the designated time period
ChartsDistribution of operating systems deployed on switches and hosts, respectively

The large Devices Inventory card has one tab.

The Switches tab displays:

ItemDescription
Time periodAlways Now for inventory by default.
Indicates data is for device inventory.
TitleInventory | Devices.
Total number of switches in inventory during the designated time period.
Link to full screen listing of all switches.
ComponentSwitch components monitored-ASIC, Operating System (OS), Cumulus Linux license, NetQ Agent version, and Platform.
Distribution chartsDistribution of switch components across the network.
UniqueNumber of unique items of each component type. For example, for License, you might have CL 2.7.2 and CL 2.7.4, giving you a unique count of two.

The full screen Devices Inventory card provides tabs for all switches and all hosts.

ItemDescription
TitleInventory | Devices | Switches.
Closes full screen card and returns to workbench.
Time periodTime period does not apply to the Inventory cards. This is always Default Time.
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
All Switches and All Hosts tabsDisplays all monitored switches and hosts in your network. By default, the device list is sorted by hostname. These tabs provide the following additional data about each device:
  • Agent
    • State: Indicates communication state of the NetQ Agent on a given device. Values include Fresh (heard from recently) and Rotten (not heard from recently).
    • Version: Software version number of the NetQ Agent on a given device. This should match the version number of the NetQ software loaded on your server or appliance; for example, 2.1.0.
  • ASIC
    • Core BW: Maximum sustained/rated bandwidth. Example values include 2.0 T and 720 G.
    • Model: Chip family. Example values include Tomahawk, Trident, and Spectrum.
    • Model Id: Identifier of networking ASIC model. Example values include BCM56960 and BCM56854.
    • Ports: Indicates port configuration of the switch. Example values include 32 x 100G-QSFP28, 48 x 10G-SFP+, and 6 x 40G-QSFP+.
    • Vendor: Manufacturer of the chip. Example values include Broadcom and Mellanox.
  • CPU
    • Arch: Microprocessor architecture type. Values include x86_64 (Intel), ARMv7 (AMD), and PowerPC.
    • Max Freq: Highest rated frequency for CPU. Example values include 2.40 GHz and 1.74 GHz.
    • Model: Chip family. Example values include Intel Atom C2538 and Intel Atom C2338.
    • Nos: Number of cores. Example values include 2, 4, and 8.
  • Disk Total Size: Total amount of storage space in physical disks (not total available). Example values: 10 GB, 20 GB, 30 GB.
  • License State: Indicator of validity. Values include ok and bad.
  • Memory Size: Total amount of local RAM. Example values include 8192 MB and 2048 MB.
  • OS
    • Vendor: Operating System manufacturer. Values include Cumulus Networks, RedHat, Ubuntu, and CentOS.
    • Version: Software version number of the OS. Example values include 3.7.3, 2.5.x, 16.04, 7.1.
    • Version Id: Identifier of the OS version. For Cumulus, this is the same as the Version (3.7.x).
  • Platform
    • Date: Date and time the platform was manufactured. Example values include 7/12/18 and 10/29/2015.
    • MAC: System MAC address. Example value: 17:01:AB:EE:C3:F5.
    • Model: Manufacturer's model name. Examples values include AS7712-32X and S4048-ON.
    • Number: Manufacturer part number. Examples values include FP3ZZ7632014A, 0J09D3.
    • Revision: Release version of the platform.
    • Series: Manufacturer serial number. Example values include D2060B2F044919GD000060, CN046MRJCES0085E0004.
    • Vendor: Manufacturer of the platform. Example values include Cumulus Express, Dell, EdgeCore, Lenovo, Mellanox.
  • Time: Date and time the data was collected from device.
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

Inventory|Switch Card

Knowing what components are included on all of your switches aids in upgrade, compliance, and other planning tasks. Viewing this data is accomplished through the Switch Inventory card.

The small Switch Inventory card displays:

ItemDescription
Indicates data is for switch inventory
CountTotal number of switches in the network inventory
ChartDistribution of overall health status during the designated time period; fresh versus rotten

The medium Switch Inventory card displays:

ItemDescription
Indicates data is for switch inventory.
Filter

View fresh switches (those you have heard from recently) or rotten switches (those you have not heard from recently) on this card.
Chart

Distribution of switch components (disk size, OS, ASIC, NetQ Agents, CPU, Cumulus Linux licenses, platform, and memory size) during the designated time period. Hover over chart segment to view versions of each component.

Note: You should only have one version of NetQ Agent running and it should match the NetQ Platform release number. If you have more than one, you likely need to upgrade the older agents.

UniqueNumber of unique versions of the various switch components. For example, for OS, you might have CL 3.7.1 and CL 3.7.4 making the unique value two.

The large Switch Inventory card contains four tabs.

The Summary tab displays:

ItemDescription
Indicates data is for switch inventory.
FilterView fresh switches (those you have heard from recently) or rotten switches (those you have not heard from recently) on this card.
Charts

Distribution of switch components (disk size, OS, ASIC, NetQ Agents, CPU, Cumulus Linux licenses, platform, and memory size), divided into software and hardware, during the designated time period. Hover over chart segment to view versions of each component.

Note: You should only have one version of NetQ Agent running and it should match the NetQ Platform release number. If you have more than one, you likely need to upgrade the older agents.

UniqueNumber of unique versions of the various switch components. For example, for OS, you might have CL 3.7.6 and CL 3.7.4 making the unique value two.

The ASIC tab displays:

ItemDescription
Indicates data is for ASIC information.
FilterView fresh switches (those you have heard from recently) or rotten switches (those you have not heard from recently) on this card.
Vendor chartDistribution of ASIC vendors. Hover over chart segment to view the number of switches with each version.
Model chartDistribution of ASIC models. Hover over chart segment to view the number of switches with each version.
Show AllOpens full screen card displaying all components for all switches.

The Platform tab displays:

ItemDescription
Indicates data is for platform information.
FilterView fresh switches (those you have heard from recently) or rotten switches (those you have not heard from recently) on this card.
Vendor chartDistribution of platform vendors. Hover over chart segment to view the number of switches with each vendor.
Platform chartDistribution of platform models. Hover over chart segment to view the number of switches with each model.
License State chartDistribution of Cumulus Linux license status. Hover over chart segments to highlight the vendor and platforms that have that license status.
Show AllOpens full screen card displaying all components for all switches.

The Software tab displays:

ItemDescription
Indicates data is for software information.
FilterView fresh switches (those you have heard from recently) or rotten switches (those you have not heard from recently) on this card.
Operating System chartDistribution of OS versions. Hover over chart segment to view the number of switches with each version.
Agent Version chart

Distribution of NetQ Agent versions. Hover over chart segment to view the number of switches with each version.

Note: You should only have one version of NetQ Agent running and it should match the NetQ Platform release number. If you have more than one, you likely need to upgrade the older agents.

Show AllOpens full screen card displaying all components for all switches.

The full screen Switch Inventory card provides tabs for all components, ASIC, platform, CPU, memory, disk, and OS components.

Switch Card

Viewing detail about a particular switch is essential when troubleshooting performance issues. With NetQ you can view the overall performance and drill down to view attributes of the switch, interface performance and the events associated with a switch. This is accomplished through the Switches card.

The small Switch card displays:

ItemDescription
Indicates data is for a single switch.
titleHostname of switch.
ChartDistribution of switch alarms during the designated time period.
TrendTrend of alarm count, represented by an arrow:
  • Pointing upward and green: alarm count is higher than the last two time periods, an increasing trend.
  • Pointing downward and bright pink: alarm count is lower than the last two time periods, a decreasing trend.
  • No arrow: alarm count is unchanged over the last two time periods, trend is steady.
CountCurrent count of alarms on the switch.
RatingOverall performance of the switch. Determined by the count of alarms relative to the average count of alarms during the designated time period:
  • Low: Count of alarms is below the average count; a nominal count.
  • Med: Count of alarms is in range of the average count; some room for improvement.
  • High: Count of alarms is above the average count; user intervention recommended.

The medium Switch card displays:

ItemDescription
Indicates data is for a single switch.
titleHostname of switch.
AlarmsWhen selected, displays distribution and count of alarms by alarm category, generated by this switch during the designated time period.
Charts

When selected, displays distribution of alarms by alarm category, during the designated time period.

The large Switch card contains four tabs:

The Attributes tab displays:

ItemDescription
Indicates data is for a single switch.
title<Hostname> | Attributes.
HostnameUser-defined name for this switch.
Management IPIPv4 or IPv6 address used for management of this switch.
Management MACMAC address used for management of this switch.
Agent StateOperational state of the NetQ Agent on this switch; Fresh or Rotten.
Platform VendorManufacturer of this switch box. Cumulus Networks is identified as the vendor for a switch in the Cumulus in the Cloud (CITC) environment, as seen here.
Platform ModelManufacturer model of this switch. VX is identified as the model for a switch in CITC environment, as seen here.
ASIC VendorManufacturer of the ASIC installed on the motherboard.
ASIC ModelManufacturer model of the ASIC installed on the motherboard.
OSOperating system running on the switch. CL indicates a Cumulus Linux license.
OS VersionVersion of the OS running on the switch.
NetQ Agent VersionVersion of the NetQ Agent running on the switch.
License StateIndicates whether the license is valid (ok) or invalid/missing (bad).
Total InterfacesTotal number of interfaces on this switch, and the number of those that are up and down.

The Utilization tab displays:

ItemDescription
Indicates utilization data is for a single switch.
Title<Hostname> | Utilization.
PerformanceDisplays distribution of CPU and memory usage during the designated time period.
Disk UtilizationDisplays distribution of disk usage during the designated time period.

The Interfaces tab displays:

ItemDescription
Indicates interface statistics for a single switch.
Title<Hostname> | Interface Stats.
Interface ListList of interfaces present during the designated time period.
Interface FilterSorts interface list by Name, Rx Util (receive utilization), or Tx Util (transmit utilization).
Interfaces CountNumber of interfaces present during the designated time period.
Interface StatisticsDistribution and current value of various transmit and receive statistics associated with a selected interface:
  • Broadcast: Number of broadcast packets
  • Bytes: Number of bytes per second
  • Drop: Number of dropped packets
  • Errs: Number of errors
  • Frame: Number of frames received
  • Multicast: Number of multicast packets
  • Packets: Number of packets per second
  • Utilization: Bandwidth utilization as a percentage of total available bandwidth

The Digital Optics tab displays:

ItemDescription
Indicates digital optics metrics for a single switch.
Title<Hostname> | Digital Optics.
Interface ListList of interfaces present during the designated time period.
SearchSearch for an interface by Name.
Interfaces CountNumber of interfaces present during the designated time period.
Digital Optics StatisticsUse the parameter dropdown to change the chart view to see metrics for Laser RX Power, Laser Output Power, Laser Bias Current, Module Temperature, and Module Voltage.

The full screen Switch card provides multiple tabs.

ItemDescription
Title<hostname>
Closes full screen card and returns to workbench.
Default TimeDisplayed data is current as of this moment.
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
AlarmsDisplays all known critical alarms for the switch. This tab provides the following additional data about each address:
  • Hostname: User-defined name of the switch
  • Message: Description of alarm
  • Message Type: Indicates the protocol or service which generated the alarm
  • Severity: Indicates the level of importance of the event; it is always critical for NetQ alarms
  • Time: Date and time the data was collected
All InterfacesDisplays all known interfaces on the switch. This tab provides the following additional data about each interface:
  • Details: Information about the interface, such as MTU, table number, members, protocols running, VLANs
  • Hostname: Hostname of the given event
  • IfName: Name of the interface
  • Last Changed: Data and time that the interface was last enabled, updated, deleted, or changed state to down
  • OpId: Process identifier; for internal use only
  • State: Indicates if the interface is up or down
  • Time: Date and time the data was collected
  • Type: Kind of interface; for example, VRF, switch port, loopback, ethernet
  • VRF: Name of the associated virtual route forwarding (VRF) interface if deployed
MAC AddressesDisplays all known MAC addresses for the switch. This tab provides the following additional data about each MAC address:
  • Egress Port: Importance of the event-critical, warning, info, or debug
  • Hostname: User-defined name of the switch
  • Last Changed: Data and time that the address was last updated or deleted
  • MAC Address: MAC address of switch
  • Origin: Indicates whether this switch owns this address (true) or if another switch owns this address (false)
  • Remote: Indicates whether this address is reachable via a VXLAN on another switch (true) or is reachable locally on the switch (false)
  • Time: Date and time the data was collected
  • VLAN Id: Identifier of an associated VLAN if deployed
VLANsDisplays all configured VLANs on the switch. This tab provides the following additional data about each VLAN:
  • Hostname: User-defined name of the switch
  • IfName: Name of the interface
  • Last Changed: Data and time that the VLAN was last updated or deleted
  • Ports: Ports used by the VLAN
  • SVI: Indicates whether is the VLAN has a switch virtual interface (yes) or not (no)
  • Time: Date and time the data was collected
  • VLANs: Name of the VLAN
IP RoutesDisplays all known IP routes for the switch. This tab provides the following additional data about each route:
  • Hostname: User-defined name of the switch
  • Is IPv6: Indicates whether the route is based on an IPv6 address (true) or an IPv4 address (false)
  • Message Type: Service type; always route
  • NextHops: List of hops in the route
  • Origin: Indicates whether the route is owned by this switch (true) or not (false)
  • Prefix: Prefix for the address
  • Priority: Indicates the importance of the route; higher priority is used before lower priority
  • Route Type: Kind of route, where the type is dependent on the protocol
  • RT Table Id: Identifier of the routing table that contains this route
  • Source: Address of source switch; *None* if this switch is the source
  • Time: Date and time the data was collected
  • VRF: Name of the virtual route forwarding (VRF) interface if used by the route
IP NeighborsDisplays all known IP neighbors of the switch. This tab provides the following additional data about each neighbor:
  • Hostname: User-defined name of the switch
  • IfIndex: Index of the interface
  • IfName: Name of the interface
  • IP Address: IP address of the neighbor
  • Is IPv6: Indicates whether the address is an IPv6 address (true) or an IPv4 address (false)
  • Is Remote: Indicates whether this address is reachable via a VXLAN on another switch (true) or is reachable locally on the switch (false)
  • MAC Address: MAC address of neighbor
  • Message Type: Service type; always neighbor
  • OpId: Process identifier; for internal use only
  • Time: Date and time the data was collected
  • VRF: Name of the virtual route forwarding (VRF) interface if deployed
IP AddressesDisplays all known IP addresses for the switch. This tab provides the following additional data about each address:
  • Hostname: User-defined name of the switch
  • IfName: Name of the interface
  • Is IPv6: Indicates whether the address is an IPv6 address (true) or an IPv4 address (false)
  • Mask: Mask for the address
  • Prefix: Prefix for the address
  • Time: Date and time the data was collected
  • VRF: Name of the virtual route forwarding (VRF) interface if deployed
BTRFS UtilizationDisplays disk utilization information for devices running Cumulus Linux 3.x and the b-tree file system (BTRFS):
  • Device Allocated: Percentage of the disk space allocated by BTRFS
  • Hostname: Hostname of the given device
  • Largest Chunk Size: Largest remaining chunk size on disk
  • Last Changed: Data and time that the storage allocation was last updated
  • Rebalance Recommended: Based on rules described in When to Rebalance BTRFS Partitions, a rebalance is suggested
  • Unallocated Space: Amount of space remaining on the disk
  • Unused Data Chunks Space: Amount of available data chunk space
Installed PackagesDisplays all known interfaces on the switch. This tab provides the following additional data about each package:
  • CL Version: Version of Cumulus Linux associated with the package
  • Hostname: Hostname of the given event
  • Last Changed: Data and time that the interface was last enabled, updated, deleted, or changed state to down
  • Package Name: Name of the package
  • Package Status: Indicates if the package is installed
  • Version: Version of the package
SSD UtilizationDisplays overall health and utilization of a 3ME3 solid state drive (SSD). This tab provides the following data about each drive:
  • Hostname: Hostname of the device with the 3ME3 drive installed
  • Last Changed: Data and time that the SSD information was updated
  • SSD Model: SSD model name
  • Total PE Cycles Supported: PE cycle rating for the drive
  • Current PE Cycles Executed: Number of PE cycle run to date
  • % Remaining PE Cycles: Number of PE cycle available before drive needs to be replaced
Forwarding ResourcesDisplays usage statistics for all forwarding resources on the switch. This tab provides the following additional data about each resource:
  • ECMP Next Hops: Maximum number of hops seen in forwarding table, number used, and the percentage of this usage versus the maximum number
  • Hostname: Hostname where forwarding resources reside
  • IPv4 Host Entries: Maximum number of hosts in forwarding table, number of hosts used, and the percentage of usage versus the maximum
  • IPv4 Route Entries: Maximum number of routes in forwarding table, number of routes used, and the percentage of usage versus the maximum
  • IPv6 Host Entries: Maximum number of hosts in forwarding table, number of hosts used, and the percentage of usage versus the maximum
  • IPv6 Route Entries: Maximum number of routes in forwarding table, number of routes used, and the percentage of usage versus the maximum
  • MAC Entries: Maximum number of MAC addresses in forwarding table, number of MAC addresses used, and the percentage of usage versus the maximum
  • MCAST Route: Maximum number of multicast routes in forwarding table, number of multicast routes used, and the percentage of usage versus the maximum
  • Time: Date and time the data was collected
  • Total Routes: Maximum number of total routes in forwarding table, number of total routes used, and the percentage of usage versus the maximum
ACL ResourcesDisplays usage statistics for all ACLs on the switch.
The following is diplayed for each ACL:
  • Maximum entries in the ACL
  • Number entries used
  • Percentage of this usage versus the maximum
This tab also provides the following additional data about each ACL:
  • Hostname: Hostname where the ACLs reside
  • Time: Date and time the data was collected
What Just HappenedDisplays displays events based on conditions detected in the data plane on the switch. Refer to What Just Happened for descriptions of the fields in this table.
SensorsDisplays all known sensors on the switch. This tab provides a table for each type of sensor. Select the sensor type using the filter above the table.
  • Fan:
    • Hostname: Hostname where the fan sensor resides
    • Message Type: Type of sensor; always Fan
    • Description: Text identifying the sensor
    • Speed (RPM): Revolutions per minute of the fan
    • Max: Maximum speed of the fan measured by sensor
    • Min: Minimum speed of the fan measured by sensor
    • Message: Description
    • Sensor Name: User-defined name for the fan sensor
    • Previous State: Operational state of the fan sensor before last update
    • State: Current operational state of the fan sensor
    • Time: Date and time the data was collected
  • Temperature:
    • Hostname: Hostname where the temperature sensor resides
    • Message Type: Type of sensor; always Temp
    • Critical: Maximum temperature (°C) threshold for the sensor
    • Description: Text identifying the sensor
    • Lower Critical: Minimum temperature (°C) threshold for the sensor
    • Max: Maximum temperature measured by sensor
    • Min: Minimum temperature measured by sensor
    • Message: Description
    • Sensor Name: User-defined name for the temperature sensor
    • Previous State: State of the sensor before last update
    • State: Current state of the temperature sensor
    • Temperature: Current temperature measured at sensor
    • Time: Date and time the data was collected
  • Power Supply Unit (PSU):
    • Hostname: Hostname where the temperature sensor resides
    • Message Type: Type of sensor; always PSU
    • PIn: Input power (W) measured by sensor
    • POut: Output power (W) measured by sensor
    • Sensor Name: User-defined name for the power supply unit sensor
    • Previous State: State of the sensor before last update
    • State: Current state of the temperature sensor
    • Time: Date and time the data was collected
    • VIn: Input voltage (V) measured by sensor
    • VOut: Output voltage (V) measured by sensor
Digital OpticsDisplays all available digital optics performance metrics. This tab provides a table for each of five metrics.
  • Hostname: Hostname where the digital optics module resides
  • Timestamp: Date and time the data was collected
  • IfName: Name of the port where the digital optics module resides
  • Units: Unit of measure that applies to the given metric
  • Value: Measured value during the designated time period
  • High Warning Threshold: Value used to generate a warning if the measured value excedes it.
  • Low Warning Threshold: Value used to generate a warning if the measured value drops below it.
  • High Alarm Threshold: Value used to generate an alarm if the measured value excedes it.
  • Low Alarm Threshold: Value used to generate an alarm if the measured value drops below it.
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

Network Services Cards

BGP Service Card

The small BGP Service card displays:

ItemDescription
Indicates data is for all sessions of a Network Service or Protocol
TitleBGP: All BGP Sessions, or the BGP Service
Total number of switches and hosts with the BGP service enabled during the designated time period
Total number of BGP-related alarms received during the designated time period
ChartDistribution of new BGP-related alarms received during the designated time period

The medium BGP Service card displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for all sessions of a Network Service or Protocol.
TitleNetwork Services | All BGP Sessions
Total number of switches and hosts with the BGP service enabled during the designated time period.
Total number of BGP-related alarms received during the designated time period.
Total Nodes Running chart

Distribution of switches and hosts with the BGP service enabled during the designated time period, and a total number of nodes running the service currently.

Note: The node count here may be different than the count in the summary bar. For example, the number of nodes running BGP last week or last month might be more or less than the number of nodes running BGP currently.

Total Open Alarms chart

Distribution of BGP-related alarms received during the designated time period, and the total number of current BGP-related alarms in the network.

Note: The alarm count here may be different than the count in the summary bar. For example, the number of new alarms received in this time period does not take into account alarms that have already been received and are still active. You might have no new alarms, but still have a total number of alarms present on the network of 10.

Total Nodes Not Est. chart

Distribution of switches and hosts with unestablished BGP sessions during the designated time period, and the total number of unestablished sessions in the network currently.

Note: The node count here may be different than the count in the summary bar. For example, the number of unestablished session last week or last month might be more of less than the number of nodes with unestablished sessions currently.

The large BGP service card contains two tabs.

The Sessions Summary tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for all sessions of a Network Service or Protocol.
TitleSessions Summary (visible when you hover over card).
Total number of switches and hosts with the BGP service enabled during the designated time period.
Total number of BGP-related alarms received during the designated time period.
Total Nodes Running chart

Distribution of switches and hosts with the BGP service enabled during the designated time period, and a total number of nodes running the service currently.

Note: The node count here may be different than the count in the summary bar. For example, the number of nodes running BGP last week or last month might be more or less than the number of nodes running BGP currently.

Total Nodes Not Est. chart

Distribution of switches and hosts with unestablished BGP sessions during the designated time period, and the total number of unestablished sessions in the network currently.

Note: The node count here may be different than the count in the summary bar. For example, the number of unestablished session last week or last month might be more of less than the number of nodes with unestablished sessions currently.

Table/Filter options

When the Switches with Most Sessions filter option is selected, the table displays the switches and hosts running BGP sessions in decreasing order of session count-devices with the largest number of sessions are listed first.

When the Switches with Most Unestablished Sessions filter option is selected, the table switches and hosts running BGP sessions in decreasing order of unestablished sessions-devices with the largest number of unestablished sessions are listed first.

Show All SessionsLink to view data for all BGP sessions in the full screen card.

The Alarms tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
(in header)Indicates data is for all alarms for all BGP sessions.
TitleAlarms (visible when you hover over card).
Total number of switches and hosts with the BGP service enabled during the designated time period.
(in summary bar)Total number of BGP-related alarms received during the designated time period.
Total Alarms chart

Distribution of BGP-related alarms received during the designated time period, and the total number of current BGP-related alarms in the network.

Note: The alarm count here may be different than the count in the summary bar. For example, the number of new alarms received in this time period does not take into account alarms that have already been received and are still active. You might have no new alarms, but still have a total number of alarms present on the network of 10.

Table/Filter optionsWhen the selected filter option is Switches with Most Alarms, the table displays switches and hosts running BGP in decreasing order of the count of alarms-devices with the largest number of BGP alarms are listed first.
Show All SessionsLink to view data for all BGP sessions in the full screen card.

The full screen BGP Service card provides tabs for all switches, all sessions, and all alarms.

ItemDescription
TitleNetwork Services | BGP.
Closes full screen card and returns to workbench.
Time periodRange of time in which the displayed data was collected; applies to all card sizes; select an alternate time period by clicking .
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
All Switches tabDisplays all switches and hosts running the BGP service. By default, the device list is sorted by hostname. This tab provides the following additional data about each device:
  • Agent
    • State: Indicates communication state of the NetQ Agent on a given device. Values include Fresh (heard from recently) and Rotten (not heard from recently).
    • Version: Software version number of the NetQ Agent on a given device. This should match the version number of the NetQ software loaded on your server or appliance; for example, 2.2.0.
  • ASIC
    • Core BW: Maximum sustained/rated bandwidth. Example values include 2.0 T and 720 G.
    • Model: Chip family. Example values include Tomahawk, Trident, and Spectrum.
    • Model Id: Identifier of networking ASIC model. Example values include BCM56960 and BCM56854.
    • Ports: Indicates port configuration of the switch. Example values include 32 x 100G-QSFP28, 48 x 10G-SFP+, and 6 x 40G-QSFP+.
    • Vendor: Manufacturer of the chip. Example values include Broadcom and Mellanox.
  • CPU
    • Arch: Microprocessor architecture type. Values include x86_64 (Intel), ARMv7 (AMD), and PowerPC.
    • Max Freq: Highest rated frequency for CPU. Example values include 2.40 GHz and 1.74 GHz.
    • Model: Chip family. Example values include Intel Atom C2538 and Intel Atom C2338.
    • Nos: Number of cores. Example values include 2, 4, and 8.
  • Disk Total Size: Total amount of storage space in physical disks (not total available). Example values: 10 GB, 20 GB, 30 GB.
  • License State: Indicator of validity. Values include ok and bad.
  • Memory Size: Total amount of local RAM. Example values include 8192 MB and 2048 MB.
  • OS
    • Vendor: Operating System manufacturer. Values include Cumulus Networks, RedHat, Ubuntu, and CentOS.
    • Version: Software version number of the OS. Example values include 3.7.3, 2.5.x, 16.04, 7.1.
    • Version Id: Identifier of the OS version. For Cumulus, this is the same as the Version (3.7.x).
  • Platform
    • Date: Date and time the platform was manufactured. Example values include 7/12/18 and 10/29/2015.
    • MAC: System MAC address. Example value: 17:01:AB:EE:C3:F5.
    • Model: Manufacturer's model name. Examples values include AS7712-32X and S4048-ON.
    • Number: Manufacturer part number. Examples values include FP3ZZ7632014A, 0J09D3.
    • Revision: Release version of the platform.
    • Series: Manufacturer serial number. Example values include D2060B2F044919GD000060, CN046MRJCES0085E0004.
    • Vendor: Manufacturer of the platform. Example values include Cumulus Express, Dell, EdgeCore, Lenovo, Mellanox.
  • Time: Date and time the data was collected from device.
All Sessions tabDisplays all BGP sessions networkwide. By default, the session list is sorted by hostname. This tab provides the following additional data about each session:
  • ASN: Autonomous System Number, identifier for a collection of IP networks and routers. Example values include 633284,655435.
  • Conn Dropped: Number of dropped connections for a given session.
  • Conn Estd: Number of connections established for a given session.
  • DB State: Session state of DB.
  • Evpn Pfx Rcvd: Address prefix received for EVPN traffic. Examples include 115, 35.
  • Ipv4, and Ipv6 Pfx Rcvd: Address prefix received for IPv4 or IPv6 traffic. Examples include 31, 14, 12.
  • Last Reset Time: Date and time at which the session was last established or reset.
  • Objid: Object identifier for service.
  • OPID: Customer identifier. This is always zero.
  • Peer
    • ASN: Autonomous System Number for peer device
    • Hostname: User-defined name for peer device
    • Name: Interface name or hostname of peer device
    • Router Id: IP address of router with access to the peer device
  • Reason: Text describing the cause of, or trigger for, an event.
  • Rx and Tx Families: Address families supported for the receive and transmit session channels. Values include ipv4, ipv6, and evpn.
  • State: Current state of the session. Values include Established and NotEstd (not established).
  • Timestamp: Date and time session was started, deleted, updated or marked dead (device is down).
  • Upd8 Rx: Count of protocol messages received.
  • Upd8 Tx: Count of protocol messages transmitted.
  • Up Time: Number of seconds the session has been established, in EPOCH notation. Example: 1550147910000.
  • Vrf: Name of the Virtual Route Forwarding interface. Examples: default, mgmt, DataVrf1081.
  • Vrfid: Integer identifier of the VRF interface when used. Examples: 14, 25, 37.
All Alarms tabDisplays all BGP events networkwide. By default, the event list is sorted by time, with the most recent events listed first. The tab provides the following additional data about each event:
  • Source: Hostname of network device that generated the event.
  • Message: Text description of a BGP-related event. Example: BGP session with peer tor-1 swp7 vrf default state changed from failed to Established.
  • Type: Network protocol or service generating the event. This always has a value of bgp in this card workflow.
  • Severity: Importance of the event. Values include critical, warning, info, and debug.
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

BGP Session Card

The small BGP Session card displays:

ItemDescription
Indicates data is for a single session of a Network Service or Protocol.
TitleBGP Session.

Hostnames of the two devices in a session. Arrow points from the host to the peer.
, Current status of the session, either established or not established.

The medium BGP Session card displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for a single session of a Network Service or Protocol.
TitleNetwork Services | BGP Session.

Hostnames of the two devices in a session. Arrow points in the direction of the session.
, Current status of the session, either established or not established.
Time period for chartTime period for the chart data.
Session State Changes ChartHeat map of the state of the given session over the given time period. The status is sampled at a rate consistent with the time period. For example, for a 24 hour period, a status is collected every hour. Refer to Granularity of Data Shown Based on Time Period.
Peer NameInterface name on or hostname for peer device.
Peer ASNAutonomous System Number for peer device.
Peer Router IDIP address of router with access to the peer device.
Peer HostnameUser-defined name for peer device.

The large BGP Session card contains two tabs.

The Session Summary tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for a single session of a Network Service or Protocol.
TitleSession Summary (Network Services | BGP Session).
Summary bar

Hostnames of the two devices in a session.

Current status of the session-either established , or not established .

Session State Changes ChartHeat map of the state of the given session over the given time period. The status is sampled at a rate consistent with the time period. For example, for a 24 hour period, a status is collected every hour. Refer to Granularity of Data Shown Based on Time Period.
Alarm Count ChartDistribution and count of BGP alarm events over the given time period.
Info Count ChartDistribution and count of BGP info events over the given time period.
Connection Drop CountNumber of times the session entered the not established state during the time period.
ASNAutonomous System Number for host device.
RX/TX FamiliesReceive and Transmit address types supported. Values include IPv4, IPv6, and EVPN.
Peer HostnameUser-defined name for peer device.
Peer InterfaceInterface on which the session is connected.
Peer ASNAutonomous System Number for peer device.
Peer Router IDIP address of router with access to the peer device.

The Configuration File Evolution tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates configuration file information for a single session of a Network Service or Protocol.
Title(Network Services | BGP Session) Configuration File Evolution.
Device identifiers (hostname, IP address, or MAC address) for host and peer in session. Click on to open associated device card.
, Indication of host role, primary or secondary .
TimestampsWhen changes to the configuration file have occurred, the date and time are indicated. Click the time to see the changed file.
Configuration File

When File is selected, the configuration file as it was at the selected time is shown.

When Diff is selected, the configuration file at the selected time is shown on the left and the configuration file at the previous timestamp is shown on the right. Differences are highlighted.

Note: If no configuration file changes have been made, only the original file date is shown.

The full screen BGP Session card provides tabs for all BGP sessions and all events.

ItemDescription
TitleNetwork Services | BGP.
Closes full screen card and returns to workbench.
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
All BGP Sessions tabDisplays all BGP sessions running on the host device. This tab provides the following additional data about each session:
  • ASN: Autonomous System Number, identifier for a collection of IP networks and routers. Example values include 633284,655435.
  • Conn Dropped: Number of dropped connections for a given session.
  • Conn Estd: Number of connections established for a given session.
  • DB State: Session state of DB.
  • Evpn Pfx Rcvd: Address prefix for EVPN traffic. Examples include 115, 35.
  • Ipv4, and Ipv6 Pfx Rcvd: Address prefix for IPv4 or IPv6 traffic. Examples include 31, 14, 12.
  • Last Reset Time: Time at which the session was last established or reset.
  • Objid: Object identifier for service.
  • OPID: Customer identifier. This is always zero.
  • Peer:
    • ASN: Autonomous System Number for peer device
    • Hostname: User-defined name for peer device
    • Name: Interface name or hostname of peer device
    • Router Id: IP address of router with access to the peer device
  • Reason: Event or cause of failure.
  • Rx and Tx Families: Address families supported for the receive and transmit session channels. Values include ipv4, ipv6, and evpn.
  • State: Current state of the session. Values include Established and NotEstd (not established).
  • Timestamp: Date and time session was started, deleted, updated or marked dead (device is down).
  • Upd8 Rx: Count of protocol messages received.
  • Upd8 Tx: Count of protocol messages transmitted.
  • Up Time: Number of seconds the session has be established, in EPOC notation. Example: 1550147910000.
  • Vrf: Name of the Virtual Route Forwarding interface. Examples: default, mgmt, DataVrf1081.
  • Vrfid: Integer identifier of the VRF interface when used. Examples: 14, 25, 37.
All Events tabDisplays all events networkwide. By default, the event list is sorted by time, with the most recent events listed first. The tab provides the following additional data about each event:
  • Message: Text description of a BGP-related event. Example: BGP session with peer tor-1 swp7 vrf default state changed from failed to Established.
  • Source: Hostname of network device that generated the event.
  • Severity: Importance of the event. Values include critical, warning, info, and debug.
  • Type: Network protocol or service generating the event. This always has a value of bgp in this card workflow.
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

With NetQ, you can monitor the number of nodes running the EVPN service, view switches with the sessions, total number of VNIs, and alarms triggered by the EVPN service. For an overview and how to configure EVPN in your data center network, refer to Ethernet Virtual Private Network-EVPN.

EVPN Service Card

The small EVPN Service card displays:

ItemDescription
Indicates data is for all sessions of a Network Service or Protocol
TitleEVPN: All EVPN Sessions, or the EVPN Service
Total number of switches and hosts with the EVPN service enabled during the designated time period
Total number of EVPN-related alarms received during the designated time period
ChartDistribution of EVPN-related alarms received during the designated time period

The medium EVPN Service card displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for all sessions of a Network Service or Protocol.
TitleNetwork Services | All EVPN Sessions.
Total number of switches and hosts with the EVPN service enabled during the designated time period.
Total number of EVPN-related alarms received during the designated time period.
Total Nodes Running chart

Distribution of switches and hosts with the EVPN service enabled during the designated time period, and a total number of nodes running the service currently.

Note: The node count here may be different than the count in the summary bar. For example, the number of nodes running EVPN last week or last month might be more or less than the number of nodes running EVPN currently.

Total Open Alarms chart

Distribution of EVPN-related alarms received during the designated time period, and the total number of current EVPN-related alarms in the network.

Note: The alarm count here may be different than the count in the summary bar. For example, the number of new alarms received in this time period does not take into account alarms that have already been received and are still active. You might have no new alarms, but still have a total number of alarms present on the network of 10.

Total Sessions chartDistribution of EVPN sessions during the designated time period, and the total number of sessions running on the network currently.

The large EVPN service card contains two tabs.

The Sessions Summary tab which displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for all sessions of a Network Service or Protocol.
TitleSessions Summary (visible when you hover over card).
Total number of switches and hosts with the EVPN service enabled during the designated time period.
Total number of EVPN-related alarms received during the designated time period.
Total Nodes Running chart

Distribution of switches and hosts with the EVPN service enabled during the designated time period, and a total number of nodes running the service currently.

Note: The node count here may be different than the count in the summary bar. For example, the number of nodes running EVPN last week or last month might be more or less than the number of nodes running EVPN currently.

Total Sessions chartDistribution of EVPN sessions during the designated time period, and the total number of sessions running on the network currently.
Total L3 VNIs chartDistribution of layer 3 VXLAN Network Identifiers during this time period, and the total number of VNIs in the network currently.
Table/Filter options

When the Top Switches with Most Sessions filter is selected, the table displays devices running EVPN sessions in decreasing order of session count-devices with the largest number of sessions are listed first.

When the Switches with Most L2 EVPN filter is selected, the table displays devices running layer 2 EVPN sessions in decreasing order of session count-devices with the largest number of sessions are listed first.

When the Switches with Most L3 EVPN filter is selected, the table displays devices running layer 3 EVPN sessions in decreasing order of session count-devices with the largest number of sessions are listed first.

Show All SessionsLink to view data for all EVPN sessions network-wide in the full screen card.

The Alarms tab which displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
(in header)Indicates data is for all alarms for all sessions of a Network Service or Protocol.
TitleAlarms (visible when you hover over card).
Total number of switches and hosts with the EVPN service enabled during the designated time period.
(in summary bar)Total number of EVPN-related alarms received during the designated time period.
Total Alarms chart

Distribution of EVPN-related alarms received during the designated time period, and the total number of current BGP-related alarms in the network.

Note: The alarm count here may be different than the count in the summary bar. For example, the number of new alarms received in this time period does not take into account alarms that have already been received and are still active. You might have no new alarms, but still have a total number of alarms present on the network of 10.

Table/Filter optionsWhen the Events by Most Active Device filter is selected, the table displays devices running EVPN sessions in decreasing order of alarm count-devices with the largest number of alarms are listed first.
Show All SessionsLink to view data for all EVPN sessions in the full screen card.

The full screen EVPN Service card provides tabs for all switches, all sessions, all alarms.

ItemDescription
TitleNetwork Services | EVPN
Closes full screen card and returns to workbench.
Time periodRange of time in which the displayed data was collected; applies to all card sizes; select an alternate time period by clicking .
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
All Switches tabDisplays all switches and hosts running the EVPN service. By default, the device list is sorted by hostname. This tab provides the following additional data about each device:
  • Agent
    • State: Indicates communication state of the NetQ Agent on a given device. Values include Fresh (heard from recently) and Rotten (not heard from recently).
    • Version: Software version number of the NetQ Agent on a given device. This should match the version number of the NetQ software loaded on your server or appliance; for example, 2.1.0.
  • ASIC
    • Core BW: Maximum sustained/rated bandwidth. Example values include 2.0 T and 720 G.
    • Model: Chip family. Example values include Tomahawk, Trident, and Spectrum.
    • Model Id: Identifier of networking ASIC model. Example values include BCM56960 and BCM56854.
    • Ports: Indicates port configuration of the switch. Example values include 32 x 100G-QSFP28, 48 x 10G-SFP+, and 6 x 40G-QSFP+.
    • Vendor: Manufacturer of the chip. Example values include Broadcom and Mellanox.
  • CPU
    • Arch: Microprocessor architecture type. Values include x86_64 (Intel), ARMv7 (AMD), and PowerPC.
    • Max Freq: Highest rated frequency for CPU. Example values include 2.40 GHz and 1.74 GHz.
    • Model: Chip family. Example values include Intel Atom C2538 and Intel Atom C2338.
    • Nos: Number of cores. Example values include 2, 4, and 8.
  • Disk Total Size: Total amount of storage space in physical disks (not total available). Example values: 10 GB, 20 GB, 30 GB.
  • License State: Indicator of validity. Values include ok and bad.
  • Memory Size: Total amount of local RAM. Example values include 8192 MB and 2048 MB.
  • OS
    • Vendor: Operating System manufacturer. Values include Cumulus Networks, RedHat, Ubuntu, and CentOS.
    • Version: Software version number of the OS. Example values include 3.7.3, 2.5.x, 16.04, 7.1.
    • Version Id: Identifier of the OS version. For Cumulus, this is the same as the Version (3.7.x).
  • Platform
    • Date: Date and time the platform was manufactured. Example values include 7/12/18 and 10/29/2015.
    • MAC: System MAC address. Example value: 17:01:AB:EE:C3:F5.
    • Model: Manufacturer's model name. Examples include AS7712-32X and S4048-ON.
    • Number: Manufacturer part number. Examples values include FP3ZZ7632014A, 0J09D3.
    • Revision: Release version of the platform.
    • Series: Manufacturer serial number. Example values include D2060B2F044919GD000060, CN046MRJCES0085E0004.
    • Vendor: Manufacturer of the platform. Example values include Cumulus Express, Dell, EdgeCore, Lenovo, Mellanox.
  • Time: Date and time the data was collected from device.
All Sessions tabDisplays all EVPN sessions network-wide. By default, the session list is sorted by hostname. This tab provides the following additional data about each session:
  • Adv All Vni: Indicates whether the VNI state is advertising all VNIs (true) or not (false).
  • Adv Gw Ip: Indicates whether the host device is advertising the gateway IP address (true) or not (false).
  • DB State: Session state of the DB.
  • Export RT: IP address and port of the export route target used in the filtering mechanism for BGP route exchange.
  • Import RT: IP address and port of the import route target used in the filtering mechanism for BGP route exchange.
  • In Kernel: Indicates whether the associated VNI is in the kernel (in kernel) or not (not in kernel).
  • Is L3: Indicates whether the session is part of a layer 3 configuration (true) or not (false).
  • Origin Ip: Host device's local VXLAN tunnel IP address for the EVPN instance.
  • OPID: LLDP service identifier.
  • Rd: Route distinguisher used in the filtering mechanism for BGP route exchange.
  • Timestamp: Date and time the session was started, deleted, updated or marked as dead (device is down).
  • Vni: Name of the VNI where session is running.
All Alarms tabDisplays all EVPN events network-wide. By default, the event list is sorted by time, with the most recent events listed first. The tab provides the following additional data about each event:
  • Message: Text description of a EVPN-related event. Example: VNI 3 kernel state changed from down to up.
  • Source: Hostname of network device that generated the event.
  • Severity: Importance of the event. Values include critical, warning, info, and debug.
  • Type: Network protocol or service generating the event. This always has a value of evpn in this card workflow.
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

EVPN Session Card

The small EVPN Session card displays:

ItemDescription
Indicates data is for an EVPN session
TitleEVPN Session
VNI NameName of the VNI (virtual network instance) used for this EVPN session
Current VNI NodesTotal number of VNI nodes participating in the EVPN session currently

The medium EVPN Session card displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes
Indicates data is for an EVPN session
TitleNetwork Services | EVPN Session
Summary barVTEP (VXLAN Tunnel EndPoint) Count: Total number of VNI nodes participating in the EVPN session currently
VTEP Count Over Time chartDistribution of VTEP counts during the designated time period
VNI NameName of the VNI used for this EVPN session
TypeIndicates whether the session is established as part of a layer 2 or layer 3 overlay network

The large EVPN Session card contains two tabs.

The Session Summary tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes
Indicates data is for an EVPN session
TitleSession Summary (Network Services | EVPN Session)
Summary barVTEP (VXLAN Tunnel EndPoint) Count: Total number of VNI devices participating in the EVPN session currently
VTEP Count Over Time chartDistribution of VTEPs during the designated time period
Alarm Count chartDistribution of alarms during the designated time period
Info Count chartDistribution of info events during the designated time period
TableVRF (for layer 3) or VLAN (for layer 2) identifiers by device

The Configuration File Evolution tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates configuration file information for a single session of a Network Service or Protocol.
Title(Network Services | EVPN Session) Configuration File Evolution.
VTEP count (currently).
TimestampsWhen changes to the configuration file have occurred, the date and time are indicated. Click the time to see the changed file.
Configuration File

When File is selected, the configuration file as it was at the selected time is shown.

When Diff is selected, the configuration file at the selected time is shown on the left and the configuration file at the previous timestamp is shown on the right. Differences are highlighted.

Note: If no configuration file changes have been made, only the original file date is shown.

The full screen EVPN Session card provides tabs for all EVPN sessions and all events.

ItemDescription
TitleNetwork Services | EVPN.
Closes full screen card and returns to workbench.
Time periodRange of time in which the displayed data was collected; applies to all card sizes; select an alternate time period by clicking .
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
All EVPN Sessions tabDisplays all EVPN sessions network-wide. By default, the session list is sorted by hostname. This tab provides the following additional data about each session:
  • Adv All Vni: Indicates whether the VNI state is advertising all VNIs (true) or not (false).
  • Adv Gw Ip: Indicates whether the host device is advertising the gateway IP address (true) or not (false).
  • DB State: Session state of the DB.
  • Export RT: IP address and port of the export route target used in the filtering mechanism for BGP route exchange.
  • Import RT: IP address and port of the import route target used in the filtering mechanism for BGP route exchange.
  • In Kernel: Indicates whether the associated VNI is in the kernel (in kernel) or not (not in kernel).
  • Is L3: Indicates whether the session is part of a layer 3 configuration (true) or not (false).
  • Origin Ip: Host device's local VXLAN tunnel IP address for the EVPN instance.
  • OPID: LLDP service identifier.
  • Rd: Route distinguisher used in the filtering mechanism for BGP route exchange.
  • Timestamp: Date and time the session was started, deleted, updated or marked as dead (device is down).
  • Vni: Name of the VNI where session is running.
All Events tabDisplays all events network-wide. By default, the event list is sorted by time, with the most recent events listed first. The tab provides the following additional data about each event:
  • Message: Text description of a EVPN-related event. Example: VNI 3 kernel state changed from down to up.
  • Source: Hostname of network device that generated the event.
  • Severity: Importance of the event. Values include critical, warning, info, and debug.
  • Type: Network protocol or service generating the event. This always has a value of evpn in this card workflow.
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

LLDP Service Card

With NetQ, you can monitor the number of nodes running the LLDP service, view nodes with the most LLDP neighbor nodes, those nodes with the least neighbor nodes, and view alarms triggered by the LLDP service. For an overview and how to configure LLDP in your data center network, refer to Link Layer Discovery Protocol.

The small LLDP Service card displays:

ItemDescription
Indicates data is for all sessions of a Network Service or Protocol.
TitleLLDP: All LLDP Sessions, or the LLDP Service.
Total number of switches with the LLDP service enabled during the designated time period.
Total number of LLDP-related alarms received during the designated time period.
ChartDistribution of LLDP-related alarms received during the designated time period.

The medium LLDP Service card displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for all sessions of a Network Service or Protocol.
TitleLLDP: All LLDP Sessions, or the LLDP Service.
Total number of switches with the LLDP service enabled during the designated time period.
Total number of LLDP-related alarms received during the designated time period.
Total Nodes Running chart

Distribution of switches and hosts with the LLDP service enabled during the designated time period, and a total number of nodes running the service currently.

Note: The node count here may be different than the count in the summary bar. For example, the number of nodes running LLDP last week or last month might be more or less than the number of nodes running LLDP currently.

Total Open Alarms chart

Distribution of LLDP-related alarms received during the designated time period, and the total number of current LLDP-related alarms in the network.

Note: The alarm count here may be different than the count in the summary bar. For example, the number of new alarms received in this time period does not take into account alarms that have already been received and are still active. You might have no new alarms, but still have a total number of alarms present on the network of 10.

Total Sessions chartDistribution of LLDP sessions running during the designated time period, and the total number of sessions running on the network currently.

The large LLDP service card contains two tabs.

The Sessions Summary tab which displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for all sessions of a Network Service or Protocol.
TitleSessions Summary (Network Services | All LLDP Sessions).
Total number of switches with the LLDP service enabled during the designated time period.
Total number of LLDP-related alarms received during the designated time period.
Total Nodes Running chart

Distribution of switches and hosts with the LLDP service enabled during the designated time period, and a total number of nodes running the service currently.

Note: The node count here may be different than the count in the summary bar. For example, the number of nodes running LLDP last week or last month might be more or less than the number of nodes running LLDP currently.

Total Sessions chartDistribution of LLDP sessions running during the designated time period, and the total number of sessions running on the network currently.
Total Sessions with No Nbr chartDistribution of LLDP sessions missing neighbor information during the designated time period, and the total number of session missing neighbors in the network currently.
Table/Filter options

When the Switches with Most Sessions filter is selected, the table displays switches running LLDP sessions in decreasing order of session count-devices with the largest number of sessions are listed first.

When the Switches with Most Unestablished Sessions filter is selected, the table displays switches running LLDP sessions in decreasing order of unestablished session count-devices with the largest number of unestablished sessions are listed first.

Show All SessionsLink to view all LLDP sessions in the full screen card.

The Alarms tab which displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
(in header)Indicates data is all alarms for all LLDP sessions.
TitleAlarms (visible when you hover over card).
Total number of switches with the LLDP service enabled during the designated time period.
(in summary bar)Total number of LLDP-related alarms received during the designated time period.
Total Alarms chart

Distribution of LLDP-related alarms received during the designated time period, and the total number of current LLDP-related alarms in the network.

Note: The alarm count here may be different than the count in the summary bar. For example, the number of new alarms received in this time period does not take into account alarms that have already been received and are still active. You might have no new alarms, but still have a total number of alarms present on the network of 10.

Table/Filter optionsWhen the Events by Most Active Device filter is selected, the table displays switches running LLDP sessions in decreasing order of alarm count-devices with the largest number of sessions are listed first
Show All SessionsLink to view all LLDP sessions in the full screen card.

The full screen LLDP Service card provides tabs for all switches, all sessions, and all alarms.

ItemDescription
TitleNetwork Services | LLDP.
Closes full screen card and returns to workbench.
Time periodRange of time in which the displayed data was collected; applies to all card sizes; select an alternate time period by clicking .
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
All Switches tabDisplays all switches and hosts running the LLDP service. By default, the device list is sorted by hostname. This tab provides the following additional data about each device:
  • Agent
    • State: Indicates communication state of the NetQ Agent on a given device. Values include Fresh (heard from recently) and Rotten (not heard from recently).
    • Version: Software version number of the NetQ Agent on a given device. This should match the version number of the NetQ software loaded on your server or appliance; for example, 2.1.0.
  • ASIC
    • Core BW: Maximum sustained/rated bandwidth. Example values include 2.0 T and 720 G.
    • Model: Chip family. Example values include Tomahawk, Trident, and Spectrum.
    • Model Id: Identifier of networking ASIC model. Example values include BCM56960 and BCM56854.
    • Ports: Indicates port configuration of the switch. Example values include 32 x 100G-QSFP28, 48 x 10G-SFP+, and 6 x 40G-QSFP+.
    • Vendor: Manufacturer of the chip. Example values include Broadcom and Mellanox.
  • CPU
    • Arch: Microprocessor architecture type. Values include x86_64 (Intel), ARMv7 (AMD), and PowerPC.
    • Max Freq: Highest rated frequency for CPU. Example values include 2.40 GHz and 1.74 GHz.
    • Model: Chip family. Example values include Intel Atom C2538 and Intel Atom C2338.
    • Nos: Number of cores. Example values include 2, 4, and 8.
  • Disk Total Size: Total amount of storage space in physical disks (not total available). Example values: 10 GB, 20 GB, 30 GB.
  • License State: Indicator of validity. Values include ok and bad.
  • Memory Size: Total amount of local RAM. Example values include 8192 MB and 2048 MB.
  • OS
    • Vendor: Operating System manufacturer. Values include Cumulus Networks, RedHat, Ubuntu, and CentOS.
    • Version: Software version number of the OS. Example values include 3.7.3, 2.5.x, 16.04, 7.1.
    • Version Id: Identifier of the OS version. For Cumulus, this is the same as the Version (3.7.x).
  • Platform
    • Date: Date and time the platform was manufactured. Example values include 7/12/18 and 10/29/2015.
    • MAC: System MAC address. Example value: 17:01:AB:EE:C3:F5.
    • Model: Manufacturer's model name. Examples include AS7712-32X and S4048-ON.
    • Number: Manufacturer part number. Examples values include FP3ZZ7632014A, 0J09D3.
    • Revision: Release version of the platform.
    • Series: Manufacturer serial number. Example values include D2060B2F044919GD000060, CN046MRJCES0085E0004.
    • Vendor: Manufacturer of the platform. Example values include Cumulus Express, Dell, EdgeCore, Lenovo, Mellanox.
  • Time: Date and time the data was collected from device.
All Sessions tabDisplays all LLDP sessions networkwide. By default, the session list is sorted by hostname. This tab provides the following additional data about each session:
  • Ifname: Name of the host interface where LLDP session is running
  • LLDP Peer:
    • Os: Operating system (OS) used by peer device. Values include Cumulus Linux, RedHat, Ubuntu, and CentOS.
    • Osv: Version of the OS used by peer device. Example values include 3.7.3, 2.5.x, 16.04, 7.1.
    • Bridge: Indicates whether the peer device is a bridge (true) or not (false)
    • Router: Indicates whether the peer device is a router (true) or not (false)
    • Station: Indicates whether the peer device is a station (true) or not (false)
  • Peer:
    • Hostname: User-defined name for the peer device
    • Ifname: Name of the peer interface where the session is running
  • Timestamp: Date and time that the session was started, deleted, updated, or marked dead (device is down)
All Alarms tabDisplays all LLDP events networkwide. By default, the event list is sorted by time, with the most recent events listed first. The tab provides the following additional data about each event:
  • Message: Text description of a LLDP-related event. Example: LLDP Session with host leaf02 swp6 modified fields leaf06 swp21.
  • Source: Hostname of network device that generated the event.
  • Severity: Importance of the event. Values include critical, warning, info, and debug.
  • Type: Network protocol or service generating the event. This always has a value of lldp in this card workflow.
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

LLDP Session Card

The small LLDP Session card displays:

ItemDescription
Indicates data is for a single session of a Network Service or Protocol.
TitleLLDP Session.
Host and peer devices in session. Host is shown on top, with peer below.
, Indicates whether the host sees the peer or not; has a peer, no peer.

The medium LLDP Session card displays:

ItemDescription
Time periodRange of time in which the displayed data was collected.
Indicates data is for a single session of a Network Service or Protocol.
TitleLLDP Session.
Host and peer devices in session. Arrow points from host to peer.
, Indicates whether the host sees the peer or not; has a peer, no peer.
Time periodRange of time for the distribution chart.
Heat mapDistribution of neighbor availability (detected or undetected) during this given time period.
HostnameUser-defined name of the host device.
Interface NameSoftware interface on the host device where the session is running.
Peer HostnameUser-defined name of the peer device.
Peer Interface NameSoftware interface on the peer where the session is running.

The large LLDP Session card contains two tabs.

The Session Summary tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected.
Indicates data is for a single session of a Network Service or Protocol.
TitleSummary Session (Network Services | LLDP Session).
Host and peer devices in session. Arrow points from host to peer.
, Indicates whether the host sees the peer or not; has a peer, no peer.
Heat mapDistribution of neighbor state (detected or undetected) during this given time period.
Alarm Count chartDistribution and count of LLDP alarm events during the given time period.
Info Count chartDistribution and count of LLDP info events during the given time period.
Host Interface NameSoftware interface on the host where the session is running.
Peer HostnameUser-defined name of the peer device.
Peer Interface NameSoftware interface on the peer where the session is running.

The Configuration File Evolution tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates configuration file information for a single session of a Network Service or Protocol.
Title(Network Services | LLDP Session) Configuration File Evolution.
Device identifiers (hostname, IP address, or MAC address) for host and peer in session. Click to open associated device card.
, Indicates whether the host sees the peer or not; has a peer, no peer.
TimestampsWhen changes to the configuration file have occurred, the date and time are indicated. Click the time to see the changed file.
Configuration File

When File is selected, the configuration file as it was at the selected time is shown. When Diff is selected, the configuration file at the selected time is shown on the left and the configuration file at the previous timestamp is shown on the right. Differences are highlighted.

Note: If no configuration file changes have been made, the card shows no results.

The full screen LLDP Session card provides tabs for all LLDP sessions and all events.

ItemDescription
TitleNetwork Services | LLDP.
Closes full screen card and returns to workbench.
Time periodRange of time in which the displayed data was collected; applies to all card sizes; select an alternate time period by clicking .
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
All LLDP Sessions tabDisplays all LLDP sessions on the host device. By default, the session list is sorted by hostname. This tab provides the following additional data about each session:
  • Ifname: Name of the host interface where LLDP session is running.
  • LLDP Peer:
    • Os: Operating system (OS) used by peer device. Values include Cumulus Linux, RedHat, Ubuntu, and CentOS.
    • Osv: Version of the OS used by peer device. Example values include 3.7.3, 2.5.x, 16.04, 7.1.
    • Bridge: Indicates whether the peer device is a bridge (true) or not (false).
    • Router: Indicates whether the peer device is a router (true) or not (false).
    • Station: Indicates whether the peer device is a station (true) or not (false).
  • Peer:
    • Hostname: User-defined name for the peer device.
    • Ifname: Name of the peer interface where the session is running.
  • Timestamp: Date and time that the session was started, deleted, updated, or marked dead (device is down).
All Events tabDisplays all events networkwide. By default, the event list is sorted by time, with the most recent events listed first. The tab provides the following additional data about each event:
  • Message: Text description of an event. Example: LLDP Session with host leaf02 swp6 modified fields leaf06 swp21.
  • Source: Hostname of network device that generated the event.
  • Severity: Importance of the event. Values include critical, warning, info, and debug.
  • Type: Network protocol or service generating the event. This always has a value of lldp in this card workflow.
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

MLAG Service Card

The small MLAG Service card displays:

ItemDescription
Indicates data is for all sessions of a Network Service or Protocol
TitleMLAG: All MLAG Sessions, or the MLAG Service
Total number of switches with the MLAG service enabled during the designated time period
Total number of MLAG-related alarms received during the designated time period
ChartDistribution of MLAG-related alarms received during the designated time period

The medium MLAG Service card displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for all sessions of a Network Service or Protocol.
TitleNetwork Services | All MLAG Sessions.
Total number of switches with the MLAG service enabled during the designated time period.
Total number of MLAG-related alarms received during the designated time period.
Total number of sessions with an inactive backup IP address during the designated time period.
Total number of bonds with only a single connection during the designated time period.
Total Nodes Running chart

Distribution of switches and hosts with the MLAG service enabled during the designated time period, and a total number of nodes running the service currently.

Note: The node count here may be different than the count in the summary bar. For example, the number of nodes running MLAG last week or last month might be more or less than the number of nodes running MLAG currently.

Total Open Alarms chart

Distribution of MLAG-related alarms received during the designated time period, and the total number of current MLAG-related alarms in the network.

Note: The alarm count here may be different than the count in the summary bar. For example, the number of new alarms received in this time period does not take into account alarms that have already been received and are still active. You might have no new alarms, but still have a total number of alarms present on the network of 10.

Total Sessions chartDistribution of MLAG sessions running during the designated time period, and the total number of sessions running on the network currently.

The large MLAG service card contains two tabs.

The All MLAG Sessions summary tab which displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for all sessions of a Network Service or Protocol.
TitleAll MLAG Sessions Summary
Total number of switches with the MLAG service enabled during the designated time period.
Total number of MLAG-related alarms received during the designated time period.
Total Nodes Running chart

Distribution of switches and hosts with the MLAG service enabled during the designated time period, and a total number of nodes running the service currently.

Note: The node count here may be different than the count in the summary bar. For example, the number of nodes running MLAG last week or last month might be more or less than the number of nodes running MLAG currently.

Total Sessions chart

Distribution of MLAG sessions running during the designated time period, and the total number of sessions running on the network currently.

Total Sessions with Inactive-backup-ip chartDistribution of sessions without an active backup IP defined during the designated time period, and the total number of these sessions running on the network currently.
Table/Filter options

When the Switches with Most Sessions filter is selected, the table displays switches running MLAG sessions in decreasing order of session count-devices with the largest number of sessions are listed first.

When the Switches with Most Unestablished Sessions filter is selected, the table displays switches running MLAG sessions in decreasing order of unestablished session count-devices with the largest number of unestablished sessions are listed first.

Show All SessionsLink to view all MLAG sessions in the full screen card.

The All MLAG Alarms tab which displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
(in header)Indicates alarm data for all MLAG sessions.
TitleNetwork Services | All MLAG Alarms (visible when you hover over card).
Total number of switches with the MLAG service enabled during the designated time period.
(in summary bar)Total number of MLAG-related alarms received during the designated time period.
Total Alarms chart

Distribution of MLAG-related alarms received during the designated time period, and the total number of current MLAG-related alarms in the network.

Note: The alarm count here may be different than the count in the summary bar. For example, the number of new alarms received in this time period does not take into account alarms that have already been received and are still active. You might have no new alarms, but still have a total number of alarms present on the network of 10.

Table/Filter optionsWhen the Events by Most Active Device filter is selected, the table displays switches running MLAG sessions in decreasing order of alarm count-devices with the largest number of sessions are listed first.
Show All SessionsLink to view all MLAG sessions in the full screen card.

The full screen MLAG Service card provides tabs for all switches, all sessions, and all alarms.

ItemDescription
TitleNetwork Services | MLAG.
Closes full screen card and returns to workbench.
Time periodRange of time in which the displayed data was collected; applies to all card sizes; select an alternate time period by clicking .
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
All Switches tabDisplays all switches and hosts running the MLAG service. By default, the device list is sorted by hostname. This tab provides the following additional data about each device:
  • Agent
    • State: Indicates communication state of the NetQ Agent on a given device. Values include Fresh (heard from recently) and Rotten (not heard from recently).
    • Version: Software version number of the NetQ Agent on a given device. This should match the version number of the NetQ software loaded on your server or appliance; for example, 2.1.0.
  • ASIC
    • Core BW: Maximum sustained/rated bandwidth. Example values include 2.0 T and 720 G.
    • Model: Chip family. Example values include Tomahawk, Trident, and Spectrum.
    • Model Id: Identifier of networking ASIC model. Example values include BCM56960 and BCM56854.
    • Ports: Indicates port configuration of the switch. Example values include 32 x 100G-QSFP28, 48 x 10G-SFP+, and 6 x 40G-QSFP+.
    • Vendor: Manufacturer of the chip. Example values include Broadcom and Mellanox.
  • CPU
    • Arch: Microprocessor architecture type. Values include x86_64 (Intel), ARMv7 (AMD), and PowerPC.
    • Max Freq: Highest rated frequency for CPU. Example values include 2.40 GHz and 1.74 GHz.
    • Model: Chip family. Example values include Intel Atom C2538 and Intel Atom C2338.
    • Nos: Number of cores. Example values include 2, 4, and 8.
  • Disk Total Size: Total amount of storage space in physical disks (not total available). Example values: 10 GB, 20 GB, 30 GB.
  • License State: Indicator of validity. Values include ok and bad.
  • Memory Size: Total amount of local RAM. Example values include 8192 MB and 2048 MB.
  • OS
    • Vendor: Operating System manufacturer. Values include Cumulus Networks, RedHat, Ubuntu, and CentOS.
    • Version: Software version number of the OS. Example values include 3.7.3, 2.5.x, 16.04, 7.1.
    • Version Id: Identifier of the OS version. For Cumulus, this is the same as the Version (3.7.x).
  • Platform
    • Date: Date and time the platform was manufactured. Example values include 7/12/18 and 10/29/2015.
    • MAC: System MAC address. Example value: 17:01:AB:EE:C3:F5.
    • Model: Manufacturer's model name. Examples values include AS7712-32X and S4048-ON.
    • Number: Manufacturer part number. Examples values include FP3ZZ7632014A, 0J09D3.
    • Revision: Release version of the platform.
    • Series: Manufacturer serial number. Example values include D2060B2F044919GD000060, CN046MRJCES0085E0004.
    • Vendor: Manufacturer of the platform. Example values include Cumulus Express, Dell, EdgeCore, Lenovo, Mellanox.
  • Time: Date and time the data was collected from device.
All Sessions tabDisplays all MLAG sessions network-wide. By default, the session list is sorted by hostname. This tab provides the following additional data about each session:
  • Backup Ip: IP address of the interface to use if the peerlink (or bond) goes down.
  • Backup Ip Active: Indicates whether the backup IP address has been specified and is active (true) or not (false).
  • Bonds
    • Conflicted: Identifies the set of interfaces in a bond that do not match on each end of the bond.
    • Single: Identifies a set of interfaces connecting to only one of the two switches.
    • Dual: Identifies a set of interfaces connecting to both switches.
    • Proto Down: Interface on the switch brought down by the clagd service. Value is blank if no interfaces are down due to clagd service.
  • Clag Sysmac: Unique MAC address for each bond interface pair. Note: Must be a value between 44:38:39:ff:00:00 and 44:38:39:ff:ff:ff.
  • Peer:
    • If: Name of the peer interface.
    • Role: Role of the peer device. Values include primary and secondary.
    • State: Indicates if peer device is up (true) or down (false).
  • Role: Role of the host device. Values include primary and secondary.
  • Timestamp: Date and time the MLAG session was started, deleted, updated, or marked dead (device went down).
  • Vxlan Anycast: Anycast IP address used for VXLAN termination.
All Alarms tabDisplays all MLAG events network-wide. By default, the event list is sorted by time, with the most recent events listed first. The tab provides the following additional data about each event:
  • Message: Text description of a MLAG-related event. Example: Clag conflicted bond changed from swp7 swp8 to swp9 swp10.
  • Source: Hostname of network device that generated the event.
  • Severity: Importance of the event. Values include critical, warning, info, and debug.
  • Type: Network protocol or service generating the event. This always has a value of clag in this card workflow.
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

MLAG Session Card

The small MLAG Session card displays:

ItemDescription
Indicates data is for a single session of a Network Service or Protocol.
TitleCLAG Session.
Device identifiers (hostname, IP address, or MAC address) for host and peer in session.
, Indication of host role, primary or secondary .

The medium MLAG Session card displays:

ItemDescription
Time period (in header)Range of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for a single session of a Network Service or Protocol.
TitleNetwork Services | MLAG Session.
Device identifiers (hostname, IP address, or MAC address) for host and peer in session. Arrow points from the host to the peer. Click to open associated device card.
, Indication of host role, primary or secondary .
Time period (above chart)Range of time for data displayed in peer status chart.
Peer Status chartDistribution of peer availability, alive or not alive, during the designated time period. The number of time segments in a time period varies according to the length of the time period.
RoleRole that host device is playing. Values include primary and secondary.
CLAG sysmacSystem MAC address of the MLAG session.
Peer RoleRole that peer device is playing. Values include primary and secondary.
Peer StateOperational state of the peer, up (true) or down (false).

The large MLAG Session card contains two tabs.

The Session Summary tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for a single session of a Network Service or Protocol.
Title(Network Services | MLAG Session) Session Summary.
Device identifiers (hostname, IP address, or MAC address) for host and peer in session. Arrow points from the host to the peer. Click to open associated device card.
, Indication of host role, primary or secondary .
Alarm Count ChartDistribution and count of CLAG alarm events over the given time period.
Info Count ChartDistribution and count of CLAG info events over the given time period.
Peer Status chartDistribution of peer availability, alive or not alive, during the designated time period. The number of time segments in a time period varies according to the length of the time period.
Backup IPIP address of the interface to use if the peerlink (or bond) goes down.
Backup IP ActiveIndicates whether the backup IP address is configured.
CLAG SysMACSystem MAC address of the MLAG session.
Peer StateOperational state of the peer, up (true) or down (false).
Count of Dual BondsNumber of bonds connecting to both switches.
Count of Single BondsNumber of bonds connecting to only one switch.
Count of Protocol Down BondsNumber of bonds with interfaces that were brought down by the clagd service.
Count of Conflicted BondsNumber of bonds which have a set of interfaces that are not the same on both switches.

The Configuration File Evolution tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates configuration file information for a single session of a Network Service or Protocol.
Title(Network Services | MLAG Session) Configuration File Evolution.
Device identifiers (hostname, IP address, or MAC address) for host and peer in session. Arrow points from the host to the peer. Click to open associated device card.
, Indication of host role, primary or secondary .
TimestampsWhen changes to the configuration file have occurred, the date and time are indicated. Click the time to see the changed file.
Configuration File

When File is selected, the configuration file as it was at the selected time is shown.

When Diff is selected, the configuration file at the selected time is shown on the left and the configuration file at the previous timestamp is shown on the right. Differences are highlighted.

The full screen MLAG Session card provides tabs for all MLAG sessions and all events.

ItemDescription
TitleNetwork Services | MLAG
Closes full screen card and returns to workbench
Time periodRange of time in which the displayed data was collected; applies to all card sizes; select an alternate time period by clicking
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab
All MLAG Sessions tabDisplays all MLAG sessions for the given session. By default, the session list is sorted by hostname. This tab provides the following additional data about each session:
  • Backup Ip: IP address of the interface to use if the peerlink (or bond) goes down.
  • Backup Ip Active: Indicates whether the backup IP address has been specified and is active (true) or not (false).
  • Bonds
    • Conflicted: Identifies the set of interfaces in a bond that do not match on each end of the bond.
    • Single: Identifies a set of interfaces connecting to only one of the two switches.
    • Dual: Identifies a set of interfaces connecting to both switches.
    • Proto Down: Interface on the switch brought down by the clagd service. Value is blank if no interfaces are down due to clagd service.
  • Mlag Sysmac: Unique MAC address for each bond interface pair. Note: Must be a value between 44:38:39:ff:00:00 and 44:38:39:ff:ff:ff.
  • Peer:
    • If: Name of the peer interface.
    • Role: Role of the peer device. Values include primary and secondary.
    • State: Indicates if peer device is up (true) or down (false).
  • Role: Role of the host device. Values include primary and secondary.
  • Timestamp: Date and time the MLAG session was started, deleted, updated, or marked dead (device went down).
  • Vxlan Anycast: Anycast IP address used for VXLAN termination.
All Events tabDisplays all events network-wide. By default, the event list is sorted by time, with the most recent events listed first. The tab provides the following additional data about each event:
  • Message: Text description of an event. Example: Clag conflicted bond changed from swp7 swp8 to swp9 swp10.
  • Source: Hostname of network device that generated the event.
  • Severity: Importance of the event. Values include critical, warning, info, and debug.
  • Type: Network protocol or service generating the event. This always has a value of clag in this card workflow.
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

OSPF Service Card

The small OSPF Service card displays:

ItemDescription
Indicates data is for all sessions of a Network Service or Protocol
TitleOSPF: All OSPF Sessions, or the OSPF Service
Total number of switches and hosts with the OSPF service enabled during the designated time period
Total number of OSPF-related alarms received during the designated time period
ChartDistribution of OSPF-related alarms received during the designated time period

The medium OSPF Service card displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for all sessions of a Network Service or Protocol.
TitleNetwork Services | All OSPF Sessions.
Total number of switches and hosts with the OSPF service enabled during the designated time period.
Total number of OSPF-related alarms received during the designated time period.
Total Nodes Running chart

Distribution of switches and hosts with the OSPF service enabled during the designated time period, and a total number of nodes running the service currently.

Note: The node count here may be different than the count in the summary bar. For example, the number of nodes running OSPF last week or last month might be more or less than the number of nodes running OSPF currently.

Total Sessions Not Established chart

Distribution of unestablished OSPF sessions during the designated time period, and the total number of unestablished sessions in the network currently.

Note: The node count here may be different than the count in the summary bar. For example, the number of unestablished session last week or last month might be more of less than the number of nodes with unestablished sessions currently.

Total Sessions chartDistribution of OSPF sessions during the designated time period, and the total number of sessions running on the network currently.

The large OSPF service card contains two tabs.

The Sessions Summary tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for all sessions of a Network Service or Protocol.
TitleSessions Summary (visible when you hover over card).
Total number of switches and hosts with the OSPF service enabled during the designated time period.
Total number of OSPF-related alarms received during the designated time period.
Total Nodes Running chart

Distribution of switches and hosts with the OSPF service enabled during the designated time period, and a total number of nodes running the service currently.

Note: The node count here may be different than the count in the summary bar. For example, the number of nodes running OSPF last week or last month might be more or less than the number of nodes running OSPF currently.

Total Sessions chartDistribution of OSPF sessions during the designated time period, and the total number of sessions running on the network currently.
Total Sessions Not Established chart

Distribution of unestablished OSPF sessions during the designated time period, and the total number of unestablished sessions in the network currently.

Note: The node count here may be different than the count in the summary bar. For example, the number of unestablished session last week or last month might be more of less than the number of nodes with unestablished sessions currently.

Table/Filter options

When the Switches with Most Sessions filter option is selected, the table displays the switches and hosts running OSPF sessions in decreasing order of session count-devices with the largest number of sessions are listed first

When the Switches with Most Unestablished Sessions filter option is selected, the table switches and hosts running OSPF sessions in decreasing order of unestablished sessions-devices with the largest number of unestablished sessions are listed first

Show All SessionsLink to view data for all OSPF sessions in the full screen card.

The Alarms tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
(in header)Indicates data is all alarms for all OSPF sessions.
TitleAlarms (visible when you hover over card).
Total number of switches and hosts with the OSPF service enabled during the designated time period.
(in summary bar)Total number of OSPF-related alarms received during the designated time period.
Total Alarms chart

Distribution of OSPF-related alarms received during the designated time period, and the total number of current OSPF-related alarms in the network.

Note: The alarm count here may be different than the count in the summary bar. For example, the number of new alarms received in this time period does not take into account alarms that have already been received and are still active. You might have no new alarms, but still have a total number of alarms present on the network of 10.

Table/Filter optionsWhen the selected filter option is Switches with Most Alarms, the table displays switches and hosts running OSPF in decreasing order of the count of alarms-devices with the largest number of OSPF alarms are listed first
Show All SessionsLink to view data for all OSPF sessions in the full screen card.

The full screen OSPF Service card provides tabs for all switches, all sessions, and all alarms.

ItemDescription
TitleNetwork Services | OSPF.
Closes full screen card and returns to workbench.
Time periodRange of time in which the displayed data was collected; applies to all card sizes; select an alternate time period by clicking .
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab
All Switches tabDisplays all switches and hosts running the OSPF service. By default, the device list is sorted by hostname. This tab provides the following additional data about each device:
  • Agent
    • State: Indicates communication state of the NetQ Agent on a given device. Values include Fresh (heard from recently) and Rotten (not heard from recently).
    • Version: Software version number of the NetQ Agent on a given device. This should match the version number of the NetQ software loaded on your server or appliance; for example, 2.1.0.
  • ASIC
    • Core BW: Maximum sustained/rated bandwidth. Example values include 2.0 T and 720 G.
    • Model: Chip family. Example values include Tomahawk, Trident, and Spectrum.
    • Model Id: Identifier of networking ASIC model. Example values include BCM56960 and BCM56854.
    • Ports: Indicates port configuration of the switch. Example values include 32 x 100G-QSFP28, 48 x 10G-SFP+, and 6 x 40G-QSFP+.
    • Vendor: Manufacturer of the chip. Example values include Broadcom and Mellanox.
  • CPU
    • Arch: Microprocessor architecture type. Values include x86_64 (Intel), ARMv7 (AMD), and PowerPC.
    • Max Freq: Highest rated frequency for CPU. Example values include 2.40 GHz and 1.74 GHz.
    • Model: Chip family. Example values include Intel Atom C2538 and Intel Atom C2338.
    • Nos: Number of cores. Example values include 2, 4, and 8.
  • Disk Total Size: Total amount of storage space in physical disks (not total available). Example values: 10 GB, 20 GB, 30 GB.
  • License State: Indicator of validity. Values include ok and bad.
  • Memory Size: Total amount of local RAM. Example values include 8192 MB and 2048 MB.
  • OS
    • Vendor: Operating System manufacturer. Values include Cumulus Networks, RedHat, Ubuntu, and CentOS.
    • Version: Software version number of the OS. Example values include 3.7.3, 2.5.x, 16.04, 7.1.
    • Version Id: Identifier of the OS version. For Cumulus, this is the same as the Version (3.7.x).
  • Platform
    • Date: Date and time the platform was manufactured. Example values include 7/12/18 and 10/29/2015.
    • MAC: System MAC address. Example value: 17:01:AB:EE:C3:F5.
    • Model: Manufacturer's model name. Examples values include AS7712-32X and S4048-ON.
    • Number: Manufacturer part number. Examples values include FP3ZZ7632014A, 0J09D3.
    • Revision: Release version of the platform.
    • Series: Manufacturer serial number. Example values include D2060B2F044919GD000060, CN046MRJCES0085E0004.
    • Vendor: Manufacturer of the platform. Example values include Cumulus Express, Dell, EdgeCore, Lenovo, Mellanox.
  • Time: Date and time the data was collected from device.
All Sessions tabDisplays all OSPF sessions networkwide. By default, the session list is sorted by hostname. This tab provides the following additional data about each session:
  • Area: Routing domain for this host device. Example values include 0.0.0.1, 0.0.0.23.
  • Ifname: Name of the interface on host device where session resides. Example values include swp5, peerlink-1.
  • Is IPv6: Indicates whether the address of the host device is IPv6 (true) or IPv4 (false).
  • Peer
    • Address: IPv4 or IPv6 address of the peer device.
    • Hostname: User-defined name for peer device.
    • ID: Network subnet address of router with access to the peer device.
  • State: Current state of OSPF. Values include Full, 2-way, Attempt, Down, Exchange, Exstart, Init, and Loading.
  • Timestamp: Date and time session was started, deleted, updated or marked dead (device is down)
All Alarms tabDisplays all OSPF events networkwide. By default, the event list is sorted by time, with the most recent events listed first. The tab provides the following additional data about each event:
  • Message: Text description of a OSPF-related event. Example: swp4 area ID mismatch with peer leaf02
  • Source: Hostname of network device that generated the event
  • Severity: Importance of the event. Values include critical, warning, info, and debug.
  • Type: Network protocol or service generating the event. This always has a value of OSPF in this card workflow.
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

OSPF Session Card

The small OSPF Session card displays:

ItemDescription
Indicates data is for a single session of a Network Service or Protocol.
TitleOSPF Session.
Hostnames of the two devices in a session. Host appears on top with peer below.
, Current state of OSPF.
Full or 2-way, Attempt, Down, Exchange, Exstart, Init, and Loading.

The medium OSPF Session card displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for a single session of a Network Service or Protocol.
TitleNetwork Services | OSPF Session.
Hostnames of the two devices in a session. Host appears on top with peer below.
, Current state of OSPF.
Full or 2-way, Attempt, Down, Exchange, Exstart, Init, and Loading.
Time period for chartTime period for the chart data.
Session State Changes ChartHeat map of the state of the given session over the given time period. The status is sampled at a rate consistent with the time period. For example, for a 24 hour period, a status is collected every hour. Refer to Granularity of Data Shown Based on Time Period.
IfnameInterface name on or hostname for host device where session resides.
Peer AddressIP address of the peer device.
Peer IDIP address of router with access to the peer device.

The large OSPF Session card contains two tabs.

The Session Summary tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates data is for a single session of a Network Service or Protocol.
TitleSession Summary (Network Services | OSPF Session).
Summary bar

Hostnames of the two devices in a session. Arrow points in the direction of the session.

Current state of OSPF. Full or 2-way, Attempt, Down, Exchange, Exstart, Init, and Loading.

Session State Changes ChartHeat map of the state of the given session over the given time period. The status is sampled at a rate consistent with the time period. For example, for a 24 hour period, a status is collected every hour. Refer to Granularity of Data Shown Based on Time Period.
Alarm Count ChartDistribution and count of OSPF alarm events over the given time period.
Info Count ChartDistribution and count of OSPF info events over the given time period.
IfnameName of the interface on the host device where the session resides.
StateCurrent state of OSPF.
Full or 2-way, Attempt, Down, Exchange, Exstart, Init, and Loading.
Is UnnumberedIndicates if the session is part of an unnumbered OSPF configuration (true) or part of a numbered OSPF configuration (false).
Nbr CountNumber of routers in the OSPF configuration.
Is PassiveIndicates if the host is in a passive state (true) or active state (false).
Peer IDIP address of router with access to the peer device.
Is IPv6Indicates if the IP address of the host device is IPv6 (true) or IPv4 (false).
If UpIndicates if the interface on the host is up (true) or down (false).
Nbr Adj CountNumber of adjacent routers for this host.
MTUMaximum transmission unit (MTU) on shortest path between the host and peer.
Peer AddressIP address of the peer device.
AreaRouting domain of the host device.
Network TypeArchitectural design of the network. Values include Point-to-Point and Broadcast.
CostShortest path through the network between the host and peer devices.
Dead TimeCountdown timer, starting at 40 seconds, that is constantly reset as messages are heard from the neighbor. If the dead time gets to zero, the neighbor is presumed dead, the adjacency is torn down, and the link removed from SPF calculations in the OSPF database.

The Configuration File Evolution tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates configuration file information for a single session of a Network Service or Protocol.
Title(Network Services | OSPF Session) Configuration File Evolution.
Device identifiers (hostname, IP address, or MAC address) for host and peer in session. Arrow points from the host to the peer. Click to open associated device card.
, Current state of OSPF.
Full or 2-way, Attempt, Down, Exchange, Exstart, Init, and Loading.
TimestampsWhen changes to the configuration file have occurred, the date and time are indicated. Click the time to see the changed file.
Configuration File

When File is selected, the configuration file as it was at the selected time is shown.

When Diff is selected, the configuration file at the selected time is shown on the left and the configuration file at the previous timestamp is shown on the right. Differences are highlighted.

The full screen OSPF Session card provides tabs for all OSPF sessions and all events.

ItemDescription
TitleNetwork Services | OSPF.
Closes full screen card and returns to workbench.
Time periodRange of time in which the displayed data was collected; applies to all card sizes; select an alternate time period by clicking .
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
All OSPF Sessions tabDisplays all OSPF sessions running on the host device. The session list is sorted by hostname by default. This tab provides the following additional data about each session:
  • Area: Routing domain for this host device. Example values include 0.0.0.1, 0.0.0.23.
  • Ifname: Name of the interface on host device where session resides. Example values include swp5, peerlink-1.
  • Is IPv6: Indicates whether the address of the host device is IPv6 (true) or IPv4 (false).
  • Peer
    • Address: IPv4 or IPv6 address of the peer device.
    • Hostname: User-defined name for peer device.
    • ID: Network subnet address of router with access to the peer device.
  • State: Current state of OSPF. Values include Full, 2-way, Attempt, Down, Exchange, Exstart, Init, and Loading.
  • Timestamp: Date and time session was started, deleted, updated or marked dead (device is down).
All Events tabDisplays all events network-wide. By default, the event list is sorted by time, with the most recent events listed first. The tab provides the following additional data about each event:
  • Message: Text description of a OSPF-related event. Example: OSPF session with peer tor-1 swp7 vrf default state changed from failed to Established.
  • Source: Hostname of network device that generated the event.
  • Severity: Importance of the event. Values include critical, warning, info, and debug.
  • Type: Network protocol or service generating the event. This always has a value of OSPF in this card workflow.
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

Validation Cards

Validation Request Card

The small Validation Request card displays:

ItemDescription
Indicates a validation request.
Validation

Select a scheduled request to run that request on-demand. A default validation is provided for each supported network protocol and service, which runs a network-wide validation check. These validations run every 60 minutes, but you may run them on-demand at any time.

Note: No new requests can be configured from this size card.

GOStart the validation request. The corresponding On-demand Validation Result cards are opened on your workbench, one per protocol and service.

The medium Validation Request card displays:

ItemDescription
Indicates a validation request.
TitleValidation Request.
Validation

Select a scheduled request to run that request on-demand. A default validation is provided for each supported network protocol and service, which runs a network-wide validation check. These validations run every 60 minutes, but you may run them on-demand at any time.

Note: No new requests can be configured from this size card.

ProtocolsThe protocols included in a selected validation request are listed here.

The large Validation Request card displays:

ItemDescription
Indicates a validation request.
TitleValidation Request.
ValidationDepending on user intent, this field is used to:
  • Select a scheduled request to run that request on-demand. A default validation is provided for each supported network protocol and service, which runs a network-wide validation check. These validations run every 60 minutes, but you may run them on-demand at any time.
  • Leave as is to create a new scheduled validation request.
  • Select a scheduled request to modify.
ProtocolsFor a selected scheduled validation, the protocols included in a validation request are listed here. For new on-demand or scheduled validations, click these to include them in the validation.
ScheduleFor a selected scheduled validation, the schedule and the time of the last run are displayed. For new scheduled validations, select the frequency and starting date and time.
  • Run Every: Select how often to run the request. Choose from 30 minutes, 1, 3, 6, or 12 hours, or 1 day.
  • Starting: Select the date and time to start the first request in the series.
  • Last Run: Timestamp of when the selected validation was started.
Scheduled ValidationsCount of scheduled validations that are currently scheduled compared to the maximum of 15 allowed.
Run NowStart the validation request.
UpdateWhen changes are made to a selected validation request, Update becomes available so that you can save your changes.

Be aware, that if you update a previously saved validation request, the historical data collected will no longer match the data results of future runs of the request. If your intention is to leave this request unchanged and create a new request, click Save As New instead.

Save As NewWhen changes are made to a previously saved validation request, Save As New becomes available so that you can save the modified request as a new request.

The full screen Validation Request card displays all scheduled validation requests.

ItemDescription
TitleValidation Request.
Closes full screen card and returns to workbench.
Default TimeNo time period is displayed for this card as each validation request has its own time relationship.
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
Validation RequestsDisplays all scheduled validation requests. By default, the requests list is sorted by the date and time that it was originally created (Created At). This tab provides the following additional data about each request:
  • Name: Text identifier of the validation.
  • Type: Name of network protocols and/or services included in the validation.
  • Start Time: Data and time that the validation request was run.
  • Last Modified: Date and time of the most recent change made to the validation request.
  • Cadence (Min): How often, in minutes, the validation is scheduled to run. This is empty for new on-demand requests.
  • Is Active: Indicates whether the request is currently running according to its schedule (true) or it is not running (false).
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

On-Demand Validation Result Card

The small Validation Result card displays:

ItemDescription
Indicates an on-demand validation result.
TitleOn-demand Result <Network Protocol or Service Name> Validation.
TimestampDate and time the validation was completed.
, Status of the validation job, where:
  • Good: Job ran successfully. One or more warnings may have occurred during the run.
  • Failed: Job encountered errors which prevented the job from completing, or job ran successfully, but errors occurred during the run.

The medium Validation Result card displays:

ItemDescription
Indicates an on-demand validation result.
TitleOn-demand Validation Result | <Network Protocol or Service Name>.
TimestampDate and time the validation was completed.
, , Status of the validation job, where:
  • Good: Job ran successfully.
  • Warning: Job encountered issues, but it did complete its run.
  • Failed: Job encountered errors which prevented the job from completing.
Devices TestedChart with the total number of devices included in the validation and the distribution of the results.
  • Pass: Number of devices tested that had successful results.
  • Warn: Number of devices tested that had successful results, but also had at least one warning event.
  • Fail: Number of devices tested that had one or more protocol or service failures.

Hover over chart to view the number of devices and the percentage of all tested devices for each result category.

Sessions Tested

For BGP, chart with total number of BGP sessions included in the validation and the distribution of the overall results.

For EVPN, chart with total number of BGP sessions included in the validation and the distribution of the overall results.

For Interfaces, chart with total number of ports included in the validation and the distribution of the overall results.

In each of these charts:

  • Pass: Number of sessions or ports tested that had successful results.
  • Warn: Number of sessions or ports tested that had successful results, but also had at least one warning event.
  • Fail: Number of sessions or ports tested that had one or more failure events.

Hover over chart to view the number of devices, sessions, or ports and the percentage of all tested devices, sessions, or ports for each result category.

This chart does not apply to other Network Protocols and Services, and thus is not displayed for those cards.

Open <Service> CardClick to open the corresponding medium Network Services card, where available.

The large Validation Result card contains two tabs.

The Summary tab displays:

ItemDescription
Indicates an on-demand validation result.
TitleOn-demand Validation Result | Summary | <Network Protocol or Service Name>.
DateDay and time when the validation completed.
, , Status of the validation job, where:
  • Good: Job ran successfully.
  • Warning: Job encountered issues, but it did complete its run.
  • Failed: Job encountered errors which prevented the job from completing.
Devices TestedChart with the total number of devices included in the validation and the distribution of the results.
  • Pass: Number of devices tested that had successful results.
  • Warn: Number of devices tested that had successful results, but also had at least one warning event.
  • Fail: Number of devices tested that had one or more protocol or service failures.

Hover over chart to view the number of devices and the percentage of all tested devices for each result category.

Sessions Tested

For BGP, chart with total number of BGP sessions included in the validation and the distribution of the overall results.

For EVPN, chart with total number of BGP sessions included in the validation and the distribution of the overall results.

For Interfaces, chart with total number of ports included in the validation and the distribution of the overall results.

For OSPF, chart with total number of OSPF sessions included in the validation and the distribution of the overall results.

In each of these charts:

  • Pass: Number of sessions or ports tested that had successful results.
  • Warn: Number of sessions or ports tested that had successful results, but also had at least one warning event.
  • Fail: Number of sessions or ports tested that had one or more failure events.

Hover over chart to view the number of devices, sessions, or ports and the percentage of all tested devices, sessions, or ports for each result category.

This chart does not apply to other Network Protocols and Services, and thus is not displayed for those cards.

Open <Service> CardClick to open the corresponding medium Network Services card, when available.
Table/Filter options

When the Most Active filter option is selected, the table displays switches and hosts running the given service or protocol in decreasing order of alarm counts. Devices with the largest number of warnings and failures are listed first. You can click on the device name to open its switch card on your workbench.

When the Most Recent filter option is selected, the table displays switches and hosts running the given service or protocol sorted by timestamp, with the device with the most recent warning or failure listed first. The table provides the following additional information:

  • Hostname: User-defined name for switch or host.
  • Message Type: Network protocol or service which triggered the event.
  • Message: Short description of the event.
  • Severity: Indication of importance of event; values in decreasing severity include critical, warning, error, info, debug.
Show All ResultsClick to open the full screen card with all on-demand validation results sorted by timestamp.

The Configuration tab displays:

ItemDescription
Indicates an on-demand validation request configuration.
TitleOn-demand Validation Result | Configuration | <Network Protocol or Service Name>.
ValidationsList of network protocols or services included in the request that produced these results.
ScheduleNot relevant to on-demand validation results. Value is always N/A.

The full screen Validation Result card provides a tab for all on-demand validation results.

ItemDescription
TitleValidation Results | On-demand.
Closes full screen card and returns to workbench.
Time periodRange of time in which the displayed data was collected; applies to all card sizes; select an alternate time period by clicking
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
On-demand Validation Result | <network protocol or service>Displays all unscheduled validation results. By default, the results list is sorted by Timestamp. This tab provides the following additional data about each result:
  • Job ID: Internal identifier of the validation job that produced the given results
  • Timestamp: Date and time the validation completed
  • Type: Network protocol or service type
  • Total Node Count: Total number of nodes running the given network protocol or service
  • Checked Node Count: Number of nodes on which the validation ran
  • Failed Node Count: Number of checked nodes that had protocol or service failures
  • Rotten Node Count: Number of nodes that could not be reached during the validation
  • Unknown Node Count: Applies only to the Interfaces service. Number of nodes with unknown port states.
  • Failed Adjacent Count: Number of adjacent nodes that had protocol or service failures
  • Total Session Count: Total number of sessions running for the given network protocol or service
  • Failed Session Count: Number of sessions that had session failures
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

Scheduled Validation Result Card

The small Scheduled Validation Result card displays:

ItemDescription
Indicates a scheduled validation result.
TitleScheduled Result <Network Protocol or Service Name> Validation.
ResultsSummary of validation results:
  • Number of validation runs completed in the designated time period.
  • Number of runs with warnings.
  • Number of runs with errors.
, Status of the validation job, where:
  • Pass: Job ran successfully. One or more warnings may have occurred during the run.
  • Failed: Job encountered errors which prevented the job from completing, or job ran successfully, but errors occurred during the run.

The medium Scheduled Validation Result card displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates a scheduled validation result.
TitleScheduled Validation Result | <Network Protocol or Service Name>.
SummarySummary of validation results:
  • Name of scheduled validation.
  • Status of the validation job, where:
    • Pass: Job ran successfully. One or more warnings may have occurred during the run.
    • Failed: Job encountered errors which prevented the job from completing, or job ran successfully, but errors occurred during the run.
ChartValidation results, where:
  • Time period: Range of time in which the data on the heat map was collected.
  • Heat map: A time segmented view of the results. For each time segment, the color represents the percentage of warning, passing, and failed results. Refer to NetQ UI Card Reference for details on how to interpret the results.
Open <Service> CardClick to open the corresponding medium Network Services card, when available.

The large Scheduled Validation Result card contains two tabs.

The Summary tab displays:

ItemDescription
Indicates a scheduled validation result.
TitleValidation Summary (Scheduled Validation Result | <Network Protocol or Service Name>).
SummarySummary of validation results:
  • Name of scheduled validation.
  • Status of the validation job, where:
    • Pass: Job ran successfully. One or more warnings may have occurred during the run.
    • Failed: Job encountered errors which prevented the job from completing, or job ran successfully, but errors occurred during the run.
  • Expand/Collapse: Expand the heat map to full width of card, collapse the heat map to the left.
ChartValidation results, where:
  • Time period: Range of time in which the data on the heat map was collected.
  • Heat map: A time segmented view of the results. For each time segment, the color represents the percentage of warning, passing, and failed results. Refer to NetQ UI Card Reference for details on how to interpret the results.
Open <Service> CardClick to open the corresponding medium Network Services card, when available.
Table/Filter options

When the Most Active filter option is selected, the table displays switches and hosts running the given service or protocol in decreasing order of alarm counts-devices with the largest number of warnings and failures are listed first.

When the Most Recent filter option is selected, the table displays switches and hosts running the given service or protocol sorted by timestamp, with the device with the most recent warning or failure listed first. The table provides the following additional information:

  • Hostname: User-defined name for switch or host.
  • Message Type: Network protocol or service which triggered the event.
  • Message: Short description of the event.
  • Severity: Indication of importance of event; values in decreasing severity include critical, warning, error, info, debug.
Show All ResultsClick to open the full screen card with all scheduled validation results sorted by timestamp.

The Configuration tab displays:

ItemDescription
Indicates a scheduled validation configuration
TitleConfiguration (Scheduled Validation Result | <Network Protocol or Service Name>)
NameUser-defined name for this scheduled validation
ValidationsList of validations included in the validation request that created this result
ScheduleUser-defined schedule for the validation request that created this result
Open Schedule CardOpens the large Validation Request card for editing this configuration

The full screen Scheduled Validation Result card provides tabs for all scheduled validation results for the service.

ItemDescription
TitleScheduled Validation Results | <Network Protocol or Service>.
Closes full screen card and returns to workbench.
Time periodRange of time in which the displayed data was collected; applies to all card sizes; select an alternate time period by clicking .
Displays data refresh status. Click to pause data refresh. Click to resume data refresh. Current refresh rate is visible by hovering over icon.
ResultsNumber of results found for the selected tab.
Scheduled Validation Result | <network protocol or service>Displays all unscheduled validation results. By default, the results list is sorted by timestamp. This tab provides the following additional data about each result:
  • Job ID: Internal identifier of the validation job that produced the given results
  • Timestamp: Date and time the validation completed
  • Type: Protocol of Service Name
  • Total Node Count: Total number of nodes running the given network protocol or service
  • Checked Node Count: Number of nodes on which the validation ran
  • Failed Node Count: Number of checked nodes that had protocol or service failures
  • Rotten Node Count: Number of nodes that could not be reached during the validation
  • Unknown Node Count: Applies only to the Interfaces service. Number of nodes with unknown port states.
  • Failed Adjacent Count: Number of adjacent nodes that had protocol or service failures
  • Total Session Count: Total number of sessions running for the given network protocol or service
  • Failed Session Count: Number of sessions that had session failures
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

Trace Cards

Trace Request Card

The small Trace Request card displays:

ItemDescription
Indicates a trace request
Select Trace listSelect a scheduled trace request from the list
GoClick to start the trace now

The medium Trace Request card displays:

ItemDescription
Indicates a trace request.
TitleNew Trace Request.
New Trace RequestCreate a new layer 3 trace request. Use the large Trace Request card to create a new layer 2 or 3 request.
Source(Required) Hostname or IP address of device where to begin the trace.
Destination(Required) IP address of device where to end the trace.
Run NowStart the trace now.

The large Trace Request card displays:

ItemDescription
Indicates a trace request.
TitleNew Trace Request.
Trace selectionLeave New Trace Request selected to create a new request, or choose a scheduled request from the list.
Source(Required) Hostname or IP address of device where to begin the trace.
Destination(Required) Ending point for the trace. For layer 2 traces, value must be a MAC address. For layer 3 traces, value must be an IP address.
VRFOptional for layer 3 traces. Virtual Route Forwarding interface to be used as part of the trace path.
VLAN IDRequired for layer 2 traces. Virtual LAN to be used as part of the trace path.
ScheduleSets the frequency with which to run a new trace (Run every) and when to start the trace for the first time (Starting).
Run NowStart the trace now.
UpdateUpdate is available when a scheduled trace request is selected from the dropdown list and you make a change to its configuration. Clicking Update saves the changes to the existing scheduled trace.
Save As NewSave As New is available in two instances:
  • When you enter a source, destination, and schedule for a new trace. Clicking Save As New in this instance saves the new scheduled trace.
  • When changes are made to a selected scheduled trace request. Clicking Save As New in this instance saves the modified scheduled trace without changing the original trace on which it was based.

The full screen Trace Request card displays:

ItemDescription
TitleTrace Request.
Closes full screen card and returns to workbench.
Time periodRange of time in which the displayed data was collected; applies to all card sizes; select an alternate time period by clicking .
ResultsNumber of results found for the selected tab.
Schedule Preview tabDisplays all scheduled trace requests for the given user. By default, the listing is sorted by Start Time, with the most recently started traces listed at the top. The tab provides the following additional data about each event:
  • Action: Indicates latest action taken on the trace job. Values include Add, Deleted, Update.
  • Frequency: How often the trace is scheduled to run
  • Active: Indicates if trace is actively running (true), or stopped from running (false)
  • ID: Internal system identifier for the trace job
  • Trace Name: User-defined name for a trace
  • Trace Params: Indicates source and destination, optional VLAN or VRF specified, and whether to alert on failure
Table ActionsSelect, export, or filter the list. Refer to Table Settings.

On-demand Trace Results Card

The small On-demand Trace Results card displays:

ItemDescription
Indicates an on-demand trace result.
Source and destination of the trace, identified by their address or hostname. Source is listed on top with arrow pointing to destination.
, Indicates success or failure of the trace request. A successful result implies all paths were successful without any warnings or failures. A failure result implies there was at least one path with warnings or errors.

The medium On-demand Trace Results card displays:

ItemDescription
Indicates an on-demand trace result.
TitleOn-demand Trace Result.
Source and destination of the trace, identified by their address or hostname. Source is listed on top with arrow pointing to destination.
, Indicates success or failure of the trace request. A successful result implies all paths were successful without any warnings or failures. A failure result implies there was at least one path with warnings or errors.
Total Paths FoundNumber of paths found between the two devices.
MTU OverallAverage size of the maximum transmission unit for all paths.
Minimum HopsSmallest number of hops along a path between the devices.
Maximum HopsLargest number of hops along a path between the devices.

The large On-demand Trace Results card contains two tabs.

The On-demand Trace Result tab displays:

ItemDescription
Indicates an on-demand trace result.
TitleOn-demand Trace Result.
, Indicates success or failure of the trace request. A successful result implies all paths were successful without any warnings or failures. A failure result implies there was at least one path with warnings or errors.
Source and destination of the trace, identified by their address or hostname. Source is listed on top with arrow pointing to destination.
Distribution by Hops chartDisplays the distributions of various hop counts for the available paths.
Distribution by MTU chartDisplays the distribution of MTUs used on the interfaces used in the available paths.
TableProvides detailed path information, sorted by the route identifier, including:
  • Route ID: Identifier of each path
  • MTU: Average speed of the interfaces used
  • Hops: Number of hops to get from the source to the destination device
  • Warnings: Number of warnings encountered during the trace on a given path
  • Errors: Number of errors encountered during the trace on a given path
Total Paths FoundNumber of paths found between the two devices.
MTU OverallAverage size of the maximum transmission unit for all paths.
Minimum HopsSmallest number of hops along a path between the devices.

The On-demand Trace Settings tab displays:

ItemDescription
Indicates an on-demand trace setting
TitleOn-demand Trace Settings
SourceStarting point for the trace
DestinationEnding point for the trace
ScheduleDoes not apply to on-demand traces
VRFAssociated virtual route forwarding interface, when used with layer 3 traces
VLANAssociated virtual local area network, when used with layer 2 traces
Job IDIdentifier of the job; used internally
Re-run TraceClicking this button runs the trace again

The full screen On-demand Trace Results card displays:

ItemDescription
TitleOn-demand Trace Results
Closes full screen card and returns to workbench
Time periodRange of time in which the displayed data was collected; applies to all card sizes; select an alternate time period by clicking
ResultsNumber of results found for the selected tab
Trace Results tabProvides detailed path information, sorted by the Resolution Time (date and time results completed), including:
  • SCR.IP: Source IP address
  • DST.IP: Destination IP address
  • Max Hop Count: Largest number of hops along a path between the devices
  • Min Hop Count: Smallest number of hops along a path between the devices
  • Total Paths: Number of paths found between the two devices
  • PMTU: Average size of the maximum transmission unit for all interfaces along the paths
  • Errors: Message provided for analysis when a trace fails
Table ActionsSelect, export, or filter the list. Refer to Table Settings

Scheduled Trace Results Card

The small Scheduled Trace Results card displays:

ItemDescription
Indicates a scheduled trace result.
Source and destination of the trace, identified by their address or hostname. Source is listed on left with arrow pointing to destination.
ResultsSummary of trace results: a successful result implies all paths were successful without any warnings or failures; a failure result implies there was at least one path with warnings or errors.
  • Number of trace runs completed in the designated time period
  • Number of runs with warnings
  • Number of runs with errors

The medium Scheduled Trace Results card displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates a scheduled trace result.
TitleScheduled Trace Result.
SummaryName of scheduled validation and summary of trace results: a successful result implies all paths were successful without any warnings or failures; a failure result implies there was at least one path with warnings or errors.
  • Number of trace runs completed in the designated time period
  • Number of runs with warnings
  • Number of runs with errors
Charts

Heat map: A time segmented view of the results. For each time segment, the color represents the percentage of warning and failed results. Refer to Granularity of Data Shown Based on Time Period for details on how to interpret the results.

Unique Bad Nodes: Distribution of unique nodes that generated the indicated warnings and/or failures.

The large Scheduled Trace Results card contains two tabs:

The Results tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates a scheduled trace result.
TitleScheduled Trace Result.
SummaryName of scheduled validation and summary of trace results: a successful result implies all paths were successful without any warnings or failures; a failure result implies there was at least one path with warnings or errors.
  • Number of trace runs completed in the designated time period
  • Number of runs with warnings
  • Number of runs with errors
Charts

Heat map: A time segmented view of the results. For each time segment, the color represents the percentage of warning and failed results. Refer to Granularity of Data Shown Based on Time Period for details on how to interpret the results.

Small charts: Display counts for each item during the same time period, for the purpose of correlating with the warnings and errors shown in the heat map.

Table/Filter options

When the Failures filter option is selected, the table displays the failure messages received for each run.

When the Paths filter option is selected, the table displays all of the paths tried during each run.

When the Warning filter option is selected, the table displays the warning messages received for each run.

The Configuration tab displays:

ItemDescription
Time periodRange of time in which the displayed data was collected; applies to all card sizes.
Indicates a scheduled trace configuration.
TitleScheduled Trace Configuration (Scheduled Trace Result).
SourceAddress or hostname of the device where the trace was started.
DestinationAddress of the device where the trace was stopped.
ScheduleThe frequency and starting date and time to run the trace.
VRFVirtual Route Forwarding interface, when defined.
VLANVirtual LAN identifier, when defined.
NameUser-defined name of the scheduled trace.
Run NowStart the trace now.
EditModify the trace. Opens Trace Request card with this information pre-populated.

The full screen Scheduled Trace Results card displays:

ItemDescription
TitleScheduled Trace Results
Closes full screen card and returns to workbench.
Time periodRange of time in which the displayed data was collected; applies to all card sizes; select an alternate time period by clicking .
ResultsNumber of results found for the selected tab.
Scheduled Trace Results tabDisplays the basic information about the trace, including:
  • Resolution Time: Time that trace was run
  • SRC.IP: IP address of the source device
  • DST.IP: Address of the destination device
  • Max Hop Count: Maximum number of hops across all paths between the devices
  • Min Hop Count: Minimum number of hops across all paths between the devices
  • Total Paths: Number of available paths found between the devices
  • PMTU: Average of the maximum transmission units for all paths
  • Errors: Message provided for analysis if trace fails

Click on a result to open a detailed view of the results.

Table ActionsSelect, export, or filter the list. Refer to Table Settings.