Troubleshooting Tip: Excessive CLI Logins to Cisco Wireless Controller
Description
This article describes a workaround to solve an issue with L2/L3 polling when it causes excessive CLI Logins to Cisco Wireless Controller.
Scope
Version: Network Sentry versions prior to 7.0.4, FortiNAC.
Solution
Issue: L2/L3 polling causing excessive SSH sessions to controller.
CLI credentials were used by default for L2/L3 polling. The inconsistencies of various device models using this method caused problems.
Workaround: Change the Cisco Wireless Controller configuration to use SNMP for communication instead of Telnet or SSH.
CLI credentials were used by default for L2/L3 polling. The inconsistencies of various device models using this method caused problems.
Workaround: Change the Cisco Wireless Controller configuration to use SNMP for communication instead of Telnet or SSH.
- From the Network Devices -> Topology View, select the Cisco WLC.
- Right-click on it and select Properties.
- Check the Advanced box and select the Use SNMP to read L2/L3 data from the device setting.
- Select the Credentials tab and select Validate Credentials to ensure the SNMP credentials are correct.
Solution: Version 7.0.4 changed Network Sentry defaults to read ARP entries from Cisco wireless using SNMP credentials. Any Cisco WLCs modeled in Topology View prior to version 7.0.4 would need to be configured to use SNMP manually.