show interface gigabitethernet
To display the first front panel interface (port 0) in a Cisco 4451 ISR, use the showinterfaces gigabitethernet command in privileged EXEC mode.
show interfaces gigabitethernet {ports}
Syntax Description
interface gigabitethernet |
Displays interface hardware. |
ports |
Displays local and registered IPC ports. |
Command Modes
Privileged EXEC
Command History
Release |
Modification |
---|---|
XE 16.11.1 |
This command was introduced. |
Usage Guidelines
You can use the show interfaces gigabitethernet command to display the first front panel interface (port 0) in a Cisco ISR4451-X router
Examples
The following is sample output from the show command with the ports keyword displays he first front panel interface (port 0) in a Cisco ISR4451-X router::
Router# show interfaces gigabitethernet GigabitEthernet0/0/0 is down, line protocol is down
Hardware is ISR4451-X-4x1GE, address is 003a.7d5e.8b40 (bia 003a.7d5e.8b40)
Internet address is 10.20.30.40/24
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not supported
Full Duplex, 1000Mbps, link type is auto, media type is SX
output flow-control is off, input flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input 02:45:34, output 02:00:47, output hang never
Last clearing of "show interface" counters 1d16h
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
618 packets input, 52156 bytes, 0 no buffer
Received 447 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 145 multicast, 118 pause input
189 packets output, 18556 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
597 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
The table below describes the significant fields shown in the display.
Field |
Description |
---|---|
GigabitEthernet0/0/0 is down, line protocol is down |
Indicates whether the interface hardware is currently active and if it has been taken down by an administrator.. |
line protocol is |
Indicates whether the software processes that handle the line protocol consider the line usable or if it has been taken down by an administrator. |
Hardware |
Hardware type and MAC address. |
Description |
Alphanumeric string identifying the interface. This appears only if the description interface configuration command has been configured on the interface. |
Internet address |
Sequence number of the in-sequence message that was last heard. |
MTU |
Maximum transmission unit of the interface. |
BW |
Bandwidth of the interface in kilobits per second. |
DLY |
Delay of the interface in microseconds. |
Reliability |
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes |
Rxload and Rxload |
Load on the interface (in the transmit “tx” and receive “rx” directions) as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. |
Encapsulation |
Encapsulation method assigned to the interface. |
Loopback |
Indicates whether loopback is set. |
Keepalive |
Indicates whether keepalives are set, and the time interval. |
Half-duplex, Full-duplex |
Indicates the duplex mode for the interface. |
1Gb/s |
Speed of the interface in Gigabits per second. |
Input Flow Rate… |
Specifies if input flow control is on or off. |
ARP Type |
Type of ARP assigned and the timeout period. |
Last input |
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This field is not updated by fast-switched traffic |
Output |
Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. Useful for knowing when a dead interface failed. |
Output hang |
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the “last” fields exceeds 24 hours, the number of days and hours is displayed. If that field overflows, asterisks are printed |
Last clearing |
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. A series of asterisks (***) indicates the elapsed time is too large to be displayed. 0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms) ago. |
Input queue (size/max/drops/flushes) |
Packet statistics on the input queue reported as:
|
Total Output Drops |
Total number of packets dropped because of a full output queue. |
Queueing Strategy |
Type of Layer 3 queueing active on this interface. The default is FIFO. |
Output queue (size/max) |
Number of packets in the output queue (size), and the maximum size of the queue (max). |
30 second input rate, 30 second output rate |
Average number of bits and packets transmitted per second in the last 30 seconds. If the interface is not in promiscuous mode, it senses network traffic it sends and receives (rather than all network traffic). The 30 second input and output rates should be used only as an approximation of traffic per second during a given 30 second period. These rates are exponentially weighted averages with a time constant of 30 seconds. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period. The calculated input rate includes packets counted as input errors. |
Packets Input |
Total number of packets received by the system. |
Bytes |
Total number of bytes, including data and MAC encapsulation, in all packets received by the system. |
Received…Broadcasts |
Total number of broadcast or multicast packets received by the interface. |
Runts |
Number of packets that are discarded because they are smaller than the minimum packet size of the medium. |
giants |
|
Throttles |
Number of times the receiver on the port was disabled, possibly because of buffer or processor overload. |
Input errors |
Includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts. |
CRC |
Cyclic redundancy check generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. |
Frame |
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device. |
Overrun |
Number of times the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver’s ability to handle the data. |
Ignored |
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers. Broadcast storms and bursts of noise can cause the ignored count to be increased. |
Watchdog |
Number of times the watchdog receive timer expired. |
Multicast |
Number of multicast packets. |
Pause input |
Number of pause packets received. |
Packets output |
Total number of messages transmitted by the system. |
Bytes |
Total number of bytes, including data and MAC encapsulation, transmitted by the system. |
Underruns |
Number of times that the transmitter has been running faster than the router can handle. |
Output errors |
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, because some datagrams may have more than one error and others may have errors that do not fall into any of the specifically tabulated categories. |
Collisions |
Number of messages retransmitted because of an Ethernet collision. This is usually the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). A packet that collides is counted only once in output packets. |
Interface resets |
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. Interface resets can occur when an interface is looped back or shut down. |
Babbles |
Transmit jabber timer expired. |
Late collision |
Number of late collisions. Late collision happens when a collision occurs after transmitting the preamble. |
Deferred |
Number of times that the interface had to defer while ready to transmit a frame because the carrier was asserted. |
Lost carrier |
Number of times the carrier was lost during transmission. |
No carrier |
Number of times the carrier was not present during the transmission. |
Pause output |
Number of pause packets transmitted. |
Output buffer failures, Output buffers swapped out |
Number of output butters failures and output buffers swapped out. |