Thanks, for the 172.20.129.60 subnet, I still see it's wrong. In the enterprise port config you put a /24 subnet instead of a /29. Regardless, I would suggest opening a TAC case so we can do some pcaps to see what is happening

You can't use that command or access the file because you are in the restricted shell. You will need a TAC case to get the token to elevate out of the restricted shell and clear the old value from the known hosts file.

Hi Mark. Yes, please open a TAC case. This issue has been seen before with restoring 2.3.3.5 where it does exactly as you state and updates the latest available package for that service, even when not intended. As for removing those packages, that's ...

Can you take a screen shot of config from the enterprise interface in the config wizard setup there and provide that? I'm curious based on the diagram how we expect the enterprise to communicate to the gateway when the gateway is outside the subnet o...

To be honest, the best approach would be to take a copy of your running config from each device and reset the network. Then add the devices to Catalyst Center and let it rebuild the network through the fabric management.