Sourcefire 3D Device Upgrade Failed

[chrisjoyce1980]

I've attempted 3 time now to upgrade a 3D7125 from 5.3.0.3 to 5.4.0-763 with it failing at the same step

Installing Sourcefire 3D Device S3 Upgrade version: 5.4.0-763
Local Install

Update Installation Failed : [15%] Fatal error: Error running script 200_pre/005_check_manager.pl

I've re-download the software and no joy.  Any clues?

[Marvin Rhoads]

I saw a similar error on one of the ASA FirePOWER modules I upgraded. A different one and a 3D7125 went fine.

For the failure, I opened a TAC case and the engineer had to drop into the root shell and run a fixup script to straighten it out. Once he did that the upgrade completed successfully.

FYI - there is a Sourcefire community that is better suited for this question topic:

https://supportforums.cisco.com/community/12183446/sourcefire

[Nayan.Patel85]

HI,

I am running into same problem on my SourceFire 3d7110 appliance.

Update Installation Failed : [15%] Fatal error: Error running script 200_pre/005_check_manager.pl

We RMAed the box and the one we got as replacement is running 5.3.0.3 code version.

Our FMC is running 6.2.2 code version so I can't manage this appliance through FMC and push the upgrades.

So I trying to upgrade the code from appliance it self.

There must be a way to disable the check temporarily.

[Marvin Rhoads]

You can reimage the appliance from ISO to version 6.2.

Use "Sourcefire_3D_Device_S3-6.2.2-81-Restore.iso" from here: 

https://software.cisco.com/download/home/286261238/type/286271056/release/6.2.2?catid=268438162

Perform initial setup and register it with your FMC. Deploy policies to it and patch it up to the current release.

[moigomez]

Device must be managed to upgrade.  

You could confirm that on the logs under /var/log/sf/Sourcefire_3D_Device_S3_Patch-X.X.X.X/200_pre/005_check_manager.pl.log

That Perl script confirms if the device is being managed by the FireSight (Defense Center).

[Ralph Rye]

Ran into a similar issue, and it turned out that I didn't have a access control policy applied.  Once I applied the default policy the patch / update applied sucessfully.

The error logs in  /var/log/sf/Sourcefire_3D_Device_S3_Patch-X.X.X.X/200_pre/  pointed me in the right direction.

Ralph