Secondary ACS requiring License / PAK after Patching
I have just been patching out ACS 1121 on Ver 5.3 in preparation for upgrading to 5.5 however having successfully patched the secondary server I tried to promote this to the Primary and this seemed to fail with no error message.
A reboot of the Secondary now has it asking for it's license file using the PAK supplied with the product. Is this normal ? and can I recover this as I don't have the PAK supplied.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...