Western Digital OpenFlex Data24 3200 User Manual page 27

User Guide
f. SPDK initiator running on the host is not supported on all host configurations. Please contact
Western Digital for supported configurations.
g. Extended metadata on 4k and 512B block sectors is not supported.
3. OCAPI and GUI related:
a. Maximum of one GUI or OCAPI client per enclosure is supported. Launch one GUI to display one
dashboard and up to one device page.
b. Only basic authentication is supported.
c. The Web Client needs to operate with the HTTP Conditional capability provided by the Web
Service. If the client does not, it may see a "precondition failed" error, match HTTP Conditional
capability.
d. Daylight Savings Time (DST) field under system clock will always be disabled.
e. TLS certification file size cannot exceed 4K when uploaded through in-band management.
f. Maximum of one openflex-api installed server in one subnet for managing up to three enclosures
via in-band.
g. When using In-Band GUI enclosure management, the first MI Device that is nvme connected in
the in-band setup process determines which controller (IOM) MI Device is used for the GUI Device
Page information via the OpenFlex API. Management through the other IOM requires changing the
first MI Device connected or switch to the Out-of-Band IP on the other controller IOM. Generally
either IOM can be used for enclosure management. Refer to the
for the In-Band Management setup and usage instructions.
h. When creating accounts for In-Band Management, setup the user credentials to be the same on
both the compute and storage nodes (MAT-4719).
i. When using In-Band enclosure management, if the enclosure is put into low power sleep mode, the
power must be restored back on through the out-of-band management port.
j. The OCAPI interface with the option stream=True may exceed all the available file handles. Explicitly
close the connection if you are using stream=True. This issue does not exist when using cURL
(MAT-3874).
k. Sensor threshold names are abstracted to the CIM model naming convention and the enclosure
status more closely follows VITA-40 status reporting.
l. OCAPI consistently returns HTTP code 429 even if there are no known outstanding connections
4. Enclosure related:
a. IPv6 networking is not supported.
b. VLAN tagging is not supported.
c. Hot swap one CRU at a time.
d. Factory or reset pinhole when the enclosure is in low-power mode is not supported.
1. Overview
1.9 Limitations & Restrictions
section
Management (page 103)
19