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

• Cannot be a SPAN destination port.
SPAN destinations, as their name implies, define where traffic copied from the SPAN
source will be sent. Destination ports have the following requirements:
• Can include any physical port including Ethernet or Fibre Channel
Note
Logical interfaces such as virtual Fibre Channel, Ethernet port channel, and SAN port
channel interfaces cannot be SPAN destinations.
• Can be configured in only one SPAN session at a time
• Do not participate in a spanning-tree instance
• Can be configured to support IDS/IPS applications where the need to have the
forwarding engine learn the MAC address of the IDS/IPS is required
• Can be configured to inject packets enabling IDS/IPS to disrupt traffic
In addition, SPAN destinations have the following restrictions:
• Cannot be SPAN sources
• Cannot be Virtual Fibre Channel, Ethernet port channel, and SAN port channel
interfaces
SPAN on the Nexus 5x00 supports the capability to configure up to 18 SPAN sessions with
any two active simultaneously. Table 7-2 lists the SPAN session limits for the Nexus 5x00.
Table 7-2. Nexus 5x00 SPAN Session Limits
Configuring SPAN on Nexus 5x00
Configuring SPAN on a Nexus 5x00 is a multistep process in which the SPAN source,
SPAN destination, and monitoring ports are defined. The first step is to define the monitor
port connection where the network analysis, IDS/IPS, or other device collects the SPAN
traffic, as demonstrated in Example 7-8. Figure 7-3 illustrates the topology used in
Examples 7-8 through 7-14.