HBA Fibre Card for VIOS IVM POWERVM | Unix Linux Forums | AIX

  Go Back    


AIX AIX is IBM's industry-leading UNIX operating system that meets the demands of applications that businesses rely upon in today's marketplace.

HBA Fibre Card for VIOS IVM POWERVM

AIX


Tags
aix, unix

Closed Thread    
 
Thread Tools Search this Thread Display Modes
    #1  
Old 03-13-2013
filosophizer filosophizer is offline
Registered User
 
Join Date: Jan 2009
Last Activity: 27 January 2014, 7:13 AM EST
Posts: 299
Thanks: 44
Thanked 13 Times in 7 Posts
HBA Fibre Card for VIOS IVM POWERVM

I had previously asked a question in this thread

and was answered:
Quote:
Originally Posted by dukessd View Post
POWER7 information
Dynamically managing physical adapters

IBM

You can use the Integrated Virtualization Manager to change the physical adapters that a running logical partition uses.

ensure that the Integrated Virtualization Manager is at version 1.5 or later.

HTH

I checked the above link and checked my POWERVM IVM

For the IVM VIOS Partition
Dynamic Logical Partitioning (DLPAR)


Partition hostname or IP address: xx.xx.xx.xx
Partition communication state: Active
Memory DLPAR capable: Yes
Processing DLPAR capable: Yes
I/O adapter DLPAR capable: Yes

For all other Client Partitions, which are switched on and off
Partition hostname or IP address:
Partition communication state: Not Configured
Memory DLPAR capable: No
Processing DLPAR capable: No
I/O adapter DLPAR capable: No



Question #1 : How can I enable the client partitions to be I/O adapter DLPAR capable: YES ?

Now, my system plan on IVM VIOS shows regarding the Fibre Adapter


Code:
Cards  
Backplane Slot Bus Device Feature or CCIN Device Description Device Serial # Order Status Used by Partition / Profile 
P1    C1     3            Fibre Channel Serial Bus 1F8030C37B           Own               vios / vios 


Code:
# lsdev -Cc adapter | grep fcs0
fcs0      Available 0A-08 FC Adapter

# lscfg -vl fcs0
  fcs0             U787B.001.DNW3313-P1-C1-T1  FC Adapter

        Part Number.................10N8620
        Serial Number...............1F8030C37B
        Manufacturer................001F
        EC Level....................A
        Customer Card ID Number.....5759
        FRU Number.................. 10N8620
        Device Specific.(ZM)........3
        Network Address.............10000000C9707270
        ROS Level and ID............02C82138
        Device Specific.(Z0)........1036406D
        Device Specific.(Z1)........00000000
        Device Specific.(Z2)........00000000
        Device Specific.(Z3)........03000909
        Device Specific.(Z4)........FFC01159
        Device Specific.(Z5)........02C82138
        Device Specific.(Z6)........06C12138
        Device Specific.(Z7)........07C12138
        Device Specific.(Z8)........20000000C9707270
        Device Specific.(Z9)........BS2.10X8
        Device Specific.(ZA)........B1F2.10X8
        Device Specific.(ZB)........B2F2.10X8
        Device Specific.(ZC)........00000000
        Hardware Location Code......U787B.001.DNW3313-P1-C1-T1

# lsdev -p fcs0
fcnet0 Defined   0A-08-01 Fibre Channel Network Protocol Device
fscsi0 Available 0A-08-02 FC SCSI I/O Controller Protocol Device
# lsdev -p fcs1
fcnet1 Defined   0A-09-01 Fibre Channel Network Protocol Device
fscsi1 Available 0A-09-02 FC SCSI I/O Controller Protocol Device
#


# rmdev -Rdl fcs0
fcnet0 deleted
fscsi0 deleted
fcs0 deleted
# rmdev -Rdl fcs1
fcnet1 deleted
fscsi1 deleted
fcs1 deleted
# cfgmgr
Method error (/usr/lib/methods/cfgefscsi -l fscsi0 ):
        0514-061 Cannot find a child device.
Method error (/usr/lib/methods/cfgefscsi -l fscsi1 ):
        0514-061 Cannot find a child device.

# lscfg | grep fcs
+ fcs0             U787B.001.DNW3313-P1-C1-T1       FC Adapter
+ fcs1             U787B.001.DNW3313-P1-C1-T2       FC Adapter
# lscfg | grep fcnet
* fcnet0           U787B.001.DNW3313-P1-C1-T1       Fibre Channel Network Protocol Device
* fcnet1           U787B.001.DNW3313-P1-C1-T2       Fibre Channel Network Protocol Device
# lscfg | grep fscsi
+ fscsi0           U787B.001.DNW3313-P1-C1-T1       FC SCSI I/O Controller Protocol Device
+ fscsi1           U787B.001.DNW3313-P1-C1-T2       FC SCSI I/O Controller Protocol Device

# lsdev -p fcs0
fcnet0 Defined   0A-08-01 Fibre Channel Network Protocol Device
fscsi0 Available 0A-08-02 FC SCSI I/O Controller Protocol Device
# lsdev -p fcs1
fcnet1 Defined   0A-09-01 Fibre Channel Network Protocol Device
fscsi1 Available 0A-09-02 FC SCSI I/O Controller Protocol Device
#

