27.03.2013 Views

Cisco Broadband Cable Command Reference Guide

Cisco Broadband Cable Command Reference Guide

Cisco Broadband Cable Command Reference Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

show interface cable<br />

2-430<br />

Table 2-35 show interface cable Field Descriptions (continued)<br />

Field Description<br />

<strong>Cisco</strong> <strong>Broadband</strong> <strong>Cable</strong> <strong>Command</strong> <strong>Reference</strong> <strong>Guide</strong><br />

Chapter 2 <strong>Cisco</strong> <strong>Cable</strong> Modem Termination System <strong>Command</strong>s<br />

runts Number of packets that are discarded because they are smaller than<br />

the medium’s minimum packet size.<br />

giants Number of packets that are discarded because they are bigger than<br />

the standard Ethernet Maximum Transmission Unit (MTU) size.<br />

For Ethernet packets, RFC 1757 defines giants as “the total number<br />

of packets received that were longer than 1518 octets (excluding<br />

framing bits, but including FCS octets) and were otherwise well<br />

formed.”<br />

input errors Total number of errors received on the interface. This count<br />

includes runts and giants, which are shown above, as well as other<br />

errors, such as no buffers, and CRC, frame, overrun, and ignored<br />

counts. This count can also include DOCSIS protocol errors such<br />

as an invalid SID in the DOCSIS frame, a bad extended header<br />

length, corrupted concatenated packets, and invalid bandwidth<br />

requests.<br />

CRC Indicates the number of times the cyclic redundancy checksum<br />

(CRC) generated by the originating LAN station or far-end device<br />

does not match the checksum calculated from the data received.<br />

frame Number of packets received incorrectly having a CRC error and a<br />

non-integer number of octets.<br />

overrun Number of times the receiver hardware was unable to forward<br />

received data to a hardware buffer because the input rate exceeded<br />

the receiver’s ability to handle the data.<br />

ignored Number of received packets ignored by the interface because the<br />

interface hardware ran low on internal buffers.<br />

packets output Total number of messages sent by the system.<br />

bytes Total number of bytes, including data and MAC encapsulation, sent<br />

by the system.<br />

underruns Number of times the sender has been running faster than the<br />

receiving device can handle.<br />

output errors Sum of all errors that prevented the final transmission of packets<br />

out of the interface being examined.<br />

collisions Not applicable to the <strong>Cisco</strong> uBR7246.<br />

interface resets Number of times an interface has been completely reset.<br />

output buffer failures Number of times the output buffer has failed.<br />

output buffer swapped out Number of times the output buffer has been swapped out.<br />

Tip In <strong>Cisco</strong> IOS Release 12.1(12)EC, 12.2(8)BC1, and later releases, you can add a timestamp to show<br />

commands using the exec prompt timestamp command in line configuration mode.<br />

OL-1581-05

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

Saved successfully!

Ooh no, something went wrong!