Everything seems to be working fine on the new WAN acceleration deployment that has gone through a lot of troubleshooting in the past few weeks. However, there's an issue with accessing a spoke device from the hub via WebUI & SSH.
Deployment is in a hub (1) & spoke (10) topology all in offpath mode with WCCP packet interception mode. WXOS - 18.104.22.168.
This particular site (spoke) doesn't have re-direction enabled on it, yet I can't access it via webUI & SSH. I can ping the spoke & it's gateway. I have asked client to check for any possible access lists/policies that could cause this but none was found.
Can someone help with this?
PS: I asked for the spoke device to be 'power cycled' at the branch. I could access the spoke through SSH & WebUI for a brief period (either during or shortly after power cycling) but I got denied again after this short period.
I tried your suggestion but it didn't work. However, I was able to identify the issue. It was an ip conflict on the spoke device. Like I mentioned earlier, whenever the device is restarted, I can get access into the device for sometime & I get 'kicked out' of the GUI (or SSH) after a short period. I guessed this was due to an ip conflict with another device whenever there's a broadcast from the device.
I worked with the customer on this and my assumption was right so we resolved the ip addressing issue.