Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

no-bundle-flap

date_range 20-Nov-23

Syntax

content_copy zoom_out_map
no-bundle-flap;

Hierarchy Level

content_copy zoom_out_map
[edit dynamic-profiles name interfaces name load-balancing-options]

Description

When you add a new member to an existing AMS bundle, all the existing members and the newly added member of the AMS bundle go for reboot and disrupts the traffic. To overcome this problem for IPsec services, configure the no-bundle-flap statement before adding a new member to the AMS bundle. When you configure no-bundle-flap command and add a new member to the AMS bundle, the existing members of AMS bundle will not reboot, only the newly added member reboot avoiding the traffic disruption.

Required Privilege Level

system—To view this statement in the configuration.

system-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 21.1R1

footer-navigation