000-221 · Question #138
After performing a NIM rte install, the administrator noticed that not all filesets are at the correct Technology Level (TL). What action will help the administrator determine why the inconsistent…
The correct answer is D. On the NIM server run the NIM IsIpp command to indentify downlevel filesets contained in the lpp_source. When a NIM rte install produces inconsistent fileset Technology Levels, the root cause is often that the lpp_source resource itself contains downlevel filesets. Running the NIM lslpp operation on the server against the lpp_source directly reveals which filesets are at…
Question
After performing a NIM rte install, the administrator noticed that not all filesets are at the correct Technology Level (TL). What action will help the administrator determine why the inconsistent fileset levels were installed?
Options
- AOn the NIM server, run an Ippchk to identify if the Software Vital Product Data is valid.
- BOn the NIM client, run oslevel command against the TL to identify missing prerequisites.
- CRun instfix command on NIM client to determine what filesets are inconsistent.
- DOn the NIM server run the NIM IsIpp command to indentify downlevel filesets contained in the lpp_source.
How the community answered
(63 responses)- A14% (9)
- B5% (3)
- C3% (2)
- D78% (49)
Why each option
When a NIM rte install produces inconsistent fileset Technology Levels, the root cause is often that the lpp_source resource itself contains downlevel filesets. Running the NIM lslpp operation on the server against the lpp_source directly reveals which filesets are at lower-than-expected levels.
The lppchk command validates the consistency and integrity of filesets already installed on a running system, but executing it on the NIM server does not reveal the fileset levels stored inside an lpp_source resource.
The oslevel command reports the current Technology Level of the AIX installation on the client and can surface missing filesets relative to a TL, but it does not diagnose whether the NIM lpp_source itself supplied downlevel packages.
The instfix command reports on APARs and fix packages installed on the local system but is not designed to audit fileset levels contained within a NIM lpp_source or explain why downlevel content was installed from the source.
The NIM lslpp operation queries the contents of an lpp_source resource on the NIM server and lists each fileset along with its installed level. By running this command the administrator can directly compare the levels present in the source against the target TL and identify any downlevel or missing filesets that caused the inconsistent installation outcome on the client.
Concept tested: NIM lslpp operation to audit lpp_source fileset levels
Source: https://www.ibm.com/docs/en/aix/7.3?topic=nim-lslpp-operation
Topics
Community Discussion
No community discussion yet for this question.