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_red
icon_orange
icon_red
icon_red
icon_red
icon_red
icon_green
icon_red
icon_red
icon_red
icon_red
icon_orange
icon_green
 

FS#4274 — FS#8211 — N5548 and QoS

Attached to Project— Network
Maintenance
Whole Network
CLOSED
100%
We are going to update all N5548 in order to better generate server limitations to 200Mbps, 300Mbps and more if the customer has bought additional bandwidth with it.

Date:  Thursday, 21 March 2013, 18:37PM
Reason for closing:  Done
Comment by OVH - Sunday, 10 March 2013, 23:16PM

5.135.134.0/24: done


Comment by OVH - Sunday, 10 March 2013, 23:16PM

178.33.238.0/24: done
178.33.236.0/24: done

178.33.63.0/24: doing


Comment by OVH - Sunday, 10 March 2013, 23:21PM

178.33.63.0/24 is not going well:
http://status.ovh.net/?do=details&id=4275


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

178.33.63.0/24: done


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

37.59.32.0/24: doing
46.105.118.0/24: doing
46.105.114.0/24: doing
46.105.112.0/24: doing
46.105.110.0/24: doing
46.105.106.0/24: doing
46.105.104.0/24: doing
178.33.234.0/24: doing
178.33.232.0/24: doing
178.33.230.0/24: doing


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

46.105.114.0/24: A down

Reason: Reset triggered due to HA policy of Reset
System version: 6.0(2)N1(1)
Service: fwm hap reset

178.33.230.0/24: A down
Reason: Reset triggered due to HA policy of Reset
System version: 6.0(2)N1(1)
Service: fwm hap reset


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

37.59.32.0/24: done
46.105.118.0/24: done
46.105.114.0/24: done
46.105.112.0/24: done
46.105.110.0/24: done
46.105.106.0/24: done
46.105.104.0/24: done
178.33.234.0/24: done
178.33.232.0/24: done
178.33.230.0/24: done


Comment by OVH - Tuesday, 12 March 2013, 17:24PM

176.31.224.0/24: doing
176.31.228.0/24: doing
176.31.230.0/24: doing
176.31.236.0/24: doing
176.31.238.0/24: doing
178.33.226.0/24: doing
178.33.228.0/24: doing
46.105.116.0/24: doing


Comment by OVH - Tuesday, 12 March 2013, 17:25PM

176.31.238.0/24: We don't start the upgrade due to a new problem:

Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes disruptive reset SFP uController needs
upgrade
100 yes disruptive reset SFP uController needs
upgrade
101 yes disruptive reset SFP uController needs
upgrade
102 yes disruptive reset SFP uController needs
upgrade
103 yes disruptive reset SFP uController needs
upgrade
104 yes disruptive reset SFP uController needs
upgrade
105 yes disruptive reset SFP uController needs
upgrade
106 yes disruptive reset SFP uController needs
upgrade
107 yes disruptive reset SFP uController needs
upgrade
108 yes disruptive reset SFP uController needs
upgrade
109 yes disruptive reset SFP uController needs
upgrade
111 yes disruptive reset SFP uController needs
upgrade


Comment by OVH - Tuesday, 12 March 2013, 17:26PM

176.31.236.0/24: A has crashed.

Reason: Reset triggered due to HA policy of Reset
System version: 6.0(2)N1(1)
Service: fwm hap reset

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


Comment by OVH - Tuesday, 12 March 2013, 18:00PM

176.31.224.0/24: A is up but FEX upgrade is not going well.

Continuing with installation process, please wait.
The login will be disabled until the installation is completed.

Performing supervisor state verification.
SUCCESS

Supervisor non-disruptive upgrade successful.

Pre-loading modules.
FAIL. Return code 0x4200000E (Image download failed on the FEX).

Remaining action::
"Module(s) 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 111 still
need to be upgraded".

Install has failed. Return code 0x40930069 (Preload of module image
failed).
Please identify the cause of the failure, and try 'install all' again.

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


Comment by OVH - Tuesday, 12 March 2013, 18:00PM

176.31.224.0/24: done
176.31.228.0/24: done
176.31.230.0/24: done
176.31.236.0/24: done
176.31.238.0/24: done
178.33.226.0/24: done
178.33.228.0/24: done
46.105.116.0/24: done


Comment by OVH - Wednesday, 13 March 2013, 01:18AM

176.31.232.0/24: doing
178.33.224.0/24: doing
46.105.108.0/24: doing
37.59.34.0/24: doing
5.39.64.0/24: doing
5.39.66.0/24: doing
5.39.68.0/24: doing
5.39.70.0/24: doing

37.59.16.0/24: doing
37.59.18.0/24: doing
37.59.20.0/24: doing
37.59.22.0/24: doing
5.135.136.0/24: to debug
5.135.138.0/24: doing
5.135.140.0/24: doing
5.135.142.0/24: doing


Comment by OVH - Wednesday, 13 March 2013, 01:18AM

198.27.74.0/24: todo
192.95.32.0/24: todo


Comment by OVH - Wednesday, 13 March 2013, 01:21AM

176.31.232.0/24: done
178.33.224.0/24: done
46.105.108.0/24: done
37.59.34.0/24: done
5.39.64.0/24: done
5.39.66.0/24: done
5.39.68.0/24: done
5.39.70.0/24: done
37.59.16.0/24: done
37.59.18.0/24: done
37.59.20.0/24: done
37.59.22.0/24: done
5.135.136.0/24: done
5.135.138.0/24: done
5.135.140.0/24: done
5.135.142.0/24: done


Comment by OVH - Thursday, 14 March 2013, 07:23AM

QoS limits internal traffic while it should not. We made the rollback of the
configuration to debug with the Cisco TAC.


Comment by OVH - Thursday, 14 March 2013, 07:23AM

178.33.241.0/24: doing


Comment by OVH - Thursday, 14 March 2013, 07:23AM

178.33.241.0/24: done