rssLink RSS dla wszystkich kategorii
 
icon_orange
icon_red
icon_red
icon_blue
icon_blue
icon_blue
icon_green
icon_red
icon_blue
icon_blue
icon_blue
icon_blue
icon_blue
icon_blue
icon_blue
icon_blue
icon_red
icon_blue
icon_orange
icon_red
icon_blue
icon_blue
icon_blue
icon_blue
icon_green
icon_blue
icon_blue
 

FS#28476 — RBX VAC

Przydzielony do projektu— Anty-DDoS
Modernizacja
Backend / Core
ZAMKNIĘTE
100%
The new VAC in RBX is ready. This new version, based on our vRouters
& FPGA solutions and 100G links, provides higher capacity and better
mitigation functionalities, as we have better control over both the
hardware and software.

We will start moving traffic from the previous VAC (vac1-*-a9/n7) to
the new one (rbx-vac1-a75).

This page will be updated along the way, as we enable the new VAC for
IP ranges.
Data:  czwartek, 20 kwiecień 2017, 09:21
Powód zamknięcia:  Done
Komentarz od OVH - środa, 08 marzec 2017, 10:16

We are starting to move firewall and permanent mitigation traffic for IPs in range 192.99.0.0/24.


Komentarz od OVH - środa, 08 marzec 2017, 11:04

We are suspending this operation for now and rolled back, as we're seeing routing issues for IPs under antiphishing.


Komentarz od OVH - środa, 08 marzec 2017, 11:54

The routing issue is fixed, we are resuming the operation.


Komentarz od OVH - czwartek, 09 marzec 2017, 10:02

We start moving some more traffic, for IPs in 192.99.0.0/16.


Komentarz od OVH - czwartek, 09 marzec 2017, 10:21

We rollbacked for now as we're seeing that some firewall rules are
not properly blocking traffic.


Komentarz od OVH - poniedziałek, 13 marzec 2017, 08:04

10.03.2017, 19:06PM
The issue is fixed, we will resume traffic switchover on Monday.


Komentarz od OVH - poniedziałek, 13 marzec 2017, 09:21

Firewall and permanent mitigation traffic is now going through rbx-vac1-a75 for IPs in range 192.99.0.0/19.


Komentarz od OVH - poniedziałek, 13 marzec 2017, 12:19

Extended to 192.99.0.0/17.


Komentarz od OVH - wtorek, 14 marzec 2017, 08:19

We are isolating rbx-vac1-a75 to update it to the latest version, to
see if it fixes an issue we're seeing where OSPF neighbors on uplinks
don't come back up automatically.


Komentarz od OVH - wtorek, 14 marzec 2017, 08:34

It seems to have fixed the issue. We're putting back traffic.


Komentarz od OVH - wtorek, 14 marzec 2017, 09:13

Extended to 192.99.0.0/16.


Komentarz od OVH - wtorek, 14 marzec 2017, 10:18

Added 167.114.0.0/16.


Komentarz od OVH - wtorek, 14 marzec 2017, 12:06

Added 158.69.0.0/16.


Komentarz od OVH - wtorek, 14 marzec 2017, 12:52

Added 144.217.0.0/16.


Komentarz od OVH - środa, 15 marzec 2017, 08:44

Adding 51.254.0.0/15.


Komentarz od OVH - środa, 15 marzec 2017, 09:40

Adding 149.202.0.0/16.


Komentarz od OVH - środa, 15 marzec 2017, 10:30

Adding 37.187.0.0/16.


Komentarz od OVH - środa, 15 marzec 2017, 11:09

Adding 151.80.0.0/16.


Komentarz od OVH - czwartek, 16 marzec 2017, 08:38

16.03.2017, 07:58AM
We will now move the rest of the firewall and permanent mitigation traffic to rbx-vac1-a75.


Komentarz od OVH - czwartek, 16 marzec 2017, 10:23

All firewall and permanent mitigation traffic in RBX is now going through rbx-vac1-a75.
Next week we will start moving the traffic of IPs under forced mitigation.


Komentarz od OVH - wtorek, 21 marzec 2017, 11:33

We are starting to move 'forced mitigation' traffic to rbx-vac1-a75.


Komentarz od OVH - wtorek, 21 marzec 2017, 11:54

Moved forced mitigation traffic for 167.114.0.0/16


Komentarz od OVH - wtorek, 21 marzec 2017, 15:47

Adding 158.69.0.0/16


Komentarz od OVH - środa, 22 marzec 2017, 08:16

21.03.2017, 18:08PM
We have observed an issue on the FPGA in Armor. We have moved the traffic back to vac1-0(b)-a9 while we investigate.


Komentarz od OVH - środa, 29 marzec 2017, 07:58

28.03.2017, 17:41PM
We've identified and fixed the issue in the FPGA's design, which was causing random pipeline stalls depending on the type and rate of traffic.
We're doing the final tests before moving forced mitigation traffic back to rbx-vac1-a75.


Komentarz od OVH - środa, 29 marzec 2017, 12:28

We will now move some forced mitigation traffic to rbx-vac1-a75, starting with this range : 167.114.0.0/16.


Komentarz od OVH - czwartek, 30 marzec 2017, 12:22

Added 158.69.0.0/16


Komentarz od OVH - czwartek, 30 marzec 2017, 12:40

Adding 37.187.0.0/18 and 192.99.0.0/16.


Komentarz od OVH - piątek, 31 marzec 2017, 10:18

Added 37.187.0.0/16 and 149.56.0.0/16


Komentarz od OVH - wtorek, 04 kwiecień 2017, 10:18

New FPGA issue encountered last night. Moving back traffic to vac1-0(b)-a9 until fixed.


Komentarz od OVH - piątek, 07 kwiecień 2017, 10:02

Putting back previous configured /16 networks


Komentarz od OVH - czwartek, 13 kwiecień 2017, 08:13

12.04.2017, 17:41PM
We have observed some issues on Armor FPGA. We are moving the forced mitigation traffic back to vac1-0(b)-a9 for now. We captured a lot of metrics and information on the issue that will help us track the bug.


Komentarz od OVH - piątek, 14 kwiecień 2017, 11:19

The latest issues on the FPGA, related to specific http packets, are now fixed.
We are resuming the traffic migration, starting with the previously migrated ranges:
167.114.0.0/16
158.69.0.0/16
192.99.0.0/16
149.56.0.0/16
37.187.0.0/16


Komentarz od OVH - środa, 19 kwiecień 2017, 08:37

18.04.2017, 10:41AM

Added 5.135.0.0/16 and 5.196.0.0/16

18.04.2017, 14:59PM

Added 144.217.0.0/16


Komentarz od OVH - środa, 19 kwiecień 2017, 10:27

Added:
- 178.32.0.0/15
- 92.222.0.0/16
- 151.80.0.0/16


Komentarz od OVH - czwartek, 20 kwiecień 2017, 09:18

20.04.2017, 08:51AM

We are now moving the rest of the traffic to rbx-vac1-a75.