Abstract:
A method of validating a storage array network deployment includes receiving information from a user, utilizing the information in a capacity associated with the storage array network, and notifying the user if the utilizing produces an error. The method may further include waiting for user direction before utilizing the information, or waiting until a predetermined amount of information has been received before utilizing the information. The method may further include evaluating one or more formats of the information for suitability for an intended use of the information. The error may be indicated by an abnormal response as a result of utilizing the information.

Description:
BACKGROUND OF THE INVENTION 
       [0001]    As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. 
         [0002]    An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. 
         [0003]    Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. 
         [0004]    The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use, such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems. 
         [0005]    The data storage systems may be configured as a Storage Area Network (SAN). SAN environments are generally quite complex, so network professionals must have extensive knowledge of networking principals to properly deploy a SAN. Even experienced technicians and/or engineers may introduce errors into a deployment. For example, an incorrect value for a field may be entered through a typing error or transcription error, which can lead to poor SAN performance. Such a seemingly minor issue may require many hours of troubleshooting to resolve. Examples of such fields include server addresses, SYSLOG server identification, wrong SNMP server identification, among others. 
         [0006]    Many other potential configuration errors exist. For example, components may have been physically connected incorrectly, or required connections may be missing. 
         [0007]    Further, configurations may change over time. Such changes introduce an opportunity for a set-up error. 
         [0008]    There is currently no easy way to confirm that a SAN is properly configured, following an initial setup or after a configuration change. 
       SUMMARY OF THE INVENTION 
       [0009]    The described embodiments provide a validation procedure that may be executed during or after an initial SAN setup, or when a reconfiguration of the SAN occurs. The described embodiments may notify a maintainer of the SAN if conflict or errors are detected. 
         [0010]    The described embodiments may evaluate a configuration state of devices that make up the SAN, along with devices otherwise associated with the SAN, such as the customer&#39;s email server, syslog server, SNMP server, among others. 
         [0011]    As additional storage arrays are added to the group, the described embodiments may compare new information against the current (i.e., running) configuration, and the customer will be notified if they&#39;ve misconfigured any of their IP addresses, subnet masks, or gateways. 
         [0012]    In one aspect, the invention is a method of validating a network deployment, including utilizing deployment information received from the user upon receiving direction from the user to validate the network deployment. The method further includes notifying the user if the utilizing deployment information produces an abnormal response. 
         [0013]    In one embodiment, utilizing deployment information received from the user includes applying a server IP address. In another embodiment, utilizing deployment information received from the user may include one or more of applying a subnet mask, applying a default gateway, applying a domain name server address, and applying a network time protocol. 
         [0014]    In one embodiment, an abnormal response includes a mismatched subnet. In another embodiment, an abnormal response includes an incorrect gateway. 
         [0015]    In one embodiment, the method further includes comparing one or more set-up parameters for an existing network to corresponding set-up parameters of a newly-added network, and notifying the user if a mismatch is determined to exist. In another embodiment, the notifying further includes disclosing one or more aspects of the abnormal results. 
         [0016]    In another aspect, the invention is a method of validating a storage array network deployment, including receiving information from a user, utilizing the information in a capacity associated with the storage array network, and notifying the user if the utilizing produces an error. 
         [0017]    One embodiment further includes waiting for user direction before utilizing the information. Another embodiment further includes waiting until a predetermined amount of information has been received before utilizing the information. Another embodiment further includes evaluating one or more formats of the information for suitability for an intended use of the information. 
         [0018]    In one embodiment, the error includes detecting an abnormal response as a result of utilizing the information. In one embodiment, notifying further includes disclosing one or more aspects of the error. 
         [0019]    In another aspect, the invention is a non-transitory computer-readable medium with computer code instruction stored thereon, the computer code instructions when executed by an a processor cause an apparatus to receive information from a user, utilize the information in a capacity associated with the storage array network, and notify the user if the utilizing produces an error. 
         [0020]    In one embodiment, the computer code instructions, when executed by a processor, further cause the apparatus to wait for user direction before utilizing the information. In another embodiment, the computer code instructions when executed by an a processor further cause the apparatus to wait until a predetermined amount of information has been received before utilizing the information. In another embodiment, the computer code instructions when executed by an a processor further cause the apparatus to evaluate one or more formats of the information for suitability for an intended use of the information. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0021]    The foregoing will be apparent from the following more particular description of example embodiments of the invention, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating embodiments of the present invention. 
           [0022]      FIG. 1  illustrates an embodiment of a procedure for validating a storage array network (SAN) according to the invention. 
           [0023]      FIG. 2A  is a schematic view of a computer network environment in which an embodiment of the present invention may be implemented. 
           [0024]      FIG. 2B  ( FIGS. 2B-I  and  2 B-II) is a block diagram view of another computer network environment in which an embodiment of the present invention may be implemented. 
           [0025]      FIG. 3  illustrates one example of a SAN validation process constructed and arranged according to the invention. 
       
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
       [0026]    A description of example embodiments of the invention follows. 
         [0027]    One embodiment of a procedure for validating a storage array network (SAN) is depicted in  FIG. 1 . At the start  102  of the procedure, input (i.e., information) from a user is received  104 . The input may include a value or values, a text string, a check box or radio button selection, or any other type of information-conveying entity known in the art. In one embodiment, the input is received in response to some stimulus, e.g., a request for such information. In other embodiments, the input is received spontaneously from an information source, not in response to any request or other stimulus. 
         [0028]    In one embodiment, receiving  104  input from a user may be part of an initial SAN setup procedure, i.e., when a SAN with an initial storage array is first assembled and connected to a host. In another embodiment, the receiving  104  input from a user may be part of an augmented SAN deployment, where one or more additional storage arrays are added to an existing SAN. 
         [0029]    The received input is utilized  106  in the SAN as, for example, a network parameter. The result of the utilization may result in an error. If no error results  108   a,  the procedure for validating the SAN ends  112 . If the utilized input produces an error  108   b,  the user is notified that an error was produced and the procedure for validating the SAN ends  112 . Utilizing input information, when the input is received, may identify physical misconnections, typographical or transcription errors and other such user input errors, at the time of SAN deployment or augmentation. 
         [0030]    The determination of whether or not utilizing an input produces an error may depend on any one of, or a combination of, a number of different criteria. Part of the determination may include simply evaluating whether the input format is appropriate for the intended utilization. For example, a hexadecimal value would not be appropriate for use as an IP address. Similarly, a pure number value would be inappropriate for use in a field that calls for a text string. 
         [0031]    Part of the determination may include actively utilizing the input, and evaluating whether the expected response to the utilization occurs (i.e., that the input actually works for its intended purpose). Examples of input that may be utilized to determine if the input works for its intended purpose include (1) IP address, (2) Subnet mask, (3) Default gateway, (4) Domain Name Server (DNS), (5) Network Time Protocol (NTP), (6) server addresses, (7) SYSLOG server, among others known to be associated with a SAN deployment. 
         [0032]    In one embodiment, the determination ( 108   a,    108   b ) of whether utilization of an input causes an error to occur is made each and every time the input (or an updated input) is received. In some embodiments, the determination ( 108   a,    108   b ) is made as the input is received. In other embodiments, the determination ( 108   a,    108   b ) is made for two or more inputs as a batch. The batch determination may be made upon user initiation, upon a predetermined threshold number of inputs being received, or upon other suitable criteria. 
         [0033]    The determination ( 108   a,    108   b ) may evaluate appropriate configuration of associated devices such as (1) email server, (2) SYSLOG server, (3) SNMP server, among others, so that potential problems may be identified as part of the deployment. 
         [0034]    For an augmented SAN deployment, where one or more additional storage arrays are added to an existing SAN, input from a user may relate to information unique to the additional storage arrays. The input in this case may need to be compatible with the currently running SAN configuration (i.e., the SAN configuration that the additional storage arrays will be augment), so that the input may be compared to corresponding parameters from the existing SAN configuration. 
         [0035]      FIG. 2A  illustrates a computer network environment  200  in which an embodiment of the present invention may be implemented. The computer  241  and the sets  222 A,  222 B,  222 C of one or more storage devices (each one of the sets  222 A,  222 B,  222 C representing one or more storage devices) are linked through network  242 . The computer  241  and the sets  222 A,  222 B,  222 C of one or more storage devices may be connected through any network as is known in the art, including a storage area network (SAN), a wide area network (WAN) or local area network (LAN). The computer  241  may embody an Information Handling System (IHS)  320  (referring to  FIG. 3  to follow) and/or any embodiment of the IHS described herein. While three sets  222 A,  222 B,  222 C of storage devices are depicted, the computer network environment  200  may comprise any number of storage devices. 
         [0036]    As illustrated in  FIG. 2B  ( FIGS. 2B-I  and  2 B-II), in one embodiment, the present invention may run on a network  201  that may include, but is not limited to, a storage area network (SAN)  203  and a local area network (LAN)  202 . The LAN  202  may include components such as one or more clients  201   a,    201   b,    201   c,    201   d  that communicate through one or more network switches  205   c,    205   d  to one or more network interface cards (NICs)  207   e,    207   f ,  207   g,    207   h  to one or more servers  210   a,    210   b.  The SAN  203  may include, but is not limited to, an internet protocol (IP) SAN. The SAN  203  may include components such as one or more servers  210   a,    210   b  that communicate to one or more network switches  205   a,    205   b  through a set of one or more network interface cards (NICs)  207   a,    207   b,    207   c,    207   d.  Network switches  205   a ,  205   b  of the storage area network  203  may communicate to Peer Storage (PS) series arrays  220   a ,  220   b  across the SAN  203 . Therefore, the SAN  203  may include components such as a PS series group  222  that may include, but is not limited, to, storage groups  221   a,    221   b  and PS series data arrays  220   a,    220   b.  The PS series group  222  may include a given set (referring to each of  222 A,  222 B, and  222 C of  FIG. 2A ) of storage devices. In an alternative embodiment, the SAN  203  may be considered to include the LAN  202  and the above-mentioned components with which the LAN  202  communicates, in addition to the above-mentioned components with which the SAN  203  communicates. 
         [0037]      FIG. 3  illustrates one example of a SAN validation process according to the embodiments described herein. After or during the SAN set up process, a user (e.g., SAN customer) chooses  304  to validate the set up. During or after completion of the validation process, the user may receive an alert  306  identifying any invalid network configurations. The user may further receive validation results  308  regarding configured devices. If no further arrays are being added  310 , the user is notified that the configuration is valid  312  and the validation process ends  314 . 
         [0038]    If one or more arrays are being added  316 , any new information relating to the added arrays are compared  318  against the existing configuration for validity. If a configuration mismatch exists  320 , the user is notified of the mismatch  322  and the process ends  314 . The user may also receive information concerning the nature of the mismatch to aid in correcting the problem. If no configuration mismatch exists, the user is notified that the configuration is valid  326  and the validation process ends  314 . 
         [0039]    For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, calculate, determine, classify, process, transmit, receive, retrieve, originate, switch, store, display, communicate, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, or other purposes. For example, an information handling system may be a personal computer (e.g., desktop or laptop), tablet computer, mobile device (e.g., personal digital assistant (PDA) or smart phone), server (e.g., blade server or rack server), a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include random access memory (RAM), one or more processing resources such as a central processing unit (CPU) or hardware or software control logic, ROM, and/or other types of nonvolatile memory. Additional components of the information handling system may include one or more disk drives, one or more network ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, touchscreen and/or a video display. The information handling system may also include one or more buses operable to transmit communications between the various hardware components. 
         [0040]    It will be apparent that one or more embodiments described herein may be implemented in many different forms of software and hardware. Software code and/or specialized hardware used to implement embodiments described herein is not limiting of the embodiments of the invention described herein. Thus, the operation and behavior of embodiments are described without reference to specific software code and/or specialized hardware—it being understood that one would be able to design software and/or hardware to implement the embodiments based on the description herein. 
         [0041]    Further, certain embodiments of the example embodiments described herein may be implemented as logic that performs one or more functions. This logic may be hardware-based, software-based, or a combination of hardware-based and software-based. Some or all of the logic may be stored on one or more tangible, non-transitory, computer-readable storage media and may include computer-executable instructions that may be executed by a controller or processor. The computer-executable instructions may include instructions that implement one or more embodiments of the invention. The tangible, non-transitory, computer-readable storage media may be volatile or non-volatile and may include, for example, flash memories, dynamic memories, removable disks, and non-removable disks. 
         [0042]    While this invention has been particularly shown and described with references to example embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention encompassed by the appended claims.