Home > SPAN Questions 2

SPAN Questions 2

November 18th, 2019 Go to comments

Question 1

Question 2

Question 3

Explanation

A physical port that belongs to an EtherChannel group can be configured as a SPAN source port and still be a part of the EtherChannel. In this case, data from the physical port is monitored as it participates in the EtherChannel. However, if a physical port that belongs to an EtherChannel group is configured as a SPAN destination, it is removed from the group.

Reference: http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750x_3560x/software/release/12-2_55_se/configuration/guide/3750xscg/swspan.html

Question 4

Explanation

Remote SPAN (RSPAN) is used when source ports are not located on the same switch as the Destination port. RSPAN is an advanced feature that requires a special VLAN to carry the monitored traffic and is not supported by all switches.

The Configuring SPAN and RSPAN link (http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960/software/release/12-2_40_se/configuration/guide/scg/swspan.pdf) mentions about two things:

+ We recommend that you configure an RSPAN VLAN before you configure an RSPAN source or a destination session.
+ First create a new VLAN to be the RSPAN VLAN for the RSPAN session

But this question asks about “Cisco recommendation” so answer C is the better one.

Question 5

Question 6

Explanation

The RSPAN VLAN carries SPAN traffic between RSPAN source and destination sessions. It has these special characteristics:
+ All traffic in the RSPAN VLAN is always flooded.
+ No MAC address learning occurs on the RSPAN VLAN.
+ RSPAN VLAN traffic only flows on trunk ports.
+ RSPAN VLANs must be configured in VLAN configuration mode by using the remote-span VLAN configuration mode command.
+ STP can run on RSPAN VLAN trunks but not on SPAN destination ports.
+ An RSPAN VLAN cannot be a private-VLAN primary or secondary VLAN.

Reference: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750e_3560e/software/release/12-2_55_se/configuration/guide/3750escg/swspan.pdf

Question 7

Explanation

RSPAN extends SPAN by enabling remote monitoring of multiple switches across your network. The traffic for each RSPAN session is carried over a user-specified RSPAN VLAN that is dedicated for that RSPAN session in all participating switches (therefore answer B is correct). The SPAN traffic from the sources is copied onto the RSPAN VLAN through a reflector port and then forwarded over trunk ports that are carrying the RSPAN VLAN to any RSPAN destination session monitoring the RSPAN VLAN.

Reference: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2950/software/release/12-1_11_yj4/configuration/guide/lrescg/swspan.html

The RSPAN VLAN carries SPAN traffic between RSPAN source and destination sessions. One of the special characteristics is “No MAC address learning occurs on the RSPAN VLAN”.

Reference: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750e_3560e/software/release/12-2_55_se/configuration/guide/3750escg/swspan.pdf

Question 8

Explanation

A destination port has these characteristics:

+ …
+ It does not participate in any of the Layer 2 protocols (STP, VTP, CDP, DTP, PagP).

Reference: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750x_3560x/software/release/12-2_55_se/configuration/guide/3750xscg/swspan.html

Question 9

Explanation

The RSPAN VLAN carries SPAN traffic between RSPAN source and destination sessions. It has these special characteristics:
+ All traffic in the RSPAN VLAN is always flooded.
+ No MAC address learning occurs on the RSPAN VLAN.
+ RSPAN VLAN traffic only flows on trunk ports.
+ RSPAN VLANs must be configured in VLAN configuration mode by using the remote-span VLAN configuration mode command.
+ STP can run on RSPAN VLAN trunks but not on SPAN destination ports.
+ An RSPAN VLAN cannot be a private-VLAN primary or secondary VLAN.

Reference: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750e_3560e/software/release/12-2_55_se/configuration/guide/3750escg/swspan.pdf

Question 10

Comments
  1. No comments yet.
  1. No trackbacks yet.