From: wsqccie@hotnail.com
Date: Mon Apr 21 2003 - 10:33:07 GMT-3
Annu/Denis
I also test, the nei ebgp-mulithop is must for R4 and R9.
However, I meet the below issue, pls help:
Just same your network, a more router connect to r4, eg, called r11. and there are diffirent in FR.
R4 and R9connect to R5 with S0.1
R10 connect to R5 with s0.2
It is no problem to setup bgp connection between confedaratin 4000(r4and r11) and confedaration 400 (R10 and r9),
r5 will not join BGP. in condedaration 400 can not reach the route decleared b 4000. it is unreachable. I try to find the path with traceout , but will successed end in R5. I donot know why.
urgent!thanks!
----- Original Message -----
From: "Denis Theodossiou" <denis.theodossiou@btinternet.com>
To: "'Annu Roopa'" <annu_roopa@yahoo.com>; <jhays@jtan.com>; <ccielab@groupstudy.com>; <wsqccie@hotmail.com>
Sent: Monday, April 21, 2003 5:13 PM
Subject: RE: BGP Confedration issue-longish
> Shouldn't you use ebgp-multihop between R4 and R9, since on the layer 2
> you are going via 2 hops (R4<->R5<->R9) and they are in different AS
> (ie. It will be a confed-ebgp connection) ?
>
> Denis
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Annu Roopa
> Sent: 19 April 2003 16:49
> To: jhays@jtan.com; ccielab@groupstudy.com; wsqccie@hotmail.com
> Cc: annu_roopa@yahoo.com
> Subject: RE: BGP Confedration issue-longish
>
>
> Thanks to all those who replied. I have the complete configs now.
> Jonathan if u see my diagram i dont think i have mentioned 2 Hubs (could
> not find it). Only R5 is the Hub of the Frelay cloud and R4/R9/R10 are
> spokes on the same subnet. There is no routing protcol and i have Fr
> maps between them. Statics if needed. WSqccie: The "?" u have against is
> correct (as i understand ..correct me if i am wrong) as R5 and R9 is
> identifying the Confedration of R9 and R5. R5 is hub with 3 spokes
> R4/R9/R10. R5 (Hub) and one spoke R10 is in same Confed 400 while other
> 2 spokes (R9/R4) are in Confed 4000. The Confed sub AS# are identified
> with them.PVc are all up and i can ping all the neighbour interfaces.
> R5- confed sub AS - 1000R10- confed sub AS - 1001R9- confed sub AS -
> 2000R4- confed sub AS - 2001
> ------------------------------------------------------
> hostname R4
> ip subnet-zero
> interface Loopback0
> ip address 153.1.33.11 255.255.255.0
>
> interface Ethernet0
> ip address 153.1.43.11 255.255.255.128
> ip ospf priority 0
> !
> interface Serial0
> ip address 153.1.200.4 255.255.255.0
> encapsulation frame-relay
> ip split-horizon
> no arp frame-relay
> frame-relay map ip 153.1.200.5 301 broadcast
> frame-relay map ip 153.1.200.9 301 broadcast
> frame-relay map ip 153.1.200.10 301 broadcast
> no frame-relay inverse-arp
> frame-relay lmi-type cisco
>
> !
> router bgp 2001
> no synchronization
> bgp router-id 153.1.33.11
> bgp log-neighbor-changes
> bgp confederation identifier 4000
> bgp confederation peers 2000
> network 153.1.33.0 mask 255.255.255.0
> neighbor 153.1.200.9 remote-as 2000
>
> R4#ping 153.1.200.9
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 153.1.200.9, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 116/119/128
> ms
>
> R4#ping
> Protocol [ip]:
> Target IP address: 153.1.200.9
> Repeat count [5]: 10
> Datagram size [100]:
> Timeout in seconds [2]:
> Extended commands [n]: y
> Source address or interface: 153.1.200.4
> Type of service [0]:
> Set DF bit in IP header? [no]:
> Validate reply data? [no]:
> Data pattern [0xABCD]:
> Loose, Strict, Record, Timestamp, Verbose[none]:
> Sweep range of sizes [n]:
> Type escape sequence to abort.
> Sending 10, 100-byte ICMP Echos to 153.1.200.9, timeout is 2
> seconds:!!!!!!!!!!
> Success rate is 100 percent (10/10), round-trip min/avg/max =
> 116/126/212 ms
>
> ----------------------------------------------------------------
> hostname R5
> ip subnet-zero
> no ip domain-lookup
> interface Loopback0
> ip address 153.1.1.5 255.255.255.0
>
> interface Ethernet0
> ip address 186.1.1.5 255.255.255.0
> !
> interface Serial0
> ip address 153.1.200.5 255.255.255.0
> encapsulation frame-relay
> no arp frame-relay
> frame-relay map ip 153.1.200.4 103 broadcast
> frame-relay map ip 153.1.200.9 102 broadcast
> frame-relay map ip 153.1.200.10 104 broadcast
> no frame-relay inverse-arp
>
> router bgp 1000
> bgp router-id 153.1.1.5
> bgp log-neighbor-changes
> bgp confederation identifier 400
> bgp confederation peers 1001
> network 153.1.1.0 mask 255.255.255.0
> neighbor 153.1.200.9 remote-as 4000
> neighbor 153.1.200.9 send-community
> neighbor 153.1.200.10 remote-as 1001
> neighbor 153.1.200.10 next-hop-self
> neighbor 153.1.200.10 send-community
> neighbor 186.1.1.100 remote-as 100
> neighbor 186.1.1.100 route-map com in
> !
> route-map com permit 10
> match as-path 11
> set community 400:600 additive
> !
> route-map com permit 20
> !
> -------------------------------------------------------------
> hostname R9
> interface Loopback0
> ip address 153.1.9.9 255.255.255.0!
>
> interface Serial0
> ip address 153.1.200.9 255.255.255.0
> encapsulation frame-relay
> ip split-horizon
> no arp frame-relay
> frame-relay map ip 153.1.200.4 201 broadcast
> frame-relay map ip 153.1.200.5 201 broadcast
> frame-relay map ip 153.1.200.10 201 broadcast
> no frame-relay inverse-arp
> !
>
> router bgp 2000
> no synchronization
> bgp router-id 153.1.9.9
> bgp log-neighbor-changes
> bgp confederation identifier 4000
> bgp confederation peers 2001
> network 153.1.9.0 mask 255.255.255.0
> neighbor 153.1.200.4 remote-as 2001
> neighbor 153.1.200.5 remote-as 400
> neighbor 153.1.200.5 route-map comm in
> !
> ip kerberos source-interface any
> ip classless
>
> ip route 153.1.1.0 255.255.255.0 153.1.200.5
> ip bgp-community new-format
> ip community-list 1 deny 400:600
> ip community-list 1 permit internet
> !
> route-map comm permit 10
> match community 1
> !
>
> R9# ping
> Protocol [ip]:
> Target IP address: 153.1.200.4
> Repeat count [5]:
> Datagram size [100]:
> Timeout in seconds [2]:
> Extended commands [n]: y
> Source address or interface: 153.1.200.9
> Type of service [0]:
> Set DF bit in IP header? [no]:
> Validate reply data? [no]:
> Data pattern [0xABCD]:
> Loose, Strict, Record, Timestamp, Verbose[none]:
> Sweep range of sizes [n]:
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 153.1.200.4, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 116/117/120
> ms
>
> ------------------------------------------------------
> R10#sr
> hostname R10
>
> interface Loopback0
> ip address 153.1.4.4 255.255.255.0
> !
> interface Ethernet0
> ip address 153.1.43.10 255.255.255.128
> ip ospf cost 100
> ip ospf priority 100
> !
> interface Serial0
> ip address 153.1.200.10 255.255.255.0
> encapsulation frame-relay
> ip split-horizon
> no arp frame-relay
> frame-relay map ip 153.1.200.4 401 broadcast
> frame-relay map ip 153.1.200.5 401 broadcast
> frame-relay map ip 153.1.200.9 401 broadcast
> no frame-relay inverse-arp
> !
> router bgp 1001
> no synchronization
> bgp router-id 153.1.4.4
> bgp log-neighbor-changes
> bgp confederation identifier 400
> bgp confederation peers 1000
> network 153.1.4.0 mask 255.255.255.0
> neighbor 153.1.200.5 remote-as 1000
>
> ip kerberos source-interface any
> ip classless
> no ip http server
> ip bgp-community new-format
> !
> access-list 8 deny 100.100.8.0 0.0.0.255
> access-list 8 permit any
>
> route-map eight permit 10
> match ip address 8
> !
> Let me know. Thanks Annu
>
>
> ---------------------------------
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
This archive was generated by hypermail 2.1.4 : Thu May 01 2003 - 13:36:00 GMT-3