mcaroca

E-mail sent

Log file upload done. From already thank you very much.

Hi: Is this error logged in file: load_hmc_rest_api_conf.out related to the stated problem? ... SEA0 Rest API Error : SEAArray (IBM1 @ hmc1) Rest API 2022-06-16 15:01:42 : Check and write .. /home/lpar2rrd/lpar2rrd/tmp/restapi/IBM1__sea__hmc1.json, HASH(0x285a128), 0 Rest API 2022-06-16 15:01:42 : Write to file :…

Hello team: With version server lpar2rrd 7.4 the problem persists with different IBM Power servers connected by REST API. The problem is that when you go to "Configuration - SEA" it displays only one SEA for each server. Each IBM power server has 2 test environment VIOS (ha_mode) plus 2 production environment VIOS…

Hi team, Have they managed to reproduce the problem?

Hi: I mean incomplete deployment, as an incomplete list of existing SEAs. The 3 IBM servers have 4 VIOS and each VIOS has 2 SEA's active and using. That is, in each IBM server there are 8 SEA's in total. As can be seen in this screenshot, only one SEA is listed per server (omitting 7). In each VIOS: # lsdev -Cc adapter…

Hello: Incomplete deployment could be related to one of these messages?

If you prefer, there will be an IBM support case to confirm the proposed solution or for them to indicate any additional alternatives.

Hello: The problem is with the counters of the affected LPAR in the same HMC. It cannot be that the idle_cycles counter is greater than capped_cycles (I highlight it in red box). I solved it with alternative 1 already indicated. "1.- The least impact and if it has the LPM capacity. You can migrate 
the non-active Lpar.…

Hello:
 Maybe it's something similar that happened to me, see: https://forum.xorux.com/discussion/975/100-bad-lpar-cpu-graph-after-running-resource-affinity-process-on-power8-server-in-hmc#latest

Also another detail, apparently the information of all the existing VIOS is not obtained.

Hi: Perhaps the observed pattern is that it only lists a single SEA per server (there are 2 on each server)

Hello: With this new installer it was possible to activate the lpar2rrd monitoring service. Thank you so much. [lpar2rrd@ibmmon lpar2rrd-7.21]$ sh ./update.sh Where is LPAR2RRD actually located [/home/lpar2rrd/lpar2rrd]: Extracting distribution Backing up original version : 7.20 to…

Hello: The service was not working after the update attempt. These types of errors appear in logs: BEGIN failed - compilation aborted at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 25. Compilation failed in require at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 25. BEGIN failed - compilation aborted at…

Resolved. With the shared file it worked perfect on all affected graphics. Thank you very much for your time.

Remember to first select a time range and then click on graph.

[Fri Apr 23 09:11:38 2021] detail-graph-cgi.pl: ERROR: Expected some arguments after 'COMMENT:' at /home/lpar2rrd/lpar2rrd/bin/detail-graph-cgi.pl line 8158 [Fri Apr 23 09:11:42 2021] detail-graph-cgi.pl: ERROR: Expected some arguments after 'COMMENT:' at /home/lpar2rrd/lpar2rrd/bin/detail-graph-cgi.pl line 8158

Hello In version 7.10 of Lpar2rrd when trying to solve the problem reported here. Now it presents the following error window in the same graphics indicated in this discussion. Thank you

Thank you very much

Only labels appear wrong in the larger window. It should keep the label with the previously selected date range.

The fact of linking the 2 HMC's that manage the same IBM servers to avoid losing metrics in the event of an eventual incident with any HMC. Duplicate servers are deployed in "Configuration - Servers", through REST API.

IBM Support notes that there is a recently discovered flaw related to partition LPM and counts with dedicated processors. Its repair is already being worked on but there is no certainty when it is released. At the moment, the alternatives to correct the counters are: 1.- The least impact and if it has the LPM capacity. You…

It is not an API problem, you can also see the difference of the counters at the command level (see attached). So I am going to open a case in IBM support in this regard I will inform you of news.

I have restarted the LPar and the problem persists. The CPU metric is still frozen at 100%. When reviewing the metrics directly on the web HMC they look correct (see screenshot). Will it be a problem with the API? Is IBM responsible for developing that API to see if I can open a case on IBM support?Thank you.

Lpar have always been with core dedicated, the affinity process (Dynamic Platform Optimizer) serves to reorganize the allocation of cpu and memory to an lpar or vios. Ref. Dynamic Platform Optimizer (affinity cpu / ram process): https://www.ibm.com/support/knowledgecenter/TI0003N/p8hat/p8hat_dpoovw.htm…