05-12-2009
Log in to your VIO Server
list all the disk in VIO Server
#lspv
you should see something like
hdisk0___________ PVID_ID_______volume_group_it_belongs_to
list it here ...
thanks
10 More Discussions You Might Find Interesting
1. 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
2. AIX
trying to put VIO server software into this p520, firmware upgraded to the latest and greatest..SF240_415_318 , I think
a few questions, on this practice AIX machine on AIX 7.1
VIO can only be installed if ASMI or HMC is running ???
if so, perhaps ASMI is much simpler, since I will need to... (2 Replies)
Discussion started by: ppchu99
2 Replies
3. 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
4. AIX
Hello AIX GURU's
Can anybody tell me the steps to crate shared VG (enhanced concurent) for my Lpars from VIO server?
my questions are:
1.
Should I crate Enhanced Concurent VG in VIO and map it using virtual Scsi to Lpar?
or
2. Can I just create virtual SCSI in VIO and map to Lpar and... (1 Reply)
Discussion started by: Vit0_Corleone
1 Replies
5. AIX
Hi,
I would like to know installing vio server on local disk and mirroring rootvg,
if I am creating AIX VIO CLIENT(lpar),
and any of single local hard disk failuare.
will it affect lpars? will lpars able to boot.
what needs to be done? (1 Reply)
Discussion started by: manoj.solaris
1 Replies
6. AIX
Hi,
I am facing an issue in vio server. When I run
bosboot -ad /dev/hdisk0
I am getting an error
trustchk: Verification of attributes failed: /usr/sbin/bootinfo
: accessauths
regards,
vjm
Please use code tags next time for your code and data. (8 Replies)
Discussion started by: vjm
8 Replies
7. AIX
Hi,
I would like to know after the installation of vio server. how many logical network interfaces will be created on vio server if I am having two physical interfaces on vio server.
I am asking this question because I would like know to on the basis of logical network interfaces creation on... (0 Replies)
Discussion started by: manoj.solaris
0 Replies
8. AIX
Want to run this by you all before opening a PMR with IBM Support.
It's been a few weeks since I have done this so I can't be 100% sure of how I think it worked in the previous version.
We upgraded our HMC's yesterday to 7.7.9 SP2 in hopes of fixing some issues we were having. Today I needed... (4 Replies)
Discussion started by: juredd1
4 Replies
9. AIX
Hi Experts, Kind of embarrassed to ask this , it's been a while I've done this . Can anyone verify below procedure to replace HBA in the VIO server. Many client LPARs are using this HBA for NPIV . Please correct me if I am wrong . Thanks in Advanced
Identify the HBA (did that)
Unconfigure the... (2 Replies)
Discussion started by: JME2015
2 Replies
10. UNIX for Advanced & Expert Users
Hello,
I would like to identify the blade or/and bladecenter from the hosted VIO server.
I prefer the "command line" solution. May be kdb.
Like, I want to ask the child about his father.
Thank you (1 Reply)
Discussion started by: x41
1 Replies
LEARN ABOUT OSX
net::server::log::sys::syslog
Net::Server::Log::Sys::Syslog(3) User Contributed Perl Documentation Net::Server::Log::Sys::Syslog(3)
NAME
Net::Server::Log::Sys::Syslog - log via Syslog
SYNOPSIS
use base qw(Net::Server::PreFork);
__PACKAGE__->run(
log_file => 'Sys::Syslog',
syslog_ident => 'myapp',
);
DESCRIPTION
This module provides Sys::Syslog logging to the Net::Server system.
CONFIGURATION
log_file
To begin using Sys::Syslog logging, simply set the Net::Server log_file configuration parameter to "Sys::Syslog".
If the magic name "Sys::Syslog" is used, all logging will take place via the Sys::Syslog module. If syslog is used the parameters
"syslog_logsock", "syslog_ident", and "syslog_logopt",and "syslog_facility" may also be defined.
syslog_logsock
Only available if "log_file" is equal to "Sys::Syslog". May be either unix, inet, native, console, stream, udp, or tcp, or an arrayref
of the types to try. Default is "unix" if the version of Sys::Syslog < 0.15 - otherwise the default is to not call setlogsock.
See Sys::Syslog.
syslog_ident
Only available if "log_file" is equal to "Sys::Syslog". Id to prepend on syslog entries. Default is "net_server". See Sys::Syslog.
syslog_logopt
Only available if "log_file" is equal to "Sys::Syslog". May be either zero or more of "pid","cons","ndelay","nowait". Default is
"pid". See Sys::Syslog.
syslog_facility
Only available if "log_file" is equal to "Sys::Syslog". See Sys::Syslog and syslog. Default is "daemon".
DEFAULT ARGUMENTS FOR Net::Server
The following arguments are available in the default "Net::Server" or "Net::Server::Single" modules. (Other personalities may use
additional parameters and may optionally not use parameters from the base class.)
Key Value Default
## syslog parameters (if log_file eq Sys::Syslog)
syslog_logsock (native|unix|inet|udp
|tcp|stream|console) unix (on Sys::Syslog < 0.15)
syslog_ident "identity" "net_server"
syslog_logopt (cons|ndelay|nowait|pid) pid
syslog_facility w+ daemon
METHODS
"initialize"
This method is called during the initilize_logging method of Net::Server. It returns a single code ref that will be stored under the
log_function property of the Net::Server object. That code ref takes log_level and message as arguments and calls the initialized
log4perl system.
"handle_log_error"
This method is called if the log_function fails for some reason. It is passed the Net::Server object, the error that occurred while
logging and an arrayref containing the log level and the message. In turn, this calls the legacy Net::Server::handle_syslog_error
method.
LICENCE
Distributed under the same terms as Net::Server
POD ERRORS
Hey! The above document had some coding errors, which are explained below:
Around line 104:
You forgot a '=back' before '=head1'
Around line 114:
'=item' outside of any '=over'
perl v5.16.2 2012-06-05 Net::Server::Log::Sys::Syslog(3)