02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>FTOS</strong> Behavior: On <strong>the</strong> C-<strong>Series</strong> and S-<strong>Series</strong>, all monitored frames are tagged if <strong>the</strong> configured<br />

monitoring direction is transmit (TX), regardless of whe<strong>the</strong>r <strong>the</strong> monitored port (MD) is a Layer 2 or<br />

Layer 3 port. If <strong>the</strong> MD port is a Layer 2 port, <strong>the</strong> frames are tagged with <strong>the</strong> VLAN ID of <strong>the</strong> VLAN to<br />

which <strong>the</strong> MD belongs. If <strong>the</strong> MD port is a Layer 3 port, <strong>the</strong> frames are tagged with VLAN ID 4095. If<br />

<strong>the</strong> MD port is in a Layer 3 VLAN, <strong>the</strong> frames are tagged with <strong>the</strong> respective Layer 3 VLAN ID. For<br />

example, in <strong>the</strong> configuration source gig 6/0 destination gig 6/1 direction tx, if <strong>the</strong> MD port<br />

gigabite<strong>the</strong>rnet 6/0 is an untagged member of any VLAN, all monitored frames that <strong>the</strong> MG port<br />

gigabite<strong>the</strong>rnet 6/1 receives are tagged with <strong>the</strong> VLAN ID of <strong>the</strong> MD port. Similarly, if BPDUs are<br />

transmitted, <strong>the</strong> MG port receives <strong>the</strong>m tagged with <strong>the</strong> VLAN ID 4095. This behavior might result in a<br />

difference between <strong>the</strong> number of egress packets on <strong>the</strong> MD port and monitored packets on <strong>the</strong> MG<br />

port.<br />

Important Points to Remember<br />

• Port Monitoring is not supported on E<strong>the</strong>rScale plat<strong>for</strong>ms.<br />

• Port Monitoring is supported on physical ports only; VLAN and port-channel interfaces do not support<br />

port monitoring. A SONET port may only be a monitored port.<br />

• The Monitored (source, “MD”) and Monitoring ports (destination, “MG”) must be on <strong>the</strong> same switch.<br />

• In general, a monitoring port should have “no ip address" and "no shutdown" as <strong>the</strong> only configuration;<br />

<strong>FTOS</strong> permits a limited set of commands <strong>for</strong> monitoring ports; display <strong>the</strong>m using <strong>the</strong> command ?. A<br />

monitoring port also may not be a member of a VLAN.<br />

Configuring Port Monitoring<br />

To configure port monitoring:<br />

Step Task Command Syntax Command Mode<br />

3 Verify that <strong>the</strong> intended monitoring port has no<br />

configuration o<strong>the</strong>r than no shutdown, as shown in<br />

Figure 88.<br />

4 Create a monitoring session using <strong>the</strong> command<br />

monitor session from CONFIGURATION mode, as<br />

shown in Figure 88.<br />

5 Specify <strong>the</strong> source and destination port and direction<br />

of traffic, as shown in Figure 88.<br />

show interface EXEC Privilege<br />

monitor session CONFIGURATION<br />

source MONITOR SESSION<br />

<strong>FTOS</strong> <strong>Configuration</strong> <strong>Guide</strong>, version 7.7.1.0 177

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

Saved successfully!

Ooh no, something went wrong!