|
|
My solution is as follows:
R14#show run | s r b
router bgp 112
bgp router-id 172.9.0.3
bgp log-neighbor-changes
no bgp default ipv4-unicast
neighbor 172.9.143.3 remote-as 9
!
address-family ipv4
redistribute ospf 112
neighbor 172.9.143.3 activate
neighbor 172.9.143.3 send-label
exit-address-family
R14#show run | s r ospf
router ospf 112
router-id 172.9.0.14
redistribute bgp 112 subnets
network 172.9.0.14 0.0.0.0 area 0
network 172.9.145.14 0.0.0.0 area 0
distance ospf intra-area 10
R15# show run | s r ospf
router ospf 112
router-id 172.9.0.15
network 172.9.0.15 0.0.0.0 area 0
network 172.9.145.15 0.0.0.0 area 0
network 172.9.157.15 0.0.0.0 area 0
R7#show run | s r b
router bgp 9
bgp log-neighbor-changes
no bgp default ipv4-unicast
!
address-family ipv4 vrf ABC
network 172.9.0.7 mask 255.255.255.255
redistribute ospf 112
exit-address-family
R7#
R7#show run | s r ospf
router ospf 112 vrf ABC
router-id 172.9.0.7
domain-tag 9
redistribute bgp 9 subnets
network 172.9.0.7 0.0.0.0 area 0
network 172.9.157.7 0.0.0.0 area 0
RP/0/0/CPU0:XR3#show running-config router bgp
Mon Mar 23 15:41:07.258 UTC
router bgp 9
vrf ABC
rd 9:9
address-family ipv4 unicast
network 172.9.0.3/32
allocate-label all
!
address-family ipv6 unicast
network 2002:172:9::3/128
!
neighbor 172.9.143.14
remote-as 112
address-family ipv4 unicast
route-policy R14R3ipv4 in
route-policy R3R14ipv4 out
as-override
!
address-family ipv4 labeled-unicast
route-policy R14R3label in
route-policy R3R14label out
as-override
!
!
!
!
RP/0/0/CPU0:XR4(config)#show running-config router bgp
Mon Mar 23 15:42:00.775 UTC
router bgp 9
vrf ABC
rd 9:9
address-family ipv4 unicast
network 172.9.0.4/32
allocate-label all
!
neighbor 172.9.114.11
remote-as 112
address-family ipv4 unicast
route-policy R11R4ipv4 in
route-policy R4R11ipv4 out
as-override
!
address-family ipv4 labeled-unicast
route-policy R11R4label in
route-policy R4R11label out
as-override
!
!
!
!
R8#show run | s r b
router bgp 9
bgp log-neighbor-changes
no bgp default ipv4-unicast
address-family ipv4 vrf ABC
network 172.9.0.8 mask 255.255.255.255
neighbor 172.9.128.12 remote-as 112
neighbor 172.9.128.12 activate
neighbor 172.9.128.12 as-override
neighbor 172.9.128.12 send-label
exit-address-family
!
R11#show run | s r b
router bgp 112
bgp log-neighbor-changes
no bgp default ipv4-unicast
neighbor 172.9.114.4 remote-as 9
!
address-family ipv4
network 172.9.114.0 mask 255.255.255.0
redistribute ospf 112
neighbor 172.9.114.4 activate
neighbor 172.9.114.4 send-label
exit-address-family
R11#
R11#show run | s r ospf
router ospf 112
router-id 172.9.0.11
redistribute bgp 112 subnets
network 172.9.0.11 0.0.0.0 area 0
network 172.9.112.11 0.0.0.0 area 0
distance ospf intra-area 10
R12#show run | s r b
router bgp 112
bgp log-neighbor-changes
neighbor 172.9.128.8 remote-as 9
!
address-family ipv4
redistribute ospf 112
neighbor 172.9.128.8 activate
neighbor 172.9.128.8 send-label
exit-address-family
R12#
R12#show run | s r ospf
router ospf 112
router-id 172.9.0.12
redistribute bgp 112 subnets
network 172.9.0.12 0.0.0.0 area 0
network 172.9.112.12 0.0.0.0 area 0
distance ospf intra-area 10
I have the following questions:
1 why only the network segment network 172.9.114.0 mask 255.255.255.0 of R4 R11 is announced in BGP, while the direct network segments of R12 R8 and R3 R14 are not announced in BGP!
2. Why don‘t we use soo on R4 and R8 to prevent routes learned from cer11 from being announced to cer12 through SP?
3. The service provider of site2 has clearly stated that R3 does bidirectional redistribution on R7?
4. According to this solution, a large number of suboptimal routes are found
5, ask a correct solution!
|
-
|
English
Post time 24-3-2015 17:18:40
