-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
device type and ssh autodetect for ArubaOS-CX switches #3133
base: develop
Are you sure you want to change the base?
Conversation
Does the HP ProCurve driver actually work with the Aruba-CX devices? We should probably do the standard |
Test process is here: |
I ran both tests (test_netmiko_show.py and test_netmiko_config.py) against an Aruba 6405. test_netmiko_show.py
test_netmiko_conf.py
|
Is anything else necessary? |
Interesting... I tested the netmiko/netmiko/hp/hp_procurve.py Line 60 in 20baa4e
was causing it to fail, as the ArubaOS CX switches do not have an enable mode. I was able to get at least config backup working by connecting to my AOS-CX switches with the basic |
The device type
aruba_os
seems to be for the controllers and gateways.The device types
aruba_osswitch
andaruba_procurve
point to theHPProcurve
class and seem to be intended for the HP/Aruba 2500 and 2900 series switches.The new device type
arubaos_cx
should be for the switches Aruba CX 6000/8300/10000 series.I've mapped this to the
HPProcurve
class.The Aruba CX switches can be recognized quite easily.
show version
produces the following output:I think looking for the string "ArubaOS-CX" should be a solid solution.