OVHcloud Network Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
FS#7574 — Internal routing
Scheduled Maintenance Report for Network & Infrastructure
Completed
We are going to change the settings of our internal routing in RBX between all datacenters and routers.

The aim is for the servers to communicate more directly between then if they are in different datacentres. The same way as for the access to NAS and backup.

Update(s):

Date: 2012-11-07 17:00:56 UTC
vss-2/2b-6k: done
vss-3/3b/4-6k: done
vss-5a/b-6k: done
vss-6a/b-6k: done
vss-7a/b-6k: done
vss-8a/b-6k: done
vss-9a/b-6k: done
rbx-s14/s15-6k: done


Date: 2012-11-06 11:39:00 UTC
The consequence:

The traffic for all servers of all DC in RBX
to the servers managed by vss-1/1b and rbx-s3/s4
passes directly instead of going out on
the backbone and then come back.
exchanges will therefore be more rapid
and with less latency.

The least is that we lose netflow
visibility netflow and therefore
the detection of scans and attacks
on the internal network. This problem
should be solved in a few weeks with
a new release of NX-OS for rbx-97-n7
which will enable the netflow on F2
maps (which we have implemented 6 months ago).
We will shortly be able to activate it and
then see if the netflow on F2 is sufficient
to detect scans / attacks or it is necessary
to change F2 cards to new M2 that so the
netflow 'better'.









Date: 2012-11-06 11:22:08 UTC
We have moved prefixes
of rbx-s3/s4 in the new
zone. And the vss-1/1b
prefixes as well.

which means:
178.33.60.0/24
178.33.61.0/24
178.33.62.0/24
188.165.12.0/24
188.165.13.0/24
188.165.14.0/24
188.165.15.0/24
94.23.0.0/24
94.23.1.0/24
94.23.2.0/24
94.23.3.0/24
94.23.4.0/24
94.23.5.0/24
94.23.6.0/24
94.23.7.0/24
94.23.8.0/24
94.23.9.0/24
94.23.10.0/24
94.23.11.0/24
94.23.12.0/24
94.23.13.0/24
94.23.14.0/24
94.23.15.0/24
94.23.16.0/24
94.23.17.0/24
94.23.18.0/24
94.23.19.0/24
94.23.20.0/24
94.23.21.0/24
94.23.22.0/24
94.23.23.0/24
94.23.24.0/24
94.23.25.0/24
94.23.26.0/24
94.23.27.0/24
94.23.28.0/24
94.23.29.0/24
94.23.30.0/24
94.23.31.0/24
94.23.32.0/24
94.23.33.0/24
94.23.34.0/24
94.23.35.0/24
94.23.36.0/24
94.23.37.0/24
94.23.38.0/24
94.23.39.0/24
94.23.40.0/24
94.23.41.0/24
94.23.42.0/24
94.23.43.0/24
94.23.44.0/24
94.23.45.0/24
94.23.46.0/24
94.23.47.0/24
94.23.48.0/24
94.23.49.0/24
94.23.50.0/24
94.23.51.0/24
94.23.52.0/24
94.23.53.0/24
94.23.54.0/24
94.23.55.0/24
94.23.56.0/24
94.23.57.0/24

Date: 2012-11-06 10:08:20 UTC
The 1st phase is completed.

We are going to make the internal routing direct via rbx-97-n7.

Date: 2012-11-06 10:06:48 UTC
We are finishing all direct connections between ASR and rbx-97-n7.

g1 / rbx-97: doing

done

g2 / rbx-97: doing

done

Date: 2012-11-06 10:06:03 UTC
Done.

We wait 2-3 minutes for all OSPF sessions to mount.

Date: 2012-11-06 10:05:28 UTC
We are now changing the area of all routers B in all datacenters of RBX.

Date: 2012-11-06 10:04:53 UTC
Done.

We are changing all services area (NAS, backup, etc...).

Done.

Date: 2012-11-06 10:03:33 UTC
All A routers are in the new area.

We are now changing the rbx-97-n7 area.

Date: 2012-11-06 10:02:52 UTC
Work in progress

Date: 2012-11-06 10:02:25 UTC
Before changing the weights in the routing, we are going to change the setting of the internal routing zone to create a new zone.

Some perturbations are expected for a few minutes, the time to synchronise OSPF in a new area.
Posted Nov 06, 2012 - 09:59 UTC