@archspangler, I bet you've already worked around this by now - but I'm answering for everyone else with the same question.
A Data Collection Node is basically a Splunk heavy forwarder, configured and scheduled by a central Splunk process called "hydra". The collection of data from VMware and from NetApp ONTAP each use this approach.
There isn't a specific OVA for use with Netapp collection, BUT there's no reason you can't simply jumpstart the process by using the VMware OVA. (That's what I do, anyway.) This gives you benefits of an easily-deployed / easily configured virtual appliance as a starting point, where Splunk and the OS are ready to go.
To that, you simply add the NetApp components - and ignore the VMware components or disable or delete the VMware pieces. (They can live side-by-side without conflict, but don't try to use the same DCN for dual roles. The scheduler doesn't know how to balance such wildly different work loads.)
,
