Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
Install has failed. Return code 0x40930039 (aborting due to failed upgrade).
Please identify the cause of the failure, and try 'install all' again.
Update(s):
Date: 2013-02-11 00:34:38 UTC All OK. the new spare is compatible with the A and B.
We believe that the first spare had a malfunction of
the update procedure then was unable to start it. we'll check tomorrow.
All UP.
We do apologize for the breakdown.
Date: 2013-02-11 00:22:03 UTC Its UP on A. we are cutting the B uplink.
Date: 2013-02-11 00:21:33 UTC All servers are UP on the B uplink.
we are going to connect the A uplink
Date: 2013-02-11 00:20:44 UTC We have replaced the spare with another one
and remains the same, we are unable to remount the service.
We have cut the A upkink, the same
we have cut the B uplink, it's better,
the FEX is being detected by the system.
We are reconnecting to all EG servers which are on 107
on the new spare with only the B uplink. We are resetting the service
then we'll check why the A uplink is causing this problem.
Date: 2013-02-11 00:16:17 UTC Thereafter the replacement, the uplinks
are again up and the FEX is updated.
The old one is therefore dead. we are counting
8 minutes of software update and 3 minutes extra to boot.
Date: 2013-02-11 00:14:08 UTC We are replacing the FEX with a spare.
Date: 2013-02-11 00:13:36 UTC The FEX 107 is probably dead. We are rebooting it
in hard, meanwhile we are preparing the spare.
Date: 2013-02-11 00:12:17 UTC 02/10/2013 23:44:49.312663: Module register received
02/10/2013 23:44:49.313470: Image Version Mismatch
02/10/2013 23:44:49.313679: Registration response sent
02/10/2013 23:44:49.313858: Requesting satellite to download image
02/10/2013 23:50:18.23809: Image preload successful.
02/10/2013 23:50:19.149814: Deleting route to FEX
02/10/2013 23:50:19.156902: Module disconnected
02/10/2013 23:50:19.157457: Module Offline
02/10/2013 23:50:19.160406: Deleting route to FEX
02/10/2013 23:50:19.169426: Module disconnected
02/10/2013 23:50:19.170815: Offlining Module
02/10/2013 23:50:19.187956: Deleting route to FEX
02/10/2013 23:50:19.197621: Module disconnected
02/10/2013 23:50:19.199081: Offlining Module
02/10/2013 23:54:49.345669: Module timed out
Date: 2013-02-11 00:12:08 UTC 1 more
Date: 2013-02-11 00:12:00 UTC 2 more FEX
Date: 2013-02-11 00:11:44 UTC Still 3 FEX are down.
Date: 2013-02-11 00:11:20 UTC Okay, we have tried to do our best but it got worse.
We will do the old action which will generate
a 15 minutes breakdown starting from now.
the A is UP and is updating the FEX all from the beginning.
Date: 2013-02-11 00:08:27 UTC We are retrying the VPC action
Date: 2013-02-11 00:06:29 UTC We have reversed the role of the VPC
to switch primary to secondary and secondary to primary.
This has caused a cutoff in the service.
We believe that this allows us to decrease
the breakdown time due to to the FEX update.