How to put vscsi in available state?


 
Thread Tools Search this Thread
Operating Systems AIX How to put vscsi in available state?
# 8  
Old 07-28-2015
Quote:
Originally Posted by agent.kgb
There can be at least 3 possible problems:
  1. you didn't connect client VSCSI device to a server VSCSI device.
  2. you connected client VSCSI device to wrong server VSCSI device.
  3. you connected client VSCSI device to the right server VSCSI device, but made a mistake in a device definition (wrong LPAR ID).
On server4 side:
Code:
lscfg -l vscsi1

On VIOS side:
Code:
lsdev -dev vhost* -vpd

On HMC side:
Code:
lssyscfg -r prof -m YOUR_MANAGED_SYSTEM --filter "lpar_names=YOUR_VIOS" -F virtual_scsi_adapters
lssyscfg -r prof -m YOUR_MANAGED_SYSTEM --filter "lpar_names=server4" -F virtual_scsi_adapters


Thanks, I just started this job a little over a month ago and just trying to make the companies environment healthy, "or trying, HA", don't know who set this up and when..

#:/>lscfg -l vscsi1
vscsi1 U8205.E6D.211476V-V6-C41-T1 Virtual SCSI Client Adapter



Output of VIOSDEV1 below
Code:
  $ lsdev -dev vhost* -vpd
    vhost7           U8205.E6D.211476V-V1-C90  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V1-C90
   
    vhost6           U8205.E6D.211476V-V1-C80  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V1-C80
   
    vhost5           U8205.E6D.211476V-V1-C70  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V1-C70
   
    vhost4           U8205.E6D.211476V-V1-C60  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V1-C60
   
    vhost3           U8205.E6D.211476V-V1-C40  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V1-C40
   
    vhost2           U8205.E6D.211476V-V1-C30  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V1-C30
   
    vhost1           U8205.E6D.211476V-V1-C50  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V1-C50
   
    vhost0           U8205.E6D.211476V-V1-C20  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V1-C20
   
   
    PLATFORM SPECIFIC
   
    Name:  v-scsi-host
      Node:  v-scsi-host@30000014
      Physical Location: U8205.E6D.211476V-V1-C20
   
    Name:  v-scsi-host
      Node:  v-scsi-host@30000032
      Physical Location: U8205.E6D.211476V-V1-C50
   
    Name:  v-scsi-host
      Node:  v-scsi-host@3000001e
      Physical Location: U8205.E6D.211476V-V1-C30
   
    Name:  v-scsi-host
      Node:  v-scsi-host@30000028
      Physical Location: U8205.E6D.211476V-V1-C40
   
    Name:  v-scsi-host
      Node:  v-scsi-host@3000003c
      Physical Location: U8205.E6D.211476V-V1-C60
   
    Name:  v-scsi-host
      Node:  v-scsi-host@30000046
      Physical Location: U8205.E6D.211476V-V1-C70
   
    Name:  v-scsi-host
      Node:  v-scsi-host@30000050
      Physical Location: U8205.E6D.211476V-V1-C80
   
    Name:  v-scsi-host
      Node:  v-scsi-host@3000005a
      Physical Location: U8205.E6D.211476V-V1-C90
  $
   
  Output of VIOSDEV2 below
  $ lsdev -dev vhost* -vpd
    vhost7           U8205.E6D.211476V-V2-C91  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V2-C91
   
    vhost6           U8205.E6D.211476V-V2-C81  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V2-C81
   
    vhost5           U8205.E6D.211476V-V2-C71  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V2-C71
   
    vhost4           U8205.E6D.211476V-V2-C61  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V2-C61
   
    vhost3           U8205.E6D.211476V-V2-C41  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V2-C41
   
    vhost2           U8205.E6D.211476V-V2-C31  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V2-C31
   
    vhost1           U8205.E6D.211476V-V2-C51  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V2-C51
   
    vhost0           U8205.E6D.211476V-V2-C21  Virtual SCSI Server Adapter
   
          Hardware Location Code......U8205.E6D.211476V-V2-C21
   
   
    PLATFORM SPECIFIC
   
    Name:  v-scsi-host
      Node:  v-scsi-host@30000015
      Physical Location: U8205.E6D.211476V-V2-C21
   
    Name:  v-scsi-host
      Node:  v-scsi-host@30000033
      Physical Location: U8205.E6D.211476V-V2-C51
   
    Name:  v-scsi-host
      Node:  v-scsi-host@3000001f
      Physical Location: U8205.E6D.211476V-V2-C31
   
    Name:  v-scsi-host
      Node:  v-scsi-host@30000029
      Physical Location: U8205.E6D.211476V-V2-C41
   
    Name:  v-scsi-host
      Node:  v-scsi-host@3000003d
      Physical Location: U8205.E6D.211476V-V2-C61
   
    Name:  v-scsi-host
      Node:  v-scsi-host@30000047
      Physical Location: U8205.E6D.211476V-V2-C71
   
    Name:  v-scsi-host
      Node:  v-scsi-host@30000051
      Physical Location: U8205.E6D.211476V-V2-C81
   
    Name:  v-scsi-host
      Node:  v-scsi-host@3000005b
      Physical Location: U8205.E6D.211476V-V2-C91

