cancel
Showing results for 
Search instead for 
Did you mean: 

HSG80 - no CLI !

 
Occasional Advisor

HSG80 - no CLI !

Please, I got a big donation : several EMA12000, DS10 to GS80, SAN switches and more.

Well, the problem is with the EMA12000 / HSG80.
I connected its RJ12 port to the COM port on my PC, started hyperterminal : 9600 baud, 8 data bits, 1 stop bit, and no parity. I tried 19200 baud too...

And... no CLI prompt.

In front pannels, no faults, no problem, no alarm, all the controllers and disk seem al right in every EMA12000. But whatever HSG80 I connect o hyperterminal (or other software), I get no CLI prompt.

Thansk for your help !

Vincent MARECHAL

5 REPLIES 5
Acclaimed Contributor

Re: HSG80 - no CLI !

Did you try this:

The maintenance port supports serial communications with default values of
9600 baud using 8 data bits, 1 stop bit, and no parity.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Occasional Advisor

Re: HSG80 - no CLI !

Thanks Torsten,

 

Yes I tried 9600 and 19200...

So I just factory reseted two associated HSG80, but no luck...

 

No cli, no matter what I do, no CLI.

The cable I use is the one described in HoffmanLabs or in this document too.

 

I don't have any more idea...

 

 

 

Acclaimed Contributor

Re: HSG80 - no CLI !

I don't know much about this device, so I can only tell you common problems with serial connections, sorry.
These are wrong connection settings, wrong cables, wrong emulation settings.

Hopefully someone else can tell you more ... why not asking the vms subforum?


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Occasional Advisor

Re: HSG80 - no CLI !

Solution found : my cable was inverted.

I had the pinout of Hoffman Labs site, and from a document quoted even in this hp site... but pins 1 to 6 are inverted !!!

 

 

I saw this looking for HSG80 RJ12 pin names, null modem layout and RS232 DB9 pins names.

From these I made my null modem. And it works.

 

But what documents in Internet and Hoffman Labs numbers pins 1 to 6 are 6 to 1.

I think computing engineers are not electronics engineers...

 

Here is the real pinout :

RJ11  <-> DB9

1 : DSR <-> 4 : DTR

2 : RXD <-> 2 : RXD

3, 4 GND <-> 5 : GND

5 : TXD <-> 3 : TXD

6 : DTR <-> 4 : DTR, 6 : DSR, 8 : CTS

This is exactly what sites publicate but inverting RJ12 pin numbers. I'm 100% sure and electronics engineer so things are this way, and not just a point of view.

 

Please note that it can be cabled differently for DB9 signals DTR, DSR, CTS.

That's why MMJ is different, as one can see on HP site.

You just have to make shure it is null modem. Mainly crossing RXD and TXD, and forcing one way DTR, DSR and DB9 and CTS for detection.

 

Well, I don't know why RJ11 is inverted on this pinout... surely because one site publicated inverted and others copied information.

 

Regards,

 

Vincent MARECHAL

 

 

 

 

Valued Contributor

Re: HSG80 - no CLI !

This is the cable I made for the HSG80 and it works:

The cable is relatively simple to make yourself. All you need is a RJ11 (6pin) cable and a DB9 (PC serial) female connector. You can use a cable from a telephone or modem. Cut off one RJ11 connector and solder the DB9 to that end.

RJ11       DB9

3+4   ->  5     
5       ->   3
2       ->   2

3 and 4 are the two center pins of the RJ11 and they both go to ground (5 at DB9), the two pins left and right from the ground are RECV_DATA and TX_DATA.

BTW: Use the RS232 port on the controller and not that one between the SCSI ports.

***********************************************
"If it seems illogical... you just don't have enough information"