Re: Clients connected through 2702 AP (IOS AP) cannot telnet/SSH to others devices

boonhine79 · ‎10-29-2018

Hi ,

I am having issue here with the client which are connected through 2702 AP by enabling 802.1x will not able to telnet/SSH to others devices . But the client connected through 3802 AP with same setting will works perfectly .

But when we removed the 802.1x from the WLAN setting on WLC , WEP with open authentication , the wireless clients will not having any issue no matter it is connected with 3802 AP or 2702 AP .

I am suspecting the issue was due to the IOS bug , but i was been searching on Cisco bug portal , couldnt get a matched . Anyone experience this issue before ?

*** Issue only happened on Telnet and SSH , clients is able to do internet surfing . No issue on authentication as we can see the client was passing the authentication phase and get into "Run" state

From

Boonhine17

Rich R · ‎10-30-2018

Autonomous or CAPWAP?

What version(s) of IOS or WLC code?

------------------------------
Please click Helpful if this post helped you and Select as Solution (drop down menu at top right of this reply) if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's and TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's, Best Practices for 9800 WLC's and Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390

boonhine79 · ‎10-30-2018

Hi rrudling ,

Cisco 5520 WLC , issue was found on 8.2.166.0 . We upgraded to 8.2.170 and 8.3.143 (cisco recommended version ) , issue remain the same .

Issue reported :

client connected to 2702 AP cannot telnet / SSH to core switch as well as others devices when enabled the 802.1x on authentication . When the same client with same devices connected to 3802 AP , telnet /SSH services resumed immediately . When removed the 802.1x from authentication , just using WPA2 with password , telnet /SSH services will just working as usual no matter the client is connected to 2702 or 3802 AP . For your information , issue only happened on telnet/SSH as well as Avaya softphone , but client connected on 2702 still able to surf internet , ping the core switch , ping the Avaya server , only telnet , SSH and Avaya softphone cannot registered with the Avaya server .

superego · ‎11-01-2018

Can you adjust the AP TCP MSS to 1300?

Configuring TCP MSS (GUI)

Step 1	Choose WIRELESS > Access Points > Global Configuration to open the Global Configuration page.
Step 2	Under TCP MSS, select the Global TCP Adjust MSS check box and set the MSS for all access points that are