01-08-2023 10:00 PM
I have a number of Aironet 3502i WAP's and they all work fine. They get DHCP address from switch and allow clients, etc.
All bar one allow console connection and show output on boot and command entry etc. so I need to find out why one of them would not allow the console to work. I can telnet/ssh to it via IP address but cannot see anything on the console screen. Same cable, same settings in Putty and it does connect, there is just no output. Have tried different speeds in Putty but not the other settings.
Is there somewhere you can check the serial requirements or do you think it is just a connection gone faulty?
Thank you
Solved! Go to Solution.
01-09-2023 01:27 AM
- Try cold start (power cycle) of the access point , and check if the problem is still in place, if so in these conditions then the console can be considered faulty ,
M.
01-08-2023 11:19 PM
- As a sanity check use your terminal equipment (with PuTTY) on another console connection and check if that can work ,
M.
01-09-2023 01:22 AM
Thanks marce1000 but I can do that. Swap a different WAP in and no issue. It is only this single WAP which is causing the issue. I s'pose I can work around it but it is frustrating because if I want to make changes I need to plug it in inside (not in the shed where it lives) to do anything.
I should say this one is also the only one running in autonomous mode if that makes any difference.
01-08-2023 11:59 PM
Hi,
Did you try these settings:
If still not working then try another laptop!
Regards
Dont forget to rate helpful posts
01-09-2023 01:25 AM
Thank you Sandeep, as I said to marce1000 the cable and console work on other WAP's. It is only this one.
I did try speeds and flow but left everything "standard" and, thinking about it, I have actually tried it on a different computer too.
01-09-2023 01:27 AM
- Try cold start (power cycle) of the access point , and check if the problem is still in place, if so in these conditions then the console can be considered faulty ,
M.
01-09-2023 04:28 PM
Thanks marce1000, can confirm there is no output even on cold boot so you have confirmed the console port as faulty. Very odd.
I might convert this one to lightweight and use a different one for the autonomous to bypass the issue.
Will accept your response as solution.
Thank you for your help
Cheers,
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