US20050025075A1 - Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain_IDs - Google Patents

Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain_IDs Download PDF

Info

Publication number
US20050025075A1
US20050025075A1 US10/791,143 US79114304A US2005025075A1 US 20050025075 A1 US20050025075 A1 US 20050025075A1 US 79114304 A US79114304 A US 79114304A US 2005025075 A1 US2005025075 A1 US 2005025075A1
Authority
US
United States
Prior art keywords
fabric
switch
vsan
end devices
fabrics
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/791,143
Inventor
Dinesh Dutt
Silvano Gai
Bruno Raimondo
Thomas Edsall
Subrata Banerjee
Rajeev Bhardwaj
Ankur Jain
Davide Bergamasco
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Cisco Technology Inc
Original Assignee
Cisco Technology Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority to US10/609,442 priority Critical patent/US7499410B2/en
Application filed by Cisco Technology Inc filed Critical Cisco Technology Inc
Priority to US10/791,143 priority patent/US20050025075A1/en
Priority to CN2004800108260A priority patent/CN1778076B/en
Priority to CN2010101414913A priority patent/CN101795298B/en
Priority to AU2004300680A priority patent/AU2004300680B2/en
Priority to EP04756162.6A priority patent/EP1636946B1/en
Priority to CA2521463A priority patent/CA2521463C/en
Priority to EP18176090.1A priority patent/EP3389229A1/en
Priority to PCT/US2004/020518 priority patent/WO2005004408A1/en
Assigned to CISCO TECHNOLOGY, INC. reassignment CISCO TECHNOLOGY, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BANERJEE, SUBRATA, BHARDWAJ, RAJEEV, EDSALL, THOMAS J., GAI, SILVANO, BERGAMASCO, DAVIDE, JAIN, ANKUR, RAIMONDO, BRUNO, DUTT, DINESH G.
Publication of US20050025075A1 publication Critical patent/US20050025075A1/en
Priority to US12/343,843 priority patent/US7876711B2/en
Priority to US12/975,072 priority patent/US8625460B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols 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]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4641Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2212/00Encapsulation of packets

