Which Two Settings Complete an ERSPAN Passive Interface in FMC?
An engineer must configure an ERSPAN passive interface on a Cisco Secure IPS by using the Cisco Secure Firewall Management Center. These configurations have been performed already: • Configure the passive interface. • Configure the ERSPAN IP address. Which two additional settings must be configured to complete the configuration? (Choose two.)
Community Insight
This item tests the exact field set FMC demands for an ERSPAN passive interface on a Secure IPS — the trap is choosing generic interface options like Destination MAC or inline-only settings such as Bypass Mode.
Completing an ERSPAN passive interface on a Cisco Secure IPS managed by Secure Firewall Management Center requires more than the passive interface and ERSPAN IP address. The remaining required fields are the Flow ID and the Source IP, making D and E the correct answer.
Candidates often pick "Destination MAC" because ERSPAN is a GRE-encapsulated mirroring technology where a destination MAC feels intuitively necessary, but FMC does not require it; Bypass Mode is also tempting even though it applies to inline sets, not passive interfaces.
Community Discussion (2 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Cisco's FMC device configuration documentation for interfaces states that, for ERSPAN interfaces, you must set the Flow ID to identify the ERSPAN traffic and the Source IP address of the ERSPAN traffic. Because the scenario already covers the passive interface itself and the ERSPAN IP address, the only two remaining required fields are Flow ID (D) and Source IP (E). These two values let the sensor recognize and correctly decapsulate the mirrored GRE stream arriving from the ERSPAN source switch or router. Without a Flow ID the sensor cannot distinguish this ERSPAN stream from other traffic, and without the Source IP it cannot validate the origin of the mirrored packets, so the configuration would be incomplete and the passive interface would not come up as intended. Selecting D and E therefore matches the vendor's own checklist exactly.Why the Other Options Are Wrong
Destination MAC (A) is part of how a physical switch or router builds the ERSPAN frame on the network side, but FMC's ERSPAN passive interface dialog does not require you to enter one, so it does not complete the configuration described. TCP Intercept (B) is a legacy IOS denial-of-service protection feature and has nothing to do with defining an ERSPAN monitoring interface in FMC. Bypass Mode (C) is a hardware-bypass setting relevant to inline sets and inline interface pairs — a passive interface never sits in the forwarding path, so bypass is meaningless here. Only Flow ID and Source IP are the missing mandatory parameters, and the question explicitly asks for exactly two.Community Comment Notes
Community consensus lines up with the vendor documentation rather than with any distractor. As gaprendizaje noted, the correct pair is D and E, and that commenter pointed directly at the FMC interfaces documentation containing the line "For ERSPAN interfaces, set…" the Flow ID and Source IP of the ERSPAN traffic. donciga confirmed the same pair and cited the Firepower Management Center 6.4 guide chapter on inline sets and passive interfaces for threat defense. The shared reasoning is that FMC's ERSPAN fields are deliberately minimal — passive interface, ERSPAN IP address, Flow ID and Source IP — which is exactly the four-item list the question is checking.Exam Strategy Tip
Treat interface-configuration items as checklist-memorization questions: for each monitoring mode, recall the precise FMC fields. If an option sounds like it belongs to inline sets (bypass) or to another feature entirely (TCP Intercept), eliminate it before weighing the remaining candidates.Official Reference
- https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/management-center/device-config/760/management-center-device-config-76/interfaces-settings-ifcs-ips.html
- https://www.cisco.com/c/en/us/td/docs/security/firepower/640/configuration/guide/fpmc-config-guide-v64/inline_sets_and_passive_interfaces_for_firepower_threat_defense.html
Exam Strategy
Memorize the four FMC fields that define an ERSPAN passive interface: the passive interface itself, the ERSPAN IP address, the Flow ID and the Source IP. If an option belongs to inline sets (Bypass Mode) or to an unrelated IOS feature (TCP Intercept), discard it immediately and then confirm the count matches what the question demands.
Frequently Asked Questions
Why is Destination MAC not required for an FMC ERSPAN passive interface?
FMC only asks for the ERSPAN IP address, Flow ID and Source IP; the destination MAC is handled on the network side when the mirroring switch or router builds the ERSPAN frame.
Why is Bypass Mode wrong for an ERSPAN passive interface?
Bypass Mode is a hardware-bypass option for inline sets and inline interface pairs. A passive interface only receives monitored traffic, so it is never in the forwarding path and bypass does not apply.