Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

RSPAN Redundant Destination Interface


I am installing a product called Forescout CounterACT.  This product works by having traffic forwarded to it along an RSPAN vlan.  The CounterACT Virtual Machine will be installed as a Highly Available VM in a Hyper-V farm. 

RSPAN specifically targets a destination interface as part of the configuration of RSPAN.  Should an issue arise where the Virtual Machine is moved to the other Hyper-V farm, the targeted destination port will no longer be correct in the switch config. 

Does anyone have any ideas how I can set up RSPAN with two destination ports or have the destination port change?



New Member

A NIC team can share the load

A NIC teaming can share the load of traffic between physical and virtual networks among some or all of its members, as well as provide passive failover in the event of a hardware failure or network outage



Observe these guidelines to choose the correct NIC Teaming policy:

  • Route based on the originating port ID: Choose an uplink based on the virtual port where the traffic entered the virtual switch.
  • Route based on an IP hash: Choose an uplink based on a hash of the source and destination IP addresses of each packet. For non-IP packets, whatever is at those offsets is used to compute the hash.
  • Route based on a source MAC hash: Choose an uplink based on a hash of the source Ethernet.
  • Use explicit failover order: Always use the highest order uplink from the list of Active adapters which passes failover detection criteria.
  • Route based on physical NIC load (Only available on Distributed Switch): Choose an uplink based on the current loads of physical NICs.