[SLE] Not SUSE-related - serial port on a Compaq 8-port SAN-switch?
All, I'm trying to connect to a Compaq StorageWorks SAN Switch 8 over the serial port, that is using a null-modem cable. And I'm not getting anywhere. I use minicom on the host system, have tried all the baudrates, played with hardware and software flowcontrol, but I'm just not getting anything from the switch. I've been googling a lot and haven't really come up with anything solid. I've even got the switch manuals, but they don't say else besides "connect the serial cable". So on the off chance that someone here might just know how this story goes .... /Per Jessen, Zürich -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Wednesday 19 July 2006 4:21 pm, Per Jessen wrote:
All,
I'm trying to connect to a Compaq StorageWorks SAN Switch 8 over the serial port, that is using a null-modem cable. And I'm not getting anywhere. I use minicom on the host system, have tried all the baudrates, played with hardware and software flowcontrol, but I'm just not getting anything from the switch.
Does the port work with other serial devices? Check that it hasn't been disabled in the BIOS? Do you have a breakout box so you can test the port and cable? Are you sure it needs a null-modem? Do you get anything on your screen? Do you see any response on the switch? -- Collector of vintage computers http://www.ncf.ca/~ba600 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Wed, 2006-07-19 at 23:57 -0400, Mike wrote:
On Wednesday 19 July 2006 4:21 pm, Per Jessen wrote:
All,
I'm trying to connect to a Compaq StorageWorks SAN Switch 8 over the serial port, that is using a null-modem cable. And I'm not getting anywhere. I use minicom on the host system, have tried all the baudrates, played with hardware and software flowcontrol, but I'm just not getting anything from the switch.
Does the port work with other serial devices? Check that it hasn't been disabled in the BIOS? Do you have a breakout box so you can test the port and cable? Are you sure it needs a null-modem? Do you get anything on your screen? Do you see any response on the switch?
-- Collector of vintage computers http://www.ncf.ca/~ba600
I'd try a "loop-back" by first jumpering p2 and p3 on the 9-pin null-modem cable, then make sure minicom is echoing what you type. You might not have the correct /dev/ttySx set up in minicom. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thursday 20 July 2006 00:37, Tom Patton wrote:
I'd try a "loop-back" by first jumpering p2 and p3 on the 9-pin null-modem cable, then make sure minicom is echoing what you type. You might not have the correct /dev/ttySx set up in minicom.
OMFG! A *real* troubleshooter in our midst! ;-) -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Mike wrote:
Does the port work with other serial devices?
Yes.
Check that it hasn't been disabled in the BIOS?
It's not.
Do you have a breakout box so you can test the port and cable?
The cable is working. I use it for a couple of headless systems too.
Are you sure it needs a null-modem?
No, that's one thing I'm not certain about - the port on the switch is male, as is the port on the host.
Do you get anything on your screen?
Nothing. No response whatsoever.
Do you see any response on the switch?
Nope. /Per Jessen, Zürich -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Per Jessen wrote:
Do you have a breakout box so you can test the port and cable?
The cable is working. I use it for a couple of headless systems too.
Are you sure it needs a null-modem?
No, that's one thing I'm not certain about - the port on the switch is male, as is the port on the host.
This is one of the reasons you may want a break out box. There is no hard standard for such connections and some manufacturers use a male connector, where others would use a female. With a break out box, you can see which pins are used for transmit & receive and wire accordingly. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Do you have a breakout box so you can test the port and cable? The cable is working. I use it for a couple of headless systems too. Are you sure it needs a null-modem? No, that's one thing I'm not certain about - the port on the switch is male, as is the port on the host .>This is one of the reasons you may want a break out box. There is no hard standard for such connections and some manufacturers use a male connector, where others would use a female. With a break out box, you can see which pins are used for transmit & receive and wire accordingly.
Check out the statserial utility; statserial will show the status of the pins of the serial port, like a software breakout box.
Adam Williams wrote:
Do you have a breakout box so you can test the port and cable? The cable is working. I use it for a couple of headless systems too. Are you sure it needs a null-modem? No, that's one thing I'm not certain about - the port on the switch is male, as is the port on the host .>This is one of the reasons you may want a break out box. There is no hard standard for such connections and some manufacturers use a male connector, where others would use a female. With a break out box, you can see which pins are used for transmit & receive and wire accordingly.
Check out the statserial utility; statserial will show the status of the pins of the serial port, like a software breakout box.
Good one - thanks Adam. I'll let you know. /Per Jessen, Zürich -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Per Jessen wrote:
Check out the statserial utility; statserial will show the status of the pins of the serial port, like a software breakout box.
Good one - thanks Adam. I'll let you know.
The main difference between a working connection (null-modem to another device) is that DCD is raised, whereas it isn't when I try the SAN switch. I haven't been able to try a straight through cable though - I need a gender bender. /Per Jessen, Zürich -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Per Jessen wrote:
Per Jessen wrote:
Check out the statserial utility; statserial will show the status of the pins of the serial port, like a software breakout box.
Good one - thanks Adam. I'll let you know.
The main difference between a working connection (null-modem to another device) is that DCD is raised, whereas it isn't when I try the SAN switch.
I haven't been able to try a straight through cable though - I need a gender bender.
OK, problem solved - it needed a straight through cable, not a null-modem. Thanks for your advice everyone. /Per Jessen, Zürich -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Adam Williams wrote:
Do you have a breakout box so you can test the port and cable? The cable is working. I use it for a couple of headless systems too. Are you sure it needs a null-modem? No, that's one thing I'm not certain about - the port on the switch is male, as is the port on the host .>This is one of the reasons you may want a break out box. There is no hard standard for such connections and some manufacturers use a male connector, where others would use a female. With a break out box, you can see which pins are used for transmit & receive and wire accordingly.
Check out the statserial utility; statserial will show the status of the pins of the serial port, like a software breakout box.
No software can tell you how a connector is wired. You need the break out box to see where the transmit and receive pins are. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (6)
-
Adam Williams -
Carl Hartung -
James Knott -
Mike -
Per Jessen -
Tom Patton