FS#1902 — FS#5879 — VPS: Switching the infrastructure
Attached to Project— VPS
Maintenance | |
Infrastructure | |
CLOSED | |
![]() |
We will implement new N5548 to replace N5010.Then, we will switch the FEX of the rack on the new N5. During this time, traffic will switch to the other side.
Before that, we have to change the configuration of routers.
Date: Wednesday, 19 October 2011, 12:11PMBefore that, we have to change the configuration of routers.
Reason for closing: Done
We will cut the traffic on rbx-s9-6k
Traffic is now on rbx-s10 only.We will change the configuration and connect properly the new vps-2a/b and its satellite vss-20/21.
The 2a/b are ready,the manipulation will be done tomorrow.
We restart the upgrade from the A side.
vps-10-n5 vers vps-20-n5
The A side is cut on the vps-10-n5.We disconnect on the vps-20-n5
A host is not correctly connected on the B side.
The A side is connected on the vps-20-n5
We attack the B side ie we upgrade FEX of vps-11-n5 on vps-21-n5.
We cut the B port on host
We have forgotten to reconfigure the router.Fixed
Everything is cut on the B side.Every thing work on the A side.
We have finalised the B side,it will take roughly 2h.
We switch on the B side.
The B side is up. We have finalized the setting of 4x10G
per rack.
We switch the routing configuration on the rbx-s10-6k.
So we will cut traffic on the s10. It's going to work
on the s9. Then we change the configuration.
The B side is up. We have finalized the setting of 4x10G
per rack.
We switch the routing configuration on the rbx-s10-6k.
So we will cut traffic on the s10. It's going to work
on the s9. Then we change the configuration.
The traffic is cut on the s10.Everything is routed by the s9.
We are doing the configuration change.
We have just cut the old infrastructure.
The configuration of side B was modified. the router was re-put
on the routing. Both of the routers are active
both of the A and B infra are active.
End of the maintenance.
During the maintenance (since 1 day), we lost
14 packets
--- 46.105.24.104 ping statistics ---
91579 packets transmitted, 91565 received, 0% packet loss, time 91895190ms
Except for the case of host which was poorly redundant:
--- 46.105.7.106 ping statistics ---
91681 packets transmitted, 90207 received, +2 errors, 1% packet loss, time 91993321ms
24 minutes of crashes. it is a VPS client who took the
99.9% offer and did not (yet) switched on the HA offers
ensuring 99.99% for a little extra money.