Date: 20-10-20  Time: 15:13 PM

Recent Posts

Pages: 1 ... 6 7 [8] 9 10
71
Virtualization / Re: number of VIOS for large virtualized server
« Last post by Michael on April 20, 2020, 05:55:48 PM »
Hello Michael and many thanks for your quick answer.
Yes we are planning to use LPM but not for frequent LPAR move: it is supposed to be used primarily for failover in case of hardware failure or maintenance of one of the two production E980, we will make use of PEP and most of the cores are mobile activation.

So what you were saying about LPM is that it is a common practice to keep some VIOS idle (no client attached) just to use them as MSP with a dedicated network access ?
Yes, (becoming) common practice - especially when LPM is frequent and/or FRAME evacuation must be as quick as possible. Generally with dedicated (non-user) network.
Remember: for a failover (crash of frame or site) - LPM is too late. For that you need to be LPM capable, but you would use SRR for the "movement" of the partitioin. SRR ensures that when the frame/site comes back on-line the "original" LPAR gets removed - no double activation by accident.
Quote
Regarding vNIC failover, as each backing device is statically bound to one VIOS and we will have at least 2 LAN switches, I plan to dedicate a set of 4 sr-iov ports for my critical LPARs and as I have 4 VLANs I think I will use one physical sr-iov port from 4 adapters to create logical ports for my 4 VLANs like this :

vNIC1/VLAN1 : main logical port on port1 of adapter1 managed by VIOS1 and backup on port1 of adapter2/VIOS2, port1 of adapter3/VIOS1 and port1 of adapter4/VIOS2

for other vNICs/VLANs I use the same set of physical ports to define the backing devices but with a rotation of main ports over the set of 4 physical ports : main backing device will be
vNIC2/VLAN2 => port1 of adapter2 / VIOS2
vNIC3/VLAN3 => port1 of adapter3 / VIOS1
vNIC4/VLAN4 => port1 of adapter4 / VIOS2

adapter1 is attached to LAN switch 1
adapter2 is attached to LAN switch 2
adapter3 is attached to LAN switch 1 (or switch 3)
adapter4 is attached to LAN switch 2 (or switch 4)
Sounds about right - but I prefer diagrams for networking.
Have you been to a recent POWER TechU - if so, there are some good presentations re: vNIC setups for performance and elimination of SPOF.
Quote

I am in charge for only some critical LPARs that need a highly redundant and performant architecture, but my customer will probably follow the same kind of architecture for other LPARs on the same servers.

Thank you also for your advice about POWER6 migration and also regarding software and firmware levels, I will give instructions so that we will have latest levels during the validation tests.

Best regards

Fabrice
Glad to be of assistance.
72
Virtualization / Re: number of VIOS for large virtualized server
« Last post by fplatel on April 20, 2020, 09:54:58 AM »
Hello Michael and many thanks for your quick answer.
Yes we are planning to use LPM but not for frequent LPAR move: it is supposed to be used primarily for failover in case of hardware failure or maintenance of one of the two production E980, we will make use of PEP and most of the cores are mobile activation.

So what you were saying about LPM is that it is a common practice to keep some VIOS idle (no client attached) just to use them as MSP with a dedicated network access ?

Regarding vNIC failover, as each backing device is statically bound to one VIOS and we will have at least 2 LAN switches, I plan to dedicate a set of 4 sr-iov ports for my critical LPARs and as I have 4 VLANs I think I will use one physical sr-iov port from 4 adapters to create logical ports for my 4 VLANs like this :

vNIC1/VLAN1 : main logical port on port1 of adapter1 managed by VIOS1 and backup on port1 of adapter2/VIOS2, port1 of adapter3/VIOS1 and port1 of adapter4/VIOS2

for other vNICs/VLANs I use the same set of physical ports to define the backing devices but with a rotation of main ports over the set of 4 physical ports : main backing device will be
vNIC2/VLAN2 => port1 of adapter2 / VIOS2
vNIC3/VLAN3 => port1 of adapter3 / VIOS1
vNIC4/VLAN4 => port1 of adapter4 / VIOS2

adapter1 is attached to LAN switch 1
adapter2 is attached to LAN switch 2
adapter3 is attached to LAN switch 1 (or switch 3)
adapter4 is attached to LAN switch 2 (or switch 4)

I am in charge for only some critical LPARs that need a highly redundant and performant architecture, but my customer will probably follow the same kind of architecture for other LPARs on the same servers.

Thank you also for your advice about POWER6 migration and also regarding software and firmware levels, I will give instructions so that we will have latest levels during the validation tests.

