Method and system for validating logical end-to-end access paths in storage area networks
First Claim
1. A process for validating a state of a storage area network (SAN), comprising:
- defining a SAN access path policy representative of SAN logical access paths, said SAN logical access paths defining end-to-end access relationship between an application on a server and data LUNs stored on storage devices in the SAN and having logical access path attributes with attribute values, collecting configuration information from devices of the SAN, standardizing formats of the configuration information and reconciling any conflicts, processing the collected configuration information to identify the SAN logical access paths, and computing the associated attribute values, comparing the identified SAN logical access paths and computed attribute values with the SAN access path policy to identify any logical path discrepancies or violations.
4 Assignments
0 Petitions
Accused Products
Abstract
A method and system for validating logical access path in a storage area network is provided. It supports definition of a SAN access path policy that represent which application to data LUN logical access paths should not exist, which should exist, and what should be the end-to-end attributes of each. It performs the SAN-customized graph-based validation algorithm based on information it collects automatically from devices distributed across the SAN using a variety of non-intrusive mechanisms. It enables to identify violations of actual logical access paths relative to the required access paths as determined by the policy. It enables notification about violations, with all their relevant context information, to the appropriate target recipient using a variety of means.
102 Citations
16 Claims
-
1. A process for validating a state of a storage area network (SAN), comprising:
-
defining a SAN access path policy representative of SAN logical access paths, said SAN logical access paths defining end-to-end access relationship between an application on a server and data LUNs stored on storage devices in the SAN and having logical access path attributes with attribute values, collecting configuration information from devices of the SAN, standardizing formats of the configuration information and reconciling any conflicts, processing the collected configuration information to identify the SAN logical access paths, and computing the associated attribute values, comparing the identified SAN logical access paths and computed attribute values with the SAN access path policy to identify any logical path discrepancies or violations. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A process for validating a state change event of a storage area network (SAN), comprising:
-
defining a SAN access path policy representative of SAN logical access paths, defining a SAN state based on SAN logical access paths and attribute values associated with the logical access paths, obtaining SAN event description information, and comparing the SAN event description information with the SAN state to identify a any logical path discrepancies or violations. - View Dependent Claims (12, 13, 14)
-
-
15. A storage area network (SAN) validation manager, comprising:
-
a policy engine that stores a SAN access path policy representative of SAN logical access paths, said SAN logical access paths defining end-to-end access relationship between an application on a server and data LUNs stored on storage devices in the SAN and having logical access path attributes with attribute values, a validation engine that collects configuration information from devices of the SAN, standardizes formats of the configuration information and reconciles any conflicts, The validation engine further processing the collected configuration information to identify the SAN logical access paths and computing the associated attribute values, and comparing the identified SAN logical access paths and computed attribute values with the SAN access path policy to identify any logical path discrepancies or violations. - View Dependent Claims (16)
-
Specification