How are the IP addresses assigned to both ports of the drive in the chassis assembly?
IP addresses are assigned to each port of the drives via DHCP, controlled by the storage system manager.

What is the use case of the “Version” field for an object Entry using the API?
The version field is for the one and only value for this key. You can not write more than one value by changing the version. The version check is applied to the single key/value that you are attempting to replace.
How do we obtain drive unique information from the drive?
Drive information can be obtained using the Kinetic Admin API’s getLog command, which provides information about the serial number, world wide name (WWN), and network interfaces (IP address). Learn more about the Kinetic Admin and Client API by viewing the Javadoc.
Can I use a Kinetic HDD in my current conventional SAS chassis?
While the interface connector and form factor of Kinetic HDDs look identical to conventional HDDs, Kinetic HDDs are designed with an Ethernet interface which is the backbone of the cloud data center. Kinetic HDDs work only in specially designed chassis which support an Ethernet backplane and host connection.
Is there an emulator that can be used for the Kinetic API?
Yes, please visit the kinetic-java GitHub repository for more information about the kinetic-simulator.
What is the benefit of an Ethernet interface?
An Ethernet interface leverages the existing datacenter fabric, allowing for development of long-desired functionality such as: peer-to-peer migration of data, data sharing between drives, the ability for multiple applications to share a drive, and the elimination of physical distance limits imposed by SAS/SATA.
What is the benefit of a key/value drive?
A key/value drive allows applications utilizing object-based storage to communicate directly with target devices. This eliminates the need for multiple layers of legacy hardware and software such as POSIX, RAID controllers, and volume managers that were designed for a older, file-based use cases and impede efficient performance and scaling of object storage. Eliminating these layers provides significant gains in TCO and rack density.