Pinagem Cabo Serial Db9 Rj45
Hi Everyone, I have an Equallogic storage array to use for testing that I believe is a ps100e, with two blue sata controllers on the back that have RJ45 serial connections. Nothing I've used so far has gotten any kind of traffic from them, so can anyone help me out with a pinout of the console cable that was included with the devices? (All I got was the machine itself).
Hello i am in the middle of setting up my lab and I have ran into a bit of a problem. My motherboard is new and has no seiral ports, and the cable itself is not long enough to reach from my lab to my PC, so what i am asking is there a colsole cable that is DB9 to USB or do i have to get a longer DB9 cable then buy a DB9 to usb converter? The management ports are 10/100/1000 Mbps-capable; you can also use either straight-through or cross-over twisted-pair cables since the ports also support MDI/MDIX. • The console and auxiliary ports are serial ports and require the use of a flat rollover cable for terminal server connectivity (and a DB9 connector for.
I've seen a couple of sketchy places online to buy them, but I'm in a bit of a hurry and don't have much of a budget, so I was hoping to make one if they're non-standard. Here's the pinout and baud settings. Make sure that flowcontrol is off on the serial port. This info can be found on the Equallogic support website.
Solution Title Serial Console Cable, Identification for Type I, II Controllers, Pinouts for RJ-45 connector Solution Details Type-1: FRU PN=95-0444. Cable 'dongle' will have a white ID tag with 51-0003-02 marked on it. It is 10 inches long, black, with silver DB-9(M) and a micro DB-9 on the other end. You can order the dongle as a Molex part number, by looking for it on google. You will also need a Null modem cable to go with it if you don't have one, easy to find, even most Radio Shack's have them.
Type-2: FRU PN 95-0517. Cable will have a white ID tag with 51-0008 marked on it. It is 10 feet long, black with a DB-9(F) and the RJ-45 on the other end Here is the pinout for the RJ-45 serial connector used on the EqualLogic Type-2 (SATA 2 Control Module): 1 - DTR (out) 2 - CTS (in) 3 - Chassis Gnd 4 - RxD (in) 5 - TxD (out) 6 - Sig Gnd 7 - RTS (out) 8 - DSR (in) In current firmware versions we do not purposefully set, or respond to, any of the control signals (DTR, CTS, RTS, DSR), so you should either configure the device you are connecting so that it ignores them, or provide local loopbacks as needed.
The serial settings are: 9600 baud, no parity, 8 data bits, 1 stop bit, no flow control. Here's the pinout and baud settings. Make sure that flowcontrol is off on the serial port. This info can be found on the Equallogic support website. Solution Title Serial Console Cable, Identification for Type I, II Controllers, Pinouts for RJ-45 connector Solution Details Type-1: FRU PN=95-0444. Cable 'dongle' will have a white ID tag with 51-0003-02 marked on it.
Pinagem Cabo Serial Db9 Rj45
It is 10 inches long, black, with silver DB-9(M) and a micro DB-9 on the other end. You can order the dongle as a Molex part number, by looking for it on google. You will also need a Null modem cable to go with it if you don't have one, easy to find, even most Radio Shack's have them. Type-2: FRU PN 95-0517. Cable will have a white ID tag with 51-0008 marked on it.
It is 10 feet long, black with a DB-9(F) and the RJ-45 on the other end Here is the pinout for the RJ-45 serial connector used on the EqualLogic Type-2 (SATA 2 Control Module): 1 - DTR (out) 2 - CTS (in) 3 - Chassis Gnd 4 - RxD (in) 5 - TxD (out) 6 - Sig Gnd 7 - RTS (out) 8 - DSR (in) In current firmware versions we do not purposefully set, or respond to, any of the control signals (DTR, CTS, RTS, DSR), so you should either configure the device you are connecting so that it ignores them, or provide local loopbacks as needed. The serial settings are: 9600 baud, no parity, 8 data bits, 1 stop bit, no flow control. Controller Type-1: FRU PN=95-0444. Cable 'dongle' will have a white ID tag with 51-0003-02 marked on it. It is 10 inches long, black, with silver DB-9(M) and a micro DB-9 on the other end. You can order the dongle as a Molex part number, by looking for it on google. You will also need a Null modem cable to go with it if you don't have one, easy to find, even most Radio Shack's have them.
The Micro-DB9 serial connector for type-1 EqualLogic controllers is a straight-through connector. Micro-DB9-male - DB9-male 1 - 1 2 - 2 3 - 3 4 - 4 5 - 5 6 - 6 7 - 7 8 - 8 9 - 9 To properly connect this cable to a PC serial port, you will need to supply a DB9F to DB9F null-modem cable Controller Type-2: FRU PN 95-0517.
Cable will have a white ID tag with 51-0008 marked on it. It is 10 feet long, black with a DB-9(F) and the RJ-45 on the other end Here is the pinout for the RJ-45 serial connector used on the EqualLogic Type-2 (SATA 2 Control Module): 1 - DTR (out) 2 - CTS (in) 3 - Chassis Gnd 4 - RxD (in) 5 - TxD (out) 6 - Sig Gnd 7 - RTS (out) 8 - DSR (in) In current firmware versions we do not purposefully set, or respond to, any of the control signals (DTR, CTS, RTS, DSR), so you should either configure the The serial settings are: 9600 baud, no parity, 8 data bits, 1 stop bit, no flow control. If interested in purchasing the Dell EqualLogic branded one, please check with EqualLogic Customer servcie to see if they are still available: Regards, Joe. Ok we have an old PS series array - 2 heads, 4 controllers. We have just relocated it to our new DC and purchased the required cable - followed the instructions, created a session using Putty and got signed on to the box. All fine for a few days. Then yesterday tried to sign on a couple of times (password incorrect) then restarted the Putty session - and now it will not accept any keyboard entry at all.
We rebooted the array and saw all the boot messages appear in the Putty session but still we are inhibited from entering any text. I've opened another Putty session to another box and that is fine. I've created a new putty session from scratch - still no joy.
I've tried the connection in the other management ports of the other controllers but that doesn't seem to work either. Anyone got a clue as to what the problem might be? Thanks Wayne.