On Sun, 26 Oct 1997, Lyamin Alex wrote:
> Hi Gents,
>
> Recently.. Somewhere in Cityline...
>
> HQ-1#sh ip bgp 195.210.128.0
> BGP routing table entry for 195.210.128.0/18, version 348782
> Paths: (1 available, best #1)
> 2854 6731, (aggregated by 6731 195.210.128.130)
> 193.232.90.94 from 193.232.90.94 (194.84.128.17)
> Origin IGP, valid, external, atomic-aggregate, best
We are announcing all =RUSSIAN-PEERS= group of routes at M9. Are you shure
that you are not getting that route from us? Or what is the problem?
Please describe in details.
>
> Could it be fixed?
> Also..
>
> Network Next Hop Metric LocPrf Weight Path
> *> 0.0.0.0 195.16.99.37 0 8263 ?
> *> 62.0.0.0 195.16.99.37 0 8263 i
Also seems to be strange - we are announcing default route corse of lack
of full table to you. 62.64.0.0/19 is our block - you urgently need to
turn on classless routing. And you also must recieve 195.16.96.0/19
aggregate from us. Seems that it is some problems at your side - anyway we
will perform a check.
> First is useless, second is Mystery (should we turn on classles ip routing?;)...
classless routing is now requed parameter to get a full table from your
uplink provider on the internet. I don't know rules of bgp4 peering at
concert and teleglobe, but at sprintlink CLASSLESS _MUST_ be turned on.
Your configuration now can couse some problems in routing for your
network.
>
>
> --
> Lyamin Alex
>
Best regards,
Victor L. Belov @ Teleport-TP NOC
scream@portal.ru
+7 095 234 7000 Ext #13
