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#362 — FS#4439 — Maintenance infra network- 06/08/10

Attached to Project— Hosting
Maintenance
all (Plan hostings)
CLOSED
100%
We are launching a maintenance on the shared infra network on 06/08 at 01:00 CEST (estimated duration: around 1h). The shared hosting's plate-form would be unavailable during a maintenance of few minutes (around 4 to 5 min).

Date:  Wednesday, 22 December 2010, 11:24AM
Reason for closing:  Done
Comment by OVH - Sunday, 08 August 2010, 00:48AM

we are starting the task. Switches p19-61/62 and p19-65/66 are going to restart successively to be updated.


Comment by OVH - Sunday, 08 August 2010, 00:56AM

thereafter a cisco bug blocking the upgrade ( Inconsistent error message comparing to the available place on the bootflash), we restarted p19-65 (on the same version). After this reboot, 7 ports among one of the fex is set to error. A fex spare 2248 is ready to start on this couple of chassis. We have to finish the upgrade of the peer in order to upload it (2248 is not supported but in the latest version of nx-os).

error message:
Version Compatibility check failed. Return code 0x40930062 (free space in the filesystem is below threshold).


Comment by OVH - Sunday, 08 August 2010, 00:59AM

Reload on the same version p19-66 because of a bug in progress. We could then start the upgrade itself.


Comment by OVH - Sunday, 08 August 2010, 01:00AM

Upgrading p19-65 in progress.


Comment by OVH - Sunday, 08 August 2010, 01:01AM

Correction, p19-66 is upgraded. We are reloading the fex on this chassis.


Comment by OVH - Sunday, 08 August 2010, 01:02AM

Upgrading p19-65 is now in progress.


Comment by OVH - Sunday, 08 August 2010, 01:12AM

The couple p19-65/66 is actually updated but the fexs passed off-line after rebooting p19-65 on the latest version and reactivation of ports-channels.
At this moment, for an unknown reason, fex's port configuration was reinitialised at part of p19-65 which is provoking a mismatch between the configuration of the 2 chassis. Even by disconnecting the uplinks of the fexs at part of p19-65, ports are not remounted on p19-66. We decreased the configuration of all fex ports on p19-65 and ports are remounted.
We must review the migration protocol for p19-61/62 which contains 6 fexs. We are reporting then, the upgrades on these switches to a later date.

We are facing difficulties to remount fex 2248.


Comment by OVH - Sunday, 08 August 2010, 01:14AM

We resolved the uplinks problems on 2248 but the fex is not mounting:

p19-66-n5# 2010 Aug 6 03:21:54 p19-66-n5 %$ VDC-1 %$ %VMM-2-VMM_SERVICE_ERR: VDC1: Service SAP 175 returned error 0x40290000 (err
or) in if_bind sequence


Comment by OVH - Sunday, 08 August 2010, 01:16AM

We tried with the 2nd fex 2248, the same.

However, after checking, problems were prior to these ports and the machines have already been moved to other ports of the same fex. This will give us time to solve the problem on the fex 2248.


Comment by OVH - Sunday, 08 August 2010, 01:18AM

End of maintenance for tonight. we are planning ASAP a new nightly intervention for p19-61/62.