[Webinar] Streamline your web hosting managementRegister Today

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1621
  • Last Modified:

ER-SPAN and traffic filtering

We are trying to span traffic from site A to site B.  Site A is a VoIP telephony call centre and site B is a server building where the voice calls must be recorded.  The Cisco floor switches in site A are configured to ER-SPAN the traffic to specific ports in site B, into which are plugged the voice recording servers.  We're using ER-SPAN as its a layer 3 network architecture...this wont be changing.
We set up the SPAN and it sent ALL traffic to site B, and crashed the network.  Ouch.  We need to find a way to restrict or filter the traffic being spanned to be RTP traffic only (just the voice traffic, not someone downloading Shrek 2!)
Limitations with ERSPAN seem to be that we cannot apply an ACL to it, nor can we get the policy based routing right to try filter this traffic.
We're banged our heads together and are stuck!  Any suggestions would be welcomed.
  • 3
1 Solution
CasinoAlAuthor Commented:
I should add that the switches at both ends of this arrangement are Cisco 6500s

What code are you running? With Release 12.2(18)SXD and later releases, for local SPAN, you can configure per-VLAN filtering on destination trunk ports using allowed VLAN lists.

ERSPAN Guidelines and Restrictions

These are ERSPAN guidelines and restrictions:

"Release 12.2(18)SXE and later releases support ERSPAN.

"Release 12.2(18)SXF and later releases support ERSPAN when the router is operating in any switching mode. (CSCec70695)

"Release 12.2(18)SXE and rebuilds support ERSPAN only when the router is operating in the compact switching mode: all modules must be fabric-enabled.

"The following supervisor engines support ERSPAN:

Supervisor engines manufactured with PFC3B and PFC3BXL support ERSPAN.

A WS-SUP720 (a Supervisor Engine 720 manufactured with a PFC3A) can only support ERSPAN if it has hardware version 3.2 or higher. Enter the show module version | include WS-SUP720-BASE command to display the hardware version. For example:

Router# show module version | include WS-SUP720-BASE

 7    2  WS-SUP720-BASE     SAD075301SZ Hw :3.2

To confirm that your supervisor engine supports ERSPAN, enter the show asic-version slot slot_number | include ASIC|HYPERION command for the supervisor engine. For example:

Router# show asic-version slot 1 | include ASIC|HYPERION

Module in slot 1 has 2 type(s) of ASICs

        ASIC Name      Count      Version

         HYPERION          1      (6.0)

harbor235 ;}
CasinoAlAuthor Commented:
thanks for your comments. We have successfully activated ER SPANing so we know it works.  the tricky bit is that its SPANing ALL traffic on the source switch,  we were trying to filter what's spanned so it is only the RTP streams - this is the VoIP component.

How or where are filters applied?  Is it possible that filtering traffic is simple not compatible with ER-SPAN, or are we just missing the right config item - eg filtering on the ACL, not the VACL etc?

any further comments of course gratefully received!

you might check this link in ciscowiki: http://supportwiki.cisco.com/ViewWiki/index.php/VACL_Capture_for_Granular_Traffic_Analysis_with_Cisco_Catalyst_6000/6500_Running_Cisco_IOS_Software

in order to filter the traffic you need rather VACL. VSPAN just can't du that.

I'm not quite sure how ER-SPAN is different from VSPAN. it seems it does basically the same but can send the captured traffic over routed network. in any case you might consider to apply PACL on your destination port so you don't need to change your current configuration. just add the needed filtering on port level (no matter this is L2 port you still can apply this special PACL). more info:

if you manage to make it work you could post some details and/or configuration example. it would be definitely interesting for other readers
CasinoAlAuthor Commented:
I'm afriad neither of these solved the issue.  On further escalation direct to Cisco we learned that when employing an ER-SPAN, its not possible to apply a filter or ACL.  I dont understand much about it, but it has to do with GRE tunnels?

We eventually split the network another way so that the ER span picked up and spanned a particular VLAN and the only traffic on that VLAN was voice.


PS - please can this be marked as "solved by asker?"

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now