User guide

Quick Steps for Using BGP Configuring BGP
page 4-4 OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2015
Quick Steps for Using BGP
The following steps and points summarize enabling BGP on the OmniSwitch.
1 For BGP to be operational, the router's unique router-id and primary address must be configured.
Assign the BGP local speaker's router-id and primary IP address that uniquely identifies the router in the
routing domain. If these values have not been manually configured, they default to the user-defined Loop-
back0 interface address, if present, or to the address assigned to the first operational IP interface.
-> ip router router-id 1.1.1.1
-> ip router primary-address 1.1.1.1
2 The BGP software is not loaded automatically when the router is booted. The user must manually load
the software into memory by typing the following command:
-> ip load bgp
3 Assign an Autonomous System (AS) number to the local BGP speaker. The user can change the default
AS number to fit the network requirements. For example:
-> ip bgp autonomous-system 100
4 Enable the BGP protocol by entering the following command:
-> ip bgp admin-state enable
5 Create a BGP peer entry. The local BGP speaker should be able to reach this peer. The IP address
assigned to the peer should be valid. For example:
-> ip bgp neighbor 198.45.16.145
6 Assign an AS number to the peer just created. All peers require an AS number. The AS number does
not have to be the same as the AS number for the local BGP speaker. For example:
-> ip bgp neighbor 198.45.16.145 remote-as 200
7 As a BGP peer is not active on the network until enabled, use the following command to enable the
peer created in Step 4:
-> ip bgp neighbor 198.45.16.145 admin-state enable