Patent Application
20100115163
1. Field of the Invention
The invention relates to the Serial Attached SCSI (SAS) data transfer technology protocol. More particularly, the invention relates to methods, devices and system architectures for SAS Zoning management.
2. Description of the Related Art
SCSI refers to the Small Computer Systems Interface set of electronic interface standards that allow various devices to communicate with one another, e.g., computers to communicate with peripheral devices. Serial Attached SCSI (SAS) refers to a point-to-point serial protocol for data transfer technology between computer network storage devices, such as hard drives and tape drives. An SAS domain is an input/output (I/O) system that includes a set or network of SAS devices that communicate with one another.
SAS provides switching capability using (SAS) expanders, which act as switches between SAS initiators (e.g., hosts) and SAS targets (e.g., end devices, such as disk drives), and are fully capable of connecting multiple SAS hosts to multiple SAS end devices. Accordingly, SAS is being explored as a possible mechanism for connecting large groups of targets in various storage area network (SAN) applications, and other applications. Within such SAN applications, the management of SAS domains is a key element to the success of SAS implementation within the network systems that make up the SAS domains.
In general, an SAS initiator device directs information to an SAS target device through ports of one or more SAS expanders in the SAS domain. A port can include one or more physical links, or phys, to connect devices in an SAS domain. A port can use a single phy or, if the port is configured as a wide port, can use multiple phys logically grouped to provide higher bandwidth. Ports are formed dynamically, although multiple phys also can be physically grouped in a static manner, i.e., a connector. Often, ports and connectors end up grouping the same phys.
The SAS specifications presently support zoning capabilities within an SAS domain. SAS zoning is implemented by one or more (typically a set of) zoning expanders that cooperate to define the zoned service delivery subsystem (ZSDS). The zoning expanders, i.e., SAS expanders with zoning capabilities, control whether a phy is permitted to open a connection to or participate in a connection with another phy. Such control determines whether two SAS devices attached to the SAS zoning expander through the phys are able to communicate. Such communication is important for sharing storage resources among multiple servers, including the ability to prevent servers from connecting to other servers and associated storage devices of the other servers.
The phys of the SAS zoning expanders are assigned zone groups. A zone group is a set of phys in a zoned portion of a service delivery subsystem (ZPSDS) that can have the same access permissions. A zoned portion of a service delivery subsystem (ZPSDS) is a group of zoning expander devices that cooperate to control access between phys. When SAS exchanges are routed through SAS zoning expanders, the SAS zoning expanders may verify that the phys (e.g., the SAS devices coupled to the phys) are permitted to participate in the connection. Also, the SAS zoning expanders may deny the connection if the phys are not permitted to participate in the connection.
Conventionally, applications designed to manage SAS zoning allow each phy on the edge of the ZPSDS to be assigned into a zone group, then allow permissions to be established and assigned for the zone groups to communicate with one another. Such a relatively direct SAS zoning approach often poses several problems for the management application.
For example, application administrators typically think about visibility among devices, such as to which target devices a particular initiator device should have access. Such approach is analogous to Fibre Channel (FC) World Wide Name (WWN) based zoning, and most often is used in dynamic topologies where changes sometimes may occur. Also, application administrators sometimes think in terms of connectors or ports, such as to what other connectors should devices attached to a particular connector have access. Such approach is analogous to Fibre Channel (FC) Port based zoning, and most often is used in static topologies. Sometimes application administrators want to implement a specific strategy, such as preventing access by a first SAS device to another SAS device. In all of these cases, conventionally, the SAS zoning application has to deconstruct the zoning requirements, i.e., break down the device or connector model to the phy level, to be able to map phys into zone groups and then to assign zone group permissions.
Moreover, all of the target devices in the SAS domain are not always attached directly to the ZPSDS. Therefore, target devices sometimes are forced to share a common ZPSDS entry point associated with the same zone group. When this occurs, the SAS zoning application must bundle target devices together based on their ZPSDS attachment points to see if zoning requirements can be realized on a particular topology before breaking down the device or connector model to the phy level to map phys into zone groups and assign zone group permissions.
The invention is embodied in a method, apparatus and system for managing SAS zoning, using connector grouping, without requiring the SAS zoning management requirements to be deconstructed down to the phy level. A connector grouping management application is configured to allow connectors on the edge of the ZPSDS to be grouped into any number of zones or zone configurations. These defined zones are used to create a minimal number of zone groups, e.g., by creating one zone group per defined zone and populating the zone group with the phys associated with the connectors in the zone from which the zone group is based, and to configure the respective permissions of the created zone groups. The connector grouping application then compares all existing zone groups for phys common to more than one zone group. The connector grouping application removes all phys common to more than one zone group from their respective zone groups and moves the common phys to a new zone group. The zone groups are compared and processed in this manner until no zone groups have common phys. Once all zone groups have been processed accordingly, information associated with the resulting zone groups and their respective permissions are transferred to the zone manager.
In the following description, like reference numerals indicate like components to enhance the understanding of the invention through the description of the drawings. Also, although specific features, configurations and arrangements are discussed hereinbelow, it should be understood that such is done for illustrative purposes only. A person skilled in the relevant art will recognize that other steps, configurations and arrangements are useful without departing from the spirit and scope of the invention.
A SAS connector grouping management application is described herein that simplifies the work of an SAS domain administrator. The connector grouping methods, devices and systems described herein allow an SAS domain administrator to interface with the particular SAS zoning application without requiring the administrator to deconstruct the zoning requirements down to the phy level. The connector grouping methods, devices and systems described herein allow connectors on the edge of the ZPSDS to be grouped into any number of zones or zone configurations. These defined zone configurations then are used to create the minimal number of zone groups, and to configure the respective permissions of those zone groups.
Referring now to
Each of the SAS zoning expanders 36, 38, 42 typically is coupled to one or more initiator devices 12, 14, 16, 18, and coupled to one or more target devices 22, 24, 26, 28, 32, 34. The SAS zoning expanders 36, 38, 42 also can be coupled to each other, e.g., as shown. As discussed hereinabove, an SAS expander acts as a switch between SAS initiators and SAS targets, e.g., in a manner that allows multiple SAS initiators to connect to and communicate with multiple SAS targets. Thus, SAS expanders can allow SAS exchanges to be routed between any of the SAS initiator devices and any of the SAS target devices within the SAS domain 10.
Each SAS initiator device, SAS target device, and SAS zoning expander within the SAS domain 10 has one or more physical links or physical link layers, known as phys. Connections between two or more SAS devices are made through the phys of the SAS devices. Connections may be routed between SAS devices through one or more of the SAS zoning expanders 36, 38, 42. That is, each of the SAS zoning expanders 36, 38, 42 typically are configured to control whether a device phy is permitted to open a connection to or participate in a connection with another device phy. Also, the SAS zoning expanders 36, 38, 42 define or cooperate to define a zoned service delivery subsystem (ZSDS) within the SAS domain 10. Phys of a particular SAS zoning expander can be assigned a particular zone group. The SAS zoning expanders 36, 38, 42 can include zoning capabilities enabled according to the SAS specifications and enhanced by the features and aspects of applications according to embodiments of the invention, as will be described in greater detail hereinbelow.
For appropriate SAS domain management, devices associated with the SAS domain management architecture should be able to execute various management applications that uniquely identify various domains within the network arrangement and perform various domain management functions within those domains. For example, an application or service that manages SAS domains can be running on a zone manager or work station within the network. The SAS domain management application or service can be connected to a single domain via an in-band connection, e.g., through an SAS host bus adapter (HBA) resident on the zone manager and/or the workstation. Alternatively, the SAS domain management application or service can be connected via an out-of-band connection, e.g., over an Ethernet connection to an expander or switch. According to embodiments of the invention, an SAS domain management application or service can include an SAS zoning management application with connector grouping, e.g., a connector grouping application that includes one or more specialized algorithms (or wizards), residing at least partially within the zone manager and/or the work station.
For example, referring now to
Alternatively, referring now to
One or more of the zone manager 52 and the work station 56 can be comprised partially or completely of any suitable structure or arrangement, e.g., one or more integrated circuits. Also, it should be understood that the zone manager 52 and the work station 56 each include other components, hardware and software (not shown) that are used for the operation of other features and functions of the respective devices not specifically described herein. All relevant portions of one or both of the zone manager 52 and the work station 56 can be partially or completely configured in the form of hardware circuitry and/or other hardware components within a larger device or group of components. Alternatively, all relevant portions of one or both of the zone manager 52 and the work station 56 can be partially or completely configured in the form of software, e.g., as processing instructions and/or one or more sets of logic or computer code. In such configuration, the logic or processing instructions typically are stored in a memory element or a data storage device. The data storage device typically is coupled to a processor or controller, and the controller accesses the necessary instructions from the data storage element and executes the instructions or transfers the instructions to the appropriate location within the respective device.
According to embodiments of the invention, SAS zoning management including connector grouping applications 54 involves allowing connectors on the edge of the ZPSDS to be grouped into any number of zones or zone configurations. These defined zone configurations then are used to create the minimal number of zone groups, and to configure the respective permissions of those zone groups.
As an example, referring now to
The method 60 includes a step 62 of determining the connectors within the SAS domain that are available for connector grouping. The connector grouping application 54 is configured to provide a list of available connectors on the edge of the ZPSDS that are available for forming or defining zones. Zones are a collection of objects, e.g., connectors who's attached (downstream) devices have visibility to one another, i.e., that are capable of communicating with one another. As part of the determining step 62, the connector grouping application 54 omits connectors within the SAS domain that are used to link expanders within the ZPSDS. Per the SAS specification, within an SAS domain, connectors that are used to link expanders within the ZPSDS must be placed into a specific zone group (e.g., Zone Group 1) and therefore are not to be configured. Accordingly, such connectors are not available for connector grouping according to embodiments of the invention.
The method 60 also includes a step 64 of defining zones. The connector grouping application 54 is configured to bundle connectors into various zones by selecting one or more connectors from the list of available connectors. As discussed herein, a zone is a collection of connectors or other objects that have visibility with one another, i.e., have the potential or capability to communicate with one another. The bundling of available connectors into various zones can be performed using any suitable criteria.
As part of the step 64 of defining zones, multiple zones can be defined, e.g., to fulfill zoning requirements. For example, an administrator may segment an SAS domain by dividing the connectors into zones. Also, as part of the step 64 of defining zones, one or more of the defined zones can overlap by placing a connector in multiple zones.
Once all of the appropriate zones for the SAS domain have been defined, the connector grouping application 54 then determines the minimal number of zone groups, and their respective permissions, to realize the zone definitions. This process initially involves creating one zone group per each defined zone, populating each zone group with the phys associated with the connectors in the particular defined zone, and configuring the permissions for the phys in the created zone group to communicate with each other.
In this manner, the method 60 includes a step 66 of identifying one of the defined zones. As will be discussed in greater detail hereinbelow, the method 60 eventually will loop through or identify all of the defined zones and perform a series of steps for each identified zone. The method 60 includes a step 68 of creating a zone group for the identified zone. The zone group creating step 68 creates only one zone group for the identified zone and, as will be seen from further discussion hereinbelow, only one zone group is created for each zone.
The method also includes a step 72 of populating the created zone group with appropriate connector phys. Once a zone group has been created for the identified zone, the populating step 72 populates the created zone group with the phys associated with the connectors in the zone for which the zone group was created.
The method also includes a step 74 of configuring permissions for the phys in the particular zone group. Once the created zone group has been populated with the appropriate connector phys, i.e., the phys associated with the connectors in the zone for which the zone group was created, the configuring step 74 configures the permissions for those phys in such a way that each phy in the zone group has permission to communicate with all other phys in the zone group.
The method 60 also includes a step 76 of determining whether or not all defined zones in the SAS domain have been identified for zone group creation and phys population, and for permissions configuration. If not all defined zones in the SAS domain have been identified so that a corresponding zone group can be created therefor (N), the method 60 moves to another defined zone in the SAS domain, as shown generally by a “next zone” step 78. Then, the process of identifying the zone (step 66), creating one zone group for the identified zone (step 68), populating the zone group with the appropriate connector phys (step 72) and configuring the permissions for zone group phys (step 74) is performed for the particular defined zone. This process is repeated for all defined zones in the SAS domain. Returning to the decision step 76, if all defined zones in the SAS domain have been identified and subsequent zone group creation, connector phys population and permission configuration have been performed (Y), the method 60 proceeds to the steps involved in the process of comparing all zone groups with all other zone groups, e.g., as shown in
Referring now to
The comparing step 82 compares the phys of the current zone group with the phys of a particular remaining zone group in the SAS domain. The comparing step 82 is looking for phys that reside in both the current zone group and the particular remaining zone group. In this manner, the method 60 includes a step 84 of determining whether or not there are any phys common to both the current zone group and the particular remaining zone group being compared with the current zone group. If the determining step 84 determines that there are no phys common to both the current zone group and the particular remaining zone group (N), the method 60 continues to a step 86 of determining whether or not all remaining zone groups have been compared with the current zone group.
If the determining step 84 determines that there are phys common to both the current zone group and the particular remaining zone group (Y), the method 60 performs a step 88 of creating a new zone group for the common phys. The method 60 then performs a step 92 of moving the phys common to both the current zone group and the particular remaining zone group to the new zone group that was just created by the zone group creating step 88.
The method 60 also includes a step 94 of configuring permissions for the phys just moved to the newly created (common phys) zone group. Once the method 60 performs the step 92 of moving the phys common to both the current zone group and the particular remaining zone group to the newly created (common phys) zone group, the configuring step 94 configures the appropriate permissions for those common phys in such a way that each of the common phys in the newly created (common phys) zone group has permission to communicate with all other phys in the newly created (common phys) zone group, and with the remaining phys in both the current zone group and the particular remaining zone group.
The method 60 also includes a step 96 of transferring all permissions from either one or both of the zone groups from which the common phys were removed, if that particular zone group has become empty of phys as a result of the removal of the common phys to the newly created (common phys) zone group. That is, if all of the phys in the current zone group were common to at least a portion of the phys in the particular remaining zone group to which the current zone group was compared, the removal of those common phys from the current zone group to the newly created (common phys) zone group will leave the current zone group empty. In such case, the transferring step 96 will transfer all permissions from the current zone group to the newly created (common phys) zone group. Similarly, if all of the phys in the particular remaining zone group were common to at least a portion of the phys in the current zone group to which the particular remaining zone group was compared, the removal of those common phys from the particular remaining zone group to the newly created (common phys) zone group will leave the particular remaining group empty. In such case, the transferring step 96 will transfer all permissions from the particular remaining group to the newly created (common phys) zone group. The method 60 then returns to the determining step 86.
If the determining step 86 determines that not all remaining zone groups have been compared to the current zone group (N), the method 60 moves to another remaining zone group, as shown generally by a “next remaining zone group” step 98. Then, the zone group comparison process continues with the comparison step 82 comparing the current zone group with the next (another) remaining zone group. This comparison process continues until the current zone group has been compared with all remaining zone groups.
If the determining step 86 determines that all remaining zone groups have been compared to the current zone group (Y), the method 60 continues to a step 102 of determining whether or not all zone groups have been designated as a current zone group for purposes of being compared with all remaining zone groups. If the determining step 102 determines that not all zone groups have been designated as a current zone group, and therefore have not gone through the process of being compared with all remaining zone groups (N), the method 60 performs a step 104 of designating another or the next zone group as the current zone group for purposes of comparison with the remaining zone groups.
The method 60 then returns to the comparing step 82 with the new current zone group. The process of comparing the current zone group with all remaining zone groups continues, e.g., as discussed hereinabove, until all zone groups have been a current zone group and compared with all remaining zone groups. If the determining step 102 determines that all zone groups have been designated as a current zone group, and therefore gone through the process of being compared with all remaining zone groups (Y), the method 60 performs a step 106 of transmitting all zone group information and corresponding permissions to the zone manager 52. That is, the transmitting step 106 transmits all information associated with all zone groups, and the corresponding permissions of all zone groups, to the zone manager 52.
As discussed hereinabove, the SAS connector grouping management application described herein simplifies the work of an SAS domain administrator, e.g., by allowing an SAS domain administrator to interface with the particular SAS zoning application without requiring the administrator to deconstruct the zoning requirements down to the phy level. The connector grouping applications allow connectors on the edge of the ZPSDS to be grouped into any number of defined zones, and these defined zone then are used to create the minimal number of zone groups, and to configure the respective permissions of those zone groups.
Referring now to
Initially, four zone groups zg01, zg02, zg03 and zg04 were created and populated with the phys associated with connectors resident in their respective zones z01, z02, z03 and z04. According to embodiments of the invention, the connector grouping application 54 identifies phys, and their associated connectors, in the intersecting regions. That is, for example, the connector02 is identified as residing in the first zone group zg01 and also in the second zone group zg02, the connector04 is identified as residing in the second zone group zg02 and in the third zone group zg03, and the connector06 is identified as residing in the third zone group zg03 and in the fourth zone group zg04.
As discussed hereinabove, the phys identified as residing in the more than one zone group are moved to a newly created zone group. Therefore, the connector02 will be moved to a new (fifth) zone group zg05. Also, the connector04 will be moved to a new (sixth) zone group zg06, and the connector06 will be moved to a new (seventh) zone group zg07.
It will be apparent to those skilled in the art that many changes and substitutions can be made to the embodiments of the invention herein described without departing from the spirit and scope of the invention as defined by the appended claims and their full scope of equivalents.
