CA2472056C - Methods and apparatus for encapsulating a frame for transmission in a storage area network - Google Patents
Methods and apparatus for encapsulating a frame for transmission in a storage area network Download PDFInfo
- Publication number
- CA2472056C CA2472056C CA2472056A CA2472056A CA2472056C CA 2472056 C CA2472056 C CA 2472056C CA 2472056 A CA2472056 A CA 2472056A CA 2472056 A CA2472056 A CA 2472056A CA 2472056 C CA2472056 C CA 2472056C
- Authority
- CA
- Canada
- Prior art keywords
- frame
- packet
- header
- field
- storage area
- 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.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2212/00—Encapsulation of packets
Abstract
Methods and apparatus for encapsulating a packet or frame for transmission in a storage area network are disclosed. A packet or frame compatible with a standard protocol employed in the storage area network is received or generated. The packet or frame is then encapsulated with a virtual storage area network identifier. The packet or frame may further be encapsulated with at least one of a TTL value, MPLS information, and a type of traffic to be carried by the packet or frame. For instance, the type of traffic to be carried by the packet or frame may include Ethernet, Fibre Channel, and Infiniband. Once encapsulated, the encapsulated packet or frame is sent over the storage area network. For instance, the encapsulated packet or frame may be generated as well as transmitted by a switch over an inter-switch link in the storage area network.
Description
METHODS AND APPARATUS FOR ENCAPSULATING A
FRAME FOR TRANSMISSION IN A STORAGE AREA
NETWORK
BACKGROUND OF THE INVENTION
1. Field of the Invention The present invention relates to network technology. More particularly, the present invention relates to methods and apparatus for encapsulating a frame for transmission in a storage area network.
FRAME FOR TRANSMISSION IN A STORAGE AREA
NETWORK
BACKGROUND OF THE INVENTION
1. Field of the Invention The present invention relates to network technology. More particularly, the present invention relates to methods and apparatus for encapsulating a frame for transmission in a storage area network.
2. Description of the Related Art When interconnecting computers and other devices in a networle, it has become desirable to create "virtual local area networlcs" (VLANs), in which all devices coupled to a VLAN receive all frames or packets which are universally addressed (whether by broadcast, multicast, or some other technique) on that VLAN, and in which all frames or packets which are universally addressed by a device on a VLAN are not distributed to devices outside the ULAN. The VLAN approach is particularly desirable when a single physical infrastructure is to be made available to multiple parties, each requiring that its data be kept private from the other parties. Further, the VLAN
approach protects network entities on a given VLAN from failures of devices on the same infrastructure but belonging to a different VLAN.
Various ULAN transport protocol technologies have been proposed and come to be accepted in the art. For example, VLAN technologies which are now common include LANE (for ATM LAN-Emulation), IEEE Standard,802.10, and various proprietary schemes such as Inter-Switch Links (ISL) (e.g., for Cisco Catalyst.TM.
Inter-Switch Links).
In order to allow multiple VLANs to share a single inter-switch link on the underlying physical topology, the interswitch link protocol (ISL) was developed at S Cisco Systems. See for example U.S. Pat. No. 5,742,604, entitled "Interswitch link mechanism for connecting high-performance networlc switches," Edsall, et al., issued on April 21, 1998 to Cisco Systems, Inc., which is hereby incorporated by reference for all purposes. ISL provides an encapsulation mechanism for transporting packets between poets of different switches in a network on the basis of VLAN
associations among those ports Although ISL supports multiple VLANs on a single underlying network topology, certain limitations have been observed. Some of these limitations prevent easy implementation of ISL on modern storage area networks (SANs).
In recent years, the capacity of storage devices has not increased as fast as the demand for storage. Therefore a given server or other host must access multiple, physically distinct storage nodes (typically disks). In order to solve these storage limitations, the storage area network was developed. Generally, a storage area network is a high-speed special-purpose network that interconnects different data storage devices and associated data hosts on behalf of a larger network of users.
However, although a SAN enables a storage device to be configured for use by various networlc devices and/or entities within a network, data storage needs are often dynamic rather than static.
A SAN may use various types of network traffic such as Ethernet or Fibre Channel frames. Regardless of the technology used, current SAN technology requires that a single protocol (e.g., Fibre Channel) be used throughout a particular SAN. Thus, current technology fails to address the need for supporting a multiple SAN
system in which different transport protocols or technologies simultaneously co-exist.
Note that ISL was originally designed for encapsulation of Ethernet packets. It does not support multiple different protocols on a single physical network infrastructure.
Ethernet is currently the most widely-installed LAN technology. The most commonly installed Ethernet systems are lOBASE-T systems, which provide transmission speeds up to 10 Mbps. Alternatively, fast Ethernet systems, systems, provide transmission speeds up to 100 megabits per second, while Gigabit Ethernet provides support at 1000 megabits per second (or 1 billion bits per second).
While Ethernet is widely used, use of fibre channel is proliferating in systems which demand lugh bandwidth and low latency. More specifically, the fibre channel family of standards (developed by the American National Standards Institute (ANSI)) defines a high speed communications interface for the transfer of large amounts of data between a variety of hardware systems such as personal computers, workstations, mainframes, supercomputers, storage devices and servers that have fibre channel interfaces. Fibre channel is particularly suited for connecting computer servers to shared storage devices and for interconnecting storage controllers and drives.
Moreover, fibre channel is capable of transmitting data between computer devices at a data rate of up to 1 Gbps (or 1 billion bits per second), and a data rate of 10 Gbps has been proposed by the Fibre Chamlel Industry Association. Accordingly, fibre channel is a technology that is in widespread use for transmitting data in SANS.
However, as indicated above, ISL was not optimized for fibre channel transmissions.
approach protects network entities on a given VLAN from failures of devices on the same infrastructure but belonging to a different VLAN.
Various ULAN transport protocol technologies have been proposed and come to be accepted in the art. For example, VLAN technologies which are now common include LANE (for ATM LAN-Emulation), IEEE Standard,802.10, and various proprietary schemes such as Inter-Switch Links (ISL) (e.g., for Cisco Catalyst.TM.
Inter-Switch Links).
In order to allow multiple VLANs to share a single inter-switch link on the underlying physical topology, the interswitch link protocol (ISL) was developed at S Cisco Systems. See for example U.S. Pat. No. 5,742,604, entitled "Interswitch link mechanism for connecting high-performance networlc switches," Edsall, et al., issued on April 21, 1998 to Cisco Systems, Inc., which is hereby incorporated by reference for all purposes. ISL provides an encapsulation mechanism for transporting packets between poets of different switches in a network on the basis of VLAN
associations among those ports Although ISL supports multiple VLANs on a single underlying network topology, certain limitations have been observed. Some of these limitations prevent easy implementation of ISL on modern storage area networks (SANs).
In recent years, the capacity of storage devices has not increased as fast as the demand for storage. Therefore a given server or other host must access multiple, physically distinct storage nodes (typically disks). In order to solve these storage limitations, the storage area network was developed. Generally, a storage area network is a high-speed special-purpose network that interconnects different data storage devices and associated data hosts on behalf of a larger network of users.
However, although a SAN enables a storage device to be configured for use by various networlc devices and/or entities within a network, data storage needs are often dynamic rather than static.
A SAN may use various types of network traffic such as Ethernet or Fibre Channel frames. Regardless of the technology used, current SAN technology requires that a single protocol (e.g., Fibre Channel) be used throughout a particular SAN. Thus, current technology fails to address the need for supporting a multiple SAN
system in which different transport protocols or technologies simultaneously co-exist.
Note that ISL was originally designed for encapsulation of Ethernet packets. It does not support multiple different protocols on a single physical network infrastructure.
Ethernet is currently the most widely-installed LAN technology. The most commonly installed Ethernet systems are lOBASE-T systems, which provide transmission speeds up to 10 Mbps. Alternatively, fast Ethernet systems, systems, provide transmission speeds up to 100 megabits per second, while Gigabit Ethernet provides support at 1000 megabits per second (or 1 billion bits per second).
While Ethernet is widely used, use of fibre channel is proliferating in systems which demand lugh bandwidth and low latency. More specifically, the fibre channel family of standards (developed by the American National Standards Institute (ANSI)) defines a high speed communications interface for the transfer of large amounts of data between a variety of hardware systems such as personal computers, workstations, mainframes, supercomputers, storage devices and servers that have fibre channel interfaces. Fibre channel is particularly suited for connecting computer servers to shared storage devices and for interconnecting storage controllers and drives.
Moreover, fibre channel is capable of transmitting data between computer devices at a data rate of up to 1 Gbps (or 1 billion bits per second), and a data rate of 10 Gbps has been proposed by the Fibre Chamlel Industry Association. Accordingly, fibre channel is a technology that is in widespread use for transmitting data in SANS.
However, as indicated above, ISL was not optimized for fibre channel transmissions.
-3-In view of the above, it would be desirable if properties of a VLAN could be merged with those of a SAN to enable various storage devices to be logically assigned to various entities within a networlc. Moreover, it would be beneficial if a single switching mechanism could simultaneously support different transport protocols (including at least fibre channel) within a network such as a SAN.
SUMMARY OF THE INVENTION
Methods and apparatus for encapsulating a paclcet or frame for transmission in a storage area network are disclosed. More particularly, according to the disclosed encapsulation process, a paclcet or frame is encapsulated with a virtual storage area network (VSAN) identifier. Through generation and transmission of such an encapsulated packet or frame, implementation of a single VSAN as well as a network including multiple interconnected VSANs may be achieved.
In accordance with various embodiments of the present invention, an encapsulation mechanism is implemented in a virtual storage area network (VSAN). Through the concept of a VSAN, one or more network devices (e.g., servers) and one or more data storage devices are grouped into a logical network defined within a common physical infrastructure. Each VSAN is uniquely identified by a VSAN identifier.
hl accordance with one aspect of the invention, a packet or frame compatible with a standard protocol employed in the storage area network is received or generated. The packet or frame is then encapsulated with a VSAN
identifier. For instance, a new header (or trailer) may be appended to the packet or
SUMMARY OF THE INVENTION
Methods and apparatus for encapsulating a paclcet or frame for transmission in a storage area network are disclosed. More particularly, according to the disclosed encapsulation process, a paclcet or frame is encapsulated with a virtual storage area network (VSAN) identifier. Through generation and transmission of such an encapsulated packet or frame, implementation of a single VSAN as well as a network including multiple interconnected VSANs may be achieved.
In accordance with various embodiments of the present invention, an encapsulation mechanism is implemented in a virtual storage area network (VSAN). Through the concept of a VSAN, one or more network devices (e.g., servers) and one or more data storage devices are grouped into a logical network defined within a common physical infrastructure. Each VSAN is uniquely identified by a VSAN identifier.
hl accordance with one aspect of the invention, a packet or frame compatible with a standard protocol employed in the storage area network is received or generated. The packet or frame is then encapsulated with a VSAN
identifier. For instance, a new header (or trailer) may be appended to the packet or
-4-frame compatible with the standard protocol. Once encapsulated, the encapsulated packet or frame is sent over the storage axea network. The encapsulated packet or frame is typically sent over a lii~le such as an enhanced interswitch link shared by multiple VSANs.
W addition to the VSAN identifier, the encapsulated packet or frame may include further information. More particularly, in accordance with one embodiment, the packet or frame is also encapsulated with at least one of a Time To Live (TTL) value and/or Multi-Protocol Label Switching (MPLS) information.
For instance, the TTL value may be used to specify a number of remaining hops that can be traversed before the encapsulated packet or frame is dropped. The TTL
value may also be used to specify a remaining lifetime in units of time (e.g.
milliseconds). MPLS is a common forwarding mechanism used in various technologies to forward packets and frames such as 1P packets and Ethernet frames.
However, MPLS has not been implemented or proposed for use with Fibre Channel frames.
In accordance with another embodiment, the frame is encapsulated with a type of traffic to be ca~.-ried by the frame. For instance, the type of traffic to be earned by the frame may include Ethernet, Fibre Channel, and Infiniband.
Typically, this "type" refers to the standard protocol employed to generate the frame in question. Through the identification of a traffic type, frames carrying a variety of traffic types may be transmitted within a VSAN. Moreover, multiple VSANs, each capable of supporting different traffic types, may be interconnected through the identification of a traffic type in the newly appended header.
W addition to the VSAN identifier, the encapsulated packet or frame may include further information. More particularly, in accordance with one embodiment, the packet or frame is also encapsulated with at least one of a Time To Live (TTL) value and/or Multi-Protocol Label Switching (MPLS) information.
For instance, the TTL value may be used to specify a number of remaining hops that can be traversed before the encapsulated packet or frame is dropped. The TTL
value may also be used to specify a remaining lifetime in units of time (e.g.
milliseconds). MPLS is a common forwarding mechanism used in various technologies to forward packets and frames such as 1P packets and Ethernet frames.
However, MPLS has not been implemented or proposed for use with Fibre Channel frames.
In accordance with another embodiment, the frame is encapsulated with a type of traffic to be ca~.-ried by the frame. For instance, the type of traffic to be earned by the frame may include Ethernet, Fibre Channel, and Infiniband.
Typically, this "type" refers to the standard protocol employed to generate the frame in question. Through the identification of a traffic type, frames carrying a variety of traffic types may be transmitted within a VSAN. Moreover, multiple VSANs, each capable of supporting different traffic types, may be interconnected through the identification of a traffic type in the newly appended header.
-5-Various network devices may be configured or adapted for generation of a frame compatible with a standard protocol (e.g., Fibre Channel). Similarly, a variety of network devices may be capable of receiving the frame, encapsulating the frame, and sending the encapsulated frame via a VSAN. These network devices include, but are not limited to, servers (e.g., hosts) and switches.
Moreover, the functionality for the above-mentioned generation and encapsulation processes may be implemented in software as well as hardware.
Yet another aspect of the invention pertains to computer program products including machine-readable media on which are provided program instructions for implementing the methods and techniques described above, in whole or in part.
Any of the methods of this invention may be represented, in whole or in part, as program instructions that can be provided on such machine-readable media. In addition, the invention pertains to various combinations and arrangements of data generated and/or used as described herein. For example, encapsulated frames having the format described herein and provided on appropriate media are part of this invention.
These and other features of the present invention will be described in more detail below in the detailed description of the invention and in conjunction with the following figures.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a diagram illustrating an exemplary storage area networlc, including multiple VSANs, in which the present invention may be implemented.
Moreover, the functionality for the above-mentioned generation and encapsulation processes may be implemented in software as well as hardware.
Yet another aspect of the invention pertains to computer program products including machine-readable media on which are provided program instructions for implementing the methods and techniques described above, in whole or in part.
Any of the methods of this invention may be represented, in whole or in part, as program instructions that can be provided on such machine-readable media. In addition, the invention pertains to various combinations and arrangements of data generated and/or used as described herein. For example, encapsulated frames having the format described herein and provided on appropriate media are part of this invention.
These and other features of the present invention will be described in more detail below in the detailed description of the invention and in conjunction with the following figures.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a diagram illustrating an exemplary storage area networlc, including multiple VSANs, in which the present invention may be implemented.
-6-FIG. 2 is a diagram illustrating an "extension" to a frame such as a fibre charnel in accordance with one embodiment of the invention.
FIG. 3 is a diagram illustrating an extended ISL (EISL) frame format including an EISL header in accordance with one embodiment of the invention.
FIG. 4 is a diagram illustrating an exemplary EISL header (and associated MPLS label stacle) that may be transmitted in a frame having an EISL frame format such as that illustrated in FIG. 3.
FIG. 5 is a diagram illustrating an exemplary MPLS label format that may be used for each label in the MPLS label stack of FIG. 4 in accordance with one embodiment of the invention.
FIG. 6 is a diagram illustrating an exemplary network device in which embodiments of the invention may be implemented.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
In the following description, numerous specific details axe set forth in order to provide a thorough understanding of the present invention. It will be obvious, however, to one spilled in the art, that the present invention may be practiced without some or all of these specific details. In other instances, well known process steps have not been described in detail in order not to unnecessarily obscure the present invention.
As described above, a storage area network (SAN) is a network that interconnects different data storage devices with associated networlc hosts (e.g., data servers or end user machines) on behalf of a larger network of users. A
SAN
is defined by the physical configuration of the system. In other words, those devices in a SAN must be physically interconnected.
In accordance with various embodiments of the present invention, the physical SAN is shared by multiple virtual storage area networks (VSANs), each using some or all of the physical infrastructure of the SAN. An encapsulation mechanism is employed to implement the VSANs. Through the concept of a VSAN, one or more network devices (e.g., servers) and one or more data storage devices are grouped into a logical network defined within a common physical network infrastructure. Communication among these devices may be accomplished by coupling the network devices and data storage devices together through one or more switches. Exemplary data storage devices that may be used in a VSAN include, but are not limited to, storage disks in various configurations such as a redundant array interconnected disk (RAID).
Each VSAN is uniquely identified by a VSAN identifier rather than any particular physical configuration of devices within the network. For instance, a unique identifier may be simultaneously associated with one or more network devices as well as one or more storage devices. W general, the VSAN identifier does not represent any particular physical network device or link.
Within a ULAN infrastructure, individual VLANs are distinguished through the use of a VLAN identifier (e.g., within the range of zero through 4094).
W accordance with various embodiments of the invention, individual VSANs will be distinguished within a VSAN infrastructure through the use of a VSAN
identifier, as described above. It would be desirable to support mixed _g_ infrastructures containing both VLANs and VSANs, for example, using a trunk link or router able to carry traffic among VLANs and VSANs.
In accordance with one embodiment, VLAN identifiers and VSAN
identifiers share the same number space. In other words, any given number can be a VSAN identifier or a VLAN identifier, but cannot be used to independently identify a VSAN and a VLAN at the same time. For example, it would not be possible to have both a VSAN #1 and VLAN #1 at the same time.
In accordance with another embodiment, VLAN identifiers and VSAN
identifiers have independent number spaces. In other words, a given number can be either a VSAN identifier or a VLAN identifier, as well as an identifier for both a VSAN and a VLAN simultaneously. Since a number may correspond to either a VSAN or a VLAN, the type of network (e.g., VSAN or VLAN) is also identified.
Thus, VSAN #1 and VLAN #1 can both exist at the same time as different and independent virtual networks. This type may be a separate field in the EISL
header or may be incorporated into the frame type (e.g., traffic type), which will be described in further detail below with reference to FIG. 4.
FIG. 1 is a diagram illustrating an exemplary storage area network 101 in which the present invention may be implemented. As shown in FIG. 1, data storage devices 102, 104, 106, 108, 110, and 112 axe coupled to hosts (e.g., servers) 114, 116, and 128 via several switches 118, 120, and 122. The switches commuW cate with one another via interswitch links 124 and 126. The elements described in this paragraph together comprise the physical infrastructure of SAN
101. The storage devices, switches, and hosts of SAN 101 communicate using one or more standard protocols such as fibre channel (FC), fibre channel IP
(FCIP), SCSI, SCSI over IP, Ethernet, Infiniband, and the like. Sometimes, these protocols are referred to herein as "types" of traffic.
One or more VSANs may be created through logically grouping various network devices with selected data storage devices. For instance, as shown in FIG.
1, a first VSAN, VSANl, consists of server 114, 128 and data storage devices 102, 106, 110, and 114, while a second VSAN, VSAN2, consists of server 116, 128 and data storage devices 104, 108, and 112. Note that both VSANl and VSAN2 share the interswitch links 124 and 126 to communicate. For example, both host 114 of VSANl and host 116 of VSAN2 use link 126 to access storage device 110 and storage device 112, respectively.
To ensure that network traffic crossing interswitch links 124 and 126 is properly routed to (and limited to) devices within the associated VSANs, the traffic must be identifiable as either VSAN1 traffic or VSAN2 traffic. Tlus can be accomplished in various ways. One convenient methodology employed with this invention encapsulates data frames with some sort of VSAN identifier. That way switches 118, 120, and 122 can examine frames crossing linlcs 124 and 126 to determine which VSAN is involved and make appropriate switching decisions based upon this information.
Various embodiments of the invention may be applied to encapsulate a packet or frame as described below with reference to FIGs. 2 through 5. The distinction between packet and frame is not universally accepted. However, one distinction that is commonly used is defined as follows. A packet is the unit of data that is routed between an origin and a destination on the Internet or any other packet-switched networlc. Each packet is separately numbered and includes the Internet address of the destination. In contrast, a frame is data that is transmitted between. adjacent network devices. The information or data in the frame may contain packets or other data units used in a higher-level or different protocol.
For convenience, the subsequent discussion will describe encapsulated f~a~nes used to transmit data over SAN. Switches act on frames and use information about VSANs to make switching decisions. Thus, in accordance with various embodiments of the invention, frames that originate within a VSAN are constrained to stay within the physical resources allotted to that VSAN. Thus, a gateway working at a lugher protocol layer (e.g., application layer 7) may pass such a packet from one VSAN to another. In order to enforce this restriction, frames may be encapsulated with a structure that identifies a VSAN to which the frames belong. Once encapsulated, the encapsulated frame is moved across network nodes; in particular over inter-switch links in the storage area network.
Thus, through tlus encapsulation, a single link may transport frames associated with multiple VSANs. An exemplary encapsulated paclcet will be described in further detail below with reference to FIG. 3 and FIG. 4.
Note that the frames being encapsulated possess the frame format specified for a standard protocol such as Ethernet or fibre channel. Hence, software and hardware conventionally used to generate such frames may be employed with this invention. Additional hardware and/or software is employed to encapsulate the standard frames in accordance with this invention. Those of skill in the art will understand how to develop the necessary hardware and software to allow encapsulation of the type described below.
In accordance with the present invention, a frame compatible with a standard protocol employed in a storage area network is obtained at a node where encapsulation subsequently takes place. The frame is generated by a network device such as a host, switch, or storage device. In a typical scenario, the host machine generates the frame in accordance with a standard protocol such as fibre channel and forwards the frame to a switch. The switch then performs an encapsulation process such as that described below. In some embodiments, the host or storage device may itself perform the encapsulation described herein.
In still other embodiments, the switch may receive a data stream and first frame it in accordance with a standard protocol and then encapsulate the resulting frame to produce the new frames of this invention. The resulting encapsulated frame is sometimes referred to herein an "extended ISL" (EISL) frame because of its general relationship with the interswitch link protocol described in US
Patent No. 5,742,604, previously incorporated by reference.
As just explained, the encapsulation process may be performed by a network device outside the switch (e.g., by a host) as well as within a switch.
Obviously, the appropriate network devices should be configured with the appropriate software and/or hardware for performing EISL encapsulation. Of ' course, all network devices within the storage area network need not be configured with EISL encapsulation software (or hardware). Rather, selected network devices may be configured with or adapted for EISL encapsulation functionality.
Similarly, in various embodiments, such EISL encapsulation functionality may be enabled or disabled through the selection of various modes. Moreover, it may be desirable to configure selected ports of networlc devices as EISL-capable ports capable of performing EISL encapsulation, either continuously, or only when in an EISL
enabled state.
The standard protocol (e.g., layer 2 protocol) employed in the storage area network (i.e., the protocol used to frame the data) will typically, although not necessarily, be synonymous with the "type of traffic" carried by the network.
As explained below, the type of traffic is defined in some encapsulation formats.
Examples of the type of traffic are typically layer 2 or corresponding layer formats such as Ethernet and Fibre Channel.
Another type of traffic that may be used within a VSAN is an InfiniBand architecture, which is a relatively recent input/output (I/O) specification for servers.
More particularly, connections between servers, remote storage and networking are accomplished by attaching all devices through a central, unified, fabric of InfiniBand switches and links. Stated benefits of the InfiniBand architecture include lower latency, easier and faster sharing of data, and built in security and quality of service. The InfiniBand architecture is a rapidly developing technology for server clusters as well as I/O for remote storage and networking. Thus, the InfiniBand Architecture is well suited to address the demands generated by the rapid growth of the Internet and the convergence of data and telecommunications (voice, data, video, and storage) on the W ternet. With InfiniBand, data is transmitted in one or more packets that together form a message. For instance, a message can be a remote direct memory access (RDMA) read or write operation, a channel send or receive message, a transaction-based operation (that can be reversed), or a multicast transmission.
In addition, other types of traffic may include token ring, token bus, and various protocols compatible with satellite systems such as Aloha. It is also important to note that the type of traffic should also be supported by the technology used in the storage area network. For instance, the technology used in the hosts and/or switches (e.g., interface port circuitry) as well as the communication mediums should support the traffic type being carried in the encapsulated frame.
As shown in FIG. 2, a frame compatible with a standard protocol employed in a storage area network is obtained. For instance, a frame such as a fibre channel frame 202 typically includes a header 204, payload 206 and error checlc information such as a cyclic redundancy checking (CRC) value 208. Cyclic redundancy checl~ing is a method of checking a received frame for errors in data that has been transmitted on a communications link. As described above, it is necessary to identify the VSAN associated with the frame 202. However, pursuant to the standard governing fibre channel, the header 204 of a fibre channel frame 202 does not include unused bits to enable additional fields to be defined. As a result, an "extension" 210 to the frame 202 is required. Extension 210 may assume various formats. Importantly, it should include at least information identifying the VSAN and other information specifying one or more of the following: type of traffic, MPLS information, and time to live.
In accordance with various embodiments, as shown in FIG. 3, a new frame 302 having an extended ISL (EISL) format is generated from information obtained from the original frame 202. More particularly, encapsulation may include the appending of a new header (or trailer) to the original frame 202. For instance, as shown, the new frame 302 includes a payload 303 that preferably includes both the header 204 and payload 206 of the original frame, and a new EISL header 304.
In addition, the payload 303 may also include the CRC 208 of the original frame.
Encapsulation may also comprise the modification or replacement of the original CRC value 208 with a new (e.g., additional) or modified CRC value 306. More particularly, since the new frame is longer than the original frame 202, a new CRC
value 306 may be generated (e.g., calculated) to correspond the longer length of the frame 302 that includes the newly appended EISL header 304 and its associated length. This new CRC 306 may therefore replace the original CRC 208. In this manner, a new frame is generated by encapsulating the frame with an EISL
header.
In accordance with various embodiments, an EISL frame 302 such as that illustrated in FIG. 3 is preceded by a start of frame (SOF) delimiter 308 and terminated by an end of frame (EOF) delimiter 310. These delimiters enable an EISL-capable port to receive and recognize frames in EISL format. However, if an EISL-capable port is not in EISL mode or, alternatively, the port is not EISL-capable and it receives frames in the EISL format, it can drop the frame.
FIG. 4 is a diagram illustrating an exemplary EISL header of a frame that has an overall EISL frame format such as that illustrated in FIG. 3. More particularly, as described above, the EISL header preferably identifies a VSAN. In addition, encapsulation may include providing further information in the encapsulated frame. As will be described in further detail below, the EISL
header may supply fiuther information in various fields of the EISL header. More particularly, an EISL indicator field 402 may be used to indicate the presence of an EISL header. In addition, an EISL version indicator field 404 may indicate a version of EISL used to create the frame. In a specific example, the EISL
version indicator field 404 of the EISL header includes at least 2 bits.
The EISL header further includes a field indicating a frame type 406 (i.e., traffic type). The type of traffic (e.g., payload) to be carried by the frame may include a variety of traffic types such as those described above, including but not limited to, Ethernet, fibre chaimel, and Infiniband. In one embodiment, the frame type field 406 is a 4-bit field. Through the identification of a traffic type, EISL
formatted frames carrying a variety of traffic types may be transmitted within a VSAN. Moreover, multiple VSANs, each capable of supporting different traffic types, may be interconnected through the identification of a traffic type in the newly appended EISL header.
Multi-Protocol Label Switching (MPLS) label field (e.g., Indicator) 408 indicates whether the EISL header is carrying MPLS information such as an MPLS
label stack, a common forwarding mechanism for both fibre channel and Ethernet frames. An exemplary MPLS label stack will be described in further detail below with reference to FIG. 5. In one embodiment, the MPLS label field 408 is a 1-bit field. More particularly, the MPLS label field 408 indicates whether or not MPLS
labels are provided in the EISL frame. For instance, the indicator may be set to 1 if the EISL header includes an MPLS label stack and otherwise be set to 0. The MPLS label field 408 may also indicate the number of labels present in 416.
Priority field 410 may indicate a user priority for the EISL frame. The user priority may represent various types of priorities. As one example, the user priority may be a generic priority, without a guaranteed level of service, that is used to merely indicate a priority such as a numerical ranl~ing. For instance, higher values simply represent higher user priority while lower values may represent lower priority. Higher priority users receive available bandwidth first, regardless of how much total bandwidth is available. The number of bits used for this field will vary with the number of priority levels or values implemented.
As another example, the user priority may indicate a quality of service (QoS) of the payload of the EISL frame. On the Internet and in other networks, QoS is the idea that transmission rates, error rates, and other characteristics can be measured, improved, and, to some extent, guaranteed in advance. QoS is of particular concern for the continuous transmission of high-bandwidth video and multimedia information. Transmitting this bind of content dependably is difficult in public networks using ordinary "best effort" protocols. Typically, the number of bits required for a priority field are greater to specify the quality of service than a simple numerical priority. In one embodiment, the priority field 410 is a 3-bit field.
As described above, the EISL header, at a minimum, includes a VSAN
identifier field 412 adapted for including a VSAN identifier that identifies one or more VSANs. More particularly, in accordance with one embodiment, the VSAN
identifier identifies a VSAN associated with the payload of the EISL frame, and therefore the payload of the original frame (e.g., Fibre Channel frame). In accordance with one embodiment, the VSAN identifier field 412 is a 12-bit field.
The format of the identifier may be identical to or similar to VLAN
identifiers as well as similar to addresses employed in certain standard protocols such as Ethernet.
In some storage area networks, there may be topology as well as routing problems that could cause a frame to traverse a loop within the network. Such a loop will consume bandwidth unnecessarily. liz order to solve this problem, a Time To Live (TTL) field 414 may be used to indicate a TTL value specifying the number of remaining hops that can be traversed before the frame is dropped.
More specifically, the TTL value of the TTL field 414 is initialized by the network device (e.g., switch) that generates the EISL frame including the EISL header.
A
default value may, for example, be set to 16. Subsequent network devices (e.g., switches) receiving the EISL frame decrement the TTL value of the TTL field by 1.
In accordance with one embodiment, a TTL value of 1 indicates to the receiving network device (e.g., switch) that the EISL frame should be dropped.
When the EISL frame is dropped, an error message may be sent to the intended recipient of the frame as well as to the sender of the frame. Similarly, a TTL
value of 0 may indicate that the TTL field 414 should be ignored, allowing the EISL
frame to be forwarded by the switch. In accordance with one embodiment, the TTL field 414 is an 8-bit field.
As described above, an MPLS indicator 408 may be used to indicate whether the EISL header is carrying MPLS information such as an MPLS label stack 416. As a paclcet of a connectionless network layer protocol travels from one router to the next, each router malces an independent forwarding decision for that packet. That is, each router analyzes the packet's header, and each muter runs a network layer routing algorithm. Each router independently chooses a next hop for the packet, based on its analysis of the packet's header and the results of running the routing algorithm.
Paclcet headers contain considerably more information than is needed simply to choose the next hop. Choosing the next hop can therefore be thought of as the composition of two functions. The first function partitions the entire set of possible packets into a set of "Forwarding Equivalence Classes (FECs)." The second function maps each FEC to a next hop. Insofar as the forwarding decision is concerned, different packets which get mapped into the same FEC are indistinguishable. All packets which belong to a particular FEC and which travel from a particular node will follow the same path (or if certain kinds of mufti-path routing are in use, they will all follow one of a set of paths associated with the FEC).
In conventional IP forwarding, a particular router will typically consider two packets to be in the same FEC if there is some address prefix X in that router's routing tables such that X is the "longest match" for each packet's destination address. As the packet traverses the network, each hop in turn reexamines the packet and assigns it to a FEC. In MPLS, the assignment of a particular packet to a particular FEC is done just once, as the packet enters the network. The FEC to which the packet is assigned is encoded as a short fixed length value known as a "label."
When a paclcet is forwarded to its next hop, the label is sent along with it;
that is, the packets are "labeled" before they are forwarded. At subsequent hops, there is no further analysis of the packet's network layer header. Rather, the label is used as an index into a table which specifies the next hop and a new label.
The old label is replaced with the new label, and the packet is forwarded to its next hop. In the MPLS forwarding paradigm, once a paclcet is assigned to a FEC, no fuuther header analysis is done by subsequent routers; all forwarding is driven by the labels. This has a number of advantages over conventional networlc layer forwarding. For instance, through MPLS labels, it is possible to circumvent conventional 1P routing. Further details of the MPLS forwarding mechanism and MPLS label stack encoding are disclosed in RFC 3031, Multiprotocol Label Switching Architecture, Rosen et al., January 2001 and RFC 3032, MPLS Label Stack Encoding, Rosen et al., January 2001, respectively, and are incorporated by reference for all purposes.
As described above with reference to block 408 of FIG. 4, an indicator may be used to indicate whether the EISL frame includes a label stack. W
accordance with one embodiment, a label stack may include a maximum of 4 labels. Each label in the label stack has an identical label format.
FIG. 5 is a diagram illustrating an exemplary MPLS label format that may be used for each label in the MPLS label stack of FIG. 4 in accordance with one embodiment of the invention. Label field 502 carries the actual value of the corresponding label used to make forwarding decisions. When a labeled packet is received, the label value at the top of the stack is looked up. As a result of a successful lookup in a corresponding table, file or database, the following information is ascertained: a) the next hop to which the paclcet is to be forwarded, and b) the operation to be performed on the label stack before forwarding;
this operation may be to replace the top label stack entry with another, to pop an entry off the label staclc, or to replace the top label stack entry and then to push one or more additional entries on the' label stack. In addition to learning the next hop and the label stack operation, one may also learn the outgoing data link encapsulation, and possibly other information which is needed in order to properly forward the packet. In accordance with one embodiment, the label field 502 is a 32-bit field.
Experimental field 504 may be reserved for experimental use. The experimental field 504 is typically used to encode the Differentiated Service Code Point (DSCP), which is a mechanism for Quality of Service.
In addition, a termination field 506 may be provided in the label to indicate if this label is the last label in the staclc. In accordance with one embodiment, the termination field is a single bit indicator. For instance, the termination field 506 may indicate that the label is the last label in the label stack when the indicator is in a first state (e.g., 1) and that the label is not the last label in the label staclc when the indicator is in a second state (e.g., 0).
The label may also include a TTL field 508. The TTL field 508 is typically used to provide TTL field semantics associated with IPv4 paclcets or Hop Count semantics associated with IPv6 packets.
As described above, encapsulation may be performed in a variety of network devices. FIG. 6 is a diagram illustrating an exemplary network device in which embodiments of the invention may be implemented. The network device illustrated is a hybrid switch that can switch both Ethernet and fibre channel frames. It is preferred that frames of various types (e.g., Ethernet and fibre channel) be transported via a single switching mechanism. Through the use of an extended ISL (EISL) frame format, frames of different types may be transported using the same switch or ISL, rather than dedicating a switch or ISL to different frame (or traffic) types.
As shown in FIG. 6, data is received by a port 602 of the switch via a bi-directional connector (not shown). In association with the incoming port, Media Access Control (MAC) block 604 is provided, which enables frames of various protocols such as Ethernet or fibre channel to be received. Once a frame is encapsulated as described above, it is then received by a forwarding engine 608, wluch obtains information from various fields of the frame, such as source address and destination address. The forwarding engine 608 then accesses a forwarding table (not shown) to determine whether the source address has access to the specified destination address. The forwarding engine 608 also determines the appropriate port of the switch via which to send the frame, and generates an appropriate routing tag for the frame.
Once the frame is appropriately formatted for transmission, the frame will be received by a buffer queuing block 606 prior to transmission. Rather than transmitting frames as they are received, it may be desirable to temporarily store the frame in a buffer or queue 606. For instance, it may be desirable to temporarily store a paclcet based upon Quality of Service in one of a set of queues that each correspond to different priority levels. The frame is then transmitted via switch fabric 610 to the appropriate port. Each outgoing port also has its own MAC
bloclc and bi-directional connector via which the frame may be transmitted.
Although the networlc device described above with reference to FIG. 6 is described as a switch, this network device is merely illustrative. Thus, other network devices such as routers may be implemented to receive, process, modify and/or generate packets or frames with functionality such as that described above for transmission in a storage area network. Moreover, the above-described network devices are merely illustrative, and therefore other types of networlc devices may be implemented to perform the disclosed encapsulation functionality.
Once the EISL frame is generated, the encapsulated frame may be sent by the switch over an inter-switch (ISL) link configured to couple source and destination port interface circuitry in a sequential arrangement of interconnected switches as illustrated in FIG. 1. The ISL link may consist of any type of media (e.g., twisted-pair or fiber) capable of functioning as an extension to a switching bus or other coxmnunication medium. Moreover, port interface circuitry may comprise encapsulation as well as decapsulation circuits. Since the interface to the ISL essentially comprises the port interface circuitry, any number of ports of a network device such as the switch illustrated in FIG. 6 are capable of being configured as EISL ports. That is, the ISL port interface circuit may include a circuit and/or otherwise be configured with software that includes functionality for encapsulating paclcets according to the disclosed EISL encapuslation mechanism, as well as decapsulating packets.
Although illustrative embodiments and applications of this invention are shovcnl and described herein, many variations and modifications are possible which remain within the concept, scope, and spirit of the invention, acid these variations would become clear to those of ordinary slcill in the art after perusal of tlus application. For instance, the present invention is described as being implemented using a specific EISL header. However, it should be understood that the invention is not limited to such implementations, but instead would equally apply regardless of the fields defined in such a header. Moreover, the present invention would apply regardless of the context and system in which it is implemented. Thus, broadly speaking, the operations described above need not be used within a SAN, but may be used to enable protocol compatibility within any network.
W addition, although an exemplary switch is described, the above-described embodiments may be implemented in a variety of network devices (e.g., servers) as well as in a variety of mediums. For instance, instructions and data for implementing the above-described invention may be stored on a disk drive, a hard drive, a floppy disk, a server computer, or a remotely networked computer.
Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
FIG. 3 is a diagram illustrating an extended ISL (EISL) frame format including an EISL header in accordance with one embodiment of the invention.
FIG. 4 is a diagram illustrating an exemplary EISL header (and associated MPLS label stacle) that may be transmitted in a frame having an EISL frame format such as that illustrated in FIG. 3.
FIG. 5 is a diagram illustrating an exemplary MPLS label format that may be used for each label in the MPLS label stack of FIG. 4 in accordance with one embodiment of the invention.
FIG. 6 is a diagram illustrating an exemplary network device in which embodiments of the invention may be implemented.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
In the following description, numerous specific details axe set forth in order to provide a thorough understanding of the present invention. It will be obvious, however, to one spilled in the art, that the present invention may be practiced without some or all of these specific details. In other instances, well known process steps have not been described in detail in order not to unnecessarily obscure the present invention.
As described above, a storage area network (SAN) is a network that interconnects different data storage devices with associated networlc hosts (e.g., data servers or end user machines) on behalf of a larger network of users. A
SAN
is defined by the physical configuration of the system. In other words, those devices in a SAN must be physically interconnected.
In accordance with various embodiments of the present invention, the physical SAN is shared by multiple virtual storage area networks (VSANs), each using some or all of the physical infrastructure of the SAN. An encapsulation mechanism is employed to implement the VSANs. Through the concept of a VSAN, one or more network devices (e.g., servers) and one or more data storage devices are grouped into a logical network defined within a common physical network infrastructure. Communication among these devices may be accomplished by coupling the network devices and data storage devices together through one or more switches. Exemplary data storage devices that may be used in a VSAN include, but are not limited to, storage disks in various configurations such as a redundant array interconnected disk (RAID).
Each VSAN is uniquely identified by a VSAN identifier rather than any particular physical configuration of devices within the network. For instance, a unique identifier may be simultaneously associated with one or more network devices as well as one or more storage devices. W general, the VSAN identifier does not represent any particular physical network device or link.
Within a ULAN infrastructure, individual VLANs are distinguished through the use of a VLAN identifier (e.g., within the range of zero through 4094).
W accordance with various embodiments of the invention, individual VSANs will be distinguished within a VSAN infrastructure through the use of a VSAN
identifier, as described above. It would be desirable to support mixed _g_ infrastructures containing both VLANs and VSANs, for example, using a trunk link or router able to carry traffic among VLANs and VSANs.
In accordance with one embodiment, VLAN identifiers and VSAN
identifiers share the same number space. In other words, any given number can be a VSAN identifier or a VLAN identifier, but cannot be used to independently identify a VSAN and a VLAN at the same time. For example, it would not be possible to have both a VSAN #1 and VLAN #1 at the same time.
In accordance with another embodiment, VLAN identifiers and VSAN
identifiers have independent number spaces. In other words, a given number can be either a VSAN identifier or a VLAN identifier, as well as an identifier for both a VSAN and a VLAN simultaneously. Since a number may correspond to either a VSAN or a VLAN, the type of network (e.g., VSAN or VLAN) is also identified.
Thus, VSAN #1 and VLAN #1 can both exist at the same time as different and independent virtual networks. This type may be a separate field in the EISL
header or may be incorporated into the frame type (e.g., traffic type), which will be described in further detail below with reference to FIG. 4.
FIG. 1 is a diagram illustrating an exemplary storage area network 101 in which the present invention may be implemented. As shown in FIG. 1, data storage devices 102, 104, 106, 108, 110, and 112 axe coupled to hosts (e.g., servers) 114, 116, and 128 via several switches 118, 120, and 122. The switches commuW cate with one another via interswitch links 124 and 126. The elements described in this paragraph together comprise the physical infrastructure of SAN
101. The storage devices, switches, and hosts of SAN 101 communicate using one or more standard protocols such as fibre channel (FC), fibre channel IP
(FCIP), SCSI, SCSI over IP, Ethernet, Infiniband, and the like. Sometimes, these protocols are referred to herein as "types" of traffic.
One or more VSANs may be created through logically grouping various network devices with selected data storage devices. For instance, as shown in FIG.
1, a first VSAN, VSANl, consists of server 114, 128 and data storage devices 102, 106, 110, and 114, while a second VSAN, VSAN2, consists of server 116, 128 and data storage devices 104, 108, and 112. Note that both VSANl and VSAN2 share the interswitch links 124 and 126 to communicate. For example, both host 114 of VSANl and host 116 of VSAN2 use link 126 to access storage device 110 and storage device 112, respectively.
To ensure that network traffic crossing interswitch links 124 and 126 is properly routed to (and limited to) devices within the associated VSANs, the traffic must be identifiable as either VSAN1 traffic or VSAN2 traffic. Tlus can be accomplished in various ways. One convenient methodology employed with this invention encapsulates data frames with some sort of VSAN identifier. That way switches 118, 120, and 122 can examine frames crossing linlcs 124 and 126 to determine which VSAN is involved and make appropriate switching decisions based upon this information.
Various embodiments of the invention may be applied to encapsulate a packet or frame as described below with reference to FIGs. 2 through 5. The distinction between packet and frame is not universally accepted. However, one distinction that is commonly used is defined as follows. A packet is the unit of data that is routed between an origin and a destination on the Internet or any other packet-switched networlc. Each packet is separately numbered and includes the Internet address of the destination. In contrast, a frame is data that is transmitted between. adjacent network devices. The information or data in the frame may contain packets or other data units used in a higher-level or different protocol.
For convenience, the subsequent discussion will describe encapsulated f~a~nes used to transmit data over SAN. Switches act on frames and use information about VSANs to make switching decisions. Thus, in accordance with various embodiments of the invention, frames that originate within a VSAN are constrained to stay within the physical resources allotted to that VSAN. Thus, a gateway working at a lugher protocol layer (e.g., application layer 7) may pass such a packet from one VSAN to another. In order to enforce this restriction, frames may be encapsulated with a structure that identifies a VSAN to which the frames belong. Once encapsulated, the encapsulated frame is moved across network nodes; in particular over inter-switch links in the storage area network.
Thus, through tlus encapsulation, a single link may transport frames associated with multiple VSANs. An exemplary encapsulated paclcet will be described in further detail below with reference to FIG. 3 and FIG. 4.
Note that the frames being encapsulated possess the frame format specified for a standard protocol such as Ethernet or fibre channel. Hence, software and hardware conventionally used to generate such frames may be employed with this invention. Additional hardware and/or software is employed to encapsulate the standard frames in accordance with this invention. Those of skill in the art will understand how to develop the necessary hardware and software to allow encapsulation of the type described below.
In accordance with the present invention, a frame compatible with a standard protocol employed in a storage area network is obtained at a node where encapsulation subsequently takes place. The frame is generated by a network device such as a host, switch, or storage device. In a typical scenario, the host machine generates the frame in accordance with a standard protocol such as fibre channel and forwards the frame to a switch. The switch then performs an encapsulation process such as that described below. In some embodiments, the host or storage device may itself perform the encapsulation described herein.
In still other embodiments, the switch may receive a data stream and first frame it in accordance with a standard protocol and then encapsulate the resulting frame to produce the new frames of this invention. The resulting encapsulated frame is sometimes referred to herein an "extended ISL" (EISL) frame because of its general relationship with the interswitch link protocol described in US
Patent No. 5,742,604, previously incorporated by reference.
As just explained, the encapsulation process may be performed by a network device outside the switch (e.g., by a host) as well as within a switch.
Obviously, the appropriate network devices should be configured with the appropriate software and/or hardware for performing EISL encapsulation. Of ' course, all network devices within the storage area network need not be configured with EISL encapsulation software (or hardware). Rather, selected network devices may be configured with or adapted for EISL encapsulation functionality.
Similarly, in various embodiments, such EISL encapsulation functionality may be enabled or disabled through the selection of various modes. Moreover, it may be desirable to configure selected ports of networlc devices as EISL-capable ports capable of performing EISL encapsulation, either continuously, or only when in an EISL
enabled state.
The standard protocol (e.g., layer 2 protocol) employed in the storage area network (i.e., the protocol used to frame the data) will typically, although not necessarily, be synonymous with the "type of traffic" carried by the network.
As explained below, the type of traffic is defined in some encapsulation formats.
Examples of the type of traffic are typically layer 2 or corresponding layer formats such as Ethernet and Fibre Channel.
Another type of traffic that may be used within a VSAN is an InfiniBand architecture, which is a relatively recent input/output (I/O) specification for servers.
More particularly, connections between servers, remote storage and networking are accomplished by attaching all devices through a central, unified, fabric of InfiniBand switches and links. Stated benefits of the InfiniBand architecture include lower latency, easier and faster sharing of data, and built in security and quality of service. The InfiniBand architecture is a rapidly developing technology for server clusters as well as I/O for remote storage and networking. Thus, the InfiniBand Architecture is well suited to address the demands generated by the rapid growth of the Internet and the convergence of data and telecommunications (voice, data, video, and storage) on the W ternet. With InfiniBand, data is transmitted in one or more packets that together form a message. For instance, a message can be a remote direct memory access (RDMA) read or write operation, a channel send or receive message, a transaction-based operation (that can be reversed), or a multicast transmission.
In addition, other types of traffic may include token ring, token bus, and various protocols compatible with satellite systems such as Aloha. It is also important to note that the type of traffic should also be supported by the technology used in the storage area network. For instance, the technology used in the hosts and/or switches (e.g., interface port circuitry) as well as the communication mediums should support the traffic type being carried in the encapsulated frame.
As shown in FIG. 2, a frame compatible with a standard protocol employed in a storage area network is obtained. For instance, a frame such as a fibre channel frame 202 typically includes a header 204, payload 206 and error checlc information such as a cyclic redundancy checking (CRC) value 208. Cyclic redundancy checl~ing is a method of checking a received frame for errors in data that has been transmitted on a communications link. As described above, it is necessary to identify the VSAN associated with the frame 202. However, pursuant to the standard governing fibre channel, the header 204 of a fibre channel frame 202 does not include unused bits to enable additional fields to be defined. As a result, an "extension" 210 to the frame 202 is required. Extension 210 may assume various formats. Importantly, it should include at least information identifying the VSAN and other information specifying one or more of the following: type of traffic, MPLS information, and time to live.
In accordance with various embodiments, as shown in FIG. 3, a new frame 302 having an extended ISL (EISL) format is generated from information obtained from the original frame 202. More particularly, encapsulation may include the appending of a new header (or trailer) to the original frame 202. For instance, as shown, the new frame 302 includes a payload 303 that preferably includes both the header 204 and payload 206 of the original frame, and a new EISL header 304.
In addition, the payload 303 may also include the CRC 208 of the original frame.
Encapsulation may also comprise the modification or replacement of the original CRC value 208 with a new (e.g., additional) or modified CRC value 306. More particularly, since the new frame is longer than the original frame 202, a new CRC
value 306 may be generated (e.g., calculated) to correspond the longer length of the frame 302 that includes the newly appended EISL header 304 and its associated length. This new CRC 306 may therefore replace the original CRC 208. In this manner, a new frame is generated by encapsulating the frame with an EISL
header.
In accordance with various embodiments, an EISL frame 302 such as that illustrated in FIG. 3 is preceded by a start of frame (SOF) delimiter 308 and terminated by an end of frame (EOF) delimiter 310. These delimiters enable an EISL-capable port to receive and recognize frames in EISL format. However, if an EISL-capable port is not in EISL mode or, alternatively, the port is not EISL-capable and it receives frames in the EISL format, it can drop the frame.
FIG. 4 is a diagram illustrating an exemplary EISL header of a frame that has an overall EISL frame format such as that illustrated in FIG. 3. More particularly, as described above, the EISL header preferably identifies a VSAN. In addition, encapsulation may include providing further information in the encapsulated frame. As will be described in further detail below, the EISL
header may supply fiuther information in various fields of the EISL header. More particularly, an EISL indicator field 402 may be used to indicate the presence of an EISL header. In addition, an EISL version indicator field 404 may indicate a version of EISL used to create the frame. In a specific example, the EISL
version indicator field 404 of the EISL header includes at least 2 bits.
The EISL header further includes a field indicating a frame type 406 (i.e., traffic type). The type of traffic (e.g., payload) to be carried by the frame may include a variety of traffic types such as those described above, including but not limited to, Ethernet, fibre chaimel, and Infiniband. In one embodiment, the frame type field 406 is a 4-bit field. Through the identification of a traffic type, EISL
formatted frames carrying a variety of traffic types may be transmitted within a VSAN. Moreover, multiple VSANs, each capable of supporting different traffic types, may be interconnected through the identification of a traffic type in the newly appended EISL header.
Multi-Protocol Label Switching (MPLS) label field (e.g., Indicator) 408 indicates whether the EISL header is carrying MPLS information such as an MPLS
label stack, a common forwarding mechanism for both fibre channel and Ethernet frames. An exemplary MPLS label stack will be described in further detail below with reference to FIG. 5. In one embodiment, the MPLS label field 408 is a 1-bit field. More particularly, the MPLS label field 408 indicates whether or not MPLS
labels are provided in the EISL frame. For instance, the indicator may be set to 1 if the EISL header includes an MPLS label stack and otherwise be set to 0. The MPLS label field 408 may also indicate the number of labels present in 416.
Priority field 410 may indicate a user priority for the EISL frame. The user priority may represent various types of priorities. As one example, the user priority may be a generic priority, without a guaranteed level of service, that is used to merely indicate a priority such as a numerical ranl~ing. For instance, higher values simply represent higher user priority while lower values may represent lower priority. Higher priority users receive available bandwidth first, regardless of how much total bandwidth is available. The number of bits used for this field will vary with the number of priority levels or values implemented.
As another example, the user priority may indicate a quality of service (QoS) of the payload of the EISL frame. On the Internet and in other networks, QoS is the idea that transmission rates, error rates, and other characteristics can be measured, improved, and, to some extent, guaranteed in advance. QoS is of particular concern for the continuous transmission of high-bandwidth video and multimedia information. Transmitting this bind of content dependably is difficult in public networks using ordinary "best effort" protocols. Typically, the number of bits required for a priority field are greater to specify the quality of service than a simple numerical priority. In one embodiment, the priority field 410 is a 3-bit field.
As described above, the EISL header, at a minimum, includes a VSAN
identifier field 412 adapted for including a VSAN identifier that identifies one or more VSANs. More particularly, in accordance with one embodiment, the VSAN
identifier identifies a VSAN associated with the payload of the EISL frame, and therefore the payload of the original frame (e.g., Fibre Channel frame). In accordance with one embodiment, the VSAN identifier field 412 is a 12-bit field.
The format of the identifier may be identical to or similar to VLAN
identifiers as well as similar to addresses employed in certain standard protocols such as Ethernet.
In some storage area networks, there may be topology as well as routing problems that could cause a frame to traverse a loop within the network. Such a loop will consume bandwidth unnecessarily. liz order to solve this problem, a Time To Live (TTL) field 414 may be used to indicate a TTL value specifying the number of remaining hops that can be traversed before the frame is dropped.
More specifically, the TTL value of the TTL field 414 is initialized by the network device (e.g., switch) that generates the EISL frame including the EISL header.
A
default value may, for example, be set to 16. Subsequent network devices (e.g., switches) receiving the EISL frame decrement the TTL value of the TTL field by 1.
In accordance with one embodiment, a TTL value of 1 indicates to the receiving network device (e.g., switch) that the EISL frame should be dropped.
When the EISL frame is dropped, an error message may be sent to the intended recipient of the frame as well as to the sender of the frame. Similarly, a TTL
value of 0 may indicate that the TTL field 414 should be ignored, allowing the EISL
frame to be forwarded by the switch. In accordance with one embodiment, the TTL field 414 is an 8-bit field.
As described above, an MPLS indicator 408 may be used to indicate whether the EISL header is carrying MPLS information such as an MPLS label stack 416. As a paclcet of a connectionless network layer protocol travels from one router to the next, each router malces an independent forwarding decision for that packet. That is, each router analyzes the packet's header, and each muter runs a network layer routing algorithm. Each router independently chooses a next hop for the packet, based on its analysis of the packet's header and the results of running the routing algorithm.
Paclcet headers contain considerably more information than is needed simply to choose the next hop. Choosing the next hop can therefore be thought of as the composition of two functions. The first function partitions the entire set of possible packets into a set of "Forwarding Equivalence Classes (FECs)." The second function maps each FEC to a next hop. Insofar as the forwarding decision is concerned, different packets which get mapped into the same FEC are indistinguishable. All packets which belong to a particular FEC and which travel from a particular node will follow the same path (or if certain kinds of mufti-path routing are in use, they will all follow one of a set of paths associated with the FEC).
In conventional IP forwarding, a particular router will typically consider two packets to be in the same FEC if there is some address prefix X in that router's routing tables such that X is the "longest match" for each packet's destination address. As the packet traverses the network, each hop in turn reexamines the packet and assigns it to a FEC. In MPLS, the assignment of a particular packet to a particular FEC is done just once, as the packet enters the network. The FEC to which the packet is assigned is encoded as a short fixed length value known as a "label."
When a paclcet is forwarded to its next hop, the label is sent along with it;
that is, the packets are "labeled" before they are forwarded. At subsequent hops, there is no further analysis of the packet's network layer header. Rather, the label is used as an index into a table which specifies the next hop and a new label.
The old label is replaced with the new label, and the packet is forwarded to its next hop. In the MPLS forwarding paradigm, once a paclcet is assigned to a FEC, no fuuther header analysis is done by subsequent routers; all forwarding is driven by the labels. This has a number of advantages over conventional networlc layer forwarding. For instance, through MPLS labels, it is possible to circumvent conventional 1P routing. Further details of the MPLS forwarding mechanism and MPLS label stack encoding are disclosed in RFC 3031, Multiprotocol Label Switching Architecture, Rosen et al., January 2001 and RFC 3032, MPLS Label Stack Encoding, Rosen et al., January 2001, respectively, and are incorporated by reference for all purposes.
As described above with reference to block 408 of FIG. 4, an indicator may be used to indicate whether the EISL frame includes a label stack. W
accordance with one embodiment, a label stack may include a maximum of 4 labels. Each label in the label stack has an identical label format.
FIG. 5 is a diagram illustrating an exemplary MPLS label format that may be used for each label in the MPLS label stack of FIG. 4 in accordance with one embodiment of the invention. Label field 502 carries the actual value of the corresponding label used to make forwarding decisions. When a labeled packet is received, the label value at the top of the stack is looked up. As a result of a successful lookup in a corresponding table, file or database, the following information is ascertained: a) the next hop to which the paclcet is to be forwarded, and b) the operation to be performed on the label stack before forwarding;
this operation may be to replace the top label stack entry with another, to pop an entry off the label staclc, or to replace the top label stack entry and then to push one or more additional entries on the' label stack. In addition to learning the next hop and the label stack operation, one may also learn the outgoing data link encapsulation, and possibly other information which is needed in order to properly forward the packet. In accordance with one embodiment, the label field 502 is a 32-bit field.
Experimental field 504 may be reserved for experimental use. The experimental field 504 is typically used to encode the Differentiated Service Code Point (DSCP), which is a mechanism for Quality of Service.
In addition, a termination field 506 may be provided in the label to indicate if this label is the last label in the staclc. In accordance with one embodiment, the termination field is a single bit indicator. For instance, the termination field 506 may indicate that the label is the last label in the label stack when the indicator is in a first state (e.g., 1) and that the label is not the last label in the label staclc when the indicator is in a second state (e.g., 0).
The label may also include a TTL field 508. The TTL field 508 is typically used to provide TTL field semantics associated with IPv4 paclcets or Hop Count semantics associated with IPv6 packets.
As described above, encapsulation may be performed in a variety of network devices. FIG. 6 is a diagram illustrating an exemplary network device in which embodiments of the invention may be implemented. The network device illustrated is a hybrid switch that can switch both Ethernet and fibre channel frames. It is preferred that frames of various types (e.g., Ethernet and fibre channel) be transported via a single switching mechanism. Through the use of an extended ISL (EISL) frame format, frames of different types may be transported using the same switch or ISL, rather than dedicating a switch or ISL to different frame (or traffic) types.
As shown in FIG. 6, data is received by a port 602 of the switch via a bi-directional connector (not shown). In association with the incoming port, Media Access Control (MAC) block 604 is provided, which enables frames of various protocols such as Ethernet or fibre channel to be received. Once a frame is encapsulated as described above, it is then received by a forwarding engine 608, wluch obtains information from various fields of the frame, such as source address and destination address. The forwarding engine 608 then accesses a forwarding table (not shown) to determine whether the source address has access to the specified destination address. The forwarding engine 608 also determines the appropriate port of the switch via which to send the frame, and generates an appropriate routing tag for the frame.
Once the frame is appropriately formatted for transmission, the frame will be received by a buffer queuing block 606 prior to transmission. Rather than transmitting frames as they are received, it may be desirable to temporarily store the frame in a buffer or queue 606. For instance, it may be desirable to temporarily store a paclcet based upon Quality of Service in one of a set of queues that each correspond to different priority levels. The frame is then transmitted via switch fabric 610 to the appropriate port. Each outgoing port also has its own MAC
bloclc and bi-directional connector via which the frame may be transmitted.
Although the networlc device described above with reference to FIG. 6 is described as a switch, this network device is merely illustrative. Thus, other network devices such as routers may be implemented to receive, process, modify and/or generate packets or frames with functionality such as that described above for transmission in a storage area network. Moreover, the above-described network devices are merely illustrative, and therefore other types of networlc devices may be implemented to perform the disclosed encapsulation functionality.
Once the EISL frame is generated, the encapsulated frame may be sent by the switch over an inter-switch (ISL) link configured to couple source and destination port interface circuitry in a sequential arrangement of interconnected switches as illustrated in FIG. 1. The ISL link may consist of any type of media (e.g., twisted-pair or fiber) capable of functioning as an extension to a switching bus or other coxmnunication medium. Moreover, port interface circuitry may comprise encapsulation as well as decapsulation circuits. Since the interface to the ISL essentially comprises the port interface circuitry, any number of ports of a network device such as the switch illustrated in FIG. 6 are capable of being configured as EISL ports. That is, the ISL port interface circuit may include a circuit and/or otherwise be configured with software that includes functionality for encapsulating paclcets according to the disclosed EISL encapuslation mechanism, as well as decapsulating packets.
Although illustrative embodiments and applications of this invention are shovcnl and described herein, many variations and modifications are possible which remain within the concept, scope, and spirit of the invention, acid these variations would become clear to those of ordinary slcill in the art after perusal of tlus application. For instance, the present invention is described as being implemented using a specific EISL header. However, it should be understood that the invention is not limited to such implementations, but instead would equally apply regardless of the fields defined in such a header. Moreover, the present invention would apply regardless of the context and system in which it is implemented. Thus, broadly speaking, the operations described above need not be used within a SAN, but may be used to enable protocol compatibility within any network.
W addition, although an exemplary switch is described, the above-described embodiments may be implemented in a variety of network devices (e.g., servers) as well as in a variety of mediums. For instance, instructions and data for implementing the above-described invention may be stored on a disk drive, a hard drive, a floppy disk, a server computer, or a remotely networked computer.
Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
Claims (53)
1. A method implemented on a network device for use in a storage area network, the method comprising:
receiving or generating a packet or frame compatible with a standard protocol employed in the storage area network, the packet or frame including a first header;
encapsulating the packet or frame with a virtual storage area network identifier and information specifying a type of traffic to be carried by the packet or frame, wherein the type of traffic to be carried by the packet or frame is one of two or more available types of traffic, wherein the two or more available types of traffic include at least one of Ethernet, fibre channel, or Infiniband, wherein encapsulating comprises adding a second header to the packet or frame to create a new packet or frame, wherein the second header includes fields for the virtual storage area network identifier and the information specifying the type of traffic to be carried by the packet or frame; and sending the encapsulated packet or frame.
receiving or generating a packet or frame compatible with a standard protocol employed in the storage area network, the packet or frame including a first header;
encapsulating the packet or frame with a virtual storage area network identifier and information specifying a type of traffic to be carried by the packet or frame, wherein the type of traffic to be carried by the packet or frame is one of two or more available types of traffic, wherein the two or more available types of traffic include at least one of Ethernet, fibre channel, or Infiniband, wherein encapsulating comprises adding a second header to the packet or frame to create a new packet or frame, wherein the second header includes fields for the virtual storage area network identifier and the information specifying the type of traffic to be carried by the packet or frame; and sending the encapsulated packet or frame.
2. The method of claim 1, wherein the network device is a switch and wherein sending the encapsulated packet or frame comprises sending the encapsulated packet or frame over an inter-switch link in the storage area network.
3. The method of claim 1, wherein the second header further includes a first field for the TTL value and a second field for the MPLS information.
4. The method of claim 1, wherein the type of traffic to be carried by the packet or frame specifies the standard protocol of the packet or frame.
5. The method as recited in claim 1, wherein the second header further includes information specifying at least one of a TTL value or MPLS information.
6. The method of claim 1, wherein the network device is a switch and wherein sending the encapsulated packet or frame comprises sending the encapsulated packet or frame over an inter-switch link in the storage area network.
7. The method as recited in claim 1, wherein the TTL value specifies a number of remaining hops that can be traversed before the encapsulated packet or frame is dropped.
8. The method as recited in claim 1, wherein the TTL value specifies a remaining lifetime.
9. The method of claim 1, further comprising calculating an error check value for the new packet or frame and including the error check value in the new packet or frame.
10. The method of claim 1, wherein the second header includes a first field for the TTL
value and a second field for the MPLS information.
value and a second field for the MPLS information.
11. The method of claim 1, wherein the type of traffic to be carried by the packet or frame specifies the standard protocol of the packet or frame.
12. The method of claim 1, wherein the second header includes four bits for the field specifying a type of traffic to be carried by the packet or frame.
13. The method of claim 1, wherein the second header further comprises a field specifying a user priority for the packet or frame.
14. The method of claim 1, wherein the standard protocol is Fibre Channel.
15. The method of claim 1, wherein the standard protocol is Ethernet.
16. The method of claim 1, wherein the standard protocol is Infiniband.
17. The method of claim 1, wherein the header field for the virtual storage area network identifier has 12 bits reserved.
18. The method of claim 1, wherein the second header includes a TTL field and the field has 8 bits reserved.
19. The method of claim 1, wherein the second header includes an indicator field to indicate whether one or more MPLS labels are present.
20. The method of claim 1, wherein the second header includes an indicator field to indicate a number of MPLS labels present in the new packet or frame.
21. The method of claim 1, wherein the new packet or frame includes one or more MPLS
labels, each of the labels including an indicator to indicate whether the label is the last label in a label stack.
labels, each of the labels including an indicator to indicate whether the label is the last label in a label stack.
22. The method of claim 19, wherein the indicator field is one bit.
23. The method of claim 1, wherein the second header further includes a version field indicating a version of the second header.
24. A computer readable medium for storing thereon computer-readable instructions for performing a method on a network device in a storage area network, said instructions, when executed by a computer processor, cause the computer processor to carry out the method to receive or generate a packet or frame compatible with a standard protocol employed in the storage area network, the packet or frame encapsulate the packet or frame with a virtual storage area network identifier and information specifying a type of traffic to be carried by the packet or frame to create a new packet or frame that includes a second header, wherein the type of traffic to be carried by the packet or frame is one of two or more available types of traffic, wherein the two or more available types of traffic include at least one of Ethernet, fibre channel, or Infiniband, wherein the second header includes fields for the virtual storage area network identifier and the type of traffic to be carried by the packet or frame; and send the encapsulated packet or frame.
25. The computer-readable medium as recited in claim 24, wherein the second header further includes information specifying at least one of a TTL value or MPLS
information.
information.
26. The computer-readable medium of claim 24, wherein the network device is a switch and wherein said instructions, when executed by a computer processor, cause the computer processor to send the encapsulated packet or frame over an inter-switch link in the storage area network.
27. The computer-readable medium as recited in claim 25, wherein the TTL value specifies a number of remaining hops that can be traversed before the encapsulated packet or frame is dropped.
28. The method as recited in claim 25, wherein the TTL value specifies a remaining lifetime.
29. The computer-readable medium of claim 24, said instructions, when executed by a computer processor, cause the computer processor calculate an error check value for the new packet or frame and including the error check value in the new packet or frame.
30. The computer-readable medium of claim 25, wherein the second header includes a first field for the TTL value and a second field for the MPLS information.
31. The computer-readable medium of claim 24, wherein the type of traffic to be carried by the packet or frame specifies the standard protocol of the packet or frame.
32. The computer-readable medium of claim 24, wherein the second header includes four bits for the field specifying a type of traffic to be carried by the packet or frame.
33. The computer-readable medium of claim 24, wherein the second header further comprises a field specifying a user priority for the packet or frame.
34. The computer-readable medium of claim 24, wherein the standard protocol is Fibre Channel.
35. The computer-readable medium of claim 24, wherein the standard protocol is Ethernet.
36. The computer-readable medium of claim 24, wherein the standard protocol is Infiniband.
37. The computer-readable medium of claim 25, wherein the header field for the virtual storage area network identifier has 12 bits reserved.
38. The computer-readable medium of claim 25, wherein the second header includes a TTL field and the field has 8 bits reserved.
39. The computer-readable medium of claim 25, wherein the second header includes an indicator field to indicate whether one or more MPLS labels are present.
40. The computer-readable medium of claim 25, wherein the new packet or frame includes one or more MPLS labels, each of the labels including an indicator to indicate whether the label is the last label in a label stack.
41. The computer-readable medium of claim 25, wherein the second header includes an indicator field to indicate a number of MPLS labels present in the new packet or frame.
42. The computer-readable medium of claim 39, wherein the indicator field is one bit.
43. The computer-readable medium of claim 24, wherein the second header further includes an indicator field to indicate whether the second header is present.
44. The computer-readable medium of claim 25, wherein the second header further includes a version field indicating a version of the second header.
45. A network device for use in a storage area network, the network device comprising:
a plurality of ports each configured to transmit and/or receive packets or frames compatible with one or more standard protocols employed in the storage area network; and a processor and associated instructions that can encapsulate packets or frames of at least one of the standard protocols to include a virtual storage area network identifier, and a type of traffic to be carried by the packet or frame and deliver the resulting encapsulated packets or frames for transmission over the storage area network, the packet or frame including a first header, wherein the processor and associated instructions are configured to append a second header to the packet or frame to create a new packet or frame, wherein the second header includes a field for the virtual storage area network identifier and a field specifying the type of traffic to be carried by the packet or frame, wherein the type of traffic to be carried by the packet or frame is one of two or more available types of traffic, wherein the two or more available types of traffic include at least one of Ethernet, fibre channel, or Infiniband.
a plurality of ports each configured to transmit and/or receive packets or frames compatible with one or more standard protocols employed in the storage area network; and a processor and associated instructions that can encapsulate packets or frames of at least one of the standard protocols to include a virtual storage area network identifier, and a type of traffic to be carried by the packet or frame and deliver the resulting encapsulated packets or frames for transmission over the storage area network, the packet or frame including a first header, wherein the processor and associated instructions are configured to append a second header to the packet or frame to create a new packet or frame, wherein the second header includes a field for the virtual storage area network identifier and a field specifying the type of traffic to be carried by the packet or frame, wherein the type of traffic to be carried by the packet or frame is one of two or more available types of traffic, wherein the two or more available types of traffic include at least one of Ethernet, fibre channel, or Infiniband.
46. The network device as recited in claim 45, wherein the second header further includes a field for information specifying at least one of a TTL value or MPLS
information.
information.
47. The network device as recited in claim 45, wherein the network device is a switch, and where at least one of the ports supports an inter-switch link with another switch on a storage area.
48. The network device of claim 47, wherein the port supporting an inter-switch link provides fibre channel packets or frames.
49. The network device of claim 47, wherein the port supporting an inter-switch link provides Ethernet packets or frames.
50. The network device of claim 47, wherein the port supporting an inter-switch link provides Infiniband packets or frames.
51. The network device of claim 45, further comprising a plurality of line cards, each providing at least one of the plurality of ports.
52. The network device of claim 46, wherein the network device is configured to calculate an error check value for the new packet or frame and include the error check value in the new packet or frame.
53. The network device of claim 46, wherein the second header includes a first field for the TTL value and a second field for the MPLS information.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/034,160 US7599360B2 (en) | 2001-12-26 | 2001-12-26 | Methods and apparatus for encapsulating a frame for transmission in a storage area network |
US10/034,160 | 2001-12-26 | ||
PCT/US2002/041072 WO2003058891A1 (en) | 2001-12-26 | 2002-12-23 | Methods and apparatus for encapsulating a frame for transmission in a storage area network |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2472056A1 CA2472056A1 (en) | 2003-07-17 |
CA2472056C true CA2472056C (en) | 2010-09-21 |
Family
ID=21874674
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2472056A Expired - Fee Related CA2472056C (en) | 2001-12-26 | 2002-12-23 | Methods and apparatus for encapsulating a frame for transmission in a storage area network |
Country Status (10)
Country | Link |
---|---|
US (2) | US7599360B2 (en) |
EP (1) | EP1459485B1 (en) |
JP (1) | JP4335009B2 (en) |
KR (1) | KR100927265B1 (en) |
CN (1) | CN100348000C (en) |
AT (1) | ATE363171T1 (en) |
AU (1) | AU2002364204B2 (en) |
CA (1) | CA2472056C (en) |
DE (1) | DE60220313T2 (en) |
WO (1) | WO2003058891A1 (en) |
Families Citing this family (225)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8219681B1 (en) | 2004-03-26 | 2012-07-10 | Emc Corporation | System and method for managing provisioning of storage resources in a network with virtualization of resources in such a network |
US8032701B1 (en) * | 2004-03-26 | 2011-10-04 | Emc Corporation | System and method for managing provisioning of storage resources in a network with virtualization of resources in such a network |
US7061939B1 (en) * | 2001-06-13 | 2006-06-13 | Juniper Networs, Inc. | Source synchronous link with clock recovery and bit skew alignment |
US7734808B1 (en) | 2001-12-18 | 2010-06-08 | Cisco Technology, Inc. | End-to-end congestion control in a Fibre Channel network |
US7599360B2 (en) * | 2001-12-26 | 2009-10-06 | Cisco Technology, Inc. | Methods and apparatus for encapsulating a frame for transmission in a storage area network |
US7499410B2 (en) * | 2001-12-26 | 2009-03-03 | Cisco Technology, Inc. | Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain—IDs |
US7616637B1 (en) * | 2002-04-01 | 2009-11-10 | Cisco Technology, Inc. | Label switching in fibre channel networks |
US7406034B1 (en) | 2002-04-01 | 2008-07-29 | Cisco Technology, Inc. | Methods and apparatus for fibre channel frame delivery |
US7227867B1 (en) * | 2002-04-16 | 2007-06-05 | Juniper Networks, Inc. | Multi-protocol label switching in a network device |
US7656884B1 (en) * | 2002-05-24 | 2010-02-02 | Cisco Technology, Inc. | Apparatus and method for a generic service locking mechanism for a fibre channel switching fabric of a storage area network |
US7013318B2 (en) * | 2002-05-29 | 2006-03-14 | Raytheon Company | Method and system for encapsulating cells |
US7206288B2 (en) * | 2002-06-12 | 2007-04-17 | Cisco Technology, Inc. | Methods and apparatus for characterizing a route in fibre channel fabric |
EP1522174B1 (en) * | 2002-07-16 | 2009-09-09 | Enterasys Networks, Inc. | Apparatus and method for a virtual hierarchial local area network |
US7397768B1 (en) | 2002-09-11 | 2008-07-08 | Qlogic, Corporation | Zone management in a multi-module fibre channel switch |
US8005918B2 (en) | 2002-11-12 | 2011-08-23 | Rateze Remote Mgmt. L.L.C. | Data storage devices having IP capable partitions |
EP1561306B1 (en) * | 2002-11-12 | 2007-03-07 | Zetera Corporation | Communication protocols, systems and methods |
US7742473B2 (en) * | 2002-11-12 | 2010-06-22 | Mark Adams | Accelerator module |
US7170890B2 (en) * | 2002-12-16 | 2007-01-30 | Zetera Corporation | Electrical devices with improved communication |
US7649880B2 (en) | 2002-11-12 | 2010-01-19 | Mark Adams | Systems and methods for deriving storage area commands |
US7346058B1 (en) * | 2002-11-27 | 2008-03-18 | Cisco Technology, Inc. | Multiprotocol encapsulation system and method |
US7433326B2 (en) * | 2002-11-27 | 2008-10-07 | Cisco Technology, Inc. | Methods and devices for exchanging peer parameters between network devices |
US7782784B2 (en) * | 2003-01-10 | 2010-08-24 | Cisco Technology, Inc. | Port analyzer adapter |
US7899048B1 (en) | 2003-01-15 | 2011-03-01 | Cisco Technology, Inc. | Method and apparatus for remotely monitoring network traffic through a generic network |
US20040160975A1 (en) * | 2003-01-21 | 2004-08-19 | Charles Frank | Multicast communication protocols, systems and methods |
US8081642B2 (en) | 2003-01-31 | 2011-12-20 | Brocade Communications Systems, Inc. | Method and apparatus for routing between fibre channel fabrics |
US7424533B1 (en) | 2003-05-23 | 2008-09-09 | Cisco Technology, Inc. | Method and apparatus for role-based access control |
US7894348B2 (en) | 2003-07-21 | 2011-02-22 | Qlogic, Corporation | Method and system for congestion control in a fibre channel switch |
US7430175B2 (en) * | 2003-07-21 | 2008-09-30 | Qlogic, Corporation | Method and system for managing traffic in fibre channel systems |
US7406092B2 (en) * | 2003-07-21 | 2008-07-29 | Qlogic, Corporation | Programmable pseudo virtual lanes for fibre channel systems |
US7792115B2 (en) | 2003-07-21 | 2010-09-07 | Qlogic, Corporation | Method and system for routing and filtering network data packets in fibre channel systems |
US7646767B2 (en) | 2003-07-21 | 2010-01-12 | Qlogic, Corporation | Method and system for programmable data dependant network routing |
US7420982B2 (en) * | 2003-07-21 | 2008-09-02 | Qlogic, Corporation | Method and system for keeping a fibre channel arbitrated loop open during frame gaps |
US7684401B2 (en) * | 2003-07-21 | 2010-03-23 | Qlogic, Corporation | Method and system for using extended fabric features with fibre channel switch elements |
US8165136B1 (en) * | 2003-09-03 | 2012-04-24 | Cisco Technology, Inc. | Virtual port based SPAN |
US7474666B2 (en) | 2003-09-03 | 2009-01-06 | Cisco Technology, Inc. | Switch port analyzers |
US20050078704A1 (en) * | 2003-10-14 | 2005-04-14 | International Business Machines Corporation | Method and apparatus for translating data packets from one network protocol to another |
US11108591B2 (en) | 2003-10-21 | 2021-08-31 | John W. Hayes | Transporting fibre channel over ethernet |
US7533175B1 (en) * | 2003-10-24 | 2009-05-12 | Network Appliance, Inc. | Network address resolution and forwarding TCP/IP packets over a fibre channel network |
US7447207B2 (en) * | 2003-10-27 | 2008-11-04 | Hewlett-Packard Development Company, L.P. | Method of and apparatus for transporting SCSI data over a network |
CN100466649C (en) * | 2003-12-03 | 2009-03-04 | 华为技术有限公司 | Method for transmitting multi-protocol tag exchange protocol data unit |
CN1311673C (en) * | 2003-12-03 | 2007-04-18 | 华为技术有限公司 | Method for transmitting multi-protocol tag exchange protocol data unit |
WO2005055547A1 (en) * | 2003-12-03 | 2005-06-16 | Huawei Technologies Co., Ltd. | A method for transmitting multi-protocol label switch protocol data unit |
US7634582B2 (en) * | 2003-12-19 | 2009-12-15 | Intel Corporation | Method and architecture for optical networking between server and storage area networks |
US8185600B2 (en) * | 2003-12-29 | 2012-05-22 | Broadcom Corporation | Programming system and method for a video network |
US7460537B2 (en) * | 2004-01-29 | 2008-12-02 | Brocade Communications Systems, Inc. | Supplementary header for multifabric and high port count switch support in a fibre channel network |
US7707309B2 (en) | 2004-01-29 | 2010-04-27 | Brocade Communication Systems, Inc. | Isolation switch for fibre channel fabrics in storage area networks |
US8782654B2 (en) | 2004-03-13 | 2014-07-15 | Adaptive Computing Enterprises, Inc. | Co-allocating a reservation spanning different compute resources types |
WO2005089239A2 (en) | 2004-03-13 | 2005-09-29 | Cluster Resources, Inc. | System and method of providing a self-optimizing reservation in space of compute resources |
US7325075B1 (en) | 2004-03-15 | 2008-01-29 | Hewlett-Packard Development Company, L.P. | Methods for address and name discovery for Ethernet entities |
US7818517B1 (en) | 2004-03-26 | 2010-10-19 | Emc Corporation | Architecture for virtualization of networked storage resources |
US8627005B1 (en) | 2004-03-26 | 2014-01-07 | Emc Corporation | System and method for virtualization of networked storage resources |
US7770059B1 (en) | 2004-03-26 | 2010-08-03 | Emc Corporation | Failure protection in an environment including virtualization of networked storage resources |
US7486689B1 (en) * | 2004-03-29 | 2009-02-03 | Sun Microsystems, Inc. | System and method for mapping InfiniBand communications to an external port, with combined buffering of virtual lanes and queue pairs |
US7340167B2 (en) * | 2004-04-23 | 2008-03-04 | Qlogic, Corporation | Fibre channel transparent switch for mixed switch fabrics |
US7930377B2 (en) | 2004-04-23 | 2011-04-19 | Qlogic, Corporation | Method and system for using boot servers in networks |
US20070266388A1 (en) | 2004-06-18 | 2007-11-15 | Cluster Resources, Inc. | System and method for providing advanced reservations in a compute environment |
US8018936B2 (en) * | 2004-07-19 | 2011-09-13 | Brocade Communications Systems, Inc. | Inter-fabric routing |
US7742484B2 (en) | 2004-07-30 | 2010-06-22 | Brocade Communications Systems, Inc. | Multifabric communication using a backbone fabric |
US8532119B2 (en) * | 2004-07-30 | 2013-09-10 | Brocade Communications Systems, Inc. | Interfabric routing header for use with a backbone fabric |
US7466712B2 (en) * | 2004-07-30 | 2008-12-16 | Brocade Communications Systems, Inc. | System and method for providing proxy and translation domains in a fibre channel router |
US7936769B2 (en) | 2004-07-30 | 2011-05-03 | Brocade Communications System, Inc. | Multifabric zone device import and export |
US8059664B2 (en) | 2004-07-30 | 2011-11-15 | Brocade Communications Systems, Inc. | Multifabric global header |
US8176490B1 (en) | 2004-08-20 | 2012-05-08 | Adaptive Computing Enterprises, Inc. | System and method of interfacing a workload manager and scheduler with an identity manager |
US8295299B2 (en) | 2004-10-01 | 2012-10-23 | Qlogic, Corporation | High speed fibre channel switch element |
US8238347B2 (en) * | 2004-10-22 | 2012-08-07 | Cisco Technology, Inc. | Fibre channel over ethernet |
US7593324B2 (en) * | 2004-10-25 | 2009-09-22 | Cisco Technology, Inc. | Graceful port shutdown protocol for fibre channel interfaces |
US7916628B2 (en) * | 2004-11-01 | 2011-03-29 | Cisco Technology, Inc. | Trunking for fabric ports in fibre channel switches and attached devices |
WO2006053093A2 (en) | 2004-11-08 | 2006-05-18 | Cluster Resources, Inc. | System and method of providing system jobs within a compute environment |
US7499970B2 (en) * | 2004-11-12 | 2009-03-03 | International Business Machines Corporation | Method and system for supervisor partitioning of client resources |
US7649844B2 (en) * | 2004-12-29 | 2010-01-19 | Cisco Technology, Inc. | In-order fibre channel packet delivery |
US8863143B2 (en) | 2006-03-16 | 2014-10-14 | Adaptive Computing Enterprises, Inc. | System and method for managing a hybrid compute environment |
US7702850B2 (en) | 2005-03-14 | 2010-04-20 | Thomas Earl Ludwig | Topology independent storage arrays and methods |
US9231886B2 (en) | 2005-03-16 | 2016-01-05 | Adaptive Computing Enterprises, Inc. | Simple integration of an on-demand compute environment |
JP5031195B2 (en) * | 2005-03-17 | 2012-09-19 | 株式会社日立製作所 | Storage management software and grouping method |
CA2603577A1 (en) | 2005-04-07 | 2006-10-12 | Cluster Resources, Inc. | On-demand access to compute resources |
US7483387B2 (en) | 2005-05-23 | 2009-01-27 | Cisco Technology, Inc. | Hierarchical label distribution for inter-area summarization of edge-device addresses |
US7620981B2 (en) * | 2005-05-26 | 2009-11-17 | Charles William Frank | Virtual devices and virtual bus tunnels, modules and methods |
AU2006272404B2 (en) * | 2005-07-17 | 2011-02-24 | Obsidian Research Corporation | A method to extend the physical reach of an infiniband network |
US9813283B2 (en) | 2005-08-09 | 2017-11-07 | Oracle International Corporation | Efficient data transfer between servers and remote peripherals |
US7743214B2 (en) * | 2005-08-16 | 2010-06-22 | Mark Adams | Generating storage system commands |
US8819092B2 (en) | 2005-08-16 | 2014-08-26 | Rateze Remote Mgmt. L.L.C. | Disaggregated resources and access methods |
US7577134B2 (en) * | 2005-08-19 | 2009-08-18 | Brocade Communications Systems, Inc. | Port expander for fibre channel fabrics in storage area networks |
US20070058620A1 (en) * | 2005-08-31 | 2007-03-15 | Mcdata Corporation | Management of a switch fabric through functionality conservation |
KR100715673B1 (en) * | 2005-09-07 | 2007-05-09 | 한국전자통신연구원 | A method for processing subscriber packet using subscriber identification tags |
US9270532B2 (en) | 2005-10-06 | 2016-02-23 | Rateze Remote Mgmt. L.L.C. | Resource command messages and methods |
WO2007047694A2 (en) * | 2005-10-17 | 2007-04-26 | Alebra Technologies, Inc. | Method, process and system for sharing data in a heterogeneous storage network |
US7760717B2 (en) * | 2005-10-25 | 2010-07-20 | Brocade Communications Systems, Inc. | Interface switch for use with fibre channel fabrics in storage area networks |
US7484021B2 (en) * | 2005-10-27 | 2009-01-27 | Cisco Technology, Inc. | Technique for implementing virtual fabric membership assignments for devices in a storage area network |
US7644179B1 (en) | 2005-12-01 | 2010-01-05 | Cisco Technology, Inc. | Inter-VSAN routing with NAT |
US7769023B2 (en) * | 2005-12-21 | 2010-08-03 | Cisco Technology, Inc. | Fibre channel traffic redirect scheme using access control lists |
CN1866868B (en) * | 2006-01-18 | 2010-10-06 | 华为技术有限公司 | Multi protocol label switched network flow managing system, method and device |
CN100353307C (en) * | 2006-02-16 | 2007-12-05 | 杭州华三通信技术有限公司 | Storage system and method of storaging data and method of reading data |
US7548560B1 (en) * | 2006-02-27 | 2009-06-16 | Qlogic, Corporation | Method and system for checking frame-length in fibre channel frames |
US7924881B2 (en) | 2006-04-10 | 2011-04-12 | Rateze Remote Mgmt. L.L.C. | Datagram identifier management |
US8040795B2 (en) * | 2006-05-10 | 2011-10-18 | Cisco Technology, Inc. | Backup path convergence in the APS environment |
US8886771B2 (en) * | 2006-05-15 | 2014-11-11 | Cisco Technology, Inc. | Method and system for providing distributed allowed domains in a data network |
EP1860033B1 (en) * | 2006-05-26 | 2011-01-12 | MTC - Macchine Trasformazione Carta Srl | Banding machine for logs of sheet material |
EP1868329A1 (en) * | 2006-06-12 | 2007-12-19 | Deutsche Thomson-Brandt Gmbh | Method of transferring data between a sending station in a first network and a receiving station in a second network, and apparatus for controlling the communication between the sending station in the first network and the receiving station in the second network |
US20070286204A1 (en) * | 2006-06-12 | 2007-12-13 | Hamid Ould-Brahim | Supporting Multi-Protocol Label Switching (MPLS) Applications Over Ethernet Switch Paths |
US7660307B2 (en) * | 2006-06-29 | 2010-02-09 | Verint Americas Inc. | Systems and methods for providing recording as a network service |
US7500023B2 (en) | 2006-10-10 | 2009-03-03 | International Business Machines Corporation | Facilitating input/output processing by using transport control words to reduce input/output communications |
US7502873B2 (en) | 2006-10-10 | 2009-03-10 | International Business Machines Corporation | Facilitating access to status and measurement data associated with input/output processing |
CN101179556B (en) * | 2006-11-06 | 2012-07-04 | 华为技术有限公司 | Method and apparatus for conveying optical fibre channel service |
US8531941B2 (en) | 2007-07-13 | 2013-09-10 | Cisco Technology, Inc. | Intra-domain and inter-domain bridging over MPLS using MAC distribution via border gateway protocol |
US8310953B2 (en) * | 2007-08-21 | 2012-11-13 | International Business Machines Corporation | Method and apparatus for enabling an adapter in a network device to discover the name of another adapter of another network device in a network system |
US8396009B2 (en) * | 2007-08-21 | 2013-03-12 | International Business Machines Corporation | Method and apparatus for an adapter in a network device to discover its adapter name in a network system |
US20090052461A1 (en) * | 2007-08-21 | 2009-02-26 | Ibm Corporation | Method and Apparatus for Fibre Channel Over Ethernet Data Packet Translation Via Look up Table Conversion Bridge in a Network System |
US8041773B2 (en) | 2007-09-24 | 2011-10-18 | The Research Foundation Of State University Of New York | Automatic clustering for self-organizing grids |
US7787454B1 (en) * | 2007-10-31 | 2010-08-31 | Gigamon Llc. | Creating and/or managing meta-data for data storage devices using a packet switch appliance |
KR20090052784A (en) * | 2007-11-21 | 2009-05-26 | 엘지전자 주식회사 | Method for commnunicating with relay station |
WO2009081953A1 (en) * | 2007-12-26 | 2009-07-02 | Canon Anelva Corporation | Sputtering apparatus, sputter film forming method, and analyzer |
US7840717B2 (en) | 2008-02-14 | 2010-11-23 | International Business Machines Corporation | Processing a variable length device command word at a control unit in an I/O processing system |
US9052837B2 (en) | 2008-02-14 | 2015-06-09 | International Business Machines Corporation | Processing communication data in a ships passing condition |
US7941570B2 (en) | 2008-02-14 | 2011-05-10 | International Business Machines Corporation | Bi-directional data transfer within a single I/O operation |
US7899944B2 (en) | 2008-02-14 | 2011-03-01 | International Business Machines Corporation | Open exchange limiting in an I/O processing system |
US8117347B2 (en) | 2008-02-14 | 2012-02-14 | International Business Machines Corporation | Providing indirect data addressing for a control block at a channel subsystem of an I/O processing system |
US8082481B2 (en) | 2008-02-14 | 2011-12-20 | International Business Machines Corporation | Multiple CRC insertion in an output data stream |
US7917813B2 (en) | 2008-02-14 | 2011-03-29 | International Business Machines Corporation | Exception condition determination at a control unit in an I/O processing system |
US8312189B2 (en) | 2008-02-14 | 2012-11-13 | International Business Machines Corporation | Processing of data to monitor input/output operations |
US7904605B2 (en) | 2008-02-14 | 2011-03-08 | International Business Machines Corporation | Computer command and response for determining the state of an I/O operation |
US8176222B2 (en) | 2008-02-14 | 2012-05-08 | International Business Machines Corporation | Early termination of an I/O operation in an I/O processing system |
US8108570B2 (en) | 2008-02-14 | 2012-01-31 | International Business Machines Corporation | Determining the state of an I/O operation |
US8478915B2 (en) * | 2008-02-14 | 2013-07-02 | International Business Machines Corporation | Determining extended capability of a channel path |
US7840718B2 (en) | 2008-02-14 | 2010-11-23 | International Business Machines Corporation | Processing of data to suspend operations in an input/output processing log-out system |
US7937507B2 (en) | 2008-02-14 | 2011-05-03 | International Business Machines Corporation | Extended measurement word determination at a channel subsystem of an I/O processing system |
US8166206B2 (en) | 2008-02-14 | 2012-04-24 | International Business Machines Corporation | Cancel instruction and command for determining the state of an I/O operation |
US8214562B2 (en) | 2008-02-14 | 2012-07-03 | International Business Machines Corporation | Processing of data to perform system changes in an input/output processing system |
US7890668B2 (en) | 2008-02-14 | 2011-02-15 | International Business Machines Corporation | Providing indirect data addressing in an input/output processing system where the indirect data address list is non-contiguous |
US7908403B2 (en) | 2008-02-14 | 2011-03-15 | International Business Machines Corporation | Reserved device access contention reduction |
US8095847B2 (en) | 2008-02-14 | 2012-01-10 | International Business Machines Corporation | Exception condition handling at a channel subsystem in an I/O processing system |
US8001298B2 (en) * | 2008-02-14 | 2011-08-16 | International Business Machines Corporation | Providing extended measurement data in an I/O processing system |
US8196149B2 (en) | 2008-02-14 | 2012-06-05 | International Business Machines Corporation | Processing of data to determine compatability in an input/output processing system |
CN101981962B (en) * | 2008-03-31 | 2013-07-24 | 日本电气株式会社 | Concealment processing device, concealment processing method, and concealment processing program |
US8307048B2 (en) * | 2008-07-15 | 2012-11-06 | International Business Machines Corporation | Network system with initiator subnetwork communication to target subnetwork communication including fibre channel over ethernet to fibre channel over internet protocol conversion |
US7937504B2 (en) | 2008-07-31 | 2011-05-03 | International Business Machines Corporation | Transport control channel program message pairing |
US7904606B2 (en) | 2008-07-31 | 2011-03-08 | International Business Machines Corporation | Transport control channel program chain linked branching |
US8055807B2 (en) | 2008-07-31 | 2011-11-08 | International Business Machines Corporation | Transport control channel program chain linking including determining sequence order |
US8417895B1 (en) | 2008-09-30 | 2013-04-09 | Violin Memory Inc. | System for maintaining coherency during offline changes to storage media |
US8838850B2 (en) * | 2008-11-17 | 2014-09-16 | Violin Memory, Inc. | Cluster control protocol |
US8442059B1 (en) | 2008-09-30 | 2013-05-14 | Gridiron Systems, Inc. | Storage proxy with virtual ports configuration |
US8218571B2 (en) * | 2008-10-24 | 2012-07-10 | International Business Machines Corporation | Fibre channel framing and signaling optional header for ethernet fabric configuration information |
US8472482B2 (en) * | 2008-10-27 | 2013-06-25 | Cisco Technology, Inc. | Multiple infiniband ports within a higher data rate port using multiplexing |
US8443150B1 (en) | 2008-11-04 | 2013-05-14 | Violin Memory Inc. | Efficient reloading of data into cache resource |
US8214599B2 (en) * | 2008-11-04 | 2012-07-03 | Gridiron Systems, Inc. | Storage device prefetch system using directed graph clusters |
US8775741B1 (en) | 2009-01-13 | 2014-07-08 | Violin Memory Inc. | Using temporal access patterns for determining prefetch suitability |
US8788758B1 (en) | 2008-11-04 | 2014-07-22 | Violin Memory Inc | Least profitability used caching scheme |
US8214608B2 (en) * | 2008-11-04 | 2012-07-03 | Gridiron Systems, Inc. | Behavioral monitoring of storage access patterns |
US8285961B2 (en) | 2008-11-13 | 2012-10-09 | Grid Iron Systems, Inc. | Dynamic performance virtualization for disk access |
CN101459611B (en) * | 2008-12-23 | 2011-07-06 | 杭州华三通信技术有限公司 | Data transmission scheduling method, system and device for IP SAN storage |
US8667366B1 (en) | 2009-04-17 | 2014-03-04 | Violin Memory, Inc. | Efficient use of physical address space for data overflow and validation |
US8417871B1 (en) | 2009-04-17 | 2013-04-09 | Violin Memory Inc. | System for increasing storage media performance |
JP5332854B2 (en) * | 2009-04-20 | 2013-11-06 | ソニー株式会社 | Wireless transmitter, wireless transmission method, wireless receiver, and wireless reception method |
US8713252B1 (en) | 2009-05-06 | 2014-04-29 | Violin Memory, Inc. | Transactional consistency scheme |
US9069676B2 (en) | 2009-06-03 | 2015-06-30 | Violin Memory, Inc. | Mapping engine for a storage device |
US8402198B1 (en) | 2009-06-03 | 2013-03-19 | Violin Memory, Inc. | Mapping engine for a storage device |
US9973446B2 (en) | 2009-08-20 | 2018-05-15 | Oracle International Corporation | Remote shared server peripherals over an Ethernet network for resource virtualization |
US8402246B1 (en) | 2009-08-28 | 2013-03-19 | Violin Memory, Inc. | Alignment adjustment in a tiered storage system |
US20110103391A1 (en) | 2009-10-30 | 2011-05-05 | Smooth-Stone, Inc. C/O Barry Evans | System and method for high-performance, low-power data center interconnect fabric |
US9077654B2 (en) | 2009-10-30 | 2015-07-07 | Iii Holdings 2, Llc | System and method for data center security enhancements leveraging managed server SOCs |
US20130107444A1 (en) | 2011-10-28 | 2013-05-02 | Calxeda, Inc. | System and method for flexible storage and networking provisioning in large scalable processor installations |
US9054990B2 (en) | 2009-10-30 | 2015-06-09 | Iii Holdings 2, Llc | System and method for data center security enhancements leveraging server SOCs or server fabrics |
US9465771B2 (en) | 2009-09-24 | 2016-10-11 | Iii Holdings 2, Llc | Server on a chip and node cards comprising one or more of same |
US9876735B2 (en) | 2009-10-30 | 2018-01-23 | Iii Holdings 2, Llc | Performance and power optimized computer system architectures and methods leveraging power optimized tree fabric interconnect |
US8599863B2 (en) | 2009-10-30 | 2013-12-03 | Calxeda, Inc. | System and method for using a multi-protocol fabric module across a distributed server interconnect fabric |
US9311269B2 (en) | 2009-10-30 | 2016-04-12 | Iii Holdings 2, Llc | Network proxy for high-performance, low-power data center interconnect fabric |
US9680770B2 (en) | 2009-10-30 | 2017-06-13 | Iii Holdings 2, Llc | System and method for using a multi-protocol fabric module across a distributed server interconnect fabric |
US9648102B1 (en) | 2012-12-27 | 2017-05-09 | Iii Holdings 2, Llc | Memcached server functionality in a cluster of data processing nodes |
US10877695B2 (en) | 2009-10-30 | 2020-12-29 | Iii Holdings 2, Llc | Memcached server functionality in a cluster of data processing nodes |
US11720290B2 (en) | 2009-10-30 | 2023-08-08 | Iii Holdings 2, Llc | Memcached server functionality in a cluster of data processing nodes |
US8332542B2 (en) | 2009-11-12 | 2012-12-11 | International Business Machines Corporation | Communication with input/output system devices |
US8711864B1 (en) * | 2010-03-30 | 2014-04-29 | Chengdu Huawei Symantec Technologies Co., Ltd. | System and method for supporting fibre channel over ethernet communication |
US8635375B2 (en) | 2010-04-14 | 2014-01-21 | Brocade Communications Systems, Inc. | Remote F—ports |
US8514856B1 (en) | 2010-06-24 | 2013-08-20 | Cisco Technology, Inc. | End-to-end fibre channel over ethernet |
US8959288B1 (en) | 2010-07-29 | 2015-02-17 | Violin Memory, Inc. | Identifying invalid cache data |
US8832384B1 (en) | 2010-07-29 | 2014-09-09 | Violin Memory, Inc. | Reassembling abstracted memory accesses for prefetching |
CN102457435B (en) * | 2010-10-27 | 2015-02-25 | 杭州华三通信技术有限公司 | Message transmission method in FC (Fiber Channel) network as well as FC system and FC equipment |
US8594080B2 (en) * | 2010-10-29 | 2013-11-26 | International Business Machines Corporation | Multiple functionality in a virtual storage area network device |
US8972689B1 (en) | 2011-02-02 | 2015-03-03 | Violin Memory, Inc. | Apparatus, method and system for using real-time performance feedback for modeling and improving access to solid state media |
US8635416B1 (en) | 2011-03-02 | 2014-01-21 | Violin Memory Inc. | Apparatus, method and system for using shadow drives for alternative drive commands |
US8364854B2 (en) | 2011-06-01 | 2013-01-29 | International Business Machines Corporation | Fibre channel input/output data routing system and method |
US8738811B2 (en) | 2011-06-01 | 2014-05-27 | International Business Machines Corporation | Fibre channel input/output data routing system and method |
US8364853B2 (en) | 2011-06-01 | 2013-01-29 | International Business Machines Corporation | Fibre channel input/output data routing system and method |
US8677027B2 (en) | 2011-06-01 | 2014-03-18 | International Business Machines Corporation | Fibre channel input/output data routing system and method |
US9021155B2 (en) | 2011-06-01 | 2015-04-28 | International Business Machines Corporation | Fibre channel input/output data routing including discarding of data transfer requests in response to error detection |
US8583988B2 (en) | 2011-06-01 | 2013-11-12 | International Business Machines Corporation | Fibre channel input/output data routing system and method |
US8312176B1 (en) | 2011-06-30 | 2012-11-13 | International Business Machines Corporation | Facilitating transport mode input/output operations between a channel subsystem and input/output devices |
US8549185B2 (en) | 2011-06-30 | 2013-10-01 | International Business Machines Corporation | Facilitating transport mode input/output operations between a channel subsystem and input/output devices |
US8346978B1 (en) | 2011-06-30 | 2013-01-01 | International Business Machines Corporation | Facilitating transport mode input/output operations between a channel subsystem and input/output devices |
US8473641B2 (en) | 2011-06-30 | 2013-06-25 | International Business Machines Corporation | Facilitating transport mode input/output operations between a channel subsystem and input/output devices |
US8780913B2 (en) * | 2011-08-30 | 2014-07-15 | International Business Machines Corporation | Operating an infiniband network having nodes and at least one IB switch |
US9092594B2 (en) | 2011-10-31 | 2015-07-28 | Iii Holdings 2, Llc | Node card management in a modular and large scalable server system |
WO2013069133A1 (en) * | 2011-11-10 | 2013-05-16 | 株式会社日立製作所 | Frame relay apparatus, communication system, and data transfer method |
US9729408B2 (en) * | 2012-02-15 | 2017-08-08 | Vss Monitoring, Inc. | Encapsulating data packets |
US9819737B2 (en) | 2012-08-23 | 2017-11-14 | Cisco Technology, Inc. | System and method for policy based fibre channel zoning for virtualized and stateless computing in a network environment |
US9391926B2 (en) | 2012-10-26 | 2016-07-12 | Dell Products L.P. | Systems and methods for stacking fibre channel switches with fibre channel over ethernet stacking links |
US9083550B2 (en) * | 2012-10-29 | 2015-07-14 | Oracle International Corporation | Network virtualization over infiniband |
US8918542B2 (en) | 2013-03-15 | 2014-12-23 | International Business Machines Corporation | Facilitating transport mode data transfer between a channel subsystem and input/output devices |
US8990439B2 (en) | 2013-05-29 | 2015-03-24 | International Business Machines Corporation | Transport mode data transfer between a channel subsystem and input/output devices |
US9503523B2 (en) * | 2013-09-20 | 2016-11-22 | Cisco Technology, Inc. | Hybrid fibre channel storage with end-to-end storage provisioning and external connectivity in a storage area network environment |
US9853873B2 (en) | 2015-01-10 | 2017-12-26 | Cisco Technology, Inc. | Diagnosis and throughput measurement of fibre channel ports in a storage area network environment |
US10084859B2 (en) * | 2015-01-26 | 2018-09-25 | International Business Machines Corporation | Method to designate and implement new routing options for high priority data flows |
US9900250B2 (en) | 2015-03-26 | 2018-02-20 | Cisco Technology, Inc. | Scalable handling of BGP route information in VXLAN with EVPN control plane |
US10222986B2 (en) | 2015-05-15 | 2019-03-05 | Cisco Technology, Inc. | Tenant-level sharding of disks with tenant-specific storage modules to enable policies per tenant in a distributed storage system |
US11588783B2 (en) | 2015-06-10 | 2023-02-21 | Cisco Technology, Inc. | Techniques for implementing IPV6-based distributed storage space |
US10778765B2 (en) | 2015-07-15 | 2020-09-15 | Cisco Technology, Inc. | Bid/ask protocol in scale-out NVMe storage |
US10785150B2 (en) * | 2015-09-25 | 2020-09-22 | Intel Corporation | CRC update mechanism |
US9892075B2 (en) | 2015-12-10 | 2018-02-13 | Cisco Technology, Inc. | Policy driven storage in a microserver computing environment |
JP6734058B2 (en) | 2016-01-27 | 2020-08-05 | 株式会社バイオス | Control device |
CN107851132B (en) * | 2016-04-29 | 2021-04-09 | 慧与发展有限责任合伙企业 | Method, system, and medium for target driven peer-to-peer partition synchronization |
US10140172B2 (en) | 2016-05-18 | 2018-11-27 | Cisco Technology, Inc. | Network-aware storage repairs |
US20170351639A1 (en) | 2016-06-06 | 2017-12-07 | Cisco Technology, Inc. | Remote memory access using memory mapped addressing among multiple compute nodes |
US10664169B2 (en) | 2016-06-24 | 2020-05-26 | Cisco Technology, Inc. | Performance of object storage system by reconfiguring storage devices based on latency that includes identifying a number of fragments that has a particular storage device as its primary storage device and another number of fragments that has said particular storage device as its replica storage device |
US11563695B2 (en) | 2016-08-29 | 2023-01-24 | Cisco Technology, Inc. | Queue protection using a shared global memory reserve |
US10891253B2 (en) | 2016-09-08 | 2021-01-12 | Microsoft Technology Licensing, Llc | Multicast apparatuses and methods for distributing data to multiple receivers in high-performance computing and cloud-based networks |
US10545914B2 (en) | 2017-01-17 | 2020-01-28 | Cisco Technology, Inc. | Distributed object storage |
US10243823B1 (en) | 2017-02-24 | 2019-03-26 | Cisco Technology, Inc. | Techniques for using frame deep loopback capabilities for extended link diagnostics in fibre channel storage area networks |
US10713203B2 (en) | 2017-02-28 | 2020-07-14 | Cisco Technology, Inc. | Dynamic partition of PCIe disk arrays based on software configuration / policy distribution |
US10254991B2 (en) | 2017-03-06 | 2019-04-09 | Cisco Technology, Inc. | Storage area network based extended I/O metrics computation for deep insight into application performance |
US10303534B2 (en) | 2017-07-20 | 2019-05-28 | Cisco Technology, Inc. | System and method for self-healing of application centric infrastructure fabric memory |
US10404596B2 (en) | 2017-10-03 | 2019-09-03 | Cisco Technology, Inc. | Dynamic route profile storage in a hardware trie routing table |
US10942666B2 (en) | 2017-10-13 | 2021-03-09 | Cisco Technology, Inc. | Using network device replication in distributed storage clusters |
US10884975B2 (en) | 2017-11-30 | 2021-01-05 | Samsung Electronics Co., Ltd. | Differentiated storage services in ethernet SSD |
US10866917B2 (en) * | 2018-12-03 | 2020-12-15 | Ati Technologies Ulc | Inter device data exchange via external bus by utilizing communication port |
US11159612B1 (en) | 2020-04-28 | 2021-10-26 | Hewlett Packard Enterprise Development Lp | Determining non-TDP zones in a storage area network |
JPWO2022102544A1 (en) | 2020-11-13 | 2022-05-19 |
Family Cites Families (120)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5818603A (en) | 1996-03-29 | 1998-10-06 | Ricoh Company, Ltd. | Method and system for controlling and communicating with machines using multiple communication formats |
US5428471A (en) * | 1992-07-30 | 1995-06-27 | Alcatel Network Systems, Inc. | Fail-safe automatic shut-down apparatus and method for high output power optical communications system |
US5708659A (en) * | 1993-10-20 | 1998-01-13 | Lsi Logic Corporation | Method for hashing in a packet network switching system |
US5617421A (en) * | 1994-06-17 | 1997-04-01 | Cisco Systems, Inc. | Extended domain computer network using standard links |
US5675741A (en) | 1994-10-25 | 1997-10-07 | Cabletron Systems, Inc. | Method and apparatus for determining a communications path between two nodes in an Internet Protocol (IP) network |
US5506838A (en) * | 1994-12-29 | 1996-04-09 | Emc Corporation | Packet propagation and dynamic route discovery apparatus and techniques |
US5682479A (en) | 1995-05-05 | 1997-10-28 | Silicon Graphics, Inc. | System and method for network exploration and access |
US5862125A (en) * | 1995-06-07 | 1999-01-19 | Mci Communication Corporation | Automated restoration of unrestored link and nodal failures |
US5819112A (en) | 1995-09-08 | 1998-10-06 | Microsoft Corporation | Apparatus for controlling an I/O port by queuing requests and in response to a predefined condition, enabling the I/O port to receive the interrupt requests |
US5809285A (en) * | 1995-12-21 | 1998-09-15 | Compaq Computer Corporation | Computer system having a virtual drive array controller |
US6035105A (en) * | 1996-01-02 | 2000-03-07 | Cisco Technology, Inc. | Multiple VLAN architecture system |
US5959990A (en) * | 1996-03-12 | 1999-09-28 | Bay Networks, Inc. | VLAN frame format |
US5742604A (en) * | 1996-03-28 | 1998-04-21 | Cisco Systems, Inc. | Interswitch link mechanism for connecting high-performance network switches |
US5764636A (en) * | 1996-03-28 | 1998-06-09 | Cisco Technology, Inc. | Color blocking logic mechanism for a high-performance network switch |
US5740171A (en) * | 1996-03-28 | 1998-04-14 | Cisco Systems, Inc. | Address translation mechanism for a high-performance network switch |
GB2318030B (en) * | 1996-10-04 | 2001-03-14 | Ibm | Communication system with exchange of capability information |
US5740159A (en) * | 1996-05-23 | 1998-04-14 | Northern Telecom Limited | Loopback mechanism for frame relay OAM |
US6101497A (en) * | 1996-05-31 | 2000-08-08 | Emc Corporation | Method and apparatus for independent and simultaneous access to a common data set |
US6076105A (en) | 1996-08-02 | 2000-06-13 | Hewlett-Packard Corp. | Distributed resource and project management |
US6202135B1 (en) * | 1996-12-23 | 2001-03-13 | Emc Corporation | System and method for reconstructing data associated with protected storage volume stored in multiple modules of back-up mass data storage facility |
US6185203B1 (en) * | 1997-02-18 | 2001-02-06 | Vixel Corporation | Fibre channel switching fabric |
US5964841A (en) * | 1997-03-03 | 1999-10-12 | Cisco Technology, Inc. | Technique for handling forwarding transients with link state routing protocol |
US6160813A (en) | 1997-03-21 | 2000-12-12 | Brocade Communications Systems, Inc. | Fibre channel switching system and method |
US5959972A (en) * | 1997-05-27 | 1999-09-28 | 3Com Corporation | Method of port/link redundancy in an ATM switch |
US6209059B1 (en) * | 1997-09-25 | 2001-03-27 | Emc Corporation | Method and apparatus for the on-line reconfiguration of the logical volumes of a data storage system |
US5879112A (en) * | 1997-10-30 | 1999-03-09 | Ivey; Roy M. | Water supply line tapping tool |
US6188694B1 (en) * | 1997-12-23 | 2001-02-13 | Cisco Technology, Inc. | Shared spanning tree protocol |
US6032194A (en) * | 1997-12-24 | 2000-02-29 | Cisco Technology, Inc. | Method and apparatus for rapidly reconfiguring computer networks |
US6208649B1 (en) * | 1998-03-11 | 2001-03-27 | Cisco Technology, Inc. | Derived VLAN mapping technique |
US6330614B1 (en) * | 1998-03-20 | 2001-12-11 | Nexabit Networks Llc | Internet and related networks, a method of and system for substitute use of checksum field space in information processing datagram headers for obviating processing speed and addressing space limitations and providing other features |
US6208623B1 (en) * | 1998-04-13 | 2001-03-27 | 3Com Corporation | Method of combining PNNI and E-IISP in an asynchronous transfer mode network |
US7027406B1 (en) * | 1998-04-16 | 2006-04-11 | Avaya Communication Israel Ltd. | Distributed port-blocking method |
US6188668B1 (en) * | 1998-05-01 | 2001-02-13 | Emulex Corporation | Automatic isolation in loops |
US7430164B2 (en) * | 1998-05-04 | 2008-09-30 | Hewlett-Packard Development Company, L.P. | Path recovery on failure in load balancing switch protocols |
US6260120B1 (en) * | 1998-06-29 | 2001-07-10 | Emc Corporation | Storage mapping and partitioning among multiple host processors in the presence of login state changes and host controller replacement |
US6295575B1 (en) * | 1998-06-29 | 2001-09-25 | Emc Corporation | Configuring vectors of logical storage units for data storage partitioning and sharing |
US6269381B1 (en) * | 1998-06-30 | 2001-07-31 | Emc Corporation | Method and apparatus for backing up data before updating the data and for restoring from the backups |
US6269431B1 (en) * | 1998-08-13 | 2001-07-31 | Emc Corporation | Virtual storage and block level direct access of secondary storage for recovery of backup data |
US6262977B1 (en) * | 1998-08-28 | 2001-07-17 | 3Com Corporation | High availability spanning tree with rapid reconfiguration |
US6295296B1 (en) * | 1998-09-08 | 2001-09-25 | Cisco Technology, Inc. | Use of a single data structure for label forwarding and imposition |
US6438612B1 (en) * | 1998-09-11 | 2002-08-20 | Ssh Communications Security, Ltd. | Method and arrangement for secure tunneling of data between virtual routers |
US6426952B1 (en) * | 1998-09-18 | 2002-07-30 | The United States Of America As Represented By The Secretary Of The Navy | Multi-interface point-to-point switching system (MIPPSS) having an internal universal signal format |
US6266705B1 (en) * | 1998-09-29 | 2001-07-24 | Cisco Systems, Inc. | Look up mechanism and associated hash table for a network switch |
US6185631B1 (en) | 1998-10-14 | 2001-02-06 | International Business Machines Corporation | Program for transferring execution of certain channel functions to a control unit and having means for combining certain commands and data packets in one sequence |
US6408001B1 (en) * | 1998-10-21 | 2002-06-18 | Lucent Technologies Inc. | Method for determining label assignments for a router |
US6765919B1 (en) * | 1998-10-23 | 2004-07-20 | Brocade Communications Systems, Inc. | Method and system for creating and implementing zones within a fibre channel system |
US6205488B1 (en) * | 1998-11-13 | 2001-03-20 | Nortel Networks Limited | Internet protocol virtual private network realization using multi-protocol label switching tunnels |
US6493349B1 (en) | 1998-11-13 | 2002-12-10 | Nortel Networks Limited | Extended internet protocol virtual private network architectures |
US6898189B1 (en) * | 2000-08-23 | 2005-05-24 | Cisco Technology, Inc. | Restartable spanning tree for high availability network systems |
US6226771B1 (en) * | 1998-12-14 | 2001-05-01 | Cisco Technology, Inc. | Method and apparatus for generating error detection data for encapsulated frames |
US6529963B1 (en) * | 1998-12-29 | 2003-03-04 | Lsi Logic Corporation | Methods and apparatus for interconnecting independent fibre channel fabrics |
US6337861B1 (en) * | 1999-02-02 | 2002-01-08 | Cisco Technology, Inc. | Method and apparatus to properly route ICMP messages in a tag-switching network |
US6473421B1 (en) | 1999-03-29 | 2002-10-29 | Cisco Technology, Inc. | Hierarchical label switching across multiple OSPF areas |
ATE406017T1 (en) | 1999-05-11 | 2008-09-15 | British Telecomm | OPTICAL COMMUNICATIONS NETWORK |
US6661773B1 (en) | 1999-06-07 | 2003-12-09 | Intel Corporation | Method for detection of stale cells following route changes in a data communication |
US6804776B1 (en) | 1999-09-21 | 2004-10-12 | Cisco Technology, Inc. | Method for universal transport encapsulation for Internet Protocol network communications |
US6674760B1 (en) * | 1999-09-28 | 2004-01-06 | Extreme Networks, Inc. | Method and system for implementing end-to-end QoS in packet-switched networks |
US6859435B1 (en) * | 1999-10-13 | 2005-02-22 | Lucent Technologies Inc. | Prevention of deadlocks and livelocks in lossless, backpressured packet networks |
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 |
US6643287B1 (en) * | 1999-11-24 | 2003-11-04 | Pluris, Inc. | Apparatus and method for forwarding encapsulated data packets on a network having multiple links between nodes |
US7006525B1 (en) * | 2000-02-23 | 2006-02-28 | Cypress Semiconductor Corp. | Hybrid data transport scheme over optical networks |
US7082140B1 (en) * | 2000-03-17 | 2006-07-25 | Nortel Networks Ltd | System, device and method for supporting a label switched path across a non-MPLS compliant segment |
ATE416791T1 (en) * | 2000-05-02 | 2008-12-15 | Theravance Inc | COMPOSITION CONTAINING A CYCLODEXTRIN AND A GLYCOPEPTIDE ANTIBIOTIC |
JP4168574B2 (en) * | 2000-06-02 | 2008-10-22 | 株式会社日立製作所 | Packet transfer apparatus, packet transfer control method, and packet transfer apparatus setting method |
US6920133B1 (en) * | 2000-06-07 | 2005-07-19 | At&T Corp. | Techniques for introducing in-band network management packets in multi-protocol label switching networks |
EP1162793B1 (en) * | 2000-06-09 | 2012-08-15 | Broadcom Corporation | Gigabit switch with multicast handling |
US6920153B2 (en) * | 2000-07-17 | 2005-07-19 | Nortel Networks Limited | Architecture and addressing scheme for storage interconnect and emerging storage service providers |
US6775230B1 (en) * | 2000-07-18 | 2004-08-10 | Hitachi, Ltd. | Apparatus and method for transmitting frames via a switch in a storage area network |
US6847647B1 (en) * | 2000-09-26 | 2005-01-25 | Hewlett-Packard Development Company, L.P. | Method and apparatus for distributing traffic over multiple switched fiber channel routes |
US6879560B1 (en) * | 2000-12-08 | 2005-04-12 | At&T Corp. | System and method for limiting congestion over a switch network |
JP2002190825A (en) | 2000-12-21 | 2002-07-05 | Fujitsu Ltd | Traffic engineering method and node equipment using it |
US6975589B2 (en) | 2000-12-30 | 2005-12-13 | Redback Networks Inc. | Method and apparatus for a hybrid variable rate pipe |
US7054304B2 (en) * | 2001-01-19 | 2006-05-30 | Terited International , Inc. | Method and protocol for managing broadband IP services in a layer two broadcast network |
US20020101868A1 (en) * | 2001-01-30 | 2002-08-01 | David Clear | Vlan tunneling protocol |
US7050392B2 (en) * | 2001-03-30 | 2006-05-23 | Brocade Communications Systems, Inc. | In-order delivery of frames during topology change |
US6947379B1 (en) | 2001-04-03 | 2005-09-20 | Cisco Technology, Inc. | Packet routing to reduce susceptibility to disturbances |
US6604407B2 (en) * | 2001-04-03 | 2003-08-12 | Denso Corporation | Leak check apparatus for fuel vapor purge system |
US7366194B2 (en) | 2001-04-18 | 2008-04-29 | Brocade Communications Systems, Inc. | Fibre channel zoning by logical unit number in hardware |
US20020156924A1 (en) | 2001-04-23 | 2002-10-24 | Moshe Czeiger | Method for communicating between fibre channel systems |
US20020156918A1 (en) | 2001-04-23 | 2002-10-24 | Brocade Communications Systems, Inc. | Dynamic path selection with in-order delivery within sequence in a communication network |
US20020159456A1 (en) | 2001-04-27 | 2002-10-31 | Foster Michael S. | Method and system for multicasting in a routing device |
US6728220B2 (en) * | 2001-05-24 | 2004-04-27 | Riverstone Networks, Inc. | Method and system for preventing transmission loops in a label switching domain |
US6728848B2 (en) * | 2001-06-11 | 2004-04-27 | Hitachi, Ltd. | Method and system for backing up storage system data |
US7072298B2 (en) * | 2001-06-13 | 2006-07-04 | Computer Network Technology Corporation | Method and apparatus for rendering a cell-based switch useful for frame based protocols |
US6985490B2 (en) * | 2001-07-11 | 2006-01-10 | Sancastle Technologies, Ltd. | Extension of fibre channel addressing |
US7330892B2 (en) * | 2001-09-07 | 2008-02-12 | Network Appliance, Inc. | High-speed data transfer in a storage virtualization controller |
US6779050B2 (en) * | 2001-09-24 | 2004-08-17 | Broadcom Corporation | System and method for hardware based reassembly of a fragmented packet |
US6532212B1 (en) * | 2001-09-25 | 2003-03-11 | Mcdata Corporation | Trunking inter-switch links |
US7366784B2 (en) * | 2001-11-27 | 2008-04-29 | Hitachi, Ltd. | System and method for providing and using a VLAN-aware storage device |
US20030107987A1 (en) * | 2001-12-07 | 2003-06-12 | Kinstler Gary A. | Reconfiguration system for a communication network |
US7298739B1 (en) * | 2001-12-14 | 2007-11-20 | Applied Micro Circuits Corporation | System and method for communicating switch fabric control information |
US6920154B1 (en) * | 2001-12-17 | 2005-07-19 | Supergate Technology Usa, Inc. | Architectures for a modularized data optimization engine and methods therefor |
US7599360B2 (en) | 2001-12-26 | 2009-10-06 | Cisco Technology, Inc. | Methods and apparatus for encapsulating a frame for transmission in a storage area network |
US7499410B2 (en) * | 2001-12-26 | 2009-03-03 | Cisco Technology, Inc. | Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain—IDs |
US7085846B2 (en) * | 2001-12-31 | 2006-08-01 | Maxxan Systems, Incorporated | Buffer to buffer credit flow control for computer network |
US7155494B2 (en) | 2002-01-09 | 2006-12-26 | Sancastle Technologies Ltd. | Mapping between virtual local area networks and fibre channel zones |
US7216158B2 (en) * | 2002-01-18 | 2007-05-08 | Bea Systems, Inc. | System, method and interface for controlling server lifecycle |
US7349992B2 (en) * | 2002-01-24 | 2008-03-25 | Emulex Design & Manufacturing Corporation | System for communication with a storage area network |
US7873984B2 (en) * | 2002-01-31 | 2011-01-18 | Brocade Communications Systems, Inc. | Network security through configuration servers in the fabric environment |
US7161935B2 (en) * | 2002-01-31 | 2007-01-09 | Brocade Communications Stystems, Inc. | Network fabric management via adjunct processor inter-fabric service link |
US20030189929A1 (en) | 2002-04-04 | 2003-10-09 | Fujitsu Limited | Electronic apparatus for assisting realization of storage area network system |
US7328260B1 (en) * | 2002-06-04 | 2008-02-05 | Symantec Operating Corporation | Mapping discovered devices to SAN-manageable objects using configurable rules |
US7487264B2 (en) * | 2002-06-11 | 2009-02-03 | Pandya Ashish A | High performance IP processor |
US7206288B2 (en) * | 2002-06-12 | 2007-04-17 | Cisco Technology, Inc. | Methods and apparatus for characterizing a route in fibre channel fabric |
US7319669B1 (en) * | 2002-11-22 | 2008-01-15 | Qlogic, Corporation | Method and system for controlling packet flow in networks |
US7433326B2 (en) * | 2002-11-27 | 2008-10-07 | Cisco Technology, Inc. | Methods and devices for exchanging peer parameters between network devices |
US7275103B1 (en) | 2002-12-18 | 2007-09-25 | Veritas Operating Corporation | Storage path optimization for SANs |
US7606239B2 (en) * | 2003-01-31 | 2009-10-20 | Brocade Communications Systems, Inc. | Method and apparatus for providing virtual ports with attached virtual devices in a storage area network |
US8081642B2 (en) * | 2003-01-31 | 2011-12-20 | Brocade Communications Systems, Inc. | Method and apparatus for routing between fibre channel fabrics |
DE10308323B4 (en) * | 2003-02-26 | 2007-10-11 | Infineon Technologies Ag | Semiconductor chip arrangement with ROM |
US7447224B2 (en) * | 2003-07-21 | 2008-11-04 | Qlogic, Corporation | Method and system for routing fibre channel frames |
US20050080903A1 (en) * | 2003-09-30 | 2005-04-14 | Moshe Valenci | Method, system, and program for maintaining a link between two network entities |
US20080028096A1 (en) * | 2003-10-21 | 2008-01-31 | Henderson Alex E | Transporting fibre channel over ethernet |
US20050108444A1 (en) * | 2003-11-19 | 2005-05-19 | Flauaus Gary R. | Method of detecting and monitoring fabric congestion |
US7355983B2 (en) * | 2004-02-10 | 2008-04-08 | Cisco Technology, Inc. | Technique for graceful shutdown of a routing protocol in a network |
US8018936B2 (en) * | 2004-07-19 | 2011-09-13 | Brocade Communications Systems, Inc. | Inter-fabric routing |
US7593324B2 (en) * | 2004-10-25 | 2009-09-22 | Cisco Technology, Inc. | Graceful port shutdown protocol for fibre channel interfaces |
US7916628B2 (en) * | 2004-11-01 | 2011-03-29 | Cisco Technology, Inc. | Trunking for fabric ports in fibre channel switches and attached devices |
US7649844B2 (en) * | 2004-12-29 | 2010-01-19 | Cisco Technology, Inc. | In-order fibre channel packet delivery |
US7519058B2 (en) * | 2005-01-18 | 2009-04-14 | Qlogic, Corporation | Address translation in fibre channel switches |
-
2001
- 2001-12-26 US US10/034,160 patent/US7599360B2/en active Active
-
2002
- 2002-12-23 WO PCT/US2002/041072 patent/WO2003058891A1/en active IP Right Grant
- 2002-12-23 AU AU2002364204A patent/AU2002364204B2/en not_active Ceased
- 2002-12-23 JP JP2003559086A patent/JP4335009B2/en not_active Expired - Fee Related
- 2002-12-23 AT AT02799279T patent/ATE363171T1/en not_active IP Right Cessation
- 2002-12-23 KR KR1020047010143A patent/KR100927265B1/en active IP Right Grant
- 2002-12-23 CA CA2472056A patent/CA2472056C/en not_active Expired - Fee Related
- 2002-12-23 EP EP02799279A patent/EP1459485B1/en not_active Expired - Lifetime
- 2002-12-23 DE DE60220313T patent/DE60220313T2/en not_active Expired - Lifetime
- 2002-12-23 CN CNB028282620A patent/CN100348000C/en not_active Expired - Fee Related
-
2004
- 2004-03-01 US US10/791,143 patent/US20050025075A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
WO2003058891A1 (en) | 2003-07-17 |
CN1620784A (en) | 2005-05-25 |
KR100927265B1 (en) | 2009-11-18 |
AU2002364204A1 (en) | 2003-07-24 |
US20050025075A1 (en) | 2005-02-03 |
EP1459485B1 (en) | 2007-05-23 |
US20030118053A1 (en) | 2003-06-26 |
JP2005514862A (en) | 2005-05-19 |
US7599360B2 (en) | 2009-10-06 |
CA2472056A1 (en) | 2003-07-17 |
DE60220313D1 (en) | 2007-07-05 |
EP1459485A1 (en) | 2004-09-22 |
ATE363171T1 (en) | 2007-06-15 |
AU2002364204B2 (en) | 2008-04-03 |
JP4335009B2 (en) | 2009-09-30 |
CN100348000C (en) | 2007-11-07 |
KR20040068355A (en) | 2004-07-30 |
DE60220313T2 (en) | 2008-01-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2472056C (en) | Methods and apparatus for encapsulating a frame for transmission in a storage area network | |
US8238347B2 (en) | Fibre channel over ethernet | |
US10057164B2 (en) | Apparatus and methods to aggregate FCoE (fibre channel over ethernet) filter rules of a single interface in a single or few rules on a first-hop FCoE networking element | |
US10027603B1 (en) | Methods and apparatus to reduce forwarding state on an FCoE-to-FC gateway using port-specific MAC addresses | |
US9225656B2 (en) | Quality of service in a heterogeneous network | |
US9246834B2 (en) | Fibre channel over ethernet | |
US8565231B2 (en) | Ethernet extension for the data center | |
US9414136B2 (en) | Methods and apparatus to route fibre channel frames using reduced forwarding state on an FCoE-to-FC gateway | |
US7830793B2 (en) | Network device architecture for consolidating input/output and reducing latency | |
US8125992B2 (en) | System and method for providing proxy and translation domains in a fibre channel router | |
US8446913B2 (en) | Multifabric zone device import and export | |
US7145866B1 (en) | Virtual network devices | |
US6018530A (en) | Method for transmitting using a modified transport control protocol | |
US20060023708A1 (en) | Interfabric routing header for use with a backbone fabric | |
US8798046B2 (en) | Methods and apparatus for providing unique MAC address to individual node for fibre channel over Ethernet (FCoE) traffic | |
US20060023751A1 (en) | Multifabric global header | |
JP3956303B2 (en) | COMMUNICATION METHOD USING LOGICAL CHANNEL ACCORDING TO PRIORITY, COMMUNICATION DEVICE FOR IMPLEMENTING SAME, PROGRAM THEREOF, AND RECORDING MEDIUM | |
Wadekar | Handbook of Fiber Optic Data Communication: Chapter 11. InfiniBand, iWARP, and RoCE |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
MKLA | Lapsed |
Effective date: 20171227 |