Detecting configuration inconsistency in storage networks

• US 7,349,961 B2
• Filed: 12/07/2001
• Issued: 03/25/2008
• Est. Priority Date: 12/07/2001
• Status: Expired due to Fees

• Current Assignee: Hitachi, Ltd.
• Original Assignee: Hitachi, Ltd.
• Inventors: Yamamoto, Masayuki
• Primary Examiner(s): Cardone; Jason D
• Assistant Examiner(s): Swearingen; Jeffrey R
• Application Number:
  US10/013,418
• Publication Number:
  US 20030208589A1
• Time in Patent Office: 2,300 Days
• Field of Search: 709/224, 709/223, 709/213, 709/220, 714/37
• US Class Current: 709/224
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/0859 by keeping history of different configuration generations or by rolling back to previous configuration versions
• CPC Class Codes: H04L 41/0866 Checking the configuration
• CPC Class Codes: H04L 43/0811 by checking connectivity

Abstract

The present invention provides techniques for managing configurations within centralized storage management systems. Specific embodiments provide users such as IT managers the capability to check configurations of SAN devices in a system and detect any inconsistencies. Select embodiments provide users the capability to check changes to device configurations prior to actually implementing the changes.

Claims

1. A method of managing a storage area network (SAN) at a manager running on a management server, wherein the management server is connected via a management network, separate from the storage area network, to a plurality of servers, a disk subsystem and a switch connected to the servers and disk subsystem, the plurality of servers, the disk subsystem and the switch constituting the storage area network, the method comprising, in response to a configuration change in the storage area network by an administrator:

providing a first agent on each of the servers for managing configuration of the server, each first agent capable of reporting configuration information of the server to the manager running on the management server via the management network;

providing a second agent on the disk subsystem for managing configuration of the disk subsystem, the second agent capable of reporting configuration information of the disk subsystem to the manager running on the management server via the management network;

providing a third agent on the switch for managing configuration of the switch, the third agent capable of reporting configuration information of the switch to the manager running on the management server via the management network;

collecting configuration information from each first agent, second agent, and third agent, wherein the configuration information is collected via the management network;

examining the configuration information collected, the configuration information comprising storage area network security information or storage area network switch zoning information;

detecting any inconsistencies in the configurations of the servers, switch and disk subsystem, by checking interrelationships among the servers, switch and disk subsystem based on the security information or the switch zoning information, wherein the detected inconsistencies comprise security-related inconsistencies or switch zoning-related inconsistencies;

determining a cause of the detected inconsistencies; and

storing information on the detected inconsistencies and the determined cause.

2. The method of claim 1, further comprising:

accepting input of a suggested change to at least one of configuration of the server, configuration of the disk subsystem, and configuration of the switch;

thereupon detecting an inconsistency in the configuration information collected from the first, second, and third agent and the suggested change; and

providing any inconsistency detected as a result.

3. The method of claim 2, further comprising:

receiving all input indicating whether to apply the suggested change; and

applying the suggested change if the input indicates to do so, otherwise discarding the suggested change.

4. The method of claim 1, further comprising:

receiving an indication of a failure;

determining whether the failure was a result of a hardware fault;

if the failure did not result from hardware fault, then

detecting an inconsistency in the configuration information collected from the first, second, and third agent;

for each inconsistency detected, checking a configuration history for related entries; and

providing any related entries as a result.

5. The method of claim 1, further comprising:

providing inconsistency information to users.

6. The method of claim 1, further comprising:

providing suggested changes to correct any inconsistencies.

7. The method of claim 1, further comprising:

changing at least one of configuration of one of the servers, configuration of the disk subsystem, and configuration of the switch to correct inconsistencies.

8. The method of claim 1,

wherein detecting inconsistency among the collected information comprises:

checking a consistency of masking configuration; and

checking a consistency of security configuration.

9. The method of claim 1,

wherein the step of detecting any inconsistencies comprises:

for each pair of host port ID and binding ID in a collection of masking information, checking for existence of a corresponding entry for the pair in a collection of topology information;

