IBM Skip to main contentUnited States
     Home  |  Products & services  |  Support & downloads  |  My account
 Select a country
 IBM Research
Dakshi Agrawal's homepage
Research interests
Publications
Presentations
Page Contact

 
Dakshi Agrawal's homepage   >   Publications   >
Policy based validation of SAN configuration

Written by: Dakshi Agrawal, James Giles, Kang-won Lee, Kaladhar Voruganti, and Khalid Filali-Adib.

Citation: In the Proceedings of IEEE International Workshop on Policies for Distributed Systems and Networks (Policy 2004), June 2004.

Copyright © (2004) by IEEE. Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit. To copy otherwise, to republish, to post on servers, or to redistribute to lists, requires prior specific permission and/or a fee.

PDF  Preprint version (202KB)
 Get Adobe® Reader®
Abstract:
Historically, storage has been directly connected to servers for fast local access and easy configuration. In recent years, storage area networks (SANs) have defined an alternative storage paradigm that allows storage to be shared among servers using fast interconnects. One of the key challenges of SAN management is the large number of configuration problems that are encountered in a typical SAN deployment. These configuration problems can be addressed by SAN management software. However, hard-coding the SAN configuration rules into the management software is not a viable option since it is not possible to easily modify or replace old configuration rules and specify new policies and guidelines. In this paper, we propose a novel policy-based SAN configuration validation system that can be used to specify, store, and evaluate configuration policies for SANs. We also introduce five new operators for collection policies that are useful for evaluating a wide variety of practical SAN configuration policies found in practice. The policy-based SAN configuration checking approach proposed in this paper is discussed within the context of device interoperability constraints. However, this approach is extensible as it can also be used to enforce performance, reliability, and security-related configuration constraints.
  About IBM  |  Privacy  |  Terms of use  |  Contact