lp-hea are the native adapters attached to the Balde itself (they are HEA, and each HEA has 4 Logical ports). We use them, say for the first installation or for servers where you don't want redundancy, they are SPOF (single point of failure) adapters.
Virtual adapters (l-lan), are created at VIOS/client level, we create them at VIO level to define the priority of VIOS and add multiple vlans to it. At client level we create those for it to communicate to outer world.
Physical cable are the actual cables from which the traffic goes in and out of the Blade, without the physical port your virtual adapter at VIO are of no use.
Now coming to SEA (shared ethernet adapter), to create a SEA you need a physical adapter, a virtual adapter (actually two, one with trunking priority, vlans (if you want) and other is called control channel adapter, ctrl chan adapter is the heart beat of SEA). Then the VIO create a new adapter called SEA, remember that SEA will not be visible from HMC, you can only see it when you are in VIO.
If you have SEA, it will be redundant and you can avoid SPOF.
thanks a lot
so for what I understood I have to use these to create SEA
is it too much to ask who to do it? is by command or using smitty
Hello,
When I try to upgrade AIX from 5.1 to 5.3 I get this error message
20EE0008 : No adapters found Adapter, Riser, System Bd.
Anyone know anything about it ? (1 Reply)
Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Hi
I have 4 NIC's connected to my RHEL 5.3 server. Two on one subnet creating bond0, and two on a second subnet which create bond1. Both bonds are set to use DHCP to obtain IP addresses. Here is the config file for ifcfg-bond0:
DHCP_HOSTNAME=rrnltshckvmx001
DEVICE=bond0
BOOTPROTO=dhcp... (2 Replies)
Hi all,
I set up the following configuration on my system:
- An LPar with a virtual adapter, first one with a vlan id=703 and id port=13.
- The first adapter have to connect to a VIOS in which i configured an SEA.
So, the VA is set up on interface ent2, SEA on ent29 (by linking a... (0 Replies)
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
I am trying to get my boss' ipad to print on our local printers, and rapidly coming to loathe the product.
After several false starts I'm attempting to use the free WePrint application, running on a Windows machine, to "forward" our printers from it to the ipad over the local network. I've hit... (2 Replies)
Hi guys,
I've been trying to tackle this issue for days and I'm stumped. Hopefully someone can give more light on what else I can do.
I have a p7 series box, with dual VIOS and 10 lpars and everything was working fine until I had to move the box to another location in the data centre. Ensured... (16 Replies)
Discussion started by: aixkidbee
16 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)