In that case, you should start a sniffer trace filtering on all telnet (tcp/23) traffic between RME and the WLC in question. Then run a new Sync Archive job. When it fails, the sniffer trace file will indicate why this is happening.
According to this, your WLC is running code greater than or equal to 5.2, and you may need to increase your telnet timeout in order to fetch the entire config. Go to RME > Devices > Device Management > RME Devices, and the edit the device attributes for this device. Increase the telnet timeout to 72 seconds (you may need to go higher, but start there). Save and apply your changes, then try the Sync Archive job again.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...