Best regards

Fabrice
73
Virtualization / Re: number of VIOS for large virtualized server
« Last post by Michael on April 15, 2020, 07:50:28 AM »
It is quite common to have more than one pair of VIOS servers - for various reasons. The reasons you mention are common ones.
If you are considering LPM - frequent LPM - a dedicated (pair) of MSP (Moving Service Partitions) with zero "client partitions". This ensures that the "application" networks are not (directly) affected by LPM.Note: even though MSP such as these are not hosting clients in the classic sense of SEA Failover - they could still be involved in a vNIC failover scheme.
Further, if you are considering using LPM to migrate partitions remember than the POWER6 ones will have to go down at least once: POWER9 only supports POWER9, POWER8 and POWER7 modes. An inactive (L)PM should be possible between POWER6 and POWER9.
And - in your position - I would try and plan AIX updates, if any, prior to the migrations. And, before any critical partitions are on the POWER9 - do any firmware updates, including a IPL (if there are any DEFERRED updates).
Lastly, do not forget to examine PEP (Power Enterprise Pools) and SRR (Simplified Remote Restart).
Enjoy - sounds like you get to build/architect  something to be proud of!
Michael
74
Virtualization / number of VIOS for large virtualized server
« Last post by fplatel on April 14, 2020, 09:05:50 AM »
Hello
One of my customers is about to acquire three E980 POWER9  servers with a lot of cores (168 cores activated in total) and memory (more than 4TB of RAM in total). Two servers will be on production site plus one on DR site.
They want to consolidate several LPARs from various P6/P7/P8 servers, I cant remember how much exactly but it will be probably dozens.
Network virtualization will be mostly via vNIC with SR-IOV 10Gbps adapters , and storage access via NPIV over 32Gb FC adapters.

As I plan to implement vNIC failover with a highly redundant architecture especially for some critical LPARs, I am wondering if it is a good practice to use more than 2 VIOS per physical machine, and I am thinking about dedicating a pair of VIOS for critical LPARs while other LPARs will use another pair of VIOS. Or is it better to use only two VIOS for all LPARs with more entitled processor per VIOS?
My concern is to ensure that the critical LPARs will have constant performance so that's why I want to have dedicated access to virtualized ressources.

Thanks in advance for sharing advices.
Best regards
Fabrice

75
AIXTOOLS / Re: I´ve installed python 3.8 but isn´t work
« Last post by Michael on April 14, 2020, 06:40:28 AM »
Your welcome!
76
AIXTOOLS / Re: I´ve installed python 3.8 but isn´t work
« Last post by Javier Umanzor on April 13, 2020, 01:07:12 PM »
Thank You, it's worked.
77
AIXTOOLS / Re: I´ve installed python 3.8 but isn´t work
« Last post by Michael on April 13, 2020, 11:22:08 AM »
Add /opt/bin to your PATH.
FYI: to see what files are in a package try something such as:
 $ lslpp -f aixtools.python.py38.rte
78
AIXTOOLS / I´ve installed python 3.8 but isn´t work
« Last post by Javier Umanzor on April 10, 2020, 05:44:38 PM »
Hello, today I´ve installed python 3.8.3 on AIX 7.1. However I don´t know where is installed or how to excecute the service,because is not working.  somebody can help me?

root@servername:/tmp # oslevel -s
7100-03-03-1415
root@servername:/tmp # lslpp -l |grep python
  aixtools.python.py38.adt   3.8.2.0  COMMITTED  python py38 ADT files
  aixtools.python.py38.man.en_US
                             3.8.2.0  COMMITTED  python py38 man pages
  aixtools.python.py38.rte   3.8.2.0  COMMITTED  python py38 31-Mar-2020
79
AIXTOOLS / Re: Pyinstaller3.6 issue in aix7.1
« Last post by Michael on April 09, 2020, 09:53:10 AM »
@jessding2503 - any change?
80
AIXTOOLS / Re: Pyinstaller3.6 issue in aix7.1
« Last post by Michael on April 05, 2020, 05:26:52 PM »
I know it is saying from /unix - but I need to check ond see if that is actually supposed to come from the kernel or not.
Also, try - $ dump -X64 -H /data/manager_aix/psutil_aix.so
and also
$ ldd /data/manager_aix/psutil_aix.so
And is /data/manager_aix/psutil_aix.so opensource, or your own code?
atm: I do not think it is the Python executable, or pyinstaller - there is the implicit assumption that a shared library is able to find it's dependencies.
Pages: 1 ... 6 7 [8] 9 10