I'm using a US keyboard layout on an Intel Mac running 10.13.6. I've tried both screen in a terminal and a Mac app called "Serial" that includes full VT100 emulation. In the second log, the only actual input from my system keyboard is the "?" to cause it to print the menu; everything else just comes out from the switch without prompting.
The OOB management port was defaulting to DHCP, but this model doesn't ship with a default password; one has to be initially configured from the serial console. However, I did get the problem resolved. Your mention of the keyboard map made me think to try serial terminals on different systems. None of the ones I tried on a Linux host worked, but I finally got around to installing Putty in a Windows 10 VM, and that worked flawlessly. I'm glad that it's fixed now, but I'm even more deeply confused by the assortment of behavior I saw from the same FTDI-based USB serial dongle when used with different OS hosts.
In any case, thanks for the attempt and for prodding me in the right direction to eventually get it sorted out.
DELL-Josh Cr
Moderator
•
9.5K Posts
0
April 8th, 2020 16:00
Hi,
Are you using a US keyboard layout or something else?
smartyhall
3 Posts
0
April 8th, 2020 20:00
I'm using a US keyboard layout on an Intel Mac running 10.13.6. I've tried both screen in a terminal and a Mac app called "Serial" that includes full VT100 emulation. In the second log, the only actual input from my system keyboard is the "?" to cause it to print the menu; everything else just comes out from the switch without prompting.
DELL-Josh Cr
Moderator
•
9.5K Posts
0
April 9th, 2020 06:00
Will it let you configure anything? If you can assign a management ip and connect that way, that will rule out the serial connection as the problem.
smartyhall
3 Posts
0
April 9th, 2020 17:00
The OOB management port was defaulting to DHCP, but this model doesn't ship with a default password; one has to be initially configured from the serial console. However, I did get the problem resolved. Your mention of the keyboard map made me think to try serial terminals on different systems. None of the ones I tried on a Linux host worked, but I finally got around to installing Putty in a Windows 10 VM, and that worked flawlessly. I'm glad that it's fixed now, but I'm even more deeply confused by the assortment of behavior I saw from the same FTDI-based USB serial dongle when used with different OS hosts.
In any case, thanks for the attempt and for prodding me in the right direction to eventually get it sorted out.