Bottom line:
Assured Firmware Deployment logic was upgraded. The firmware deployment was started again and continues. The results will be visible in operations reports every 6 hours.
Detail:
Added an additional step to the assured deployment process.
Each step is triggered by messages from a candidate device:
1. send a poll to retrieve firmware hash
2. once the poll result is retrieved, save firmware version and hash
3. ** send diagnostic to device to retrieve diagnostic firmware info
4. once the info is complete, determine if the firmware should be updated
** based on supervisor firmware version, firmware date time vs expected, etc
4a. if it needs to be updated, send the firmware update command
4b. if not, assured deployment for the device is completed
6. confirm the firmware update was applied from data packets
7. go back to step one to assure correct deployment, expect exit at step 4b
We re-issued the assured deployment command:
assurefwdeploy -partner:22 -snprefix:"80A" -fw:"109" -command:"SWUPDATE 11092016GEO80.elf 171896" -date:"11-09-2016"
1047 candidate devices were identified.
Presently monitoring the deployment in production for any new potential problems, will fix any as soon as they are apparent.
No comments:
Post a Comment