Unable to upgrade to 5.4.1-59 from 5.4.0

[kiki.marconio]

When I'm trying to upgrade this error was posted in SF-MC: (reload doesn't help)

Error

Installation failed: Peer registration in progress. Please retry in a few moments.

[Marvin Rhoads]

Is the target device showing up as managed?

[kiki.marconio]

Yes. Everything is working fine with this version. (Well, the problem is that URL filtering does not provide "HTTP response" in blocking mode, thats why we would like to upgrade)

M.

[Marvin Rhoads]

Sounds like a file might not have gotten updated on FMC to flag the device registration as having completed.

I'd recommend you open a TAC case and the engineer can dig into the filesystem on the FireSIGHT Management Center to remedy the issue.

[Pavel Trinos]

Or temporary removing device could do the trick as well. Once update is completed, add the device back to SFMC.

[Guillaume BARBEROT]

for me it just after ova deployment in version 5.4.0 i want to upgrade to 5.4.1.1

i have added some asa5516-SFR during SF-MC license registration (ip and reg_key)

so when booting the SF-MC is trying to add the sourcefire module of asa, but my module have newer version (5.4.1) already installed (version were shipped with asa)

so when i try to upgrade the SF-MC, i get this error too :

Installation failed: Peer registration in progress. Please retry in a few moments.

even if in the task list the 2 tasks adding the sfr module were failed, and now there are no task left ... (no pending job)

i suppose SF-MC will stop this registration process, ... but it is still running in background somewhere since 30 minutes ....

how to quiclky kill this registration process

in th device management list i have no managed devices (as their version is newer than the SF-MC)

Any idea Marvin ?

[EDIT]

just opened a TAC Case and support engineer did the trick

devices were stuck in registration pending in the backend Database

so we used root command on FSMC (sudo su) : remove_peer.pl <asafirepowermoduleIP>

and also on each firepower module (expert, then sudo su) : remove_peer.pl <SFMCIP>

then upgrade starts correctly

at the end have to do on each asasfr module : configure manager add <SFMCIP> reg_key

and on SFMC add asa sfr modules devices

[Peter Long]

I had this very problem yesterday, I went to ad the module, and the process failed, (because of a difference of versions), then I could not update the module because a registration was in progress (Catch 22!)

Cisco FirePOWER – Update Fails ‘Peer Registration Failed: Registration in Progress’

Pete

[Dennis Perto]

When you use the on-device (ASDM) management for Firepower, you are not supposed to register a manager.

[Fred Ferrell]

I found if you go to the web GUI on the NGIPS appliance (my case 7000 series) you can go to Local > Registration and then delete the FMC from there too. No need to SSH in for this.