A BGP process must be started before configuring BGP functions. When starting a BGP process, specify the number of the AS to which the device belongs.
Changing BGP router IDs will cause the reestablishment of the BGP connection between routers.
The system view is displayed.
BGP routing loop detection is enabled.
After this function is enabled, the device reports an alarm when detecting a BGP4+ routing loop. Because the device cannot determine whether the routing loop is removed, the alarm will not be cleared automatically even if the routing loop is removed. To manually clear the BGP routing loop alarm, run the clear route loop-detect bgp alarm command.
BGP is enabled (the local AS number is specified), and the BGP view is displayed.
A BGP router ID is set.
If the router ID of the router is the IP address of a physical interface, the change in the IP address will cause route flapping on the network. To enhance network stability, configuring the address of a loopback interface as the router ID is recommended.
If the device does not have an IPv4 interface, it needs to be configured with a router ID.
All sessions between the device and its BGP4+ peers are terminated.
During the system upgrade, or maintenance, you can run this command to terminate all sessions between a device and its BGP4+ peers to prevent possible BGP4+ route flapping from affecting the network.
After the upgrade or maintenance, run the undo shutdown command to restore the BGP4+ peer sessions; otherwise, BGP4+ functions will be affected.
The configuration is committed.