Local datastore naming policy of VxRail 3.5 hosts

Hi EMC Engineering,

I have a question about local datastore naming policy of VxRail hosts.

I had create FRU replacement node using "v3.5_gen2_node_replacement.zip".

After VxRail 3.5 FRU node installation,

the SATADOM local datastore name is different in VxRail 3.5 and 3.0 .

And I found the difference in the kickstart scripting ESXi installer ISO images.

Is this a design change ?

Example :

In the VxRail 3.0 ESXi local VMFS datastore(SATADOM).

-service-datastore1

EMCXXXXXX04-01-service-datastore1

EMCXXXXXX04-02-service-datastore1

EMCXXXXXX04-03-service-datastore1

EMCXXXXXX04-04-service-datastore1

In the VxRail 3.5 ESXi local VMFS datastore(SATADOM), there are "04" inserted between AssetTag code.

- 04- -service-datastore1

EMCXXXXXX04-04-01-service-datastore1

EMCXXXXXX04-04-02-service-datastore1

EMCXXXXXX04-04-03-service-datastore1

EMCXXXXXX04-04-04-service-datastore1

Thanks.