-
Notifications
You must be signed in to change notification settings - Fork 732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cisco_wlc_ssh update name to cisco_wlc? #409
Comments
I need to think more about potential impact on others projects that have this as a dependency, but I created this TODO when I upgraded the testing
|
I just spotted this as well as I was running the tests for PR #418 . The rules of the index file specifically state the OS need to be a netmiko OS type, which is I wasn't raising that PR for this issue, but in changing the way the command and OS is compared, the test failed because the list of accepted types in the test was wrong (missing the _ssh). If it gets removed as part of an update to netmiko, that is fine, so long as the test here is also updated to reflect the change. |
Now that Cisco's recent WLCs run IOS-XE this may not be worth changing in both netmiko or ntc-templates projects. For the common |
ISSUE TYPE
TEMPLATE USING
SAMPLE COMMAND OUTPUT
SUMMARY
Other systems are jumping in and working in conjunction with NTC templates. Specifically Netmiko integration in this issue. The name for wireless is typically
cisco_wlc
in Netmiko, which then does not find an NTC template in the home directory. As a work around the device_type ofcisco_wlc_ssh
does work, but seems a little out of the ordinary to use with Netmiko since it is SSH by using it.Would like to remove the _ssh suffix on the cisco_wlc_ssh names to assist with this. Are there other non-ssh templates for this?
The text was updated successfully, but these errors were encountered: