Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello,Can I upgrade from 17.3.5 Amsterdam to 17.9.10 Cupertino on my ISR 4431?CPLD Version: 19042950Rommon: 17.6.1AIR-GAPPED routerCurrently Bundle mode, I plan switch to Install modeAnd what about the Smart licenses? any restriction if I don't regis...
Hello,
I have a couple of ASAs 5515 on HA cluster, I configured on the active unit
failover key xxxxxxxxxxxxxkey config-key password-encryption xxxxxxxxxxxxxxx
However the config syn failed and I lost the HA cluster, the configured one worked for a c...
Hello,
Our Default self-signed server certificates are about to expire, so I need to know if is possible to renew them manually editing them on this way without breaking the cluster.
Certificate to renew:
Deployment, 1 prim admin, 1 prim monitoring...
Hello Team,
I need to know if is possible nowadays to use an ACS 5.7 to authenticate with Radius the PaloAlto devices with OS 10.2, I followed a couple of guides with no success, no matches on the services selection rules, neither on the authorizatio...
Hello Team,
I need some help, we need to know if we can move the policy nodes to admin-monitoring nodes? we have version 2.4, base and Device admin licenses installed, we are running on Virtual machines.
Our Deployment:
1 primary admin-secondary moni...
FYI
The cluster was recovered, simply configured the failover key on the secondary(active) unit and the primary(down) took the active role and sync the config to the secondary(standby) unit with the masterkey.
asa 5515SW 9.4(4)5
MSG on the down unit(primary down) configured with failover and master key:
WARNING: Failover message decryption failure. Please make sureboth units have the same failover shared key and crypto licenseor system is not out of memory
Hello, did you configure the failover key and master key on both devices? I configured both keys on the active only but the failover cluster was broke due the config sync failed.
