AIX

AIX

Connect with fellow AIX users and experts to gain knowledge, share insights, and solve problems.


#Power
 View Only
  • 1.  NPIV Fiber Card Issue

    Posted Mon March 21, 2016 07:35 AM

    Originally posted by: Shady.AboShady


    Hi Guys,

    I have problem with two lpars fiber ports created at VIOS 2.2.0.12-FP24 SP-02.

    I have created 2 virtual fiber cards from dual vios p7 server and assigned it to  lpar
    and mapped the virtual cards to the physical and created the zone at SAN Sw and Host at Storage correctly, but I found that only one fiber cards can see the luns from san and the other not

    While the other one is Status:LOGGED_IN, it can be seen at SAN SW but on Storage degraded, from my side I tired to unmap and remap the card from vios to the same physical card or another still not work

    I tried to create another virtual fiber card with id 346 but still the same

    # at VIOS

    Name Physloc ClntID ClntName ClntOS
    ------------- ---------------------------------- ------ -------------- -------
    vfchost48 U9179.MHB.10724AP-V2-C346 46 DRTestEDHETLDB AIX

    Status:LOGGED_IN
    FC name:fcs14 FC loc code:U78C0.001.DBJF737-P2-C6-T1
    Ports logged in:1
    Flags:a<LOGGED_IN,STRIP_MERGE>
    VFC client name:fcs2 VFC client DRC:U9179.MHB.10724AP-V2-C346


    Name Physloc ClntID ClntName ClntOS
    ------------- ---------------------------------- ------ -------------- -------
    vfchost48 U9179.MHB.10724AP-V2-C346 46 DRTestEDHETLDB AIX

    Status:LOGGED_IN
    FC name:fcs14 FC loc code:U78C0.001.DBJF737-P2-C6-T1
    Ports logged in:1
    Flags:a<LOGGED_IN,STRIP_MERGE>
    VFC client name:fcs2 VFC client DRC:U9179.MHB.10724AP-V2-C346


    #at LAPR

    x.x.x=> lsslot -c slot
    # Slot Description Device(s)
    U9179.MHB.10724AP-V46-C0 Virtual I/O Slot vsa0
    U9179.MHB.10724AP-V46-C3 Virtual I/O Slot ent1
    U9179.MHB.10724AP-V46-C146 Virtual I/O Slot fcs0
    U9179.MHB.10724AP-V46-C246 Virtual I/O Slot fcs1 <<<
    U9179.MHB.10724AP-V46-C346 Virtual I/O Slot fcs2 <<<

    => lspath >>> show only that one card is active
    Enabled hdisk0 fscsi0
    Enabled hdisk0 fscsi0
    Enabled hdisk0 fscsi0
    Enabled hdisk0 fscsi0
    Enabled hdisk1 fscsi0
    Enabled hdisk1 fscsi0
    Enabled hdisk1 fscsi0
    Enabled hdisk1 fscsi0
    Enabled hdisk2 fscsi0
    Enabled hdisk2 fscsi0
    Enabled hdisk2 fscsi0
    Enabled hdisk2 fscsi0
    Enabled hdisk3 fscsi0
    Enabled hdisk3 fscsi0
    Enabled hdisk3 fscsi0
    Enabled hdisk3 fscsi0
    Enabled hdisk4 fscsi0
    Enabled hdisk4 fscsi0
    Enabled hdisk4 fscsi0
    Enabled hdisk4 fscsi0
    Enabled hdisk5 fscsi0
    Enabled hdisk5 fscsi0
    Enabled hdisk5 fscsi0
    Enabled hdisk5 fscsi0
    Enabled hdisk6 fscsi0
    Enabled hdisk6 fscsi0
    Enabled hdisk6 fscsi0
    Enabled hdisk6 fscsi0
    Enabled hdisk7 fscsi0
    Enabled hdisk7 fscsi0
    Enabled hdisk7 fscsi0
    Enabled hdisk7 fscsi0
    Enabled hdisk8 fscsi0
    Enabled hdisk8 fscsi0
    Enabled hdisk8 fscsi0
    Enabled hdisk8 fscsi0

    => pcmpath query adapter

    Total Dual Active and Active/Asymmetric Adapters : 1

    Adpt# Name State Mode Select Errors Paths Active
    0 fscsi0 NORMAL ACTIVE 39267 0 36 36


    ======
    I have checked with san& storage teams the zoning and every thing is working fine
    so can any one have advice for that case

    Best Regards,
    Shady Abo shady
    AIX Consultant


    #AIX-Forum


  • 2.  Re: NPIV Fiber Card Issue

    Posted Tue March 22, 2016 08:26 AM

    Originally posted by: MattDulson


    On the face of it the WWPN of your NPIV client on slot 346 can't see any LUNs. This could either be because of SAN zoning meaning it can't see the array or that the WWPN for slot 346 isn't configured on your array to talk to the LUNs.

    You could try using the devscan tool as a diagnostic aid - see http://www-01.ibm.com/support/docview.wss?uid=aixtoolsc9e095f

     


    #AIX-Forum


  • 3.  Re: NPIV Fiber Card Issue

    Posted Wed March 23, 2016 04:30 AM

    Originally posted by: Shady.AboShady


    Dear MattDulson,

     

      thanks for your replay , i have used the mentioned tool and it indicates that luns are coming from fcs0 and fcs2 but at 

      lspath output it shows that only fcs0 can see the luns as below .

     also i tired to enable parent device fcs0 from smitty mpio it couldn't see it only fcs0 

     

    here is the output from vios02 regarding "C246 & C346 " 

    #lsmap -all -npiv 

    Name Physloc ClntID ClntName ClntOS 
    - - - 
    vfchost47 U9179.MHB.10724AP-V2-C246 46 DRTestEDHETLDB AIX 

    Status:LOGGED_IN 
    FC name:fcs11 FC loc code:U78C0.001.DBJF740-P2-C6-T2 
    Ports logged in:1 
    Flags:a<LOGGED_IN,STRIP_MERGE> 
    VFC client name:fcs1 VFC client DRC:U9179.MHB.10724AP-V2-C246 

    Name Physloc ClntID ClntName ClntOS 
    - - - 
    vfchost48 U9179.MHB.10724AP-V2-C346 46 DRTestEDHETLDB AIX 

    Status:LOGGED_IN 
    FC name:fcs14 FC loc code:U78C0.001.DBJF737-P2-C6-T1 
    Ports logged in:1 
    Flags:a<LOGGED_IN,STRIP_MERGE> 
    VFC client name:fcs2 VFC client DRC:U9179.MHB.10724AP-V2-C346 

     

    => lsslot -c slot
    # Slot                      Description       Device(s)
    U9179.MHB.10724AP-V46-C0    Virtual I/O Slot  vsa0
    U9179.MHB.10724AP-V46-C3    Virtual I/O Slot  ent1
    U9179.MHB.10724AP-V46-C146  Virtual I/O Slot  fcs0
    U9179.MHB.10724AP-V46-C246  Virtual I/O Slot  fcs1
    U9179.MHB.10724AP-V46-C346  Virtual I/O Slot  fcs2

    ---------------------------------------------------------------------------

    => /usr/local/bin/devscan

    devscan v1.0.5
    Copyright (C) 2010-2012 IBM Corp., All Rights Reserved

    cmd: /usr/local/bin/devscan
    Current time: 2016-03-23 08:19:47.642878 GMT
    Running on host: prodedhdb

    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Processing FC device:
        Adapter driver: fcs0
        Protocol driver: fscsi0
        Connection type: fabric
        Link State: up
        Current link speed: 8 Gbps
        Local SCSI ID: 0x014a3e
        Local WWPN: 0xc0507603a27b00ce
        Local WWNN: 0xc0507603a27b00ce
        Device ID: Virtual FC Adapter

    SCSI ID LUN ID           WWPN             WWNN
    -----------------------------------------------------------
    011d00  0000000000000000 500507680c212ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk4  Path:            2  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011d00  0002000000000000 500507680c212ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk5  Path:            2  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011d00  0004000000000000 500507680c212ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk6  Path:            2  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011d00  0006000000000000 500507680c212ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk7  Path:            2  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011d00  0008000000000000 500507680c212ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk8  Path:            2  VG:           rootvg
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011b00  0000000000000000 500507680c312ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk4  Path:            0  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011b00  0002000000000000 500507680c312ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk5  Path:            0  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011b00  0004000000000000 500507680c312ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk6  Path:            0  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011b00  0006000000000000 500507680c312ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk7  Path:            0  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011b00  0008000000000000 500507680c312ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk8  Path:            0  VG:           rootvg
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011e00  0000000000000000 500507680c212fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk4  Path:            3  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011e00  0002000000000000 500507680c212fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk5  Path:            3  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011e00  0004000000000000 500507680c212fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk6  Path:            3  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011e00  0006000000000000 500507680c212fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk7  Path:            3  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011e00  0008000000000000 500507680c212fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk8  Path:            3  VG:           rootvg
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011c00  0000000000000000 500507680c312fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk4  Path:            1  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011c00  0002000000000000 500507680c312fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk5  Path:            1  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011c00  0004000000000000 500507680c312fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk6  Path:            1  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011c00  0006000000000000 500507680c312fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk7  Path:            1  VG:      DR-BackupVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011c00  0008000000000000 500507680c312fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk8  Path:            1  VG:           rootvg
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011800  0000000000000000 500507680c212fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Not connected      PDT: Unknown
        Name:     No ODM match  VG:       None found
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        ALUA-capable device

    011800  0001000000000000 500507680c212fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk0  Path:            3  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011800  0003000000000000 500507680c212fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk1  Path:            3  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011800  0005000000000000 500507680c212fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk2  Path:            3  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011800  0007000000000000 500507680c212fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk3  Path:            3  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011700  0000000000000000 500507680c312fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Not connected      PDT: Unknown
        Name:     No ODM match  VG:       None found
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        ALUA-capable device

    011700  0001000000000000 500507680c312fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk0  Path:            2  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011700  0003000000000000 500507680c312fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk1  Path:            2  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011700  0005000000000000 500507680c312fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk2  Path:            2  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011700  0007000000000000 500507680c312fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk3  Path:            2  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011300  0000000000000000 500507680c212e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Not connected      PDT: Unknown
        Name:     No ODM match  VG:       None found
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        ALUA-capable device

    011300  0001000000000000 500507680c212e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk0  Path:            1  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011300  0003000000000000 500507680c212e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk1  Path:            1  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011300  0005000000000000 500507680c212e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk2  Path:            1  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011300  0007000000000000 500507680c212e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk3  Path:            1  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011100  0000000000000000 500507680c312e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Not connected      PDT: Unknown
        Name:     No ODM match  VG:       None found
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        ALUA-capable device

    011100  0001000000000000 500507680c312e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk0  Path:            0  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011100  0003000000000000 500507680c312e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk1  Path:            0  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011100  0005000000000000 500507680c312e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk2  Path:            0  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    011100  0007000000000000 500507680c312e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:           hdisk3  Path:            0  VG:          EdhDbVG
        Device already SCIOLSTARTed    Dynamic Tracking Enabled
        Status: Enabled
        ALUA-capable device

    8 targets found, reporting 40 LUNs,
    40 of which responded to SCIOLSTART.
    Elapsed time this adapter: 00.406194 seconds

    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Processing FC device:
        Adapter driver: fcs1
        Protocol driver: fscsi1
        Connection type: fabric
        Link State: up
        Current link speed: 8 Gbps
        Local SCSI ID: 0x020a18
        Local WWPN: 0xc0507603a27b00d6
        Local WWNN: 0xc0507603a27b00d6
        Device ID: Virtual FC Adapter


    Nameserver query succeeded, but indicated
    no targets are available on the SAN

    No targets found
    Elapsed time this adapter: 00.010227 seconds

    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Processing FC device:
        Adapter driver: fcs2
        Protocol driver: fscsi2
        Connection type: fabric
        Link State: up
        Current link speed: 8 Gbps
        Local SCSI ID: 0x024706
        Local WWPN: 0xc0507603a27b00d8
        Local WWNN: 0xc0507603a27b00d8
        Device ID: Virtual FC Adapter

    SCSI ID LUN ID           WWPN             WWNN
    -----------------------------------------------------------
    021f00  0000000000000000 500507680c122ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021f00  0002000000000000 500507680c122ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021f00  0004000000000000 500507680c122ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021f00  0006000000000000 500507680c122ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021f00  0008000000000000 500507680c122ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021b00  0000000000000000 500507680c522ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021b00  0002000000000000 500507680c522ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021b00  0004000000000000 500507680c522ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021b00  0006000000000000 500507680c522ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021b00  0008000000000000 500507680c522ea6 500507680c002ea6
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021e00  0000000000000000 500507680c122fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021e00  0002000000000000 500507680c122fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021e00  0004000000000000 500507680c122fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021e00  0006000000000000 500507680c122fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021e00  0008000000000000 500507680c122fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021c00  0000000000000000 500507680c522fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021c00  0002000000000000 500507680c522fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021c00  0004000000000000 500507680c522fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021c00  0006000000000000 500507680c522fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021c00  0008000000000000 500507680c522fc4 500507680c002fc4
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021a00  0000000000000000 500507680c122fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Not connected      PDT: Unknown
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021a00  0001000000000000 500507680c122fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021a00  0003000000000000 500507680c122fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021a00  0005000000000000 500507680c122fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021a00  0007000000000000 500507680c122fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021700  0000000000000000 500507680c522fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Not connected      PDT: Unknown
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021700  0001000000000000 500507680c522fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021700  0003000000000000 500507680c522fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021700  0005000000000000 500507680c522fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021700  0007000000000000 500507680c522fca 500507680c002fca
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021500  0000000000000000 500507680c122e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Not connected      PDT: Unknown
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021500  0001000000000000 500507680c122e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021500  0003000000000000 500507680c122e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021500  0005000000000000 500507680c122e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021500  0007000000000000 500507680c122e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021100  0000000000000000 500507680c522e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Not connected      PDT: Unknown
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021100  0001000000000000 500507680c522e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021100  0003000000000000 500507680c522e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021100  0005000000000000 500507680c522e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    021100  0007000000000000 500507680c522e40 500507680c002e40
        Vendor ID: IBM          Device ID: 2145     Rev: 0000 NACA: yes
        PDQ: Connected          PDT: Block (Disc)
        Name:     No ODM match  VG:       None found
        Dynamic Tracking Enabled
        ALUA-capable device

    8 targets found, reporting 40 LUNs,
    40 of which responded to SCIOLSTART.
    Elapsed time this adapter: 00.384295 seconds

    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Processing iSCSI device:
        Protocol driver: iscsi0

    No targets found
    Elapsed time this adapter: 00.002636 seconds

    44 device(s) on the SAN were not found in the ODM.
    Generally, this means these devices were made available on the SAN
    after the last time cfgmgr was run on this host, or that these
    devices were deleted out of the ODM.


    Cleaning up...
    Total elapsed time: 00.912715 seconds
    Completed successfully

    =>

     

    ============================

    => lspath
    Enabled hdisk0 fscsi0
    Enabled hdisk0 fscsi0
    Enabled hdisk0 fscsi0
    Enabled hdisk0 fscsi0
    Enabled hdisk1 fscsi0
    Enabled hdisk1 fscsi0
    Enabled hdisk1 fscsi0
    Enabled hdisk1 fscsi0
    Enabled hdisk2 fscsi0
    Enabled hdisk2 fscsi0
    Enabled hdisk2 fscsi0
    Enabled hdisk2 fscsi0
    Enabled hdisk3 fscsi0
    Enabled hdisk3 fscsi0
    Enabled hdisk3 fscsi0
    Enabled hdisk3 fscsi0
    Enabled hdisk4 fscsi0
    Enabled hdisk4 fscsi0
    Enabled hdisk4 fscsi0
    Enabled hdisk4 fscsi0
    Enabled hdisk5 fscsi0
    Enabled hdisk5 fscsi0
    Enabled hdisk5 fscsi0
    Enabled hdisk5 fscsi0
    Enabled hdisk6 fscsi0
    Enabled hdisk6 fscsi0
    Enabled hdisk6 fscsi0
    Enabled hdisk6 fscsi0
    Enabled hdisk7 fscsi0
    Enabled hdisk7 fscsi0
    Enabled hdisk7 fscsi0
    Enabled hdisk7 fscsi0
    Enabled hdisk8 fscsi0
    Enabled hdisk8 fscsi0
    Enabled hdisk8 fscsi0
    Enabled hdisk8 fscsi0

     


    #AIX-Forum


  • 4.  Re: NPIV Fiber Card Issue

    Posted Wed March 23, 2016 10:57 AM

    Originally posted by: jklotz


    hello,

     

    what does show you a fcstat on the VIO whose FC port doesnt show up on the LPAR ?


    #AIX-Forum


  • 5.  Re: NPIV Fiber Card Issue

    Posted Thu March 24, 2016 04:14 AM

    Originally posted by: Shady.AboShady


    Dears,

      thanks too much for your support , after reviewing configs again we found a mistake at zoning from SAN team at SAN Switches .


    #AIX-Forum