03-24-2012
PowerHA Disk on VIO Server
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 create enhanced concurent Vg in LPAR
10 More Discussions You Might Find Interesting
1. AIX
Hi,
I define 2 new LV on the vio server and run a cfgmgr on the partition and see my 2 new hdisk (hdisk6 and hdisk7).
I extend my vg vg000 (on the partition) and add the 2 hdisks.
I had a filesystem on the vg000 and when I added the disk I would like to increase the filesystem. But I cannot do a... (0 Replies)
Discussion started by: touny
0 Replies
2. AIX
We have a frame the uses 2 vios that assign disk storage to LPAR's. We have a LPAr with multiple disk and I want to know how do I tell which vio is serving the disk. For example the LPAr has hdisk 0, 1, 2, 3 all the same size. I want to know which vio is serving hdisk0, 1. (4 Replies)
Discussion started by: daveisme
4 Replies
3. 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
4. AIX
hello Folks,
my vio:
$ lsmap -all
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost0 U9117.MMA.6534BE4-V2-C11 0x00000003
VTD ... (0 Replies)
Discussion started by: filosophizer
0 Replies
5. AIX
VIO Server is managing both AIX Clients and Linux Clients. For AIX Clients, we could do a disk mapping from slot numbers to VIO and also uname -L to determine the lparid and serial number frame its running on.
From a Linux Client,
How do I know which IBM frame its running on? Any command to... (4 Replies)
Discussion started by: rpangulu
4 Replies
6. AIX
Hi
I need to do the migratepv for the rootvg disks of the vio servers ? The current rootvg disks are on DMX3 storage and the new disks will be given from VMAX. Our setup is dual vio servers with multipathing to the vio clients.
What is the command to do the migratepv for the vio rootvg disks... (5 Replies)
Discussion started by: newtoaixos
5 Replies
7. 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
8. 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
9. AIX
:wall::wall::wall:
1. I have created an LPAR in the HMC.
2. I have allocated the storage from an Hitachi AMS2500 and assigned it to the host group.
3. I have zoned the LPAR and Storage on a Brocade 5100. (The zone sees the AMS)
Next I activated the LPAR in the HMC, SMS mode for the mksysb... (3 Replies)
Discussion started by: Dallasguy7
3 Replies
10. 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
core(4) Kernel Interfaces Manual core(4)
NAME
core - Format of memory image file
SYNOPSIS
#include <sys/core.h>
DESCRIPTION
The system writes out a memory image of a terminated process when any of various errors occur. See sigaction(2) for the list of reasons;
the most common are memory violations, illegal instructions, bus errors, and user-generated quit signals. The memory image is called core
and is written in the process's working directory (provided that it can be; normal access controls apply).
The maximum size of a core file is limited. If a process exceeds this limit, any remaining data to be written to the core file is lost.
Default behavior is for the system to create a file named core, overwriting any other file with that name in the working directory.
You can enable enhanced core file naming, which causes the system to create unique names for core files. Core files are not overwritten,
thereby preventing loss of valuable debugging information when the same program fails mulitiple times (and perhaps for mulitple reasons).
When enhanced core file naming is enabled, the system produces core files with names in the following format:
core.program_name.host_name.numeric_tag The literal string core. Up to sixteen characters taken from the program name as shown by the ps
command. The first portion of the system's network host name, or up to 16 characters of the host name, taken from the part of the host
name that precedes the first dot. This tag is assigned to the core file to make it unique among all of the core files generated by a pro-
gram on a host. The maximum value for this tag, and thus the maximum number of core files for this program and host, is set by a system
configuration parameter.
Note the tag is not a literal version number. The system selects the first available unique tag for the core file. For example, if a
program's core files have tags .0, .1, and .3, the system uses tag .2 for the next core file it creates for that program. If the
system-configured limit for core file instances is reached, the system will not create any more core files for that program/host
combination. By default, the system can create up to 16 versions of a core file.
For example, the fourth core file generated on host buggy.net.ooze.com by the program dropsy would be: core.dropsy.buggy.3
Enhanced core file naming can be enabled at the system level or the program level: At the system level, you can enable enhanced core file
naming by setting the enhanced-core-name system configuration variable to 1 in the proc subsystem: proc:
enhanced-core-name = 1 At the program level, you can enable enhanced core file naming by calling the uswitch system call with the
USW_CORE flag set. See the EXAMPLE section.
The system manager can limit the number of unique core file versions that a program can create on a specific host system by setting the
system configuration variable enhanced-core-max-versions to the desired value: proc:
enhanced-core-name = 1
enhanced-core-max-versions = 8 The miminum value is 1, the maximum is 99,999, and the default is 16.
EXAMPLE
The following example shows a code fragment that calls the uswitch system call with the USW_CORE flag set: #include <signal.h> #include
<sys/uswitch.h>
/*
* Request enhanced core file naming for
* this process then create a core file.
*/ main() {
long uval = uswitch(USC_GET, 0);
uval = uswitch(USC_SET, uval | USW_CORE);
if (uval < 0) {
perror("uswitch");
exit(1);
}
raise(SIGQUIT); }
In general, the debugger dbx(1) is sufficient to deal with core images.
RELATED INFORMATION
sigaction(2), uswitch(2), sysconfigdb(8), dbx(1) delim off
core(4)