Users Guide

Version Description
8.3.19.0 Introduced on the S4820T.
8.3.11.1 Introduced on the Z9000.
8.3.10.0 Introduced on the S4810.
Usage Information
Because this command calculates based on a Layer 2 hash algorithm, use this command to display ows for
switched Layer 2 packets, not for routed packets (use the show ip flow command to display routed
packets).
The show port-channel-flow command returns the egress port identication in a given port-channel
if a valid ow is entered. A mismatched ow error occurs if MAC-based hashing is congured for a Layer 2
interface and you are trying to display a Layer 3 ow.
The output displays three entries:
• Egress port for unfragmented packets.
• In the event of fragmented packets, the egress port of the rst fragment.
• In the event of fragmented packets, the egress port of the subsequent fragments.
NOTE: In the show port channel flow command output, the egress port for an unknown
unicast, multicast, or broadcast trac is not displayed.
The following example shows the show port-channel-flow outgoing-port-channel number
incoming-interface interface source-mac address destination-mac address
• Load-balance is congured for MAC
• Load-balance is congured for IP 4-tuple/2-tuple
• A non-IP payload is going out of Layer 2 LAG interface that is a member of VLAN with an IP address
Example
Dell#show port-channel-flow outgoing-port-channel 1 incoming-interface gi
3/3
source-mac 00:00:50:00:00:00 destination-mac 00:00:a0:00:00:00
Egress Port for port-channel 1, for the given flow, is Gi 13/2
Time Domain Reectometer (TDR) Commands
TDR is useful for troubleshooting an interface that is not establishing a link; either it is apping or not coming up at all. TDR detects
open or short conditions of copper cables on 100/1000 Base-T modules.
Important Points to Remember
• The interface and port must be enabled (congured—refer to the interface command) before running TDR. An error
message is generated if you have not enabled the interface.
• The interface on the far-end device must be shut down before running TDR.
• Because TDR is an intrusive test on an interface that is not establishing a link, do not run TDR on an interface that is passing
trac.
• When testing between two devices, do not run the test on both ends of the cable.
tdr-cable-test
Test the condition of copper cables on 100/1000 Base-T modules.
702
Interfaces