Then using this information check that the storage is zoned to the Physical WWNs and the Virtual WWNs on both adapters.
I have learned that it is not recommendet to zone the physical WWN from the NPIV-adapter.
Code:
I was still not able to see it in my SAN switch during any of this process.
We ran into the same problem as we have begun to setup our new virtual systems.
After some hot discussions with our SAN/Storage Group, they create the zones/mappings with the WWPNs which we are giving to them without seeing the ports logged in.
But after activating (opening) the adapter in the SMS menu, you should be able to see (one of) the WWPN on your switch - may it take some time till the switch refresh the list of logged in ports.
Hello guys,
It would be so nice of you if someone can provide me with these informations.
1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Hello,
I have created mapping of 2 virtual adapters for Lpars using following command:
mkvdev -vdev ipanalyzerlv1 -vadapter vhost11
mkvdev -vdev ipanalyzerlv -vadapter vhost13
The above two commands were succesfull
but when I want to map the third virtual device to the same Lpar than... (3 Replies)
Is anyone here using NPIV with AIX? If you are, what type of switch are you connected to? Also, please share some impressions of NPIV over traditional port-to-port LUN assignments. We are looking to move to NPIV and need some convincing argume... I mean information. (2 Replies)
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)
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)
Hi, I would like to ask you if you could help me to answer these questions. Please.
How to check in vios, size all pv's and to what they are mapped to?
How to chech on vios/hmc which PowerVM edition is used?
Thank you. (7 Replies)
Hello all I hope someone can help me with this. I have a single LPAR which is supplied a rootvg and datavg disk set from a dual VIO server configuration. I see dual path disks for all the datavg disks but only see one path for the rootvg disks.
The client LPAR has the following:
fcs0 ... (3 Replies)
Hello,
I do not know if this is the right title to use. I have a large dictionary database which has the following structure:
where a b c d e are in English and p q r s t are in a target language., the two separated by the delimiter =.
What I am looking for is a perl script which will take... (5 Replies)
Hi All :)
i would like to know if i can customize the WWN of the new VFC (NPIV).
Or, if i must move the LPAR on another server with another FCS, i have to change the zoning??
Thanks in advance.
Mario
---------- Post updated 09-21-12 at 02:51 AM ---------- Previous update was 09-20-12 at... (1 Reply)
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies
LEARN ABOUT DEBIAN
roar_vs_file
roar_vs_file(3) RoarAudio Programmer's Manual roar_vs_file(3)NAME
roar_vs_file, roar_vs_file_simple, roar_vs_new_from_file - File mode for VS API
SYNOPSIS
#include <roaraudio.h>
int roar_vs_file(roar_vs_t * vss, struct roar_vio_calls * vio, int closefile, int * error);
int roar_vs_file_simple(roar_vs_t * vss, char * filename, int * error);
roar_vs_t * roar_vs_new_from_file(const char * server, const char * name, char * filename, int * error);
DESCRIPTION
These functions are used to open the VS object in file mode. In the file mode the VS API reads or writes the data from or to the file
itself. The file mode uses normal VIO/DSTR so it supports streams as well. Just pass the stream URL as filename.
roar_vs_file() sets up the file mode for a already opened object using the open VIO handle vio. This function requires the use of
roar_vs_stream(3).
roar_vs_file_simple() sets up the file mode using a given filename (or URL). It opens the file using DSTR API. By default the function
assumes playback mode and tries to auto detect the audio parameters. To override the auto detection or use a diffrent stream direction use
roar_vs_stream(3).
roar_vs_new_from_file() creates a new VS object and enters file mode using the file (or URL) given as filename.
To send data to or read data from use roar_vs_iterate(3) or roar_vs_run(3).
PARAMETERS
server The server to connect to. NULL for defaults.
name The application name. This should be something the user can use to identify the application. It MUST NOT be the application's
binary name or the value of argv[0].
vio The VIO handle to be used by the file mode.
closefile
This parameter tells the file mode if the file should be closed on roar_vio_close(3). Must be ROAR_VS_TRUE (common) or
ROAR_VS_FALSE.
filename
The filename used to open the file for file mode. The file is opend using DSTR API. All kinds of files supported by DSTR are sup-
ported. This includes HTTP streams.
error This is a pointer to a integer used to store the error value in case of error. This can be NULL if not used but it is very recom-
mended to use this error value to report good error messages to the user.
RETURN VALUE
On success roar_vs_new_from_file() return a new VS object. On error, NULL is returned. roar_vs_file() and roar_vs_file_simple() returns 0
on success and -1 on error.
EXAMPLES
roar_vs_t * vss;
int err;
vss = roar_vs_new_from_file(NULL, "MyApp", "http://...", &err);
if ( vss == NULL ) {
//handle error.
}
if ( roar_vs_run(vss, &err) == -1 ) {
//handle error.
}
if ( roar_vs_close(vss, ROAR_VS_FALSE, &err) == -1 ) {
//handle error.
}
SEE ALSO roar_vs_new_simple(3), roar_vs_iterate(3), roar_vs_run(3), roar_vs_close(3), roarvs(7), libroar(7), RoarAudio(7).
RoarAudio June 2011 roar_vs_file(3)