02-14-2017 01:45 AM
I typically use the 'industry default' settings 9600 baud, 8N1. For the Aruba switches, the switch is even sensing the speed. So if you have it set different, it should work as well.
To 'sense' the speed, what the console port needs is some signal. I tend to press enter 3 times, then the console comes alive:
<enter> <enter> <enter> Connected at 9600 baud Aruba JL074A 3810M-48G-PoE+-1-slot Switch Software revision KB.16.03.0003 .....
On the speed, this is in the manual:
To connect a console to the switch, configure the PC terminal emulator as a DEC VT-100 (ANSI) terminal or use a VT-100 terminal, and configure either one to operate with these settings:
• Any baud rate from 1200 to 115200 (the switch senses the speed).
• 8 data bits, 1 stop bit, no parity, and flow control set to off.
• For the Windows Terminal program, also disable (uncheck) the “Use Function, Arrow, and Ctrl Keys for Windows” option.
• For the Hilgraeve HyperTerminal program, select the “Terminal keys” option for the “Function, arrow, and ctrl keys act as” parameter.
For me I have never experienced issues, you need to know though that you have to 'enter' a few times to wake the console up.
If you have urgent issues, please contact your Aruba partner or Aruba TAC (click for contact details).
02-17-2017 02:04 AM
In response from Herman you can see correct settings. I hope it's working for you at the mioment? If not sometimes it helps to reboot the switch when you have console port connected. Off course if you're able to reboot the switch. If you have this issue more often and it's older switch version you can configure console port settings fixed in switch configuration. This way you skip autosensing which in older version can in rare cases gives some issues.