Allied Telesis VERSION 5.4.3-2.6, BGP4 manual Enabling BGP Between Different Autonomous Systems

BGP and BGP4+ Configuration

Enabling BGP Between Different Autonomous

Systems

This example shows the minimum configuration required for enabling BGP on an interface when the BGP peers belong to different Autonomous Systems (ASs). Peer 1 and Peer 2 are two BGP peers in different ASs, AS200 and AS300 connecting to network 10.10.10.0/24.

AS200	AS300
10.10.10.10	10.10.10.11
Peer 1	Peer 2
	bgp_2

Peer 1

awplus#

configure terminal Enter the Global Configuration mode.

awplus(config)#

router bgp 200 Define the BGP routing process. The number 200 specifies the AS number of Peer 1.

awplus(config-router)#

neighbor 10.10.10.11 remote-as 300 Define BGP neighbors. 10.10.10.11 is the IP address of the neighbor (Peer 2) and 300 is the neighbor’s AS number.

Peer 2

awplus#

configure terminal Enter the Global Configuration mode.

awplus(config)#

router bgp 300 Define the BGP routing process. The number 300 specifies the AS number of Peer 2.

awplus(config-router)#

neighbor 10.10.10.10 remote-as 200 Define BGP neighbors. 10.10.10.10 is the IP address of the neighbor (Peer 1) and 200 is the neighbor’s AS number.

Names of Commands Used

router bgp (BGP and BGP4+) neighbor remote-as (BGP and BGP4+)

Validation Commands

show ip bgp summary (BGP) show ip bgp neighbors (BGP)

Software Reference Supplement for SwitchBlade® x8112, x908, x900 and x610 Series Switches

C613-50032-01 REV D AlliedWare PlusTM Operating System - Software Version 5.4.3-2.6 2.5