This is the follow-up of last Friday's incident, by RIPE NCC.
In my opinion, RIPE NCC did a good job in this incident. They identified and stopped the problem within 30 minutes!
The problem would be easier to be identified if it caused disconnection on direct peers immediately. However, in this incident, only some and indirect BGP routers kept reseting peers. If they did not deploy Remote Route Collector (RRC) to monitor BGP at remote Internet Exchanges (IX) sites, I believe it would cost us much more time to know this is not day-to-day general BGP incident.
The report itself provides us so many information to be dug further. I need more time to digest!
[Original Post]
RIPE NCC and Duke University BGP Experiment — RIPE Labs
---
Command lines to setup IP address and DNS of Windows PC
-
When I use my Windows notebook as connectivity tester, I often have to
switch the IP address configuration from DHCP to some fixed IP, and back
and forth. ...
7 months ago
0 comments:
Post a Comment