Sponsored Content
Full Discussion: NPIV mapping problem
Operating Systems AIX NPIV mapping problem Post 302600821 by johnf on Wednesday 22nd of February 2012 06:44:52 AM
Old 02-22-2012
NPIV mapping problem

Hello all I hope someone can help me with this. I have a single LPAR which is supplied a rootvg and datavg disk set from a dual VIO server configuration. I see dual path disks for all the datavg disks but only see one path for the rootvg disks.

The client LPAR has the following:
Code:
fcs0   Available C2-T1 Virtual Fibre Channel Client Adapter
fcs1   Available C3-T1 Virtual Fibre Channel Client Adapter
fcs2   Available C4-T1 Virtual Fibre Channel Client Adapter
fcs3   Available C5-T1 Virtual Fibre Channel Client Adapter

But when lspath is run the following is returned:
Code:
Enabled hdisk4 fscsi1
Enabled hdisk5 fscsi1
Enabled hdisk6 fscsi1
Enabled hdisk2 fscsi2
Enabled hdisk0 fscsi2
Enabled hdisk4 fscsi3
Enabled hdisk5 fscsi3
Enabled hdisk6 fscsi3

As can be seen FCS0 (fscsi0) is missing. From the VIO server which is serving this adapter you have:
Code:
$ lsdev -type adapter | grep fcs
fcs0             Available   8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
fcs3             Available   8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)]

When I run the map command I get the following:
Code:
$ lsmap -all -npiv
Name          Physloc                            ClntID ClntName       ClntOS
------------- ---------------------------------- ------ -------------- -------
vfchost0      U8202.E4B.06605EP-V3-C3                 2 LPAR        AIX

Status:LOGGED_IN
FC name:fcs0                    FC loc code:U78AA.001.WZSG75A-P1-C6-T1
Ports logged in:1
Flags:a<LOGGED_IN,STRIP_MERGE>
VFC client name:fcs0            VFC client DRC:U8202.E4B.06605EP-V2-C2-T1

Name          Physloc                            ClntID ClntName       ClntOS
------------- ---------------------------------- ------ -------------- -------
vfchost1      U8202.E4B.06605EP-V3-C4                 2 LPAR        AIX

Status:LOGGED_IN
FC name:fcs3                    FC loc code:U78AA.001.WZSG75A-P1-C6-T2
Ports logged in:2
Flags:a<LOGGED_IN,STRIP_MERGE>
VFC client name:fcs1            VFC client DRC:U8202.E4B.06605EP-V2-C3-T1

This is where it gets interesting on the offending vfchost it can be seen that only 1 port is logged in, whereas on the working port 2 are logged in.

I believe this is the problem but cannot find anything on a general internet trawl to answer why! I believe it is a SAN configuration problem but need evidence with which to beat up the SAN team!

I hope you can help
 

10 More Discussions You Might Find Interesting

1. SCO

nfs mapping problem

Dear all I have a SCO server with a mapping to a NFS share on a linux server. The Linux server went down and the mapping on the SCO server failed. Now when I run the df -k command on the SCO server, the NFS mapping is showing the following error: df: cannot statfs... (5 Replies)
Discussion started by: soliberus
5 Replies

2. AIX

Problem mapping LUN disk from VIOS to the LPAR

Hello guys, It would be so nice of you if someone can provide me with these informations. 1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Discussion started by: solaix14
3 Replies

3. AIX

Anyone using NPIV?

Is anyone here using NPIV with AIX? If you are, what type of switch are you connected to? Also, please share some impressions of NPIV over traditional port-to-port LUN assignments. We are looking to move to NPIV and need some convincing argume... I mean information. (2 Replies)
Discussion started by: kah00na
2 Replies

4. AIX

Migrating hdisks from vscsi to NPIV with powerpath

Hi All, I'm preparing to migrate some servers from vscsi to pass-thru NPIV. I am planning to have the SAN team move the exact LUNs from vio1/vio2 to those two VWWN through NPIV. My question is on the partition itself.. right now, let's say I have hdisk0/1/2/3/4 that are part of datavg. They... (2 Replies)
Discussion started by: lapfrank
2 Replies

5. AIX

AIX Sanboot from EMC Symmetrix with NPIV

Hi All.. On to a new implementation with AIX 7.1 san boot from EMC disks (Using NPIV). Anyone played with this recently? Wondering if we need PowerPath on the AIX clients or has native MPIO matured to replace it. Thoughts? Thanks Mr B (6 Replies)
Discussion started by: balaji_prk
6 Replies

6. AIX

Vscsi and npiv on same adapter

