Unique Method and System to Identify Host and Configure them in SAN Controller.
Publication Date: 2012-Feb-03
The IP.com Prior Art Database
Identify Host and Configure them in SAN Controller.
Page 01 of 8
Unique Method and System to Identify Host and Configure them in SAN Controller .
Storage Area Networks can use Fibre Channel, a dedicated storage transport protocol developed to address shortcomings attaching servers to storage using the SCSI protocol. SANs can also use an IP network to transmit the SCSI protocol using iSCSI. In addition, fibre channel networks can be connected across an IP network using the FCIP protocol and routed using the iFCP protocol. The connection of more than one SAN device together is known as a fabric
SANs were originally developed to use the fibre channel protocol. Since the original fibre channel protocol was created, other storage protocols have been developed, including iSCSI (a
protocol for propogating SCSI commands using TCP/IP networks), AoE (ATA over Ethernet, a non-routable protocol which uses Ethernet switches but does not use IP) and most recently announced, FCoE (Fibre Channel over Ethernet).
Each storage transport protocol has its own unique way of identification of Entities involved in Storage Area Network. For Entities connected using FC, it is the Worldwide port name (64 - bit WWPNs), iSCSI it is iSCSI qualified names (IQNs, EUI, IP address: ports) etc.
What is the problem with the existing SAN system shown in the Fig.1.
Page 02 of 8
In the existing system, knowledgeable administrators have to configure the disks and the host identification information (wwpn used by hosts) at storage controllers so that storage controllers can establish mapping between Hosts and the disks configured. Consider a case of FC card failures at the hosts or servers side. In this case, the new FC HBA has to be replaced at the host end and the WWPN number of the new host has to be
provided to storage controller so that the same disks that are exported to the hosts. This adds to the administration over-head for managing storage controllers as well as servers.
Each SCSI transport protocol has its own unique way of identification of Entities. Storage Volume Controller devices that support multiple protocols need to manage the configuration manually. In case multiple protocols are supported by the hosts, then the disks are to be mapped at the Volume controller end. For example, Volume controllers that use fibre channel as transport protocol use wwpn as a way of identification of the hosts. Similarly IQN and ISID form another unique identification for host/connections in case of iSCSI.
Thence Identification of Host at the Storage controller end, using the transport Identifier that hosts use to communicate with the controller is not a sufficient way to identify hosts. In our proposed system the above problems are resolved.
Prior Arts in the related field:
This above embodiment uses rules to manage the Hosts in a SAN environment. This is
different from our approach.
Point 13 and 14 is differe...