Hi, Seems I made a bit of a mistake trying to duplicate a configuration from one LTM to another (v11). I created a UCS archive of the original LTM and then restored that on the second LTM. Now I can't seem to get the second LTM working at all. I think the main problem is that the license from the original LTM has now been put on the new device and that's obviously not allowed. I've already tried to factory default the configuration (successful) but the problem is the license. I can't activate the license on the second LTM as it tells me the license is already activated on another LTM. I can't figure out how to either reset or completely remove the license so that I can start again. I have SSH and GUI access to both LTMs. All help is greatly appreciated. Thanks in advance, Ben Johnson

Ben - Can't you just get a new dossier and then license the box again ?

The other thing you might want to do is look for another ucs on the local box that is older than your restore by running the following command as a root user on the system: find / -name \*ucs -exec ls -la {} \;

Tried that. The dossier must be built off the license file, which is now included in the UCS archive (new behaviour as of v11 apparently). So when I try that's when I get the error that the license has been activated on a different unit.

Posted By J on 05/27/2013 06:04 PM The other thing you might want to do is look for another ucs on the local box that is older than your restore by running the following command as a root user on the system: find / -name \*ucs -exec ls -la {} \; Thanks, I'll try this. Fingers crossed.

Did you generate a new dossier? the dossier is based off of the RegKey - if that doesn't work, you might have to have to submit a ticket to have the license revoked and generate a new dossier - that is usually a pretty quick turnaround even with a priority 3 websupport ticket. With the serial number they will validate your using the correct REGKEY as well...

v11 - Restored UCS on wrong device - How to reset?

11 Replies

Jnon
Nimbostratus
May 28, 2013
Ben - Can't you just get a new dossier and then license the box again ?
Jnon
Nimbostratus
May 28, 2013
The other thing you might want to do is look for another ucs on the local box that is older than your restore by running the following command as a root user on the system:

find / -name \*ucs -exec ls -la {} \;
BenJ
Nimbostratus
May 28, 2013
Tried that. The dossier must be built off the license file, which is now included in the UCS archive (new behaviour as of v11 apparently). So when I try that's when I get the error that the license has been activated on a different unit.
BenJ
Nimbostratus
May 28, 2013
Posted By J on 05/27/2013 06:04 PM

The other thing you might want to do is look for another ucs on the local box that is older than your restore by running the following command as a root user on the system:

find / -name \*ucs -exec ls -la {} \;

Thanks, I'll try this. Fingers crossed.
Jnon
Nimbostratus
May 28, 2013
Did you generate a new dossier? the dossier is based off of the RegKey - if that doesn't work, you might have to have to submit a ticket to have the license revoked and generate a new dossier - that is usually a pretty quick turnaround even with a priority 3 websupport ticket. With the serial number they will validate your using the correct REGKEY as well...
BenJ
Nimbostratus
May 28, 2013
Posted By J on 05/27/2013 08:13 PM

Did you generate a new dossier? the dossier is based off of the RegKey - if that doesn't work, you might have to have to submit a ticket to have the license revoked and generate a new dossier - that is usually a pretty quick turnaround even with a priority 3 websupport ticket. With the serial number they will validate your using the correct REGKEY as well...

Based on your earlier advice I found an older UCS file and used that. Solved the license problem but disconnected me from the unit :/ Thankfully there was someone on site who could re-key the management IP via the front panel. Thought the UCS wasn't supposed to touch the Management stuff? In any case, I'm back to having a workable unit - and a lesson in making assumptions about how things work!

Thanks for your help.
Jnon
Nimbostratus
May 28, 2013
Were you going to use this as the HA system?

the bigip.conf file should be the same but the base, license etc.. are going to be different.

Glad your back on track - yea, the ucs you restored might have been from the initial config so you might have the default admin and root passwords.
- mubashir_133429
  Nimbostratus
  Jun 10, 2014
  hi J, I have same problem i have copy the UCS file from my 3600 and then restore it on 8900 that has i think overwrite 8900 license and now on 8900 GUI i have license registration utility which is asking me for correct license key,Before restoring 8900 has default setting and i was just trying to configure it with the configuration i had on 3600.with my question you may have idea that i am new with F5. Ok if i find the old UCS file by the above command how can i restore that UCS again as i can't do it through GUI.
Jnon_42048
Nimbostratus
May 28, 2013
Were you going to use this as the HA system?

the bigip.conf file should be the same but the base, license etc.. are going to be different.

Glad your back on track - yea, the ucs you restored might have been from the initial config so you might have the default admin and root passwords.
- mubashir_133429
  Nimbostratus
  Jun 10, 2014
  hi J, I have same problem i have copy the UCS file from my 3600 and then restore it on 8900 that has i think overwrite 8900 license and now on 8900 GUI i have license registration utility which is asking me for correct license key,Before restoring 8900 has default setting and i was just trying to configure it with the configuration i had on 3600.with my question you may have idea that i am new with F5. Ok if i find the old UCS file by the above command how can i restore that UCS again as i can't do it through GUI.
JG
Cumulonimbus
Jun 10, 2014
For your reference (next time you need do this again):

http://support.f5.com/kb/en-us/solutions/public/13000/100/sol13132.htmlRMA