From: Tandou Mohamed (dtandou@yahoo.com)
Date: Sat Dec 23 2006 - 00:30:53 ART
CAT3550-1#debug ip tcp transactions
TCP special event debugging is on
CAT3550-1#
6d09h: TCB012BFB54 created
6d09h: TCB012BFB54 setting property TCP_WINDOW_SIZE (0) 12C2EC0
6d09h: TCB012BFB54 setting property TCP_TOS (11) 12C2EC4
6d09h: TCB012BFB54 bound to 172.16.6.10.11044
6d09h: TCP: sending SYN, seq 3338094220, ack 0
6d09h: TCP0: Connection to 172.16.10.103:179, advertising MSS 536
6d09h: TCP0: state was CLOSED -> SYNSENT [11044 -> 172.16.10.103(179)]
CAT3550-1#
6d09h: TCP0: timeout #3 - timeout is 16000 ms, seq 3338094220
6d09h: TCP: (11044) -> 172.16.10.103(179)
CAT3550-1#
6d09h: TCP0: timeout #4 - timeout is 32000 ms, seq 3338094220
6d09h: TCP: (11044) -> 172.16.10.103(179)
CAT3550-1#
6d09h: TCP0: state was SYNSENT -> CLOSED [11044 -> 172.16.10.103(179)]
6d09h: TCB 0x12BFB54 destroyed
Nick Griffin <nick.jon.griffin@gmail.com> wrote: Perhaps, turn on "debug ip tcp transactions" to see if your getting any tcp client/server activity to our from that neighbor.
On 12/22/06, Tandou Mohamed <dtandou@yahoo.com> wrote: No, My Cat1 is on 172.16.6.0/24 and BB3 is on 172.16.10.0/24. I tried loopback peering using ebgp-multihop with static route it did not work. In the real lab i will not have access to the backbone to check the config. BB3 is the only router on that network 172.16.10.0/24
Thanks
Mohamed
Nick Griffin < nick.jon.griffin@gmail.com> wrote:
Tandou, does your 3550-1 have an interface on the 172.16.10.0 network, if not, do you have a route to it?
On 12/22/06, Tandou Mohamed <dtandou@yahoo.com> wrote: This is what my config looks like.
Thanks,
Mohamed
router bgp 65520
no synchronization
bgp log-neighbor-changes
bgp confederation identifier 50
bgp confederation peers 65522
neighbor internal peer-group
neighbor internal remote-as 65520
neighbor internal update-source Loopback0
neighbor 172.16.10.103 remote-as 101
neighbor 172.16.10.103 filter-list 10 out
neighbor 192.168.1.1 peer-group internal
neighbor 192.168.2.2 peer-group internal
neighbor 192.168.5.5 peer-group internal
neighbor 192.168.11.11 remote-as 65522
neighbor 192.168.11.11 ebgp-multihop 255
neighbor 192.168.11.11 update-source Loopback0
no auto-summary
CAT3550-1#sh ip bgp summary
BGP router identifier 192.168.10.10, local AS number 65520
BGP table version is 11, main routing table version 11
10 network entries and 10 paths using 1330 bytes of memory
1 BGP path attribute entries using 60 bytes of memory
1 BGP AS-PATH entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP activity 10/0 prefixes, 10/0 paths, scan interval 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
172.16.10.103 4 101 0 0 0 0 0 never Idle
192.168.1.1 4 65520 498 499 11 0 0 08:14:15 0
192.168.2.2 4 65520 498 499 11 0 0 08:14:19 0
192.168.5.5 4 65520 498 499 11 0 0 08:14:12 0
192.168.11.11 4 65522 501 500 11 0 0 08:13:06 10
"Sharifi, Reza" < Reza.Sharifi@gdit.com> wrote:
Mohamed,
Does your config looks like this sample?
router bgp 400
neighbor 1.1.1.1 remote-as 400
neighbor 1.1.1.1 update-source Loopback0
!
ip route 1.1.1.1 255.255.255.255 10.10.10.2
router bgp 400
neighbor 2.2.2.2 remote-as 400
neighbor 2.2.2.2 update-source Loopback0
!
ip route 2.2.2.2 255.255.255.255 10.10.10.1
You may want to post your config
Reza
-----Original Message-----
From: nobody@groupstudy.com [mailto: nobody@groupstudy.com] On Behalf Of
Tandou Mohamed
Sent: Friday, December 22, 2006 1:25 PM
To: ccielab@groupstudy.com
Subject: IPEXPERT LAB 38
Hello GS,
i need a hint. the lab said config bgp between Cat1 and BB3 in as 101
I configured my peering but BGP does not come up. it stays idle. i
double my config with BB3 looks ok. Any idea ?
Mohamed
This archive was generated by hypermail 2.1.4 : Tue Jan 02 2007 - 07:50:39 ART