Definitions

  • the present invention is a Continuation-in-Part of co-pending, commonly assigned, application Ser. No. 10/034,160 filed Dec. 26, 2001 and entitled “Methods and Apparatus for Encapsulating a Frame for Transmission in a Storage Area Network”, incorporated herein for all purposes.
  • the present invention relates to storage area networks, and more particularly, to a Fibre Channel Switch that enables the end devices in different Fabrics to communicate with one another while retaining their unique Fibre Channel IDs.
  • a SAN typically includes a number of storage devices, a plurality of Hosts, and a number of Switches arranged in a Switching Fabric that connects the storage devices and the Hosts.
  • Fibre Channel protocol for communication within the Fabric.
  • Fibre Channel Framing and Signaling Standard Rev 1.70, American National Standard of Accredited Standards Committee (NCITS), Feb. 8, 2002, and the Fibre Channel Switch Fabric—2, Rev. 5.4, NCITS, Jun. 26, 2001, and the Fibre Channel Generic Services—3, Rev. 7.01, NCITS, Nov. 28, 2000, all incorporated by reference herein for all purposes.
  • each device Hosts, storage devices and Switches
  • WWN World Wide Name
  • the WWN (along with other parameters) is the primary mechanism to identify each device. Fibre Channel frames are used for communication among the devices in the SAN.
  • FC_ID Fibre Channel address
  • the three byte wide Fibre Channel addresses are hierarchically structured in three fields, each one byte long: Domain_ID, Area_ID, and Port_ID.
  • Each Switch within the Fabric is assigned a Domain_ID.
  • the end devices attached to a particular Switch are assigned the Domain_ID of that Switch.
  • the Switch manages the allocation of the Area_ID and Port_ID fields for each end device to guarantee the uniqueness of the assigned addresses in that Domain. For example, if a Switch is assigned a Domain number five and the Switch subdivides its address space in two areas each having three connected end devices, then a possible Fibre Channel address allocation is: 5:1:1, 5:1:2, 5:1:3, 5:2:1, 5:2:2, and 5:2:3.
  • Fibre Channel based SANs are often organized into zones. Within each zone, Hosts can see and access only storage devices or other Hosts belonging to that zone. This allows the coexistence on the same SAN of different computing environments. For example, it is possible to define on a SAN a Unix zone and a separate Windows zone. Unix servers belonging to the Unix zone may access only storage or Hosts devices within the Unix zone, and do not interfere with the other devices connected to the SAN. In the same manner, Windows servers belonging to the Windows zone may access storage or Hosts devices only within the Windows zone, without interfering with the other devices connected to the SAN. The SAN administrator may define in a SAN multiple zones, as required or dictated by the computing and storage resources connected to it. The Switching Fabric allows communications only between devices belonging to the same zone, preventing a device of one zone from seeing or accessing a device of another zone.
  • the information infrastructure within a large enterprise will typically have a number of SANs, each dedicated for a different organization or application within the enterprise.
  • a large corporation may have different SANs for corporate, for the sales department, the marketing department, etc.
  • Each SAN will typically include redundant Fibre Channel fabrics connecting a plurality of Hosts and storage devices.
  • the redundant Switches in the Fibre Channel fabrics are provided in the event a Switch or link in one Fabric goes down. If this were to occur, the redundant fabric would be used enabling normal operation of SAN.
  • Another example is the use of a dedicated SAN for managing a mail server such as Microsoft Exchange.
  • the aforementioned arrangement has a number of disadvantages.
  • the Hosts in a given SAN can communicate only with the storage devices in that same SAN.
  • This arrangement is not only inefficient, it is expensive. Since storage devices cannot be shared among SANs, separate storage devices are required for each SAN.
  • VSAN Virtual SAN
  • the implementation of a VSAN is based on the concept of dividing the switching fabric of a single physical SAN into logical SANs, each called a VSAN.
  • the properties of each VSAN are similar to a standard SAN, in particular: (i) unicast, broadcast and multicast traffic is confined to a VSAN and does not span multiple VSANs; (ii) Fibre Channel identifiers (FC_IDs) are assigned per VSAN. This means that a given FC address may be assigned to two different Hosts in two different VSANs; and (iii) routing and distributed Fabric Services, such as Name Server, Zone Server, etc. are maintained independently for each VSAN. This results in constraining the effect of a configuration or topology change to only the affected VSAN.
  • FC_ID Fibre Channel identifiers
  • a Fibre Channel Switch and Fabric is needed which enables end devices in different Fabrics to communicate with one another while retaining their unique Fibre Channel Domain_IDs.
  • a Switch which enables end devices in different Fabrics to communicate with one another while retaining their unique Fibre Channel Domain_IDs.
  • the Switch is coupled to a first fabric having a first set of end devices and a second fabric having a second set of end devices.
  • the Switch is configured to enable communication by the first set of end devices associated with the first fabric with the second set of end devices associated with the second fabric using the unique Domain_IDs of each of the first set and the second set of end devices.
  • the first and second fabrics are first and second Virtual Storage Area Networks (VSANs) respectively.
  • VSANs Virtual Storage Area Networks
  • the first fabric and the second fabric are separate physical fabrics.
  • FIG. 1 is an exemplary Fibre Channel Fabric according to the present invention.
  • FIG. 2 is an exemplary VSAN topology according to the present invention.
  • FIG. 3 is another VSAN topology illustrating VSAN border switches.
  • FIGS. 4A and 4B is an exemplary Fibre Channel frame modified for Inter-VSAN routing according to the present invention.
  • FIG. 5 is an exemplary SAN defining “Inter-VSAN zones” according to the present invention.
  • FIG. 6 is an exemplary VSAN for illustrating the modifications to the FSPF protocol according to the present invention.
  • FIG. 7 is an exemplary VSAN for illustrating the operation of the present invention.
  • FIG. 8 is a block diagram of a Switch used to implement Inter-VSAN routing according to the present invention.
  • the main services provided by the fabric include: Dynamic Address Allocation, Routing, Name Service Zone Service, and event notification.
  • the present invention relates to Inter-VSAN and/or Inter-Fabric routing using unique Domain_IDs. Terminology specific to the present invention and defined herein includes:
  • the SAN 100 includes a first VSAN 102 and a second VSAN 104 .
  • the first VSAN 102 includes a Switch E 2 , and an end device pWWN 1 with a FC_ID address of 1.1.1.
  • the second VSAN 104 includes a Switch E 4 and an end device pWWN 4 with a FC_ID address of 2.1.1.
  • a border Switch B 1 is also included in each VSAN.
  • VSAN 102 and VSAN 104 are shown with only one Switch and one end device each for the purposes of illustration.
  • the SAN 100 can be divided into many more VSANs, with each VSAN including one or a plurality of Switches and a set of end devices (hosts and/or storage devices where the number in the set may range from one to a multiplicity of end devices.
  • the end devices pWWN 1 and pWWN 4 can communicate with one another while retaining their respective FC_ID addresses. This is accomplished through the Border Switch B 1 that straddles both VSANs. In a single step process, packets originating from end device pWWN 1 are injected from VSAN 102 to VSAN 104 and pWWN 4 , and vice-versa, through the border Switch B 1 .
  • the term “Fabric” generally implies a single physical Fabric that is divided into separate Virtual SANs.
  • the two VSANs 102 and 104 as illustrated in FIG. 1 could also be two physically separate Fabrics or SANs.
  • the Border Switch enables the end devices pWWN 1 and pWWN 4 to communicate with one another while retaining their respective FC_ID addresses.
  • the invention is described in relation to VSANs of a single Fabric or SAN. It should be understood, however, that the present invention as taught herein can be used with two separate Fabrics or SANs.
  • the Inter-VSAN routing using unique Domain_IDs of the present invention initially requires an administrator to define one or more Inter-VSANs and the end devices that can communicate with one another in the Fabric.
  • the Border Switches After the Fabric is configured, the Border Switches: (i) exchange the Inter-VSAN routing protocol (IVRP) messages with the other Border Switches in the fabric in order to determine the topology and shortest paths to the different VSANs.
  • IVRP Inter-VSAN routing protocol
  • a static configuration is needed to decide the set of VSANs that must be transited by frames from an origination Edge VSAN to a terminating Edge VSAN; (ii) exchange Fabric Shortest Path First (FSPF) information between the neighbor Switches in each VSAN and the neighbor VSANs.
  • FSPF Fabric Shortest Path First
  • Border Switches inject routes into either Transit VSANs; and/or Edge VSANs connected to the Border Switch; (iii) propagate FSPF updates between the Edge and Transit VSANs only if the updates affect routes and link cost to any of the exported Domain_IDs; (iv) exchange zoning information with its neighbor Switches on linkup; (v) exchange name server databases with its neighbor Switches.
  • Host pWWN 1 is included in VSAN 1 .
  • a second Host pWWN 2 is included in VSAN 2 .
  • a storage device pWWN 3 is included in VSAN 3 .
  • the Transit VSAN 12 is used to switch traffic between the disconnected Edge VSAN 1 , VSAN 2 , and VSAN 3 .
  • the Transit VSAN 12 as is described below,enables the Hosts pWWN 1 and pWWN 2 to access the storage device pWWN 3 and vice versa.
  • end devices such as Hosts and storage devices communicate using only Fibre Channel addresses.
  • a tag qualifies a Fibre Channel address so that it can be routed through the Switching Fabric, while being transparent to the end devices.
  • the Transit VSAN 12 switches traffic from the disconnected Edge VSAN pairs 1 - 3 and 2 - 3 and vice-versa.
  • the link between the Switches B and C can be according to various embodiments a standard FC link or remote (e.g., FCIP, FC over DWDM, etc) link.
  • the transit VSAN 12 is similar to any other VSAN and can potentially have its own end devices attached to it.
  • the Transit VSAN 12 does not care about the nature of the neighbor Edge VSANs that it is switching traffic either to or from. In other words, a transit VSAN can switch traffic to or from another transit VSAN.
  • Border Switches are switches that link between or are part of both an Edge VSAN(s) and a Transit VSAN(s).
  • pWWN 1 Host
  • FC_BD 3.1.1
  • Switches S 6 through S 10 .
  • a Transit VSAN includes Switches S 2 , S 3 , S 4 , S 5 , S 8 and S 10 , then S 2 and S 4 are considered Border Switches even though they are not necessarily at the border of VSAN 1 .
  • Switch S 3 Traffic coming from the Transit VSAN to VSAN 1 is by Switch S 3 and traffic from Switch S 1 and directed to the Transit VSAN is switched by S 4 .
  • Switches S 8 and S 10 are Border Switches for VSAN 2 .
  • Switches B and C are defined as Border Switches in FIG. 2 because they are capable of switching traffic between the Transit VSAN 12 and VSAN 1 , VSAN 2 and VSAN 3 .
  • a frame 30 having an Extended Inter-Switch Link (EISL) format for use typically on a link carrying multiple VSANs is shown. While the EISL format can also be used on a link carrying a single VSAN, another option on a link carrying only a single VSAN, is to configure the ingress port of the switch with the VSAN to be associated with frames received on that port.
  • the frame 30 includes a Start of Frame (SOF) field 32 , an EISL header field 34 , an EISL payload field 36 , an EISL Cyclical Redundancy Check (CRC) field 38 , and a End of Frame (EOF) field 40 .
  • the SOF field 32 is the start of the frame delimiter.
  • the EISL payload field 36 includes the header and payload used with a standard ISL frame.
  • the EISL CRC field 306 is used to hold a CRC value specific to the EISL.
  • the EISL CRC value differs or is a modification of a standard CRC value calculated for a regular ISL frame due to the corresponding longer length of the EISL frame 30 with the appended EISL header field 34 .
  • the EOF field 40 delineates the end of the frame 30 .
  • the EISL header field 34 is illustrated.
  • This field includes a plurality of sub-fields including an EISL indicator field 42 for indicating the presence of an EISL header field 34 , an EISL version field 44 that indicates the version of EISL header.
  • the version field 44 is at least two bits wide, allowing the indication of up to four versions of EISL frames. Additional bits may be used if more versions of EISL frames need to be indicated.
  • the frame type field 46 is used to indicate the type of traffic to be carried by the frame. Traffic types may include for example Ethernet, Fibre Channel, or Infiniband. In one embodiment, the frame type field 46 is four-bits wide, allowing up to sixteen different traffic types to be transmitted across the Fabric.
  • the Muli-Protocol Label Switching (MPLS) field 48 indicates if the frame is carrying MPLS information such as label stack 56 , which is a common forwarding mechanism for both Fibre Channel and Ethernet.
  • MPLS MPLS information
  • the MPLS field 48 is one bit wide. When set, it indicates that the EISL header 34 includes an MPLS label stack 56 . Otherwise it is reset.
  • Priority field 50 indicate the user priority of the EISL frame 30 .
  • Priority may be defined in a number of ways.
  • the user priority may be a generic numeric priority, without a guaranteed level of service. For instance, higher values represent higher user priority while lower values may represent lower priority. Higher priorities receive available bandwidth first, regardless of how much total bandwidth is available.
  • the user priority may indicate a quality of service (QoS) of the payload of the EISL frame.
  • QoS quality of service
  • the width of the Priority field 50 depends on the priority type and/or the number of priority levels.
  • the VSAN identifier field 52 or “tag” is used to identify the frame 30 as belonging to a particular VSAN. More particularly, the VSAN identifier field 52 identifies the payload of the EISL frame 30 as belonging to a particular VSAN.
  • the VSAN identifier field 412 is a twelve-bit wide 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.
  • a Time To Live (TTL) field 54 may be used to indicate a TTL value specifying the number of remaining hops that can be traversed before the frame is dropped.
  • the TTL value inserted into field 54 is initialized by the network device (e.g., a Switch) that generates the EISL frame 30 .
  • a TTL default value is initially set to an arbitrary number, for example sixteen. With each hop, subsequent network devices (e.g., Switches) receiving the EISL frame decrement the TTL value by one.
  • a TTL value of one indicates to the receiving network device (e.g., Switch) that the EISL frame should be dropped.
  • the receiving network device e.g., Switch
  • an error message may be sent to the intended recipient of the frame as well as to the sender of the frame.
  • a TTL value of 0 may indicate that the TTL field 54 should be ignored, allowing the EISL frame to be forwarded by the switch.
  • Each frame 30 also includes, in addition to the above, the Fibre Channel addresses (FC_IDs) of the source and destination end devices.
  • FC_IDs Fibre Channel addresses
  • the VSAN ID 52 qualifies a particular frame 30 as belonging to a particular VSAN, transparent to the end devices. For more information on the switching of frames 30 within a VSAN, see the aforementioned parent application.
  • Inter-VSAN zone is defined as a zone that has members from multiple VSANs.
  • Inter-VSAN zone X includes Host pWWN 1 (FC_ID 1.1.1) in VSAN 1 and storage device pWWN 3 (FC-ID 8.1.1) in VSAN 3 .
  • Inter-VSAN zone Y includes Host pWWN 2 (FC_ID 3.1.1) in VSAN 2 and the same storage device pWWN 3 (FC-ID 8.1.1) in VSAN 3 .
  • Inter-VSAN zones X and Y have thus been created so that Hosts pWWN 1 and pWWN 2 can both communicate with storage device pWWN 3 respectively.
  • Border Switches decide: (i) the content of the name server database that is exported into the Transit VSAN from the adjacent Edge VSAN and vice versa; (ii) the set of FSPF domains to export in Link State Update (LSU) messages; (iii) the set of addresses to switch from adjacent Edge VSANs to Transit VSANs and vice versa; (iv) the set of adjacent Edge VSANs to which SW_RSCNs received from a Transit VSAN are propagated; (v) the set of SW_RSCNs received from adjacent Edge VSANs to propagate into the Transit VSAN.
  • the Inter-VSAN zone is the point from which the import and export data and control traffic occurs. Since zone configuration is a well known concept, the configuration of Inter-VSAN routing via Inter-VSAN zones simplifies management and administration in the Fabric.
  • Inter-VSAN zones are contained within a zoneset and there is an active zoneset.
  • the Border Switches thus determine the import and export traffic from the Inter-VSAN zones in the active zoneset.
  • a number of protocols are implemented when a link is established between two Switches. These include the Port Manager; Domain Manager; Zone Server; Fabric Shortest Path First (FSPF); Name_Server; and Switch Register State Change Notification (SW_RSCN) protocols, as described in the above-referenced NCITS documents.
  • FSPF Fabric Shortest Path First
  • SW_RSCN Switch Register State Change Notification
  • the Port manager protocol negotiates parameters between two Switches and determines if the link is an Inter-Switch Link (ISL) or an Extended Inter-Switch Link (EISL). If the link is EISL, then it means that the link is capable of carrying VSAN frames. Otherwise, the Port Manager protocol operates the same with VSANs as with a regular SAN.
  • ISL Inter-Switch Link
  • EISL Extended Inter-Switch Link
  • the Domain Manager Protocol is responsible for the allocation of Domain_IDs and/or Fibre Channel addresses (FC_ID) for each Switch, Host and storage device in the SAN.
  • FC_ID Fibre Channel addresses
  • a FC_ID includes three components, a Domain_ID, an Area_ID, and a Port_ID.
  • a Principal Switch is selected for the SAN. The Principal Switch is responsible for assigning a Domain_ID for each Switch. Each Switch is then responsible for selecting the Area_ID and Port_ID for each end device connected to that Switch.
  • the domain number space must be unique across the VSANs that are going to communicate with one another.
  • this uniqueness can be maintained, including: (i) administratively partitioning the domain number space across the VSANs; or (ii) associate a set of Domain_IDs to be used only for biter-VSAN routing.
  • Domain_IDs between 200 - 239 (or any other arbitrary range) can be dedicated for VSAN routing.
  • a Switch that needed to communicate across VSANs could administratively be configured to request Domain_IDs in the dedicated number space range.
  • Zone Server Protocol In a standard SAN, the Zone Server Protocol is responsible for creating and maintaining a database within each Switch that defines each zone in the SAN.
  • the zones in the table are defined in terms of the Host(s) and storage device(s) in each zone.
  • a Host and/or storage device can belong to multiple zones.
  • To ensure a consistent zoning database across a SAN when an ISL link comes up between two switches, the zone database is exchanged between the switches to ensure consistency and to prevent conflicting zone definitions. If there are no conflicts, the zone databases are merged. If there are conflicts, the link is isolated and no data traffic can flow through that link until the conflicts are resolved.
  • the zone server protocol whenever a zone is added, deleted or modified, the changes are propagated throughout the Fabric.
  • the Zone Server Protocol is modified to accommodate Inter-VSAN zones having members in different VSANs. Further, existing mechanisms or new mechanisms can be devised to ensure consistency of inter-VSAN zones. Since VSANS are terminated at the border switches, intra-domain zones are not propagated to the Transit VSAN.
  • the FSPF is a link state path selection protocol. FSPF keeps track of the state of the links on all the Switches in the Fabric and associates the cost with each link. The protocol computes paths from each Switch to all the other Switches in the Fabric by adding the cost of all the links traversed by the path, and choosing or selecting the path that minimizes the cost.
  • the collection of the link state records (LSR's) (including the cost) of all the Switches in the Fabric constitutes the topology database of the Fabric, called the Link State Database.
  • the FSPF protocol has four major components, including: (i) a “Hello” protocol used to establish connectivity between neighbor Switches, to establish the identity of neighbor Switches, and to exchange FSPF parameters and capabilities between the neighbor Switches; (ii) a replicated fabric topology or Link State Database, with protocols and mechanisms to keep the databases synchronized across the Fabric; (iii) a path computation algorithm; and (iv) a routing table update.
  • the Link State Database synchronization in turn consists of two major components, an initial database synchronization and an update mechanism.
  • the initial database synchronization is used when a Switch is initialized or when an inter-Switch Link (ISL) comes up.
  • the update mechanism is used when either (i) there is a link state change, for example when an ISL goes up or down; or (ii) on a periodic basis, to prevent Switches from deleting topology information from the database.
  • the term “path selection” indicates the lowest cost or “best” path between a source and destination in the Fabric.
  • the term “routing” indicates the actual forwarding of frames to a specific destination.
  • FSPF performs hop-by-hop routing, which means that a Switch in the Fabric only needs to know the next hop on the best path to the destination.
  • the replicated topology database insures that every Switch in the Fabric has the same definition of the Fabric, and therefore, all the Switches will make consistent routing decisions.
  • a Switch needs to know, for each destination domain in the Fabric, which path should be used to route a frame to a domain.
  • a routing table entry therefore requires at a minimum a destination Domain_ID and an E_Port to which frames are forwarded.
  • a border switch For each Domain_ID of a device that is part of an inter-VSAN zone, a border switch considers the Domain_ID for announcement into the adjacent VSANs.
  • An adjacent VSAN may be a transit VSAN or an edge VSAN.
  • a thus selected Domain ID is announced into an adjacent VSAN if either that VSAN is a transit VSAN or there is a device in the VSAN that is part of the same inter-VSAN zone.
  • a border switch rewrites the VSAN of a frame that is being routed across VSANs to that of the adjacent VSAN. So, for frames being routed from an edge VSAN to a transit VSAN, a border switch rewrites the VSAN from the edge VSAN to the transit VSAN.
  • the SAN 70 includes VSAN 1 , VSAN 2 , a transit VSAN and an inter-fabric zone Z with members pWWN 1 , pWWN 2 and pWWN 4 .
  • Switch C 4 would announce the LSRs of its Link State Database to itself, Switch C 3 , Switch E 3 , and Switch E 4 , where each of the LSRs would contain information about all the links connected to the Switch C 4 .
  • Switch C 4 announces only a route for Switch E 4 with a link cost.
  • Switch E 3 would announce only a-route for E 4 .
  • switches C 1 and C 2 each announce a route for E 2 and E 1 .
  • Switch C 1 and C 2 announce the route for Switch E 4 obtained from the Transit-VSAN into VSAN 1 .
  • Switches C 3 and C 4 announce the route for Switches E 1 and E 2 into VSAN 2 .
  • Switches C 1 and C 2 have to change the VSAN for frames destined to E 4 from VSAN 1 to the Transit VSAN. In the opposite direction, they will change the VSAN for frames received for Switches E 1 and E 2 from the Transit VSAN to VSAN 1 .
  • Switches C 3 and C 4 will change the VSAN for frames destined to El and E 2 from VSAN 2 to the Transit VSAN and change the VSAN for the frames received for Switch E 4 , from the Transit VSAN to VSAN 2 .
  • Name Server Protocol With the Name Server Protocol, each Switch exchanges information regarding its locally attached end devices with the other Switches in the SAN.
  • the information that is exchanged for each end device includes the world wide name (pWWN), the Fibre Channel address (FC_ID), the type of protocol (SCSI, IP, etc.) the end device supports, and if the end device is an initiator (i.e., a Host) or a target (i.e., a storage device).
  • the changes to the name server on a Border Switch are: (i) build the list of name server entries to be exported to a Transit VSAN or Edge VSAN. This list is created from the defined Inter-VSAN zones, and (ii) terminate and proxy name server queries for the domains associated with the remote domain and respond on behalf of the name server of the queried Switch.
  • the modification rules of the Name Server Protocol can be illustrated by way of examples.
  • SW_RCSN Register State Change Notification
  • SW_RSCNs are exchanged between switches whenever the name server database changes. The change is usually due to a change in the state of a locally connected port, a locally connected switch or to the zone server database.
  • SW_RSCNs are originated by the Switch detecting the change and sent to every other Switch in the VSAN.
  • the SW_RSCN contains information about the affected end devices or Domain_ID (Domain_ID is used when changes affect the entire switch as specified in the FC-MI Technical Report, incorporated by reference herein for all purposes. This information includes the port WWN of the end device and its FC_ID.
  • An SW_RSCN can contain notification about multiple end devices.
  • SW_RSCN frames can be prevented by selecting a single Switch to be responsible for distributing SW_RSCN from one VSAN to another.
  • the selection of such a switch can be done in multiple ways, for example, either: (i) statically configured by a system administrator; (ii) selecting the principal Switch in a VSAN to be designated as the Switch for distributing SW_RSCNs; (iii) the border switches can then announce the SW_RSCN from an adjacent VSAN to only the principal switch which then distributes the SW_RSCN within its VSAN or (iv) one of the Border Switches can be selected based on some scheme such as shortest path to the VSAN for which it is advertising, the switch with the highest “switch WWN” etc. Regardless of the responsible Switch, each switch receiving a SW_RSCN notifies registered end hosts of the change as per normal RSCN rules.
  • FIG. 7 presents a scenario where two devices, pWWN 1 and pWWN 2 , need to communicate with a storage device pWWN 3 .
  • the communication between pWWN 2 and pWWN 3 is similar to the other scenarios that have been discussed previously and therefore will not be discussed in detail herein.
  • FIG. 7 illustrates two subcases of this topology, when the two transit VSANs are the same and when they are not the same.
  • an Inter-VSAN zone is defined containing the two devices. There must be one or more links connecting switches S 2 and S 3 that carry the Transit VSAN traffic. If the link between the switches is not direct, all the switches in the path between S 2 and S 3 must carry the transit VSAN.
  • the Switch 80 includes a data plane 82 and a control plane 84 .
  • the Switch includes switching logic 86 connected between two sets of ports 88 a and 88 b .
  • the switching logic is configured to route or internally switch traffic received on one port 88 a to another port 88 b and vice versa.
  • the control plane includes a state machine 90 for implementing the Port Manager; Domain Manager; Zone Server; Fabric Shortest Path First (FSPF); Name_Server; and Register State Change Notification (RSCN) protocols and their modification and changes as described herein.
  • the protocols can be implemented in hardware, programmable logic, in software running on a micro-controller, or a combination thereof.

Abstract

An Fibre Channel Switch which enables end devices in different Fabrics to communicate with one another while retaining their unique Fibre Channel Domain_IDs. The Switch is coupled to a first fabric having a first set of end devices and a second fabric having a second set of end devices. The Switch is configured to enable communication by the first set of end devices associated with the first fabric with the second set of end devices associated with the second set of end devices using the unique Domain_IDs of each of the first set and the second set of end devices. In one embodiment of the invention, the first and second fabrics are first and second Virtual Storage Array Networks (VSANs) respectively. In an alternative embodiment, the first fabric and the second fabric are separate physical fabrics.

Description

    RELATED APPLICATIONS
  • The present invention is a Continuation-in-Part of co-pending, commonly assigned, application Ser. No. 10/034,160 filed Dec. 26, 2001 and entitled “Methods and Apparatus for Encapsulating a Frame for Transmission in a Storage Area Network”, incorporated herein for all purposes.
  • BACKGROUND OF THE INVENTION
  • 1. Field of the Invention
  • The present invention relates to storage area networks, and more particularly, to a Fibre Channel Switch that enables the end devices in different Fabrics to communicate with one another while retaining their unique Fibre Channel IDs.
  • 2. Background of the Invention
  • With the increasing popularity of Internet commerce and network centric computing, businesses and other organizations are becoming more and more reliant on information. To handle all of this data, storage area networks or SANs have become very popular. A SAN typically includes a number of storage devices, a plurality of Hosts, and a number of Switches arranged in a Switching Fabric that connects the storage devices and the Hosts.
  • Most SANs rely on the Fibre Channel protocol for communication within the Fabric. For a detailed explanation of the Fibre Channel protocol and Fibre Channel Switching Fabrics and Services, see the Fibre Channel Framing and Signaling Standard, Rev 1.70, American National Standard of Accredited Standards Committee (NCITS), Feb. 8, 2002, and the Fibre Channel Switch Fabric—2, Rev. 5.4, NCITS, Jun. 26, 2001, and the Fibre Channel Generic Services—3, Rev. 7.01, NCITS, Nov. 28, 2000, all incorporated by reference herein for all purposes.
  • In Fibre Channel, each device (Hosts, storage devices and Switches) is identified by a globally unique, eight (8) byte wide World Wide Name (WWN) assigned by the manufacturer. There are two kinds of WWNs used in FC networks. If you consider a device with one or more FC adapters (or HBAs or ports) to connect to a FC network, every device is assigned a node WWN (nWWN) and each adapter is assigned a port WWN (pWWN). The nWWN and pWWN are different from each other. When the Fibre Channel devices are interconnected to form a SAN, the WWN (along with other parameters) is the primary mechanism to identify each device. Fibre Channel frames are used for communication among the devices in the SAN. The WWN, however, is not used by the frames. Each adapter or port must login to the FC network. At this time, each port is dynamically assigned a unique Fibre Channel address (FC_ID) by the Fabric. The FC_ID is used in FC networks for end devices to address each other.
  • The three byte wide Fibre Channel addresses are hierarchically structured in three fields, each one byte long: Domain_ID, Area_ID, and Port_ID. Each Switch within the Fabric is assigned a Domain_ID. The end devices attached to a particular Switch are assigned the Domain_ID of that Switch. The Switch manages the allocation of the Area_ID and Port_ID fields for each end device to guarantee the uniqueness of the assigned addresses in that Domain. For example, if a Switch is assigned a Domain number five and the Switch subdivides its address space in two areas each having three connected end devices, then a possible Fibre Channel address allocation is: 5:1:1, 5:1:2, 5:1:3, 5:2:1, 5:2:2, and 5:2:3.
  • Fibre Channel based SANs are often organized into zones. Within each zone, Hosts can see and access only storage devices or other Hosts belonging to that zone. This allows the coexistence on the same SAN of different computing environments. For example, it is possible to define on a SAN a Unix zone and a separate Windows zone. Unix servers belonging to the Unix zone may access only storage or Hosts devices within the Unix zone, and do not interfere with the other devices connected to the SAN. In the same manner, Windows servers belonging to the Windows zone may access storage or Hosts devices only within the Windows zone, without interfering with the other devices connected to the SAN. The SAN administrator may define in a SAN multiple zones, as required or dictated by the computing and storage resources connected to it. The Switching Fabric allows communications only between devices belonging to the same zone, preventing a device of one zone from seeing or accessing a device of another zone.
  • The information infrastructure within a large enterprise will typically have a number of SANs, each dedicated for a different organization or application within the enterprise. For example, a large corporation may have different SANs for corporate, for the sales department, the marketing department, etc. Each SAN will typically include redundant Fibre Channel fabrics connecting a plurality of Hosts and storage devices. The redundant Switches in the Fibre Channel fabrics are provided in the event a Switch or link in one Fabric goes down. If this were to occur, the redundant fabric would be used enabling normal operation of SAN. Another example is the use of a dedicated SAN for managing a mail server such as Microsoft Exchange.
  • The aforementioned arrangement has a number of disadvantages. Foremost, the Hosts in a given SAN can communicate only with the storage devices in that same SAN. There is no way that a Host in one SAN can directly communicate with a storage device in a second SAN. This arrangement is not only inefficient, it is expensive. Since storage devices cannot be shared among SANs, separate storage devices are required for each SAN.
  • The above-identified parent application partially addresses this problem by introducing the concept of a Virtual SAN or “VSAN”. The implementation of a VSAN is based on the concept of dividing the switching fabric of a single physical SAN into logical SANs, each called a VSAN. The properties of each VSAN are similar to a standard SAN, in particular: (i) unicast, broadcast and multicast traffic is confined to a VSAN and does not span multiple VSANs; (ii) Fibre Channel identifiers (FC_IDs) are assigned per VSAN. This means that a given FC address may be assigned to two different Hosts in two different VSANs; and (iii) routing and distributed Fabric Services, such as Name Server, Zone Server, etc. are maintained independently for each VSAN. This results in constraining the effect of a configuration or topology change to only the affected VSAN. Within each VSAN, a frame is forwarded as in any normal SAN, using the FC_ID.
  • One known solution for enabling end devices in different VSANs to communicate with one another involves the virtualization of the end devices so that there are “local instances” of each end device in the Fabric within each VSAN. See for example US Patent Publication 2003/0012204. One problem with this approach is that the border Switches between the VSANs perform FC_ID translations (i.e., Network Address translations or NATs) for the source and destination end devices. If a border Switch goes down, an alternative or fail-over path needs to be created. In addition, with certain frames, both the source and/or destination FC_IDs may be defined in the payload. A mechanism that identifies and translates these IDs must therefore be provided. This solution also does not work if encryption or a proprietary protocol is used between the source and destination end devices because there is no way for the border Switches to process the proprietary payloads or de-crypt the frames to identify the source and destination FC_IDs.
  • A Fibre Channel Switch and Fabric is needed which enables end devices in different Fabrics to communicate with one another while retaining their unique Fibre Channel Domain_IDs.
  • SUMMARY OF THE INVENTION
  • To achieve the foregoing, and in accordance with the purpose of the present invention, a Switch is disclosed which enables end devices in different Fabrics to communicate with one another while retaining their unique Fibre Channel Domain_IDs. The Switch is coupled to a first fabric having a first set of end devices and a second fabric having a second set of end devices. The Switch is configured to enable communication by the first set of end devices associated with the first fabric with the second set of end devices associated with the second fabric using the unique Domain_IDs of each of the first set and the second set of end devices. In one embodiment of the invention, the first and second fabrics are first and second Virtual Storage Area Networks (VSANs) respectively. In an alternative embodiment, the first fabric and the second fabric are separate physical fabrics.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is an exemplary Fibre Channel Fabric according to the present invention.
  • FIG. 2 is an exemplary VSAN topology according to the present invention.
  • FIG. 3 is another VSAN topology illustrating VSAN border switches.
  • FIGS. 4A and 4B is an exemplary Fibre Channel frame modified for Inter-VSAN routing according to the present invention.
  • FIG. 5 is an exemplary SAN defining “Inter-VSAN zones” according to the present invention.
  • FIG. 6 is an exemplary VSAN for illustrating the modifications to the FSPF protocol according to the present invention.
  • FIG. 7 is an exemplary VSAN for illustrating the operation of the present invention.
  • FIG. 8 is a block diagram of a Switch used to implement Inter-VSAN routing according to the present invention.
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be obvious, however, to one skilled 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.
  • In a Fibre Channel SAN, the main services provided by the fabric include: Dynamic Address Allocation, Routing, Name Service Zone Service, and event notification. The present invention relates to Inter-VSAN and/or Inter-Fabric routing using unique Domain_IDs. Terminology specific to the present invention and defined herein includes:
      • Inter-VSAN Zone—a zone that contains members from multiple VSANs.
      • VSAN Border Switch—a switch that routes traffic to and from a pair of VSANs.
      • Non-adjacent VSANs—two VSANs are considered non-adjacent on a link if the link does not carry traffic between the two VSANs.
      • Transit VSAN—a VSAN used to carry traffic across a link between two or more non-adjacent Edge VSANs. Transit VSAN(s) thus straddle non-adjacent VSANs and enables them to communicate with one another. With this arrangement, a physical SAN is divided into lower level VSANs and high level Transit VSAN(s) for handling switching between the VSANs.
      • Edge VSAN—is a VSAN from which traffic is switched to or from a Transit VSAN. An Edge VSAN can be a Transit VSAN.
  • Referring to FIG. 1, a simplified Storage Area Network (SAN) 100 according to the present invention is shown. The SAN 100 includes a first VSAN 102 and a second VSAN 104. The first VSAN 102 includes a Switch E2, and an end device pWWN1 with a FC_ID address of 1.1.1. The second VSAN 104 includes a Switch E4 and an end device pWWN4 with a FC_ID address of 2.1.1. A border Switch B1 is also included in each VSAN. VSAN 102 and VSAN 104 are shown with only one Switch and one end device each for the purposes of illustration. It should be understood that the SAN 100 can be divided into many more VSANs, with each VSAN including one or a plurality of Switches and a set of end devices (hosts and/or storage devices where the number in the set may range from one to a multiplicity of end devices.
  • With the present invention, the end devices pWWN1 and pWWN4 can communicate with one another while retaining their respective FC_ID addresses. This is accomplished through the Border Switch B1 that straddles both VSANs. In a single step process, packets originating from end device pWWN1 are injected from VSAN 102 to VSAN 104 and pWWN4, and vice-versa, through the border Switch B1.
  • It should be noted that as used herein, the term “Fabric” generally implies a single physical Fabric that is divided into separate Virtual SANs. The two VSANs 102 and 104 as illustrated in FIG. 1, could also be two physically separate Fabrics or SANs. In either case, the Border Switch enables the end devices pWWN1 and pWWN4 to communicate with one another while retaining their respective FC_ID addresses. For the remainder of the present application, the invention is described in relation to VSANs of a single Fabric or SAN. It should be understood, however, that the present invention as taught herein can be used with two separate Fabrics or SANs.
  • The Inter-VSAN routing using unique Domain_IDs of the present invention initially requires an administrator to define one or more Inter-VSANs and the end devices that can communicate with one another in the Fabric. After the Fabric is configured, the Border Switches: (i) exchange the Inter-VSAN routing protocol (IVRP) messages with the other Border Switches in the fabric in order to determine the topology and shortest paths to the different VSANs. In the absence of a routing protocol, a static configuration is needed to decide the set of VSANs that must be transited by frames from an origination Edge VSAN to a terminating Edge VSAN; (ii) exchange Fabric Shortest Path First (FSPF) information between the neighbor Switches in each VSAN and the neighbor VSANs. Specifically, Border Switches inject routes into either Transit VSANs; and/or Edge VSANs connected to the Border Switch; (iii) propagate FSPF updates between the Edge and Transit VSANs only if the updates affect routes and link cost to any of the exported Domain_IDs; (iv) exchange zoning information with its neighbor Switches on linkup; (v) exchange name server databases with its neighbor Switches. Only those entries in the Inter-VSAN zone relevant to a VSAN are exchanged across VSANs; (vi) proxy as the name server for each switch in a remote Edge VSAN for queries received from Switches in the local VSAN; (vii) translates the VSAN of a frame received from an Edge VSAN to the Transit VSAN for outbound traffic and conversely translates the VSAN of a received frame from the Transit VSAN to the appropriate Edge VSAN; and (viii) terminates all control traffic including FSPF, zone server, and name server in the adjacent Edge VSAN. Each of the functions performed by the Border Switches is defined in more detail below.
  • Referring to FIG. 2, an exemplary SAN according to the present invention is shown. The SAN 10 in this example includes three Edge VSANs (VSAN=1, VSAN=2, and VSAN=3), a Transit VSAN, four switches A, B, C, and D and three end devices, pWWN1, pWWN2 and pWWN3. Host pWWN1 is included in VSAN1. A second Host pWWN2 is included in VSAN2. A storage device pWWN3 is included in VSAN3. The Transit VSAN 12 is used to switch traffic between the disconnected Edge VSAN1, VSAN2, and VSAN3. The Transit VSAN 12, as is described below,enables the Hosts pWWN1 and pWWN2 to access the storage device pWWN3 and vice versa. In Fibre Channel, end devices such as Hosts and storage devices communicate using only Fibre Channel addresses. With the development of the VSAN, as described in detail in the above-identified parent application, a tag qualifies a Fibre Channel address so that it can be routed through the Switching Fabric, while being transparent to the end devices.
  • The Transit VSAN 12 switches traffic from the disconnected Edge VSAN pairs 1-3 and 2-3 and vice-versa. The link between the Switches B and C can be according to various embodiments a standard FC link or remote (e.g., FCIP, FC over DWDM, etc) link. The transit VSAN 12 is similar to any other VSAN and can potentially have its own end devices attached to it. The Transit VSAN 12 does not care about the nature of the neighbor Edge VSANs that it is switching traffic either to or from. In other words, a transit VSAN can switch traffic to or from another transit VSAN.
  • Referring to FIG. 3, another SAN 20 topology illustrating Border Switches is shown. Border Switches are switches that link between or are part of both an Edge VSAN(s) and a Transit VSAN(s). In this example, VSAN1 includes a Host (pWWN1, FC_BD=3.1.1) and Switches S1 through S5. VSAN2 includes a storage device (pWWN2, FC_ID=2.1.1) and Switches S6 through S10. Assuming that a Transit VSAN includes Switches S2, S3, S4, S5, S8 and S10, then S2 and S4 are considered Border Switches even though they are not necessarily at the border of VSAN1. Traffic coming from the Transit VSAN to VSAN 1 is by Switch S3 and traffic from Switch S1 and directed to the Transit VSAN is switched by S4. Similarly, Switches S8 and S10 are Border Switches for VSAN2. In yet another example, Switches B and C are defined as Border Switches in FIG. 2 because they are capable of switching traffic between the Transit VSAN 12 and VSAN1, VSAN2 and VSAN3.
  • Referring to FIG. 4A, a frame 30 having an Extended Inter-Switch Link (EISL) format for use typically on a link carrying multiple VSANs is shown. While the EISL format can also be used on a link carrying a single VSAN, another option on a link carrying only a single VSAN, is to configure the ingress port of the switch with the VSAN to be associated with frames received on that port. The frame 30 includes a Start of Frame (SOF) field 32, an EISL header field 34, an EISL payload field 36, an EISL Cyclical Redundancy Check (CRC) field 38, and a End of Frame (EOF) field 40. The SOF field 32 is the start of the frame delimiter. The EISL payload field 36 includes the header and payload used with a standard ISL frame. The EISL CRC field 306 is used to hold a CRC value specific to the EISL.
  • The EISL CRC value differs or is a modification of a standard CRC value calculated for a regular ISL frame due to the corresponding longer length of the EISL frame 30 with the appended EISL header field 34. The EOF field 40 delineates the end of the frame 30.
  • Referring to FIG. 4B, the EISL header field 34 is illustrated. This field includes a plurality of sub-fields including an EISL indicator field 42 for indicating the presence of an EISL header field 34, an EISL version field 44 that indicates the version of EISL header. In one embodiment, the version field 44 is at least two bits wide, allowing the indication of up to four versions of EISL frames. Additional bits may be used if more versions of EISL frames need to be indicated. The frame type field 46 is used to indicate the type of traffic to be carried by the frame. Traffic types may include for example Ethernet, Fibre Channel, or Infiniband. In one embodiment, the frame type field 46 is four-bits wide, allowing up to sixteen different traffic types to be transmitted across the Fabric. Moreover, multiple VSANs, each capable of transmitting different traffic types, may be interconnected through the identification of a traffic type as provided in this field. The Muli-Protocol Label Switching (MPLS) field 48 indicates if the frame is carrying MPLS information such as label stack 56, which is a common forwarding mechanism for both Fibre Channel and Ethernet. In one embodiment, the MPLS field 48 is one bit wide. When set, it indicates that the EISL header 34 includes an MPLS label stack 56. Otherwise it is reset.
  • Priority field 50 indicate the user priority of the EISL frame 30. Priority may be defined in a number of ways. As one example, the user priority may be a generic numeric priority, without a guaranteed level of service. For instance, higher values represent higher user priority while lower values may represent lower priority. Higher priorities receive available bandwidth first, regardless of how much total bandwidth is available. As another example, the user priority may indicate a quality of service (QoS) of the payload of the EISL frame. Generally, the width of the Priority field 50 depends on the priority type and/or the number of priority levels.
  • The VSAN identifier field 52 or “tag” is used to identify the frame 30 as belonging to a particular VSAN. More particularly, the VSAN identifier field 52 identifies the payload of the EISL frame 30 as belonging to a particular VSAN. In accordance with one embodiment, the VSAN identifier field 412 is a twelve-bit wide 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 SANs, 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. In order to address this problem, a Time To Live (TTL) field 54 may be used to indicate a TTL value specifying the number of remaining hops that can be traversed before the frame is dropped. The TTL value inserted into field 54 is initialized by the network device (e.g., a Switch) that generates the EISL frame 30. A TTL default value is initially set to an arbitrary number, for example sixteen. With each hop, subsequent network devices (e.g., Switches) receiving the EISL frame decrement the TTL value by one. A TTL value of one 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 54 should be ignored, allowing the EISL frame to be forwarded by the switch.
  • On a link carrying multiple VSANs, Switches communicate using frames 30. Each frame 30 also includes, in addition to the above, the Fibre Channel addresses (FC_IDs) of the source and destination end devices. The VSAN ID 52 qualifies a particular frame 30 as belonging to a particular VSAN, transparent to the end devices. For more information on the switching of frames 30 within a VSAN, see the aforementioned parent application.
  • Referring to FIG. 5, a VSAN 60 including “Inter-VSAN zones” according to the present invention is shown. An Inter-VSAN zone is defined as a zone that has members from multiple VSANs. In this example, Inter-VSAN zone X includes Host pWWN1 (FC_ID 1.1.1) in VSAN 1 and storage device pWWN3 (FC-ID 8.1.1) in VSAN 3. Inter-VSAN zone Y includes Host pWWN2 (FC_ID 3.1.1) in VSAN 2 and the same storage device pWWN3 (FC-ID 8.1.1) in VSAN 3. Inter-VSAN zones X and Y have thus been created so that Hosts pWWN1 and pWWN2 can both communicate with storage device pWWN3 respectively.
  • Using the inter-VSAN zone, Border Switches decide: (i) the content of the name server database that is exported into the Transit VSAN from the adjacent Edge VSAN and vice versa; (ii) the set of FSPF domains to export in Link State Update (LSU) messages; (iii) the set of addresses to switch from adjacent Edge VSANs to Transit VSANs and vice versa; (iv) the set of adjacent Edge VSANs to which SW_RSCNs received from a Transit VSAN are propagated; (v) the set of SW_RSCNs received from adjacent Edge VSANs to propagate into the Transit VSAN. In other words, the Inter-VSAN zone is the point from which the import and export data and control traffic occurs. Since zone configuration is a well known concept, the configuration of Inter-VSAN routing via Inter-VSAN zones simplifies management and administration in the Fabric.
  • Similar to a regular zone in a VSAN, Inter-VSAN zones are contained within a zoneset and there is an active zoneset. The Border Switches thus determine the import and export traffic from the Inter-VSAN zones in the active zoneset.
  • In a typical SAN, a number of protocols are implemented when a link is established between two Switches. These include the Port Manager; Domain Manager; Zone Server; Fabric Shortest Path First (FSPF); Name_Server; and Switch Register State Change Notification (SW_RSCN) protocols, as described in the above-referenced NCITS documents. The aforementioned protocols have been modified for Inter-VSAN routing as contemplated with the present invention as described below.
  • Port Manager Protocol: The Port manager protocol negotiates parameters between two Switches and determines if the link is an Inter-Switch Link (ISL) or an Extended Inter-Switch Link (EISL). If the link is EISL, then it means that the link is capable of carrying VSAN frames. Otherwise, the Port Manager protocol operates the same with VSANs as with a regular SAN.
  • Domain Manager Protocol: The Domain Manager Protocol is responsible for the allocation of Domain_IDs and/or Fibre Channel addresses (FC_ID) for each Switch, Host and storage device in the SAN. As noted above, a FC_ID includes three components, a Domain_ID, an Area_ID, and a Port_ID. During initialization, a Principal Switch is selected for the SAN. The Principal Switch is responsible for assigning a Domain_ID for each Switch. Each Switch is then responsible for selecting the Area_ID and Port_ID for each end device connected to that Switch.
  • According to the present invention, the domain number space must be unique across the VSANs that are going to communicate with one another. There are a number of ways in which this uniqueness can be maintained, including: (i) administratively partitioning the domain number space across the VSANs; or (ii) associate a set of Domain_IDs to be used only for biter-VSAN routing. For example, Domain_IDs between 200-239 (or any other arbitrary range) can be dedicated for VSAN routing. A Switch that needed to communicate across VSANs could administratively be configured to request Domain_IDs in the dedicated number space range.
  • Zone Server Protocol: In a standard SAN, the Zone Server Protocol is responsible for creating and maintaining a database within each Switch that defines each zone in the SAN. The zones in the table are defined in terms of the Host(s) and storage device(s) in each zone. A Host and/or storage device can belong to multiple zones. To ensure a consistent zoning database across a SAN, when an ISL link comes up between two switches, the zone database is exchanged between the switches to ensure consistency and to prevent conflicting zone definitions. If there are no conflicts, the zone databases are merged. If there are conflicts, the link is isolated and no data traffic can flow through that link until the conflicts are resolved. As part of the zone server protocol, whenever a zone is added, deleted or modified, the changes are propagated throughout the Fabric.
  • To support Inter-VSAN routing, the Zone Server Protocol is modified to accommodate Inter-VSAN zones having members in different VSANs. Further, existing mechanisms or new mechanisms can be devised to ensure consistency of inter-VSAN zones. Since VSANS are terminated at the border switches, intra-domain zones are not propagated to the Transit VSAN.
  • Fabric Shortest Path First (FSPF) Protocol: The FSPF is a link state path selection protocol. FSPF keeps track of the state of the links on all the Switches in the Fabric and associates the cost with each link. The protocol computes paths from each Switch to all the other Switches in the Fabric by adding the cost of all the links traversed by the path, and choosing or selecting the path that minimizes the cost. The collection of the link state records (LSR's) (including the cost) of all the Switches in the Fabric constitutes the topology database of the Fabric, called the Link State Database.
  • The FSPF protocol has four major components, including: (i) a “Hello” protocol used to establish connectivity between neighbor Switches, to establish the identity of neighbor Switches, and to exchange FSPF parameters and capabilities between the neighbor Switches; (ii) a replicated fabric topology or Link State Database, with protocols and mechanisms to keep the databases synchronized across the Fabric; (iii) a path computation algorithm; and (iv) a routing table update.
  • The Link State Database synchronization in turn consists of two major components, an initial database synchronization and an update mechanism. The initial database synchronization is used when a Switch is initialized or when an inter-Switch Link (ISL) comes up. The update mechanism is used when either (i) there is a link state change, for example when an ISL goes up or down; or (ii) on a periodic basis, to prevent Switches from deleting topology information from the database.
  • With the FSPF protocol, the term “path selection” indicates the lowest cost or “best” path between a source and destination in the Fabric. The term “routing” indicates the actual forwarding of frames to a specific destination. FSPF performs hop-by-hop routing, which means that a Switch in the Fabric only needs to know the next hop on the best path to the destination. The replicated topology database insures that every Switch in the Fabric has the same definition of the Fabric, and therefore, all the Switches will make consistent routing decisions. Typically, a Switch needs to know, for each destination domain in the Fabric, which path should be used to route a frame to a domain. A routing table entry therefore requires at a minimum a destination Domain_ID and an E_Port to which frames are forwarded.
  • Since the FSPF protocol is contained within a VSAN, in order to support routing for domains that are in other VSANs, the following modifications are implemented:
  • For each Domain_ID of a device that is part of an inter-VSAN zone, a border switch considers the Domain_ID for announcement into the adjacent VSANs. An adjacent VSAN may be a transit VSAN or an edge VSAN. A thus selected Domain ID is announced into an adjacent VSAN if either that VSAN is a transit VSAN or there is a device in the VSAN that is part of the same inter-VSAN zone.
  • In addition to this, a border switch rewrites the VSAN of a frame that is being routed across VSANs to that of the adjacent VSAN. So, for frames being routed from an edge VSAN to a transit VSAN, a border switch rewrites the VSAN from the edge VSAN to the transit VSAN.
  • Referring to FIG. 6, an exemplary SAN 70 useful for illustrating the modifications to the FSPF protocol is shown. The SAN 70 includes VSAN1, VSAN2, a transit VSAN and an inter-fabric zone Z with members pWWN1, pWWN2 and pWWN4. With a standard SAN, Switch C4 would announce the LSRs of its Link State Database to itself, Switch C3, Switch E3, and Switch E4, where each of the LSRs would contain information about all the links connected to the Switch C4. With Inter-VSAN routing, Switch C4 announces only a route for Switch E4 with a link cost. Similarly, Switch E3 would announce only a-route for E4. Similarly, switches C1 and C2 each announce a route for E2 and E1. On receiving a route announcement from Switches C3 and C4, Switch C1 and C2 announce the route for Switch E4 obtained from the Transit-VSAN into VSAN 1. Likewise, Switches C3 and C4 announce the route for Switches E1 and E2 into VSAN 2. From the forwarding table perspective, Switches C1 and C2 have to change the VSAN for frames destined to E4 from VSAN1 to the Transit VSAN. In the opposite direction, they will change the VSAN for frames received for Switches E1 and E2 from the Transit VSAN to VSAN1. Similarly, Switches C3 and C4 will change the VSAN for frames destined to El and E2 from VSAN 2 to the Transit VSAN and change the VSAN for the frames received for Switch E4, from the Transit VSAN to VSAN 2.
  • Name Server Protocol: With the Name Server Protocol, each Switch exchanges information regarding its locally attached end devices with the other Switches in the SAN. The information that is exchanged for each end device includes the world wide name (pWWN), the Fibre Channel address (FC_ID), the type of protocol (SCSI, IP, etc.) the end device supports, and if the end device is an initiator (i.e., a Host) or a target (i.e., a storage device).
  • To support Inter-VSAN routing, the changes to the name server on a Border Switch are: (i) build the list of name server entries to be exported to a Transit VSAN or Edge VSAN. This list is created from the defined Inter-VSAN zones, and (ii) terminate and proxy name server queries for the domains associated with the remote domain and respond on behalf of the name server of the queried Switch.
  • Referring again to FIG. 6, the modification rules of the Name Server Protocol can be illustrated by way of examples.
      • 1) Switches C1 and C2 add to the Name Server database in the Transit VSAN the devices pWWN1 and pWWN2. Similarly, Switches C3 and C4 add pWWN4 to the Name Server database in the transit VSAN. When C4 announces the route to domain E3 in the transit VSAN and C1 and C2 receive this announcement, each of them send a name server query for information about all attached end devices to E3 to the name server of E3 as specified by the FC standards. Depending on the route taken by the query, either C3 or C4 intercept this query and respond on behalf of E3 with information only about pWWN4. Likewise, when C1 and C2 announce the route to domains E1 and E2, it is received by C3 and C4. C3 and C4 then send name server queries to E1 and E2 which are intercepted by C1 or C2 which proxy and respond on behalf of the name server for the announced domains. C1 and C2 respond only with information about pWWN1 for queries to E1 and with pWWN2 for queries to E2.
      • 2) A similar process occurs in VSAN 1 when the route to domain E4 is announced by C1 and C2. Each switch in VSAN 1, in this case, E1 and E2, send name server queries for all attached end devices to E4 to the name server of E4. Depending on the route taken by the query, either C1 or C2 intercept the query and respond with information only about pWWN4.
      • 3) A similar process as above occurs in VSAN 2 when C3 and C4 announce routes to domains E1 and E2.
      • 4) If a device is added to an already announced domain or if the state of the device announced changes, notification of a change is conveyed via SW_RSCN. When a switch receives an SW_RSCN, it generates a name server query to the switch to which the end device identified in the SW_RSCN is attached. This query is also intercepted and responded to by the border switches.
    Register State Change Notification (SW_RCSN) Protocol
  • SW_RSCNs are exchanged between switches whenever the name server database changes. The change is usually due to a change in the state of a locally connected port, a locally connected switch or to the zone server database. SW_RSCNs are originated by the Switch detecting the change and sent to every other Switch in the VSAN. The SW_RSCN contains information about the affected end devices or Domain_ID (Domain_ID is used when changes affect the entire switch as specified in the FC-MI Technical Report, incorporated by reference herein for all purposes. This information includes the port WWN of the end device and its FC_ID. An SW_RSCN can contain notification about multiple end devices.
  • With Inter-VSAN routing, changes in one VSAN must be propagated to other VSANs if the change affects a device in an Inter-VSAN zone. Consider the topology in FIG. 6. If switch E4 loses the connection to pWWN4, it transmits an SW-RSCN to C3 and C4. Since pWWN4 is in a Inter-VSAN zone and C3 and C4 are Border Switches, they both will propagate the SW_RSCN to the Transit VSAN. This is received by both C1 and C2 which in turn propagate the SW_RSCN in VSAN 1. Thus, duplicate SW_RSCNs are generated which is inefficient.
  • The replication of SW_RSCN frames can be prevented by selecting a single Switch to be responsible for distributing SW_RSCN from one VSAN to another. The selection of such a switch can be done in multiple ways, for example, either: (i) statically configured by a system administrator; (ii) selecting the principal Switch in a VSAN to be designated as the Switch for distributing SW_RSCNs; (iii) the border switches can then announce the SW_RSCN from an adjacent VSAN to only the principal switch which then distributes the SW_RSCN within its VSAN or (iv) one of the Border Switches can be selected based on some scheme such as shortest path to the VSAN for which it is advertising, the switch with the highest “switch WWN” etc. Regardless of the responsible Switch, each switch receiving a SW_RSCN notifies registered end hosts of the change as per normal RSCN rules.
  • EXAMPLES
  • FIG. 7 presents a scenario where two devices, pWWN1 and pWWN2, need to communicate with a storage device pWWN3. The communication between pWWN2 and pWWN3 is similar to the other scenarios that have been discussed previously and therefore will not be discussed in detail herein. However, consider the case of pWWN1 communicating with pWWN3 where there is not a direct connection between the Border Switches of VSAN 2 and VSAN 3. FIG. 7 illustrates two subcases of this topology, when the two transit VSANs are the same and when they are not the same.
  • When the transits VSANs are the same, in order to have pWWN1 communicate with pWWN3, an Inter-VSAN zone is defined containing the two devices. There must be one or more links connecting switches S2 and S3 that carry the Transit VSAN traffic. If the link between the switches is not direct, all the switches in the path between S2 and S3 must carry the transit VSAN.
  • When the transit VSANs are not the same, the Inter-VSAN zones must be defined such that frames can be switched from one Transit VSAN to the other. In FIG. 7, a route to the switch associated with PWWN1 is announced in the transit VSAN by S1. S2 on hearing this route announcement as specified above, announces it in VSAN 1. In VSAN 1, when S3 hears this announcement, it propagates the route announcement to Transit VSAN V2, where S4 then announces in VSAN 3. Now a path has been established between the switches connected to end devices PWWN1 and PWWN3 and so communication can take place. Along with route announcements, name server query proxying and SW_RSCN propagation as specified above also occurs.
  • Referring to FIG. 8, a block diagram of a Switch that can be used for Inter-VSAN routing in a SAN according to the present invention is shown. The Switch 80 includes a data plane 82 and a control plane 84. In the data plane 82, the Switch includes switching logic 86 connected between two sets of ports 88 a and 88 b. The switching logic is configured to route or internally switch traffic received on one port 88 a to another port 88 b and vice versa. The control plane includes a state machine 90 for implementing the Port Manager; Domain Manager; Zone Server; Fabric Shortest Path First (FSPF); Name_Server; and Register State Change Notification (RSCN) protocols and their modification and changes as described herein. In alternative embodiments, the protocols can be implemented in hardware, programmable logic, in software running on a micro-controller, or a combination thereof.
  • The embodiments of the present invention described above are to be considered as illustrative and not restrictive. The various change commands described herein are only exemplary and any other types of commands may be used. 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 (29)

1. An apparatus, comprising:
a Switch configured to couple a first fabric having a first set of end devices and a second fabric having a second set of end devices, each of the first set of end devices and the second set of end devices having a unique Domain_ID address respectively, the Switch configured to enable communication between the first set of end devices in the first fabric with the second set of end devices associated with the second fabric while maintaining the unique Domain ID addresses of the first set of end devices and the second set of end devices.
2. The apparatus of claim 1, wherein the first and second fabrics are first and second Virtual Storage Area Networks (VSANs) respectively.
3. The apparatus of claim 1, wherein the first fabric and the second fabric are separate physical fabrics.
4. The apparatus of claim 1, wherein the Switch is a Border Switch that is part of both the first fabric and the second fabric, the Border Switch configured to inject frames of information between the first fabric and the second fabric to enable communication between members of the first set of end devices and the second set of end devices.
5. The apparatus of claim 1, wherein the first fabric and the second fabric are Edge fabrics and further comprising a Transit fabric configured to carry traffic between the first fabric and the second fabric.
6. The apparatus of claim 1, wherein the first fabric and the second fabric are adjacent to each other and the Switch is configured to directly switch traffic between end devices in the first and second fabrics.
7. The apparatus of claim 4, wherein the Border Switch is configured within an Inter-VSAN zone, the Inter-VSAN zone including members from the first set of end devices associated with the first fabric and the second set of end devices associated with the second fabric.
8. The apparatus of claim 7, wherein the Border Switch determines via the Inter-VSAN zone:
(i) the content of a name server database that is exported from one of the adjacent fabrics to the other and vice versa;
(ii) the set of FSPF domains to export in Link State Update (LSU) messages;
(iii) the set of addresses to switch from one of the adjacent fabrics to the other and vice versa; and
(iv) the set of adjacent fabrics to which SW_RSCNs received from a fabric are propagated and vice-versa.
9. The apparatus of claim 4, wherein the Border Switch is further configured to perform one or more of the following:
(i) exchange Inter-VSAN routing protocol (IVRP) messages with other Border Switches in the first fabric and second fabric;
(ii) exchange Fabric Shortest Path First (FSPF) information between neighboring Switches in each fabric
(iii) propagate FSPF updates across the fabrics only if the updates affect routes and link cost to any of the exported Domain_IDs;
(iv) proxies as the name server in a first fabric for each Switch in the second fabric that is exported into the first fabric and vice-versa;
(v) rewrite the VSAN of a frame received from the first VSAN to the second VSAN if traffic is destined to the second VSAN; and
(vi) constrain control traffic including FSPF, zone server, and name server within a single fabric.
10. The apparatus of claim 7, wherein the Border Switch in the Inter-VSAN zone supports the definition and exchange of Inter-VSAN zones.
11. The apparatus of claim 7, wherein the name server database in the Border Switch is configured to perform one or more of the following:
(i) build the list of name server entries to be exported from a first fabric to the second fabric and vice-versa; and
(ii) proxy as the name server in a first fabric for each Switch in the second fabric that is exported into the first fabric and vice-versa.
12. The apparatus of claim 11, wherein the Border Switch is further configured to generate Switch Register State Change Notifications (SW_RCSNs) across the fabrics when the name server database changes.
13. The apparatus of claim 12, wherein the Border Switch is further configured to prevent the replication of RCSNs in one of the following ways:
(i) selecting a first Switch and a second Switch in the first or second fabric for distributing RCSNs in each fabric respectively;
(ii) statically configuring the fabrics; or
(iii) selecting a specified Switch to distribute the RCSNs.
14. The apparatus of claim 1, wherein tile Switch enables communication between the end devices in the first fabric and the second fabric while maintaining the unique Domain_IDs of each of the first set and the second set of end devices by:
(i) administratively partitioning the domain number space across the fabrics;
or (ii) associating a range of Domain_IDs to be used only for Inter-VSAN routing.
15. An apparatus, comprising:
a first fabric;
a second fabric;
a first set of end devices associated with the first fabric and a second set of end devices associated with the second fabric, the first set and the second set of end devices each having a unique Domain ID address respectively; and
a communication mechanism configured to enable the first set of end devices associated with the first fabric to communicate with the second set of end devices associated with the second fabric while maintaining the unique Domain ID addresses of the first set of end devices and the second set of end devices.
16. The apparatus of claim 15, wherein the communication mechanism is a Switch configured to couple the first fabric and the second fabric, the Switch configured to enable communication between the first set of end devices in the first fabric with the second set of end devices associated with the second fabric while maintaining the unique Domain ID addresses of the first set of end devices and the second set of end devices.
17. The apparatus of claim 15, wherein the first and second fabrics are first and second Virtual Storage Area Networks (VSANs) respectively.
18. The apparatus of claim 15, wherein the first fabric and the second fabric are separate physical fabrics.
19. The apparatus of claim 16, wherein the Switch is a Border Switch that is part of both the first fabric and the second fabric, the Border Switch configured to inject frames of information between the first fabric and the second fabric to enable communication between members of the first set of end devices and the second set of end devices.
20. The apparatus of claim 15, wherein the first fabric and the second fabric are Edge fabrics and further comprising a Transit fabric configured to carry traffic between the first fabric and the second fabric.
21. The apparatus of claim 16, wherein the first fabric and the second fabric are adjacent to each other and the Switch is configured to directly switch traffic between end devices in the first and second fabrics.
22. The apparatus of claim 19, wherein the Border Switch is configured within an Inter-VSAN zone, the Inter-VSAN zone including members from the first set of end devices associated with the first fabric and the second set of end devices associated with the second fabric.
23. The apparatus of claim 22, wherein the Border Switch determines via the Inter-VSAN zone:
(i) the content of a name server database that is exported from one of the adjacent fabrics to the other and vice versa;
(ii) the set of FSPF domains to export in Link State Update (LSU) messages;
(iii) the set of addresses to switch from one of the adjacent fabrics to the other and vice versa; and
(iv) the set of adjacent fabrics to which SW_RSCNs received from a fabric are propagated and vice-versa.
24. The apparatus of claim 19, wherein the Border Switch is further configured to perform one or more of the following:
(i) exchange Inter-VSAN routing protocol (IVRP) messages with other Border Switches in the first fabric and second fabric;
(ii) exchange Fabric Shortest Path First (FSPF) information between neighboring Switches in each fabric;
(iii) propagate FSPF updates across the fabrics only if the updates affect routes and link cost to any of the exported Domain_IDs;
(iv) proxies as the name server in a first fabric for each Switch in the second fabric that is exported into the first fabric and vice-versa;
(v) rewrite the VSAN of a frame received from the first VSAN to the second VSAN if traffic is destined to the second VSAN; and
(vi) constrain control traffic including FSPF, zone server, and name server within a single fabric.
25. The apparatus of claim 23, wherein the Border Switch in the Inter-VSAN zone supports the definition and exchange of Inter-VSAN zones.
26. The apparatus of claim 7, wherein the name server database in the Border Switch is configured to perform one or more of the following:
(i) build the list of name server entries to be exported from a first fabric to the second fabric and vice-versa; and
(ii) proxy as the name server in a first fabric for each Switch in the second fabric that is exported into the first fabric and vice-versa.
27. The apparatus of claim 26, wherein the Border Switch is further configured to generate Switch Register State Change Notifications (SW_RCSNs) across the fabrics when the name server database changes.
28. The apparatus of claim 27, wherein the Border Switch is further configured to prevent the replication of RCSNs in one of the following ways:
(i) selecting a first Switch and a second Switch in the first or second fabric for distributing RCSNs in each fabric respectively;
(ii) statically configuring the fabrics; or
(iii) selecting a specified Switch to distribute the RCSNs.
29. The apparatus of claim 16, wherein the Switch enables communication between the end devices in the first fabric and the second fabric while maintaining the unique Domain_IDs of each of the first set and the second set of end devices by:
(i) administratively partitioning the domain number space across the fabrics;
or (ii) associating a range of Domain_IDs to be used only for Inter-VSAN routing.
US10/791,143 2001-12-26 2004-03-01 Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain_IDs Abandoned US20050025075A1 (en)

Priority Applications (11)

Application Number Priority Date Filing Date Title
US10/609,442 US7499410B2 (en) 2001-12-26 2003-06-26 Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain—IDs
US10/791,143 US20050025075A1 (en) 2001-12-26 2004-03-01 Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain_IDs
EP04756162.6A EP1636946B1 (en) 2003-06-26 2004-06-25 Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain-ids
CN2010101414913A CN101795298B (en) 2003-06-26 2004-06-25 Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain IDs
AU2004300680A AU2004300680B2 (en) 2003-06-26 2004-06-25 Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain_IDs
CN2004800108260A CN1778076B (en) 2003-06-26 2004-06-25 Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain-ID
CA2521463A CA2521463C (en) 2003-06-26 2004-06-25 A fibre channel switch that enables end devices in differenet fabrics to communicate with one another while retaining their unique fibre channel domain ids
EP18176090.1A EP3389229A1 (en) 2003-06-26 2004-06-25 Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain_ids
PCT/US2004/020518 WO2005004408A1 (en) 2003-06-26 2004-06-25 Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain_ids
US12/343,843 US7876711B2 (en) 2003-06-26 2008-12-24 Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain—IDs
US12/975,072 US8625460B2 (en) 2003-06-26 2010-12-21 Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain—IDs

Applications Claiming Priority (2)

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/791,143 US20050025075A1 (en) 2001-12-26 2004-03-01 Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain_IDs

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/034,160 Continuation-In-Part US7599360B2 (en) 2001-12-26 2001-12-26 Methods and apparatus for encapsulating a frame for transmission in a storage area network

Publications (1)

Publication Number Publication Date
US20050025075A1 true US20050025075A1 (en) 2005-02-03

Family

ID=21874674

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/034,160 Active 2024-08-23 US7599360B2 (en) 2001-12-26 2001-12-26 Methods and apparatus for encapsulating a frame for transmission in a storage area network
US10/791,143 Abandoned US20050025075A1 (en) 2001-12-26 2004-03-01 Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain_IDs

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/034,160 Active 2024-08-23 US7599360B2 (en) 2001-12-26 2001-12-26 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)

Cited By (58)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050198523A1 (en) * 2004-01-29 2005-09-08 Brocade Communications Systems, Inc. Isolation switch for fibre channel fabrics in storage area networks
US20060023751A1 (en) * 2004-07-30 2006-02-02 Wilson Steven L Multifabric global header
US20060023726A1 (en) * 2004-07-30 2006-02-02 Chung Daniel J Y Multifabric zone device import and export
US20060023708A1 (en) * 2004-07-30 2006-02-02 Snively Robert N Interfabric routing header for use with a backbone fabric
US20060023707A1 (en) * 2004-07-30 2006-02-02 Makishima Dennis H System and method for providing proxy and translation domains in a fibre channel router
US20060034302A1 (en) * 2004-07-19 2006-02-16 David Peterson Inter-fabric routing
US20070058619A1 (en) * 2005-08-19 2007-03-15 Gopal Gowda Manjunath A 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
US20070091903A1 (en) * 2005-10-25 2007-04-26 Brocade Communications Systems, Inc. Interface switch for use with fibre channel fabrics in storage area networks
US20070140236A1 (en) * 2005-12-21 2007-06-21 Cisco Technology, Inc. Fibre channel traffic redirect scheme using FC NAT ACLs
US20070266132A1 (en) * 2006-05-15 2007-11-15 Cisco Technology, Inc. Method and System for Providing Distributed Allowed Domains in a Data Network
US20070263532A1 (en) * 2006-05-10 2007-11-15 Sina Mirtorabi Backup path convergence in the APS environment
US20080013557A1 (en) * 2006-06-12 2008-01-17 Eduard Siemens 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
US20080316942A1 (en) * 2002-11-27 2008-12-25 Cisco Technology, Inc. Methods and devices for exchanging peer parameters between network devices
US7483387B2 (en) 2005-05-23 2009-01-27 Cisco Technology, Inc. Hierarchical label distribution for inter-area summarization of edge-device addresses
US20090052346A1 (en) * 2007-08-21 2009-02-26 Ibm 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
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
US20090052345A1 (en) * 2007-08-21 2009-02-26 Ibm Corporation Method and Apparatus for an Adapter in a Network Device to Discover its Adapter Name in a Network System
US7533175B1 (en) * 2003-10-24 2009-05-12 Network Appliance, Inc. Network address resolution and forwarding TCP/IP packets over a fibre channel network
US7644179B1 (en) * 2005-12-01 2010-01-05 Cisco Technology, Inc. Inter-VSAN routing with NAT
US20100017497A1 (en) * 2008-07-15 2010-01-21 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
US20100103954A1 (en) * 2008-10-27 2010-04-29 Cisco Technology, Inc. Multiple Infiniband Ports Within A Higher Data Rate Port Using Multiplexing
US20100115206A1 (en) * 2008-11-04 2010-05-06 Gridlron Systems, Inc. Storage device prefetch system using directed graph clusters
US20100115211A1 (en) * 2008-11-04 2010-05-06 Gridlron Systems, Inc. Behavioral monitoring of storage access patterns
US20100125857A1 (en) * 2008-11-17 2010-05-20 Gridlron Systems, Inc. Cluster control protocol
US7734808B1 (en) 2001-12-18 2010-06-08 Cisco Technology, Inc. End-to-end congestion control in a Fibre Channel network
US7742484B2 (en) 2004-07-30 2010-06-22 Brocade Communications Systems, Inc. Multifabric communication using a backbone fabric
US20100258432A1 (en) * 2007-12-26 2010-10-14 Canon Anelva Corporation Sputtering apparatus, sputter deposition method, and analysis apparatus
US20100306610A1 (en) * 2008-03-31 2010-12-02 Masahiro Komatsu Concealment processing device, concealment processing method, and concealment processing program
US7984253B1 (en) 2004-03-26 2011-07-19 Emc Corporation Architecture for virtualization of networked storage resources
US7992038B1 (en) 2004-03-26 2011-08-02 Emc Corporation Failure protection in an environment including virtualization of networked storage resources
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
US20120110385A1 (en) * 2010-10-29 2012-05-03 International Business Machines Corporation Multiple functionality in a virtual storage area network device
US8285961B2 (en) 2008-11-13 2012-10-09 Grid Iron Systems, Inc. Dynamic performance virtualization for disk access
US8402198B1 (en) 2009-06-03 2013-03-19 Violin Memory, Inc. Mapping engine for a storage device
US8402246B1 (en) 2009-08-28 2013-03-19 Violin Memory, Inc. Alignment adjustment in a tiered storage system
US8417871B1 (en) 2009-04-17 2013-04-09 Violin Memory Inc. System for increasing storage media performance
US8417895B1 (en) 2008-09-30 2013-04-09 Violin Memory Inc. System for maintaining coherency during offline changes to storage media
US8443150B1 (en) 2008-11-04 2013-05-14 Violin Memory Inc. Efficient reloading of data into cache resource
US8442059B1 (en) * 2008-09-30 2013-05-14 Gridiron Systems, Inc. Storage proxy with virtual ports configuration
US8627005B1 (en) 2004-03-26 2014-01-07 Emc Corporation System and method for virtualization of networked storage resources
US8635416B1 (en) 2011-03-02 2014-01-21 Violin Memory Inc. Apparatus, method and system for using shadow drives for alternative drive commands
US8635375B2 (en) 2010-04-14 2014-01-21 Brocade Communications Systems, Inc. Remote F—ports
US8667366B1 (en) 2009-04-17 2014-03-04 Violin Memory, Inc. Efficient use of physical address space for data overflow and validation
US8713252B1 (en) 2009-05-06 2014-04-29 Violin Memory, Inc. Transactional consistency scheme
US8775741B1 (en) 2009-01-13 2014-07-08 Violin Memory Inc. Using temporal access patterns for determining prefetch suitability
US8782245B1 (en) 2000-06-30 2014-07-15 Emc Corporation System and method for managing provisioning of storage resources in a network with virtualization of resources in such a network
US8788758B1 (en) 2008-11-04 2014-07-22 Violin Memory Inc Least profitability used caching scheme
US8832384B1 (en) 2010-07-29 2014-09-09 Violin Memory, Inc. Reassembling abstracted memory accesses for prefetching
US8959288B1 (en) 2010-07-29 2015-02-17 Violin Memory, Inc. Identifying invalid cache data
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
US9069676B2 (en) 2009-06-03 2015-06-30 Violin Memory, Inc. Mapping engine for a storage device
US9172556B2 (en) 2003-01-31 2015-10-27 Brocade Communications Systems, Inc. Method and apparatus for routing between fibre channel fabrics
US9350653B2 (en) 2002-04-01 2016-05-24 Cisco Technology, Inc. Label switching in fibre channel networks
US10628042B2 (en) 2016-01-27 2020-04-21 Bios Corporation Control device for connecting a host to a storage device
US20200169604A1 (en) * 2016-04-29 2020-05-28 Hewlett Packard Enterprise Development Lp Target driven peer-zoning synchronization
US11159612B1 (en) 2020-04-28 2021-10-26 Hewlett Packard Enterprise Development Lp Determining non-TDP zones in a storage area network
WO2022102544A1 (en) 2020-11-13 2022-05-19 日本たばこ産業株式会社 Cembratrienediol-containing tobacco extract and production method therefor

Families Citing this family (166)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7061939B1 (en) * 2001-06-13 2006-06-13 Juniper Networs, Inc. Source synchronous link with clock recovery and bit skew alignment
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
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
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
US7529243B2 (en) * 2002-07-16 2009-05-05 Enterasys Networks, Inc. Apparatus and method for a virtual hierarchical local area network
US7397768B1 (en) 2002-09-11 2008-07-08 Qlogic, Corporation Zone management in a multi-module fibre channel switch
US7649880B2 (en) 2002-11-12 2010-01-19 Mark Adams Systems and methods for deriving storage area commands
US7170890B2 (en) * 2002-12-16 2007-01-30 Zetera Corporation Electrical devices with improved communication
US7742473B2 (en) * 2002-11-12 2010-06-22 Mark Adams Accelerator module
US8005918B2 (en) 2002-11-12 2011-08-23 Rateze Remote Mgmt. L.L.C. Data storage devices having IP capable partitions
AU2002361716A1 (en) * 2002-11-12 2004-06-03 Zetera Corporation Data storage devices having ip capable partitions
US7346058B1 (en) * 2002-11-27 2008-03-18 Cisco Technology, Inc. Multiprotocol encapsulation system and method
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
US7424533B1 (en) * 2003-05-23 2008-09-09 Cisco Technology, Inc. Method and apparatus for role-based access control
US7646767B2 (en) 2003-07-21 2010-01-12 Qlogic, Corporation Method and system for programmable data dependant network routing
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
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
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
US7474666B2 (en) * 2003-09-03 2009-01-06 Cisco Technology, Inc. Switch port analyzers
US8165136B1 (en) * 2003-09-03 2012-04-24 Cisco Technology, Inc. Virtual port based SPAN
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
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
EP1691520A4 (en) * 2003-12-03 2006-12-06 Huawei Tech 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
US8782654B2 (en) 2004-03-13 2014-07-15 Adaptive Computing Enterprises, Inc. Co-allocating a reservation spanning different compute resources types
US7325075B1 (en) 2004-03-15 2008-01-29 Hewlett-Packard Development Company, L.P. Methods for address and name discovery for Ethernet entities
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
US7930377B2 (en) 2004-04-23 2011-04-19 Qlogic, Corporation Method and system for using boot servers in networks
US7340167B2 (en) * 2004-04-23 2008-03-04 Qlogic, Corporation Fibre channel transparent switch for mixed switch fabrics
US20070266388A1 (en) 2004-06-18 2007-11-15 Cluster Resources, Inc. System and method for providing advanced reservations in a compute environment
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
US8271980B2 (en) 2004-11-08 2012-09-18 Adaptive Computing Enterprises, 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
EP3203374B1 (en) 2005-04-07 2021-11-24 III Holdings 12, LLC On-demand access to compute resources
US7620981B2 (en) * 2005-05-26 2009-11-17 Charles William Frank Virtual devices and virtual bus tunnels, modules and methods
US7843962B2 (en) * 2005-07-17 2010-11-30 Obsidian Research Corporation 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
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
EP1952254A4 (en) * 2005-10-17 2011-06-22 Alebra Technologies Inc Method, process and system for sharing data in a heterogeneous storage network
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
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
EP1860033B1 (en) * 2006-05-26 2011-01-12 MTC - Macchine Trasformazione Carta Srl Banding machine for logs of sheet material
CN101529814B (en) * 2006-06-12 2012-08-01 北方电讯网络有限公司 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
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
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
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
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
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
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
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
US7908403B2 (en) 2008-02-14 2011-03-15 International Business Machines Corporation Reserved device access contention reduction
US7899944B2 (en) 2008-02-14 2011-03-01 International Business Machines Corporation Open exchange limiting in an I/O processing system
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
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
US9052837B2 (en) 2008-02-14 2015-06-09 International Business Machines Corporation Processing communication data in a ships passing condition
US8108570B2 (en) 2008-02-14 2012-01-31 International Business Machines Corporation Determining the state of an I/O operation
US8082481B2 (en) 2008-02-14 2011-12-20 International Business Machines Corporation Multiple CRC insertion in an output data stream
US8001298B2 (en) * 2008-02-14 2011-08-16 International Business Machines Corporation Providing extended measurement data 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
US8312189B2 (en) 2008-02-14 2012-11-13 International Business Machines Corporation Processing of data to monitor input/output operations
US7941570B2 (en) 2008-02-14 2011-05-10 International Business Machines Corporation Bi-directional data transfer within a single I/O operation
US8196149B2 (en) 2008-02-14 2012-06-05 International Business Machines Corporation Processing of data to determine compatability in an input/output processing system
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
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
US8055807B2 (en) 2008-07-31 2011-11-08 International Business Machines Corporation Transport control channel program chain linking including determining sequence order
US7904606B2 (en) 2008-07-31 2011-03-08 International Business Machines Corporation Transport control channel program chain linked branching
US7937504B2 (en) 2008-07-31 2011-05-03 International Business Machines Corporation Transport control channel program message pairing
US8218571B2 (en) * 2008-10-24 2012-07-10 International Business Machines Corporation Fibre channel framing and signaling optional header for ethernet fabric configuration information
CN101459611B (en) * 2008-12-23 2011-07-06 杭州华三通信技术有限公司 Data transmission scheduling method, system and device for IP SAN storage
JP5332854B2 (en) * 2009-04-20 2013-11-06 ソニー株式会社 Wireless transmitter, wireless transmission method, wireless receiver, and wireless reception method
US9973446B2 (en) 2009-08-20 2018-05-15 Oracle International Corporation Remote shared server peripherals over an Ethernet network for resource virtualization
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
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
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
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
US9077654B2 (en) 2009-10-30 2015-07-07 Iii Holdings 2, Llc System and method for data center security enhancements leveraging managed server SOCs
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
US20130107444A1 (en) 2011-10-28 2013-05-02 Calxeda, Inc. System and method for flexible storage and networking provisioning in large scalable processor installations
US9648102B1 (en) 2012-12-27 2017-05-09 Iii Holdings 2, Llc Memcached server functionality in a cluster of data processing nodes
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
US11720290B2 (en) 2009-10-30 2023-08-08 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
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
US8514856B1 (en) 2010-06-24 2013-08-20 Cisco Technology, Inc. End-to-end fibre channel over ethernet
CN102457435B (en) * 2010-10-27 2015-02-25 杭州华三通信技术有限公司 Message transmission method in FC (Fiber Channel) network as well as FC system and FC equipment
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
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
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
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
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
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
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
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

Citations (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5740171A (en) * 1996-03-28 1998-04-14 Cisco Systems, Inc. Address translation mechanism for a high-performance network switch
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
US5809285A (en) * 1995-12-21 1998-09-15 Compaq Computer Corporation Computer system having a virtual drive array controller
US5999930A (en) * 1996-08-02 1999-12-07 Hewlett-Packard Company Method and apparatus for distributed control of a shared storage volume
US6101497A (en) * 1996-05-31 2000-08-08 Emc Corporation Method and apparatus for independent and simultaneous access to a common data set
US6188694B1 (en) * 1997-12-23 2001-02-13 Cisco Technology, Inc. Shared spanning tree protocol
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
US6205488B1 (en) * 1998-11-13 2001-03-20 Nortel Networks Limited Internet protocol virtual private network realization using multi-protocol label switching tunnels
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
US6208649B1 (en) * 1998-03-11 2001-03-27 Cisco Technology, Inc. Derived VLAN mapping technique
US6219699B1 (en) * 1996-01-02 2001-04-17 Cisco Technologies, Inc. Multiple VLAN Architecture system
US6226771B1 (en) * 1998-12-14 2001-05-01 Cisco Technology, Inc. Method and apparatus for generating error detection data for encapsulated frames
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
US6266705B1 (en) * 1998-09-29 2001-07-24 Cisco Systems, Inc. Look up mechanism and associated hash table for a network switch
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
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
US6295575B1 (en) * 1998-06-29 2001-09-25 Emc Corporation Configuring vectors of logical storage units for data storage partitioning and sharing
US20010049739A1 (en) * 2000-06-02 2001-12-06 Koji Wakayama Apparatus and method for interworking between MPLS network and non-MPLS network
US20020110125A1 (en) * 1998-10-23 2002-08-15 David Banks Method and system for creating and implementing zones in hardware within a fibre channel system
US20020176434A1 (en) * 2001-04-18 2002-11-28 Brocade Communications Systems, Inc. Fibre channel zoning by logical unit number in hardware
US20030012204A1 (en) * 2001-07-11 2003-01-16 Sancastle Technologies, Ltd Extension of fibre channel addressing
US20030118053A1 (en) * 2001-12-26 2003-06-26 Andiamo Systems, Inc. Methods and apparatus for encapsulating a frame for transmission in a storage area network

Family Cites Families (97)

* Cited by examiner, † Cited by third party
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
US5959990A (en) * 1996-03-12 1999-09-28 Bay Networks, Inc. VLAN frame format
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
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
US5879112A (en) * 1997-10-30 1999-03-09 Ivey; Roy M. Water supply line tapping tool
US6032194A (en) 1997-12-24 2000-02-29 Cisco Technology, Inc. Method and apparatus for rapidly reconfiguring computer networks
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
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
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
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
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
CA2371026C (en) 1999-05-11 2007-11-06 British Telecommunications Public Limited Company A node and method for processing high priority transit packets in an 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
WO2001082971A2 (en) 2000-05-02 2001-11-08 Theravance, Inc. Cyclodextrin containing glycopeptide antibiotic compositions
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
EP1162795A3 (en) 2000-06-09 2007-12-26 Broadcom Corporation Gigabit switch supporting improved layer 3 switching
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
US6604407B2 (en) 2001-04-03 2003-08-12 Denso Corporation Leak check apparatus for fuel vapor purge system
US6947379B1 (en) 2001-04-03 2005-09-20 Cisco Technology, Inc. Packet routing to reduce susceptibility to disturbances
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
US20020156924A1 (en) 2001-04-23 2002-10-24 Moshe Czeiger Method for communicating between fibre channel systems
US6993023B2 (en) 2001-04-27 2006-01-31 The Boeing Company Parallel analysis of incoming data transmissions
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
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
US7221652B1 (en) 2001-12-14 2007-05-22 Applied Micro Circuits Corporation System and method for tolerating data link faults in communications with a switch fabric
US6920154B1 (en) 2001-12-17 2005-07-19 Supergate Technology Usa, Inc. Architectures for a modularized data optimization engine and methods therefor
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
WO2003063009A1 (en) 2002-01-18 2003-07-31 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
US7161935B2 (en) 2002-01-31 2007-01-09 Brocade Communications Stystems, Inc. Network fabric management via adjunct processor inter-fabric service link
US7873984B2 (en) 2002-01-31 2011-01-18 Brocade Communications Systems, Inc. Network security through configuration servers in the fabric environment
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
EP1573454A2 (en) 2002-06-11 2005-09-14 Ashish Pandya High performance ip processor for tcp/ip, rdma and ip storage applications
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
US8081642B2 (en) 2003-01-31 2011-12-20 Brocade Communications Systems, Inc. Method and apparatus for routing between fibre channel fabrics
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
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

Patent Citations (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5809285A (en) * 1995-12-21 1998-09-15 Compaq Computer Corporation Computer system having a virtual drive array controller
US6219699B1 (en) * 1996-01-02 2001-04-17 Cisco Technologies, Inc. Multiple VLAN Architecture system
US5740171A (en) * 1996-03-28 1998-04-14 Cisco Systems, Inc. Address translation mechanism for a high-performance network switch
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
US6101497A (en) * 1996-05-31 2000-08-08 Emc Corporation Method and apparatus for independent and simultaneous access to a common data set
US5999930A (en) * 1996-08-02 1999-12-07 Hewlett-Packard Company Method and apparatus for distributed control of a shared storage volume
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
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
US6188694B1 (en) * 1997-12-23 2001-02-13 Cisco Technology, Inc. Shared spanning tree protocol
US6208649B1 (en) * 1998-03-11 2001-03-27 Cisco Technology, Inc. Derived VLAN mapping technique
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
US6266705B1 (en) * 1998-09-29 2001-07-24 Cisco Systems, Inc. Look up mechanism and associated hash table for a network switch
US20020110125A1 (en) * 1998-10-23 2002-08-15 David Banks Method and system for creating and implementing zones in hardware 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
US6226771B1 (en) * 1998-12-14 2001-05-01 Cisco Technology, Inc. Method and apparatus for generating error detection data for encapsulated frames
US20010049739A1 (en) * 2000-06-02 2001-12-06 Koji Wakayama Apparatus and method for interworking between MPLS network and non-MPLS network
US20020176434A1 (en) * 2001-04-18 2002-11-28 Brocade Communications Systems, Inc. Fibre channel zoning by logical unit number in hardware
US20030012204A1 (en) * 2001-07-11 2003-01-16 Sancastle Technologies, Ltd Extension of fibre channel addressing
US20030118053A1 (en) * 2001-12-26 2003-06-26 Andiamo Systems, Inc. Methods and apparatus for encapsulating a frame for transmission in a storage area network

Cited By (105)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8782245B1 (en) 2000-06-30 2014-07-15 Emc Corporation System and method for managing provisioning of storage resources in a network with virtualization of resources in such a network
US8656100B1 (en) * 2000-06-30 2014-02-18 Emc Corporation System and method for managing provisioning of storage resources in a network with virtualization of resources in such a network
US7734808B1 (en) 2001-12-18 2010-06-08 Cisco Technology, Inc. End-to-end congestion control in a Fibre Channel network
US9350653B2 (en) 2002-04-01 2016-05-24 Cisco Technology, Inc. Label switching in fibre channel networks
US20080316942A1 (en) * 2002-11-27 2008-12-25 Cisco Technology, Inc. Methods and devices for exchanging peer parameters between network devices
US8605624B2 (en) * 2002-11-27 2013-12-10 Cisco Technology, Inc. Methods and devices for exchanging peer parameters between network devices
US10432555B2 (en) * 2003-01-31 2019-10-01 Avago Technologies International Sales Pte. Limited Method and apparatus for routing between fibre channel fabrics
US9172556B2 (en) 2003-01-31 2015-10-27 Brocade Communications Systems, Inc. Method and apparatus for routing between fibre channel fabrics
US20160006674A1 (en) * 2003-01-31 2016-01-07 Brocade Communications Systems, Inc. Method and apparatus for routing between fibre channel fabrics
US11115349B2 (en) 2003-01-31 2021-09-07 Avago Technologies International Sales Pte. Limited Method and apparatus for routing between fibre channel fabrics
US7533175B1 (en) * 2003-10-24 2009-05-12 Network Appliance, Inc. Network address resolution and forwarding TCP/IP packets over a fibre channel network
US7877512B2 (en) 2004-01-29 2011-01-25 Brocade Communications Systems, Inc. Isolation switch for fibre channel fabrics in storage area networks
US7707309B2 (en) 2004-01-29 2010-04-27 Brocade Communication Systems, Inc. Isolation switch for fibre channel fabrics in storage area networks
US8135858B2 (en) 2004-01-29 2012-03-13 Brocade Communications Systems, Inc. Isolation switch for fibre channel fabrics in storage area networks
US8055794B2 (en) 2004-01-29 2011-11-08 Brocade Communications Systems, Inc. Isolation switch for fibre channel fabrics in storage area networks
US20100166422A1 (en) * 2004-01-29 2010-07-01 Brocade Communications Systems, Inc. Isolation Switch for Fibre Channel Fabrics in Storage Area Networks
US20050198523A1 (en) * 2004-01-29 2005-09-08 Brocade Communications Systems, Inc. Isolation switch for fibre channel fabrics in storage area networks
US20110196986A1 (en) * 2004-01-29 2011-08-11 Brocade Communications Systems, Inc. Isolation Switch for Fibre Channel Fabrics in Storage Area Networks
US8627005B1 (en) 2004-03-26 2014-01-07 Emc Corporation System and method for virtualization of networked storage resources
US9311001B1 (en) * 2004-03-26 2016-04-12 Emc Corporation System and method for managing provisioning of storage resources in a network with virtualization of resources in such a network
US8856589B1 (en) 2004-03-26 2014-10-07 Emc Corporation Failure protection in an environment including virtualization of networked storage resources
US7992038B1 (en) 2004-03-26 2011-08-02 Emc Corporation Failure protection in an environment including virtualization of networked storage resources
US7984253B1 (en) 2004-03-26 2011-07-19 Emc Corporation Architecture for virtualization of networked storage resources
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
US8018936B2 (en) 2004-07-19 2011-09-13 Brocade Communications Systems, Inc. Inter-fabric routing
US20060034302A1 (en) * 2004-07-19 2006-02-16 David Peterson Inter-fabric routing
US8532119B2 (en) 2004-07-30 2013-09-10 Brocade Communications Systems, Inc. Interfabric routing header for use with a backbone fabric
US20100220734A1 (en) * 2004-07-30 2010-09-02 Brocade Communications Systems, Inc. Multifabric Communication Using a Backbone Fabric
US20060023751A1 (en) * 2004-07-30 2006-02-02 Wilson Steven L Multifabric global header
US20090073992A1 (en) * 2004-07-30 2009-03-19 Brocade Communications Systems, Inc. System and method for providing proxy and translation domains in a fibre channel router
US20060023726A1 (en) * 2004-07-30 2006-02-02 Chung Daniel J Y Multifabric zone device import and export
US7742484B2 (en) 2004-07-30 2010-06-22 Brocade Communications Systems, Inc. Multifabric communication using a backbone fabric
US20060023708A1 (en) * 2004-07-30 2006-02-02 Snively Robert N 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
US8125992B2 (en) 2004-07-30 2012-02-28 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
US8446913B2 (en) 2004-07-30 2013-05-21 Brocade Communications Systems, Inc. Multifabric zone device import and export
US8059664B2 (en) * 2004-07-30 2011-11-15 Brocade Communications Systems, Inc. Multifabric global header
US20060023707A1 (en) * 2004-07-30 2006-02-02 Makishima Dennis H System and method for providing proxy and translation domains in a fibre channel router
US7483387B2 (en) 2005-05-23 2009-01-27 Cisco Technology, Inc. Hierarchical label distribution for inter-area summarization of edge-device addresses
US20070058619A1 (en) * 2005-08-19 2007-03-15 Gopal Gowda Manjunath A Port expander for fibre channel fabrics in storage area networks
US20090274162A1 (en) * 2005-08-19 2009-11-05 Brocade Communications Systems, Inc. Port expander for fibre channel fabrics in storage area networks
US8228820B2 (en) 2005-08-19 2012-07-24 Brocade Communications System, Inc. Port expander for fibre channel fabrics in storage area networks
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
US20100232793A1 (en) * 2005-10-25 2010-09-16 Brocade Communications Systems, Inc. Interface Switch for use with Fibre Channel Fabrics in Storage Area Networks
US8897294B2 (en) 2005-10-25 2014-11-25 Brocade Communications Systems, Inc. Interface switch for use with fibre channel fabrics in storage area networks
US7760717B2 (en) * 2005-10-25 2010-07-20 Brocade Communications Systems, Inc. Interface switch for use with fibre channel fabrics in storage area networks
US20070091903A1 (en) * 2005-10-25 2007-04-26 Brocade Communications Systems, Inc. Interface switch for use with fibre channel fabrics in storage area networks
US7890654B1 (en) * 2005-12-01 2011-02-15 Cisco Technology, Inc. Dynamic inter-VSAN topology discovery
US7644179B1 (en) * 2005-12-01 2010-01-05 Cisco Technology, Inc. Inter-VSAN routing with NAT
US20070140236A1 (en) * 2005-12-21 2007-06-21 Cisco Technology, Inc. Fibre channel traffic redirect scheme using FC NAT ACLs
US7769023B2 (en) 2005-12-21 2010-08-03 Cisco Technology, Inc. Fibre channel traffic redirect scheme using access control lists
US8040795B2 (en) 2006-05-10 2011-10-18 Cisco Technology, Inc. Backup path convergence in the APS environment
US20070263532A1 (en) * 2006-05-10 2007-11-15 Sina Mirtorabi 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
US20070266132A1 (en) * 2006-05-15 2007-11-15 Cisco Technology, Inc. Method and System for Providing Distributed Allowed Domains in a Data Network
US8730977B2 (en) * 2006-06-12 2014-05-20 Thomson Licensing 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
US20080013557A1 (en) * 2006-06-12 2008-01-17 Eduard Siemens 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
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
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
US20090052345A1 (en) * 2007-08-21 2009-02-26 Ibm Corporation Method and Apparatus for an Adapter in a Network Device to Discover its Adapter Name in a Network System
US20090052346A1 (en) * 2007-08-21 2009-02-26 Ibm 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
US20100258432A1 (en) * 2007-12-26 2010-10-14 Canon Anelva Corporation Sputtering apparatus, sputter deposition method, and analysis apparatus
US20100306610A1 (en) * 2008-03-31 2010-12-02 Masahiro Komatsu 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
US20100017497A1 (en) * 2008-07-15 2010-01-21 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
US8830836B1 (en) 2008-09-30 2014-09-09 Violin Memory, Inc. Storage proxy with virtual ports configuration
US8442059B1 (en) * 2008-09-30 2013-05-14 Gridiron Systems, Inc. Storage proxy with virtual ports configuration
US8417895B1 (en) 2008-09-30 2013-04-09 Violin Memory Inc. System for maintaining coherency during offline changes to storage media
US8472482B2 (en) 2008-10-27 2013-06-25 Cisco Technology, Inc. Multiple infiniband ports within a higher data rate port using multiplexing
US20100103954A1 (en) * 2008-10-27 2010-04-29 Cisco Technology, Inc. Multiple Infiniband Ports Within A Higher Data Rate Port Using Multiplexing
US8214599B2 (en) 2008-11-04 2012-07-03 Gridiron Systems, Inc. Storage device prefetch system using directed graph clusters
US8788758B1 (en) 2008-11-04 2014-07-22 Violin Memory Inc Least profitability used caching scheme
US20100115206A1 (en) * 2008-11-04 2010-05-06 Gridlron Systems, Inc. Storage device prefetch system using directed graph clusters
US20100115211A1 (en) * 2008-11-04 2010-05-06 Gridlron Systems, Inc. Behavioral monitoring of storage access patterns
US8214608B2 (en) 2008-11-04 2012-07-03 Gridiron Systems, Inc. Behavioral monitoring of storage access patterns
US8443150B1 (en) 2008-11-04 2013-05-14 Violin Memory Inc. Efficient reloading of data into cache resource
US8285961B2 (en) 2008-11-13 2012-10-09 Grid Iron Systems, Inc. Dynamic performance virtualization for disk access
US20100125857A1 (en) * 2008-11-17 2010-05-20 Gridlron Systems, Inc. Cluster control protocol
US8838850B2 (en) 2008-11-17 2014-09-16 Violin Memory, Inc. Cluster control protocol
US8775741B1 (en) 2009-01-13 2014-07-08 Violin Memory Inc. Using temporal access patterns for determining prefetch suitability
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
US9424180B2 (en) 2009-04-17 2016-08-23 Violin Memory Inc. System for increasing utilization of storage media
US8650362B2 (en) 2009-04-17 2014-02-11 Violin Memory Inc. System for increasing utilization of storage media
US8713252B1 (en) 2009-05-06 2014-04-29 Violin Memory, Inc. Transactional consistency scheme
US8402198B1 (en) 2009-06-03 2013-03-19 Violin Memory, Inc. Mapping engine for a storage device
US9069676B2 (en) 2009-06-03 2015-06-30 Violin Memory, Inc. Mapping engine for a storage device
US8402246B1 (en) 2009-08-28 2013-03-19 Violin Memory, Inc. Alignment adjustment in a tiered storage system
US8635375B2 (en) 2010-04-14 2014-01-21 Brocade Communications Systems, Inc. Remote F—ports
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
US20120110385A1 (en) * 2010-10-29 2012-05-03 International Business Machines Corporation Multiple functionality in a virtual storage area network device
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
US9195407B2 (en) 2011-03-02 2015-11-24 Violin Memory Inc. Apparatus, method and system for using shadow drives for alternative drive commands
US8635416B1 (en) 2011-03-02 2014-01-21 Violin Memory Inc. Apparatus, method and system for using shadow drives for alternative drive commands
US10628042B2 (en) 2016-01-27 2020-04-21 Bios Corporation Control device for connecting a host to a storage device
US20200169604A1 (en) * 2016-04-29 2020-05-28 Hewlett Packard Enterprise Development Lp Target driven peer-zoning synchronization
US10873626B2 (en) * 2016-04-29 2020-12-22 Hewlett Packard Enterprise Development Lp Target driven peer-zoning synchronization
US11159612B1 (en) 2020-04-28 2021-10-26 Hewlett Packard Enterprise Development Lp Determining non-TDP zones in a storage area network
WO2022102544A1 (en) 2020-11-13 2022-05-19 日本たばこ産業株式会社 Cembratrienediol-containing tobacco extract and production method therefor
WO2022102543A1 (en) 2020-11-13 2022-05-19 日本たばこ産業株式会社 Tobacco extract containing cembratriendiol and production method therefor

Also Published As

Publication number Publication date
ATE363171T1 (en) 2007-06-15
EP1459485A1 (en) 2004-09-22
US7599360B2 (en) 2009-10-06
JP2005514862A (en) 2005-05-19
CA2472056A1 (en) 2003-07-17
CN1620784A (en) 2005-05-25
KR100927265B1 (en) 2009-11-18
CN100348000C (en) 2007-11-07
AU2002364204B2 (en) 2008-04-03
CA2472056C (en) 2010-09-21
EP1459485B1 (en) 2007-05-23
DE60220313D1 (en) 2007-07-05
DE60220313T2 (en) 2008-01-17
US20030118053A1 (en) 2003-06-26
JP4335009B2 (en) 2009-09-30
KR20040068355A (en) 2004-07-30
WO2003058891A1 (en) 2003-07-17
AU2002364204A1 (en) 2003-07-24

Similar Documents

Publication Publication Date Title
US7499410B2 (en) Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain—IDs
US20050025075A1 (en) Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain_IDs
US6304901B1 (en) Multiple VLAN architecture system
US8537837B2 (en) Switch with virtual network identifier re-write capability
US8018936B2 (en) Inter-fabric routing
US8125992B2 (en) System and method for providing proxy and translation domains in a fibre channel router
EP0861544B1 (en) Method for establishing restricted broadcast groups in a switched network
US8565235B2 (en) System and method for providing transparent LAN services
US6529963B1 (en) Methods and apparatus for interconnecting independent fibre channel fabrics
US8446913B2 (en) Multifabric zone device import and export
US9515922B2 (en) Distributed fibre channel forwarder
US8059664B2 (en) Multifabric global header
JPH11145990A (en) Trunk-based operation of 'ethernet(r)' compatible network
US7742484B2 (en) Multifabric communication using a backbone fabric
US7890654B1 (en) Dynamic inter-VSAN topology discovery
US10812446B1 (en) Dynamic host configuration across multiple sites in software defined access networks

Legal Events

Date Code Title Description
AS Assignment

Owner name: CISCO TECHNOLOGY, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DUTT, DINESH G.;GAI, SILVANO;RAIMONDO, BRUNO;AND OTHERS;REEL/FRAME:015792/0176;SIGNING DATES FROM 20040824 TO 20040901

STCB Information on status: application discontinuation

Free format text: EXPRESSLY ABANDONED -- DURING EXAMINATION