Methods and apparatus for synchronizing configuration data

• US 7,934,018 B1
• Filed: 09/30/2004
• Issued: 04/26/2011
• Est. Priority Date: 09/30/2004
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Lavallee, James E., Dubrovsky, Alexander, Gauvin, Francois
• Primary Examiner(s): Nguyen; Phuoc
• Assistant Examiner(s): Sikri; Anish
• Application Number:
  US10/954,992
• Time in Patent Office: 2,399 Days
• Field of Search: 707/201, 709/248, 709/218, 709/229, 709/238
• US Class Current: 709/248
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/1097 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]

Abstract

An agent in a storage area network stores a first identifier (e.g., a checksum value) for first zone configuration data previously used to configure a zone in the storage area network. The agent derives the first identifier from contents of the first zone configuration data. Further, the agent retrieves second zone configuration data presently used to configure the zone in the storage area network. The second zone configuration data is potentially different than the first zone configuration data. Based on contents of the second zone configuration data, the agent then produces a second identifier for the second zone configuration data. The agent then compares the first identifier and the second identifier to identify whether the first zone configuration data is different than the second zone configuration data. A user can control behavior of zoning importation and activation depending whether current zone configuration data has been changed.

Claims

1. A method for synchronizing zone configuration data in a storage area network, the method comprising:

storing a first identifier for first zone configuration data previously used to configure a zone in the storage area network, the first identifier derived from contents of the first zone configuration data;

retrieving second zone configuration data presently used to configure the zone in the storage area network, the second zone configuration data potentially being different than the first zone configuration data previously used to configure the zone;

producing a second identifier for the second zone configuration data, the second identifier being derived from contents of the second zone configuration data; and

comparing the first identifier and the second identifier to identify if the first zone configuration data is different than the second zone configuration data.

2. A method as in claim 1 further comprising:

receiving a command from a user attempting modification of a current configuration of the zone via application of user generated zone configuration data, the user generated zone configuration data being a user modified version of the first zone configuration data;

wherein comparing the first identifier and the second identifier further includes identifying that the second zone configuration data of the zone does not match the first zone configuration data; and

in response to the identifying, notifying the user that the zone is no longer configured according to the first zone configuration data.

3. A method as in claim 2 further comprising:

receiving a command from the user to configure the zone via use of the user generated zone configuration data; and

based on receipt of the command, applying the user generated zone configuration data to configure the zone even though the zone is no longer configured according to the first zone configuration data.

4. A method as in claim 1, wherein steps of retrieving and comparing are performed in response to a request by a zone configuration manager process, which is controlled by a user, to modify configuration settings of the zone;

and

notifying the zone configuration manager process that a corresponding configuration of the zone has been modified since application of the first zone configuration data to configure the zone, the zone configuration manager process in turn providing an alert message to the user attempting to modify the zone that the zone has already been modified by a zone modification process other than that initiated by the user.

5. A method as in claim 1, wherein comparing the first identifier and the second identifier further involves identifying that the second zone configuration data currently applied to the zone does not match the first zone configuration data previously applied to the zone, the method further comprising:

generating a list of differences between the first zone configuration data and the second zone configuration data; and

notifying an application controlled by the user of the differences so that the user can identify changes to the zone following configuration of the zone according to the first zone configuration data.

6. A method as in claim 1, wherein comparing the first identifier and the second identifier results in identifying that the zone is presently not configured according to the first zone configuration data, the method further comprising:

receiving a command from the user to produce merged zone configuration data based on third zone configuration data provided by the user and the second zone configuration data; and

configuring the zone with the merged zone configuration data.

7. A method as in claim 1 further comprising:

prior to the storing, applying a processing function to the contents of the first zone configuration data to derive the first identifier, the first identifier being a first unique value, the processing function deriving different unique values for different zone configuration data;

wherein producing the second identifier includes applying the processing function to the contents of the second zone configuration data to derive the second identifier, the second identifier being a second unique value;

wherein storing the first identifier includes maintaining an indication that the zone has been initially configured with the contents of the first zone configuration data; and

wherein comparing includes detecting that the first identifier is not equal to the second identifier indicating that the zone is configured with the second zone configuration data, the second zone configuration data being different than the first zone configuration data.

8. A method as in claim 1 further comprising:

identifying a difference between the first zone configuration data and the second zone configuration data; and

applying a set of merging rules to detect whether the first zone configuration data and the second zone configuration data can be merged into a single set of zone configuration data for configuring the zone;

wherein applying the set of merge rules includes;

identifying that contents of the first zone configuration data includes a port of a respective switch that is not specified by the contents of the second zone configuration data;

producing merged zone configuration data based on combining of the contents of the first zone configuration data with the contents of the second zone configuration data, the merged zone configuration data including the port as a member; and

reconfiguring the zone to include the port of the respective switch as specified by the merged zone configuration data.

9. A method as in claim 8 further comprising:

identifying a difference between the first zone configuration data and the second zone configuration data; and

applying a set of merging rules to detect whether the first zone configuration data and the second zone configuration data can be merged into a single set of zone configuration data for configuring the zone;

wherein applying the set of merge rules includes;

identifying that contents of the first zone configuration data is consistent with contents of the second zone configuration data;

producing merged zone configuration data based on combining of the contents of the first zone configuration data with the contents of the second zone configuration data; and

reconfiguring the zone based on the merged zone configuration data.

10. A method as in claim 1 further comprising:

