Merge remote-tracking branch 'origin/stage'

Cumulus Docs Auto Merge · Cumulus Docs Auto Merge · commit 5f69b62fec8b · 2026-02-24T16:18:42.000Z
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/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/Network-Virtualization/Ethernet-Virtual-Private-Network-EVPN/_index.md b/content/cumulus-linux-516/Network-Virtualization/Ethernet-Virtual-Private-Network-EVPN/_index.md
@@ -33,7 +33,7 @@ Cumulus Linux fully supports EVPN as the control plane for VXLAN, including for
   - MAC (host) mobility.
   - 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)
+  - Dual stack VXLAN mode (with both an IPv4 and IPv6 VTEP source address).
   - MLAG.
   - Static VXLAN tunnels.
   - Downstream VNIs.
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
@@ -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-517/Network-Virtualization/Ethernet-Virtual-Private-Network-EVPN/_index.md b/content/cumulus-linux-517/Network-Virtualization/Ethernet-Virtual-Private-Network-EVPN/_index.md
@@ -33,7 +33,7 @@ Cumulus Linux fully supports EVPN as the control plane for VXLAN, including for
   - MAC (host) mobility.
   - 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)
+  - Dual stack VXLAN mode (with both an IPv4 and IPv6 VTEP source address).
   - MLAG.
   - Static VXLAN tunnels.
   - Downstream VNIs.
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
@@ -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-517/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-CLI.md b/content/cumulus-linux-517/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/knowledge-base/Support/Support-Offerings/Cumulus-NetQ-Release-Versioning-and-Support-Policy.md b/content/knowledge-base/Support/Support-Offerings/Cumulus-NetQ-Release-Versioning-and-Support-Policy.md
@@ -29,8 +29,8 @@ NetQ software installation file names include a version number, in the form of x
 
 For example:
 
-- netq-apps_5.0.0-cld12u5_amd64.deb
-- netq-agent_5.0.0-cld12u5_amd64.deb
+- netq-apps_5.1.0-cld12u7_amd64.deb
+- netq-agent_5.1.0-cld12u7_amd64.deb
 
 ## Release, Support Lifecycle and Support Policy
 
@@ -43,10 +43,9 @@ NetQ is offered with a per switch subscription that includes support for 1, 3, a
 
 ## NetQ Support Matrix
 
-The following table depicts the NetQ release support matrix:
-
 | NetQ Release | Release Date | End of Support |
 | :--------: | --------- | --------- |
+| 5.1.z | 24-Feb-2026 | 24-Feb-2028|
 | 5.0.z | 03-Nov-2025 | 03-Nov-2027 |
 | 4.15.z | 31-Jul-2025 | 31-Jul-2027 |
 | 4.14.z | 22-Apr-2025 | 22-Apr-2027 |

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:
Original file line number	Diff line number	Diff line change
`@@ -1910,6 +1910,10 @@ cumulus@switch:~$ curl -u 'cumulus:CumulusLinux!' --insecure -X GET https://127.`
`1910`	`1910`	`}`
`1911`	`1911`	```
`1912`	`1912`
	`1913`	`+{{%notice note%}}`
	`1914`	+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.
	`1915`	`+{{%/notice%}}`
	`1916`	`+`
`1913`	`1917`	`### Use Filters in a Query`
`1914`	`1918`
`1915`	`1919`	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: