olá José,
running cfgmgr on the client LPAR before running cfgdev on the VIOS had no effect.
Original Message:
Sent: Thu February 08, 2024 06:03 AM
From: José Pina Coelho
Subject: ClntName not up to date in lsmap output
Did you try running cfgmgr on the client before running cfgdev on the VIOS ?
------------------------------
José Pina Coelho
IT Specialist at Kyndryl
Original Message:
Sent: Wed February 07, 2024 04:22 AM
From: Sylvain
Subject: ClntName not up to date in lsmap output
Hi Andrey,
cfgdev had no effect.
Original Message:
Sent: Mon February 05, 2024 06:16 AM
From: Andrey Klyachkin
Subject: ClntName not up to date in lsmap output
I think we need someone from HMC part of the IBM's world here. AFAIU this information comes from VIOS database. I don't remember how often the information is updated there but it usually takes some time.
Did you try to run cfgdev?
------------------------------
Andrey Klyachkin
https://www.power-devops.com
Original Message:
Sent: Fri February 02, 2024 04:44 AM
From: Sylvain
Subject: ClntName not up to date in lsmap output
Hello,
I use lsmap output in several admin scripts and I discovered that ClntName field is not up to date in lsmap output.
As a matter of fact, if an LPAR name as changed since the mapping of virtual FC to the physical FC (via vfcmap), the ClntName field still corresponds to initial LPAR name.
That is a problem because I suppose in my scripts that LPAR names (from ClntName) correspond to hostnames and I use these values to ssh into LPAR to do admin tasks. It works very well in most cases, apart when LPAR name has changed.
Is it a bug ?