determining whether a masking value for the pair is consistent with existence of an entry for the pair in the topology information; and

indicating that the masking value is consistent if the masking value and the entry for the pair are consistent;

otherwise determining a source of inconsistency.

10. The method of claim 9,

wherein determining a source of inconsistency comprises:

indicating that an inconsistency arises from LUN masking prohibiting a server from accessing a logical unit even though a binding exists, if the masking value is NG and an entry exists;

otherwise determining whether binding information for the pair is inconsistent.

11. The method of claim 10,

wherein determining whether binding information for the pair is inconsistent comprises:

determining whether an entry for the pair exists in a collection of binding information; and

indicating that an inconsistency arises from LUN masking permitting a server to access a logical unit although no binding entry exists, if no entry exists;

otherwise determining whether zone information for the pair is inconsistent.

12. The method of claim 11,

wherein determining whether zone information for the pair is inconsistent comprises:

determining whether a host port and logical unit are within a single zone;

indicating that an inconsistency arises from LUN masking permitting a server to access a logical unit although server and logical tuft are in separate zones, if host port and logical unit are not within a single zone;

otherwise determining whether security information for the pair is inconsistent.

13. The method of claim 12,

wherein determining whether security information for the pair is inconsistent comprises:

determining whether a World Wide Name (WWN) associated with the host port ID is capable of accessing the logical unit;

indicating that an inconsistency arises from LUN masking permitting a server to access a logical unit although LUN security prohibits access;

otherwise indicating that the collection of topology information is internally inconsistent.

14. The method of claim 1,

wherein the step of detecting any inconsistencies comprises:

for each pair of host port ID and volume ID in a collection of security information, checking for existence of a corresponding entry for the pair in a collection of topology information;

determining whether a security value for the pair is consistent with existence of an entry for the pair in the topology information; and

indicating that the security value is consistent if the security value and the entry for the pair are consistent;

otherwise determining a source of inconsistency.

15. The method of claim 14,

wherein determining a source of inconsistency comprises:

indicating that an inconsistency arises from LUN security prohibiting a logical unit from being accessed by a server even though a binding exists, if the security value is NG and an entry exists;

otherwise determining whether zone information for the pair is inconsistent.

16. The method of claim 15,

wherein determining whether zone information for the pair is inconsistent comprises:

determining whether host port and volume are within a single zone; and

indicating that an inconsistency arises from LUN security permitting a volume to be accessed by a server although server and volume are in separate zones, if host port and volume are not within a single zone;

otherwise determining whether binding information for the pair is inconsistent.

17. The method of claim 16,

wherein determining whether binding information for the pair is inconsistent comprises:

determining whether an entry for the pair exists in a collection of binding information; and

indicating that an inconsistency arises from LUN security permitting a volume to be accessed by a server although no binding entry exists, if no entry exists;

otherwise determining whether masking information for the pair is inconsistent.

18. The method of claim 17,

wherein determining whether masking information for the pair is inconsistent comprises:

determining whether the volume is capable of being accessed by the server;

indicating that an inconsistency arises from LUN security permitting a volume to be accessed by a server although LUN masking prohibits access;

otherwise indicating that the collection of topology information is internally inconsistent.

19. A method for managing a storage area network (SAN) the storage area network comprising a server, a disk subsystem and a switch, comprising:

providing a first agent for managing configuration of the server, the first agent capable of reporting configuration information of the server to a manager running on a management server via a management network, the management server connected to the server, the disk subsystem and the switch via the management network, separate from the storage area network;

providing a second agent for managing configuration of the disk subsystem, the second agent capable of reporting configuration information of the disk subsystem to the manager running on the management server via the management network;

providing a third agent for managing configuration of the switch, the third agent capable of reporting configuration information of the switch to the manager running on the management server via the management network;

obtaining by a manager configuration information from at least one of the first agent, the second agent, and the third agent, wherein the configuration is collected via the management network;

examining the obtained configuration information, the obtained configuration information comprising storage area network security information or storage area network switch zoning information;

