Merge branch 'fixes' into generate-offlinedocs

cumulusAnia · cumulusAnia · commit d83ae76c44f4 · 2026-02-24T14:19:14.000-08:00
diff --git a/content/cumulus-linux-511/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md b/content/cumulus-linux-511/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md
@@ -142,15 +142,15 @@ cumulus@switch:~$ nv config apply
 ```
 
 {{< /tab >}}
-{{< tab "Environment sensors">}}
+{{< tab "Environment sensor">}}
 
 ```
-cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensors state enabled
+cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensor state enabled
 cumulus@switch:~$ nv config apply
 ```
 
 ```
-cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensors sample-interval 100
+cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensor sample-interval 100
 cumulus@switch:~$ nv config apply
 ```
 
@@ -697,7 +697,7 @@ CPU statistics include the CPU core number and operation mode (user, system, idl
 | `node_memory_Zswapped_bytes` | `/proc/meminfo` Zswapped bytes. |
 
 {{< /tab >}}
-{{< tab "Environment Sensors ">}}
+{{< tab "Environment Sensor ">}}
 
 | Name | Description |
 |----- | ----------- |
diff --git a/content/cumulus-linux-512/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md b/content/cumulus-linux-512/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md
@@ -180,15 +180,15 @@ cumulus@switch:~$ nv config apply
 ```
 
 {{< /tab >}}
-{{< tab "Environment sensors">}}
+{{< tab "Environment sensor">}}
 
 ```
-cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensors state enabled
+cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensor state enabled
 cumulus@switch:~$ nv config apply
 ```
 
 ```
-cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensors sample-interval 100
+cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensor sample-interval 100
 cumulus@switch:~$ nv config apply
 ```
 
