AV
Скорее всего это не про Владивосток, а про то, чтобы обеспечить интернетом сервер. Владивосток и Питер это как точки, которые подключатся к магистралям. Ну а 100 гбит - чтобы не переделывать, когда на Чукотке сделает свой DC яндекс и dtln.
Problem
A slow peer is a peer that cannot keep up with the rate at which the router generates BGP update messages over a prolonged period of time (in the order of minutes) in an update group. The reason for this can be persistent network issues. The network reasons could be packet loss and/or loaded links, or throughput issues with the BGP sessions. Also, a BGP peer might be heavily loaded in terms of CPU and cannot service the TCP connection at the required speed.
Slow peers affect the BGP convergence of the complete update group. If one BGP peer is slow, it causes the entire update group to slow down. The result is that the other update group members will have slower convergence as well. For this reason, the issue should be resolved.
You can identify the slow peer and move it out of the update group. In order to complete this task, you can change the outbound policy for that BGP peer; however, this is a manual task. You must first identify the peer that is slow, and then move it out of the update group. The slow peer feature can do this automatically, so that no user intervention is required.