detecting any inconsistencies in the configurations of the server, switch and disk subsystem, by checking interrelationships among the server, switch and disk subsystem based on the security information or the switch zoning information, wherein the detected inconsistencies comprise security-related inconsistencies or switch zoning-related inconsistencies;

determining a cause of the detected inconsistencies; and

storing information on the detected inconsistencies and the determined cause.

20. A storage area network (SAN) configuration management apparatus, the storage area network comprising a server, a disk subsystem and a switch, comprising:

a first agent for managing configuration on a server, the first agent capable of reporting configuration information of the server to a manager running on a management server via a management network, the management server connected to the server, the disk subsystem and the switch via the management network, separate from the storage area network;

a second agent for managing configuration on a disk subsystem, the second agent capable of reporting the actual configuration of the disk subsystem to the manager running on the management server via the management network;

a third agent for managing configuration information on a switch, the third agent capable of reporting configuration information of the switch to the manager running on the management server via the management network;

means for collecting configuration information from at least one of the first agent, the second agent, and the third agent, wherein the configuration information is collected via the management network,

means for examining the collected configuration information, the collected configuration information comprising storage area network security information or storage area network switch zoning information;

means for detecting any inconsistencies in the configurations of the server, switch and disk subsystem, the means for detecting any inconsistencies operable to check interrelationships among the server, switch and disk subsystem based on the security information or the switch zoning information, wherein the detected inconsistencies comprise security-related inconsistencies or switch zoning-related inconsistencies;

means for determining a cause of the detected inconsistencies; and

means for storing information on the detected inconsistencies and the determined cause.

21. A computer program product for managing storage area network (SAN) configuration, the storage area network comprising a server, a disk subsystem and a switch, comprising:

code that is capable of requesting configuration information from a first agent about the server that it is managing, configuration information from the second agent about the disk subsystem that is managing, and configuration information from the third agent about the switch that it is managing;

code that obtains configuration information from at least one of the first agent about the server, the second agent about the disk subsystem, and the third agent about the switch, wherein the configuration information is collected via the management network, the management network, separate from the SAN, connecting the management server to the server, the disk subsystem and the switch;

code for examining the configuration information obtained, the configuration information comprising storage area network security information or storage area network switch zoning information;

code that detects inconsistencies in the configurations of the server, the disk subsystem and the switch, by checking interrelationships among the server, the switch and the disk subsystem based on the security information or the switch zoning information, wherein the detected inconsistencies comprise security-related inconsistencies or switch zoning-related inconsistencies;

code for determining a cause of the detected inconsistencies;

code for storing information on the detected inconsistencies and the determined cause; and

a computer readable storage medium for containing the codes.

22. A system, comprising

a storage area network (SAN);

a plurality of servers capable of accessing the SAN, the storage area network comprising a disk subsystem and a switch;

a management server, having a manager operable thereon, wherein the management server is connected to the plurality of servers, the disk subsystem and the switch via a management network separate from the SAN,

a disk subsystem; and

a switch, wherein the switch is connected to the servers and the disk subsystem;

wherein a first agent managing configuration of the server runs on each of the servers, each first agent capable of reporting configuration information of its server to the manager running on the management server via the management network,

wherein a second agent managing configuration of the disk subsystem runs on the disk subsystem, the second agent capable of reporting configuration information of the disk subsystem to the manager running on the management server via the management network,

wherein a third agent managing configuration of the switch runs on the switch, the third agent capable of reporting configuration information of the switch to the manager running on the management server via the management network,

wherein the manager collects actual configuration information from the first, second, and third agents, the actual configuration information comprising storage area network security information or storage area network switch zoning information and wherein the configuration information is collected via the management network,

wherein the manager examines the collected actual information; and

wherein the manager detects any inconsistencies in the configurations of the servers, switch and disk subsystem, by checking interrelationships among the servers, switch and disk subsystem based on the security information or the switch zoning information, the detected inconsistencies comprising security-related inconsistencies or switch zoning-related inconsistencies;

wherein the manager determines a cause of the detected inconsistencies; and

wherein the manager stores information on the detected inconsistencies and the determined cause.