Refer to the exhibit. A network administrator configured RSPAN to troubleshoot an issue between switch 1 and switch2. The switches are connected using interface GigabitEthernet 1/1. An external packet

Question

Exhibits

Options

• Aswitch1(config)# interface GigabitEthernet 1/1
• Bswitch2(config-if)# switchport trunk allowed vlan 10,20,30,40,50,60,70-80
• Cswitch2(config)# monitor session 1 source remote vlan 70
• Dswitch2(config)# monitor session 2 destination vlan 10
• Eswitch2(config)# monitor session 1 source remote vlan 70

• A
  14% (5)
• B
  71% (25)
• C
  9% (3)
• D
  6% (2)

Explanation

RSPAN Configuration Explanation

Options B and E are correct because RSPAN requires two key elements on the destination switch: the RSPAN VLAN (70) must be permitted on the trunk link connecting the two switches (B), and the destination switch must define a monitor session source pointing to the remote VLAN so it knows where to pull the mirrored traffic from (E). Without allowing VLAN 70 on the trunk, the mirrored traffic never reaches Switch 2, and without the source remote VLAN command, Switch 2 doesn't know to forward that traffic to the capture device.

Why the distractors are wrong:

• A is incomplete and irrelevant - simply entering the interface without additional context adds nothing to the RSPAN configuration.
• C uses monitor session 1 source remote vlan 70 but is attributed to switch2(config-if)# (interface config mode), which is the wrong configuration mode - RSPAN monitor commands must be entered in global configuration mode.
• D uses monitor session 2 with a destination vlan, which conflicts with the existing session number and incorrectly assigns a VLAN as a destination rather than an interface.

Memory Tip

Think "RSPAN = Remote VLAN must TRAVEL and be RECEIVED" - the VLAN must be allowed on the trunk (to travel) and defined as a source on the destination switch (to be received and forwarded to your capture device).

No community discussion yet for this question.