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
volreattach(8)						      System Manager's Manual						    volreattach(8)

NAME
volreattach - Reattaches disk drives that have once again become accessible SYNOPSIS
/usr/sbin/volreattach [-rb] [accessname...] /usr/sbin/volreattach -c accessname OPTIONS
The volreattach utility has the following options: Calls the volrecover utility to attempt to recover stale plexes of any volumes on the failed disk. Performs the reattach operation in the background. Checks whether a reattach is possible. No operation is performed, but the name of the disk group and disk media name at which the disk can be reattached is displayed. DESCRIPTION
The volreattach utility attempts to reattach disks using the same disk group and media names they had before detachment. This operation may be necessary if a disk has a transient failure, or if some disk drivers are unloaded or unloadable when the Logical Storage Manager is started, causing disks to enter the failed state. If the problem is fixed, the volreattach command can be used to reattach the disks without plexes being flagged as stale, as long as the reattach happens before any volumes on the disk are started. The volreattach command is called from the voldiskadm menus as part of disk recovery. The volreattach utility tries to find a disk with a disk group and disk ID matching that of the disk(s) being reattached. If the matching disk is found, the reattach operation may still fail if the original cause (or some other cause) for the disk failure still exists. EXIT CODES
A zero exit status is returned if it is possible to perform a reattach. Otherwise, non-zero is returned. SEE ALSO
volintro(8), voldiskadm(8), volrecover(8) volreattach(8)
All times are GMT -4. The time now is 05:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy