000-221 · Question #136
A host has a single virtual Ethernet adapter (ent0) configured with only a default PVID, and the administrator is trying to determine why it cannot be used to reach any other system on the network…
The correct answer is C. Look on the HMC to determine which VLAN is configured for the adapter. For a virtual Ethernet adapter on an IBM Power LPAR, the authoritative PVID and VLAN assignment is defined at the hypervisor level and is managed through the HMC. The AIX operating system view of the adapter does not hold the definitive VLAN configuration set by the…
Question
A host has a single virtual Ethernet adapter (ent0) configured with only a default PVID, and the administrator is trying to determine why it cannot be used to reach any other system on the network. He suspects that it may be caused by a problem in the VLAN configuration. How would the administrator determine the VLAN for which the adapter was configured?
Options
- AUse the command 'Isdev -I ent0' on the host to determine the port VLAN ID.
- BUse the command 'Isattr-EI ent0' on the host to determine the port VLAN ID.
- CLook on the HMC to determine which VLAN is configured for the adapter.
- DExamine the Shared Ethernet Adapter on the Virtual I/O Server to determine which VLAN the adapter is using.
How the community answered
(27 responses)- A4% (1)
- B11% (3)
- C81% (22)
- D4% (1)
Why each option
For a virtual Ethernet adapter on an IBM Power LPAR, the authoritative PVID and VLAN assignment is defined at the hypervisor level and is managed through the HMC. The AIX operating system view of the adapter does not hold the definitive VLAN configuration set by the administrator.
The lsdev -l ent0 command displays the device operational state and class in AIX but does not expose VLAN or PVID attributes that are configured at the hypervisor level on the HMC.
The lsattr -El ent0 command lists ODM attributes for the device driver in AIX, but for a virtual Ethernet adapter the values shown may not accurately reflect the HMC-level VLAN assignment and are therefore not a reliable source for diagnosing VLAN misconfiguration.
Virtual Ethernet adapters and their PVID assignments are defined as part of the logical partition hardware profile within the HMC. The HMC holds the authoritative record of which VLAN a given virtual adapter slot is assigned to, making it the correct and definitive place to verify and troubleshoot VLAN configuration issues for a specific client adapter.
Examining the Shared Ethernet Adapter on the VIOS reveals which VLANs the SEA is trunking on the physical network side, but does not directly identify the specific PVID assigned to the individual client virtual Ethernet adapter.
Concept tested: HMC-level PVID lookup for IBM Power virtual Ethernet adapters
Source: https://www.ibm.com/docs/en/power10/9105-22A?topic=adapters-virtual-ethernet-adapter-configuration
Topics
Community Discussion
No community discussion yet for this question.