Visit The New, Modern Unix Linux Community


FC disk and ioinfo


 
Thread Tools Search this Thread
Operating Systems AIX FC disk and ioinfo
# 1  
FC disk and ioinfo

Hello, I have an issue with detecting the san disk on the OS side. Something looks strange for me.

My environment:

1 LPAR has 2 physical FCs
1 VIO has 2 physical FCs

on VIO, I can see the hdisk5(LUN) and use it as root disk.
Code:
Enabled   hdisk5 fscsi0
Enabled   hdisk5 fscsi0
Enabled   hdisk5 fscsi4
Enabled   hdisk5 fscsi4

on LPAR, I can see the hdisk1 (LUN) and use it as root disk.
Code:
Enabled   hdisk1 fscsi0
Enabled   hdisk1 fscsi0
Enabled   hdisk1 fscsi2
Enabled   hdisk1 fscsi2

Then, I create the virtual FC on lpar and map it with my VIO physical FC, we can see the port is logged by lpar.
Code:
$ lsnports
name             physloc                        fabric tports aports swwpns  awwpns
fcs0             U5802.001.9K81000-P1-C5-T1          1     64     63   2048    2043
fcs4             U78AA.001.WZSHVFA-P1-C5-T1          1     64     64   2048    2046

$ lsmap -all -npiv
Name          Physloc                            ClntID ClntName       ClntOS
------------- ---------------------------------- ------ -------------- -------
vfchost0      U8202.E4C.06337BT-V4-C5                 3 xyzT        FIRMWARE

Status:LOGGED_IN
FC name:fcs0                    FC loc code:U5802.001.9K81000-P1-C5-T1
Ports logged in:3
Flags:a<LOGGED_IN,STRIP_MERGE>
VFC client name:Virtual Fibre Channel - Firmware driverVFC client DRC:U8202.E4C.06337BT-V3-C5

But I cannot see it in the lspath command. However can see it with ioinfo command on the SMS, but marked with "Unrecognized device type: 3f"
Code:
FCINFO Main Menu
Select a FC Node from the following list:
  #  Location Code                Pathname
---------------------------------------------------------------
  1. U8202.E4C.06337BT-V3-C5-T1     /vdevice/vfc-client@30000005
  2. U5802.001.9K81000-P1-C6-T1     /pci@800000020000106/fibre-channel@0
  3. U5802.001.9K81000-P1-C6-T2     /pci@800000020000106/fibre-channel@0,1
  4. U78AA.001.WZSHVFA-P1-C6-T1     /pci@800000020000205/fibre-channel@0
  5. U78AA.001.WZSHVFA-P1-C6-T2     /pci@800000020000205/fibre-channel@0,1

  q - Quit/Exit

==> 1

FC Node Menu
FC Node String: /vdevice/vfc-client@30000005
FC Node WorldWidePortName: c0507606437b0000
-----------------------------------------------------------------
1. List Attached FC Devices
2. Select a FC Device
3. Enable/Disable FC Adapter Debug flags

q - Quit/Exit

==> 1

1. 500507680b31d7fe,0                - Unrecognized device type: 3f
2. 500507680b31d7ff,0                - Unrecognized device type: 3f

I even tried to remove 1 physical FC of lpar to check if zoning is working properly, so we can see "missing" below. This means that zoning and lun mapping is working properly.
Code:
Missing   hdisk1 fscsi0
Missing   hdisk1 fscsi0
Enabled   hdisk1 fscsi2
Enabled   hdisk1 fscsi2

I could say that nothing wrong at the storage side about zoning & lun mapping, the problem is probably at OS side.

So can someone has the idea to overcome this? I have tried to fix and search for "Unrecognized device type: 3f" but seems not much resources to look into it.

Moderator's Comments:
Mod Comment Do not use QUOTE tags for computer input, output, config files, code, etc. Use CODE tags!
# 2  
Just thinking, if we can use both physical and virtual FC for same LUN?
# 3  
no one has an idea on this Smilie
# 4  
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
This User Gave Thanks to RecoveryOne For This Post:
# 5  
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 ?
# 6  
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?
# 7  
I guess you are using vscsi

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #221
Difficulty: Easy
Apple's OS X (macOS) installed base had grown to 80 million users as reported at the WWDC 2014.
True or False?

6 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

4. 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

5. 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

6. 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

Featured Tech Videos