We did an OVT only once (for adding a node), when the packaging was found to be slightly damaged from the outside. Just felt better... normally not necessary AFAIK.

Hi ,

Well i would recommend that whenever you add a new node or couple of nodes you need to create a isolated cluster,run ovt and upload then the logs.I would recommend it just to verify that Configurations got as it should.

I am implementing Isilons at customer sites and already found out that some nodes didn't came configured as should .

Option 1 (Single node ):

1.Install single node cluster

2.Run ovt check and verify no error on hardware (except network connectivity)

3.upload it

4.Re-image

5.Join existing cluster

Option 2 (multiple nodes ):

1.Install cluster with all new nodes (hopfully you have another IB switch for that)

2.Run ovt check and verify no error on hardware (except network connectivity)

3.upload it

4.Destory cluster

5.Join existing cluster for all nodes.

how this help

thanks, i was remembering something like that but i was thinking that maybe it changes with 7.1

but for security i will make the ovt.

Just a tip when doing this, part of the OVT activities includes a test of the networking, which isn't necessary when just testing a single node.  However, if you are preparing to join the node to the cluster, perhaps you have already plugged in the network cabling.  The OVT network tests could reach out and put unnecessary traffic onto the switches that could have an impact to other systems. 

I would recommend removing all network cabling to run the OVT.

You can also use isi_ovt_check --local to limit tests to the local node.