I'm trying to create my first VVOL on a brand new 3Par. I have all licenses installed including Thin Provision, Thin Reclamation, Thin Persistence, Dynamic Optimization, Adaptive Optimizaiton--etc. Basically every carte blanche in regards to licenses installed. However, when I try to create a Thinly Provision VVOL if I chose the default policy settings I get "Invalid Policy, tp_bzero". Of if I check "zero detect" I get "Invalid Policy, no_tp_bzero". Ok, so both tp_bzero AND no_tp_bzero are invalid policies?? I mean, it's got to be one of the other right? But I can't use either??
Any one see this error before?
Thanks
Can't create TPVV--invalid policy tp_bzero (and no_tp_bzero)
- Richard Siemers
- Site Admin
- Posts: 1333
- Joined: Tue Aug 18, 2009 10:35 pm
- Location: Dallas, Texas
Re: Can't create TPVV--invalid policy tp_bzero (and no_tp_bz
Yeah thats wierd, it has to be one or the other. You said this is a brand new system, what model and version of InServ, and was it professionally installed by HP?
Richard Siemers
The views and opinions expressed are my own and do not necessarily reflect those of my employer.
The views and opinions expressed are my own and do not necessarily reflect those of my employer.
-
- Posts: 1
- Joined: Thu Sep 12, 2013 2:02 pm
Re: Can't create TPVV--invalid policy tp_bzero (and no_tp_bz
I actually just bumped into this issue myself. In my case, we had recently done an InServ upgrade from 2.x to 3.x, and I was still using an older copy of the IMC (Inform Management Console) on my desktop. You should download the latest IMC from the HP 3PAR FTP and reinstall, hopefully that will address the issue (it did for me).
Re: Can't create TPVV--invalid policy tp_bzero (and no_tp_bz
modusoperandi wrote:I actually just bumped into this issue myself. In my case, we had recently done an InServ upgrade from 2.x to 3.x, and I was still using an older copy of the IMC (Inform Management Console) on my desktop. You should download the latest IMC from the HP 3PAR FTP and reinstall, hopefully that will address the issue (it did for me).
I'll second that...the same thing happened to us when we added a new array in another datacenter...it was running a new version of inform than my IMC. Upgrading did the trick.