03-07-2012
Sorry, your English is so bad and obviously your understanding of AIX / VIOS / IVM is also so poor, we cannot understand what you are asking.
Please go and read the associated redbooks, or ask your business partner for help, and then ask if you still have problems.
10 More Discussions You Might Find Interesting
1. AIX
When using PowerVM Express and IVM (no HMC) on a Power6 P520 , can I configure 2 LPARs in addition to a VIO server, or does the VIO Server count as one of the two LPAR's that PowerVM Express allows? (1 Reply)
Discussion started by: JodyTek
1 Replies
2. AIX
Hi all please give me a link for IBM PowerVM (4 Replies)
Discussion started by: babinlonston
4 Replies
3. AIX
Hi,
When I try to login on my vios ivm website http://vios through the browser -- all three of them -- firefox , chrome , Internet Explorer , i get this error
http://vioserver/j_security_check
I have java installed on the machine from where i am trying to open up the IVM/VIOS webpage.
I... (2 Replies)
Discussion started by: filosophizer
2 Replies
4. AIX
I am facing problems in moving CD-ROM from one lpar to another.
CDROM can be seen on the POWERVM (IVM) server , but through the web-access if I move it ( assign it ) to LPAR it will be assigned. I run cfgmgr , and the cdrom does not show up in the LPAR. I firmly believe this is the reason why I... (2 Replies)
Discussion started by: filosophizer
2 Replies
5. AIX
Hi experts. I want to setup a training lab.
I have a Power 5 standalone server 9110-51A (p5 510)
I want to enable PowerVM on it and create two LPARs
I don't have money for an HMC
I know I can use IVM instead
I understand IVM is part of the VIOS software
TWO QUESTIONS:
1- If... (12 Replies)
Discussion started by: livehho
12 Replies
6. AIX
Some simple questions about Intellistation 285 and powervm.
I want to learn AIX,so i will buy an used I285 from ebay.
1)Will support aix 7.1?
2)Is powervm avaliable?Where to download or buy it?
Thanks (3 Replies)
Discussion started by: Linusolaradm1
3 Replies
7. AIX
Hi,
I'm a newbie to PowerVM and LPARs ( I work with VmWare and Oracle VM Server for Sparc) .recently we purchased an 8202-e4b server, with two enclosures for add'l disk capacity. it is licensed for PowerVM standard,came preloaded as such, AIX 7.1.
I've set up HMC v8.2, and run it through a VM on... (30 Replies)
Discussion started by: computron
30 Replies
8. AIX
Hello,
POWER7 machine.
4 x 1Gbit port ethernet adapter is dedicated to vios. 8023ad etherchannel is created using those 4 ports. Etherchannel adapter is shared to lpars using SEA.
If I test network performance directly from vios partition (using iperf) I'm geting nice 4Gbit throughput. But if... (3 Replies)
Discussion started by: vilius
3 Replies
9. AIX
coming from this thread: https://www.unix.com/aix/211107-ibm-power-pseries-open-firmware-boot-vios-powervm-vet-code.html
PowerVM, formerly known as Advanced Power Virtualization (APV), is a chargeable feature of IBM POWER5, POWER6, POWER7, POWER8, and POWER9 servers and is required for support... (0 Replies)
Discussion started by: filosophizer
0 Replies
10. AIX
Hello,
After installing on P6 which is POWERVM IVM VIOS enabled (VET CODE D21C77ACD9229817CA1F00002C10004164 )
i get this message
"I/O hosting requires a hosting partition - boot not permitted".
HMC was connected to the machine
then HMC was removed through ASMI
Searching on... (2 Replies)
Discussion started by: filosophizer
2 Replies
BAD144(8) System Manager's Manual BAD144(8)
NAME
bad144 - read/write DEC standard 144 bad sector information
SYNOPSIS
bad144 disktype disk [ sno [ bad ... ] ]
DESCRIPTION
Bad144 can be used to inspect the information stored on a disk that is used by the disk drivers to implement bad sector forwarding. The
format of the information is specified by DEC standard 144, as follows.
The bad sector information is located in the first 5 even numbered sectors of the last track of the disk pack. There are five identical
copies of the information, described by the dkbad structure. Only the first of these copies is used.
Replacement sectors are allocated starting with the first sector before the bad sector information and working backwards towards the begin-
ning of the disk. A maximum of 126 bad sectors can be supported. The position of the bad sector in the bad sector table determines which
replacement sector it corresponds to.
The bad sector information and replacement sectors are conventionally only accessible through the ``h'' file system partition of the disk.
If that partition is used for a file system, the user is responsible for making sure that it does not overlap the bad sector information or
any replacement sectors.
The bad sector structure is as follows:
struct dkbad {
long bt_csn; /* cartridge serial number */
u_short bt_mbz; /* unused; should be 0 */
u_short bt_flag; /* -1 => alignment cartridge */
struct bt_bad {
u_short bt_cyl; /* cylinder number of bad sector */
u_short bt_trksec; /* track and sector number */
} bt_bad[MAXBAD];
};
Unused slots in the bt_bad array are filled with all bits set, a putatively illegal value. MAXBAD (in <sys/dkbad.h>) may be tuned locally
to reduce the space required to hold the bad-sector file in memory. It may not be greater than 126, which uses the whole disk sector. Bad
sectors past MAXBAD may be included by the formatter, but replacement sectors will not be used until MAXBAD is increased.
Bad144 is invoked by giving a device type (e.g. rk07, rm03, rm05, etc.), and a device name (e.g. hk0, hp1, etc.). It reads the first sec-
tor of the last track of the corresponding disk and prints out the bad sector information. It may also be invoked giving a serial number
for the pack and a list of bad sectors, and will then write the supplied information onto the same location. Note, however, that bad144
does not arrange for the specified sectors to be marked bad in this case. This option should only be used to restore known bad sector
information which was destroyed.
New bad sectors can be added by running the standard DEC formatter in section ``bad.''
SEE ALSO
badsect(8)
BUGS
Not all drivers support bad-sector forwarding on the PDP-11.
It should be possible to both format disks on-line under UNIX and to change the bad sector information, marking new bad sectors, without
running a standalone program.
The bootstrap drivers used to boot the system do not understand bad sectors or handle ECC errors. This means that none of these errors can
occur when reading the file /unix to boot. Sector 0 of the disk drive and the file /boot in the root file system of that drive must also
not have any of these errors in it.
The drivers that write a system core image on disk after a crash do not handle errors; thus the crash dump area must be free of errors and
bad sectors.
3rd Berkeley Distribution BAD144(8)