This knowledge base has moved to the documentation site. Please visit the knowledge base here for the most up to date content. This site is no longer maintained.

Cumulus Networks Product Bulletin 2016-04-28: BGP Configurations Unexpectedly Removed after Disabling a Peer



Executing the BGP no neighbor activate command or the Cumulus Linux cl-bgp neighbor deactivate command to disable a BGP peer removes all associated address-family configurations, such as route-maps and prefix-lists; however, the peer neighbor statement remains. 


Cumulus Linux 2.5.7 and earlier

Root Cause

This behavior is due to the default implementation from network OS vendors, including Quagga, which Cumulus Linux uses for routing. The activate and no activate commands are intended to enable or disable a particular address-family for a neighbor, not to bring down/up the peering session, though that may occur as a side effect.

When these commands are issued under router bgp (that is, without an address-family specified), they pertain to the IPv4 unicast address-family. This behavior exists for historical reasons.

Address-family parameters for a neighbor can be configured only after that address-family has been activated for that neighbor, and address-family parameters for a neighbor — including route-maps and prefix-lists — are deleted when that address-family is deactivated for the neighbor.


The correct way to disable a peer is with the neighbor shutdown command:

router bgp 65535
neighbor shutdown
neighbor route-map filter-routes out
neighbor default-originate

or cl-bgp neighbor stop command:

cumulus@switch:~$ sudo cl-bgp neighbor stop

This preserves all neighbor-specific configurations for when the peer is brought back into service.

This behavior will change starting with Cumulus Linux 3.0.0, so that address-family parameters can be preconfigured before activation and deactivation will not delete them.

Stay Informed

Subscribe to our product bulletin mailing list to learn about these announcements as soon as they're made.


This support portal has moved

Cumulus Networks is now part of the NVIDIA Networking Business Unit! The NVIDIA Cumulus Global Support Services (GSS) team has merged its operations with the NVIDIA Mellanox support services team.

You can access NVIDIA Cumulus support content from the Mellanox support portal.

You open and update new cases on the Mellanox support portal. Any previous cases that have been closed have been migrated to the Mellanox support portal.

Cases that are still open on the Cumulus portal will continue to be managed on the Cumulus portal. Once these cases close, they will be moved to the Mellanox support portal.

Powered by Zendesk