Service Manual

Command
History
This guide is platform-specific. For command information about other platforms, refer to the relevant Dell
Networking OS Command Line Reference Guide.
The following is a list of the Dell Networking OS version history for this command.
Version Description
9.8(0.0P5) Introduced on the S4048-ON.
9.8(0.0P2) Introduced on the S3048-ON.
9.2(1.0) Introduced on the Z9500.
9.0.2.0 Introduced on the S6000.
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 flows
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 identification in a given port-
channel if a valid flow is entered. A mismatched flow error occurs if MAC-based hashing is configured for
a Layer 2 interface and you are trying to display a Layer 3 flow.
The output displays three entries:
● Egress port for unfragmented packets.
● In the event of fragmented packets, the egress port of the first 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 traffic 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 configured for MAC
● Load-balance is configured 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
te 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 Te 13/2
Time Domain Reflectometer (TDR) Commands
TDR is useful for troubleshooting an interface that is not establishing a link; either it is flapping 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 (configured—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
traffic.
● When testing between two devices, do not run the test on both ends of the cable.
Interfaces
691