Page 1 of 1
hp 3PAR VLuns duplication Solution need
Posted: Fri Jan 10, 2014 2:48 pm
by sthaddin
Hi
I have problem with VLuns duplication in Solaris server.I map on VV to Solaris and system admin see 4 VLuns. Place know how to resolve this problem in hp 3PAR ?
I have sum question
What is command line for see lds,pds,and vluns and ports?
I also know how to see same thing in gui if you have snap short place send me
Place give me this information i appreciate you. This is my new job in hp 3PAR
What is the best Practices to mapping VV VVSET
Thank you
Re: hp 3PAR VLuns duplication Solution need
Posted: Sat Jan 11, 2014 4:52 pm
by skumflum
sthaddin wrote:Hi
I have problem with VLuns duplication in Solaris server.I map on VV to Solaris and system admin see 4 VLuns. Place know how to resolve this problem in hp 3PAR ?
I don't know anything about Solaris but it sounds to me that you need to look at multipathing (MPIO)? If you do not configure MPIO the OS will see a LUN for each FC Patch.
I have sum question
What is command line for see lds,pds,and vluns and ports?
You can always type help at the CLI and I recommend having the excellent CLI reference guide at hand.
Informational commands starts with "show"+something. showpd will give you informations about the disks
I also know how to see same thing in gui if you have snap short place send me
Place give me this information i appreciate you. This is my new job in hp 3PAR
What is the best Practices to mapping VV VVSET
Thank you
Do you have any specific tasks you want to accomplice?
Re: hp 3PAR VLuns duplication Solution need
Posted: Mon Jan 13, 2014 11:49 am
by zQUEz
For Solaris, take a look at the implementation guide:
http://tinyurl.com/myp2zlrAs for overall administration, you might want to hit the books. Do a search in Google for "HP 3PAR Administrator guide" and the like.
Re: hp 3PAR VLuns duplication Solution need
Posted: Tue Jan 14, 2014 10:56 am
by Cleanur
You can find the rest of the HP 3PAR Operating System Implementation Guides here
http://goo.gl/mzM4Y7 they list all of the required steps and settings required to connect each O/S. Note they're well worth following as getting the connectivity wrong upfront may well work but could lead to issues during upgrades etc.