HPE7-A08 · Question #164
Refer to the exhibits. The interface is configured on an HPE Aruba Networking CX 8320 for a VMware server NIC. The server admin complains that the VMware vMotion traffic on VLAN 3903 fails, but the…
The correct answer is A. The VLAN 3903 is configured with mtu 9198. The interface is already sending and receiving jumbo frames (as seen from packets in the 4096- 9216-byte range). vMotion uses large frames within its assigned VLAN, so the VLAN itself must support jumbo Because VLAN 3903 does not have its MTU raised, the switch drops oversized…
Question
Refer to the exhibits. The interface is configured on an HPE Aruba Networking CX 8320 for a VMware server NIC. The server admin complains that the VMware vMotion traffic on VLAN 3903 fails, but the server can ping other peers with a large payload size. What must be done to correct the issue based on the provided interface status and configuration?
Exhibit
Options
- AThe VLAN 3903 is configured with mtu 9198
- BThe interface 1/1/35 is configured with mtu 9198
- CThe VLAN 3903 is configured with jumbo
- DThat interface 1/1/35 is configured with jumbo
How the community answered
(21 responses)- A57% (12)
- B10% (2)
- C10% (2)
- D24% (5)
Explanation
The interface is already sending and receiving jumbo frames (as seen from packets in the 4096- 9216-byte range). vMotion uses large frames within its assigned VLAN, so the VLAN itself must support jumbo Because VLAN 3903 does not have its MTU raised, the switch drops oversized frames on that VLAN, causing vMotion failure even though the physical interface accepts jumbo frames.
Topics
Community Discussion
No community discussion yet for this question.