Thanks for all the responses, I think it led me in the right direction. It looks like ONTAP is interpreting the vserver as a "node" vserver, however it is in fact a "data" vserver. Most of the BURTs relate to cluster setup and or join failures causing the data vesrevers to be interpreted as node vservers. However in this case all looks healthy from this aspect:
us01cm01::*> debug cluster-setup show
Task ID SubTask ID Status Tries Failures
-------------------- ------------------------- ---------- ----- -------
network-setup enable-switchless success 0 0
network-setup lif-check success 0 0
network-setup cluster_ha_check success 0 0
network-setup relabel-lifs success 0 0
node-check rpc-check success 0 0
node-check register_mgwd_dsmfp_service
success 0 0
system-initialize get-node-name success 0 0
start-rdb check-node-name success 0 0
start-rdb resolve-aggr-names success 0 0
start-rdb system-initialize success 0 0
cluster-create create-site-list success 0 0
cluster-create join-site-list success 0 0
cluster-create wait-for-rdb-online success 0 0
cluster-create wait-for-rdb-databases success 0 0
system-startup populate-limits success 0 0
check-cluster-apps add-license success 0 0
check-cluster-apps upload-capability success 0 0
check-cluster-apps add-cluster-name success 0 0
vldb-update insert-lifs success 0 0
vldb-update system-startup success 0 0
vserver-mgmt vldb success 0 0
cr-mgmt lifmgr success 0 0
cr-mgmt bcom success 0 0
cr-mgmt register-aggregates success 0 0
cr-mgmt create-cserver success 0 0
cr-mgmt initialize_vsMsidStatusTable
success 0 0
cr-mgmt create-predef-roles success 0 0
flexcache-mgmt publish-host-based-keys success 0 0
28 entries were displayed.