Virtualization I/O requirements
When using 5620 SAM on a Guest Operating System of a hosted Virtualized installation,
specific storage requirements must be met. For optimal performance, storage should be
either internal disks (10K or 15K RPM SAS), Fiber Channel attached storage (array or
SAN) with dedicated Fiber Channel connections between hosts and Storage Arrays, or
10Gb iSCSI using non-shared infrastructure. All storage must meet the performance
metrics provided with 5620 SAM Platform Sizing Responses. Storage I/O shares must be
set to “High” and IOPs set to “Unlimited” for best performance and low latency. The
5620 SAM Auxiliary Database is not supported on a SAN where direct attached storage is
required. Therefore, in a virtual environment, the storage requirement must be met using
direct attached disks.
Refer to
Table 3-18, “Minimum collocated throughput and latency” (p. 3-20)
for the
minimum required throughput and latency for a collocated 5620 SAM configuration.
Higher scale networks and distributed configurations may require alternate throughput
and latency targets that will be provided with the 5620 SAM Platform Sizing response
that is required for every 5620 SAM deployment.
5620 SAM includes a benchmarking utility to be used for determining the throughput and
latency of the storage device to be used with the virtual server hosting 5620 SAM. The
utility is installed with a 5620 SAM Server in the
/opt/5620sam/server/nms/bin/unsupported/5620_SAM_IOTest directory and is called
5620_SAM_IOTest.pl. If 5620 SAM has not yet been installed, the utility can be obtained
from Alcatel-Lucent or from the 5620 SAM software package.
Executing the utility with the -h flag will present the user with a help menu, explaining
different options and presenting execution examples. Each mount point must be tested
and must meet the throughput and latency requirements for the specific deployment.
These throughput and latency requirements must be obtained from Alcatel-Lucent as they
are specific to each deployment. The throughput and latency targets must be met,
irrespective of any other activity on the underlying storage device and the targets must be
achievable concurrently. For this reason, it is important to understand the underlying
storage configuration to ensure that the output of the benchmarking utility is interpreted
correctly. For example, each of the listed targets may be achievable using a single 10K
RPM SAS disk but concurrently, the listed targets would not be achievable using the same
single 10K RPM SAS disk. The performance of 5620 SAM would be degraded using this
configuration.
Table 3-18
Minimum collocated throughput and latency
Mount Point
Read (MB/s)
Write (MB/s)
Latency (ms)
/opt/5620sam
37
15
< 1.0
/opt/5620sam/server/xml_output
37
15
< 1.0
/opt/5620sam/dbbackup
14
21
< 1.0
Platform requirements
Storage considerations
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
3-20
5620 SAM
3HE-09809-AAAG-TQZZA 13.0 R7
Issue 1
December 2015
