rssLink RSS for all categories
 
icon_red
icon_green
icon_red
icon_red
icon_red
icon_green
icon_green
icon_red
icon_red
icon_red
icon_orange
icon_green
icon_green
icon_green
icon_red
icon_blue
icon_red
icon_blue
icon_red
icon_red
icon_red
icon_red
icon_red
icon_red
icon_red
icon_green
icon_orange
 

FS#4275 — FS#8212 — 178.33.63.0/24

Attached to Project— Network
Incident
the whole network
CLOSED
100%
The update of this couple N5 178.33.63.0/24 has crashed:

http://status.ovh.net/?do=details&id=4274

The A switch has been updated but without updating the FEX. We are going to update the B switch at midnight, which will provoke a service cutoff for 20 minutes,
due to the FEX update at start.

Date:  Monday, 11 March 2013, 13:56PM
Reason for closing:  Done
Comment by OVH - Monday, 11 March 2013, 07:18AM

We are going to finish the update. The massacre will start :(


Comment by OVH - Monday, 11 March 2013, 13:54PM

Everything is going well. It looks like in 6.X.X de NX-OS version, the B (slave) can update FEX instantly. Once the right version is up, A recognises FEX and mount it. Basically, a nice surprise: no breakdown.

We are finishing the last PEX.


Comment by OVH - Monday, 11 March 2013, 13:55PM

Wow. Everything went well. No packet lost. It's very pleasant. Usually after N5 updates, it feels like a lost boxing competition: in pain and willing to hang oneself. It's very pleasant to finish it in a positive atmosphere.