- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Re: Aruba 3810m - ip ssh public-key (not working)
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2016 04:54 PM
08-03-2016 04:54 PM
I am configuring my new set of Aruba switches in a stack, and after getting the stack upgraded to KB.16.02.0009 and stacked I like to set up authentication via SSH keys. Normally on the HE e3800 I use a file that I can tftp over in this manner:
copy tftp pub-key-file 192.168.1.22 pubkeys_mine manager
000M Download failed: invalid key in key file.
Not so fast....that doesn't work with these Arubas. Next I tried to use this command to load them in one at a time:
# ip ssh public-key manager 'ssh-rsa AAAAB3NzaC1yc2EAAAADAQ
ABAAABAQC2Uedp8iKvwwbrae7gLt4F0coHXVrILq866VrzjODP2cJOOUg+fuR0IyjKXdyJ8HhNyRESJ+
j4MicI/aN+vCOD6SKlC3VJIfl3bODtHwXbJP7NGpqaOygNIdzBm65DQ4GK7i/khjUfSy0VbP83Zf7tru
v4R1BcRp8VDUAn+xU9qc+VNC4OkVmWBqxUk3SgA1Znp1mwda/drQXLRDGcCdrzf3tDNp5Xk878SI6K5J
R/0y9mImyXK/ri6YhCYL+r28/Nj4gRtGZoUJcabrnRHVg67PmctF4VkII1WhxRMZkD5jia8B1wk6KwDo
CO6pZ/lGGjfLli/3IwxxwyhZi5awPN'
Invalid key.
Again not working. The guide indicates that this should work. Can anyone tell me what exactly is wrong with my keys or perhaps the form of the command I am using?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2016 08:45 AM
08-04-2016 08:45 AM
SolutionUsing only the keys listed one per line in a file worked for the HP e3800, but the Aruba requires single quotes and a comment at the end of the line. This way:
'ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC7ZSzrPN+zUadGg1BK72vZcM9GlCMKHDdh0+CM/c/KgpKvMNTy2SxDQJ9W0Z/Id5hZ2i3OLCCZ8xBnEEgqBzxg/OTgNj+5jxm3Z5Jnxsq8MUaHa3t3u+tm0GbLPQsBba2CeOviLGW/WMyrDfgVs1cROy6py+yN3I6qJuI9iBxP49/P/xa+7QISQ/MZwHxjBP0xCSJj8GmEUAApb4cb5DYOenIkQBFPXrd2dK1v1THnmgi8pLURkT7auolUHdIDInusSvTYhbzlI0yQT/kuj6BEmOuPz5879XsyDkAQ7NDuuNhX5JFoiHP5CRE0a/jv47ERTl+kcPEdpGRfo9pAcPjz paul@rackspace'
You must format each line that way, and then you can use the TFTP method to load in the keys. This is not mentioned in the access and security guide.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2016 03:50 AM
08-08-2016 03:50 AM
Re: Aruba 3810m - ip ssh public-key (not working)
Good catch!
Maybe providing some documentation feedback to HPE would be great: see here.
Probably you were referring to May 2016 updated releases of:
- HP Switch Software Access Security Guide K/KA/KB.15.18
- HPE ArubaOS-Switch Access Security Guide K/KA/KB.16.01
I'm not an HPE Employee