RSS for all categories
FS#403 — FS#4481 — bru-1-6k: 10G migration
Attached to Project— Network
| Maintenance | |
| Whole Network | |
| CLOSED | |
 |
The router bru-1-6k (Brussels) is connected on two routers
through 2 10G links. We will reconnect one of the 10G
to switch on rbx-97-99 instead of rbx-99.
Date: Sunday, 29 August 2010, 14:53PMthrough 2 10G links. We will reconnect one of the 10G
to switch on rbx-97-99 instead of rbx-99.
Reason for closing: Beta version
The migration is completed.
We had an interruption due to the configuration of the BGP
on the router rbx-97. It has been fixed.
The access to 217.136.92.241 is not for chtix customers
in Brussels.
It is due to the fact that belgacom announce 217.136.64.0/19 AS5432
behind AS6774 (in International) and on the peering with
AS5432 we see 217.136.0.0/16. The rbx-97 only knows
Brussels routes. So it loops.
bru-1-6k#sh ip route 217.136.92.241
Routing entry for 217.136.64.0/19, supernet
Known via "bgp 16276", distance 200, metric 0
Tag 6774, type internal
Last update from 213.186.32.202 01:46:53 ago
Routing Descriptor Blocks:
* 213.186.32.202, from 213.251.130.92, 01:46:53 ago
Route metric is 0, traffic share count is 1
AS Hops 2
Route tag 6774
Then
bru-1-6k#sh ip route 217.136.92.241
Routing entry for 217.136.0.0/16, supernet
Known via "bgp 16276", distance 20, metric 0
Tag 5432, type external
Last update from 194.53.172.63 00:16:52 ago
Routing Descriptor Blocks:
* 194.53.172.81, from 194.53.172.81, 1w3d ago
Route metric is 0, traffic share count is 1
AS Hops 1
Route tag 5432
194.53.172.63, from 194.53.172.63, 00:16:52 ago
Route metric is 0, traffic share count is 1
AS Hops 1
Route tag 5432
We will change the configuration between bru-1 and rbx1-97
to avoid making the L3 to rbx-97 and then down
BGP on this router.
done.