Can't get terminal to display

[gregh825]

I am running the latest Airconsole driver for MAC (OS 10.9) and am running the latest firmware on my Airconsole and I am unable to get any output from connecting to a (Cisco) device to work. When I try using AirconsoleOSX, it "connects" but I get no output. There is a line in the connection output that says "Setting initial baud=9600, databits=8, parity=1, stop=1". I am guessing that the "parity =1" is the problem (Cisco default is 9600 8N1). The defaults on the console itself (from the web browser) are 9600 8N1 so I'm not sure why it is defaulting to parity=1. It seems to be coming from the driver itself "/dev/tty.Airconsole-1" because whether I try to connect via the Airconsole (WiFi), MACWISE, or a standard terminal (using screen /dev/...) I get the same result. How can I fix this?

[semaja2]

Not sure what the issue is there, but I personally use the inbuilt terminal of the air-console device as its fast and has everything I need

To get to it just navigate to http://192.168.10.1/terminal.asp

[njc235]

I have the same problem, can anyone advise? It seems like I can connect to the air console but not beyond to the switch. As the previous post mentioned, the airconsoleOSX app reports 8-1-1 as opposed to 8-N-1 which is required. Where can this be changed or am I on the wrong trail?

[daniel]

The parity as reported by AirconsoleOSX is in RFC2217 format. 1=None, 2=Odd, 3=Even, 4=Mark, 5=Space

To troubleshoot, I would rule out the OSX portions.
1. Log into the Airconsole web interface, set the line parameters you want on the "Serial" page, press save (e.g. 9600 8N1)
2. telnet into the Airconsole on port 3696 - e.g. telnet 192.168.10.1 3696
Do you then get anything coming back in your telnet session?

I'm not sure exactly which device you are connecting to, but some will require that hardware flow control is set on - you can experiment with that too.

[njc235]

AirConsole-90 login: admin
Password:
Welcome to

_____ .__ .__
/ _ \ |__|______ ____ ____ ____ __________ | | ____
/ /_\ \| \_ __ \_/ ___\/ _ \ / \ / ___/ _ \| | _/ __ \
/ | \ || | \/\ \__( <_> ) | \\___ ( <_> ) |_\ ___/
\____|__ /__||__| \___ >____/|___| /____ >____/|____/\___ >
\/ \/ \/ \/ \/


BusyBox v1.12.1 (2014-01-05 23:33:34 GMT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

Telnet to the Aironsole seems fine. I have it plugged in to an HP 2915 (J9562A) still unable to get through to the switch.

[daniel]

You need to telnet on port 3696, not on the regular telnet port.

e.g. enter the command
telnet 192.168.10.1 3696

[njc235]

Thanks for your help but still not getting anywhere beyond the air console.

telnet> open
(to) 192.168.10.1 3696
Trying 192.168.10.1...
Connected to 192.168.10.1.
Escape character is '^]'.

[daniel]

The test of telnetting to port 3696 shows that the issue lies on the serial port side of the Airconsole and not on the client side (OSX, etc). This is typically caused by one of two things:
1. Incorrect cabling (e.g. pinout incorrect, null connector used when straight through required, etc)
2. Incorrect serial settings (e.g. baud rate, hardware flow control, etc - defaults can be set in the Airconsole web interface)

Doing a quick google shows that the RJ-45 console port pinout for HP Procurve switches is non-standard - see http://andkorn.org/blog/2013/05/08/hp-p ... le-pinout/ and http://h20566.www2.hp.com/portal/site/h ... cachetoken

I would suggest checking the documentation for your switch to ensure that you have your cabling correct.

[njc235]

Excellent, that was it. Now in and working. Thanks for you help Daniel.