02-03-2019 12:23 AM
02-04-2019 01:27 AM
you supply very little information to us!
- what error do you get?
- does the device keep functioning normally?
- is the CLI accessible?
release notes report this so you may need to re-register the license?
02-04-2019 02:44 AM
Thank you pieterh for your reply.
- error received from any browser - err connection timed out
- does the device function normally - yes the device functions normally, though I have no way of adjusting any settings because there is now no way to access the device, and the RJ45 console port does not work on this device because it is listed in the manual as "for future use".
- is the CLI accessible - no the command line is not accessible. I have tried ssh and telnet, https, http, all non-accessible.
I think you are correct about re-registering the license, especially considering the default Vlan is not 192.168.1.1, as I have modified that in the running config and saved to start.
02-04-2019 01:51 AM
Hello,
in addition to the other post, you also might want to try a factory reset and then follow the instructions below (although version 1.0.01.18 is mentioned this might very well work for 1.0.02.16)
02-04-2019 02:47 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide