Monitoring Virtual Device Counters
Cumulus Linux gathers statistics for VXLANs and VLANs using virtual device counters. These counters are supported on Tomahawk, Trident II+ and Trident II-based platforms only; see the HCL for a list of supported platforms.
You can retrieve the data from these counters using tools like
ip -s link show,
Sample VXLAN Statistics
VXLAN statistics are available as follows:
Aggregate statistics are available per VNI; this includes access and network statistics.
Network statistics are available for each VNI and displayed against the VXLAN device. This is independent of the VTEP used, so this is a summary of the VNI statistics across all tunnels.
Access statistics are available per VLAN subinterface.
First, get interface information regarding the VXLAN bridge:
cumulus@switch:~$ brctl show br-vxln16757104 bridge name bridge id STP enabled interfaces -vxln16757104 8000.443839006988 no swp2s0.6 swp2s1.6 swp2s2.6 swp2s3.6 vxln16757104
To get VNI statistics, run:
cumulus@switch:~$ ip -s link show br-vxln16757104 62: br-vxln16757104: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT link/ether 44:38:39:00:69:88 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 10848 158 0 0 0 0 TX: bytes packets errors dropped carrier collsns 27816 541 0 0 0 0
To get access statistics, run:
cumulus@switch:~$ ip -s link show swp2s0.6 63: swp2s0.6@swp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-vxln16757104 state UP mode DEFAULT link/ether 44:38:39:00:69:88 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 2680 39 0 0 0 0 TX: bytes packets errors dropped carrier collsns 7558 140 0 0 0 0
To get network statistics, run:
cumulus@switch:~$ ip -s link show vxln16757104 61: vxln16757104: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-vxln16757104 state UNKNOWN mode DEFAULT link/ether e2:37:47:db:f1:94 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 0 0 0 0 0 0 TX: bytes packets errors dropped carrier collsns 0 0 0 9 0 0
Sample VLAN Statistics
For VLANs Using the VLAN-aware Bridge Mode Driver
For a bridge using the VLAN-aware bridge mode
driver, the bridge is a just a container and each VLAN (VID/PVID) in the
bridge is an independent L2 broadcast domain. As there is no netdev
available to display these VLAN statistics, the
switchd nodes are used
cumulus@switch:~$ ifquery bridge auto bridge iface bridge inet static bridge-vlan-aware yes bridge-ports swp2s0 swp2s1 bridge-stp on bridge-vids 2000-2002 4094 cumulus@switch:~$ ls /cumulus/switchd/run/stats/vlan/ 2 2000 2001 2002 all cumulus@switch:~$ cat /cumulus/switchd/run/stats/vlan/2000/aggregate Vlan id : 2000 L3 Routed In Octets : - L3 Routed In Packets : - L3 Routed Out Octets : - L3 Routed Out Packets : - Total In Octets : 375 Total In Packets : 3 Total Out Octets : 387 Total Out Packets : 3
For VLANs Using the Traditional Bridge Mode Driver
For a bridge using the traditional bridge mode driver, each bridge is a single L2 broadcast domain and is associated with an internal VLAN. This internal VLAN’s counters are displayed as bridge netdev stats.
cumulus@switch:~$ brctl show br0 bridge name bridge id STP enabled interfaces br0 8000.443839006989 yes bond0.100 swp2s2.100 cumulus@switch:~$ ip -s link show br0 42: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT link/ether 44:38:39:00:69:89 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 23201498 227514 0 0 0 0 TX: bytes packets errors dropped carrier collsns 18198262 178443 0 0 0 0
Configure the Counters in switchd
These counters are enabled by default. To configure them, use
and configure them as you would any other `switchd` parameter. The
switchd parameters are as follows:
stats.vlan.aggregate, which controls the statistics available for each VLAN. Its value defaults to BRIEF.
stats.vxlan.aggregate, which controls the statistics available for each VNI (access and network). Its value defaults to DETAIL.
stats.vxlan.member, which controls the statistics available for each local/access port in a VXLAN bridge. Its value defaults to BRIEF.
The values for each parameter can be one of the following:
- NONE: This disables the counter.
- BRIEF: This provides tx/rx packet/byte counters for the associated parameter.
- DETAIL: This provides additional feature-specific counters. In the
stats.vxlan.aggregate, DETAIL provides access vs. network statistics. For the other types, DETAIL has the same effect as BRIEF.
If you change one of these settings on the fly, the new configuration applies only to those VNIs or VLANs set up after the configuration changed; previously allocated counters remain as is.
Configure the Poll Interval
The virtual device counters are polled periodically. This can be CPU
intensive, so the interval is configurable in
switchd, with a default
of 2 seconds.
# Virtual devices hw-stat poll interval (in seconds) #stats.vdev_hw_poll_interval = 2
Configure Internal VLAN Statistics
For debugging purposes, you may need to access packet statistics
associated with internal VLAN IDs. These statistics are hidden by
default, but can be configured in
#stats.vlan.show_internal_vlans = FALSE
ethtool is not supported for virtual devices, you cannot clear
the statistics cache maintained by the kernel. You can clear the
hardware statistics via
cumulus@switch:~$ sudo echo 1 > /cumulus/switchd/clear/stats/vlan cumulus@switch:~$ sudo echo 1 > /cumulus/switchd/clear/stats/vxlan cumulus@switch:~$
Caveats and Errata
Currently the CPU port is internally added as a member of all VLANs. Because of this, packets sent to the CPU are counted against the corresponding VLAN’s tx packets/bytes. There is no workaround.
When checking the virtual counters for the bridge, the TX count is the number of packets destined to the CPU before any hardware policers take effect. For example, if 500 broadcast packets are sent into the bridge, the CPU is also sent 500 packets. These 500 packets are policed by the default ACLs in Cumulus Linux, so the CPU might receive fewer than the 500 packets if the incoming packet rate is too high. The TX counter for the bridge should be equal to 500*(number of ports in the bridge - incoming port + CPU port) or just 500 * number of ports in the bridge.
You cannot use
ethtool -Sfor virtual devices. This is because the counters available via
netdevare sufficient to display the vlan/vxlan counters currently supported in the hardware (only rx/tx packets/bytes are supported currently).