US 7,051,147 B2Grant
Storage router and method for providing virtual local storage
Issue Date:2006-05-23
•39 Claims
•3 Drawing Sheets
Abstract
A storage router and storage network provide virtual local storage on remote storage devices to Fiber Channel devices. A plurality of Fiber Channel devices, such as workstations, are connected to a Fiber Channel transport medium, and a plurality of storage devices are connected to a second Fiber Channel transport medium. The storage router interfaces between the Fiber Channel transport media. The storage router maps between the workstations and the storage devices and implements access controls for storage space on the storage devices. The storage router then allows access from the workstations to the storage devices using native low level, block protocol in accordance with the mapping and the access controls.
Metadata
Assignee
- Crossroads Systems, Inc.
Inventors
- Geoffrey B. Hoese
- Jeffry T. Russell
Application Information
Application Number:US 10/658,163
Filing Date:2003-09-09
Priority Date:1997-12-31
Art Unit:2182
Classifications
IPC:
G06F13/00
Patent Drawings (3 sheets)
Description
Related Applications
[0001] This application is a continuation of and claims the benefit of the filing dates of U.S. patent application Ser. No. 10/081,110 by inventors Geoffrey B. Hoese and Jeffry T. Russell, entitled “Storage Router and Method for Providing Virtual Local Storage” filed on Feb. 22, 2002, now U.S. Pat. No. 6,789,152 which in turn is a continuation of U.S. application Ser. No. 09/354,682 by inventors Geoffrey B. Hoese and Jeffry T. Russell, entitled “Storage Router and Method for Providing Virtual Local Storage” filed on Jul. 15, 1999, now U.S. Pat. No. 6,421,753, which in turn is a continuation of U.S. patent application Ser. No. 09/001,799, filed on Dec. 31, 1997, now U.S. Pat. No. 5,941,972, and hereby incorporates these applications by reference in their entireties as if they had been fully set forth herein.
Technical Field of the Invention
[0002] This invention relates in general to network storage devices, and more particularly to a storage router and method for providing virtual local storage on remote SCSI storage devices to Fibre Channel devices.
Background of the Invention
[0003] Typical storage transport mediums provide for a relatively small number of devices to be attached over relatively short distances. One such transport medium is a Small Computer System Interface (SCSI) protocol, the structure and operation of which is generally well known as is described, for example, in the SCSI-1, SCSI-2 and SCSI-3 specifications. High speed serial interconnects provide enhanced capability to attach a large number of high speed devices to a common storage transport medium over large distances. One such serial interconnect is Fibre Channel, the structure and operation of which is described, for example, in Fibre Channel Physical and signaling Interface (FC-PH), ANSI X3.230 Fibre Channel Arbitrated Loop (FC-AL), and ANSI X3.272 Fibre Channel Private Loop Direct Attach (FC-PLDA).
[0004] Conventional computing devices, such as computer workstations, generally access storage locally or through network interconnects. Local storage typically consists of a disk drive, tape drive, CD-ROM drive or other storage device contained within, or locally connected to the workstation. The workstation provides a file system structure, that includes security controls, with access to the local storage device through native low level, block protocols. These protocols map directly to the mechanisms used by the storage device and consist of data requests without security controls. Network interconnects typically provide access for a large number of computing devices to data storage on a remote network server. The remote network server provides file system structure, access control, and other miscellaneous capabilities that include the network interface. Access to data through the network server is through network protocols that the server must translate into low level requests to the storage device. A workstation with access to the server storage must translate its file system protocols into network protocols that are used to communicate with the server. Consequently, from the perspective of a workstation, or other computing device, seeking to access such server data, the access is much slower than access to data on a local storage device.
Summary of the Invention
[0005] In accordance with the present invention, a storage router and method for providing virtual local storage on remote SCSI storage devices to Fibre Channel devices are disclosed that provide advantages over conventional network storage devices and methods.
[0006] According to one aspect of the present invention, a storage router and storage network provide virtual local storage on remote SCSI storage devices to Fibre Channel devices. A plurality of Fibre Channel devices, such as workstations, are connected to a Fibre Channel transport medium, and a plurality of SCSI storage devices are connected to a SCSI bus transport medium. The storage router interfaces between the Fibre Channel transport medium and the SCSI bus transport medium. The storage router maps between the workstations and the SCSI storage devices and implements access controls for storage space on the SCSI storage devices. The storage router then allows access from the workstations to the SCSI storage devices using native low level, block protocol in accordance with the mapping and the access controls.
[0007] According to another aspect of the present invention, virtual local storage on remote SCSI storage devices is provided to Fibre Channel devices. A Fibre Channel transport medium and a SCSI bus transport medium are interfaced with. A configuration is maintained for SCSI storage devices connected to the SCSI bus transport medium. The configuration maps between Fibre Channel devices and the SCSI storage devices and implements access controls for storage space on the SCSI storage devices. Access is then allowed from Fibre Channel initiator devices to SCSI storage devices using native low level, block protocol in accordance with the configuration.
[0008] A technical advantage of the present invention is the ability to centralize local storage for networked workstations without any cost of speed or overhead. Each workstation access its virtual local storage as if it work locally connected. Further, the centralized storage devices can be located in a significantly remote position even in excess of ten kilometers as defined by Fibre Channel standards.
[0009] Another technical advantage of the present invention is the ability to centrally control and administer storage space for connected users without limiting the speed with which the users can access local data. In addition, global access to data, backups, virus scanning and redundancy can be more easily accomplished by centrally located storage devices.
[0010] A further technical advantage of the present invention is providing support for SCSI storage devices as local storage for Fibre Channel hosts. In addition, the present invention helps to provide extended capabilities for Fibre Channel and for management of storage subsystems.
Brief Description of the Drawings
[0011] A more complete understanding of the present invention and the advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features, and wherein:
[0012] FIG. 1 is a block diagram of a conventional network that provides storage through a network server;
[0013] FIG. 2 is a block diagram of one embodiment of a storage network with a storage router that provides global access and routing;
[0014] FIG. 3 is a block diagram of one embodiment of a storage network with a storage router that provides virtual local storage;
[0015] FIG. 4 is a block diagram of one embodiment of the storage router of FIG. 3 ; and
[0016] FIG. 5 is a block diagram of one embodiment of data flow within the storage router of FIG. 4 .
Detailed Description of the Invention
[0017] FIG. 1 is a block diagram of a conventional network, indicated generally at 10, that provides access to storage through a network server. As shown, network 10 includes a plurality of workstations 12 interconnected with a network server 14 via a network transport medium 16. Each workstation 12 can generally comprise a processor, memory, input/output devices, storage devices and a network adapter as well as other common computer components. Network server 14 uses a SCSI bus 18 as a storage transport medium to interconnect with a plurality of storage devices 20 (tape drives, disk drives, etc.). In the embodiment of FIG. 1 , network transport medium 16 is an network connection and storage devices 20 comprise hard disk drives, although there are numerous alternate transport mediums and storage devices.
[0018] In network 10, each workstation 12 has access to its local storage device as well as network access to data on storage devices 20. The access to a local storage device is typically through native low level, block protocols. On the other hand, access by a workstation 12 to storage devices 20 requires the participation of network server 14 which implements a file system and transfers data to workstations 12 only through high level file system protocols. Only network server 14 communicates with storage devices 20 via native low level, block protocols. Consequently, the network access by workstations 12 through network server 14 is slow with respect to their access to local storage. In network 10, it can Also be a logistical problem to centrally manage and administer local data distributed across an organization, including accomplishing tasks such as backups, virus scanning and redundancy.
[0019] FIG. 2 is a block diagram of one embodiment of a storage network, indicated generally at 30, with a storage router that provides global access and routing. This environment is significantly different from that of FIG. 1 in that there is no network server involved. In FIG. 2 , a Fibre Channel high speed serial transport 32 interconnects a plurality of workstations 36 and storage devices 38. A SCSI bus storage transport medium interconnects workstations 40 and storage devices 42. A storage router 44 then serves to interconnect these mediums and provide devices on either medium global, transparent access to devices on the other medium. Storage router 44 routes requests from initiator devices on one medium to target devices on the other medium and routes data between the target and the initiator. Storage router 44 can allow initiators and targets to be on either side. In this manner, storage router 44 enhances the functionality of Fibre Channel 32 by providing access, for example, to legacy SCSI storage devices on SCSI bus 34. In the embodiment of FIG. 2 , the operation of storage router 44 can be managed by a management station 46 connected to the storage router via a direct serial connection.
[0020] In storage network 30, any workstation 36 or workstation 40 can access any storage device 38 or storage device 42 through native low level, block protocols, and vice versa. This functionality is enabled by storage router 44 which routes requests and data as a generic transport between Fibre Channel 32 and SCSI bus 34. Storage router 44 uses tables to map devices from one medium to the other and distributes requests and data across Fibre Channel 32 and SCSI bus 34 without any security access controls. Although this extension of the high speed serial interconnect provided by Fibre Channel 32 is beneficial, it is desirable to provide security controls in addition to extended access to storage devices through a native low level, block protocol.
[0021] FIG. 3 is a block diagram of one embodiment of a storage network, indicated generally at 50, with a storage router that provides virtual local storage. Similar to that of FIG. 2 , storage network 50 includes a Fibre Channel high speed serial interconnect 52 and a SCSI bus 54 bridged by a storage router 56. Storage router 56 of FIG. 3 provides for a large number of workstations 58 to be interconnected on a common storage transport and to access common storage devices 60, 62 and 64 through native low level, block protocols.
[0022] According to the present invention, storage router 56 has enhanced functionality to implement security controls and routing such that each workstation 58 can have access to a specific subset of the overall data stored in storage devices 60, 62 and 64. This specific subset of data has the appearance and characteristics of local storage and is referred to herein as virtual local storage. Storage router 56 allows the configuration and modification of the storage allocated to each attached workstation 58 through the use of mapping tables or other mapping techniques.
[0023] As shown in FIG. 3 , for example, storage device 60 can be configured to provide global data 65 which can be accessed by all workstations 58. Storage device 62 can be configured to provide partitioned subsets 66, 68, 70 and 72, where each partition is allocated to one of the workstations 58 (workstations A, B, C and D). These subsets 66, 68, 70 and 72 can only be accessed by the associated workstation 58 and appear to the associated workstation 58 as local storage accessed using native low level, block protocols. Similarly, storage device 64 can be allocated as storage for the remaining workstation 58 (workstation E).
[0024] Storage router 56 combines access control with routing such that each workstation 58 has controlled access to only the specified partition of storage device 62 which forms virtual local storage for the workstation 58. This access control allows security control for the specified data partitions. Storage router 56 allows this allocation of storage devices 60, 62 and 64 to be managed by a management station 76. Management station 76 can connect directly to storage router 56 via a direct connection or, alternately, can interface with storage router 56 through either Fibre Channel 52 or SCSI bus 54. In the latter case, management station 76 can be a workstation or other computing device with special rights such that storage router 56 allows access to mapping tables and shows storage devices 60, 62 and 64 as they exist physically rather than as they have been allocated.
[0025] The environment of FIG. 3 extends the concept of a single workstation having locally connected storage devices to a storage network 50 in which workstations 58 are provided virtual local storage in a manner transparent to workstations 58. Storage router 56 provides centralized control of what each workstation 58 sees as its local drive, as well as what data it sees as global data accessible by other workstations 58. Consequently, the storage space considered by the workstation 58 to be its local storage is actually a partition (i.e., logical storage definition) of a physically remote storage device 60, 62 or 64 connected through storage router 56. This means that similar requests from workstations 58 for access to their local storage devices produce different accesses to the storage space on storage devices 60, 62 and 64. Further, no access from a workstation 58 is allowed to the virtual local storage of another workstation 58.
[0026] The collective storage provided by storage devices 60, 62 and 64 can have blocks allocated by programming means within storage router 56. To accomplish this function, storage router 56 can include routing tables and security controls that define storage allocation for each workstation 58. The advantages provided by implementing virtual local storage in centralized storage devices include the ability to do collective backups and other collective administrative functions more easily. This is accomplished without limiting the performance of workstations 58 because storage access involves native low level, block protocols and does not involve the overhead of high level protocols and file systems required by network servers.
[0027] FIG. 4 is a block diagram of one embodiment of storage router 56 of FIG. 3 . Storage router 56 can comprise a Fibre Channel controller 80 that interfaces with Fibre Channel 52 and a SCSI controller 82 that interfaces with SCSI bus 54. A buffer 84 provides memory work space and is connected to both Fibre Channel controller 80 and to SCSI controller 82. A supervisor unit 86 is connected to Fibre Channel controller 80, SCSI controller 82 and buffer 84. Supervisor unit 86 comprises a microprocessor for controlling operation of storage router 56 and to handle mapping and security access for requests between Fibre Channel 52 and SCSI bus 54.
[0028] FIG. 5 is a block diagram of one embodiment of data flow within storage router 56 of FIG. 4 . As shown, data from Fibre Channel 52 is processed by a Fibre Channel (FC) protocol unit 88 and placed in a FIFO queue 90. A direct memory access (DMA) interface 92 then takes data out of FIFO queue 90 and places it in buffer 84. Supervisor unit 86 processes the data in buffer 84 as represented by supervisor processing 93. This processing involves mapping between Fibre Channel 52 and SCSI bus 54 and applying access controls and routing functions. A DMA interface 94 then pulls data from buffer 84 and places it into a buffer 96. A SCSI protocol unit 98 pulls data from buffer 96 and communicates the data on SCSI bus 54. Data flow in the reverse direction, from SCSI bus 54 to Fibre Channel 52, is accomplished in a reverse manner.
[0029] The storage router of the present invention is a bridge device that connects a Fibre Channel link directly to a SCSI bus and enables the exchange of SCSI command set information between application clients on SCSI bus devices and the Fibre Channel links. Further, the storage router applies access controls such that virtual local storage can be established in remote SCSI storage devices for workstations on the Fibre Channel link. In one embodiment, the storage router provides a connection for Fibre Channel links running the SCSI Fibre Channel Protocol (FCP) to legacy SCSI devices attached to a SCSI bus. The Fibre Channel topology is typically an Arbitrated Loop (FC_AL).
[0030] In part, the storage router enables a migration path to Fibre Channel based, serial SCSI networks by providing connectivity for legacy SCSI bus devices. The storage router can be attached to a Fibre Channel Arbitrated Loop and a SCSI bus to support a number of SCSI devices. Using configuration settings, the storage router can make the SCSI bus devices available on the Fibre Channel network as FCP logical units. Once the configuration is defined, operation of the storage router is transparent to application clients. In this manner, the storage router can form an integral part of the migration to new Fibre Channel based networks while providing a means to continue using legacy SCSI devices.
[0031] In one implementation (not shown), the storage router can be a rack mount or free standing device with an internal power supply. The storage router can have a Fibre Channel and SCSI port, and a standard, detachable power cord can be used, the FC connector can be a copper DB9 connector, and the SCSI connector can be a 68-pin type. Additional modular jacks can be provided for a serial port and a 802.3 10BaseT port, i.e. twisted pair Ethernet, for management access. The SCSI port of the storage router an support SCSI direct and sequential access target devices and can support SCSI initiators, as well. The Fibre Channel port can interface to SCSI-3 FCP enabled devices and initiators.
[0032] To accomplish its functionality, one implementation of the storage router uses: a Fibre Channel interface based on the HEWLETT-PACKARD TACHYON HPFC-5000 controller and a GLM media interface; an Intel 80960RP processor, incorporating independent data and program memory spaces, and associated logic required to implement a stand alone processing system; and a serial port for debug and system configuration. Further, this implementation includes a SCSI interface supporting Fast-20 based on the SYMBIOS 53C8xx series SCSI controllers, and an operating system based upon the WIND RIVERS SYSTEMS VXWORKS or IXWORKS kernel, as determined by design. In addition, the storage router includes software as required to control basic functions of the various elements, and to provide appropriate translations between the FC and SCSI protocols.
[0033] The storage router has various modes of operation that are possible between FC and SCSI target and initiator combinations. These modes are: FC Initiator to SCSI Target; SCSI Initiator to FC Target; SCSI Initiator to SCSI Target; and FC Initiator to FC Target. The first two modes can be supported concurrently in a single storage router device are discussed briefly below. The third mode can involve two storage router devices back to back and can serve primarily as a device to extend the physical distance beyond that possible via a direct SCSI connection. The last mode can be used to carry FC protocols encapsulated on other transmission technologies (e.g. ATM, SONET), or to act as a bridge between two FC loops (e.g. as a two port fabric).
[0034] The FC Initiator to SCSI Target mode provides for the basic configuration of a server using Fibre Channel to communicate with SCSI targets. This mode requires that a host system have an FC attached device and associated device drivers and software to generate SCSI-3 FCP requests. This system acts as an initiator using the storage router to communicate with SCSI target devices. The SCSI devices supported can include SCSI-2 compliant direct or sequential access (disk or tape) devices. The storage router serves to translate command and status information and transfer data between SCSI-3 FCP and SCSI-2, allowing the use of standard SCSI-2 devices in a Fibre Channel environment.
[0035] The SCSI Initiator to FC Target mode provides for the configuration of a server using SCSI-2 to communicate with Fibre Channel targets. This mode requires that a host system has a SCSI-2 interface and driver software to control SCSI-2 target devices. The storage router will connect to the SCSI-2 bus and respond as a target to multiple target IDs. Configuration information is required to identify the target IDs to which the bridge will respond on the SCSI-2 bus. The storage router then translates the SCSI-2 requests to SCSI-3 FCP requests, allowing the use of FC devices with a SCSI host system. This will also allow features such as a tape device acting as an initiator on the SCSI bus to provide full support for this type of SCSI device.
[0036] In general, user configuration of the storage router will be needed to support various functional modes of operation. Configuration can be modified, for example, through a serial port or through an Ethernet port via SNMP (simple network management protocol) or a Telnet session. Specifically, SNMP manageability can be provided via an 802.3 Ethernet interface. This can provide for configuration changes as well as providing statistics and error information. Configuration can also be performed via TELNET or RS-232 interfaces with menu driven command interfaces. Configuration information can be stored in a segment of flash memory and can be retained across resets and power off cycles. Password protection can also be provided.
[0037] In the first two modes of operation, addressing information is needed to map from FC addressing to SCSI addressing and vice versa. This can be ‘hard’ configuration data, due to the need for address information to be maintained across initialization and partial reconfigurations of the Fibre Channel address space. In an arbitrated loop configuration, user configured addresses will be needed for AL_PAs in order to insure that known addresses are provided between loop reconfigurations.
[0038] With respect to addressing, FCP and SCSI 2 systems employ different methods of addressing target devices. Additionally, the inclusion of a storage router means that a method of translating device IDs needs to be implemented. In addition, the storage router can respond to commands without passing the commands through to the opposite interface. This can be implemented to allow all generic FCP and SCSI commands to pass through the storage router to address attached devices, but allow for configuration and diagnostics to be performed directly on the storage router through the FC and SCSI interfaces.
[0039] Management commands are those intended to be processed by the storage router controller directly. This may include diagnostic, mode, and log commands as well as other vendor-specific commands. These commands can be received and processed by both the FCP and SCSI interfaces, but are not typically bridged to the opposite interface. These commands may also have side effects on the operation of the storage router, and cause other storage router operations to change or terminate.
[0040] A primary method of addressing management commands though the FCP and SCSI interfaces can be through peripheral device type addressing. For example, the storage router can respond to all operations addressed to logical unit (LUN) zero as a controller device. Commands that the storage router will support can include INQUIRY as well as vendor-specific management commands. These are to be generally consistent with SCC standard commands.
[0041] The SCSI bus is capable of establishing bus connections between targets. These targets may internally address logical units. Thus, the prioritized addressing scheme used by SCSI subsystems can be represented as follows: BUS:TARGET:LOGICAL UNIT. The BUS identification is intrinsic in the configuration, as a SCSI initiator is attached to only one bus. Target addressing is handled by bus arbitration from information provided to the arbitrating device. Target addresses are assigned to SCSI devices directly, though some means of configuration, such as a hardware jumper, switch setting, or device specific software configuration. As such, the SCSI protocol provides only logical unit addressing within the Identify message. Bus and target information is implied by the established connection.
[0042] Fibre Channel devices within a fabric are addressed by a unique port identifier. This identifier is assigned to a port during certain well-defined states of the FC protocol. Individual ports are allowed to arbitrate for a known, user defined address. If such an address is not provided, or if arbitration for a particular user address fails, the port is assigned a unique address by the FC protocol. This address is generally not guaranteed to be unique between instances. Various scenarios exist where the AL-PA of a device will change, either after power cycle or loop reconfiguration.
[0043] The FC protocol also provides a logical unit address field within command structures to provide addressing to devices internal to a port. The FCP_CMD payload specifies an eight byte LUN field. Subsequent identification of the exchange between devices is provided by the FQXID (Fully Qualified Exchange ID).
[0044] FC ports can be required to have specific addresses assigned. Although basic functionality is not dependent on this, changes in the loop configuration could result in disk targets changing identifiers with the potential risk of data corruption or loss. This configuration can be straightforward, and can consist of providing the device a loop-unique ID (AL_PA) in the range of “01h” to “EFh.” Storage routers could be shipped with a default value with the assumption that most configurations will be using single storage routers and no other devices requesting the present ID. This would provide a minimum amount of initial configuration to the system administrator. Alternately, storage routers could be defaulted to assume any address so that configurations requiring multiple storage routers on a loop would not require that the administrator assign a unique ID to the additional storage routers.
[0045] Address translation is needed where commands are issued in the cases FC Initiator to SCSI Target and SCSI Initiator to FC Target. Target responses are qualified by the FQXID and will retain the translation acquired at the beginning of the exchange. This prevents configuration changes occurring during the course of execution of a command from causing data or state information to be inadvertently misdirected. Configuration can be required in cases of SCSI Initiator to FC Target, as discovery may not effectively allow for FCP targets to consistently be found. This is due to an FC arbitrated loop supporting addressing of a larger number of devices than a SCSI bus and the possibility of FC devices changing their AL-PA due to device insertion or other loop initialization.
[0046] In the direct method, the translation to BUS:TARGET:LUN of the SCSI address information will be direct. That is, the values represented in the FCP LUN field will directly map to the values in effect on the SCSI bus. This provides a clean translation and does not require SCSI bus discovery. It also allows devices to be dynamically added to the SCSI bus without modifying the address map. It may not allow for complete discovery by FCP initiator devices, as gaps between device addresses may halt the discovery process. Legacy SCSI device drivers typically halt discovery on a target device at the first unoccupied LUN, and proceed to the next target. This would lead to some devices not being discovered. However, this allows for hot plugged devices and other changes to the loop addressing.
[0047] In the ordered method, ordered translation requires that the storage router perform discovery on reset, and collapses the addresses on the SCSI bus to sequential FCP LUN values. Thus, the FCP LUN values 0-N can represent N+1 SCSI devices, regardless of SCSI address values, in the order in which they are isolated during the SCSI discovery process. This would allow the FCP initiator discovery process to identify all mapped SCSI devices without further configuration. This has the limitation that hot-plugged devices will not be identified until the next reset cycle. In this case, the address may also be altered as well.
[0048] In addition to addressing, according to the present invention, the storage router provides configuration and access controls that cause certain requests from FC Initiators to be directed to assigned virtual local storage partitioned on SCSI storage devices. For example, the same request for LUN 0 (local storage) by two different FC Initiators can be directed to two separate subsets of storage. The storage router can use tables to map, for each initiator, what storage access is available and what partition is being addressed by a particular request. In this manner, the storage space provided by SCSI storage devices can be allocated to FC initiators to provide virtual local storage as well as to create any other desired configuration for secured access.
[0049] Although the present invention has been described in detail, it should be understood that various changes, substitutions, and alterations can be made hereto without departing from the spirit and scope of the invention as defined by the appended claims.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A storage router for providing virtual local storage on remote storage devices to a device, comprising:
a buffer providing memory work space for the storage router;
a first Fibre Channel controller operable to connect to and interface with a first Fibre Channel transport medium;
a second Fibre Channel controller operable to connect to and interface with a second Fibre Channel transport medium; and
a supervisor unit coupled to the first and second Fibre Channel controllers and the buffer, the supervisor unit operable:
to maintain a configuration for remote storage devices connected to the second Fibre Channel transport medium that maps between the device and the remote storage devices and that implements access controls for storage space on the remote storage devices; and
to process data in the buffer to interface between the first Fibre Channel controller and the second Fibre Channel controller to allow access from Fibre Channel initiator devices to the remote storage devices using native low level, block protocol in accordance with the configuration.
2. The storage router of claim 1, wherein the configuration maintained by the supervisor unit includes an allocation of subsets of storage space to associated Fibre Channel devices, wherein each subset is only accessible by the associated Fibre Channel device.
3. The storage router of claim 2, wherein the Fibre Channel devices comprise workstations.
4. The storage router of claim 2, wherein the remote storage devices comprise hard disk drives.
5. The storage router of claim 1, wherein each of the first Fibre Channel controller comprises:
a Fibre Channel (FC) protocol unit operable to connect to the Fibre Channel transport medium;
a first-in-first-out queue coupled to the Fibre Channel protocol unit; and
a direct memory access (DMA) interface coupled to the first-in-first-out queue and to the buffer.
6. A storage network, comprising:
a first Fibre Channel transport medium;
a second Fibre Channel transport medium;
a plurality of workstations connected to the first Fibre Channel transport medium;
a plurality of storage devices connected to the second Fibre Channel transport medium; and
a storage router interfacing between the first Fibre Channel transport medium and the second Fibre Channel transport medium, the storage router providing virtual local storage on the storage devices to the workstations and operable:
to map between the workstations and the storage devices;
to implement access controls for storage space on the storage devices; and
to allow access from the workstations to the storage devices using native low level, block protocol in accordance with the mapping and access controls.
7. The storage network of claim 6, wherein the access controls include an allocation of subsets of storage space to associated workstations, wherein each subset is only accessible by the associated workstation.
8. The storage network of claim 6, wherein the storage devices comprise hard disk drives.
9. The storage network of claim 6, wherein the storage router comprises:
a buffer providing memory work space for the storage router;
a first Fibre Channel controller operable to connect to and interface with the first Fibre Channel transport medium, the first Fibre Channel controller further operable to pull outgoing data from the buffer and to place incoming data into the buffer;
a second Fibre Channel controller operable to connect to and interface with the second Fibre Channel transport medium, the second Fibre Channel controller further operable to pull outgoing data from the buffer and to place incoming data into the buffer; and
a supervisor unit coupled to the first and second Fibre Channel controllers and the buffer, the supervisor unit operable:
to maintain a configuration for the storage devices that maps between workstations and storage devices and that implements the access controls for storage space on the storage devices; and
to process data in the buffer to interface between the first Fibre Channel controller and the second Fibre Channel controller to allow access from workstations to storage devices in accordance with the configuration.
10. A method for providing virtual local storage on remote storage devices to Fibre Channel devices, comprising:
interfacing with a first Fibre Channel transport medium;
interfacing with a second Fibre Channel transport medium;
maintaining a configuration for remote storage devices connected to the second Fibre Channel transport medium that maps between Fibre Channel devices and the remote storage devices and that implements access controls for storage space on the remote storage devices; and
allowing access from Fibre Channel initiator devices to the remote storage devices using native low level, block protocol in accordance with the configuration.
11. The method of claim 10, wherein maintaining the configuration includes allocating subsets of storage space to associated Fibre Channel devices, wherein each subset is only accessible by the associated Fibre Channel device.
12. The method of claim 11, wherein the Fibre Channel devices comprise workstations.
13. The method of claim 11, wherein the remote storage devices comprise hard disk drives.
14. An apparatus for providing virtual local storage on a remote storage device to a device operating according to a Fibre Channel protocol, comprising:
a first controller operable to connect to and interface with a first transport medium, wherein the first transport medium is operable according to the Fibre Channel protocol;
a second controller operable to connect to and interface with a second transport medium, wherein the second transport medium is operable according to the Fibre Channel protocol; and
a supervisor unit coupled to the first controller and the second controller, the supervisor unit operable to control access from the device connected to the first transport medium to the remote storage device connected to the second transport medium using native low level, block protocols according to a map between the device and the remote storage device.
15. The apparatus of claim 14, wherein the supervisor unit is further operable to maintain a configuration wherein the configuration includes the map between the device and the remote storage device, and further wherein the map includes virtual LUNs that provide a representation of the storage device.
16. The apparatus of claim 15, wherein the map only exposes the device to LUNs that the device may access.
17. The apparatus of claim 14, wherein the supervisor unit is further operable to maintain a configuration including the map, wherein the map provides a mapping from a host device ID to a virtual LUN representation of the remote storage device to a physical LUN of the remote storage device.
18. The apparatus of claim 14, wherein the remote storage device further comprises storage space partitioned into virtual local storage for the device connected to the first transport medium.
19. The apparatus of claim 18, wherein the supervisor unit is further operable to prevent the device from accessing any storage on the remote storage device that is not part of a virtual local storage partition assigned to the device.
20. The apparatus of claim 14, wherein the first controller and the second controller further comprise a single controller.
21. A system for providing virtual local storage on remote storage devices, comprising:
a first controller operable to connect to and interface with a first transport medium operable according to a Fibre Channel protocol;
a second controller operable to connect to and interface with a second transport medium operable according to the Fibre Channel protocol;
at least one device connected to the first transport medium;
at least one storage device connected to the second transport medium; and
an access control device coupled to the first controller and the second controller, the access control device operable to:
map between the at least one device and a storage space on the at least one storage device; and
control access from the at least one device to the at least one storage device using native low level, block protocol in accordance with the map.
22. The system of claim 21, wherein the access control device is further operable to maintain a configuration wherein the configuration includes the map between the at least one device and the at least one storage device, and further wherein the map includes virtual LUNs that provide a representation of the at least one storage device.
23. The system of claim 22, wherein the map only exposes the at least one device to LUNs that the at least one device may access.
24. The system of claim 21, wherein the access control device is further operable to maintain a configuration including the map, wherein the map provides a mapping from a host device ID to a virtual LUN representation of the at least one storage device to a physical LUN of the at least one storage device.
25. The system of claim 21, wherein the at least one storage device further comprises storage space partitioned into virtual local storage for the at least one device.
26. The system of claim 25, wherein the access control unit is further operable to prevent at least one device from accessing any storage on the at least one storage device that is not part of a virtual local storage partition assigned to the at least one device.
27. The system of claim 21, wherein the first controller and the second controller further comprise a single controller.
28. A method for providing virtual local storage on remote storage devices, comprising:
mapping between a device connected to a first transport medium and a storage device connected to a second transport medium, wherein the first transport medium and the second transport medium operate according to a Fibre Channel protocol;
implementing access controls for storage space on the storage device; and
allowing access from the device connected to the first transport medium to the storage device using native low level, block protocols.
29. The method of claim 28, further comprising maintaining a configuration wherein the configuration includes a map between the device and the one storage device, and further wherein the map includes virtual LUNs that provide a representation of the storage device.
30. The method of claim 29, wherein the map only exposes the device to LUNs that the device may access.
31. The method of claim 28, further comprising maintaining a configuration including a map from a host device ID to a virtual LUN representation of the storage device to a physical LUN of the storage device.
32. The method of claim 28, further comprising partitioning storage space on the storage device into virtual local storage for the device.
33. The method of claim 32, further comprising preventing the device from accessing any storage on the storage device that is not part of a virtual local storage partition assigned to the device.
34. A system for providing virtual local storage, comprising:
a host device;
a storage device remote from the host device, wherein the storage device has a storage space;
a first controller;
a second controller
a first transport medium operable according to a Fibre Channel protocol, wherein the first transport medium connects the host device to the first controller;
a second transport medium operable according to the Fibre Channel protocol, wherein the second transport medium connects the second controller to the storage device;
a supervisor unit coupled to the first controller and the second controller, the supervisor unit operable to:
maintain a configuration that maps between the host device and at least a portion of the storage space on the storage device; and
implement access controls according to the configuration for the storage space on the storage device using native low level, block protocol.
35. The system of claim 34, wherein the supervisor unit is further operable to:
maintain a configuration that maps from the host device to a virtual representation of at least a portion of the storage space on the storage device to the storage device; and
allow the host device to access only that portion of the storage space that is contained in the map.
36. The system of claim 35, wherein the configuration comprises a map from a host device ID to a virtual LUN representation of the storage device to a physical LUN of the storage device.
37. The system of claim 34, wherein the storage device further comprises storage space partitioned into virtual local storage for the host device.
38. The system of claim 37, wherein the supervisor unit is further operable to prevent the host device from accessing any storage on the storage device that is not part of a virtual local storage partition assigned to the host device.
39. The apparatus of claim 34, wherein the first controller and the second controller further comprise a single controller.
Patent Citations (185)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3082406(A) | 1963-03-01 | Stevens | Applicant |
| US4092732(A) | 1978-05-01 | Ouchi | Applicant |
| US4415970(A) | 1983-11-01 | Swenson et al. | Applicant |
| US4455605(A) | 1984-06-01 | Cormier et al. | Applicant |
| US4504927(A) | 1985-03-01 | Callan | Applicant |
| US4533996(A) | 1985-08-01 | Gartung et al. | Applicant |
| US4573152(A) | 1986-02-01 | Greene et al. | Applicant |
| US4603380(A) | 1986-07-01 | Easton et al. | Applicant |
| US4620295(A) | 1986-10-01 | Aiden, Jr. | Applicant |
| US4644462(A) | 1987-02-01 | Matsubara et al. | Applicant |
| US4695948(A) | 1987-09-01 | Blevins et al. | Applicant |
| US4697232(A) | 1987-09-01 | Brunelle et al. | Applicant |
| US4751635(A) | 1988-06-01 | Kret | Applicant |
| US4787028(A) | 1988-11-01 | Finforck et al. | Applicant |
| US4807180(A) | 1989-02-01 | Takeuchi et al. | Applicant |
| US4811278(A) | 1989-03-01 | Bean et al. | Applicant |
| US4821179(A) | 1989-04-01 | Jensen et al. | Applicant |
| US4825406(A) | 1989-04-01 | Bean et al. | Applicant |
| US4827411(A) | 1989-05-01 | Arrowood et al. | Applicant |
| US4835674(A) | 1989-05-01 | Collins et al. | Applicant |
| US4864532(A) | 1989-09-01 | Reeve et al. | Applicant |
| US4897874(A) | 1990-01-01 | Lidensky et al. | Applicant |
| US4947367(A) | 1990-08-01 | Chang et al. | Applicant |
| US4961224(A) | 1990-10-01 | Yung | Applicant |
| US5072378(A) | 1991-12-01 | Manka | Applicant |
| US5077732(A) | 1991-12-01 | Fischer et al. | Applicant |
| US5077736(A) | 1991-12-01 | Dunphy, Jr. et al. | Applicant |
| US5124987(A) | 1992-06-01 | Milligan et al. | Applicant |
| US5155845(A) | 1992-10-01 | Beal et al. | Applicant |
| US5163131(A) | 1992-11-01 | Row et al. | Applicant |
| US5185876(A) | 1993-02-01 | Nguyen et al. | Applicant |
| US5193168(A) | 1993-03-01 | Corrigan et al. | Applicant |
| US5193184(A) | 1993-03-01 | Belsan et al. | Applicant |
| US5202856(A) | 1993-04-01 | Glider et al. | Applicant |
| US5210866(A) | 1993-05-01 | Milligan et al. | Applicant |
| US5212785(A) | 1993-05-01 | Powers et al. | Applicant |
| US5214778(A) | 1993-05-01 | Glider et al. | Applicant |
| US5226143(A) | 1993-07-01 | Baird et al. | Applicant |
| US5239632(A) | 1993-08-01 | Larner | Applicant |
| US5239643(A) | 1993-08-01 | Blount et al. | Applicant |
| US5239654(A) | 1993-08-01 | Ing-Simmons | Applicant |
| US5247638(A) | 1993-09-01 | O'Brien et al. | Applicant |
| US5247692(A) | 1993-09-01 | Fujimura | Applicant |
| US5257386(A) | 1993-10-01 | Saito | Applicant |
| US5297262(A) | 1994-03-01 | Cox et al. | Applicant |
| US5301290(A) | 1994-04-01 | Tetzlaff et al. | Applicant |
| US5315657(A) | 1994-05-01 | Abadi et al. | Applicant |
| US5317739(A) | 1994-05-01 | Elko et al. | Applicant |
| US5331673(A) | 1994-07-01 | Elko et al. | Applicant |
| US5347384(A) | 1994-09-01 | McReynolds et al. | Applicant |
| US5361347(A) | 1994-11-01 | Glider et al. | Applicant |
| US5367646(A) | 1994-11-01 | Pardillos et al. | Applicant |
| US5379385(A) | 1995-01-01 | Shomler | Applicant |
| US5379398(A) | 1995-01-01 | Cohn et al. | Applicant |
| US5388243(A) | 1995-02-01 | Glider et al. | Applicant |
| US5388246(A) | 1995-02-01 | Kasai | Applicant |
| US5394526(A) | 1995-02-01 | Crouse et al. | Applicant |
| US5396596(A) | 1995-03-01 | Hashemi et al. | Applicant |
| US5403639(A) | 1995-04-01 | Belsan et al. | Applicant |
| US5410667(A) | 1995-04-01 | Belsan et al. | Applicant |
| US5410697(A) | 1995-04-01 | Baird et al. | Applicant |
| US5414820(A) | 1995-05-01 | McFarland et al. | Applicant |
| US5416915(A) | 1995-05-01 | Mattson et al. | Applicant |
| US5418909(A) | 1995-05-01 | Jachowski et al. | Applicant |
| US5420988(A) | 1995-05-01 | Elliott | Applicant |
| US5423026(A) | 1995-06-01 | Cook et al. | Applicant |
| US5423044(A) | 1995-06-01 | Sutton et al. | Applicant |
| US5426637(A) | 1995-06-01 | Derby et al. | Applicant |
| US5430855(A) | 1995-07-01 | Wash et al. | Applicant |
| US5450570(A) | 1995-09-01 | Richek et al. | Applicant |
| US5452421(A) | 1995-09-01 | Beardsley et al. | Applicant |
| US5459857(A) | 1995-10-01 | Ludlam et al. | Applicant |
| US5463754(A) | 1995-10-01 | Beausoleil et al. | Applicant |
| US5465382(A) | 1995-11-01 | Day, III et al. | Applicant |
| US5469576(A) | 1995-11-01 | Dauerer et al. | Applicant |
| US5471609(A) | 1995-11-01 | Yudenfriend | Applicant |
| US5487077(A) | 1996-01-01 | Hassner et al. | Applicant |
| US5491812(A) | 1996-02-01 | Pisello et al. | Applicant |
| US5495474(A) | 1996-02-01 | Olnowich et al. | Applicant |
| US5496576(A) | 1996-03-01 | Jeong | Applicant |
| US5504857(A) | 1996-04-01 | Baird et al. | Applicant |
| US5507032(A) | 1996-04-01 | Kimura | Applicant |
| US5511169(A) | 1996-04-01 | Suda | Applicant |
| US5519695(A) | 1996-05-01 | Purohit et al. | Applicant |
| US5530845(A) | 1996-06-01 | Hiatt et al. | Applicant |
| US5535352(A) | 1996-07-01 | Bridges et al. | Applicant |
| US5537585(A) | 1996-07-01 | Blickerstaff et al. | Applicant |
| US5544313(A) | 1996-08-01 | Shachnai et al. | Applicant |
| US5548791(A) | 1996-08-01 | Casper et al. | Applicant |
| US5564019(A) | 1996-10-01 | Beausoleil et al. | Applicant |
| US5568648(A) | 1996-10-01 | Coscarella et al. | Applicant |
| US5581709(A) | 1996-12-01 | Ito et al. | Applicant |
| US5581714(A) | 1996-12-01 | Amini et al. | Applicant |
| US5581724(A) | 1996-12-01 | Belsan et al. | Applicant |
| US5596562(A) | 1997-01-01 | Chen | Applicant |
| US5596736(A) | 1997-01-01 | Kerns | Applicant |
| US5598541(A) | 1997-01-01 | Malladi | Applicant |
| US5613082(A) | 1997-03-01 | Brewer et al. | Applicant |
| US5621902(A) | 1997-04-01 | Cases et al. | Applicant |
| US5632012(A) | 1997-05-01 | Belsan et al. | Applicant |
| US5634111(A) | 1997-05-01 | Oeda et al. | Applicant |
| US5638518(A) | 1997-06-01 | Malladi | Applicant |
| US5642515(A) | 1997-06-01 | Jones et al. | Applicant |
| US5659756(A) | 1997-08-01 | Hefferon et al. | Applicant |
| US5664107(A) | 1997-09-01 | Chatwani et al. | Applicant |
| US5680556(A) | 1997-10-01 | Begun et al. | Applicant |
| US5701491(A) | 1997-12-01 | Dunn et al. | Applicant |
| US5712976(A) | 1998-01-01 | Falcon, Jr. et al. | Applicant |
| US5727218(A) | 1998-03-01 | Hotchkin | Applicant |
| US5729705(A) | 1998-03-01 | Weber | Applicant |
| US5743847(A) | 1998-04-01 | Nakamura et al. | Applicant |
| US5748924(A) | 1998-05-01 | Llorens et al. | Applicant |
| US5751975(A) | 1998-05-01 | Gillespie et al. | Applicant |
| US5768623(A) | 1998-06-01 | Judd et al. | Applicant |
| US5774683(A) | 1998-06-01 | Gulick | Applicant |
| US5781715(A) | 1998-07-01 | Sheu | Applicant |
| US5802278(A) | 1998-09-01 | Isfeld et al. | Applicant |
| US5805816(A) | 1998-09-01 | Picazo, Jr. et al. | Applicant |
| US5809328(A) | 1998-09-01 | Nogales et al. | Applicant |
| US5812754(A) | 1998-09-01 | Lui et al. | Applicant |
| US5835496(A) | 1998-11-01 | Yeung et al. | Applicant |
| US5845107(A) | 1998-12-01 | Fisch et al. | Applicant |
| US5848251(A) | 1998-12-01 | Lomelino et al. | Applicant |
| US5857080(A) | 1999-01-01 | Jander et al. | Applicant |
| US5860137(A) | 1999-01-01 | Raz et al. | Applicant |
| US5864653(A) | 1999-01-01 | Tavallaei et al. | Applicant |
| US5867648(A) | 1999-02-01 | Foth et al. | Applicant |
| US5884027(A) | 1999-03-01 | Garbus et al. | Applicant |
| US5889952(A) | 1999-03-01 | Hunnicutt et al. | Applicant |
| US5913045(A) | 1999-06-01 | Gillespie et al. | Applicant |
| US5923557(A) | 1999-07-01 | Eidson | Applicant |
| US5933824(A) | 1999-08-01 | DeKoning et al. | Applicant |
| US5935260(A) | 1999-08-01 | Ofer | Applicant |
| US5941969(A) | 1999-08-01 | Ram et al. | Applicant |
| US5941972(A) | 1999-08-01 | Hoese et al. | Examiner |
| US5953511(A) | 1999-09-01 | Sescilia et al. | Applicant |
| US5959994(A) | 1999-09-01 | Boggs et al. | Applicant |
| US5974530(A) | 1999-10-01 | Young | Applicant |
| US5978379(A) | 1999-11-01 | Chan et al. | Examiner |
| US5991797(A) | 1999-11-01 | Futral et al. | Applicant |
| US6000020(A) | 1999-12-01 | Chin et al. | Examiner |
| US6021451(A) | 2000-02-01 | Bell et al. | Applicant |
| US6041381(A) | 2000-03-01 | Hoese | Applicant |
| US6055603(A) | 2000-04-01 | Ofer et al. | Applicant |
| US6065087(A) | 2000-05-01 | Keaveny et al. | Applicant |
| US6070253(A) | 2000-05-01 | Tavallaei et al. | Applicant |
| US6073209(A) | 2000-06-01 | Bergsten | Applicant |
| US6073218(A) | 2000-06-01 | DeKoning et al. | Applicant |
| US6075863(A) | 2000-06-01 | Krishnan et al. | Applicant |
| US6081849(A) | 2000-06-01 | Born et al. | Applicant |
| US6098149(A) | 2000-08-01 | Ofer et al. | Applicant |
| US6108684(A) | 2000-08-01 | DeKoning et al. | Applicant |
| US6118766(A) | 2000-09-01 | Akers | Applicant |
| US6131119(A) | 2000-10-01 | Fukui | Applicant |
| US6134617(A) | 2000-10-01 | Weber | Applicant |
| US6141737(A) | 2000-10-01 | Krantz et al. | Applicant |
| US6145006(A) | 2000-11-01 | Vishlitsky et al. | Applicant |
| US6148004(A) | 2000-11-01 | Nelson et al. | Applicant |
| US6185203(B1) | 2001-02-01 | Berman | Examiner |
| US6209023(B1) | 2001-03-01 | Dimitroff et al. | Applicant |
| US6219771(B1) | 2001-04-01 | Kikuchi et al. | Applicant |
| US6223266(B1) | 2001-04-01 | Sartore | Applicant |
| US6230218(B1) | 2001-05-01 | Casper et al. | Applicant |
| US6260120(B1) | 2001-07-01 | Blumenau et al. | Applicant |
| US6330629(B1) | 2001-12-01 | Kondo et al. | Applicant |
| US6341315(B1) | 2002-01-01 | Arroyo et al. | Applicant |
| US6343324(B1) | 2002-01-01 | Hubis et al. | Applicant |
| US6363462(B1) | 2002-03-01 | Bergsten | Applicant |
| US6421753(B1) | 2002-07-01 | Hoese et al. | Examiner |
| US6425035(B1) | 2002-07-01 | Hoese et al. | Examiner |
| US6425036(B1) | 2002-07-01 | Hoese et al. | Applicant |
| US6484245(B1) | 2002-11-01 | Sanada et al. | Applicant |
| US6529996(B1) | 2003-03-01 | Nguyen et al. | Applicant |
| US6738854(B1) | 2004-05-01 | Hoese et al. | Examiner |
| US6763419(B1) | 2004-07-01 | Hoese et al. | Examiner |
| US6789152(B1) | 2004-09-01 | Hoese et al. | Examiner |
| EP810530(A2) | 1997-12-01 | Applicant | |
| EP827059(A2) | 1998-03-01 | Applicant | |
| GB2296798(A) | 1996-07-01 | Applicant | |
| GB2297636(A) | 1996-08-01 | Applicant | |
| GB2341715 | 2000-03-01 | Applicant | |
| JP6301607 | 1994-10-01 | Applicant | |
| JP8-230895 | 1996-09-01 | Applicant | |
| WO98/36357 | 1998-08-01 | Applicant | |
| WO99/34297(A1) | 1999-07-01 | Applicant |
Non-Patent Literature (123)
- DIGITAL StorageWorks, Using Your HSZ70 Array Controller in a SCSI Controller Shelf (DS-BA356-M Series), User's Guide, pp. 1-1 through A-5 with index, Jan. 1998.Applicant
- DIGITAL StorageWorks, HSZ70 Array Controller HSOF Version 7.0 (EK-HSZ70-CG.A01), Configuration Manual, pp. 1-2 through G15 with index, Jul. 1997.Applicant
- DIGITAL StorageWorks, HSZ70 Array Controller HSOF Version 7.0, CLI Reference Manual, pp. 1-156, Jul. 1997.Applicant
- Decision Returning Petition mailed Feb. 28, 2005.Applicant
- Block-Based Distributed File Systems, Anthony J. McGregor, Jul. 1997.Applicant
- Compaq StorageWorks HSG80 Array Controller ACS Version 8.3 (Maintenance and Service Guide) Nov. 1998.Applicant
- Compaq StorageWorks HSG80 Array Controller ACS Version 8.3 (Configuration and CLI Reference Guide) Nov. 1998.Applicant
- CRD-5500 SCSI RAID Controller User's Manual CMD Technology, Inc. pp. 1-1 to 6-25, revised Nov. 21, 1996.Applicant
- DIGITAL Storage Works, HSZ70 Array Controller, HSOF Version 7.0 EK-HSZ70-CG. A01, Digital Equipment Corporation, Maynard, Massachusetts.Applicant
- DIGITAL StorageWorks HSZ70 Array Controller HSOF Version 7.0 EK-HSZ270-RM. A01 CLI Reference Manual.Applicant
- DIGITAL StorageWorks HSZ70 Array Controller HSOF Version 7.0 EK-HSZ70-SV. A01, 1997.Applicant
- DIGITAL StorageWorks HSG80 Array Controller ACS Version 8.0 (User's Guide Jan. 1998).Applicant
- DP5380 Asynchronous SCSI Interface, National Semiconductor Corporation, Arlington, TX, May 1989, pp. 1-32.Applicant
- Emerson, “Ancor Communications: Performance evaluation of switched fibre channel I/O system using—FCP for SCSI” Feb. 1, 1995, IEEE, pp. 479-484.Applicant
- Fibre Channel and ATM: The Physical Layers, Jerry Quam WESCON/94, published Sep. 27-29, 1994. pp. 648-652.Applicant
- Fiber Channel storage interface for video-on-demand servers by Anazaloni, et al, Jun. 15, 1905.Applicant
- Gen5 S-Series XL System Guide Revision 1.01 by Chen, Jun. 18, 1905.Applicant
- Graphical User Interface for MAXSTRAT Gen5/Gen-S Servers User's guide 1.1, Jun. 11, 1996.Applicant
- High Performance Data transfers Using Network-Attached Peripherals at the national Storage Laboratory by Hyer, Feb. 26, 1993.Applicant
- IFT-3000 SCSI to SCSI Disk array Controller Instruction Manual Revision 2.0 by Infotrend Technologies, Inc., 1995.Applicant
- Implementing a Fibre Channel SCSI transport by Snively, 1994.Applicant
- “InfoServer 150—Installation and Owner's Guide”, EK-INFSV-OM-001, Digital Equipment Corporation, Maynard, Massachusettes 1991, Chapters 1 and 2.Applicant
- InforServer 150VXT Photograph.Applicant
- Infoserver 100 System Operations Guide, First Edition Digital Equipment Corporation, 1990.Applicant
- Johnson, D.B., et al., “The Peregrine High Performance RPC System”, Software-Practice and Experience, 23(2):201-221, Feb. 1993.Applicant
- Local-Area networks for the IBM PC by Haugdahl.Applicant
- Misc. Reference Manual Pages, SunOS 5.09.Applicant
- New serial I/Os speed storage subsystems by Bursky, Feb. 6, 1995.Applicant
- Petal: Distributed Virtual Disks, Edward K. Lee and Chandramohan A. Thekkath, ACM SIGPLAN Notices, vol. 31, Issue 9, Sep. 1996, pp. 84-92.Applicant
- Pictures of internal components of the InfoServer 150, taken from http://bindarydinosaurs.couk/Museum/Digital/infoserver/infoserver.php in Nov. 2004.Applicant
- Raidtec FibreArray and Raidtec FlexArray UltraRAID Systems, Windows IT PRO Article, Oct. 1997.Applicant
- S.P. Joshi, “Ethernet controller chip interfaces with variety of 16-bit processors,” electronic Design, Hayden Publishing Co., Inc., Rochelle Part, NJ, Oct. 14, 1982. pp. 193-200.Applicant
- Simplest Migration to Fibre Channel Technology Article, Digital Equipment Corporation, Nov. 10, 1997, published on PR Newswire.Applicant
- Systems Architectures Using Fibre Channel, Roger Cummings, Twelfth IEEE Symposium on Mass Storage Systems, Copyright 1993 IEEE. pp. 251-256.Applicant
- Dot Hill's Request to Exceed Page Limit in Motion for Summary Judgment filed Jun. 29, 2005. Case No. A-03-CV-754 (SS).Applicant
- Request for Ex Parte Reexamination for 6,425,035. Third Party Requester: William A. Blake.Applicant
- Request for Ex Parte Reexamination for 6,425,035. Third Party Requester: Natu J. Patel.Applicant
- Office Action dated Jan. 21, 2003 for 10/174,720 (CROSS1120-8).Applicant
- Office Action dated Feb. 27, 2001 for 09/354,682 (CROSS1120-1).Applicant
- Office Action dated Aug. 11, 2000 for 09/354,682 (CROSS1120-1).Applicant
- Office Action dated Dec. 16, 1999 for 09/354,682 (CROSS1120-1).Applicant
- Office Action dated Nov. 6, 2002 for 10/023,786 (CROSS1120-4).Applicant
- Office Action dated Jan. 21, 2003 for 10/081,110 (CROSS1120-5).Applicant
- Office Action in Ex Parte Reexamination 90/007,127, mailed Feb. 7, 2005.Applicant
- Reply to Office Action Under Ex Parte Reexamination Dated Feb. 2, 2007 for 90/007,127 filed on Apr. 6, 2005.Applicant
- Reply to Office Action Under Ex Parte Reexamination Dated Feb. 2, 2007 for 90/007,125 and 90/007,317 filed on Apr. 6, 2005.Applicant
- Office Action in Ex Parte Reexamination 90/007,126, mailed Feb. 7, 2005.Applicant
- Reply to Office Action Under Ex Parte Reexamination Dated Feb. 2, 2007 for 90/007,126 filed on Apr. 6, 2005.Applicant
- Office Action in Ex Parte Reexamination 90/007,124, mailed Feb. 7, 2005.Applicant
- Office Action in Ex Parte Reexamination 90/007,123, mailed Feb. 7, 2005.Applicant
- Reply to Office Action Under Ex Parte Reexamination Dated Feb. 2, 2007 for 90/007,123 filed on Apr. 5, 2005.Applicant
- European Office Action issued Apr. 1, 2004 in Application No. 98966104.6-2413.Applicant
- Fiber Channel (FCS)/ATM Interworking: A Design Solution by Anzaloni, et al.Applicant
- Copies of the following are on the attached CD-Rom.Applicant
- Defendant's First Supplemental Trial Exhibit List, Crossroads Systems, Inc., v. Chaparral Network Storage, Inc., C.A. No. A-00CA-217-SS (W.D. Tex. 2001). (CD-Rom).Applicant
- Defendant's Third Supplemental Trial Exhibit List, Crossroads Systems, Inc. v. Pathlight Technology, Inc., C.A. No. A-00CA-248-SS (W.D. Tex. 2001) (CD-Rom).Applicant
- Defendant Chaparral Network Storage, Inc.'s First Supplemental Trial Exhibit List (D1 through D271) (CD-ROM Chaparral Exhibits ExList—Def), Sep. 2, 2001.Applicant
- Plaintiff's Fourth Amended Trial Exhibit List, Crossroads Systems, Inc. v. Chaparral Network Storage, Inc, C.A. No. A-00CA-217-SS (W.D. Tex. 2001) (CD-Rom), Sep. 11, 2001.Applicant
- Trail Transcripts, Crossroads Systems, Inc. v. Chaparral Network Storage, Inc., C.A. No. A-00CA-217-SS (W.D. Tex. 2001). (CD-Rom).Applicant
- Trail Transcripts, Crossroads Systems, Inc. v. Pathlight Technology, Inc., C.A. No. A-00CA-248-SS (W.D. Tex. 2001). (CD-Rom).Applicant
- Datasheet for CrossPoint 4100 Fibre Channel to SCSI Router (Dedek Ex 41 (ANCT 117-120)) (CD-ROM Chaparral Exhibits D012).Applicant
- Symbios Logic- Software Interface Specification Series 3 SCSI RAID Controller Software Release 02.xx (Engelbrecht Ex 2 (LSI 1421-1658)) (CD-ROM Chaparral Exhibits D013), Dec. 3, 1997.Applicant
- Press Release- Symbios Logic to Demonstrate Strong Support for Fibre Channel at Fall Comdex (Engelbrecht 12 (LSI 2785-86)) (CD-ROM Chaparral Exhibits D016), Nov. 13, 1996.Applicant
- OEM Datasheet on the 3701 Controller (Engelbrecht 13 (LSI 01837-38)) (CD-ROM Chaparral Exhibits D017), Jun. 17, 1905.Applicant
- Nondisclosure Agreement Between Adaptec and Crossroads Dated Oct. 17, 1996 (Quisenberry Ex 25 (CRDS 8196)) (CD-ROM Chaparral Exhibits D020).Applicant
- Organizational Presentation on the External Storage Group (Lavan Ex 1 (CNS 182242-255)) (CD-ROM Chaparral Exhibits D021), Apr. 11, 1996.Applicant
- Bridge. C, Bridge Between SCSI-2 and SCSI-3 FCP (Fibre Channel Protocol) (CD-ROM Chaparral Exhibits P214).Applicant
- Bridge Phase II Architecture Presentation (Lavan Ex 2 (CNS 182287-295)) (CD-ROM Chaparral Exhibits D022), Apr. 12, 1996.Applicant
- Attendees/Action Items from Apr. 12, 1996 Meeting at BTC (Lavan Ex 3 (CNS 182241)) (CD-ROM Chaparral Exhibits D023), Apr. 12, 1996.Applicant
- Brooklyn Hardware Engineering Requirements Documents, Revision 1.4 (Lavan Ex 4 (CNS 178188-211)) (CD-ROM Chaparral Exhibits D024) by Pecone, May 26, 1996.Applicant
- Brooklyn Single-Ended SCSI RAID Bridge Controller Hardware OEM Manual, Revision 2.1 (Lavan EX 5 (CNS 177169-191)) (CD-ROM Chaparral Exhibits D025), Mar. 21, 1996.Applicant
- Coronado Hardware Engineering Requirements Document, Revision 0.0 (Lavan Ex 7 (CNS 176917-932)) (CD-ROM Chaparral Exhibits D027) by O'Dell, Sep. 30, 1996.Applicant
- ESS/FPG Organization (Lavan Ex 8 (CNS 178639-652)) (CD-ROM Chaparral Exhibits D028), Dec. 6, 1996.Applicant
- Adaptec MCS ESS Presents: Intelligent External I/O Raid Controllers “Bridge” Strategy (Lavan Ex 9 (CNS 178606-638)). (CD-ROM Chaparral Exhibits D029), Feb. 6, 1996.Applicant
- AEC-7313 Fibre Channel Daughter Board (for Brooklyn) Engineering Specification, Revision 1.0 (Lavan Ex 10 (CNS 176830-850)) (CD-ROM Chaparral Exhibits D030), Feb. 27, 1997.Applicant
- Bill of Material (Lavan Ex 14 (CNS 177211-214)) (CD-ROM Chaparral Exhibits D034), Jul. 24, 1997.Applicant
- AEC-. 4412B, AEC-7412/B2 External RAID Controller Hardware OEM Manual, Revision 2.0 (Lavan Ex 15 (CNS 177082-123)) (CD-ROM Chaparral Exhibits D035), Jun. 27, 1997.Applicant
- Coronado II, AEC-7312A Fibre Channel Daughter (for Brooklyn) Hardware Specification, Revision 1.2 (Lavan Ex 16 (CNS 177192-210)) (CD-ROM Chaparral Exhibits D036) by Tom Yang, Jul. 18, 1997.Applicant
- AEC-4412B, AEC7412/3B External RAID Controller Hardware OEM Manual, Revision 3.0. (Lavan Ex 17 (CNS 177124-165)) (CD-ROM Chaparral Exhibits D037), Aug. 25, 1997.Applicant
- Memo Dated Aug. 15, 1997 to AEC-7312A Evaluation Unit Customers re: B001 Release Notes (Lavan Ex 18 (CNS 182878-879)) (CD-ROM Chaparral Exhibits D038).Applicant
- Brooklyn Main Board (AES-0302) MES Schedule (Lavan Ex 19 (CNS 177759-763)) (CD-ROM Chaparral Exhibits D039), Feb. 11, 1997.Applicant
- News Release-Adaptec Adds Fibre Channel Option to its External RAID Controller Family (Lavan Ex 20 (CNS 182932-934)) (CD-ROM Chaparral Exhibits D040), May 6, 1997.Applicant
- AEC-4412B/7412B User's Guide, Rev. A (Lavan Ex 21) (CD-ROM Chaparral Exhibits D041), Jun. 19, 1905.Applicant
- Data Book- AIC-7895 PCI Bus Master Single Chip SCSI Host Adapter (Davies Ex 1 (CNS 182944-64)) (CD-ROM Chaparral Exhibits D046), May 21, 1996.Applicant
- Data Book- AIC-1160 Fibre Channel Host Adapter ASIC (Davies Ex 2 (CNS 181800-825)) (CD-ROM Chaparral Exhibits D047), Jun. 18, 1905.Applicant
- Viking RAID Software (Davies Ex 3 (CNS 180969-181026)) (CD-ROM Chaparral Exhibits D048), Jun. 18, 1905.Applicant
- Header File with Structure Definitions (Davies Ex 4 (CNS 180009-018)) (CD-ROM Chaparral Exhibits D049), Aug. 8, 1996.Applicant
- C++ SourceCode for the SCSI Command Handler (Davies Ex 5 (CNS 179136-168)) (CD-ROM Chaparral Exhibits D050), Aug. 8, 1996.Applicant
- Header File Data Structure (Davies Ex 6 (CNS 179997-180008)) (CD-ROM Chaparral Exhibits D051), Jan. 2, 1997.Applicant
- SCSI Command Handler (Davies Ex 7 (CNS 179676-719)) (CD-ROM Chaparral Exhibits D052), Jan. 2, 1997.Applicant
- Coronado: Fibre Channel to SCSI Intelligent RAID Controller Product Brief (Kalwitz Ex I (CNS 182804-805)) (CD-ROM Chaparral Exhibits D053).Applicant
- Bill of Material (Kalwitz Ex 2 (CNS 181632-633)) (CD-ROM Chaparral Exhibits D054), Mar. 17, 1997.Applicant
- Emails Dated Jan. 13-Mar. 31, 1997 from P. Collins to Mo re: Status Reports (Kalwitz Ex 3 (CNS 182501-511)) (CD-ROM Chaparral Exhibits D055).Applicant
- Hardware Schematics for the Fibre Channel Daughtercard Coronado (Kalwitz Ex 4 (CNS 181639-648)) (CD-ROM Chaparral Exhibits D056).Applicant
- Adaptec Schematics re AAC-340 (Kalwitz Ex 14 (CNS 177215-251)) (CD-ROM Chaparral Exhibits D057).Applicant
- Bridge Product Line Review (Manzanares Ex 3 (CNS 177307-336)) (CD-ROM Chaparral Exhibits D058).Applicant
- AEC Bridge Series Products-Adaptec External Controller RAID Products Pre-Release Draft, v.6 (Manzanares Ex 4 (CNS 174632-653)). (CD-ROM Chaparral Exhibits D059), Oct. 28, 1997.Applicant
- Hewlett-Packard Roseville Site Property Pass for Brian Smith (Dunning Ex 14 (HP 489) (CD-ROM Chaparral Exhibits D078), Nov. 7, 1996.Applicant
- Distribution Agreement Between Hewlett-Packard and Crossroads (Dunning Ex 15 (HP 326-33) (CD-ROM Chaparral Exhibits D079).Applicant
- HPFC-5000 Tachyon User's Manuel, First Edition (PTI 172419-839) (CD-ROM Chaparral Exhibits D084), May 1, 1996.Applicant
- X3T10 994D—(Draft) Information Technology: SCSI-3 Architecture Model, Rev. 1.8 (PTI 165977) (CD-ROM Chaparral Exhibits D087).Applicant
- X3T10 Project 1047D: Information Technology- SCSI-3 Controller Commands (SCC), Rev, 6c (PTI 166400-546) (CD-ROM Chaparral Exhibits D088), Sep. 3, 1996.Applicant
- X3T10 995D- (Draft) SCSI-3 Primary Commands, Rev. 11 (Wanamaker Ex 5 (PTI 166050-229)) (CD-ROM Chaparral Exhibits D089), Nov. 13, 1996.Applicant
- VBAR Volume Backup and Restore (CRDS 12200-202) (CD-ROM Chaparral Exhibits D099).Applicant
- Preliminary Product Literature for Infinity Commstor's Fibre Channel to SCSI Protocol Bridge (Smith Ex 11; Quisenberry Ex 31 (SPLO 428-30) (CD-ROM Chaparral Exhibits D143), Aug. 19, 1996.Applicant
- Letter dated Jul. 12, 1996 from J. Boykin to B. Smith re: Purchase Order for Evaluation Units from Crossroads (Smith Ex 24) CRDS 8556-57) (CD-ROM Chaparral Exhibits D144), Jul. 12, 1996.Applicant
- CrossPoint 4100 Fibre Channel to SCSI Router Preliminary Datasheet (Hulsey Ex 9 (CRDS 16129-130)) (CD-ROM Chaparral Exhibits D145), Nov. 1, 1996.Applicant
- CrossPoint 4400 Fibre Channel to SCSI Router Preliminary Datasheet (Bardach Ex. 9 Quisenberry Ex 33 (CRDS 25606-607)) (CD-ROM Chaparral Exhibits D153), Nov. 1, 1996.Applicant
- Fax Dated Jul. 22, 1996 from L. Petti to B. Smith re: Purchase Order from Data General for FC2S Fibre to Channel SCSI Protocol Bridge Model 11 (Smith Ex 25; Quisenberry Ex 23; Bardach Ex 11 (CRDS 8552-55;8558) (CD-ROM Chaparral Exhibits D155).Applicant
- Email Dated Dec. 20, 1996 from J. Boykin to B. Smith re: Purchase Order for Betas in Feb. and Mar. (Hoese Ex 16, Quisenberry Ex 25; Bardach Ex 12 (CRDS 13644-650) (CD-ROM Chaparral Exhibits D156).Applicant
- Infinitiy Commstor Fibre Channel Demo for Fall Comdex, 1996 (Hoese Ex 15, Bardach Ex 13 (CRDS 27415) (CD-ROM Chaparral Exhibits D157).Applicant
- Fax Dated Dec. 19, 1996 from B. Bardach to T. Rarich re: Purchase Order Information (Bardach Ex. 14; Smith Ex 16 (CRDS 4460)) (CD-ROM Chaparral Exhibits D158).Applicant
- Miscellaneous Documents Regarding Comdex (Quisenberry Ex 2 (CRDS 27415-465)) (CD-ROM Chaparral Exhibits D165).Applicant
- CrossPoint 4100 Fibre Channel to SCSI Router Preliminary Datasheet (Quisenberry) Ex 3 (CRDS 4933-34) (CD-ROM Chaparral Exhibits D166) (CD-ROM Chaparral Exhibits D166).Applicant
- CrossPoint 4400 Fibre to Channel to SCSI Router Preliminary Datasheet; Crossroads Company and Product Overview (Quisenberry Ex 4 (CRDS 25606; 16136)) (CD-ROM Chaparral Exhibits D167).Applicant
- Crossroads Purchase Order Log (Quisenberry Ex 9 (CRDS 14061-062)) (CD-ROM Chaparral Exhibits D172).Applicant
- RAID Manager 5 with RDAC 5 for UNIX V.4 User's Guide (LSI-01854) (CD-ROM Chaparral Exhibits P062), Sep. 1, 1996.Applicant
- Letter dated May 12, 1997 from Alan G. Leal to Barbara Bardach enclosing the original OEM License and Purchase Agreement between Hewlett-Package Company and Crossroads Systems, Inc. (CRDS 02057) (CD-ROM Chaparral Exhibits P130).Applicant
- CR4x00 Product Specification (CRDS 43929) (CD-ROM Chaparral Exhibits P267), Jun. 1, 1998.Applicant
- Symbios Logic—Hardware Function Specification for the Symbios Logic Series 3 Fibre Channel Disk Array Controller Model 3701 (Engelbrecht Ex 3 (LSI-1659-1733) (CD-ROM Pathlight Exhibits D074).Applicant
- Report of the Working Group on Storage I/O for Large Scale Computing; Department of Computer Science Duke University: CS-1996-21 (PTI 173330-347). (CD-ROM Pathlight Exhibits D098).Applicant
- Brian Allison's 1999 Third Quarter Sales Plan (PDX 38 ) CNS 022120-132)) (CD-ROM Pathlight Exhibits D201), Jun. 5, 2001.Applicant
- Brooklyn SCSI-SCSI Intellegent External RAID Bridge Definition Phase External Documentation (CD-ROM Pathlight Exhibits D129).Applicant