@@ -921,7 +921,7 @@ CPU statistics include the CPU core number and operation mode (user, system, idl
 | `node_memory_Zswapped_bytes` | `/proc/meminfo` Zswapped bytes. |
 
 {{< /tab >}}
-{{< tab "Environment Sensors ">}}
+{{< tab "Environment Sensor ">}}
 
 | Name | Description |
 |----- | ----------- |
diff --git a/content/cumulus-linux-513/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md b/content/cumulus-linux-513/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md
@@ -256,19 +256,19 @@ cumulus@switch:~$ nv config apply
 ```
 
 {{< /tab >}}
-{{< tab "Environment sensors">}}
+{{< tab "Environment sensor">}}
 
 To enable environment sensor statistics:
 
 ```
-cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensors state enabled
+cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensor state enabled
 cumulus@switch:~$ nv config apply
 ```
 
 To adjust the sample interval for environment sensor statistics:
 
 ```
-cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensors sample-interval 100
+cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensor sample-interval 100
 cumulus@switch:~$ nv config apply
 ```
 
@@ -2392,7 +2392,7 @@ CPU statistics include the CPU core number and operation mode (user, system, idl
 | `node_memory_Zswapped_bytes` | `/proc/meminfo` Zswapped bytes. |
 
 {{< /tab >}}
-{{< tab "Environment Sensors ">}}
+{{< tab "Environment Sensor ">}}
 
 | Name | Description |
 |----- | ----------- |
diff --git a/content/cumulus-linux-514/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md b/content/cumulus-linux-514/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md
@@ -258,19 +258,19 @@ cumulus@switch:~$ nv config apply
 ```
 
 {{< /tab >}}
-{{< tab "Environment sensors">}}
+{{< tab "Environment sensor">}}
 
 To enable environment sensor statistics:
 
 ```
-cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensors state enabled
+cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensor state enabled
 cumulus@switch:~$ nv config apply
 ```
 
 To adjust the sample interval for environment sensor statistics:
 
 ```
-cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensors sample-interval 100
+cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensor sample-interval 100
 cumulus@switch:~$ nv config apply
 ```
 
@@ -2793,7 +2793,7 @@ CPU statistics include the CPU core number and operation mode (user, system, idl
 | `node_memory_Zswapped_bytes` | `/proc/meminfo` Zswapped bytes. |
 
 {{< /tab >}}
-{{< tab "Environment Sensors ">}}
+{{< tab "Environment Sensor ">}}
 
 | Name | Description |
 |----- | ----------- |
diff --git a/content/cumulus-linux-514/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-API.md b/content/cumulus-linux-514/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-API.md
@@ -1853,6 +1853,10 @@ cumulus@switch:~$ curl -u 'cumulus:CumulusLinux!' --insecure -X GET https://127.
 }
 ```
 
+{{%notice note%}}
+The API `GET` operation output matches the operational revision view (equivalent to `nv show --rev=operational`) and omits unset fields that are shown in the default `nv show` output.
+{{%/notice%}}
+
 ### Use Filters in a Query
 
 You can use filters to show specific information in a query with the `curl -u '<username>:<password>' -k -X GET http://path?filter=<filter>` syntax. The following example is the equivalent REST API method for the NVUE `nv show interface --filter type=svi` command, which shows all SVIs configured on the switch:
diff --git a/content/cumulus-linux-514/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-CLI.md b/content/cumulus-linux-514/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-CLI.md
@@ -190,7 +190,7 @@ Additional options are available for certain `nv show` commands. For example, yo
 | `--filter` | Filters show command output on column data. For example, the `nv show interface --filter mtu=1500` shows only the interfaces with MTU set to 1500. For more information, see {{<link url="#filter-nv-show-command-output" text="Filter nv show Command Output">}} below.|
 | `--hostname`| Shows system configuration for the switch with the specified hostname. For example, `nv show --hostname leaf01`.|
 | `--operational` | Shows the running configuration (the actual system state). For example, `nv show interface swp1 --operational` shows the running configuration for swp1. The running and applied configuration should be the same. If different, inspect the logs. |
-| `--output` | Shows command output in table (`auto`), `json`, `yaml`, or `native` format. Use `native` format for {{<link url="FRRouting/#nvue-show-commands-and-vtysh-output" text="certain routing">}} `nv show` commands to see the output that vtysh provides. For example:<br>`nv show interface bond1 --output auto`<br>`nv show interface bond1 --output json`<br>`nv show interface bond1 --output yaml`<br>`nv show evpn multihoming esi --output native`<br>|
+| `--output` | Shows command output in table (`auto`), `json`, `yaml`, or `native` format. Use `native` format for {{<link url="FRRouting/#nvue-show-commands-and-vtysh-output" text="certain routing">}} `nv show` commands to see the output that vtysh provides. For example:<br>`nv show interface bond1 --output auto`<br>`nv show interface bond1 --output json`<br>`nv show interface bond1 --output yaml`<br>`nv show evpn multihoming esi --output native`<br>{{%notice note%}}The `--output json` option matches the output in `--rev=operational` and omits unset fields that are shown in the default `nv show` command output.{{%/notice%}}|
 | `--paginate`      | Paginates the output. For example, `nv show interface bond1 --paginate on`. |
 | `--pending`       | Shows the last applied configuration and any pending set or unset configuration that you have not yet applied. For example, `nv show interface bond1 --pending`.|
 | `--rev <revision>`| Shows a detached pending configuration. See the `nv config detach` configuration management command below. For example, `nv show --rev 1`. You can also show only applied or only operational information in the `nv show` output. For example, to show only the applied settings for swp1 configuration, run the `nv show interface swp1 --rev=applied` command. To show only the operational settings for swp1 configuration, run the `nv show interface swp1 --rev=operational` command. |
diff --git a/content/cumulus-linux-515/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md b/content/cumulus-linux-515/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md
@@ -280,19 +280,19 @@ cumulus@switch:~$ nv config apply
 ```
 
 {{< /tab >}}
-{{< tab "Environment sensors">}}
+{{< tab "Environment sensor">}}
 
 To enable environment sensor statistics:
 
 ```
-cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensors state enabled
+cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensor state enabled
 cumulus@switch:~$ nv config apply
 ```
 
 To adjust the sample interval for environment sensor statistics:
 
 ```
-cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensors sample-interval 100
+cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensor sample-interval 100
 cumulus@switch:~$ nv config apply
 ```
 
@@ -2785,7 +2785,7 @@ CPU statistics include the CPU core number and operation mode (user, system, idl
 | `node_memory_Zswapped_bytes` | `/proc/meminfo` Zswapped bytes. |
 
 {{< /tab >}}
-{{< tab "Environment Sensors ">}}
+{{< tab "Environment Sensor ">}}
 
 | Name | Description |
 |----- | ----------- |
diff --git a/content/cumulus-linux-515/System-Configuration/Authentication-Authorization-and-Accounting/TACACS.md b/content/cumulus-linux-515/System-Configuration/Authentication-Authorization-and-Accounting/TACACS.md
@@ -398,18 +398,13 @@ TACACS+ per-command authorization lets you configure the commands that TACACS+ u
 
 The following command allows TACACS+ users at privilege level 0 to run the `nv` and `ip` commands.
 
-{{%notice note%}}
-After configuring TACACS+ per-command authorization, you must restart the NVUE service.
-{{%/notice%}}
-
 {{< tabs "TabID392 ">}}
 {{< tab "NVUE Commands ">}}
 
 ```
 cumulus@switch:~$ nv set system aaa tacacs authorization 0 command ip 
 cumulus@switch:~$ nv set system aaa tacacs authorization 0 command nv
 cumulus@switch:~$ nv config apply
-cumulus@switch:~$ sudo systemctl restart nvued.service
 ```
 
 To show the per-command authorization settings, run the `nv show system aaa tacacs authorization` command:
@@ -431,7 +426,6 @@ When you configure per-command authorization on the switch, only define the init
 
 ```
 cumulus@switch:~$ sudo tacplus-restrict -i -u tacacs0 -a ip nv
-cumulus@switch:~$ sudo systemctl restart nvued.service
 ```
 
 The `tacplus-auth` command handles authorization for each command. To make this an enforced authorization, change the TACACS+ log in to use a restricted shell, with a very limited executable search path. Otherwise, the user can bypass the authorization. The `tacplus-restrict` utility simplifies setting up the restricted environment.
diff --git a/content/cumulus-linux-515/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-API.md b/content/cumulus-linux-515/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-API.md
@@ -1875,6 +1875,10 @@ cumulus@switch:~$ curl -u 'cumulus:CumulusLinux!' --insecure -X GET https://127.
 }
 ```
 
+{{%notice note%}}
+The API `GET` operation output matches the operational revision view (equivalent to `nv show --rev=operational`) and omits unset fields that are shown in the default `nv show` output.
+{{%/notice%}}
+
 ### Use Filters in a Query
 
 You can use filters to show specific information in a query with the `curl -u '<username>:<password>' -k -X GET http://path?filter=<filter>` syntax. The following example is the equivalent REST API method for the NVUE `nv show interface --filter type=svi` command, which shows all SVIs configured on the switch:
diff --git a/content/cumulus-linux-515/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-CLI.md b/content/cumulus-linux-515/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-CLI.md
@@ -192,7 +192,7 @@ Additional options are available for certain `nv show` commands. For example, yo
 | `--filter` | Filters show command output on column data. For example, the `nv show interface --filter mtu=1500` shows only the interfaces with MTU set to 1500. For more information, see {{<link url="#filter-nv-show-command-output" text="Filter nv show Command Output">}} below.|
 | `--hostname`| Shows system configuration for the switch with the specified hostname. For example, `nv show --hostname leaf01`.|
 | `--operational` | Shows the running configuration (the actual system state). For example, `nv show interface swp1 --operational` shows the running configuration for swp1. The running and applied configuration should be the same. If different, inspect the logs. |
-| `--output` | Shows command output in table (`auto`), `json`, `yaml`, or `native` format. Use `native` format for {{<link url="FRRouting/#nvue-show-commands-and-vtysh-output" text="certain routing">}} `nv show` commands to see the output that vtysh provides. For example:<br>`nv show interface bond1 --output auto`<br>`nv show interface bond1 --output json`<br>`nv show interface bond1 --output yaml`<br>`nv show evpn multihoming esi --output native`<br>|
+| `--output` | Shows command output in table (`auto`), `json`, `yaml`, or `native` format. Use `native` format for {{<link url="FRRouting/#nvue-show-commands-and-vtysh-output" text="certain routing">}} `nv show` commands to see the output that vtysh provides. For example:<br>`nv show interface bond1 --output auto`<br>`nv show interface bond1 --output json`<br>`nv show interface bond1 --output yaml`<br>`nv show evpn multihoming esi --output native`<br>{{%notice note%}}The `--output json` option matches the output in `--rev=operational` and omits unset fields that are shown in the default `nv show` command output.{{%/notice%}}|
 | `--paginate`      | Paginates the output. For example, `nv show interface bond1 --paginate on`. |
 | `--pending`       | Shows the last applied configuration and any pending set or unset configuration that you have not yet applied. For example, `nv show interface bond1 --pending`.|
 | `--rev <revision>`| Shows a detached pending configuration. See the `nv config detach` configuration management command below. For example, `nv show --rev 1`. You can also show only applied or only operational information in the `nv show` output. For example, to show only the applied settings for swp1 configuration, run the `nv show interface swp1 --rev=applied` command. To show only the operational settings for swp1 configuration, run the `nv show interface swp1 --rev=operational` command. |
diff --git a/content/cumulus-linux-516/Layer-1-and-Switch-Ports/802.1X-Interfaces.md b/content/cumulus-linux-516/Layer-1-and-Switch-Ports/802.1X-Interfaces.md
@@ -446,7 +446,8 @@ Dynamic VRF assignment on 802.1X enables layer 3 ports to be authenticated and a
 You can use dynamic VRF assignment to place users or devices dynamically into different VRFs based on authentication, policies, or network conditions. This approach is commonly used in multi-tenant environments, service provider networks, enterprise security, and VPN segmentation.
 
 {{%notice note%}}
-VRFs coming in on the Radius authentication message must already exist on the switch.
+- VRFs coming in on the Radius authentication message must already exist on the switch.
+- Dynamic VRF assignment is supported in {{<link url="#host-modes" text="multi host mode">}} only.
 {{%/notice%}}
 
 {{< tabs "TabID451 ">}}
diff --git a/content/cumulus-linux-516/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md b/content/cumulus-linux-516/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md
@@ -310,19 +310,19 @@ cumulus@switch:~$ nv config apply
 ```
 
 {{< /tab >}}
-{{< tab "Environment sensors">}}
+{{< tab "Environment sensor">}}
 
 To enable environment sensor statistics:
 
 ```
-cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensors state enabled
+cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensor state enabled
 cumulus@switch:~$ nv config apply
 ```
 
 To adjust the sample interval for environment sensor statistics:
 
 ```
-cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensors sample-interval 100
+cumulus@switch:~$ nv set system telemetry platform-stats class environment-sensor sample-interval 100
 cumulus@switch:~$ nv config apply
 ```
 
@@ -2889,7 +2889,7 @@ CPU statistics include the CPU core number and operation mode (user, system, idl
 | `node_memory_Zswapped_bytes` | `/proc/meminfo` Zswapped bytes. |
 
 {{< /tab >}}
-{{< tab "Environment Sensors ">}}
+{{< tab "Environment Sensor ">}}
 
 | Name | Description |
 |----- | ----------- |
diff --git a/content/cumulus-linux-516/Network-Virtualization/Ethernet-Virtual-Private-Network-EVPN/_index.md b/content/cumulus-linux-516/Network-Virtualization/Ethernet-Virtual-Private-Network-EVPN/_index.md
@@ -31,11 +31,13 @@ Cumulus Linux fully supports EVPN as the control plane for VXLAN, including for
 
   EVPN VXLAN IPv6 VTEP does not support:
   - MAC (host) mobility.
-  - PIM multicast based BUM handling.
-  - Interoperability with an IPv4 VTEP in the fabric.
+  - PIM multicast-based BUM handling.
+  - Interoperability with IPv4 and IPv6 VTEPs in the fabric.
+  - Dual stack VXLAN mode (with both an IPv4 and IPv6 VTEP source address).
   - MLAG.
   - Static VXLAN tunnels.
-  - The NVUE command `auto` setting for the VXLAN source IP address, which is applicable only for IPv4 VXLAN tunnels. If you want to set up IPv6 VXLAN tunnels, you must configure the VXLAN source IP address manually as an IPv6 GUA address.
+  - Downstream VNIs.
+  - The NVUE `nv set nve vxlan source address` command `auto` setting, which is applicable only for IPv4 VXLAN tunnels. If you want to configure IPv6 VXLAN tunnels, you must set the VXLAN source IP address manually as an IPv6 GUA address.
 
   {{%notice note%}}
   EVPN VXLAN IPv6 VTEP is a Beta feature.
diff --git a/content/cumulus-linux-516/System-Configuration/Authentication-Authorization-and-Accounting/TACACS.md b/content/cumulus-linux-516/System-Configuration/Authentication-Authorization-and-Accounting/TACACS.md
@@ -422,19 +422,13 @@ TACACS per-command authorization supports {{<link url="NVUE-CLI/#command-complet
 
 The following command allows TACACS+ users at privilege level 0 to run the `nv` and `ip` commands.
 
-{{%notice note%}}
-- Ensure that TACACS+ servers are reachable before setting new command authorization rules.
-- After configuring TACACS+ per-command authorization, you must restart the NVUE service.
-{{%/notice%}}
-
 {{< tabs "TabID392 ">}}
 {{< tab "NVUE Commands ">}}
 
 ```
 cumulus@switch:~$ nv set system aaa tacacs authorization 0 command ip 
 cumulus@switch:~$ nv set system aaa tacacs authorization 0 command nv
 cumulus@switch:~$ nv config apply
-cumulus@switch:~$ sudo systemctl restart nvued.service
 ```
 
 To show the per-command authorization settings, run the `nv show system aaa tacacs authorization` command:
@@ -456,7 +450,6 @@ When you configure per-command authorization on the switch, only define the init
 
 ```
 cumulus@switch:~$ sudo tacplus-restrict -i -u tacacs0 -a ip nv
-cumulus@switch:~$ sudo systemctl restart nvued.service
 ```
 
 The `tacplus-auth` command handles authorization for each command. To make this an enforced authorization, change the TACACS+ log in to use a restricted shell, with a very limited executable search path. Otherwise, the user can bypass the authorization. The `tacplus-restrict` utility simplifies setting up the restricted environment.
diff --git a/content/cumulus-linux-516/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-API.md b/content/cumulus-linux-516/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-API.md
@@ -1910,6 +1910,10 @@ cumulus@switch:~$ curl -u 'cumulus:CumulusLinux!' --insecure -X GET https://127.
 }
 ```
 
+{{%notice note%}}
+The API `GET` operation output matches the operational revision view (equivalent to `nv show --rev=operational`) and omits unset fields that are shown in the default `nv show` output.
+{{%/notice%}}
+
 ### Use Filters in a Query
 
 You can use filters to show specific information in a query with the `curl -u '<username>:<password>' -k -X GET http://path?filter=<filter>` syntax. The following example is the equivalent REST API method for the NVUE `nv show interface --filter type=svi` command, which shows all SVIs configured on the switch:
diff --git a/content/cumulus-linux-516/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-CLI.md b/content/cumulus-linux-516/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-CLI.md
diff --git a/content/cumulus-linux-516/Whats-New/_index.md b/content/cumulus-linux-516/Whats-New/_index.md
diff --git a/content/cumulus-linux-517/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md b/content/cumulus-linux-517/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md
diff --git a/content/cumulus-linux-517/System-Configuration/Authentication-Authorization-and-Accounting/TACACS.md b/content/cumulus-linux-517/System-Configuration/Authentication-Authorization-and-Accounting/TACACS.md
diff --git a/content/cumulus-linux-517/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-API.md b/content/cumulus-linux-517/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-API.md
diff --git a/content/cumulus-linux-517/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-CLI.md b/content/cumulus-linux-517/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-CLI.md

Original file line number	Diff line number	Diff line change
`@@ -1853,6 +1853,10 @@ cumulus@switch:~$ curl -u 'cumulus:CumulusLinux!' --insecure -X GET https://127.`
`1853`	`1853`	`}`
`1854`	`1854`	```
`1855`	`1855`
	`1856`	`+{{%notice note%}}`
	`1857`	+The API `GET` operation output matches the operational revision view (equivalent to `nv show --rev=operational`) and omits unset fields that are shown in the default `nv show` output.
	`1858`	`+{{%/notice%}}`
	`1859`	`+`
`1856`	`1860`	`### Use Filters in a Query`
`1857`	`1861`
`1858`	`1862`	You can use filters to show specific information in a query with the `curl -u '<username>:<password>' -k -X GET http://path?filter=<filter>` syntax. The following example is the equivalent REST API method for the NVUE `nv show interface --filter type=svi` command, which shows all SVIs configured on the switch:
Original file line number	Diff line number	Diff line change
`@@ -1875,6 +1875,10 @@ cumulus@switch:~$ curl -u 'cumulus:CumulusLinux!' --insecure -X GET https://127.`
`1875`	`1875`	`}`
`1876`	`1876`	```
`1877`	`1877`
	`1878`	`+{{%notice note%}}`
	`1879`	+The API `GET` operation output matches the operational revision view (equivalent to `nv show --rev=operational`) and omits unset fields that are shown in the default `nv show` output.
	`1880`	`+{{%/notice%}}`
	`1881`	`+`
`1878`	`1882`	`### Use Filters in a Query`
`1879`	`1883`
`1880`	`1884`	You can use filters to show specific information in a query with the `curl -u '<username>:<password>' -k -X GET http://path?filter=<filter>` syntax. The following example is the equivalent REST API method for the NVUE `nv show interface --filter type=svi` command, which shows all SVIs configured on the switch: