On 2015-12-31, 9:08 AM, Eric Van Tol wrote:
I’ve looked at this and there’s nothing in the console port config at all. I’ve
tried disabling and re-enabling the console port in the config, as well as
rebooting the switch to see if there was some “negotiation” going on. I’m able
to connect to the console using a Cisco 2511 terminal server, as well as just a
regular serial connection to a PC. It’s just the connection to this MRV console
server that isn’t working. This is what I get:
InReach:0 >>telnet 172.28.1.2 2100
Entering character mode
Escape character is ^] .
ÿÿÿÿ¿ÿÿÿÿÿÿ¿ÿÿ
I can remove the cable from the EX4200 and plug it into anything else and it
works fine, so I’m stumped as to why any EX doesn’t work.
-evt
From: Will O'Brien - NOAA Affiliate [mailto:[email protected]]
Sent: Thursday, December 31, 2015 12:04 PM
To: Eric Van Tol <[email protected]>
Cc: [email protected]
Subject: Re: [j-nsp] EX4200 console port woes
double check the console port config... .
It's under system ports console
On Thu, Dec 31, 2015 at 9:11 AM, Eric Van Tol
<[email protected]<mailto:[email protected]>> wrote:
Hi all,
I have been struggling for the past day to get my EX4200 console ports to work
on an MRV LX4000T console server and something is just not right. I'm hoping
someone else may have come across this or tell me where I'm being stupid.
I'm using a rolled cable that works fine with the SRX and various Cisco
consoles. Console server is configured with 8N1, no flow control, 9600bps, but
when I try to connect to the EX, I get gibberish on the screen and framing
errors showing up in the port stats on the console server. Pinouts for both the
EX and SRX (and I imagine all Juniper gear) are the same:
EX:
http://www.juniper.net/techpubs/en_US/release-independent/junos/topics/reference/specifications/port-ex-series-console-connector-pinout.html
SRX:
http://www.juniper.net/techpubs/en_US/release-independent/junos/topics/reference/specifications/rj45-connector-pinout-srx110-for-console-port.html
I cannot figure out what's going on with the EX. Again, cable has been tested
with multiple other kit, so it's not a cable issue AFAIK.
Thanks,
evt
_______________________________________________
juniper-nsp mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
looks like misconfiguration rate.. you can always try setting your
client to various different values and see which works
try 19200, 57600, or 115200
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
