Hello Friends,
My question/problem is that I noticed 2 servers in my environment vscsi is showing up as defined (not available) or is defined and not showing the path to both vscsi's when ruining lspath command. I am new to AIX admin, work alone, and work in an small environment. My question is, is it a need to make available? I know every LPAR should have redundancy, this is not urgent as this may of been like this since I started with this company a month ago, but i would like to understand this process/commands and how this could of happened. any help is greatly appreciated.
Please let me know if any other information maybe needed to support me on this.
Thanks in advanced fellow friends.
all other LPARs have the below output..
code:
#:/>lspath
Enabled hdisk0 vscsi0
Enabled hdisk1 vscsi0
Enabled hdisk0 vscsi1
Enabled hdisk1 vscsi1
#:/>lsdev -Cc adapter
ent0 Available Virtual I/O Ethernet Adapter (l-lan)
pkcs11 Available ACF/PKCS#11 Device
vsa0 Available LPAR Virtual Serial Adapter
vscsi0 Available Virtual SCSI Client Adapter
vscsi1 Available Virtual SCSI Client Adapter
The two LPARs that my question is for is showing me both different output:
server 4
code:
#:/>lspath
Enabled hdisk0 vscsi0
Enabled hdisk1 vscsi0
#:/>lsdev -Cc adapter
ent0 Available Virtual I/O Ethernet Adapter (l-lan)
pkcs11 Available ACF/PKCS#11 Device
vsa0 Available LPAR Virtual Serial Adapter
vscsi0 Available Virtual SCSI Client Adapter
vscsi1 Defined Virtual SCSI Client Adapter
server 5
code:
#:/>lspath
Enabled hdisk0 vscsi0
Enabled hdisk1 vscsi0
code:
#:/>lsdev -Cc adapter
ent0 Available Virtual I/O Ethernet Adapter (l-lan)
pkcs11 Available ACF/PKCS#11 Device
vsa0 Available LPAR Virtual Serial Adapter
vscsi0 Available Virtual SCSI Client Adapter
vscsi1 Available Virtual SCSI Client Adapter
What happens if you execute mkdev -l vscsi1
?
1 Like
Do I have to make vscsi1? it looks as if its already made. no?
also should I try these commands in LPAR or vio servers?
agent.kgb:
on server4.
It gives me this error message
code:
#:/>mkdev -l vscsi1
Method error (/usr/lib/methods/cfg_vclient):
0514-040 Error initializing a device into the kernel.
There can be at least 3 possible problems:
you didn't connect client VSCSI device to a server VSCSI device.
you connected client VSCSI device to wrong server VSCSI device.
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:
lscfg -l vscsi1
On VIOS side:
lsdev -dev vhost* -vpd
On HMC side:
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
1 Like
You seem to lack a solid understanding how all the virtualisation works:
First you create a virtual SCSI adapter on the VIOS and allow a certain LPAR to use it. For the LPAR it is used like any physical SCSI adapter, save for the fact that it is just a software construct in the VIOS. You do this on the HMC (see here ), then run cfgdev
on the VIOS.
Next you create (virtual) SCSI-devices on the VIOS: see the command "mkvdev" on the VIOS for creating such devices. You create such a device by assigning a "backing device" (some disk space the VIOS can control) and connect it to a virtual SCSI adapter.
For instance:
mkvdev -vdev hdisk10 -dev vtdisk_lpar5 -vadapter vhost5
This means: take "hdisk10" on the VIOS and use it(s disk space) to create a virtual disk "vtdisk_lpar5", which is connected to a virtual SCSI adapter named "vhost5". If "vhost5" is connected to the "lpar 5" you can run the cfgmgr
command there and the newly connected disk would appear.
I hope this helps.
bakunin
agent.kgb:
There can be at least 3 possible problems:
you didn't connect client VSCSI device to a server VSCSI device.
you connected client VSCSI device to wrong server VSCSI device.
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:
lscfg -l vscsi1
On VIOS side:
lsdev -dev vhost* -vpd
On HMC side:
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
$ 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
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?
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.
1 Like
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.