Topic
  • 5 replies
  • Latest Post - ‏2012-02-24T12:04:25Z by robinsguk
robinsguk
robinsguk
30 Posts

Pinned topic MPIO in VIOS

‏2012-02-20T14:50:58Z |
Hello,

I'm running a couple of VIOS's at 2.2.1.3.

Each has a 2 port fc adapter which have connections to a switch and then on to a DS5100.

When I run mpio_get_config -Av I get "Error: Unable to find devices."

I can see the LUNs mapped to the server.

lsattr -El fscsiX shows:
attach switch How this adapter is CONNECTED False
dyntrk yes Dynamic Tracking of FC Devices True
fc_err_recov fast_fail FC Fabric Event Error RECOVERY Policy True
scsi_id 0x30500 Adapter SCSI ID False
sw_fc_class 3 FC Class for Fabric True
What's causing mpio_get_config to error?

Thanks

Glenn
Updated on 2012-02-24T12:04:25Z at 2012-02-24T12:04:25Z by robinsguk
  • The_Doctor
    The_Doctor
    80 Posts

    Re: MPIO in VIOS

    ‏2012-02-20T16:21:59Z  
    Are you sure you're using MPIO ? What's:
    
    oem_setup_env lsdev -Cc disk lsattr -El hdisk*
    

    say ?

    Maybe you have SDDPCM installed..... in which case, you'd want to something like:
    
    oem_setup_env pcmpath query device sddpcm_get_config -Av
    


    BTW, if you would use the "code" tags..... it would make life much easier for those of us trying to decipher your command output.
  • robinsguk
    robinsguk
    30 Posts

    Re: MPIO in VIOS

    ‏2012-02-21T10:37:19Z  
    Are you sure you're using MPIO ? What's:
    <pre class="jive-pre"> oem_setup_env lsdev -Cc disk lsattr -El hdisk* </pre>
    say ?

    Maybe you have SDDPCM installed..... in which case, you'd want to something like:
    <pre class="jive-pre"> oem_setup_env pcmpath query device sddpcm_get_config -Av </pre>

    BTW, if you would use the "code" tags..... it would make life much easier for those of us trying to decipher your command output.
    Here's one of the disks, hdisk5
    root@UK-P02-VIOSA:/home/padmin lsdev -Cc disk
    hdisk0 Available 03-00-00 SAS Disk Drive
    hdisk1 Available 03-00-00 SAS Disk Drive
    hdisk2 Available 04-00-00 SAS Disk Drive
    hdisk3 Available 04-00-00 SAS Disk Drive
    hdisk4 Available 01-00-02 MPIO IBM 2076 FC Disk
    hdisk5 Available 01-00-02 MPIO IBM 2076 FC Disk
    hdisk6 Available 01-00-02 MPIO IBM 2076 FC Disk
    hdisk7 Available 01-00-02 MPIO IBM 2076 FC Disk
    hdisk8 Available 01-00-02 MPIO IBM 2076 FC Disk

    root@UK-P02-VIOSA:/home/padmin lsattr -El hdisk5
    PCM PCM/friend/fcpother Path Control Module False
    algorithm round_robin Algorithm True
    clr_q no Device CLEARS its Queue on error True
    dist_err_pcnt 0 Distributed Error Percentage True
    dist_tw_width 50 Distributed Error Sample Time True
    hcheck_cmd test_unit_rdy Health Check Command True
    hcheck_interval 60 Health Check Interval True
    hcheck_mode nonactive Health Check Mode True
    location Location Label True
    lun_id 0x1000000000000 Logical Unit Number ID False
    lun_reset_spt yes LUN Reset Supported True
    max_retry_delay 60 Maximum Quiesce Time True
    max_transfer 0x40000 Maximum TRANSFER Size True
    node_name 0x5005076802001ec6 FC Node Name False
    pvid none Physical volume identifier False
    q_err yes Use QERR bit True
    q_type simple Queuing TYPE True
    queue_depth 8 Queue DEPTH True
    reassign_to 120 REASSIGN time out value True
    reserve_policy no_reserve Reserve Policy True
    rw_timeout 30 READ/WRITE time out value True
    scsi_id 0x50800 SCSI ID False
    start_timeout 60 START unit time out value True
    timeout_policy fail_path Timeout Policy True
    unique_id 3321360050768028180DD700000000000000604214503IBMfcp Unique device identifier False
    ww_name 0x5005076802101ec6 FC World Wide Name False
  • ey344
    ey344
    15 Posts

    Re: MPIO in VIOS

    ‏2012-02-21T11:27:35Z  
    • robinsguk
    • ‏2012-02-21T10:37:19Z
    Here's one of the disks, hdisk5
    root@UK-P02-VIOSA:/home/padmin lsdev -Cc disk
    hdisk0 Available 03-00-00 SAS Disk Drive
    hdisk1 Available 03-00-00 SAS Disk Drive
    hdisk2 Available 04-00-00 SAS Disk Drive
    hdisk3 Available 04-00-00 SAS Disk Drive
    hdisk4 Available 01-00-02 MPIO IBM 2076 FC Disk
    hdisk5 Available 01-00-02 MPIO IBM 2076 FC Disk
    hdisk6 Available 01-00-02 MPIO IBM 2076 FC Disk
    hdisk7 Available 01-00-02 MPIO IBM 2076 FC Disk
    hdisk8 Available 01-00-02 MPIO IBM 2076 FC Disk

    root@UK-P02-VIOSA:/home/padmin lsattr -El hdisk5
    PCM PCM/friend/fcpother Path Control Module False
    algorithm round_robin Algorithm True
    clr_q no Device CLEARS its Queue on error True
    dist_err_pcnt 0 Distributed Error Percentage True
    dist_tw_width 50 Distributed Error Sample Time True
    hcheck_cmd test_unit_rdy Health Check Command True
    hcheck_interval 60 Health Check Interval True
    hcheck_mode nonactive Health Check Mode True
    location Location Label True
    lun_id 0x1000000000000 Logical Unit Number ID False
    lun_reset_spt yes LUN Reset Supported True
    max_retry_delay 60 Maximum Quiesce Time True
    max_transfer 0x40000 Maximum TRANSFER Size True
    node_name 0x5005076802001ec6 FC Node Name False
    pvid none Physical volume identifier False
    q_err yes Use QERR bit True
    q_type simple Queuing TYPE True
    queue_depth 8 Queue DEPTH True
    reassign_to 120 REASSIGN time out value True
    reserve_policy no_reserve Reserve Policy True
    rw_timeout 30 READ/WRITE time out value True
    scsi_id 0x50800 SCSI ID False
    start_timeout 60 START unit time out value True
    timeout_policy fail_path Timeout Policy True
    unique_id 3321360050768028180DD700000000000000604214503IBMfcp Unique device identifier False
    ww_name 0x5005076802101ec6 FC World Wide Name False
    hdisk5 Available 01-00-02 MPIO IBM 2076 FC Disk - that looks something like a V7000.

    The mpio_get_config command is only applicable for DS3000 and DS4000 presented disk. However I'm also looking for the equivalent command for V7000 presented disk.

    From your lsattr command, the unique_id field matches the UID of the Volume on the V7000, so it is possible to be sure to match a Volume to it's hdisk equivalent in VIOS. There surely must be a nicer way of getting the info though.

    Ed
  • robinsguk
    robinsguk
    30 Posts

    Re: MPIO in VIOS

    ‏2012-02-21T11:42:31Z  
    • ey344
    • ‏2012-02-21T11:27:35Z
    hdisk5 Available 01-00-02 MPIO IBM 2076 FC Disk - that looks something like a V7000.

    The mpio_get_config command is only applicable for DS3000 and DS4000 presented disk. However I'm also looking for the equivalent command for V7000 presented disk.

    From your lsattr command, the unique_id field matches the UID of the Volume on the V7000, so it is possible to be sure to match a Volume to it's hdisk equivalent in VIOS. There surely must be a nicer way of getting the info though.

    Ed
    Doh!, of course it is.

    I'll have a hunt around too to see if I can find the command?

    Glenn
  • robinsguk
    robinsguk
    30 Posts

    Re: MPIO in VIOS

    ‏2012-02-24T12:04:25Z  
    • robinsguk
    • ‏2012-02-21T11:42:31Z
    Doh!, of course it is.

    I'll have a hunt around too to see if I can find the command?

    Glenn
    Sometimes things are so obvious.

    V7000=SVC therefore sddpcm required.