Iscsi Security; Stable Operation; Quality Of Service (Qos); Figure 70 Qos - Fujitsu ETERNUS DX S5 Series Design Manual

3. SAN Functions

Stable Operation

iSCSI Security

For an iSCSI interface, the iSCSI authentication function can be used when the initiator accesses the target. The
iSCSI authentication function is available for host connections and remote copying.
The Challenge Handshake Authentication Protocol (CHAP) is supported for iSCSI authentication. For CHAP
Authentication, unidirectional CHAP or bidirectional CHAP can be selected. When unidirectional CHAP is used,
the target authenticates the initiator to prevent fraudulent access. When bidirectional CHAP is used, the target
authenticates the initiator to prevent fraudulent access and the initiator authenticates the target to prevent
impersonation.
Note that the Internet Storage Name Service (iSNS) is also supported as an iSCSI name resolution.
Stable Operation

Quality of Service (QoS)

●
QoS
The performance of a high priority server is guaranteed by configuring the performance limit of each
connected server.
When the load from one application is high in a storage integrated environment and sufficient resources to
process other operations cannot be secured, performance may be reduced.
The QoS function guarantees performance by limiting resources for applications with a low priority so that
resources are secured for high priority applications.
Sixteen priority levels of bandwidth limits (maximum performance limits) can be configured on the hosts,
CA ports, volumes, and LUN groups. The performance configuration patterns of the bandwidth limit can be
individually changed via ETERNUS Web GUI or ETERNUS CLI.
In addition, scheduled operations (when setting a bandwidth limit for hosts, CA ports, and LUN groups) are
possible by setting a duration using ETERNUS CLI.
Linking with ETERNUS SF Storage Cruiser significantly reduces the operation workload on the system
administrator when applying the QoS function because performance designing and tuning are automatically
performed.
Figure 70
Server A
Low priority
ETERNUS DX
QoS
Server B
When QoS is not applied
High priority
Processing requests
from A increase
Server A
Required performance for A
Affects the performance of B
Server B
Required performance for B
I/O performance
Because the workload for A, which has a low
priority, significantly increases, the required
performance for B cannot be maintained
When QoS is applied
Server A
Server B
High
I/O performance
Because the workload for A is lower than
the upper limit, the workload for B, which has
a high priority, can be reduced
139
The workload does not exceed
the upper limit even when
processing requests from A
increase
Workload upper limit for A
Workload upper limit for B
High
Design Guide