Disabling bgp4 – Brocade Virtual ADX Switch and Router Guide (Supporting ADX v03.1.00) User Manual
Page 224
210
Brocade Virtual ADX Switch and Router Guide
53-1003246-01
Enabling and disabling BGP4
8
NOTE
By default, the Virtual ADX device ID is the IP address configured on the lowest numbered loopback
interface. If the device does not have a loopback interface, the default device ID is the lowest
numbered IP interface address configured on the device. For more information, refer to
on page 244. If you change the device ID, all current BGP4 sessions, OSPF
adjacencies, and OSPFv3 adjacencies are cleared.
NOTE
When BGP4 is enabled on a device, resetting the system is unnecessary. The protocol is activated
when you enable it. The device begins a BGP4 session with a BGP4 neighbor when you add the
neighbor.
Disabling BGP4
If you disable BGP4, the device removes all the running configuration information for the disabled
protocol from the running configuration. To restore the BGP4 configuration, you must reload the
software to load the BGP4 configuration from the startup configuration. When you save the startup
configuration file after disabling the protocol, all of the BGP4 configuration information for the
disabled protocol is removed from the startup configuration file.
The CLI displays a warning message such as the following.
Virtual ADX(config)# no router bgp
router bgp mode now disabled. All bgp config data will be lost when writing to
flash!
The Web Management Interface does not display a warning message.
If you are testing a BGP4 configuration and may need to disable and re-enable the protocol, you
should make a backup copy of the startup configuration file containing the BGP4 configuration
information. If you remove the configuration information by saving the configuration after disabling
the protocol, you can restore the BGP4 configuration by copying the backup copy of the startup
configuration file onto the flash memory.
To disable BGP4 without losing the BGP4 configuration information, remove the local AS (for
example, by entering the no local-as num command). When you remove the local AS, BGP4 retains
the other configuration information but will not become operational until you reset the local AS.