From d92d9478d5588ede0ee7e514e8a0cac7cde33678 Mon Sep 17 00:00:00 2001 From: cumulusAnia Date: Tue, 28 Jan 2025 14:26:07 -0800 Subject: [PATCH] review feedback --- .../Optional-BGP-Configuration.md | 11 ++--------- .../NVIDIA-User-Experience-NVUE/NVUE-CLI.md | 2 +- 2 files changed, 3 insertions(+), 10 deletions(-) diff --git a/content/cumulus-linux-512/Layer-3/Border-Gateway-Protocol-BGP/Optional-BGP-Configuration.md b/content/cumulus-linux-512/Layer-3/Border-Gateway-Protocol-BGP/Optional-BGP-Configuration.md index 03e4d64bc5..69da1edd52 100644 --- a/content/cumulus-linux-512/Layer-3/Border-Gateway-Protocol-BGP/Optional-BGP-Configuration.md +++ b/content/cumulus-linux-512/Layer-3/Border-Gateway-Protocol-BGP/Optional-BGP-Configuration.md @@ -1882,7 +1882,8 @@ To bring BGP sessions with the neighbor back up, run the `no neighbor swp51 shut To reduce packet loss during planned switch or link maintenance, you can configure graceful BGP shutdown globally, on a peer group, or on a specific peer. {{%notice note%}} -You can enable graceful BGP shutdown either globally or on a peer or peer group but not both. +Graceful shutdown is active for a peer if you enable it at any level; globally, on the peer group, **or** on the specific peer. +Graceful shutdown is **not** active for a peer if you disable it on all levels; globally, on the peer group **and** on the specific peer. {{%/notice%}} ### Global Graceful BGP Shutdown @@ -2010,10 +2011,6 @@ Last update: Sun Dec 20 03:04:53 2020 When you enable BGP graceful shutdown on a peer, Cumulus Linux attaches a `graceful-shutdown` community to the relevant routes. Neighbors receiving the `graceful-shutdown` community mark these routes as less preferred if alternative routes exist. If no other routes are available, neighbors continue to use the routes with the `graceful-shutdown` community. If you enable graceful shutdown (maintenance) in multiple parts of the network or where there are no additional routes, traffic does not stop on the routes that have the attached `graceful-shutdown` community. -{{%notice note%}} -Before you enable graceful shutdown on a peer, make sure that *global* graceful shutdown is `off`. -{{%/notice%}} - {{< tabs "1962 ">}} {{< tab "NVUE Commands ">}} @@ -2085,10 +2082,6 @@ graceful-shutdown on When you enable BGP graceful shutdown on a peer group, Cumulus Linux attaches a `graceful-shutdown` community to the relevant routes. Neighbors receiving the `graceful-shutdown` community mark these routes as less preferred if alternative routes exist. If no other routes are available, neighbors continue to use the routes with the `graceful-shutdown` community. If you enable graceful shutdown (maintenance) in multiple parts of the network or where there are no additional routes, traffic does not stop on the routes that have the attached `graceful-shutdown` community. -{{%notice note%}} -Before you enable graceful shutdown on a peer group, make sure that *global* graceful shutdown is `off`. -{{%/notice%}} - {{< tabs "2037 ">}} {{< tab "NVUE Commands ">}} diff --git a/content/cumulus-linux-512/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-CLI.md b/content/cumulus-linux-512/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-CLI.md index de25ddacb2..108ca19279 100644 --- a/content/cumulus-linux-512/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-CLI.md +++ b/content/cumulus-linux-512/System-Configuration/NVIDIA-User-Experience-NVUE/NVUE-CLI.md @@ -459,7 +459,7 @@ cumulus@switch:~$ nv config apply -m "this is my message" To reset the NVUE configuration on the switch back to the default values, run the `nv config replace ` command; for example: ``` -cumulus@switch:~$ nv config replace /etc/switch.yaml +cumulus@switch:~$ nv config replace /usr/lib/python3/dist-packages/cue_config_v1/initial.yaml cumulus@switch:~$ nv config apply ```