Sponsored Content
Operating Systems AIX How to put vscsi in available state? Post 302950731 by agent.kgb on Tuesday 28th of July 2015 09:42:37 AM
Old 07-28-2015
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

This User Gave Thanks to agent.kgb For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

TIME_WAIT state

in TCP, is TIME_WAIT state really essential..!!! (3 Replies)
Discussion started by: sasikanth
3 Replies

2. 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

3. 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

4. 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

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

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

7. 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

8. 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

9. 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
oss_midiloop(7) 						    OSS Devices 						   oss_midiloop(7)

NAME
oss_midiloop - Loopback MIDI driver. DESCRIPTION
The loopback midi driver makes it possible to create special purpose virtual midi devices based on user land server processes. INTRODUCTION
MIDI loopback devices are like named pipes or pseudo terminals. They are grouped in client and server device pairs. The server side device must be open before the client side device can be opened. SERVER SIDE DEVICE The server side device is used by some special application (such as a software based MIDI synthesizer) to receice MIDI events from the applications that want to play MIDI. CLIENT SIDE DEVICE Client applications such as MIDI players open the client side device when they need to play some MIDI stream (file). The client side device behaves like any "ordinary" MIDI device. However it cannot be opened when there is no program connected to the server side. COMPATIBILITY ISSUES
MIDI loopback devices differ from "normal" MIDI devices because an application is needed at the both ends of the loop. The loop device will return a "Connection reset by peer" error (ECONNRESET) error. Applications designed to be used as loopback based server applications can/should use this error (returned by read or write) as an end-of-stream indication. OPTIONS
o midiloop_instances: Specifies how many loopback client/server MIDI device pairs to be created. Values: 1-16 Default: 1 KNOWN PROBLEMS
None FILES
/etc/oss4/conf/oss_midiloop.conf Device configuration file AUTHOR
4Front Technologies 16 December 2012 oss_midiloop(7)
All times are GMT -4. The time now is 08:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy