000-221 · Question #65
A NIM server is used to support different AIX Technology Levels among several clients. Each technology level is maintained in a separate lpp_source. Which command(s) will display what AIX fixes are…
The correct answer is A. niminv-o fixget-a targets=lpp_source1,lpp_source2. The niminv command with the fixget operation queries one or more NIM lpp_source resources to report which AIX fixes are available at each Technology Level.
Question
A NIM server is used to support different AIX Technology Levels among several clients. Each technology level is maintained in a separate lpp_source. Which command(s) will display what AIX fixes are available for several TL levels supported by a NIM server?
Options
- Animinv-o fixget-a targets=lpp_source1,lpp_source2
- Bnim_update_check-lsumalpp_source1 nim_update_check-lsumalpp_source2
- Cnim-o cust-a fixes=update_all lpp_source1Jpp_source2
- Dnim -o Ippmgr-a Ippmgr_flags="Isb" lpp_source1, Ipp_source2
How the community answered
(51 responses)- A84% (43)
- B10% (5)
- C4% (2)
- D2% (1)
Why each option
The niminv command with the fixget operation queries one or more NIM lpp_source resources to report which AIX fixes are available at each Technology Level.
niminv -o fixget performs a fix inventory against NIM resources, and the -a targets= attribute accepts a comma-separated list of lpp_source names, allowing a single command to report available fixes across multiple Technology Levels maintained on the NIM server.
nim_update_check -lsuma is not valid syntax for querying fix availability across multiple lpp_sources simultaneously from a NIM server.
nim -o cust -a fixes=update_all installs fixes onto NIM client systems rather than displaying what fixes are available in lpp_sources.
nim -o lppmgr is used for managing and cleaning up lpp_source contents, not for reporting available fix levels across multiple Technology Levels.
Concept tested: NIM niminv fixget for multi-TL fix inventory
Source: https://www.ibm.com/docs/en/aix/7.3?topic=n-niminv-command
Topics
Community Discussion
No community discussion yet for this question.