Module 3 Ip San, Fcoe, Nas
Module 3 Ip San, Fcoe, Nas
Module 3 Ip San, Fcoe, Nas
Sol: ISCSI is a transport layer protocol that describes how Small Computer
System Interface (SCSI) packets should be transported over
a TCP/IP network.
ISCSI, which stands for Internet Small Computer System Interface, works on
top of the Transport Control Protocol (TCP) and allows the SCSI command to
be sent end-to-end over local-area networks (LANs), wide-area networks
(WANs) or the internet.
Sol: ISCSI is a transport layer protocol that describes how Small Computer
System Interface (SCSI) packets should be transported over
a TCP/IP network.
A standard NIC with a software iSCSI initiator is the simplest and least
expensive connectivity option. It is easy to implement because most servers
come with at least one, and in many cases two, embedded NICs. It requires
only a software initiator for iSCSI functionality. Because NICs provide
TOE NIC helps alleviate this burden. A TOE NIC offloads TCP management
functions from the host and leaves only the iSCSI functionality to the host
processor.
The host passes the iSCSI information to the TOE card, and the TOE card
sends the information to the destination using TCP/IP. Although this solution
improves performance, the iSCSI functionality is still handled by a software
initiator that requires host CPU cycles.
Native topology does not have FC components. The initiators may be either
directly attached to targets or connected through the IP network. For example,
the initiators can exist in an IP environment while the storage remains in an
FC environment.
After an initiator is logged on to the network, it can access the available LUNs
on the storage array. A single array port can service multiple hosts or initiators
as long as the array port can handle the amount of storage traffic that the
hosts generate.
The Figure (b) illustrates iSCSI host connectivity to an FC storage array. In this
case, the array does not have any iSCSI ports. Therefore, an external device,
called a gateway or a multiprotocol router, must be used to facilitate the
communication between the iSCSI host and FC storage.
The gateway converts IP packets to FC frames and vice versa. The bridge
devices contain both FC and Ethernet ports to facilitate the communication
between the FC and IP environments.
Sol: Figure below displays a model of the iSCSI protocol layers and depicts the
encapsulation order of the SCSI commands for their delivery through a
physical carrier.
SCSI is the command protocol that works at the application layer of the Open
System Interconnection (OSI) model. The initiators and targets use SCSI
commands and responses to talk to each other.
The SCSI command descriptor blocks, data, and status messages are
encapsulated into TCP/IP and transmitted across the network between the
initiators and targets.
The FCIP protocol stack is shown in Figure below Applications generate SCSI
commands and data, which are processed by various layers of the protocol
stack.
The upper layer protocol SCSI includes the SCSI driver program that executes
the read-and-write commands. Below the SCSI layer is the Fibre Channel
Protocol (FCP) layer, which is simply a Fibre Channel frame whose payload is
SCSI. The FCP layer rides on top of the Fibre Channel transport layer. This
enables the FC frames to run natively within a SAN fabric environment. In
addition, the FC frames can be encapsulated into the IP packet and sent to a
remote SAN over the IP.
The FCIP layer encapsulates the Fibre Channel frames onto the IP payload
and passes them to the TCP layer as shown in the figure below. TCP and IP
are used for transporting the encapsulated information across Ethernet,
wireless, or other media that support the TCP/IP traffic.
Sol: A NAS device is optimized for file-serving functions such as storing, retrieving,
and accessing files for applications and clients. As shown in Figure below, a general-
purpose server can be used to host any application because it runs a general-
purpose operating system.
Benefits of NAS:
Sol: There are three different types of NAS implementation they are
1. Unified NAS & its Connectivity: Unified NAS performs file serving and
storing of file data, along with providing access to block-level data. It
supports both CIFS and NFS protocols for file access and iSCSI and FC
protocols for block level access. Due to consolidation of NAS-based and
SAN-based access on a single storage platform, unified NAS reduces an
organization’s infrastructure and management costs.
A unified NAS contains one or more NAS heads and storage in a single
system. NAS heads are connected to the storage controllers (SCs), which
provide access to the storage. These storage controllers also provide
connectivity to iSCSI and FC hosts. The storage may consist of different
drive types, such as SAS, ATA, FC, and flash drives, to meet different
workload requirements.
In Unified NAS Connectivity, Each NAS head in a unified NAS has front-
end Ethernet ports, which connect to the IP network. The front-end ports
provide connectivity to the clients and service the file I/O requests. Each
NAS head has back-end ports, to provide connectivity to the storage
controllers.
Sol: NAS provides file-level data access to its clients. File I/O is a high-level
request that specifies the file to be accessed. The process of handling I/O’s in
a NAS environment is as follows:
Sol: NAS uses IP network; therefore, bandwidth and latency issues associated
with IP affect NAS performance. The Various factors that affect NAS
performance at different levels follow: