Topic
  • 6 replies
  • Latest Post - ‏2012-05-12T07:20:54Z by SystemAdmin
prashanna
prashanna
2 Posts

Pinned topic VIO query

‏2011-07-19T07:13:11Z |
Hi,

What is the command to be executed from VIO Client to find it's VIO Server name...

Thanks
Updated on 2012-05-12T07:20:54Z at 2012-05-12T07:20:54Z by SystemAdmin
  • ostost
    ostost
    16 Posts

    Re: VIO query

    ‏2011-07-21T17:02:05Z  
    There is no command available to do that
  • tony.evans
    tony.evans
    55 Posts

    Re: VIO query

    ‏2011-07-22T07:59:40Z  
    There isn't a 1-to-1 relationship between partitions and the VIO servers they may use.

    There may be 3 VIO servers, and a partition could be using virtual resources from all, none or some of them at the same time.

    In terms of virtual networking, the partitions have no concept of being connected to a VIO server. The partitions put packets onto the PowerVM virtual ethernet switch, and some of the VIO servers depending on configuration move that data to the physical network.

    For storage, there is a more direct relationship, but it's still not 1-to-1 and is (partition) 1-to-many (vio).

    I'll say the same thing I tell my team mates - if you want to know, you have to draw the diagram. Partition to VIO configurations are documented in several places, HMC, VIO, Client and the best way to know what's going on is use the standard commands (lscfg, lsdev) and the HMC and draw a diagram.
  • Theeraph
    Theeraph
    21 Posts

    Re: VIO query

    ‏2011-07-27T08:41:05Z  
    Hi,
    .
    1. (Since the system I use have only virtual FC (NPIV), but no virtual SCSI.)
    Find out this VIO client LPAR ID and managed system serial number:
    .
    • find the FC adapter that is virtual:
    efs-db-t1:root:/root> lsdev -Cc adapter|grep fcs
    fcs0 Available 41-T1 Virtual Fibre Channel Client Adapter
    fcs1 Available 42-T1 Virtual Fibre Channel Client Adapter
    fcs2 Available 43-T1 Virtual Fibre Channel Client Adapter
    fcs3 Available 44-T1 Virtual Fibre Channel Client Adapter
    .
    In this case, we can use any fcs.
    .
    • find LPAR ID of this VIO client and managed system serial number:
    efs-db-t1:root:/root> lscfg -vl fcs0
    fcs0 U8205.E6B.068FD1P-V66-C41-T1 Virtual Fibre Channel Client Adapter
    ...
    ...omitted...
    ...
    .
    In this case, LPAR_ID is 66 and slot number for this virtual adapter is 41. The managed system that contains this partition type/model is 8205-E6B with serial number 068FD1P.
    .
    2 (This assumes that this VIO client communication to HMC works)
    Find out HMC IP address/hostname:
    .
    efs-db-t1:root:/root> /usr/sbin/rsct/bin/ctsthl -l|grep Host
    Host Identity: efs-hmcdc1.localdomain
    Host Identity: 172.22.40.98
    Host Identity: loopback
    Host Identity: ::1
    Host Identity: 127.0.0.1
    Host Identity: 1.1.1.66
    Host Identity: efs-db-t1v
    .
    The "Host Identity" IP/hostname that does not belong to this VIO client should belong to HMC. (In this case 172.22.40.98)
    .
    3. (Assume that you know the password of hscroot user on HMC)
    .
    Find out the managed system name:
    .
    efs-db-t1:root:/root> ssh hscroot@172.22.40.98 lssyscfg -r sys -F name,type_model,serial_num,state
    .
    EFS-VT-P1 P740-1,8205-E6B,068FD1P,Operating
    EFS-VT-P2 P740-2,8205-E6B,068FD2P,Operating
    .
    In this case, for serial number "068FD1P", the managed system name is "EFS-VT-P1 P740-1".
    .
    4. Find out VIOS LPAR ID and LPAR name:
    .
    efs-db-t1:root:/root> ssh hscroot@172.22.40.98 lshwres -m "EFS-VT-P1\ P740-1" -r virtualio --rsubtype fc --level lpar --filter "lpar_ids=66"
    .
    lpar_name=efs-db-t1,lpar_id=66,slot_num=41,adapter_type=client,state=1,is_required=1,remote_lpar_id=71,remote_lpar_name=efs-vios1a,remote_slot_num=66,"wwpns=c0507603dc850030,c0507603dc850031"
    lpar_name=efs-db-t1,lpar_id=66,slot_num=42,adapter_type=client,state=1,is_required=1,remote_lpar_id=72,remote_lpar_name=efs-vios1b,remote_slot_num=66,"wwpns=c0507603dc850032,c0507603dc850033"
    ...
    ...omitted...
    ...
    .
    In this case, we have 2 VIOS servers with LPAR ID 71 (LPAR name efs-vios1a) and LPAR ID 72 (LPAR name efs-vios2a).
    .
    5. Find out VIOS IP address:
    .
    efs-db-t1:root:/root> ssh hscroot@172.22.40.98 lssyscfg -m "EFS-VT-P1\ P740-1" -r lpar -F lpar_id,name,rmc_ipaddr | sort
    ...
    ...omitted...
    ...
    71,efs-vios1a,172.22.40.93
    72,efs-vios1b,172.22.40.94
    73,efs-dmgr1,172.22.29.31
    74,efs-nimdc1,172.22.40.95
    .
    So the IP addresses of VIOS are 172.22.40.93 and 172.22.40.94.
    .
    (Sorry, I can only find out LPAR ID, LPAR name and one IP address of VIOS server. I cannot think of the way to get VIOS hostname yet...)
    .
    Hope this helps,
    Theeraphong
  • PrashannaVenkatesh
    PrashannaVenkatesh
    3 Posts

    Re: VIO query

    ‏2011-08-17T10:51:50Z  
    Many Thanks to all responded
  • SystemAdmin
    SystemAdmin
    1743 Posts

    Re: VIO query

    ‏2012-04-26T16:36:14Z  
    Many Thanks to all responded
    use the kdb utlity to find the vio server and vhost utility

    echo " cvai" | kdb
  • SystemAdmin
    SystemAdmin
    1743 Posts

    Re: VIO query

    ‏2012-05-12T07:20:54Z  
    use the kdb utlity to find the vio server and vhost utility

    echo " cvai" | kdb
    I also use kdb for lpar using 'Virtual Fibre Channel Adapter' to find associated VIO Server :

    
    # lsdev -Cc adapter | grep fcs fcs0 Available 10-T1 Virtual Fibre Channel Client Adapter fcs1 Available 11-T1 Virtual Fibre Channel Client Adapter
    


    
    # kdb The specified kernel file is a 64-bit kernel. [..] (0)> vfcs NAME      ADDRESS             STATE   HOST      HOST_ADAP  OPENED NUM_ACTIVE fcs0      0xF10001003AE1F000  0x0008  vios1 vfchost2  0x01    0x0000 fcs1      0xF10001003A693000  0x0008  vios2 vfchost2  0x01    0x0000
    


    Hope this can help.

    Benoit.