500-440 · Question #38
In Cisco Finesse 10.0(x), which VM network adapter type removes the requirement to disable the LRO feature on the VM host?
The correct answer is C. E1000 network adapter type. E1000 is correct because it emulates an Intel 82545EM Gigabit Ethernet NIC in software, which handles packet processing in a way that does not rely on Large Receive Offload (LRO) at the hypervisor level. Cisco Finesse 10.0(x) installation guides specifically call out E1000 as…
Question
In Cisco Finesse 10.0(x), which VM network adapter type removes the requirement to disable the LRO feature on the VM host?
Options
- AVlance network adapter type
- BFlexible VM network adapter type
- CE1000 network adapter type
- DVMXNET network adapter type
- EVMXNET3 network adapter type
How the community answered
(60 responses)- A5% (3)
- B2% (1)
- C92% (55)
- E2% (1)
Explanation
E1000 is correct because it emulates an Intel 82545EM Gigabit Ethernet NIC in software, which handles packet processing in a way that does not rely on Large Receive Offload (LRO) at the hypervisor level. Cisco Finesse 10.0(x) installation guides specifically call out E1000 as the adapter choice that lets you skip the otherwise mandatory step of disabling LRO on the ESXi host - a step required to prevent packet-handling issues in the VM guest.
Why the distractors are wrong:
- Vlance (A) is a legacy, slow AMD PCnet32 emulation - it predates the LRO concern entirely and is not recommended for Finesse.
- Flexible (B) is a VMware adapter that can toggle between Vlance and VMXNET modes; it does not resolve the LRO requirement.
- VMXNET (D) is an older paravirtualized VMware adapter that still requires LRO to be disabled on the host.
- VMXNET3 (E) is the modern, high-performance paravirtual adapter and is a common wrong guess - but its built-in offload features (including LRO) are exactly why LRO must be disabled when using it with Finesse.
Memory tip: Think E1000 = "Emulated, no LRO needed." The paravirtual adapters (VMXNET, VMXNET3) are deeply integrated with the hypervisor's offload stack, so they create the LRO problem; the emulated E1000 sidesteps it entirely.
Topics
Community Discussion
No community discussion yet for this question.