OVHcloud Network Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
FS#8183 — rbx-g2-a9
Scheduled Maintenance Report for Network & Infrastructure
Completed
The update of rbx-g1-a9 was successfully completed yesterday (task # 8168 http://status.ovh.co.uk/?do=details&id=4224), we will update the second ASR of roubaix: rbx-g2-a9.

We will install the same SMUs as on rbx-g1-a9.

We will start the maintenance at 11:00pm (CET).
We plan to isolate the network router once SMUs \"Hit\" installed.

Update(s):

Date: 2013-03-06 00:57:27 UTC
All SMUs were installed on rbx-g2-a9.

We will reset the traffic on the router.

Date: 2013-03-06 00:56:30 UTC
Done.

We are rebooting line cards 5,6 and 7.

Date: 2013-03-06 00:56:00 UTC
Done.

We are performing now the fpd updates.
We will restart some line card,so this update can take effect.

Date: 2013-03-06 00:53:33 UTC
The last reboot was performed.

We are installing the last wave of SUMs hitless:
disk0:asr9k-px-4.2.1.CSCua23419-1.0.0
disk0:asr9k-px-4.2.1.CSCud40419-1.0.0
disk0:asr9k-px-4.2.1.CSCua69216-1.0.0
disk0:asr9k-px-4.2.1.CSCuc32974-1.0.0
disk0:asr9k-px-4.2.1.CSCud90009-1.0.0

Date: 2013-03-06 00:53:02 UTC
Done.

4th wave of SMUs installations. This also requires a reboot :

disk0:asr9k-px-4.2.1.CSCua37747-1.0.0
disk0:asr9k-px-4.2.1.CSCub25750-1.0.0
disk0:asr9k-px-4.2.1.CSCuc53449-1.0.0
disk0:asr9k-px-4.2.1.CSCua79711-1.0.0
disk0:asr9k-px-4.2.1.CSCub11774-1.0.0
disk0:asr9k-px-4.2.1.CSCub11995-1.0.0
disk0:asr9k-px-4.2.1.CSCub67882-1.0.0
disk0:asr9k-px-4.2.1.CSCuc06881-1.0.0
disk0:asr9k-px-4.2.1.CSCub46482-1.0.0
disk0:asr9k-px-4.2.1.CSCuc62781-1.0.0
disk0:asr9k-px-4.2.1.CSCua89206-1.0.0
disk0:asr9k-px-4.2.1.CSCua61015-1.0.0
disk0:asr9k-px-4.2.1.CSCud28144-1.0.0
disk0:asr9k-px-4.2.1.CSCuc09304-1.0.0
disk0:asr9k-px-4.2.1.CSCua87017-1.0.0
disk0:asr9k-px-4.2.1.CSCua63901-1.0.0

Date: 2013-03-06 00:52:06 UTC
The router is now isolated from the network.

We will install the third wave of SMUs, the router needs to be reloaded:

disk0:asr9k-px-4.2.1.CSCtz62914-1.0.0
disk0:asr9k-px-4.2.1.CSCtz72477-1.0.0
disk0:asr9k-px-4.2.1.CSCtz89449-1.0.0
disk0:asr9k-px-4.2.1.CSCua47910-1.0.0
disk0:asr9k-px-4.2.1.CSCub11591-1.0.0
disk0:asr9k-px-4.2.1.CSCuc14747-1.0.0
disk0:asr9k-px-4.2.1.CSCuc37536-1.0.0
disk0:asr9k-px-4.2.1.CSCty84643-1.0.0
disk0:asr9k-px-4.2.1.CSCty99591-1.0.0
disk0:asr9k-px-4.2.1.CSCua09897-1.0.0
disk0:asr9k-px-4.2.1.CSCua14945-1.0.0
disk0:asr9k-px-4.2.1.CSCua16764-1.0.0
disk0:asr9k-px-4.2.1.CSCua76130-1.0.0
disk0:asr9k-px-4.2.1.CSCub42561-1.0.0


Date: 2013-03-06 00:49:43 UTC
done.

We started isolating rbx-g2-a9.

All traffic will flow through rbx-g1-a9 during the update.

Date: 2013-03-06 00:49:37 UTC
We moved to the second SMUs update wave:

disk0:asr9k-px-4.2.1.CSCub30075-1.0.0
disk0:asr9k-px-4.2.1.CSCub35029-1.0.0
disk0:asr9k-px-4.2.1.CSCub68512-1.0.0
disk0:asr9k-px-4.2.1.CSCub76221-1.0.0
disk0:asr9k-px-4.2.1.CSCub96985-1.0.0
disk0:asr9k-px-4.2.1.CSCub98258-1.0.0
disk0:asr9k-px-4.2.1.CSCuc14280-1.0.0
disk0:asr9k-px-4.2.1.CSCuc24002-1.0.0
disk0:asr9k-px-4.2.1.CSCuc32799-1.0.0
disk0:asr9k-px-4.2.1.CSCuc35303-1.0.0
disk0:asr9k-px-4.2.1.CSCuc35670-1.0.0
disk0:asr9k-px-4.2.1.CSCuc95853-1.0.0

Date: 2013-03-06 00:49:02 UTC
done

Date: 2013-03-06 00:48:56 UTC
We started with the first SMUs wave :

disk0:asr9k-px-4.2.1.CSCty18600-1.0.0
disk0:asr9k-px-4.2.1.CSCty36337-1.0.0
disk0:asr9k-px-4.2.1.CSCty83866-1.0.0
disk0:asr9k-px-4.2.1.CSCtz63248-1.0.0
disk0:asr9k-px-4.2.1.CSCua04907-1.0.0
disk0:asr9k-px-4.2.1.CSCua28899-1.0.0
disk0:asr9k-px-4.2.1.CSCua31485-1.0.0
disk0:asr9k-px-4.2.1.CSCua71542-1.0.0
disk0:asr9k-px-4.2.1.CSCua74062-1.0.0
disk0:asr9k-px-4.2.1.CSCua79562-1.0.0
disk0:asr9k-px-4.2.1.CSCub09558-1.0.0
disk0:asr9k-px-4.2.1.CSCub22596-1.0.0
disk0:asr9k-px-4.2.1.CSCub27892-1.0.0
disk0:asr9k-px-4.2.1.CSCub29765-1.0.0

These SMUs are hitless,this has no impact on traffic.
Posted Mar 06, 2013 - 00:47 UTC