Question #2 : Is it must to have fcnet0 Available for the working for Fibre Card and getting a SAN Drive ? I have not yet connected the SAN, because I have to order it, and before that I want to ensure, it can work with the existing config.



Thank You.
Sponsored Links
    #2  
Old 03-14-2013
MichaelFelt MichaelFelt is offline
Registered User
 
Join Date: Nov 2012
Last Activity: 11 December 2013, 7:33 AM EST
Location: on the road for work; home is private time
Posts: 311
Thanks: 6
Thanked 76 Times in 71 Posts
I use IVM a lot, but do not have any Power6, now do I have the funding for buying a SAN. My systems are not provided by work.

I have never used the feature to move I/O adapters. I have never needed it. (wanted yes, but needed, no.) Instead I use virtual scsi.

With internal disks I have two volume groups: rootvg and a vgClient. I try and only use logical partitions from vgClient as boot disks for the client partitions.

Recently I have been using iSCSI to provide additional disks. I have put iSCSI disks "into" the VIOS/IVM and been able to share these via no_reserve to multiple partitions. I have also created iSCSI luns and both traditional LP backed remote disks as well as FileBacked remote disks.

Obviously, there are better ways to get performance (buying a better NAS and getting Gbit network installed helpd a lot!).

Before I forget: the DLPAR capabilities: since they are all no (when off that is obvious - there are no RMC daemons running, so no DLPAR communication is available). If you are still seeing that - after pressing the "retrieve capabilities" button - then apparently there is no IP communication between the VIOS (functioning as HMC "master" for this purpose) and the partitions. May also be they need a few more minutes to establish the communication links (by design, may take up to 5 minutes).

Hope this helps!
Sponsored Links
    #3  
Old 03-14-2013
filosophizer filosophizer is offline
Registered User
 
Join Date: Jan 2009
Last Activity: 27 January 2014, 7:13 AM EST
Posts: 299
Thanks: 44
Thanked 13 Times in 7 Posts
Quote:
Originally Posted by MichaelFelt View Post
I use IVM a lot, but do not have any Power6, now do I have the funding for buying a SAN. My systems are not provided by work.

I have never used the feature to move I/O adapters. I have never needed it. (wanted yes, but needed, no.) Instead I use virtual scsi.

With internal disks I have two volume groups: rootvg and a vgClient. I try and only use logical partitions from vgClient as boot disks for the client partitions.

Recently I have been using iSCSI to provide additional disks. I have put iSCSI disks "into" the VIOS/IVM and been able to share these via no_reserve to multiple partitions. I have also created iSCSI luns and both traditional LP backed remote disks as well as FileBacked remote disks.

Obviously, there are better ways to get performance (buying a better NAS and getting Gbit network installed helpd a lot!).

Before I forget: the DLPAR capabilities: since they are all no (when off that is obvious - there are no RMC daemons running, so no DLPAR communication is available). If you are still seeing that - after pressing the "retrieve capabilities" button - then apparently there is no IP communication between the VIOS (functioning as HMC "master" for this purpose) and the partitions. May also be they need a few more minutes to establish the communication links (by design, may take up to 5 minutes).

Hope this helps!
I don't have POWER6 either, I have power5 without HMC.
The partitions are running for 10 days now under VIOS/IVM and still I cannot see the DLPAR communication functions availability on the client Partitions.

Thanks for the tip about sharing internal disks through vscsi.

But, I want to know if I can attach SAN Storage through switch on POWER5 running IVM VIOS. So, the disks will be owned/handled by IVM/VIOS and then as you mentioned using vscsi to assign to the partitions.
    #4  
Old 03-15-2013
MichaelFelt MichaelFelt is offline
Registered User
 
Join Date: Nov 2012
Last Activity: 11 December 2013, 7:33 AM EST
Location: on the road for work; home is private time
Posts: 311
Thanks: 6
Thanked 76 Times in 71 Posts
of course you can attach san disks to vios partition.

you can share the luns via mkvdev -dev hdiskX -vadapter vhostZ ... just as if they are internal disks.

i thought you wanted to move the HBA to the client partition. Rumor says that can be done with IVM - I have never verified that personally. please forgive any misunderstanding on my part.

hope this helps.

p.s. I will find the command to reset the RMC communication. might need an external link for a picture. really fighting with my tablet. i still strongly dislike the virtual keyboard, and my finger seems to be a failed pointer when it comes to selecting text
The Following User Says Thank You to MichaelFelt For This Useful Post:
filosophizer (03-15-2013)
Sponsored Links
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
CD-ROM issue with PowerVM IVM VIOS filosophizer AIX 2 01-02-2013 06:29 AM
IBM VIOS POWERVM IVM error filosophizer AIX 2 12-17-2012 03:28 AM
VIOS IVM unavailable - how do I restart it? need2bageek AIX 2 02-24-2011 12:24 PM
PowerVM Express and IVM limitations JodyTek AIX 1 05-01-2008 01:19 PM



All times are GMT -4. The time now is 10:57 PM.