US20090187924A1 - Resolving SAS timing issues for long-distance SAS extender - Google Patents
Resolving SAS timing issues for long-distance SAS extender Download PDFInfo
- Publication number
- US20090187924A1 US20090187924A1 US12/342,069 US34206908A US2009187924A1 US 20090187924 A1 US20090187924 A1 US 20090187924A1 US 34206908 A US34206908 A US 34206908A US 2009187924 A1 US2009187924 A1 US 2009187924A1
- Authority
- US
- United States
- Prior art keywords
- small computer
- serial attached
- computer module
- attached small
- module interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/40—Bus structure
- G06F13/4004—Coupling between buses
- G06F13/4027—Coupling between buses using bus bridges
- G06F13/4045—Coupling between buses using bus bridges where the bus bridge performs an extender function
Definitions
- the SCSI adapter devices and the SCSI controller devices for peripherals are simple and cost effective, highly standardized, and often built into the computers and peripherals designed for the bus.
- Each device on the bus has a priority, and the highest priority device for communication control has to win the rights for the use of the bus.
- the negotiation for the control of the bus is conducted within a predetermined time window to all devices, but each SCSI device on the bus acts independently for the detection of the time-window.
- SAS Serial Attached SCSI
- FC Fiber Channel interface
- FIG. 1 is a schematic diagram of the SAS Extender.
- FIG. 2 is a data flow diagram showing every step that the SAS Extender follows.
- FIG. 3 is a data flow diagram (continuation of FIG. 2 ).
- FIG. 4 is a data flow diagram (continuation of FIGS. 2 and 3 ).
- FIG. 1 shows the topology of the SAS extender.
- Initiator 110 sends SAS traffic over SAS link 102 , where it is encapsulated within fibre channel frames by SAS Extender 120 A before forwarding over fibre channel link 104 to SAS extender 120 B, where the fibre channel encapsulation is removed and the SAS traffic is forwarded to SAS target 112 over SAS link 106 .
- SAS Target 112 sends traffic over SAS link 106 to SAS Extender 120 B, which encapsulates the SAS traffic in a fibre channel frame and transmits over fibre channel link 104 to SAS Extender 120 A, which removes the fibre channel encapsulation and forwards the traffic to the SAS initiator 110 over SAS link 102 .
- a problem arises when the length of the fibre channel link is increased beyond approximately 100 meters, and the SAS timers go off before the response can make the trip back.
- Our invention alleviates this problem by responding 7 immediately to the SAS traffic that requires it, and forwards traffic that does not.
- SAS extender emulating SAS expander: When a Report General command is received by the SAS extender 120 over a SAS link, it responds indicating that it supports an expander. This allows the SAS extender to use the AIP primitive to indicate that an arbitration is in progress on the remote link, even though it may not be. This resets the Open Address timer so that it does not expire before receiving an Open Accept from the remote link (the target).
- SAS extender emulates a SAS expander, it does not do discovery, but instead requires other expanders to update its routing table as known in the art.
- a table is used to look at incoming SAS traffic to determine whether it must be immediately responded to as well as passed on to the remote link, or simply passed on to the remote link. In the case of traffic responded to immediately, the SAS extender then waits for the appropriate response from the remote link before proceeding.
- FIGS. 1 , 2 and 3 are complementary and they are a complete flow diagram of the invention.
- the process begins at step 201 , and flows to step 202 , where it checks for fibre channel link traffic (traffic from FC 104 to the extender 120 A). If fibre channel traffic is detected (yes), the process flows to step 270 , where the encapsulation is removed and the unencapsulated SAS traffic is forwarded via the SAS link 102 . The process then returns to check again.
- fibre channel link traffic traffic from FC 104 to the extender 120 A. If fibre channel traffic is detected (yes), the process flows to step 270 , where the encapsulation is removed and the unencapsulated SAS traffic is forwarded via the SAS link 102 . The process then returns to check again.
- step 202 If in step 202 no fibre channel traffic is detected (no), then the process moves to step 203 , where it checks for SAS/SATA traffic. If SAS/SATA traffic has not been received (no), it returns to step 202 . If SAS/SATA traffic has been received (yes), the process moves to step 204 , where it checks whether an IDENTIFY frame has been received. If an IDENTIFY frame has been received (yes), then the process moves to step 220 , and the extender responds as an expander. The process then returns to step 202 , where it continues as previously described.
- step 204 traffic is received but it is not an IDENTIFY frame (no)
- step 206 it checks for an OPEN ADDRESS frame. If the traffic received is an OPEN ADDRESS frame (yes), the process flows to step 222 , and the frame is encapsulated and forwarded to the fibre channel link.
- step 224 where AIP is sent to the initiator 110 via the SAS link 102 .
- step 226 it checks whether an OPEN ACCEPT has been received on the fibre channel link 104 . If an OPEN ACCEPT has not been received (no), the process returns to step 224 to send another AIP. If an OPEN ACCEPT has been received (yes), the process returns to step 202 as described previously.
- step 206 If in step 206 the traffic received is not an OPEN ADDRESS frame (no), then the process flows to step 208 , where it checks for an SMP frame. If the traffic is an SMP frame (yes), it then determines the type of SMP frame. In step 400 , it checks if the SMP frame is a REPORT GENERAL frame. If it is a REPORT GENERAL frame (yes), then the process moves to step 412 , where the extender responds to the frame as known in the art, indicating that the extender is a SAS expander with the Externally Configurable Route Table bit set to one. The process then returns to step 202 .
- step 400 If in step 400 the SMP frame is not a REPORT GENERAL frame, the process flows to step 402 , where it checks if the frame is a DISCOVER or DISCOVER LIST frame. If it is a DISCOVER or DISCOVER LIST frame (yes), the process moves to step 410 , where it responds with its routing table as known in the art. The process then returns to step 202 .
- step 402 If in step 402 , the frame is not a DISCOVER or DISCOVER LIST frame (no), then the process flows to step 404 , where it checks if the frame is a CONFIGURE ROUTE INFO command. If the traffic is a CONFIG ROUTE INFO command (yes), the process flows to step 408 , where it receives and updates it's routing table. The process then returns to step 202 .
- step 404 If in step 404 the SMP command is not a CONFIG ROUTE INFO command, the process goes to step 406 , where the extender responds with SMP COMMAND NOT SUPPORTED as known in the art. The process then returns to step 202 .
- step 208 If in step 208 the traffic is not an SMP command (no), the process moves to step 210 , where it checks for a BREAK command. If the traffic is a BREAK command (yes), then the process flows to step 230 , where it responds via the SAS/SATA link 102 with a BREAK REPLY, and encapsulates and forwards the BREAK command via the fibre channel link 104 . The process then returns to step 202 .
- step 210 If in step 210 the traffic is not a BREAK command (no), the process moves to step 300 , where it checks for a CLOSE command. If the received traffic is a CLOSE primitive (yes), the process continues at step 302 , where it returns the CLOSE primitive via the SAS/SATA link, and then encapsulates and forwards the CLOSE primitive via the fibre channel link. The process then moves to step 304 , where it looks for a corresponding CLOSE primitive to be received via the fibre channel link. If a CLOSE primitive is not received via the fibre channel link (no), the process returns to check again. If a CLOSE primitive is received (yes), the process discards the CLOSE primitive rather than forward it in step 314 , and then returns to step 202 .
- step 300 If in step 300 the traffic received is not a CLOSE primitive (no) the process moves to step 306 , where if checks if the received traffic is an ACK, a NAK, or a BREAK REPLY primitive. If yes, then the process flows to step 308 , where the traffic is discarded, and the process then returns to step 202 .
- step 306 If in step 306 the traffic is not an ACK, a NAK, or a BREAK REPLY primitive (no), then the process moves to step 318 , where it checks for a Hard Reset. If the received traffic is a Hard Reset (yes), the process moves to step 310 , where it performs a fibre channel logout on the fibre channel link and then returns to step 202 .
- step 318 If in step 318 the traffic is not a Hard Reset (no), then the process flows to step 316 , where it checks whether the received traffic is valid traffic. If the received traffic is valid (yes), the process moves to step 312 , where it encapsulates the traffic and forwards it via the fibre channel link. The process then returns to step 202 .
- step 316 If in step 316 the received traffic is not valid (no), the process moves to step 320 , where it discards the traffic and returns to step 202 .
- a method for resolving serial attached small computer system interface timing issues for long distance serial attached small computer system interface extender comprising the steps of:
- first serial attached small computer system interface extender is connected to a second serial attached small computer system interface extender, through a fibre channel;
- the first serial attached small computer system interface extender emulating a serial attached small computer system interface expander
- the first serial attached small computer system interface extender having a lookup table
- the first serial attached small computer system interface extender determining whether to immediately respond on the first serial attached small computer system interface link, to encapsulate and forward the serial attached small computer system interface traffic toward a serial attached small computer system interface target via the fibre channel, or to do both to immediately respond on the first serial attached small computer system interface link and to encapsulate and forward the serial attached small computer system interface traffic toward the serial attached small computer system interface target via the fibre channel;
- first serial attached small computer system interface extender immediately responding on the first serial attached small computer system interface link and forwarding the serial attached small computer system interface traffic toward the serial attached small computer system interface target, the first serial attached small computer system interface extender monitoring for a corresponding response, coming via the fibre link, and handling the corresponding response, based on the lookup table;
- the first serial attached small computer system interface extender encapsulating the serial attached small computer system interface traffic within frames of the fibre channel
- serial attached small computer system interface traffic to the serial attached small computer system interface target, over a second serial attached small computer system interface link.
Abstract
This invention extends the distance at which a SAS extender can function. The distance is increased a large amount over the traditional 10 meters. As a result timers will not go off before the response can make a trip back. This is accomplished by emulating as a SAS expander, using SAS AIP's (Arbitration In Progress), and using a lookup table to determine which SAS events must be responded to immediately and which ones to be passed on to the remote link.
Description
- This is a Cont. of another Accelerated Exam. application Ser. No. 12/015,655, filed Jan. 17, 2008, to be issued in December 2008, as a US patent, with the same title, inventors, and assignee, IBM.
- The SCSI adapter devices and the SCSI controller devices for peripherals are simple and cost effective, highly standardized, and often built into the computers and peripherals designed for the bus. Each device on the bus has a priority, and the highest priority device for communication control has to win the rights for the use of the bus. The negotiation for the control of the bus is conducted within a predetermined time window to all devices, but each SCSI device on the bus acts independently for the detection of the time-window.
- Serial Attached SCSI (SAS) is the next generation of the Small Computer System Interface (SCSI), used for connecting storage devices to a computer system. It has been developed as an alternative to the Fiber Channel interface (FC), offering similar performance and reduced cost, at the expense of connectivity and scalability. Because it is an electrical technology as opposed to optical, it has a distance limitation of 10 meters, making it useful only inside cabinets and for peripherals that are physically located next to the computer system that uses the interface. It would be useful to have a means of using the SAS technology without having to sacrifice the ability to have remote connectivity for storage. The timings for SAS are such that the propagation delay associated with long distance links over one hundred meters will become problematic without a method to keep the SAS timers from popping.
- The distance at which a SAS extender can function is greatly increased beyond the traditional 10 meters and thus the timers will not go off before the response can make a trip back. This is accomplished by:
-
- emulating as a SAS expander,
- using SAS AIP's (Arbitration In Progress), and
- using a lookup table to determine which SAS events must be responded to immediately and which ones to be passed on to the remote link.
-
FIG. 1 is a schematic diagram of the SAS Extender. -
FIG. 2 is a data flow diagram showing every step that the SAS Extender follows. -
FIG. 3 is a data flow diagram (continuation ofFIG. 2 ). -
FIG. 4 is a data flow diagram (continuation ofFIGS. 2 and 3 ). -
FIG. 1 shows the topology of the SAS extender.Initiator 110 sends SAS traffic overSAS link 102, where it is encapsulated within fibre channel frames by SAS Extender 120A before forwarding overfibre channel link 104 to SAS extender 120B, where the fibre channel encapsulation is removed and the SAS traffic is forwarded toSAS target 112 overSAS link 106. When responding, SAS Target 112 sends traffic overSAS link 106 to SAS Extender 120B, which encapsulates the SAS traffic in a fibre channel frame and transmits overfibre channel link 104 to SAS Extender 120A, which removes the fibre channel encapsulation and forwards the traffic to theSAS initiator 110 overSAS link 102. A problem arises when the length of the fibre channel link is increased beyond approximately 100 meters, and the SAS timers go off before the response can make the trip back. Our invention alleviates this problem by responding 7 immediately to the SAS traffic that requires it, and forwards traffic that does not. - SAS extender emulating SAS expander: When a Report General command is received by the
SAS extender 120 over a SAS link, it responds indicating that it supports an expander. This allows the SAS extender to use the AIP primitive to indicate that an arbitration is in progress on the remote link, even though it may not be. This resets the Open Address timer so that it does not expire before receiving an Open Accept from the remote link (the target). - Even though the SAS extender emulates a SAS expander, it does not do discovery, but instead requires other expanders to update its routing table as known in the art.
- A table is used to look at incoming SAS traffic to determine whether it must be immediately responded to as well as passed on to the remote link, or simply passed on to the remote link. In the case of traffic responded to immediately, the SAS extender then waits for the appropriate response from the remote link before proceeding.
-
FIGS. 1 , 2 and 3 are complementary and they are a complete flow diagram of the invention. - The process begins at
step 201, and flows tostep 202, where it checks for fibre channel link traffic (traffic from FC 104 to the extender 120A). If fibre channel traffic is detected (yes), the process flows tostep 270, where the encapsulation is removed and the unencapsulated SAS traffic is forwarded via theSAS link 102. The process then returns to check again. - If in
step 202 no fibre channel traffic is detected (no), then the process moves tostep 203, where it checks for SAS/SATA traffic. If SAS/SATA traffic has not been received (no), it returns tostep 202. If SAS/SATA traffic has been received (yes), the process moves tostep 204, where it checks whether an IDENTIFY frame has been received. If an IDENTIFY frame has been received (yes), then the process moves tostep 220, and the extender responds as an expander. The process then returns tostep 202, where it continues as previously described. - If in
step 204, traffic is received but it is not an IDENTIFY frame (no), then the process continues atstep 206, where it checks for an OPEN ADDRESS frame. If the traffic received is an OPEN ADDRESS frame (yes), the process flows tostep 222, and the frame is encapsulated and forwarded to the fibre channel link. The process continues atstep 224, where AIP is sent to theinitiator 110 via the SASlink 102. The process then flows tostep 226, where it checks whether an OPEN ACCEPT has been received on thefibre channel link 104. If an OPEN ACCEPT has not been received (no), the process returns tostep 224 to send another AIP. If an OPEN ACCEPT has been received (yes), the process returns tostep 202 as described previously. - If in
step 206 the traffic received is not an OPEN ADDRESS frame (no), then the process flows tostep 208, where it checks for an SMP frame. If the traffic is an SMP frame (yes), it then determines the type of SMP frame. Instep 400, it checks if the SMP frame is a REPORT GENERAL frame. If it is a REPORT GENERAL frame (yes), then the process moves tostep 412, where the extender responds to the frame as known in the art, indicating that the extender is a SAS expander with the Externally Configurable Route Table bit set to one. The process then returns tostep 202. - If in
step 400 the SMP frame is not a REPORT GENERAL frame, the process flows tostep 402, where it checks if the frame is a DISCOVER or DISCOVER LIST frame. If it is a DISCOVER or DISCOVER LIST frame (yes), the process moves tostep 410, where it responds with its routing table as known in the art. The process then returns tostep 202. - If in
step 402, the frame is not a DISCOVER or DISCOVER LIST frame (no), then the process flows tostep 404, where it checks if the frame is a CONFIGURE ROUTE INFO command. If the traffic is a CONFIG ROUTE INFO command (yes), the process flows tostep 408, where it receives and updates it's routing table. The process then returns tostep 202. - If in
step 404 the SMP command is not a CONFIG ROUTE INFO command, the process goes tostep 406, where the extender responds with SMP COMMAND NOT SUPPORTED as known in the art. The process then returns tostep 202. - If in
step 208 the traffic is not an SMP command (no), the process moves tostep 210, where it checks for a BREAK command. If the traffic is a BREAK command (yes), then the process flows tostep 230, where it responds via the SAS/SATA link 102 with a BREAK REPLY, and encapsulates and forwards the BREAK command via thefibre channel link 104. The process then returns to step 202. - If in
step 210 the traffic is not a BREAK command (no), the process moves to step 300, where it checks for a CLOSE command. If the received traffic is a CLOSE primitive (yes), the process continues atstep 302, where it returns the CLOSE primitive via the SAS/SATA link, and then encapsulates and forwards the CLOSE primitive via the fibre channel link. The process then moves to step 304, where it looks for a corresponding CLOSE primitive to be received via the fibre channel link. If a CLOSE primitive is not received via the fibre channel link (no), the process returns to check again. If a CLOSE primitive is received (yes), the process discards the CLOSE primitive rather than forward it instep 314, and then returns to step 202. - If in
step 300 the traffic received is not a CLOSE primitive (no) the process moves to step 306, where if checks if the received traffic is an ACK, a NAK, or a BREAK REPLY primitive. If yes, then the process flows to step 308, where the traffic is discarded, and the process then returns to step 202. - If in
step 306 the traffic is not an ACK, a NAK, or a BREAK REPLY primitive (no), then the process moves to step 318, where it checks for a Hard Reset. If the received traffic is a Hard Reset (yes), the process moves to step 310, where it performs a fibre channel logout on the fibre channel link and then returns to step 202. - If in
step 318 the traffic is not a Hard Reset (no), then the process flows to step 316, where it checks whether the received traffic is valid traffic. If the received traffic is valid (yes), the process moves to step 312, where it encapsulates the traffic and forwards it via the fibre channel link. The process then returns to step 202. - If in
step 316 the received traffic is not valid (no), the process moves to step 320, where it discards the traffic and returns to step 202. - Below is the preferred embodiment of the invention:
- A method for resolving serial attached small computer system interface timing issues for long distance serial attached small computer system interface extender, the method comprising the steps of:
- an initiator sending serial attached small computer system interface traffic, over a first serial attached small computer system interface link, to a first serial attached small computer system interface extender;
- wherein the first serial attached small computer system interface extender is connected to a second serial attached small computer system interface extender, through a fibre channel;
- the first serial attached small computer system interface extender emulating a serial attached small computer system interface expander;
- responding to a report general command received from the first serial attached small computer system interface link;
- indicating that the first serial attached small computer system interface extender is a serial attached small computer system interface expander, by setting an externally configurable route table bit;
- wherein the first serial attached small computer system interface extender having a lookup table;
- based on the lookup table, the first serial attached small computer system interface extender determining whether to immediately respond on the first serial attached small computer system interface link, to encapsulate and forward the serial attached small computer system interface traffic toward a serial attached small computer system interface target via the fibre channel, or to do both to immediately respond on the first serial attached small computer system interface link and to encapsulate and forward the serial attached small computer system interface traffic toward the serial attached small computer system interface target via the fibre channel;
- in case of first serial attached small computer system interface extender immediately responding on the first serial attached small computer system interface link and forwarding the serial attached small computer system interface traffic toward the serial attached small computer system interface target, the first serial attached small computer system interface extender monitoring for a corresponding response, coming via the fibre link, and handling the corresponding response, based on the lookup table;
- the first serial attached small computer system interface extender encapsulating the serial attached small computer system interface traffic within frames of the fibre channel;
- forwarding the encapsulated the serial attached small computer system interface traffic to the second serial attached small computer system interface extender;
- removing the encapsulated the serial attached small computer system interface traffic; and
- forwarding the serial attached small computer system interface traffic to the serial attached small computer system interface target, over a second serial attached small computer system interface link.
- Any variations of the above teaching are also intended to be covered by this patent application.
Claims (1)
1. A system for resolving serial attached small computer module interface timing issues for long distance serial attached small computer module interface extender, said system comprising:
a lookup table; and
a first serial attached small computer module interface extender;
wherein an initiator sends serial attached small computer module interface traffic, over a first serial attached small computer module interface link, to said first serial attached small computer module interface extender;
said first serial attached small computer module interface extender is connected to a second serial attached small computer module interface extender, through a fibre channel;
said first serial attached small computer module interface extender emulates a serial attached small computer module interface expander;
a report general command received from said first serial attached small computer module interface link is responded to;
wherein it is indicated that said first serial attached small computer module interface extender is the serial attached small computer module interface expander, by setting an externally configurable route table bit;
said first serial attached small computer module interface extender having said lookup table;
based on said lookup table, said first serial attached small computer module interface extender determines whether to immediately respond on said first serial attached small computer module interface link, to encapsulate and forward said serial attached small computer module interface traffic toward a serial attached small computer module interface target via said fibre channel, or to do both to immediately respond on said first serial attached small computer module interface link and to encapsulate and forward said serial attached small computer module interface traffic toward said serial attached small computer module interface target via said fibre channel;
based on said lookup table, for resolving the timing issues including a first serial attached small computer module interface timer expiring due to the long distance interconnection between the first and the second serial attached small computer module interface extender, when the first serial attached small computer module interface extender immediately responding on said first serial attached small computer module interface link and encapsulating and forwarding said serial attached small computer module interface traffic toward said serial attached small computer module interface target, said first serial attached small computer module interface extender monitors for a corresponding response, coming via said fibre link, and handles said corresponding response, based on said lookup table;
said first serial attached small computer module interface extender encapsulates said serial attached small computer module interface traffic within frames of said fibre channel;
said encapsulated said serial attached small computer module interface traffic is forwarded to said second serial attached small computer module interface extender;
said encapsulated said serial attached small computer module interface traffic is removed; and
said serial attached small computer module interface traffic is forwarded to said serial attached small computer module interface target, over a second serial attached small computer module interface link.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/342,069 US20090187924A1 (en) | 2008-01-17 | 2008-12-23 | Resolving SAS timing issues for long-distance SAS extender |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/015,655 US7475163B1 (en) | 2008-01-17 | 2008-01-17 | Method and system for resolving SAS timing issues for long-distance SAS extender |
US12/342,069 US20090187924A1 (en) | 2008-01-17 | 2008-12-23 | Resolving SAS timing issues for long-distance SAS extender |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/015,655 Continuation US7475163B1 (en) | 2008-01-17 | 2008-01-17 | Method and system for resolving SAS timing issues for long-distance SAS extender |
Publications (1)
Publication Number | Publication Date |
---|---|
US20090187924A1 true US20090187924A1 (en) | 2009-07-23 |
Family
ID=40175041
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/015,655 Expired - Fee Related US7475163B1 (en) | 2008-01-17 | 2008-01-17 | Method and system for resolving SAS timing issues for long-distance SAS extender |
US12/342,069 Abandoned US20090187924A1 (en) | 2008-01-17 | 2008-12-23 | Resolving SAS timing issues for long-distance SAS extender |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/015,655 Expired - Fee Related US7475163B1 (en) | 2008-01-17 | 2008-01-17 | Method and system for resolving SAS timing issues for long-distance SAS extender |
Country Status (1)
Country | Link |
---|---|
US (2) | US7475163B1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090248889A1 (en) * | 2008-03-25 | 2009-10-01 | International Business Machines Corporation | Serial attached scsi and serial ata wide port tunnelling through a fibre channel connection |
US20090248884A1 (en) * | 2008-03-25 | 2009-10-01 | International Business Machines Corporation | Distance extender for serial attached scsi and serial ata |
US20110302368A1 (en) * | 2010-06-02 | 2011-12-08 | Hitachi, Ltd. | Storage system having sas as its backend communication standard |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101515871B (en) * | 2009-03-27 | 2011-04-20 | 杭州华三通信技术有限公司 | Method for inhibiting change of state of SAS link and monitoring entity |
US9021173B2 (en) | 2012-10-26 | 2015-04-28 | International Business Machines Corporation | High speed differential wiring strategy for serially attached SCSI systems |
Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US921816A (en) * | 1907-07-23 | 1909-05-18 | John T Everett | Pipe clamp or coupling collar. |
US5528765A (en) * | 1993-03-15 | 1996-06-18 | R. C. Baker & Associates Ltd. | SCSI bus extension system for controlling individual arbitration on interlinked SCSI bus segments |
US6185651B1 (en) * | 1997-11-05 | 2001-02-06 | Compaq Computer Corp | SCSI bus extender utilizing tagged queuing in a multi-initiator environment |
US6430632B1 (en) * | 1999-05-28 | 2002-08-06 | International Business Machines Corporation | Data management small computer system interface (SCSI) extender for extending SCSI communications between SCSI interfaces located relatively far apart |
US6650656B2 (en) * | 2001-02-28 | 2003-11-18 | Crossroads Systems, Inc. | Method and system for reconciling extended copy command target descriptor lengths |
US20040193736A1 (en) * | 2003-03-26 | 2004-09-30 | Brea Technologies, Inc. | Expedited completion done messages, method and apparatus |
US6848007B1 (en) * | 1999-11-12 | 2005-01-25 | Crossroads Systems, Inc. | System for mapping addresses of SCSI devices between plurality of SANs that can dynamically map SCSI device addresses across a SAN extender |
US20060004935A1 (en) * | 2004-06-30 | 2006-01-05 | Pak-Lung Seto | Multi-protocol bridge |
US7035952B2 (en) * | 2003-09-24 | 2006-04-25 | Hewlett-Packard Development Company, L.P. | System having storage subsystems and a link coupling the storage subsystems |
US20070121621A1 (en) * | 2005-11-30 | 2007-05-31 | Michael Moretti | Integrated active-active fibre channel capability in SATA and SAS devices |
US7308534B2 (en) * | 2005-01-13 | 2007-12-11 | Hitachi, Ltd. | Apparatus and method for managing a plurality of kinds of storage devices |
US20080162773A1 (en) * | 2006-12-29 | 2008-07-03 | Clegg Roger T | Apparatus and methods for multiple unidirectional virtual connections among sas devices |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5921816A (en) | 1995-11-13 | 1999-07-13 | Larabell; Henri | SCSI adapter for a computer system having an internal SCSI bus |
-
2008
- 2008-01-17 US US12/015,655 patent/US7475163B1/en not_active Expired - Fee Related
- 2008-12-23 US US12/342,069 patent/US20090187924A1/en not_active Abandoned
Patent Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US921816A (en) * | 1907-07-23 | 1909-05-18 | John T Everett | Pipe clamp or coupling collar. |
US5528765A (en) * | 1993-03-15 | 1996-06-18 | R. C. Baker & Associates Ltd. | SCSI bus extension system for controlling individual arbitration on interlinked SCSI bus segments |
US6185651B1 (en) * | 1997-11-05 | 2001-02-06 | Compaq Computer Corp | SCSI bus extender utilizing tagged queuing in a multi-initiator environment |
US6430632B1 (en) * | 1999-05-28 | 2002-08-06 | International Business Machines Corporation | Data management small computer system interface (SCSI) extender for extending SCSI communications between SCSI interfaces located relatively far apart |
US6848007B1 (en) * | 1999-11-12 | 2005-01-25 | Crossroads Systems, Inc. | System for mapping addresses of SCSI devices between plurality of SANs that can dynamically map SCSI device addresses across a SAN extender |
US6650656B2 (en) * | 2001-02-28 | 2003-11-18 | Crossroads Systems, Inc. | Method and system for reconciling extended copy command target descriptor lengths |
US20040193736A1 (en) * | 2003-03-26 | 2004-09-30 | Brea Technologies, Inc. | Expedited completion done messages, method and apparatus |
US7035952B2 (en) * | 2003-09-24 | 2006-04-25 | Hewlett-Packard Development Company, L.P. | System having storage subsystems and a link coupling the storage subsystems |
US20060004935A1 (en) * | 2004-06-30 | 2006-01-05 | Pak-Lung Seto | Multi-protocol bridge |
US7308534B2 (en) * | 2005-01-13 | 2007-12-11 | Hitachi, Ltd. | Apparatus and method for managing a plurality of kinds of storage devices |
US20070121621A1 (en) * | 2005-11-30 | 2007-05-31 | Michael Moretti | Integrated active-active fibre channel capability in SATA and SAS devices |
US20080162773A1 (en) * | 2006-12-29 | 2008-07-03 | Clegg Roger T | Apparatus and methods for multiple unidirectional virtual connections among sas devices |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090248889A1 (en) * | 2008-03-25 | 2009-10-01 | International Business Machines Corporation | Serial attached scsi and serial ata wide port tunnelling through a fibre channel connection |
US20090248884A1 (en) * | 2008-03-25 | 2009-10-01 | International Business Machines Corporation | Distance extender for serial attached scsi and serial ata |
US7949789B2 (en) * | 2008-03-25 | 2011-05-24 | International Business Machines Corporation | Distance extender for serial attached SCSI and serial ATA |
US8019895B2 (en) * | 2008-03-25 | 2011-09-13 | International Business Machines Corporation | Serial attached SCSI and serial ATA wide port tunnelling through a fibre channel connection |
US20110289233A1 (en) * | 2008-03-25 | 2011-11-24 | International Business Machines Corporation | Serial attached scsi and serial ata wide port tunnelling through a fibre channel connection |
US8516154B2 (en) * | 2008-03-25 | 2013-08-20 | International Business Machines Corporation | Serial attached SCSI and serial ATA wide port tunnelling through a fibre channel connection |
US20110302368A1 (en) * | 2010-06-02 | 2011-12-08 | Hitachi, Ltd. | Storage system having sas as its backend communication standard |
US8463949B2 (en) * | 2010-06-02 | 2013-06-11 | Hitachi, Ltd. | Storage system having SAS as its backend communication standard |
US8843680B2 (en) | 2010-06-02 | 2014-09-23 | Hitachi, Ltd. | Storage system having SAS as its backend communication standard |
Also Published As
Publication number | Publication date |
---|---|
US7475163B1 (en) | 2009-01-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1697850B1 (en) | Managing transmissions between devices | |
US7587536B2 (en) | Method and apparatus for distributing USB hub functions across a network | |
JP5103371B2 (en) | Method and apparatus for improving the performance of USB mass storage devices in the presence of long transmission delays | |
US11269316B2 (en) | Intelligent controller and sensor network bus, system and method including smart compliant actuator module | |
US20080005395A1 (en) | Adapter to convert USB device into WUSB device | |
TW200821857A (en) | Dynamic power cycling | |
US7475163B1 (en) | Method and system for resolving SAS timing issues for long-distance SAS extender | |
CN106959935B (en) | Method compatible with I2C communication and IPMB communication | |
TW200815987A (en) | Device connection system and device connection method | |
JP6550192B2 (en) | Network device | |
TW201447595A (en) | System and method of sending PCI Express data over Ethernet connection | |
US7908404B1 (en) | Method and system for managing network and storage data | |
JP6272465B2 (en) | Storage system, method and apparatus for processing operational requests | |
US20150358202A1 (en) | Fibre channel gateway system | |
CN107222256A (en) | The implementation method that a kind of online heavy chain of SRIO optical fiber links based on FPGA connects | |
US9882737B2 (en) | Network system | |
CN104536853B (en) | A kind of device ensureing dual controller storage device resource continuous availability | |
US7047346B2 (en) | Transparent fiber channel concentrator for point to point technologies | |
CN108885484B (en) | Remote terminal device, control method thereof, computer system, and recording medium | |
US9755892B2 (en) | Integrated device managment over Ethernet network | |
CN108008657B (en) | Load balancing redundancy switching system with control panel and switching panel buses directly connected | |
US20150350014A1 (en) | Networking implementation using a converged high speed input/output fabric technology | |
JP6358959B2 (en) | Hierarchical network with regular redundant links | |
US8954623B2 (en) | Universal Serial Bus devices supporting super speed and non-super speed connections for communication with a host device and methods using the same | |
JP2006268610A (en) | Fault isolating method, communication apparatus including fault isolating function, and program |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KLEIN, CRAIG A;WINARSKI, DANIEL JAMES;JOHNSON, TIMOTHY ALLEN;AND OTHERS;REEL/FRAME:022050/0864 Effective date: 20080116 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE |