Troubleshooting Access Points Using Telnet or SSH
The controller supports the use of the Telnet and Secure Shell (SSH) protocols to troubleshoot lightweight access points. Using these protocols makes debugging easier, especially when the access point is unable to connect to the controller.
-
The upgrade command cannot be used when a Telnet or SSH session is enabled.
-
You can enable a Telnet or SSH session on unjoined access points with non default credentials.
Troubleshooting Access Points Using Telnet or SSH (GUI)
Procedure
Step 1 |
Choose Wireless > Access Points > All APs to open the All APs page. |
Step 2 |
Click the name of the access point for which you want to enable Telnet or SSH. |
Step 3 |
Choose the Advanced tab to open the All APs > Details for (Advanced) page. |
Step 4 |
Select the Telnet check box to enable Telnet connectivity on this access point. The default value is unchecked. |
Step 5 |
Select the SSH check box to enable SSH connectivity on this access point. The default value is unchecked. |
Step 6 |
Click Apply. |
Step 7 |
Click Save Configuration. |
Troubleshooting Access Points Using Telnet or SSH (CLI)
Procedure
Step 1 |
Enable Telnet or SSH connectivity on an access point by entering this command: config ap {telnet | ssh} enable Cisco_AP The default value is disabled.
|
||
Step 2 |
Save your changes by entering this command: save config |
||
Step 3 |
See whether Telnet or SSH is enabled on an access point by entering this command: show ap config general Cisco_AP Information similar to the following appears:
|