22.05.2017 Views

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

Nexus Switching 2nd Edition

Nexus Switching 2nd Edition

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Jealousy(config)# monitor session 1<br />

Jealousy(config-monitor)# source vlan 100 rx<br />

Jealousy(config-monitor)# source vlan 101 tx<br />

Jealousy(config-monitor)# source vlan 102<br />

Jealousy(config-monitor)# description SPAN Session 1<br />

Jealousy(config-monitor)# destination interface e1/26<br />

Jealousy(config-monitor)# no shut<br />

Jealousy(config-monitor)# end<br />

Tip<br />

Don’t forget to no shut the monitor session!<br />

The monitor session’s status can be reviewed through the use of the show monitor<br />

comm<strong>and</strong>, as demonstrated in Example 7-4. This information is helpful when verifying the<br />

SPAN session’s configuration <strong>and</strong> status.<br />

Example 7-4. Displaying a Monitor Session’s Configuration<br />

Click here to view code image<br />

Jealousy# show monitor session 1<br />

session 1<br />

---------------<br />

description : SPAN Session 1<br />

type<br />

: local<br />

state<br />

: down (No operational src/dst)<br />

source intf :<br />

rx :<br />

tx :<br />

both :<br />

source VLANs :<br />

rx : 100,102<br />

tx : 101-102<br />

both : 102<br />

filter VLANs : filter not specified<br />

destination ports : Eth1/26<br />

Legend: f = forwarding enabled, l = learning enabled<br />

When the ingress <strong>and</strong> learning keywords are present on the monitor port configuration—for<br />

example, to support an IDS/IPS—the destination port’s status reflects this, as shown in<br />

Example 7-5.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!