configuring the zone with the first zone configuration data prior to retrieving the second zone configuration data; and

wherein retrieving the second zone configuration data includes communicating with a switch resource of the storage area network that implements the zone, the switch resource implementing the zone to support a logical path between a host resource and a storage resource of the storage area network.

11. A method as in claim 1, wherein the first zone configuration data is different than the second zone configuration data, the method further comprising:

based on the comparing, detecting that the first identifier is not equal to the second identifier;

providing notification to a user that the zone has been configured by a source other than the user; and

providing notification to the user that the zone has been reconfigured with the second zone configuration data subsequent to a time of the zone being configured with the first zone configuration data.

12. A method as in claim 11, wherein the first identifier is a first checksum value derived from the contents of the first zone configuration data, and wherein the second identifier is a second checksum value derived from the contents of the second zone configuration data, the method further comprising:

providing the user with an option of reviewing differences between the first zone configuration data and the second zone configuration data.

13. A method as in claim 12 further comprising:

based on input from the user, updating a repository of configuration information associated with the user to include the second zone configuration data to indicate that the zone is currently configured in accordance with the second zone configuration data.

14. A method as in claim 13, wherein multiple different sources in a storage area network environment compete to modify the zone, the multiple different sources including the user and the source other than the user.

15. A method as in claim 1, wherein the first zone configuration data is identical to the second zone configuration data, the method further comprising:

based on the comparing, detecting that the first identifier is equal to the second identifier;

providing notification to a user that there has been no configuration changes to the zone since configuring of the zone with the first zone configuration data; and

utilizing new zone configuration data provided by the user to configure the zone.

16. A method as in claim 1 further comprising:

applying a processing function to the contents of the first zone configuration data to derive the first identifier, the first identifier being a first unique value;

wherein storing the first identifier includes storing an indication that the zone has been initially configured with the first zone configuration data;

wherein producing the second identifier includes applying the processing function to contents of the second zone configuration data to derive the second identifier, the second identifier being a second unique value; and

wherein comparing includes detecting that the first identifier is not equal to the second identifier indicating that configuration of the zone has changed since configuring the zone with the first zone configuration data.

17. A method as in claim 1 further comprising:

in response to detecting that the first identifier is different than the second identifier, providing notification that a configuration of the zone has changed since configuration of the zone with the first zone configuration data.

18. A method as in claim 17 further comprising:

applying a processing function to the contents of the first zone configuration data to derive the first identifier, the first identifier being a first unique checksum value; and

wherein producing the second identifier includes applying the processing function to the contents of the second zone configuration data to derive the second identifier, the second identifier being a second unique checksum value.

19. A computer system associated with a storage area network, the computer system comprising:

a processor;

a memory unit that stores instructions associated with an application executed by the processor; and

an interconnect coupling the processor and the memory unit, enabling the computer system to execute the application and perform operations of;

storing a first identifier for first zone configuration data previously used to configure a zone in the storage area network, the first identifier derived from contents of the first zone configuration data;

retrieving second zone configuration data presently used to configure the zone in the storage area network, the second zone configuration data potentially being different than the first zone configuration data previously used to configure the zone;

producing a second identifier for the second zone configuration data, the second identifier being derived from contents of the second zone configuration data; and

comparing the first identifier and the second identifier to identify if the first zone configuration data is different than the second zone configuration data.

20. A computer system as in claim 19, wherein the first zone configuration data is different than the second zone configuration data, the first identifier being a first checksum value derived from the contents of the first zone configuration data, and the second identifier being a second checksum value derived from the contents of the second zone configuration data, the computer system further performing operations of:

based on the comparing, detecting that the first identifier is not equal to the second identifier;

providing notification to a user that the zone has been configured by a source other than the user;

providing notification to the user that the zone has been reconfigured with the second zone configuration data subsequent to a time of the zone being configured with the first zone configuration data;

providing the user with an option of reviewing differences between the first zone configuration data and the second zone configuration data;

based on input from the user, updating a repository of configuration information associated with the user to include the second zone configuration data to indicate that the zone is currently configured in accordance with the second zone configuration data; and

wherein multiple different sources in a storage area network environment compete to modify the zone, the multiple different sources including the user and the source other than the user.

21. A computer system associated with a storage area network, the computer system providing:

means for storing a first identifier for first zone configuration data previously used to configure a zone in the storage area network, the first identifier derived from contents of the first zone configuration data;

means for retrieving second zone configuration data presently used to configure the zone in the storage area network, the second zone configuration data potentially being different than the first zone configuration data previously used to configure the zone;

means for producing a second identifier for the second zone configuration data, the second identifier being derived from contents of the second configuration data; and

means for comparing the first identifier and the second identifier to identify if the first zone configuration data is different than the second zone configuration data.

22. A computer program product including a hardware computer-readable storage medium having instructions stored thereon for processing data information, such that the instructions, when carried out by a processing device, enable the processing device to perform the steps of:

storing a first identifier for first zone configuration data previously used to configure a zone in the storage area network, the first identifier derived from contents of the first zone configuration data;

retrieving second zone configuration data presently used to configure the zone in the storage area network, the second zone configuration data potentially being different than the first zone configuration data previously used to configure the zone;

producing a second identifier for the second zone configuration data, the second identifier being derived from contents of the second zone configuration data; and

comparing the first identifier and the second identifier to identify if the first zone configuration data is different than the second zone configuration data.