03-27-2012
Hi,
VIO and HA are completely different concepts. With VIO server hardware resources are shared. If you have single Blade server and you want to have multiple client partitions then you can have VIO. Dual VIO can eliminate the downtime for hardware failure,as you client partition can be accessible from both vio.
Now if you have complete server hardware failure for i.e. servers planner goes faulty then your both the vio will be down with you client partition also. In this scenario if you have HACMP configured then your database will be up from another hardware. For HA you need tow physical servers or lpars from different physical servers or CEC's. Then you have to configure HACMP so that if one server is down your database with your ip address will be moved to another node configured in HACMP.
Hope this resolves your query.
Regards,
VJM
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
LEARN ABOUT OSF1
nissetup
nissetup(8) System Manager's Manual nissetup(8)
NAME
nissetup, ypsetup - Sets up the Network Information Service (NIS) environment
SYNOPSIS
/usr/sbin/nissetup
/usr/sbin/ypsetup
DESCRIPTION
The nissetup (formerly ypsetup) script configures and runs NIS on your system. You can use nissetup to initially set up your NIS configura-
tion, to change your current NIS configuration, or to remove your NIS configuration. NIS provides a distributed data lookup service for
sharing data among networked systems.
Before running nissetup, make sure that your system is connected to a local area network and that the network is configured and running.
You must know the name of your NIS domain and your system's role in the domain (master server, slave server, or client).
Security Note
You invoke nissetup from the SysMan Menu. See sysman(8) for more information.
When using the nissetup script to set up a NIS server that is running with enhanced security, you must answer yes to the question about
locking the domain name and authorized servers (the ypbind -S option). If you are setting up a master server, the server is bound to itself
(done by default). If you are setting up a slave server, the server is bound to itself done by default) and optionally to the master server
and any other slave servers.
If your system will be the master server for your NIS domain, be sure no other master exists for your domain and that the NIS database
files are in the /var/yp/src directory.
Note
Remove the root entry, if it exists, from the passwd database file.
If your system be will be a slave server or client, be sure a master server is already set up for your NIS domain.
FILES
Specifies the command pathname NIS parameters pertinent to a specific system
Default NIS Databases
In the /var/yp/src directory, the default databases are: Group database Host database Sendmail alias database Network group aliases data-
base Network database Password database Protocol database RPC database Service database
SEE ALSO
Commands: domainname(1), ypwhich(1), svcsetup(8), sysman(8), sysman_station(8), ypbind(8), yppasswdd(8), ypserv(8), ypxfr(8)
Files: svc.conf(4)
Networking: nis_intro(7), nis_manual_setup(7)
Network Administration
nissetup(8)