10 More Discussions You Might Find Interesting
1. AIX
I have a broken PV in a VIO VG that's used to support client LPARs using LVs. On the client LPAR, I reduced all PVs from the relevant client VG and thus deleted it. I.e. there is no client LPAR using the VIO VG. Yet when I try to reducevg the VIO VG, it complains that the LV hosted on the PV is... (2 Replies)
Discussion started by: maraixadm
2 Replies
2. AIX
I know the VIOs are generally to be treated as an appliance and one should never drop down to oem_setup_env. In reality however, oem is a very useful tool to get the job done. So that leads me into the question of using the Chef client on a VIO.
Currently a big push to manage all our *nix... (4 Replies)
Discussion started by: RecoveryOne
4 Replies
3. Linux
Hi,
Could you please help me with the below issue..
I'm running RHEL6 OS on both server (192.168.0.10) and client machines (192.168.0.1).
I'm trying to connect to server from the client machine using ftp service.
I have installed vsftpd daemon on both the machines.
I'm getting... (4 Replies)
Discussion started by: raosr020
4 Replies
4. AIX
Hi
In my vio server I have the below output
$ lsvopt | grep -i SAPSITGS
sapsitgs_cdrom TL12UP.iso 3182
In my vio client lpar I have the below output
root@sapsitgs:/ # lsdev -Cc cdromcd0 Available Virtual SCSI Optical Served by VIO Server
cd1... (1 Reply)
Discussion started by: newtoaixos
1 Replies
5. AIX
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)
Discussion started by: newtoaixos
1 Replies
6. AIX
Hi
im logged in to the vio servers now.
when i give
# lspv | wc -l
i get the count as 6246
how will i know if a lun has been already mapped to a vio client or it is left free without mapping to any of the vio client ? (1 Reply)
Discussion started by: newtoaixos
1 Replies
7. AIX
Just a question which may seem dumb to some out there, but then again I am not a super technie so that's my excuse.
Is it possible to say provision a test AIX LPAR (has a 10gb boot lun and 20gb data) under a VIO which has connectivity to SAN Array A so it can see the disks provisioned to it,... (2 Replies)
Discussion started by: Johnny1314
2 Replies
8. AIX
Hi,
I am having single p series blade with Single Physcial CPU with dual core,
on that vio server is installed, I have created vio client allocate 0.9 each cpu , now when I am running prtconf command on vio client it is showing "2" no of processor,
My query using which command it will... (1 Reply)
Discussion started by: manoj.solaris
1 Replies
9. AIX
Hi,
I would like to reboot vio client but I am not able to access vio client(I am not able to get putty) , I am able to get putty of vio server,
is there any command by using which from vio server I can reboot vio client? (3 Replies)
Discussion started by: manoj.solaris
3 Replies
10. AIX
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)
Discussion started by: manoj.solaris
1 Replies
AUSCOPE(1) General Commands Manual AUSCOPE(1)
NAME
auscope - Network Audio System Protocol Filter
SYNOPSIS
auscope [ option ] ...
DESCRIPTION
auscope is an audio protocol filter that can be used to view the network packets being sent between an audio application and an audio
server.
auscope is written in Perl, so you must have Perl installed on your machine in order to run auscope. If your Perl executable is not
installed as /usr/local/bin/perl, you should modify the first line of the auscope script to reflect the Perl executable's location. Or,
you can invoke auscope as
perl auscope [ option ] ...
assuming the Perl executable is in your path.
To operate, auscope must know the port on which it should listen for audio clients, the name of the desktop machine on which the audio
server is running and the port to use to connect to the audio server. Both the output port (server) and input port (client) are automati-
cally biased by 8000. The output port defaults to 0 and the input port defaults to 1.
ARGUMENTS
-i<input-port>
Specify the port that auscope will use to take requests from clients.
-o<output-port>
Determines the port that auscope will use to connect to the audio server.
-h<audio server name>
Determines the desktop machine name that auscope will use to find the audio server.
-v<print-level>
Determines the level of printing which auscope will provide. The print-level can be 0 or 1. The larger numbers provide greater
output detail.
EXAMPLES
In the following example, mcxterm is the name of the desktop machine running the audio server, which is connected to the TCP/IP network
host tcphost. auscope uses the desktop machine with the -h command line option, will listen for client requests on port 8001 and connect
to the audio server on port 8000.
Ports (file descriptors) on the network host are used to read and write the audio protocol. The audio client auplay will connect to the
audio server via the TCP/IP network host tcphost and port 8001:
auscope -i1 -o0 -hmcxterm
auplay -audio tcp/tcphost:8001 dial.snd
In the following example, the auscope verbosity is increased to 1, and the audio client autool will connect to the audio server via the
network host tcphost, while displaying its graphical interface on another server labmcx:
auscope -i1 -o0 -hmcxterm -v1
autool -audio tcp/tcphost:8001 -display labmcx:0.0
SEE ALSO
nas(1), perl(1)
COPYRIGHT
Copyright 1994 Network Computing Devices, Inc.
AUTHOR
Greg Renda, Network Computing Devices, Inc.
1.9.3 AUSCOPE(1)
Unable to connect VIO client