With version 2.5.0, the
datatype of the <fwversion> XML Element in the <media…> block
changed from Int to String. Depending
upon how you do XML parsing, this may or may not be a concern. We have encountered cases where generated
XSD’s, used to generate XML parsing code, will fail to load the new XML
message, because it now sees a string in the contents of the <fwversion>
element, rather than an integer, and flags this as invalid data.
Previously, the DataPac
firmware version was an integer, typically somewhere between 100 and 105 or
so. Beginning in 2.5.0, this was
expanded to include the actual HDD firmware version, as well as the actual SSD firmware
version, if applicable, enclosed in parenthesis. This change was only made in the
<fwversion> element of the <media> (DataPac) XML messages.
This case shows the
previously displayed value, as well as the Hard Disk Drive version in the
DataPac. Since there are only HDD’s in
the DataPac, the value returned is “(4206)”.
This example shows a Hyper DataPac that contains both HDD
and SSD drives. When both are present,
the data returned will show the previously displayed value, followed by the HDD
firmware version then the SSD firmware version, separated by a slash (/). So this DataPac has HDD’s that are at
firmware version 4206, as well as SSD’s at firmware version X040.
To put it more in context, below are the full CorteX XML response
messages for the first full DataPac. The
2.5.0 example is for a fully HDD DataPac.
Example of pre-2.5.0 version
(generated by: http://ip_addr/storage/arrays/[serial#]/media)
<?xml version="1.0" encoding="iso-8859-1"?>
Mar 21 07:00:00 2013</manufacturingdate>
Example of 2.5.0 version
<manufacturingdate>Thu Mar 21 07:00:00 2013</manufacturingdate>