cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
13263
Views
9
Helpful
5
Replies

Firepower 2100 boot directly to Rommon

cgedwards
Level 1
Level 1

I have a pair of Cisco 2100 series firepower devices that I am configuring for deployment at two separate locations. Currently when powered on, they go into rommon, without any prompt from me. Once I type the boot command they will complete their boot process and allow configuration through the Firepower GUI. As these will be at remote sites, I need them to boot fully without user input.

1 Accepted Solution

Accepted Solutions

cgedwards
Level 1
Level 1

Shortly after posting I found this:

 

https://quickview.cloudapps.cisco.com/quickview/bug/CSCvp57772

 

The bug report linked solved my issue, though I find it weird as these are fresh from the box appliances.

View solution in original post

5 Replies 5

cgedwards
Level 1
Level 1

Shortly after posting I found this:

 

https://quickview.cloudapps.cisco.com/quickview/bug/CSCvp57772

 

The bug report linked solved my issue, though I find it weird as these are fresh from the box appliances.

 

 - Did you examine the confreg value the device was shipped with , (as explained in the bug-report) ?

 M.



-- Let everything happen to you  
       Beauty and terror
      Just keep going    
       No feeling is final
Reiner Maria Rilke (1899)

It was set to 0x0. I went through the prompts of the confreg command and the value had changed to 0x1 when I was done. I did not see this step in any startup guide, so just a bit annoyed that this was buried so deeply in Cisco's documentation.

 

          - Yeah it stunned me too , that I could not  find this rather quick with searching.

 M.



-- Let everything happen to you  
       Beauty and terror
      Just keep going    
       No feeling is final
Reiner Maria Rilke (1899)

Yes, I've been seeing it on multiple 2100 series this year. It's a change from previous behavior and definitely, as the bugID indicates, not how it should work.

The "confreg 0x1" command fixes it permanently. I had answered a similar thread a couple of weeks ago:

https://community.cisco.com/t5/network-security/fpr2140%E5%BC%80%E6%9C%BA%E8%BF%9B%E8%A1%8Crommon%E6%A8%A1%E5%BC%8F/td-p/4503896

 

Review Cisco Networking for a $25 gift card