Skip to content

Commit f1860d5

Browse files
committed
Merge branch 'final5.17-feedback' into stage
2 parents 370c5b0 + 5a93689 commit f1860d5

3 files changed

Lines changed: 2 additions & 3 deletions

File tree

content/cumulus-linux-517/Monitoring-and-Troubleshooting/Security-Alerts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Cumulus Linux can send proactive alerts as SNMPv3 traps to configured trap desti
2323
- Disk full and disk I/O error events are logged to syslog only (no SNMP traps). The `space_left` and `admin_space_left` thresholds provide an early warning through SNMP traps before these critical conditions are reached.
2424
- A clean `auditd` restart (`sudo service auditd restart`) does not trigger an alert.
2525
- The security alerts manage only the `alert-related` action parameters in the `auditd` configuration (`space_left_action`, `admin_space_left_action`, `disk_full_action`, `disk_error_action`).
26-
- If the `auditd.conf` file contains invalid values (for example, if `admin_space_left` has a higher setting than `space_left`), enabling or disabling security alerts fails because the `auditd` service cannot restart. To recover, correct the values in `/etc/audit/auditd.conf` file, then run the `sudo systemctl reset-failed auditd` and
26+
- If the `auditd.conf` file contains invalid values (for example, if `admin_space_left` has a higher setting than `space_left`), enabling or disabling security alerts fails because the `auditd` service cannot restart. To recover, correct the values in the `/etc/audit/auditd.conf` file, then run the `sudo systemctl reset-failed auditd` and
2727
`sudo systemctl restart auditd` commands.
2828
{{%/notice%}}
2929

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -526,7 +526,7 @@ cumulus@switch:~$ sudo rm ~tacacs0/bin/*
526526
527527
## Server-side Per-command Authorization
528528
529-
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.
529+
When 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.
530530
531531
{{%notice note%}}
532532
- 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.

content/cumulus-linux-517/Whats-New/New-and-Removed-NVUE-Commands.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,6 @@ nv set qos advance-buffer-config <profile-id> shared-headroom exclusive-headroom
5151
nv set qos advance-buffer-config <profile-id> shared-headroom oversubscription-ratio
5252
nv set qos advance-buffer-config <profile-id> shared-headroom required-headroom-per-pg
5353
nv set qos pfc <profile-id> small-packet-probability
54-
nv set system config backup restore <snapshot-id>
5554
nv set system dot1x pre-auth allow-protocol lldp ingress
5655
nv set system dot1x pre-auth allow-protocol lldp egress
5756
nv set system dot1x pre-auth allow-protocol lldp both

0 commit comments

Comments
 (0)