HP p2000 G3 config
greetings,
I have (8) disks in a RAID 10 on an HP p2000 G3. I have 1.8 TB available. Current owner is controller A. Will that automatically fail over to controller B if A goes down?
two other things, the smallest vDisk I can create is about 450 GB according to the interface. Why is that? I may want to create one smaller.
last, where do I get the host WWN/IQN so I can add hosts to the p2000?
I guess this is actually my last question - anyone have any frequent issues with the p2000 that required a reboot of the unit, thus resulting in powering down and rebooting of production servers?
thanks
I have (8) disks in a RAID 10 on an HP p2000 G3. I have 1.8 TB available. Current owner is controller A. Will that automatically fail over to controller B if A goes down?
two other things, the smallest vDisk I can create is about 450 GB according to the interface. Why is that? I may want to create one smaller.
last, where do I get the host WWN/IQN so I can add hosts to the p2000?
I guess this is actually my last question - anyone have any frequent issues with the p2000 that required a reboot of the unit, thus resulting in powering down and rebooting of production servers?
thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
(okay you stated vdisk!)
you should be able to create any size volume you like.!!!
you should be able to create any size volume you like.!!!
the default size presented for a volume is usually the remaining space in the vdisk?
if you change the number?
if you change the number?
ASKER
just created a 98 GB volume successfully. read-write is the access on the vdisk. there goes the smallest disk size of 450 GB. still not sure where to check failover to controller B, but it shows controller A as the owner.
any suggestion on cache optimization (standard or super sequential)?
any suggestion on cache optimization (standard or super sequential)?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
physical view, do not have access to hand.
ASKER
thanks. graphical enclosure view shows green ticks by both controllers (A and B) and (2) iSCSI ports on A and (2) on B.
sorry about the vdisk / volume mix up. it does show in my properties for my (1) vdisk that spans all physical disks and has 1.8 TB free that the minimum disk size is 450 GB. I now believe that may be referring to the size of one physical disk in the unit.
I am trying to quickly configure this to place that messed up exchange server with the snapshot problem when I do either a clone or V2V later.
thanks again for all your help
sorry about the vdisk / volume mix up. it does show in my properties for my (1) vdisk that spans all physical disks and has 1.8 TB free that the minimum disk size is 450 GB. I now believe that may be referring to the size of one physical disk in the unit.
I am trying to quickly configure this to place that messed up exchange server with the snapshot problem when I do either a clone or V2V later.
thanks again for all your help
follow my iSCSI articles to setup iSCSI networks if required.
ASKER
HA! I had done that already by following your article some time back. I just didn't get around to adding a host.
quick question and I think I am done with this post, do you like the HP p2000? have you had any major problems with one? mine is brand new and I got it because it was a lot less expensive than another EMC product and I didn't want to add an expansion to my current AX4 for redundancy reasons. I have heard mixed things so was just curious of your opinion...
thanks
quick question and I think I am done with this post, do you like the HP p2000? have you had any major problems with one? mine is brand new and I got it because it was a lot less expensive than another EMC product and I didn't want to add an expansion to my current AX4 for redundancy reasons. I have heard mixed things so was just curious of your opinion...
thanks
Yes, we like them, ideal for small businesses, but we had clients that had some fail last year.
ASKER
well, that's not very re-assuring. hopefully they weren't the g3 models.
either way, it's what I got so hopefully it'll work.
either way, it's what I got so hopefully it'll work.
Suggestion: You should split your drives between controller A and control B for best performance.
If controller A owns your vdisk what does controller B own. (If you have disks on controller B I missed it.)
From P2000 Best Practices guide:
“A host can use any available data path to access a volume owned by either controller. The preferred path, which offers slightly better performance, is through target ports on a volume’s owning controller.”
Some MIPO configurations will only use the preferred path (active/optimized) for drive access and the non-prefer path (Active/not optimized) for fail over.
As far as controller failover:
“Controller failure results in the surviving controller doing the following:
• Taking ownership of all RAID sets
• Managing the failed controller’s cache data
• Restarting data protection services
• Assuming the host port characteristics of both controllers”
-Lee
PS You can use the SAN interface under tools>shut down or restart controller to shut down storage controller A. This will allow you to ‘watch’ what happens when a control fails. A vdisk owned by controller A will change to control B. Put control A back online and the disks will change back to controller A.
If controller A owns your vdisk what does controller B own. (If you have disks on controller B I missed it.)
From P2000 Best Practices guide:
“A host can use any available data path to access a volume owned by either controller. The preferred path, which offers slightly better performance, is through target ports on a volume’s owning controller.”
Some MIPO configurations will only use the preferred path (active/optimized) for drive access and the non-prefer path (Active/not optimized) for fail over.
As far as controller failover:
“Controller failure results in the surviving controller doing the following:
• Taking ownership of all RAID sets
• Managing the failed controller’s cache data
• Restarting data protection services
• Assuming the host port characteristics of both controllers”
-Lee
PS You can use the SAN interface under tools>shut down or restart controller to shut down storage controller A. This will allow you to ‘watch’ what happens when a control fails. A vdisk owned by controller A will change to control B. Put control A back online and the disks will change back to controller A.
ASKER
so if I create a volume, will it be restricted to a minimum size of 450 GB? that is what the interface says, but I may want to create one much smaller for a smaller VM.