US 7,230,929 B2Grant
Method and system for dynamically assigning domain identification in a multi-module fibre channel switch
Issue Date:2007-06-12
•2 Claims
•11 Drawing Sheets
Abstract
A method for entering fabric configuration in a fibre channel system for a multi-module fibre channel switch is provided. The method includes determining if a primary blade has been selected for the multi-module switch; sending exchange fabric parameters to internal ports of the multi-module switch; and processing principal switch selection events.
Metadata
Assignee
- QLogic, Corporation
Inventors
- Steven Manning Betker
- Timothy R. Vitters
- Renae M. Weber
Application Information
Application Number:US 10/200,393
Filing Date:2002-07-22
Priority Date:2002-07-22
Art Unit:2616
Classifications
IPC:
H04L12/28
Patent Drawings (11 sheets)
Description
Cross Reference to Related Application
[0001] This application is related to U.S. patent application entitled “METHOD AND SYSTEM FOR PRIMARY BLADE SELECTION IN A MULTI-MODULE FIBRE CHANNEL SWITCH”, U.S. Ser. No. 10/200,487, having common inventors and Assignee, filed on even date herewith, the disclosure of which is incorporated herein by reference in its' entirety.
Background
[0002] 1. Field of the Invention
[0003] The present invention relates to networking systems, and more particularly to systems using fibre channel fabrics for interconnecting fibre channel devices.
[0004] 2. Background of the Invention
[0005] Fibre channel is a set of American National Standard Institute (ANSI) standards which provide a serial transmission protocol for storage and network protocols such as HIPPI, SCSI, IP, ATM and others. Fibre channel provides an input/output interface to meet the requirements of both channel and network users.
[0006] Fibre channel supports three different topologies: point-to-point, arbitrated loop and fibre channel fabric. The point-to-point topology attaches two devices directly. The arbitrated loop topology attaches devices in a loop. The fibre channel fabric topology attaches host systems directly to a fabric, which are then connected to multiple devices. The fibre channel fabric topology allows several media types to be interconnected.
[0007] Fibre channel is a closed system that relies on multiple ports to exchange information on attributes and characteristics to determine if the ports can operate together. If the ports can work together, they define the criteria under which they communicate.
[0008] In fibre channel, a path is established between two nodes where the path's primary task is to transport data from one point to another at high speed with low latency, performing only simple error detection in hardware. The fibre channel switch provides circuit/packet switched topology by establishing multiple simultaneous point-to-point connections.
[0009] Fibre channel fabric devices include a node port or “N_Port” that manages fabric connections. The N_port establishes a connection to a fabric element (e.g., a switch) having a fabric port or F_port. Fabric elements include the intelligence to handle routing, error detection, recovery, and similar management functions.
[0010] A fibre channel switch is a multi-port device where each port manages a simple point-to-point connection between itself and its attached system. Each port can be attached to a server, peripheral, I/O subsystem, bridge, hub, router, or even another switch. A switch receives a connection request from one port and automatically establishes a connection to another port. Multiple calls or data transfers happen concurrently through the multi-port fibre channel switch.
[0011] A fibre channel switch may use multiple modules (also referred to as “blades” or “blade”) connected by fibre channel ports. Conventionally, a multi-module switch should appear to the other devices in the fibre channel fabric as a single switch.
[0012] Fibre channel switch addressing is defined by Fibre Channel Standard FC-SW-2. Typically, a 24-bit identifier is used to uniquely identify a switch. The 24 bit address includes a 8-bit Domain Identification (“Domain_ID.”) number; 8-bit Area Identifier (Area_ID) and 8-bit Port Identifer (Port_ID), as stated in FC-SW—2 Section 4.8, incorporated herein by reference in its entirety.
[0013] Domain_ID identifies a domain of one or more switches that have the same Domain_ID for all N_Ports and NL_Ports (an N_Port that can perform an Arbitrated Loop function). A domain in the fibre channel environment as defined by ANSI Standard X3.289-199X Fibre Channel-Fabric Generic Requirements (FC-FG), incorporated herein by reference in its entirety, is the highest or most significant hierarchical level in a three-level addressing scheme. If there are more than one switch in a Domain, then each switch within the domain is directly connected via an inter-switch link (“ISL”) to at least another switch in the domain.
[0014] Conventional systems pre-define a Domain_ID when a fibre channel switch is configured. Typically, a switch is assigned a Domain_ID the procedures defined in FC-SW-2. However, if a multi-module switch needs to appear as a single switch to the rest of the Fabric, the Domain_ID assignment procedure must be such that a consistent interface is available within the fabric.
[0015] Current Fiber Channel standards do not provide a mechanism to combine multiple switch modules into one switch.
[0016] Therefore, what is required is a process and system that can dynamically assign Domain_ID after a primary blade in a multi-module switch is selected.
Summary of the Invention
[0017] In one aspect, the present invention solves the foregoing drawbacks by providing a method for entering fabric configuration in a fibre channel system for a multi-module fibre channel switch. The method includes determining if a primary blade has been selected for the multi-module switch; sending exchange fabric parameters to internal ports of the multi-module switch; and processing principal switch selection events.
[0018] In another aspect of the present invention, a method for processing principal switch selection events in a fibre channel system using a multi-module fibre channel switch is provided. The method includes determining if a switch module has received exchange fabric parameters; determining if the switch module has received domain identification values; sending domain identification values to all internal ports; and operating as a non-principal switch if the switch module is also a primary blade.
[0019] The method also includes determining if a F_S_TOV timer has expired if no domain identification value is received; and operating as the principal switch if the switch module is a primary blade and the F_S-TOV timer has expired.
[0020] In another aspect of the present invention, a method for operating a principal switch in a fibre channel system using a multi-module switch is provided. The method includes sending exchange blade parameters with a local domain assigned value to plural internal ports in the switch module.
[0021] In yet another aspect, a method for operating a multi-module switch as a non-principal switch in a fibre channel system is provided. The method includes requesting local domain identification values from other modules; and sending exchange blade parameters with local domain assigned values to internal ports. The method includes isolating the switch module if the local domain assignment value was unsuccessful.
[0022] In yet another aspect, a method for domain identification value assignment for a multi-module switch in a fibre channel system is provided. The method includes receiving exchange blade parameters with local domain value assigned; and sending domain identification value assigned flags to external ports.
[0023] The method includes isolating external ports if the exchange blade parameter has a rejected value for local domain assignment.
[0024] In one aspect of the present invention, Domain_ID may be dynamically assigned.
[0025] In another aspect of the present invention, a multi-module switch can act as a principal switch, with the primary blade performing Domain_ID assignments for the multi-module switch and for other external switches. The multi-module switch can also operate as non-principal switch, with the primary blade requesting a Domain_ID assignment on behalf of the multi-module switch and informing the other modules of the assignment.
[0026] This brief summary has been provided so that the nature of the invention may be understood quickly. A more complete understanding of the invention can be obtained by reference to the following detailed description of the preferred embodiments thereof concerning the attached drawings.
Brief Description of the Drawings
[0027] The foregoing features and other features of the present invention will now be described with reference to a fibre channel system. In the drawings, the same components have the same reference numerals. The illustrated embodiment is intended to illustrate, but not to limit the invention. The drawings include the following Figures:
[0028] FIG. 1 , as described above, shows a block diagram of a fibre channel system using a fibre channel fabric;
[0029] FIG. 2 is a block diagram showing multi-module switch;
[0030] FIG. 3 is block diagram of a switch in a multi-module switch environment that can select a primary blade, according to one aspect of the present invention;
[0031] FIG. 4 is a process flow diagram of executable process steps for selecting a primary blade in a multi-module switch environment;
[0032] FIG. 5 is a flow diagram of a executable process steps for processing exchange blade parameters for selecting a primary blade, according to one aspect of the present invention;
[0033] FIG. 6 is a block diagram showing ISLs between plural multi-module switches;
[0034] FIG. 7 is a process flow diagram of executable process steps for fabric configuration entry criteria for each blade, according to one aspect of the present invention;
[0035] FIG. 8 is a process flow diagram of executable process steps for principal switch selection, according to one aspect of the present invention;
[0036] FIG. 9 is a process flow diagram of executable process steps for primary blade and principal switch operation, according to one aspect of the present invention;
[0037] FIG. 10 is a process flow diagram of executable process steps for primary blade, and non-principal switch operation, according to one aspect of the present invention; and
[0038] FIG. 11 is a process flow diagram of executable process steps for non-primary blade operation during Domain_ID address assignment, according to one aspect of the present invention.
Detailed Description of the Preferred Embodiments
[0039] Definitions:
[0040] The following definitions are provided as they are typically (but not exclusively) used in the fibre channel environment, implementing the various adaptive aspects of the present invention.
- [0041] a. “Blade”: A module in a multi-module fibre channel switch.
- [0042] b. “Blade_ID”: A unique identifier for identifying a switch module.
- [0043] c. “B_S_TOV Timer”: A timer to detect inactivity during primary blade selection.
- [0044] d. “E-Port”: Expansion port
- [0045] e. “EBP”: Exchange Blade Parameters, created by a Multi-Blade Protocol.
- [0046] f. “EFP”: Exchange Fabric Parameters as defined by FC-SW-2.
- [0047] g. “Fibre channel ANSI Standard”: The standard describes the physical interface, transmission and signaling protocol of a high performance serial link for support of other high level protocols associated with IPI, SCSI, IP, ATM and others.
- [0048] h. “FC-1”: Fibre channel transmission protocol, which includes serial encoding, decoding and error control.
- [0049] i. “FC-2”: Fibre channel signaling protocol that includes frame structure and byte sequences.
- [0050] j. “FC-3”: Defines a set of fibre channel services that are common across plural ports of a node.
- [0051] k. “FC-4”: Provides mapping between lower levels of fibre channel, IPI and SCSI command sets, HIPPI data framing, IP and other upper level protocols.
- [0052] l. “Fabric”: A system which interconnects various ports attached to it and is capable of routing fibre channel frames by using destination identifiers provided in FC-2 frame headers.
- [0053] m. “Fabric Topology” This is a typology where a device is directly attached to a fibre channel fabric that uses destination identifiers embedded in frame headers to route frames through a fibre channel fabric to a desired destination.
- [0054] n. F_S_TOV Timer: Defined by FC-SW-2, a time constant used to ensure that fabric stability has been achieved during fabric configuration.
- [0055] o. Multi Blade protocol: A protocol that operates on internal switch module ports to assign a primary blade and exchange blade parameters.
- [0056] p. Port: A general reference to N. Sub.—Port or F. Sub.—Port.
- [0057] q. “Slot Number”: A unique identifier for each blade in a multi-module switch derived from the physical location of the blade in a chasis.
[0058] The Fibre Channel Specification used to build one embodiment of the present-invention includes:
[0059] FC-SW-2 standard as published by the American National Standard Institute.
[0060] To facilitate an understanding of the preferred embodiment, the general architecture and operation of a fibre channel system will be described. The specific architecture and operation of the preferred embodiment will then be described with reference to the general architecture of the fibre channel system.
[0061] FIG. 1 is a block diagram of a fibre channel system 100 implementing the methods and systems in accordance with the adaptive aspects of the present invention. System 100 includes plural devices that are interconnected. Each device includes one or more ports, classified as node ports (N_Ports), fabric ports (F_Ports), and expansion ports (E_Ports). Node ports may be located in a node device, e.g. server 103, disk array 105 and storage device 104. Fabric ports are located in fabric devices such as switch 101 and 102. Arbitrated loop 105 may be operationally coupled to switch 101 using arbitrated loop ports (FL;Ports).
[0062] The devices of FIG. 1 are operationally coupled via “links” or “paths”. A path may be established between two N_ports, e.g. between server 103 and storage 104. A packet-switched path may be established using multiple links, e.g. an N-Port in server 103 may establish a path with disk array 105 through switch 102.
[0063] Switch 101 includes an E_Port that enables a path to another switch 102. An ISL enables N_Ports to operationally couple to other N-Ports in a fabric.
[0064] FIG. 2 is a block diagram that shows plural switch modules (or blades) 102A–102F integrated into a single multi-switch module 200. Internal ports between the switch modules operate on a multi-blade protocol, while external ports operate under FC-SW-2 protocol.
[0065] FIG. 3 is a block diagram of a blade in a multi-module switch, e.g. 102A that implement the adaptive aspects of the present invention. Switch module 102A includes plural external ports (F_Ports operationally coupled to other devices, e.g. server 103; or E_Ports coupled to other switch modules) 300A through 300D; and internal ports 301A–301D that operate under the multi-blade protocol.
[0066] Switch module 102A also includes a primary blade state machine 302 that uses EBPs under the multi-blade protocol to select the primary blade for module 200.
[0067] Also included in switch module 102A is a principal switch state machine 303 that processes principal switch selection and Domain ID assignment for the switch module.
[0068] Primary Blade Selection:
[0069] FIG. 4 shows a flow diagram of executable process steps for selecting a primary blade in a multi-module switch environment. In one aspect of the present invention EBP parameters are used to select a primary blade, and once a primary blade is selected other blades are notified of the primary blade selection. A blade with the lowest priority and slot number is selected as the primary blade. As defined above, a slot number is unique to a particular blade (or switch module, used interchangeably throughout this specification).
[0070] Turning in detail to FIG. 4 , in step S400 the process starts and switch module 200 is initialized.
[0071] In step S401, retained primary blade priority and blade number is initialized to the blade's priority and blade number.
[0072] In step S402, internal ports 301A–301D are initialized.
[0073] In step S403, a B_S-TOV timer is started and thereafter, in steps S404, an EBP request is sent to all adjacent blades. In one aspect the B_S_TOV timer (not shown) is operationally coupled or integrated with state machine 302.
[0074] An example of an EBP request is provided below:
[0075]
| TABLE 1 | ||
|---|---|---|
| EBP Request Payload | ||
| Byte | ||
| Item | Size | |
| Command Code = hex′ 82′ | 1 | |
| Reserved | 1 | |
| Payload Length | 2 | |
| Reserved | 3 | |
| Primary Blade Priority | 1 | |
| Reserved | 3 | |
| Primary Blade Slot | 1 | |
| Number | ||
| Reserved | 3 | |
| Primary Blade Assigned | 1 | |
| Local Domain_ID Status | 1 | |
| Reserved | 2 | |
| Local Domain_ID | 1 | |
| Reserved | 3 | |
| Switch Priority | 1 | |
| Design specific data | N | |
[0076] Payload Length: This field may contain a 16-bit unsigned integer that specifies the total payload length in bytes. This value is hex‘18’+size of design specific data.
[0077] Primary Blade Priority: This field specifies the priority level of a blade that an EBP transmitting blade believes is the primary blade.
[0078] Primary Blade Slot Number: This field specifies the slot number of the blade that the EBP transmitting blade believes is the primary blade. This value uniquely identifies each blade in a switch derived from the physical location of the module in a chassis.
[0079] Primary Blade Assigned: This field indicates that the primary blade role is assigned. If zero, the primary blade has not been selected. If non-zero, the primary blade has been selected. Table 2 below shows an example of primary blade values.
[0080]
| TABLE 2 | |
|---|---|
| Primary Blade Assigned Status | |
| value | Comments |
| 0 | Unassigned. Primary |
| blade selection is | |
| in progress. | |
| 1 | Assigned. Primary |
| blade role assigned. | |
[0081] Local Domain_ID Status: Indicates Domain_ID status of a blade. The primary blade is responsible for requesting a Domain_ID on behalf of all blades. When Local Domain_ID status is two, blades are permitted to transmit Domain_ID assignment (“DIA”) requests on external E_Ports. Allowable values are shown in Table 3.
[0082]
| TABLE 3 | |
|---|---|
| Local Domain_ID Status | |
| value | Comments |
| 1 | Predefined. Local Domain_ID was |
| predefined by configuration data. | |
| 2 | Accepted. Local Domain_ID has been |
| granted by principal switch. | |
| 3 | Accepted. Local Domain_ID has been |
| granted by principal switch and | |
| fabric is in reconfiguration. | |
| 4 | Rejected. Local Domain_ID has been |
| rejected by principal switch. | |
| 5 | Rejected. Local Domain_ID has been |
| rejected by principal switch and | |
| fabric is in reconfiguration. | |
[0083] Local Domain_ID: This denotes a switch's local Domain_ID.
[0084] Switch Priority Value: This denotes a switch's priority as defined by FC-SW-2.
[0085] In step S405, the process determines if all switch modules have received an EBP payload. If an EBP payload has been received, then the EBP is processed in step S406, as shown in the process steps of FIG. 5 . If a primary blade has been selected, as determined in step S407, the local blade is set as a non-primary blade in step S408. If the primary blade has not been selected, then the process moves back to step S405.
[0086] If an EBP is not received in step s405, then in step S405A, the process determines, if the B_S_TOV timer has expired. If the timer has not expired the process moves to step s405.
[0087] If the timer has expired, then in step S409, the process determines if the retained slot number is the local slot number. If not, the process moves to step s405.
[0088] If the retained slot number is the local slot number, then in step S410, the local blade is set as the primary blade.
[0089] In step S411, the primary blade sends EBPs to all internal ports and the selected blade operates as the primary blade in step S412.
[0090] FIG. 5 is a flow diagram of executable process steps that describes processing of EBPs (step S406) for selecting a primary blade, according to one aspect of the present invention.
[0091] Turning in detail to FIG. 5 , in step S500, EBP's are received and the B_S_TOV timer is started.
[0092] In step S501, the EBP payload is analyzed by primary blade state machine 302, to determine whether a primary blade flag is set. If it is set, then the process moves to step S503, where the EBP priority and slot number replaces the retained priority and slot number.
[0093] If the primary blade flag is not set in step S501, then in step S502, the process determines if the EBP priority is less than the retained priority. If it is less, then the process moves to step S503.
[0094] If the EBP priority is not less than the retained priority, then in step S506, the process determines if the EBP priority is equal to the retained priority. If not, the process terminates at step S508.
[0095] If the EBP priority is equal to the retained priority, then in step S507, the process determines if the EBP slot number is less than the retained slot number. If it is less, then the process moves to step S503. If not, the process terminates at step S508.
[0096] Once the EBP priority and slot number are retained in step S503, in step S504 (similar to step S411), EBPs are sent to all internal ports with the selected primary blade and the process terminates in step S505.
[0097] Principal Switch and Domain ID Assignment:
[0098] A principal switch is selected whenever an external E_Port ISL is established.
[0099] FIG. 6 shows plural multi-module switches 200A–200D operationally coupled to each other. Each multi-module switch has a primary blade that may be selected by the process discussed above. Each switch module (blade) has its own state machine. By following the process steps described below, the switch modules will appear to the rest of the Fabric as a single switch. Non-multi-module switches use the process defined by FC-SW-2.
[0100] FIG. 7 is a process flow diagram of executable process steps for switch modules in a fabric to enter fabric configuration. In one aspect of the present invention, a primary blade is selected before the principal switch selection process is started. In a single blade switch, the only blade operates as the primary blade. A switch sends EFPs during fabric configuration and inter-blade EFP exchange occurs at the same time. A blade with external E_Port ISL can initiate principal switch selection on behalf of other blades and send EFPs. Other blades receive EFPs on internal ports, signaling the start of principal switch selection. Each blade may also operate independently during EFP exchange.
[0101] Turning in detail to FIG. 7 , in step S701, a switch module (e.g. 200A) enters fabric configuration. The switch module waits in step S702 for a primary blade to be selected, as described above. After primary blade selection is complete in step S702, the process determines whether an external E_Port is initialized in step S703.
[0102] If external E_Port ISL initialization is complete in step S703, the switch module initiates principal switch selection. In step S704, an EFP is sent to external E_Ports as specified in FC-SW-2 and in step S707, EFPs are sent on all internal E_Ports to notify other switch modules that principal switch selection has started.
[0103] If external E_Ports are not initialized in step S703, then in step S705, the process determines if an EFP has been received on an internal port, before starting principal switch selection. In step S705, a switch module receiving an EFP on an internal port joins principal switch selection, and in step S706 the EFPs are processed as specified in FC-SW-2.
[0104] In step S707, EFPs are sent on all internal E_Ports to notify all other switch modules that principal switch selection has started.
[0105] In step S708 each switch module initializes principal switch selection timer F_S_TOV as specified in FC-SW-2. The process then moves to the principal switch selection process in step S709, described below with respect to FIG. 8 .
[0106] FIG. 8 is a flow diagram of executable process steps for principal switch selection (step S709). The process starts when the principal switch selection entry is completed in FIG. 7 . After a principal switch is selected, each switch module transitions to one of three domain address assignment processes, described below.
[0107] Turning in detail to FIG. 8 , in step S801 the principal switch selection events starts. Principal switch selection events are processed in steps S802, S804 and S809 until a principal switch is selected. The events include receipt of EFPS, DIA flags and expiration of F-S-TOV timer. These events may be processed in any order.
[0108] If an EFP is received in step S802, the process moves to step S803. In step S803, the EFP is processed as specified in FC-SW-2 for principal switch selection.
[0109] If an EFP is not received, then the process determines if a set DIA flag is received in step S804, signaling the end of principal switch selection. If the DIA flag is set then the switch module does not become the principal switch and the process moves to step S805.
[0110] In step S805, the process sends DIA flag values to internal ports to notify other switch modules that principal switch selection is complete. Other switch modules in step S804 receive DIA values sent in step S805.
[0111] In step S806, the process determines if the switch module is the primary blade. If it is the primary blade then the process moves to step S807 and the switch module operates as a non-principal switch, described below with respect to FIG. 10 .
[0112] In step S806, if the switch module is not the primary blade, the process moves to step S808 and the switch module operates as a non-primary blade during domain address assignment described below with respect to FIG. 11 .
[0113] If the DIA flag is not set in step S804, then in step S809, the process determines if the F-S_TOV timer has expired. If F_S_TOV timer expires in step S809, the switch module may become the principal switch.
[0114] In step S810, the process determines if the switch module is the primary blade. If yes, then in step S811, the process determines if the switch module is the principal switch. The process compares the switch's worldwide name with the principal switch's worldwide name discovered in step S803. If either step S810 or S811 is false, the process resumes wait for the next event. If the switch module is the principal switch in step S811, then the process moves to step S812 and the switch module operates as the principal switch described below with respect to FIG. 9 .
[0115] FIG. 9 is a process flow diagram of executable process steps for a primary blade that operates as a principal switch (step S812, FIG. 8 ). In addition to standard FC-SW-2 operations, the primary blade sends the switch's local Domain_ID status to non-primary blades.
[0116] Turning in detail to FIG. 9 , in step S901, a primary blade operates as the principal switch.
[0117] In step S902, the primary blade assigns the local switch Domain_ID as specified in FC-SW-2, including sending DIA flags to external E_Ports and internal ports. It is noteworthy that non-primary blades at step S804 receive the DIA flags.
[0118] In step S903, an EBP with this switch's local Domain_ID and status is sent to all non-primary blades. Other non-primary blades at step S1102, as described below, also receive these EBPs.
[0119] In step S904, the switch continues to operate as the principal switch as specified in FC-SW-2.
[0120] FIG. 10 is a process flow diagram of executable process steps for a primary blade that operates as a non-principal switch. In addition to standard FC-SW-2 operations, the primary blade sends this switch's local Domain_ID and status to non-primary blades.
[0121] Turning in detail to FIG. 10 , in step S1001, a primary blade operates as a non-principal switch.
[0122] In step S1002, the primary blade requests a local switch Domain_Id as specified in FC-SW-2.
[0123] In step S1003, the process verifies if the local Domain_ID request is successful, and if successful, the process moves to step S1004.
[0124] In step S1004, an EBP with the switch's local Domain_ID and status flag is sent to all non-primary blades. Other non-primary blades at step S1102 also receive these EBPs.
[0125] In step S1005, the switch continues to operate as a non-principal switch, as specified in FC-SW-2, and sends DIA information to external E_Ports and internal ports.
[0126] Returning to step S1003, if the local Domain_ID request is unsuccessful then the process moves to step S1006. In step S1006, EBPs with the switch's local Domain_ID and status flags are sent to all non-primary blades. Other non-primary blades at step S1104 receive these EBPs. Thereafter, in step S1007, external E-port ISLs are isolated per FC-SW-2.
[0127] FIG. 11 is a process flow diagram of executable process steps for a non-primary blade during Domain_ID assignment (S808). The non-primary blade waits until this switch's local Domain_ID and status flags are received from the primary blade.
[0128] Turning in detail to FIG. 11 , in step S1101, a non-primary blade moves to Domain_ID assignment. The non-primary blade waits for an EBP indicating that the local switch Domain_ID is either accepted in step S1102 or rejected in steps S1104. When the local switch domain is accepted in step S1102, the switch module operates with the EBP local switch Domain_ID.
[0129] In step S1103, the switch module sends DIA information to external E-Port ISLs to notify neighboring switches as specified in FC-SW-2.
[0130] When the local switch domain is rejected in step S1104, the switch module operates with the EBP local switch Domain_ID and in step S1105, the switch module isolates external E-Ports.
[0131] In one aspect of the present invention, Domain_ID may be dynamically assigned.
[0132] In another aspect of the present invention, a multi-module switch can act as a principal switch, with the primary blade performing Domain_ID assignment for the multi-module switch and for other external switches. The multi-module switch can also operate as non-principal switch, with the primary blade requesting a Domain_ID assignment on behalf of the multi-module switch and informing the other modules of the assignment.
[0133] Although the present invention has been described with reference to specific embodiments, these embodiments are illustrative only and not limiting. Many other applications and embodiments of the present invention will be apparent in light of this disclosure and the following claims
Claims
What is claimed is:
1. A method for processing principal switch selection events in a fibre channel system using a multi-module fibre channel switch, comprising:
determining if exchange fabric parameters have been received by a switch module;
determining if domain identification values have been received by the switch module;
sending domain identification values to all internal ports;
operating as a non-principal switch if the switch module is also a primary blade;
determining if a F_S_TOV timer has expired if no domain identification value is received; and
operating as the principal switch if the switch module is a primary blade and the F_S-TOV timer has expired.
2. A method for processing principal switch selection events in a fibre channel system using a multi-module fibre channel switch, comprising:
determining if exchange fabric parameters have been received by a switch module;
determining if domain identification values have been received by the switch module;
sending domain identification values to all internal ports;
operating as a non-principal switch if the switch module is also a primary blade; and
assigning the switch module as a non-primary blade if the domain identification value is received by the switch module and the switch module is not a primary blade.
Patent Citations (58)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4162375(A) | 1979-07-01 | Schlichte | Applicant |
| US4425640(A) | 1984-01-01 | Philip et al. | Applicant |
| US4546468(A) | 1985-10-01 | Christmas et al. | Applicant |
| US4569043(A) | 1986-02-01 | Simmons et al. | Applicant |
| US4725835(A) | 1988-02-01 | Schreiner et al. | Applicant |
| US4821034(A) | 1989-04-01 | Anderson et al. | Applicant |
| US5144622(A) | 1992-09-01 | Takiyasu et al. | Applicant |
| US5367520(A) | 1994-11-01 | Cordell | Applicant |
| US5598541(A) | 1997-01-01 | Malladi | Applicant |
| US5610745(A) | 1997-03-01 | Bennett | Applicant |
| US5687172(A) | 1997-11-01 | Cloonan et al. | Applicant |
| US5748612(A) | 1998-05-01 | Stoevhase et al. | Applicant |
| US5818842(A) | 1998-10-01 | Burwell et al. | Applicant |
| US5894560(A) | 1999-04-01 | Carmichael et al. | Applicant |
| US5987028(A) | 1999-11-01 | Yang et al. | Applicant |
| US5999528(A) | 1999-12-01 | Chow et al. | Applicant |
| US6014383(A) | 2000-01-01 | McCarty | Applicant |
| US6021128(A) | 2000-02-01 | Hosoya et al. | Applicant |
| US6047323(A) | 2000-04-01 | Krause | Applicant |
| US6081512(A) | 2000-06-01 | Muller et al. | Applicant |
| US6118776(A) | 2000-09-01 | Berman | Applicant |
| US6128292(A) | 2000-10-01 | Kim et al. | Applicant |
| US6144668(A) | 2000-11-01 | Bass et al. | Applicant |
| US6160813(A) | 2000-12-01 | Banks et al. | Applicant |
| US6308220(B1) | 2001-10-01 | Mathur | Applicant |
| US6324181(B1) | 2001-11-01 | Wong et al. | Applicant |
| US6330236(B1) | 2001-12-01 | Ofek et al. | Applicant |
| US6353612(B1) | 2002-03-01 | Zhu et al. | Applicant |
| US6370605(B1) | 2002-04-01 | Chong | Applicant |
| US6411599(B1) | 2002-06-01 | Blanc et al. | Applicant |
| US6424658(B1) | 2002-07-01 | Mathur | Applicant |
| US6449274(B1) | 2002-09-01 | Holden et al. | Applicant |
| US6467008(B1) | 2002-10-01 | Gentry et al. | Applicant |
| US6597691(B1) | 2003-07-01 | Anderson et al. | Applicant |
| US6597777(B1) | 2003-07-01 | Ho | Applicant |
| US6697359(B1) | 2004-02-01 | George | Applicant |
| US6697368(B2) | 2004-02-01 | Chang et al. | Examiner |
| US6760302(B1) | 2004-07-01 | Ellinas et al. | Applicant |
| US6886141(B1) | 2005-04-01 | Kunz et al. | Applicant |
| US2001/0038628(A1) | 2001-11-01 | Ofek et al. | Applicant |
| US2002/0034178(A1) | 2002-03-01 | Schmidt et al. | Applicant |
| US2002/0196773(A1) | 2002-12-01 | Berman | Applicant |
| US2003/0016683(A1) | 2003-01-01 | George et al. | Applicant |
| US2003/0091062(A1) | 2003-05-01 | Lay et al. | Applicant |
| US2003/0120983(A1) | 2003-06-01 | Vieregge et al. | Applicant |
| US2003/0179748(A1) | 2003-09-01 | George et al. | Applicant |
| US2003/0189935(A1) | 2003-10-01 | Warden et al. | Applicant |
| US2004/0013092(A1) | 2004-01-01 | Betker et al. | Applicant |
| US2004/0013125(A1) | 2004-01-01 | Betker et al. | Applicant |
| US2004/0024831(A1) | 2004-02-01 | Yang et al. | Applicant |
| US2004/0028038(A1) | 2004-02-01 | Anderson et al. | Applicant |
| US2004/0141521(A1) | 2004-07-01 | George | Applicant |
| US2006/0047852(A1) | 2006-03-01 | Shah et al. | Applicant |
| US2006/0074927(A1) | 2006-04-01 | Sullivan et al. | Applicant |
| EP649098 | 1994-09-01 | Applicant | |
| EP856969 | 1998-01-01 | Applicant | |
| WO-98/36537 | 1998-08-01 | Applicant | |
| WO3/088050(A1) | 2003-10-01 | Examiner |
Non-Patent Literature (15)
- Clark, Tom, “Zoning for Fibre Channel Fabrics”, Vixel Corporation Paper—XP002185194., (Aug. 1999), pp. 1-6.Applicant
- Malavalli, Kumar, et al., “Distributed Computing with fibre channel fabric”, Proc of the Computer Soc. Int'l Conf., Los Alamitos, IEEE Comp Soc. Press., vol. Conf. 37, XP000340745, (Feb. 24, 1992), pp. 269-274.Applicant
- Martin, Charles R., “Fabric Interconnection of fibre channel standard nodes”, Proceedings of the SPIE, (Sep. 8, 1992), pp. 65-71.Applicant
- Yoshida, Hu, “LUN Security Considerations for Storage Area Networks,” Hitachi Data Systems Paper—XP 002185193 (1999), pp. 1-7.Applicant
- Claudio DeSanti, “Virtual Fabrics Switch Support”; VF Switch Support, T11/04-395v2. Sep. 2004, pp. 1-15.Applicant
- Pelissier et al, “Inter-Fabric Routing”, dated Jul. 30, 2004, Inter Fabric Routing (04-520v0); pp. 1-31.Applicant
- DeSanti et al, “Virtual Fabrics”; Virtual Fabrics, T11/03-352v0, May 2003; pp. 1-4.Applicant
- Martin et al , “Virtual Channel Architecture”, Presentation by Brocade to T11/03-369v0 dated Jun. 2, 2003.Applicant
- Curtis, A. R., “Design Considerations for 10-Gbit Fibre Channel”, Curtis A. Ridgeway, Distinguished I/O Architect. Storage and Computing ASIC's Division, LSI Logic Corp..Applicant
- Malavalli, Kumar, “High Speed Fibre Channel Switching Fabric Devices”, Proceedings of the SPIE, SPIE, Bellingham, VA, USA vol. 1577, XP000562869, ISSN: 0277-786X,(Sep. 4, 1991),216-226.Applicant
- Melhem, et al., “Minimizing Wavelength Conversions in WDM Path Establishment”, Computer Science Department, University of Pittsburgh, Pittsburgh, PA 15260, (2001),197-211.Applicant
- Ridgeway, Curt, “0GFC-40GFC using 4-lane XAUI's”, LSI Logic Presentation—T11/03-069v0.Applicant
- Fibre Channel Switch Fabric—2 (FC-SW-2) Rev 5.4, NCITS working draft proposed American National Standard for Information Technology, Jun. 26, 2001., T11/Project 1305-D/Rev 5.4.Applicant
- Fibre Channel Generic Services—3 (FC-GS-3) Rev 7.01, NCITS working draft proposed American National Standard for Information Technology, Nov. 28, 2000., T11/Project 1356 D/Rev 7.01.Applicant
- Brown, Douglas W., “A State-Machine Synthesizer”, 18th Design Automation Conference, (1981),301-305.Applicant