02-04-2010
LPAR and AIX VIO Disk Mappring for Linux Clients
VIO Server is managing both AIX Clients and Linux Clients. For AIX Clients, we could do a disk mapping from slot numbers to VIO and also uname -L to determine the lparid and serial number frame its running on.
From a Linux Client,
How do I know which IBM frame its running on? Any command to get serial number?
How do I know which VIO disks the linux client disks are mapped to?
Are there any commands to list physical location(U9117.MMA.2329AFD-V20-C6-T1) of disks similar to lscfg in AIX so that slot numbers can determined?
Thanks
10 More Discussions You Might Find Interesting
1. AIX
Hi,
I define 2 new LV on the vio server and run a cfgmgr on the partition and see my 2 new hdisk (hdisk6 and hdisk7).
I extend my vg vg000 (on the partition) and add the 2 hdisks.
I had a filesystem on the vg000 and when I added the disk I would like to increase the filesystem. But I cannot do a... (0 Replies)
Discussion started by: touny
0 Replies
2. UNIX for Dummies Questions & Answers
Can you have a Dynamic LPAR without VIO and if yes is there a benefit to having both? I am attempting to implement VIO and Resource pooling at my company and want to understand the limitations.
Also, I have been told the managing and allocation of the Logical Volumes is a time consuming task as... (0 Replies)
Discussion started by: bombers73
0 Replies
3. AIX
We have a frame the uses 2 vios that assign disk storage to LPAR's. We have a LPAr with multiple disk and I want to know how do I tell which vio is serving the disk. For example the LPAr has hdisk 0, 1, 2, 3 all the same size. I want to know which vio is serving hdisk0, 1. (4 Replies)
Discussion started by: daveisme
4 Replies
4. AIX
hello Folks,
my vio:
$ lsmap -all
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost0 U9117.MMA.6534BE4-V2-C11 0x00000003
VTD ... (0 Replies)
Discussion started by: filosophizer
0 Replies
5. AIX
Hi,
I was looking on Google for AIX-VIO/LPAR with ISCSI solution and found following really nice tutorial about how to setup ISCSI with free NAS.
1) Build Your Own Open Source NAS Device Using FreeNAS | Train Signal Training - Free Computer Training Videos
2) Build Your Own Open Source... (4 Replies)
Discussion started by: kabir
4 Replies
6. AIX
I am wondering if there is a command I can run from **with-in** LPAR server (server01) to find out the hostname or IP address or other parameters for VIO server in charge of server01? (1 Reply)
Discussion started by: ms1232
1 Replies
7. AIX
Just a question which may seem dumb to some out there, but then again I am not a super technie so that's my excuse.
Is it possible to say provision a test AIX LPAR (has a 10gb boot lun and 20gb data) under a VIO which has connectivity to SAN Array A so it can see the disks provisioned to it,... (2 Replies)
Discussion started by: Johnny1314
2 Replies
8. AIX
Hi All,
I've been trying to create a new LPAR for some days now but I can't get the VIO server to recognize the new LPAR. This is what I did:
On HMC create new LPAR
On HMC create new virtual scsi adapter for LPAR in VIO profile
On HMC add new virtual scsi adapter for LPAR with DLPAR... (6 Replies)
Discussion started by: petervg
6 Replies
9. AIX
:wall::wall::wall:
1. I have created an LPAR in the HMC.
2. I have allocated the storage from an Hitachi AMS2500 and assigned it to the host group.
3. I have zoned the LPAR and Storage on a Brocade 5100. (The zone sees the AMS)
Next I activated the LPAR in the HMC, SMS mode for the mksysb... (3 Replies)
Discussion started by: Dallasguy7
3 Replies
10. AIX
Hi Guys,
I have fresh new installed VIO 2.2.3.70 on a p710, 3 physical SAS disks, rootvg on hdisk0
and 3 VIO clients through vscsi, AIX7.1tl4 AIX6.1tl9 RHEL6.5ppc, each lpar has its rootvg installed on a LV on datavg (hdisk2) mapped to vhost0,1,2
There is no vg on hdisk1, I use it for my... (1 Reply)
Discussion started by: frenchy59
1 Replies
LEARN ABOUT HPUX
vxsplitlines
vxsplitlines(1M) vxsplitlines(1M)
NAME
vxsplitlines - show disks with conflicting configuration copies in a cluster
SYNOPSIS
vxsplitlines [-g diskgroup] [-c daname]
DESCRIPTION
If you import portions of a disk group on different systems, this can lead to conflicting configuration copies on the disks of the disk
group.
If the configuration information in a disk group is ambiguous, it may not be possible for Veritas Volume Manager to determine which config-
uration copy is most up-to-date. (This is usually termed a serial split brain (SSB) condition when it occurs in a cluster.) You cannot
import a disk group in this state unless you specify which disk's configuration copy to use.
You can use the vxsplitlines command to see which disks in a disk group have conflicting configuration copies, and use this information
together with your knowledge of the history of the disk groups' usage to determine which configuration copy is most valid.
The output from vxsplitlines displays the vxdg commands that you can run to import the disk group using the available configuration copies.
The -o selectcp option of the vxdg import command is used to select the configuration copy to use for the import.
OPTIONS
-c daname Display the SSB IDs for each disk that are stored in the configuration copy on the disk specified by its disk access name.
Note: Although the SSB IDs for some disks may match, this does not necessarily mean that those disks' configuration copies have
recorded all the configuration changes. When viewed from some other configuration copies, the SSB IDs of the same disks may not
match.
-g diskgroup
Specifies the disk group. If a disk group is not specified, the default disk group is used as determined from the rules on the
vxdg(1M) manual page.
EXAMPLES
Display the disks on each side of the split in the disk group newdg:
vxsplitlines -g newdg
Display the SSB IDs stored in the configuration copy on disk c2t4d0:
vxsplitlines -g newdg -c c2t4d0
NOTES
The vxsplitlines is primarily intended to be used with private disk groups, but it also works with shared disk groups.
The version number of the disk group must be 110 or greater.
SEE ALSO
vxdg(1M)
Veritas Volume Manager Administrator's Guide
VxVM 5.0.31.1 24 Mar 2008 vxsplitlines(1M)