[ris-int] NCC#2004093307 [195.80.224.0/24 not flapping?]
RIPE NCC RIS ris-request at ripe.net
Fri Oct 8 16:42:50 CEST 2004
Hi all, I'd like to ask an advice on this case. This is about a peering session at RRC0 with AS7018 (12.0.1.63). They're saying that they recently do not receive the announcements/withdrawals of the beacon prefix 195.80.224.0/24. Apparently, the last time they noticed the flapping of this prefix was in the beginning of June 2004. In fact, looking at the RIS database, we can see the daily updates of the other RRC0 peers for 195.80.224.0/24, but none from AS7018. The peering session with them has been up for about 3 weeks. How can we check whether the BGP updates are being sent to them or not? Thanks, Vasco ----- Begin forwarded message ----- Date: Wed, 29 Sep 2004 18:18:40 -0400 From: Jay Borkenhagen <jayb at att.com> To: rispeering at ripe.net Subject: NCC#2004093307 195.80.224.0/24 not flapping? Cc: Aman Shaikh <ashaikh at research.att.com> Message-Id: <16731.13504.826194.244753 at oz.mt.att.com> Hi, We've got a BGP session from our 12.0.1.63 to your 193.0.4.28. I thought that 195.80.224.0/24 was supposed to oscillate based on the schedule at http://www.ripe.net/ris/beaconlist.html, but I haven't seen that prefix flap since sometime in early June 2004. Below I'll include what I've got now. Jay B. route-spews#show ip bgp sum [...] 193.0.4.28 4 12654 16 2163875 45600521 0 0 1w6d 2 [...] route-spews#show ip bgp nei 193.0.4.28 routes BGP table version is 45601230, local router ID is 12.0.1.63 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, S Stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 195.80.224.0 193.0.4.28 0 100 0 12654 i *> 195.80.239.0 193.0.4.28 0 100 0 12654 i Total number of prefixes 2 route-spews#show ip bgp 195.80.224.0/24 BGP routing table entry for 195.80.224.0/24, version 32179320 Paths: (2 available, best #1) Advertised to update-groups: 1 3 4 12654, (aggregated by 64536 10.34.183.128) 193.0.4.28 from 193.0.4.28 (193.0.4.28) Origin IGP, metric 0, localpref 100, valid, external, best Community: 7018:2000 12654, (aggregated by 64536 10.34.183.128), (received-only) 193.0.4.28 from 193.0.4.28 (193.0.4.28) Origin IGP, metric 0, localpref 100, valid, external route-spews#show ip bgp 195.80.239.0/24 BGP routing table entry for 195.80.239.0/24, version 32179323 Paths: (2 available, best #1) Advertised to update-groups: 1 3 4 12654, (aggregated by 64512 10.255.255.255) 193.0.4.28 from 193.0.4.28 (193.0.4.28) Origin IGP, metric 0, localpref 100, valid, external, best Community: 7018:2000 12654, (aggregated by 64512 10.255.255.255), (received-only) 193.0.4.28 from 193.0.4.28 (193.0.4.28) Origin IGP, metric 0, localpref 100, valid, external route-spews# -- Jay Borkenhagen jayb at att.com AT&T Internet Services ------ End forwarded message ------ -- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 206 bytes Desc: not available URL: <https://www.ripe.net/ripe/mail/archives/ris-int/attachments/20041008/e08180eb/attachment.sig>
[ Ris-int Archives ]