nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

type
: local
state
: up
source intf :
rx
: Veth10
tx
: Veth10
both
: Veth10
source VLANs :
rx :
tx :
both :
filter VLANs : filter not specified
destination ports : Eth5/1
ERSPAN on Nexus 1000V
The Nexus 1000V series switches have the capability to configure traditional SPAN
sessions, referred to as local SPAN sessions, for Ethernet traffic in addition to ERSPAN.
ERSPAN differs from traditional SPAN in that ERSPAN enables the monitored traffic to be
encapsulated in a GRE packet and routed across an IP network. With ERSPAN, network
administrators can centralize network analysis tools and route the monitored traffic.
ERSPAN builds on the concepts of source ports and destination ports. Source ports, as their
name implies, are the source of the traffic to be sent via ERSPAN to the destination ports.
Source ports have the following requirements:
• Can be any port type including Ethernet, virtual Ethernet, port channel, or VLAN.
• Can be a VLAN. When a VLAN is used as SPAN source, all ports that belong to the
VLAN are considered as part of the SPAN source.
• Can be configured with a direction (ingress, egress or both) to monitor.
• Cannot be a SPAN destination port.
ERSPAN destinations define where traffic copied from the ERSPAN source will be sent.
ERSPAN destination ports are specified by an IP address.
In addition, ERSPAN destinations have the following restrictions:
• Cannot be ERSPAN sources
SPAN on the Nexus 1000V supports the ability to configure up to 64 SPAN and ERSPAN
sessions.
Configuration of ERSPAN on Nexus 1000V is a multistep process in which the ERSPAN
source and ERSPAN destination are defined. The first step is to configure the ERSPAN port
profile. Refer to Chapter 9, “Nexus 1000V,” for additional details on port profile
configuration. Example 7-18 illustrates a port profile that will be used for ERSPAN.
Example 7-18. ERSPAN Port Profile Configuration
Click here to view code image