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

FS#4235 — FS#8167 — switch ports on the networks 176.31.224-238

Attached to Project— Dedicated servers
Modernization
RBX4
CLOSED
100%
We are updating the ports' setting of the network switches 176.31.224-238.
The intervention will start from 10:00am and 12:00pm on 05/03/2013.
A ping loss of about a second is expected for servers belonging to these networks.


Date:  Friday, 15 March 2013, 18:36PM
Reason for closing:  Done
Comment by OVH - Wednesday, 06 March 2013, 07:13AM

The intervention started.


Comment by OVH - Wednesday, 06 March 2013, 07:14AM

The intervention is done for these networks 176.31.224, 176.31.226, 176.31.228-230, 176.31.232, 176.31.234, 176.31.236, 176.31.238
Remaining these networks 176.31.225, 176.31.227, 176.31.231, 176.31.233, 176.31.235, 176.31.237


Comment by OVH - Thursday, 07 March 2013, 06:42AM

We will update again switches port configuration on the networks 176.31.224-238.
In order to minimize the load on the network equipment, we will limit the maximum number of mac transiting a virtual rack to 20.
Please contact us if this limit is not high enough for your infrastructure.
We will start on 07/03 at 10am by 176.31.224 and 176.31.225 networks.


Comment by OVH - Thursday, 07 March 2013, 11:42AM

The intervention starts on networks 176.31.224 and 176.31.225.


Comment by OVH - Thursday, 07 March 2013, 11:44AM

It is completed for networks 176.31.224 and 176.31.225.
We move to networks 176.31.226, 176.31.228 and 176.31.230.


Comment by OVH - Thursday, 07 March 2013, 12:18PM

176.31.226, 176.31.228 and 176.31.230 terminated.
We move to 176.31.232, 176.31.234, 176.31.236.


Comment by OVH - Thursday, 07 March 2013, 15:14PM

176.31.232, 176.31.234, 176.31.236 completed.
We move to 176.31.227, 176.31.229, 176.31.231, 176.31.233, 176.31.235 and 176.31.237


Comment by OVH - Thursday, 07 March 2013, 15:14PM

176.31.227, 176.31.229, 176.31.231, 176.31.233, 176.31.235 and 176.31.237 completed.
We complete the intervention with 176.31.238 and 176.31.239.


Comment by OVH - Thursday, 07 March 2013, 15:14PM

The intervention is completed.


Comment by OVH - Thursday, 07 March 2013, 17:00PM

We notice problems on the networks 176.31.224 and 176.31.225 after the intervention. We are investigating.


Comment by OVH - Thursday, 07 March 2013, 20:45PM

The problems were solved, the situation is back to normal


Comment by OVH - Friday, 15 March 2013, 10:33AM

We will board networks 176.31.224-238 tomorrow morning from 10am.
Again, 1 second ping loss on the machines of this network.


Comment by OVH - Friday, 15 March 2013, 10:33AM

The intervention start on these networks:
176.31.224
176.31.226
176.31.228
176.31.230


Comment by OVH - Friday, 15 March 2013, 18:33PM

176.31.224 done
176.31.226 done
176.31.228 done
176.31.230 done


Comment by OVH - Friday, 15 March 2013, 18:33PM

176.31.225 doing
176.31.227 doing
176.31.229 doing
176.31.231 doing


Comment by OVH - Friday, 15 March 2013, 18:34PM

176.31.225 done
176.31.227 done
176.31.229 done
176.31.231 done
---------------
176.31.232 doing
176.31.234 doing
176.31.236 doing
176.31.238 doing


Comment by OVH - Friday, 15 March 2013, 18:35PM

176.31.232 done
176.31.234 done
176.31.236 done
176.31.238 done
---------------
176.31.233 doing
176.31.235 doing
176.31.237 doing
176.31.239 doing


Comment by OVH - Friday, 15 March 2013, 18:35PM

176.31.233 done
176.31.235 done
176.31.237 done
176.31.239 done