How to differentiate between a standalone LPAR and a VIOC (which again is a lpar)? Post: 302949916

Sponsored Content

Operating Systems AIX How to differentiate between a standalone LPAR and a VIOC (which again is a lpar)? Post 302949916 by blackrageous on Friday 17th of July 2015 01:33:56 PM

07-17-2015

Registered User

I have never heard the term standalone LPAR. The very name Logical Paritition means it is not a physical contruct. An IBM stand alone server is a physical entity that cannot be partitioned (these are usually older models, current models with appropriate licensing support virtualization). Perhaps you mean the case where an IBM server that supports partitioning has only 1 LPAR that has all they physical resources. A VIOS (virtual IO server) is a custom LPAR that can be used to give other LPARS virtual resources. The VIOS is assigned the physical resources of the IBM server (like a physical adapter) and then the VIOS can create a virtual adapter (like vSCSI) and map it to a client LPAR.

The "real magic" in Virtual Based systems is what is know as the hypervisor. IBM servers support PHYP and OpenKVM (for linux OpenPower). The hypervisor is a layer between physical resources of a server and the logical partitons (LPARS).

---------- Post updated at 12:33 ---------- Previous update was at 12:27 ----------

about the prtconf command:, a physical system would return "-1 NULL"

-L
Displays LPAR partition number and partition name if this is an LPAR partition, otherwise returns
"-1 NULL".

blackrageous

View Public Profile for blackrageous

Find all posts by blackrageous

10 More Discussions You Might Find Interesting

1. AIX

LPAR and CFGMGR

I have a P570 that for some reason is not allowing the P1-T6 NIC to be recognized. I have confirmed from the HMC that it is set for the LPAR, but when I do a cfgmgr, it won't recognize it. It though is recognizing the slot cards just fine which are P1-C3 for one shelf and P1-C3 of another shelf....

2. AIX

Autostart of LPAR

Hi, I have 2 lpars on my AIX that needs to be started manually after each reboot. Because the servers are storing the NFS and NIS info, other servers won't run correctly until they start up. I found in IBM documentation the steps to make it automatic. My question is, I want to know if...

3. AIX

LPAR

I am planning for System P with 2 number of 2-core processor (4 core in total). Can I make 3 LPARS with this processor configuration without the support of micropartitioning, that means with simple LPAR only.

4. AIX

ldom and lpar

hi, Plz let me know if the concept of sun ldom and aix lpar is same or not. thnx, snj

5. AIX

LPAR creation

can i get a step b syep explanation in creating LPAR... i have searched for tutorials i couldn't find the right one....

6. AIX

Bootting up a new LPAR

I have created a new LPAR using IVM. I activated the LPAR, and start the window terminal (java), it prompt me for the padmin password. After keyin the password, it will shows BOOTP parameter. I am just wondering how come it didnt go to screen where i can select to go into SMS menu to pick...

7. AIX

LPAR freezes after switching of storage (lpar is mirrored)

Hi all, I have the following configuration 2 ds3524 storage disk systems located over 2 locations 2 P720 server located over 2 locations DS3524 are connected to san switch. Each vio server has 1 fc adapter attached to a san switch. per p720 server 2 virtual io servers. Vio 1 has 1 lun...

8. AIX

Mirroring in LPAR

Hi Folks, I am a newbie in AIX. Can someone please tell me how to do root mirroring in AIX LPAR which is created from mksysb image via HMC/NIM. ? AIX 5.3/6.1 Let me know. Thanks in advance

9. AIX

Hostname for each lpar

Hi Gurus, Can a AIX server with 4 LPARs, each having it's own hostname on the same physical host. Is this possible? Thanks, S

10. AIX

Lpar migration

We have a 2 node oracle rac cluster one node is in frame 1 and other is in frame 2 Now,because of some hardware failure(processor card and cable) in frame 1 we will failover database services from lpar in frame 1 to lpar(oracle rac cluster node2) in frame2 and the entire replacement of hardware...

LEARN ABOUT SUSE

ipsec_tncfg

IPSEC_TNCFG(8)                                                    [FIXME: manual]                                                   IPSEC_TNCFG(8)

NAME

       ipsec_tncfg - manipulate KLIPS virtual interfaces

SYNOPSIS

       ipsec tncfg
             ipsec tncfg --create virtual
             ipsec tncfg --delete virtual
             ipsec tncfg --attach --virtual virtual --physical physical
             ipsec tncfg --detach --virtual virtual
             ipsec tncfg --clear
             ipsec tncfg --version
             ipsec tncfg --help

OBSOLETE

       Note that tncfg is only supported on the classic KLIPS stack. It is not supported on any other stack and will be completely removed in
       future versions. A replacement command still needs to be designed

DESCRIPTION

       The historical use of tncfg is to attach/detach IPsec virtual interfaces (e.g. ipsec0) to/from physical interfaces (e.g. eth0) through
       which packets will be forwarded once processed by KLIPS.

       The modern use of tncfg is to create and delete virtual interfaces known as mastXXX. mast stands for Mooring and XXX.

       The form with no additional arguments lists the contents of /proc/net/ipsec_tncfg. The format of /proc/net/ipsec_tncfg is discussed in
       ipsec_tncfg(5).

       The --attach form attaches the virtual interface to the physical one.

       The --detach form detaches the virtual interface from whichever physical interface it is attached to.

       The --clear form clears all the virtual interfaces from whichever physical interfaces they were attached to.

       Virtual interfaces typically have names like ipsec0 or mast0 while physical interfaces typically have names like eth0 or ppp0.

EXAMPLES

       ipsec tncfg --create mast12
           creates the mast12 device.

       ipsec tncfg --create ipsec4
           creates an ipsec4 device, but does not attach it.

       ipsec tncfg --attach --virtual ipsec0 --physical eth0
           attaches the ipsec0 virtual device to the eth0 physical device.

FILES

       /proc/net/ipsec_tncfg, /usr/local/bin/ipsec

SEE ALSO

       ipsec(8), ipsec_manual(8), ipsec_eroute(8), ipsec_spi(8), ipsec_spigrp(8), ipsec_klipsdebug(8), ipsec_tncfg(5)

HISTORY

       Written for the Linux FreeS/WAN project <http://www.freeswan.org/> by Richard Guy Briggs.

[FIXME: source]                                                     10/06/2010                                                      IPSEC_TNCFG(8)

10 More Discussions You Might Find Interesting

1. AIX

LPAR and CFGMGR

Discussion started by: LegendMan

2. AIX

Autostart of LPAR

Discussion started by: rahzzbietel

3. AIX

LPAR

Discussion started by: pchangba

4. AIX

ldom and lpar

Discussion started by: snjksh