For HMC command, What inputs in "Your_managed_System" "lpar_name=DEVVIOS2"
?

sorry a little puzzled

Last edited by jim mcnamara; 07-28-2015 at 12:47 PM..
# 9  
Old 07-28-2015
I don't know the name of your managed system. It is the IBM server, where all your LPARs reside. You can look which managed systems you have using the command lssyscfg -r sys -F name
# 10  
Old 07-28-2015
Quote:
Originally Posted by agent.kgb
I don't know the name of your managed system. It is the IBM server, where all your LPARs reside. You can look which managed systems you have using the command lssyscfg -r sys -F name
I am unable to find the IP to hmc...

Is there a way of using chdev -l vscsi1 ..... command to make defined state avaiable?

what would this command look like?
# 11  
Old 07-28-2015
the command you want is mkdev -l vscsi1 - this was the first command you executed and it didn't help. So you have some problem in your configuration and still have to find it.
This User Gave Thanks to agent.kgb For This Post:
# 12  
Old 07-28-2015
This User Gave Thanks to dukessd For This Post:
# 13  
Old 09-10-2015
Sorry been very busy with work, I forgot to update everyone but I got this worked out! thanks again everyone! you all are very helpful. Smilie
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Unable to install client AIX LPAR to vscsi hdisk provided from VIOS

Hi everybody, I have Power5 server with 4 internal hdisks each of 70Gb. VIOS server was installed via Virtual I/O Server Image Repository on the HMC. HMC release - 7.7.0 VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies

2. AIX

Devices.vscsi.disk ?

Hello, When I assigned CDROM from IVM (VIOS) to LPAR and then running cfgmgr i get the following message on the client lpar #cfgmgr cfgmgr: 0514-621 WARNING: The following device packages are required for device support but are not currently installed. devices.vscsi.disk searching... (0 Replies)
Discussion started by: filosophizer
0 Replies

3. AIX

Open firmware state to running state

Hi Admins, I am having a whole system lpar in open firmware state on HMC. How can I bring it to running state ? Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies

4. AIX

Kdb - vscsi disk mapping from AIX 5.3 CLIENT side

If you're familiar with vscsi mappings thru a VIO Server, you are probably aware, on an AIX 6.1 Client LPAR, that: print cvai | kdbcan provide useful information to you.... like VIO Server name & vhost #. But, "cvai" does not appear to be part of the Kernel Debugger in AIX 5.3. My question is... (3 Replies)
Discussion started by: The Doctor
3 Replies

5. AIX

hdisk mapping to a vSCSi Adapter

Hello, I have a VIOS System and would like to do mapping some hdisks, hdisk160 until hdisk165 to a vSCSi Adapter. I try to do this in the oem_setup_env like the following: for i in $(lspv | grep hdisk* | awk {'print $1'}; do mkdev -V $i -p vhost20 done There where a mapping with... (4 Replies)
Discussion started by: torsten163
4 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

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

8. Solaris

Zone in down state.

One of my zone is stuck in down state, not able to boot it or halt it .. not even detach .. is there any way to recover without rebooting the whole system ( global zone ) ? (3 Replies)
Discussion started by: fugitive
3 Replies

9. UNIX for Advanced & Expert Users

TIME_WAIT state

in TCP, is TIME_WAIT state really essential..!!! (3 Replies)
Discussion started by: sasikanth
3 Replies
Login or Register to Ask a Question