Hi all,
A quick question: is there some kind of limitation in the cisco managed AWS cloud that prevents me from setting a static IP?
Reason: we lost one vsmart last night for a short duration because it wasn't getting a lease. Also, its logs are full of DHCP stuff that doesn't add very much.
Problem:
I started with VPN512 and configured a static route to the gateway, similar to what is currently in the RIB coming from the DHCP. Then I set a static IP and after that, I lost the SSH connection over VPN512. The change from dynamic to static seems to cause this and I can repeat this behavior. To be clear, I use the same IP for static as the device received dynamically.
NOTE: I also can't test via the CLI, because I cannot detach them from the template:
[24-Aug-2022 9:55:10 CEST] Starting Checks.
[24-Aug-2022 9:55:10 CEST] Deactivate vsmart policy before switching to cli mode
If that refers to the centralized policy, there's no chance that I'm detaching that policy. It's a live environment.
Kr,
Axel