Hi, I want to change from vscsi to npiv. Is it possible to use both on the same adapter, so we can change the systems one by one, or must we place a second FC adapter in the VIO servers? Thanks, Ronald (2 Replies)
Discussion started by: ronaldm60
2 Replies

7. AIX

Key mapping problem in qputty

Hello, I am using fgltty connection (which is actually qputty) to my AIX 6.1 server. The problem is that PageUp and PageDown keys are not working and i cannot find a way to do the correct mapping for this issue. I read and tried many things that i saw in the web but nothing worked. Well... (2 Replies)
Discussion started by: omonoiatis9
2 Replies

8. Shell Programming and Scripting

Creating unique mapping from multiple mapping

Hello, I do not know if this is the right title to use. I have a large dictionary database which has the following structure: where a b c d e are in English and p q r s t are in a target language., the two separated by the delimiter =. What I am looking for is a perl script which will take... (5 Replies)
Discussion started by: gimley
5 Replies

9. AIX

NPIV custom WWN

Hi All :) i would like to know if i can customize the WWN of the new VFC (NPIV). Or, if i must move the LPAR on another server with another FCS, i have to change the zoning?? Thanks in advance. Mario ---------- Post updated 09-21-12 at 02:51 AM ---------- Previous update was 09-20-12 at... (1 Reply)
Discussion started by: Zio Bill
1 Replies

10. AIX

VIOS FC Mapping/NPIV questions

Please forgive me here as I don't fully understand what I am talking about here so if I use the wrong terminology please overlook me. We have multiple AIX LPARs on the managed system with two VIO Servers. A Co-Worker and I are trying to set up a new LPAR client (The guy that knows this is out)... (14 Replies)
Discussion started by: juredd1
14 Replies
SCSI(4) 						     Kernel Interfaces Manual							   SCSI(4)

Name
       SCSI - Small Computer System Interconnect

Description
       The  ULTRIX  system interfaces to disk and tape devices through the Small Computer System Interconnect (SCSI).  Initial ULTRIX SCSI support
       is limited to the Digital-supplied mass storage devices.  The following devices are fully supported on the ULTRIX system:

       o    Winchester disks: RZ22, RZ23, RZ23L, RZ24, RZ55, RZ56, RZ57, RX23, RX26, RX33

       o    Magnetic tapes: TZ30, TZK50, TLZ04, TSZ05, TKZ08, TZK10

       o    Optical disks: RRD40, RRD42

       Under the ULTRIX operating system, a SCSI device is referred to by its logical name.  Logical names take the following form:
       nn#
       The nn argument is the two-character name; the number sign (#) represents the unit number.  The two character names for SCSI devices are:

       rz  -  RZ22, RZ23, RZ23L, RZ24, RZ55, RZ56, RZ57, RX23, RX26, RX33, RRD40, RRD42 disks

       tz  -  TZ30, TZK50, TLZ04, TSZ05, TKZ08, and TZK10 tapes

       The unit number is a combination of the SCSI bus number, either 0, 1, ... and the device's target ID number.   The  unit  number  is  eight
       times  the  bus	number plus the target ID.  For example, an RZ23 disk at target ID 3 on bus 0 would be referred to as rz3; a TZK50 tape at
       target ID 5 on the second SCSI bus would be referred to as 13.

       The SCSI bus has eight possible target device IDs.  By default, one is allocated to the system.	This allows for a maximum of seven  target
       devices connected to a SCSI bus.

Restrictions
       The ULTRIX SCSI device driver does not operate with optical disks, other than the Digital-supplied devices.

       The SCSI driver attempts to support on a best effort basis, non-Digital-supplied winchester disks and magnetic tapes.

       The following notes apply to the driver's handling of non-Digital-supplied disks:

	  o   These disks are assigned a device type of RZxx, instead of RZ22, RZ23, RZ23L, RZ55, RZ56, RZ57, RX23, RX26, or RX33.  The RZxx disks
	      follow the same logical device naming scheme as the Digital-supplied disks.

	  o   During the autoconfigure phase of the system startup, the driver prints the contents of the SCSI vendor  ID,  product  ID,  and  the
	      revision level fields of the inquiry data return by the SCSI device.

	  o   RZxx  disks  are	assigned a default partition table. The default table can be modified by editing the sz_rzxx_sizes[8] entry in the
	      file The utility can also be used to modify the partition table on a RZxx disk.

	  o   The only logical unit number (LUN) supported for each target ID is 0.

See Also
       rz(4), tz(4), chpt(8)

																	   SCSI(4)
All times are GMT -4. The time now is 04:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy