000-221 · Question #219
An existing LPAR is configured with a vSCSI disk for a root volume group. An administrator is configuring NPIV to provide secondary storage to the partition. DLPAR operations are used to add the…
The correct answer is C. Save the current configuration to a profile. After using DLPAR to add NPIV adapters to a running LPAR, the administrator must save the current runtime configuration to the partition profile to ensure the adapters persist across future restarts.
Question
An existing LPAR is configured with a vSCSI disk for a root volume group. An administrator is configuring NPIV to provide secondary storage to the partition. DLPAR operations are used to add the required client and server adapters to the client and VIO Server partitions. Once the NPIV adapters have been configured, what action should be taken against the client LPAR to ensure access to SAN storage is not compromised?
Options
- AShutdown and reboot AIX.
- BShutdown and reactivate the profile.
- CSave the current configuration to a profile.
- DAdd the physical WWVPN to the virtual device configuration.
How the community answered
(27 responses)- A4% (1)
- B4% (1)
- C85% (23)
- D7% (2)
Why each option
After using DLPAR to add NPIV adapters to a running LPAR, the administrator must save the current runtime configuration to the partition profile to ensure the adapters persist across future restarts.
Shutting down and rebooting AIX causes unnecessary downtime and does not address the need to persist DLPAR changes to the partition profile.
Shutting down and reactivating from the unmodified profile would restore the pre-DLPAR configuration, removing the newly added NPIV adapters and eliminating secondary SAN storage access.
DLPAR operations modify a partition's active configuration in memory but do not automatically update the saved profile stored on the HMC or IVM. Saving the current configuration to the profile records the newly added NPIV client and server adapters so that if the LPAR is ever restarted or reactivated, the SAN storage connectivity provided by those adapters is not lost.
NPIV virtual adapters use virtual WWPNs assigned by the VIO Server - adding a physical WWPN directly to the virtual device configuration is not a valid or necessary step in NPIV client adapter setup.
Concept tested: AIX NPIV DLPAR adapter persistence via profile save
Source: https://www.ibm.com/docs/en/power-systems-hw?topic=npiv-configuring-virtual-fibre-channel-adapters
Topics
Community Discussion
No community discussion yet for this question.