- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Veritas Volume Manage 3.5 total confusion!
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-28-2006 05:51 AM
тАО08-28-2006 05:51 AM
The boot volume (vg00) is on the internal server disks and will remain lvm.
1. Create a disk group with two of the disks. One from each tray.
2. Have both paths active to each disk.
3. Create the filesytems on the disks.
4. Mirror the disks.
The Veritas administration guide is very hard to understand. I am very fulent in LVM.
Can someone help me with instructions to carry out my task.
Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-28-2006 05:58 AM
тАО08-28-2006 05:58 AM
Re: Veritas Volume Manage 3.5 total confusion!
1. You want LVM for vg00.. correct?
2. VxVM 3.5 for other volume groups other than vg00. Install VxVM 3.5 base foundation suite with license on the server.
3. Make sure that what naming standrad for vg's and logical volumes going to be for VxVM and then you can use following steps to create and assign disks.
use gUI which would be easier for you add disks, create vg's and logical volumes.
/opt/VRTSob/bin/vea &
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-28-2006 06:12 AM
тАО08-28-2006 06:12 AM
Re: Veritas Volume Manage 3.5 total confusion!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-28-2006 06:16 AM
тАО08-28-2006 06:16 AM
Re: Veritas Volume Manage 3.5 total confusion!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-28-2006 07:16 AM
тАО08-28-2006 07:16 AM
Re: Veritas Volume Manage 3.5 total confusion!
I tried vea but even though I see my server and "disks" and "enclosures", etc, I see no way of managing the disks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-28-2006 07:52 AM
тАО08-28-2006 07:52 AM
SolutionVEA is Explorer style and should be intuitive. But if you do not know the basics - I believe you'll get no further. It has been my experience that VxVM persons adapt quickly with LVM/other VMs in case of the other way around...
At any rate, if the GUI is not much of help to you - try the TUI --- vxdiskadm. But to get started - you will need to carve a useless rootdg or just create all of your stuff using the mandatory "diskgroup" rootdg. You can use vxinstall to create rootdg and other diskgroups... You may want to try using the VEA GUI once more once yu've got rootdg carved up...
Hope this helps...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-28-2006 08:37 AM
тАО08-28-2006 08:37 AM
Re: Veritas Volume Manage 3.5 total confusion!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-28-2006 08:47 AM
тАО08-28-2006 08:47 AM
Re: Veritas Volume Manage 3.5 total confusion!
1. ioscan -fn
2. insf -e
3. vxdctl enable --> this may take a while.
4. vxdg list --> should show you disks "error" means uninitialized by VxVM.
"online" means already initialized.
"LVM" using by LVM
5. vxdisksetup -i /dev/rdsk/cxtydz
will initialize disk
run same command to initialize disks.
6. you can use vea gui once you initialize disks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2006 05:31 AM
тАО08-29-2006 05:31 AM
Re: Veritas Volume Manage 3.5 total confusion!
After that you can use vxdiskadm or vea to do the rest of your work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-31-2006 02:07 AM
тАО08-31-2006 02:07 AM
Re: Veritas Volume Manage 3.5 total confusion!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-31-2006 10:32 AM
тАО08-31-2006 10:32 AM
Re: Veritas Volume Manage 3.5 total confusion!
If i use vxdiskadm and look at a disk I see the following:
Device to list in detail [,none,q,?] (default: none) EMC_CLARiiON0_2
Device: EMC_CLARiiON0_2
devicetag: EMC_CLARiiON0_2
type: auto
flags: online error private autoconfig
errno: Device path not valid
Multipathing information:
numpaths: 4
c8t0d3 state=enabled
c10t0d3 state=NoLicense
c6t0d3 state=NoLicense
c4t0d3 state=NoLicense
This does not look good to me!!!
I used the suggested script from the CFS document to create the VXFS disk and ran into these errors:
+ /etc/vx/bin/vxdisksetup c8t0d3
VxVM vxdisksetup ERROR V-5-2-43 c8t0d3: Invalid disk device for vxdisksetup
+ vxdisk online c8t0d3
VxVM vxdisk ERROR V-5-1-537 Device c8t0d3: Not in the configuration
+ vxdisk -f init c8t0d3
VxVM vxdisk ERROR V-5-1-3421 Device c8t0d3 is already in use by LVM.
Any idea what you did to resolve the multi-pathing related problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2006 02:12 AM
тАО09-01-2006 02:12 AM
Re: Veritas Volume Manage 3.5 total confusion!
The above step to be done before you create volume groups other wise your info will be lost.
reboot your system to keep it persistent.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2006 03:01 AM
тАО09-01-2006 03:01 AM
Re: Veritas Volume Manage 3.5 total confusion!
THe previous poster I think mentions one -- that is explicit/forced suppression of paths so VxVM only sees one path...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2006 06:21 AM
тАО09-01-2006 06:21 AM
Re: Veritas Volume Manage 3.5 total confusion!
I was able to disable the multi-pathing and the disks are "online".
When I startup the cluster and the CFS package, both servers in the cluster crash. I think it is because I have a problem with "enclosure based names for disks". I want to CFS 2 SAN disks called:
root@omzatl05:/vxdisk list
DEVICE TYPE DISK GROUP STATUS
EMC_CLARiiON0_1 auto:none - - online invalid
EMC_CLARiiON0_2 auto:none - - online invalid
The problem is these "enclosures" are pointing to different SAN disks.
On server omzatl05 the enclosure EMC_CLARiiON0_1 points to c8t0d3 and this is SAN LUN 222.
But on server omzatl06 the enclosure EMC_CLARiiON0_1 points to c5t0d3 which is SAN LUN 508.
So these "enclosures" need to point to the same SAN disk? I would expect they should.
So is there a way to create an "emclosure" and select the spcific c#t#d# to use? All my enclosures where built automatically when I ran the vxinstall command.
Thanks once again for everyones help. I did not know this would be so difficult.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2006 06:30 AM
тАО09-01-2006 06:30 AM
Re: Veritas Volume Manage 3.5 total confusion!
yes you can do. don't have handy documentation. If you search from veritas support docs then you would get how to create enclosure for Clariion disks. I think you have to install some library files to see Clariion based enclosures.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2006 06:34 AM
тАО09-01-2006 06:34 AM
Re: Veritas Volume Manage 3.5 total confusion!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2006 06:57 AM
тАО09-01-2006 06:57 AM
Re: Veritas Volume Manage 3.5 total confusion!
EMC uses a HLU/ALU numbering pair to present the disks. The ALU is the "LUN number" and the HLU is the unix drive number ( the d# value in the special file c#t#d#). The HLU/ALU pairs on the 2 servers do not match and this explains the mismatch I saw in my previous message.
I have asked our SAN folks to correct this and I'll see if this helps.
I still cannot find any docs that describe how to build a new "enclosure" and add a specific disk to it. Any ideas?
Thanks once again for the help...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2006 02:03 AM
тАО09-07-2006 02:03 AM