Reference Guide
monitor interface command example
Dell#monitor interface tengig 0/1
Dell Networking OS uptime is 1 day(s), 4 hour(s), 31 minute(s)
Monitor time: 00:00:00 Refresh Intvl.: 2s
Interface: Te 0/1, Disabled, Link is Down, Linespeed is 1000 Mbit
Traffic statistics: Current Rate Delta
Input bytes: 0 0 Bps 0
Output bytes: 0 0 Bps 0
Input packets: 0 0 pps 0
Output packets: 0 0 pps 0
64B packets: 0 0 pps 0
Over 64B packets: 0 0 pps 0
Over 127B packets: 0 0 pps 0
Over 255B packets: 0 0 pps 0
Over 511B packets: 0 0 pps 0
Over 1023B packets: 0 0 pps 0
Error statistics:
Input underruns: 0 0 pps 0
Input giants: 0 0 pps 0
Input throttles: 0 0 pps 0
Input CRC: 0 0 pps 0
Input IP checksum: 0 0 pps 0
Input overrun: 0 0 pps 0
Output underruns: 0 0 pps 0
Output throttles: 0 0 pps 0
m - Change mode c - Clear screen
l - Page up a - Page down
T - Increase refresh interval t - Decrease refresh interval
q - Quit
Maintenance Using TDR
The time domain reectometer (TDR) is supported on all Dell Networking switch/routers. TDR is an assistance tool to resolve link
issues that helps detect obvious open or short conditions within any of the four copper pairs. TDR sends a signal onto the physical
cable and examines the reection of the signal that returns. By examining the reection, TDR is able to indicate whether there is a
cable fault (when the cable is broken, becomes unterminated, or if a transceiver is unplugged).
TDR is useful for troubleshooting an interface that is not establishing a link, that is, when the link is apping or not coming up. Do not
use TDR on an interface that is passing trac. When a TDR test is run on a physical cable, it is important to shut down the port on
the far end of the cable. Otherwise, it may lead to incorrect test results.
NOTE: TDR is an intrusive test. Do not run TDR on a link that is up and passing trac.
To test the condition of cables on 100/1000/10000 BASE-T modules, follow the below steps using the tdr-cable-test
command.
Step
Command Syntax Command Mode Usage
1.
tdr-cable-test tengigabitethernet <slot>/
<port>
EXEC Privilege To test for cable faults on the TenGigabitEthernet
cable.
• Between two ports, you must not start the
test on both ends of the cable.
• Enable the interface before starting the test.
• The port must be enabled to run the test or
the test prints an error message.
94
Interfaces










