
Configuring IP Exterior Gateway Protocols (BGP and EGP)
2-2
308628-15.0 Rev 00
router_id
is the BGP router ID expressed as an octet string. The router ID typically
is a circuitless IP interface used by BGP to communicate with other BGP routers.
If the router is also running OSPF, the BGP ID must match the OSPF ID.
For example, the following command configures global BGP with a router ID
(local IP address) of 2.2.2.2:
ip#
/jointfilesconvert/97454/bgp router-id 2.2.2.2
/jointfilesconvert/97454/bgp#
BGP is now running on the router with default values for all BGP parameters. You
customize BGP by modifying BGP parameters as described in Chapter 3,
“Configuring Global BGP Parameters.”
Step 2: Defining a Peer-to-Peer Connection
For BGP to exchange routing information with BGP peers located in other
autonomous systems or within the same AS, you must configure at least one peer
connection.
To define a peer-to-peer connection, go to the BGP prompt (for example,
box; ip;
/jointfilesconvert/97454/bgp
) and enter:
peer local
<local_ip_address> remote <remote_ip_address>
as
<as_number>
local_ip_address
is the address, expressed in dotted-decimal format, of an IP
interface on the local router.
remote_ip_address
is the address of an IP interface on the remote peer router.
as_number
is the number of the AS in which the remote peer is located.
For example, the following command defines a peer-to-peer connection between
local IP interface 2.3.3.3 and remote interface 2.3.3.4. The remote BGP peer is
located in AS 4.
/jointfilesconvert/97454/bgp#
peer local 2.3.3.3 remote 2.3.3.4 as 4
peer/2.3.3.3/2.3.3.4#
The BGP peer-to-peer relationship is established with default values for all BGP
peer parameters. You customize the peer-to-peer connection by modifying BGP
peer parameters as described in Chapter 4, “
Configuring BGP Peers.”
Comentarios a estos manuales