[ris-int] Re: [NCC#2004119411: Peering SURFnet - RIPE werkt niet (ARS S9757) (fwd)]
Arife Vural arife at ripe.net
Mon Nov 29 13:19:30 CET 2004
Hi Peter, It looks I missed Anchor prefix, 195.80.239.0/24. We are announcing this prefix continously. That means you should get at least one prefix from us, and that would be 2 when we start to announce normal Beacon prefix. Please, let us know if you still get no prefix from us. Regards. Arife > It's what we expect on RRC00. We do announce and withdrawal Beacon prefix > in fixed time intervals. Because of that you can not get the prefixes from > us (AS12654) continously. > > You can get the time schedule of Beacon prefixes in the following link: > > http://www.ripe.net/projects/ris/docs/beaconlist.html > > Regards. > Arife > > ---------- Forwarded message ---------- > Date: Thu, 25 Nov 2004 18:56:29 +0100 > From: Peter Blondel <blondel at sara.nl> > Reply-To: nic at sara.nl > To: "Henk Uijterwaal (RIPE-NCC)" <henk at ripe.net> > Cc: nic at sara.nl > Subject: Peering SURFnet - RIPE werkt niet (ARS S9757) > > Hallo Henk, > > Ik zag net 'toevallig' dat we geen prefixen binnen krijgen op jullie > peering met de BR2.Amsterdam1 sinds vanmorgen: > 193.0.4.28 4 12654 33 204375 2255254 0 0 08:39:31 0 > > -- uit de logging: > Nov 24 23:49:54.962 UTC: %BGP-5-ADJCHANGE: neighbor 193.0.4.28 > Down Peer closed the session > Nov 25 08:43:08.210 UTC: %BGP-5-ADJCHANGE: neighbor 193.0.4.28 Up > > en resetten vanaf onze kant helpt niet. Hebben jullie iets veranderd ? > > met vriendelijke groeten > Peter Blondel > SARA NCC > > ----- End forwarded message -----
[ Ris-int Archives ]