topic Re: Question about running sfr do password-reset in Network Security

Question about running sfr do password-reset

manofsteel03 — Thu, 19 May 2022 09:24:47 GMT

Currently we have a pair of ASA5525 with SFR setup in High Availability mode but have forgotten what the SRF password is.
We understand that in order to reset the password on the SFR you login to the ASA and then run the command session sfr do password-reset. My question is, if you do this on the Primary ASA, will it copy the new password over to the secondary or does this have to be performed manually on each device? Also, does changing the password affect any other operations on the device itself that we need to be aware of?

Thx in Advance.

Re: Question about running sfr do password-reset

balaji.bandi — Thu, 19 May 2022 09:49:05 GMT

I do not recollect correctly, doing primary should be replicated to secondary i guess.

Re: Question about running sfr do password-reset

Marvin Rhoads — Tue, 24 May 2022 18:03:05 GMT

@manofsteel03 the sfr (Firepower) modules have no awareness of each other and operate as independent devices. That applies whether the ASAs are in an HA pair, cluster or otherwise.

So you have to run the command on each ASA for which you need to reset the password. No data plane or other user traffic will be affected by doing this.

Re: Question about running sfr do password-reset

manofsteel03 — Thu, 23 Jun 2022 05:13:06 GMT

Thx for the info. Greatly appreciated.

Re: Question about running sfr do password-reset

manofsteel03 — Thu, 23 Jun 2022 17:14:18 GMT

I decided to run the command session sfr do password-reset on the appliance. Got no error messages after hitting the Enter key. Now when I run session sfr console it then asks for login. I enter admin (as well as Admin) as the username but I get a response Login Incorrect. This is a ASA5555-X unit. Any other username it would default to?

Thx in advance for any help given.

Re: Question about running sfr do password-reset

Marvin Rhoads — Thu, 23 Jun 2022 18:44:33 GMT

The default is username admin with password Admin123. The admin username is built-in and cannot be deleted. I suppose somebody could have went into the expert (OS level) prompt and really performed unsupported command to change that but under normal operations it should always be available. If all else fails, you can reimage the module.