Skip to content

Commit c658ba9

Browse files
author
Cumulus Docs Auto Merge
committed
Merge remote-tracking branch 'origin/stage'
2 parents 83fe2cf + 753c68b commit c658ba9

4 files changed

Lines changed: 13 additions & 7 deletions

File tree

  • content
    • cumulus-linux-516/Whats-New
    • cumulus-linux-517

content/cumulus-linux-516/Whats-New/_index.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -65,6 +65,12 @@ To upgrade to Cumulus Linux 5.16 from a release that does not support package up
6565
Cumulus Linux 5.16 does not support online package upgrade; you can use offline package upgrade instead.
6666
{{%/notice%}}
6767

68+
### Significant NVUE Command and API Updates
69+
70+
{{%notice warning%}}
71+
To align with a long-term vision of a common interface between Cumulus Linux, NVIDIA OS (NVOS), and Host-Based Networking, Cumulus Linux 5.15 included significant NVUE command and API updates. If you are upgrading to Cumulus Linux 5.16 from Cumulus Linux 5.14 or earlier, review the list of {{<exlink url="https://docs.nvidia.com/networking-ethernet-software/cumulus-linux-515/Whats-New/New-and-Changed-NVUE-Commands/" text="New, Changed, and Deprecated NVUE Commands in Cumulus Linux 5.15">}} before you upgrade to ensure a smooth transition.
72+
{{%/notice%}}
73+
6874
### Maximum Number of NVUE Revisions
6975

7076
Cumulus Linux includes an option to set the {{<link url="NVUE-CLI/#maximum-revisions-limit" text="maximum number of revisions">}} after which NVUE deletes older revisions automatically. The default setting is 100. If you upgrade to Cumulus Linux 5.16 from 5.12 or earlier, the first time you run `nv set` or `nv unset` commands, NVUE deletes older revisions if the number of revisions on the switch is greater than 100.

content/cumulus-linux-517/Layer-1-and-Switch-Ports/802.1X-Interfaces.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -446,7 +446,8 @@ Dynamic VRF assignment on 802.1X enables layer 3 ports to be authenticated and a
446446
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.
447447

448448
{{%notice note%}}
449-
VRFs coming in on the Radius authentication message must already exist on the switch.
449+
- VRFs coming in on the Radius authentication message must already exist on the switch.
450+
- Dynamic VRF assignment is supported in {{<link url="#host-modes" text="multi host mode">}} only.
450451
{{%/notice%}}
451452

452453
{{< tabs "TabID451 ">}}

content/cumulus-linux-517/Network-Virtualization/Ethernet-Virtual-Private-Network-EVPN/_index.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,6 @@ Cumulus Linux fully supports EVPN as the control plane for VXLAN, including for
3636
- Dual stack VXLAN mode (with both an IPv4 and IPv6 VTEP source address).
3737
- MLAG.
3838
- Static VXLAN tunnels.
39-
- Downstream VNIs.
4039
- 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.
4140

4241
{{%notice note%}}

content/cumulus-linux-517/System-Configuration/Authentication-Authorization-and-Accounting/TACACS.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -485,7 +485,7 @@ cumulus@switch:~$ sudo rm ~tacacs0/bin/*
485485
486486
## Server-side Per-command Authorization
487487
488-
Whe you use server-side per-command authorization, Cumulus Linux sends every command that the TACACS+ user enters to the TACACS server for authorization before executing the command. The TACACS server is the sole authority on which commands are permitted; you don't need to configure local per-command configuration on the switch.
488+
Whe you use server-side per-command authorization, Cumulus Linux sends every command that the TACACS+ user enters to the TACACS server for authorization before executing the command.
489489
490490
{{%notice note%}}
491491
- You can use server-side per-command authorization together with specific command authorization so that Cumulus Linux authorizes certain commands locally and forwards all other commands *only* to the TACACS server.
@@ -497,17 +497,17 @@ By default, server-side per-command authorization is disabled for all privilege
497497
498498
To enable server-side per-command authorization for a TACACS privilege level, run the `nv set system aaa tacacs authorization <priority-id> all-commands enabled` command.
499499
500-
The following example enables server-side authorization for all commands at privilege level 15:
500+
The following example enables server-side authorization for all commands at privilege level 0:
501501
502502
```
503-
cumulus@switch:~$ nv set system aaa tacacs authorization 15 all-commands enabled
503+
cumulus@switch:~$ nv set system aaa tacacs authorization 0 all-commands enabled
504504
cumulus@switch:~$ nv config apply
505505
```
506506
507-
To disable server-side per-command authorization for a TACACS privilege level and revert to local command authorization only, run the `nv set system aaa tacacs authorization <priority-id> all-commands disabled` command:
507+
To disable server-side per-command authorization for a TACACS privilege level, run the `nv set system aaa tacacs authorization <priority-id> all-commands disabled` command:
508508
509509
```
510-
cumulus@switch:~$ nv set system aaa tacacs authorization 15 all-commands disabled
510+
cumulus@switch:~$ nv set system aaa tacacs authorization 0 all-commands disabled
511511
cumulus@switch:~$ nv config apply
512512
```
513513

0 commit comments

Comments
 (0)