Sponsored Content
Full Discussion: FC disk and ioinfo
Operating Systems AIX FC disk and ioinfo Post 303044312 by Phat on Tuesday 18th of February 2020 11:24:00 PM
Old 02-19-2020
Quote:
Originally Posted by zxmaus
I have no idea what you are saying - this all sounds confusing.

Maybe start over again. Your frame has 4 fibre channel adapters
you have allocated two to the vio and 2 to an lpar.
And now what - you are trying to map the adapters from the lpar via vio to another lpar?
With NPIV you map to a virtual wwpn, while when you zone to a physical adapter, you map to the physical wwpn. So I do not understand how removing a fibre channel adapter would show anything ?
Hi Zmaus,
The point 1 and 2 are correct. On the lpar I can see the LUN with 2 physical fibre.
Now I would like to use 1 more virtual fiber adapter to assign to lpar from VIO. And zoning virtual wwpn to the same LUN.

If everything is correct, I can see the LUN with 2 physical fibre adapters + 1 virtual fibre adapter.

--- Post updated at 05:24 AM ---

Quote:
Originally Posted by RecoveryOne
Taking a massive stab in the dark, but looks like if you removed the physical hba assigned to the lpar from the lpar and then your path for hdisk0 went missing: Your disks are not coming from the VIO. Without going into an in depth look at your system, are you sure you are presenting disks up from the VIO? Are you sure your lpar has virtual adapters presented up from the VIO? I mean, the whole point of running a VIO is so that takes all (or most) of your adapters so you can present them to the lpars as part of the virtualization layer. There should be very few instances where you need physical adapters assigned the a lpar running under a VIO.

Also from ioinfo from the openfirmware, its common to see that message. openfirmware is not aware so to speak to anything not apart of the system.

IF I manage to find time, I will show you how one of my environments are setup. Currently a lot of cruft on my plate that I must address first. Also, you should note that I'm not using NPIV, and my setup may not be the 'IBM recommended' way.
In the meantime, here's some handy links:
Access Denied
And since you are using npiv:
AIX for System Administrators
Hi RecoveryOne,

I'm checking the links you shared. From my side, I presented the virtual adapter to both VIO and lpar. With the lsmap I can see the client has logged in the fibre channel, from the SAN switch, checked with storage team, I can see the virtual wwpn. Further check with them, I can be quite sure the zoning & LUN masking works properly, that virtual WWPN is the same zone member with physical wwpn. Removing physical wwpn, make the link missing, means that the virtual wwpn(which is same zone) should see the LUN as well.

A bit curious, if you did not use NPIV, so which method you are using now?
 

6 More Discussions You Might Find Interesting

1. Solaris

( VxVM ) How to add the removed disk back to previous disk group

Previously , i remove the disk by #vxdg -g testdg -k rmdisk testdg02 But i got error when i -k adddisk bash-2.03# vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - online invalid c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies

2. Linux

How to Calculate Disk Queue length and Disk Busy Time

Hi, Am doing an enhancements related to monitoring a Linux disk I/O statistics. The /proc/diskstats file is used to get the each disk I/O statistics. But, It returns the raw value. How to calculate the Disk Queue Length and Disk Busy time from the raw values. Guide me. (1 Reply)
Discussion started by: maruthu
1 Replies

3. Solaris

Convert from raw disk to solaris volume manager disk

I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below: root@moneta # df -h Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 9.8G 513M 9.3G 6% /... (4 Replies)
Discussion started by: fretagi
4 Replies

4. AIX

Clone or mirror your AIX OS larger disk to smaller disk ?

hello folks, I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies

5. Filesystems, Disks and Memory

DISK ARRAY PROTECTION SUSPENDED message displayed following disk replacement

Hello, On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active. We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED. ... (1 Reply)
Discussion started by: terrya
1 Replies

6. AIX

DISK ARRAY PROTECTION SUSPENDED message following disk replacement

Hello, On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active. We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED. ... (3 Replies)
Discussion started by: terrya
3 Replies
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)
All times are GMT -4. The time now is 04:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy