Default config: All bgp pairing have already been
configured.
R1.....................
int s0/1
ip add
20.20.20.1 255.255.255.0
no shut
int s0/0
ip add
10.10.10.1 255.255.255.0
no shut
int lo 1
ip add
150.150.150.1 255.255.255.0
no shut
exit
router bgp
100
nei
10.10.10.2 remote-as 100
nei
10.10.10.2 next-hop-self
nei
20.20.20.2 remote-as 111
bgp
router-id 150.150.150.1
no
synchronization
R2..................
int s0/1
ip add 30.30.30.2 255.255.255.0
no shut
int s0/0
ip add 10.10.10.2 255.255.255.0
no shut
int lo 1
ip add 77.77.77.1 255.255.255.0
no shut
exit
router bgp 100
nei 10.10.10.1 remote-as 100
nei 10.10.10.1 next-hop-self
nei 30.30.30.1 remote-as 111
bgp router-id 77.77.77.1
no synchronization
ISP1..................................
int s0/0
ip add
20.20.20.2 255.255.255.0
no shut
int s0/1
ip add
30.30.30.1 255.255.255.0
no shut
int lo 1
ip add
200.200.200.1 255.255.255.0
no shut
exit
router bgp
111
nei
20.20.20.1 remote-as 100
nei
30.30.30.2 remote-as 100
bgp
router-id 200.200.200.1
no
synchronization
Now lets
face the problems
1) Cfg soft –reconfiguration on R2 for all its neighbors. Hence clear the bgp on nei 10.10.10.2
R2(conf)#router bgp 100
nei 10.10.10.2
soft-reconfiguration inbound
nei 20.20.20.2
soft-reconfiguration inbound
[We don’t need to do in the outbound direction since it involves
sending of routes it has received.]
To clear the nei 10.10.10.2,
R2# clear ip bgp 10.10.10.2 soft
in
clear ip bgp nei 10.10.10.2 soft out
2) cfg R2 to do a route-refresh. clear nei
isp1
Route-refresh
do not actually require a config. We only need to check whether our
router support this functionality.
R2#sh
ip bgp nei 30.30.30.1
Route refresh: advertised and received (old & new)
Route refresh: advertised and received (old & new)
We do the same on ISP1 to check whether it supports
route-refresh..Then to clear the bgp nei,
R2#clear
ip bgp 30.30.30.1 in
clear ip bgp 30.30.30.1 out
No comments:
Post a Comment