Examples
The following is sample output from the
show
interface command:
> show interface
Interface GigabitEthernet1/1 "outside", is down, line protocol is down
Hardware is Accelerator rev01, BW 1000 Mbps, DLY 10 usec
Auto-Duplex, Auto-Speed
Input flow control is unsupported, output flow control is off
MAC address e865.49b8.97f2, MTU 1500
IP address unassigned
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
0 L2 decode drops
0 packets output, 0 bytes, 0 underruns
0 pause output, 0 resume output
0 output errors, 0 collisions, 0 interface resets
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (blocks free curr/low): hardware (2047/2047)
output queue (blocks free curr/low): hardware (2047/2047)
Traffic Statistics for "outside":
0 packets input, 0 bytes
0 packets output, 0 bytes
0 packets dropped
1 minute input rate 0 pkts/sec, 0 bytes/sec
1 minute output rate 0 pkts/sec, 0 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 0 pkts/sec, 0 bytes/sec
5 minute output rate 0 pkts/sec, 0 bytes/sec
5 minute drop rate, 0 pkts/sec
Interface GigabitEthernet1/2 "inside", is down, line protocol is down
Hardware is Accelerator rev01, BW 1000 Mbps, DLY 10 usec
Auto-Duplex, Auto-Speed
Input flow control is unsupported, output flow control is off
MAC address e865.49b8.97f3, MTU 1500
IP address 192.168.45.1, subnet mask 255.255.255.0
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
0 L2 decode drops
0 packets output, 0 bytes, 0 underruns
0 pause output, 0 resume output
0 output errors, 0 collisions, 0 interface resets
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (blocks free curr/low): hardware (2047/2047)
output queue (blocks free curr/low): hardware (2047/2047)
Traffic Statistics for "inside":
0 packets input, 0 bytes
0 packets output, 0 bytes
0 packets dropped
1 minute input rate 0 pkts/sec, 0 bytes/sec
1 minute output rate 0 pkts/sec, 0 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 0 pkts/sec, 0 bytes/sec
5 minute output rate 0 pkts/sec, 0 bytes/sec
5 minute drop rate, 0 pkts/sec
Interface GigabitEthernet1/3 "", is administratively down, line protocol is down
Hardware is Accelerator rev01, BW 1000 Mbps, DLY 10 usec
Auto-Duplex, Auto-Speed
Input flow control is unsupported, output flow control is off
Available but not configured via nameif
MAC address e865.49b8.97f4, MTU not set
IP address unassigned
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
0 L2 decode drops
0 packets output, 0 bytes, 0 underruns
0 pause output, 0 resume output
0 output errors, 0 collisions, 0 interface resets
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (blocks free curr/low): hardware (2047/2047)
output queue (blocks free curr/low): hardware (2047/2047)
Interface GigabitEthernet1/4 "", is administratively down, line protocol is down
Hardware is Accelerator rev01, BW 1000 Mbps, DLY 10 usec
Auto-Duplex, Auto-Speed
Input flow control is unsupported, output flow control is off
Available but not configured via nameif
MAC address e865.49b8.97f5, MTU not set
IP address unassigned
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
0 L2 decode drops
0 packets output, 0 bytes, 0 underruns
0 pause output, 0 resume output
0 output errors, 0 collisions, 0 interface resets
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (blocks free curr/low): hardware (2047/2047)
output queue (blocks free curr/low): hardware (2047/2047)
Interface GigabitEthernet1/5 "", is administratively down, line protocol is down
Hardware is Accelerator rev01, BW 1000 Mbps, DLY 10 usec
Auto-Duplex, Auto-Speed
Input flow control is unsupported, output flow control is off
Available but not configured via nameif
MAC address e865.49b8.97f6, MTU not set
IP address unassigned
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
0 L2 decode drops
0 packets output, 0 bytes, 0 underruns
0 pause output, 0 resume output
0 output errors, 0 collisions, 0 interface resets
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (blocks free curr/low): hardware (2047/2047)
output queue (blocks free curr/low): hardware (2047/2047)
Interface GigabitEthernet1/6 "", is administratively down, line protocol is down
Hardware is Accelerator rev01, BW 1000 Mbps, DLY 10 usec
Auto-Duplex, Auto-Speed
Input flow control is unsupported, output flow control is off
Available but not configured via nameif
MAC address e865.49b8.97f7, MTU not set
IP address unassigned
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
0 L2 decode drops
0 packets output, 0 bytes, 0 underruns
0 pause output, 0 resume output
0 output errors, 0 collisions, 0 interface resets
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (blocks free curr/low): hardware (2047/2047)
output queue (blocks free curr/low): hardware (2047/2047)
Interface GigabitEthernet1/7 "", is administratively down, line protocol is down
Hardware is Accelerator rev01, BW 1000 Mbps, DLY 10 usec
Auto-Duplex, Auto-Speed
Input flow control is unsupported, output flow control is off
Available but not configured via nameif
MAC address e865.49b8.97f8, MTU not set
IP address unassigned
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
0 L2 decode drops
0 packets output, 0 bytes, 0 underruns
0 pause output, 0 resume output
0 output errors, 0 collisions, 0 interface resets
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (blocks free curr/low): hardware (2047/2047)
output queue (blocks free curr/low): hardware (2047/2047)
Interface GigabitEthernet1/8 "", is administratively down, line protocol is down
Hardware is Accelerator rev01, BW 1000 Mbps, DLY 10 usec
Auto-Duplex, Auto-Speed
Input flow control is unsupported, output flow control is off
Available but not configured via nameif
MAC address e865.49b8.97f9, MTU not set
IP address unassigned
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
0 L2 decode drops
0 packets output, 0 bytes, 0 underruns
0 pause output, 0 resume output
0 output errors, 0 collisions, 0 interface resets
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (blocks free curr/low): hardware (2047/2047)
output queue (blocks free curr/low): hardware (2047/2047)
Interface Management1/1 "diagnostic", is up, line protocol is up
Hardware is en_vtun rev00, BW 1000 Mbps, DLY 10 usec
Auto-Duplex(Full-duplex), Auto-Speed(1000 Mbps)
Input flow control is unsupported, output flow control is off
MAC address e865.49b8.97f1, MTU 1500
IP address unassigned
14247681 packets input, 896591753 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
0 L2 decode drops
0 packets output, 0 bytes, 0 underruns
0 pause output, 0 resume output
0 output errors, 0 collisions, 0 interface resets
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (blocks free curr/low): hardware (0/0)
output queue (blocks free curr/low): hardware (0/0)
Traffic Statistics for "diagnostic":
14247685 packets input, 697121911 bytes
0 packets output, 0 bytes
5054964 packets dropped
1 minute input rate 2 pkts/sec, 131 bytes/sec
1 minute output rate 0 pkts/sec, 0 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 2 pkts/sec, 108 bytes/sec
5 minute output rate 0 pkts/sec, 0 bytes/sec
5 minute drop rate, 0 pkts/sec
Management-only interface. Blocked 0 through-the-device packets
The following table shows each field description.
Table 2. show interface Fields
|
Field
|
Description
|
|
Interface ID
|
The interface ID.
|
|
“interface_name ”
|
The logical interface name.
If you do not configure a name, the following message appears after the
Hardware line:
Available but not configured via nameif
|
|
is
state
|
The administrative state, as follows:
|
|
Line protocol is state
|
The line status, as follows:
|
|
VLAN identifier
|
For subinterfaces, the VLAN ID.
|
|
Hardware
|
The interface type, maximum bandwidth, delay, duplex, and speed.
When the link is down, the duplex and speed show the configured values. When
the link is up, these fields show the configured values with the actual
settings in parentheses.
|
|
Media-type
|
(Not always shown) Shows the interface media type, such as RJ-45
or SFP.
|
|
message area
|
A message might be displayed in some circumstances. See the
following examples:
-
If you do not configure a name, you see the following message:
Available but not configured via nameif
-
If an interface is a member of a redundant interface, you see
the following message: Active member of Redundant5
|
|
MAC address
|
The interface MAC address.
|
|
Site Specific MAC address
|
For clustering, shows an in-use site-specific MAC address.
|
|
MTU
|
The maximum size, in bytes, of packets allowed on this
interface. If you do not set the interface name, this field shows “MTU not
set.”
|
|
IP address
|
The interface IP address, either static or received from a DHCP
server.
|
|
Subnet mask
|
The subnet mask for the IP address.
|
|
Packets input
|
The number of packets received on this interface.
|
|
Bytes
|
The number of bytes received on this interface.
|
|
No buffer
|
The number of failures from block allocations.
|
|
Received:
|
|
|
Broadcasts
|
The number of broadcasts received.
|
|
Input errors
|
The number of total input errors, including the types listed
below. Other input-related errors can also cause the input error count to
increase, and some datagrams might have more than one error; therefore, this
sum might exceed the number of errors listed for the types below.
|
|
Runts
|
The number of packets that are discarded because they are
smaller than the minimum packet size, which is 64 bytes. Runts are usually
caused by collisions. They might also be caused by poor wiring and electrical
interference.
|
|
Giants
|
The number of packets that are discarded because they exceed the
maximum packet size. For example, any Ethernet packet that is greater than 1518
bytes is considered a giant.
|
|
CRC
|
The number of Cyclical Redundancy Check errors. When a station
sends a frame, it appends a CRC to the end of the frame. This CRC is generated
from an algorithm based on the data in the frame. If the frame is altered
between the source and destination, the system notes that the CRC does not
match. A high number of CRCs is usually the result of collisions or a station
transmitting bad data.
|
|
Frame
|
The number of frame errors. Bad frames include packets with an
incorrect length or bad frame checksums. This error is usually the result of
collisions or a malfunctioning Ethernet device.
|
|
Overrun
|
The number of times that the interface was incapable of handing
received data to a hardware buffer because the input rate exceeded the
interface’s capability to handle the data.
|
|
Ignored
|
This field is not used. The value is always 0.
|
|
Abort
|
This field is not used. The value is always 0.
|
|
L2 decode drops
|
The number of packets dropped because the name is not configured
or a frame with an invalid VLAN id is received. On a standby interface in a
redundant interface configuration, this counter may increase because this
interface has no name configured.
|
|
Packets output
|
The number of packets sent on this interface.
|
|
Bytes
|
The number of bytes sent on this interface.
|
|
Underruns
|
The number of times that the transmitter ran faster than the
interface could handle.
|
|
Output Errors
|
The number of frames not transmitted because the configured
maximum number of collisions was exceeded. This counter should only increment
during heavy network traffic.
|
|
Collisions
|
The number of messages retransmitted due to an Ethernet
collision (single and multiple collisions). This usually occurs on 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 by the output packets.
|
|
Interface resets
|
The number of times an interface has been reset. If an interface
is unable to transmit for three seconds, the system resets the interface to
restart transmission. During this interval, connection state is maintained. An
interface reset can also happen when an interface is looped back or shut down.
|
|
Babbles
|
Unused. (“babble” means that the transmitter has been on the
interface longer than the time taken to transmit the largest frame.)
|
|
Late collisions
|
The number of frames that were not transmitted because a
collision occurred outside the normal collision window. A late collision is a
collision that is detected late in the transmission of the packet. Normally,
these should never happen. When two Ethernet hosts try to talk at once, they
should collide early in the packet and both back off, or the second host should
see that the first one is talking and wait.
If you get a late collision, a device is jumping in and trying to send the packet on the Ethernet while the threat
defense device is partly finished sending the packet. The threat
defense device does not resend the packet, because it may have freed the buffers that held the first part of the packet. This is
not a real problem because networking protocols are designed to cope with collisions by resending packets. However, late collisions
indicate a problem exists in your network. Common problems are large repeated networks and Ethernet networks running beyond
the specification.
|
|
Deferred
|
The number of frames that were deferred before transmission due
to activity on the link.
|
|
input reset drops
|
Counts the number of packets dropped in the RX ring when a reset
occurs.
|
|
output reset drops
|
Counts the number of packets dropped in the TX ring when a reset
occurs.
|
|
Rate limit drops
|
The number of packets dropped if you configured the
interface at non-Gigabit speeds and attempted to transmit more than 10 Mbps or
100 Mbps, depending on configuration..
|
|
Lost carrier
|
The number of times the carrier signal was lost during
transmission.
|
|
No carrier
|
Unused.
|
|
Input queue (curr/max packets):
|
The number of packets in the input queue, the current and the
maximum.
|
|
Hardware
|
The number of packets in the hardware queue.
|
|
Software
|
The number of packets in the software queue. Not available for
Gigabit Ethernet interfaces.
|
|
Output queue (curr/max packets):
|
The number of packets in the output queue, the current and the
maximum.
|
|
Hardware
|
The number of packets in the hardware queue.
|
|
Software
|
The number of packets in the software queue.
|
|
input queue (blocks free curr/low)
|
The curr/low entry indicates the number of current and
all-time-lowest available slots on the interface's Receive (input) descriptor
ring. These are updated by the main CPU, so the all-time-lowest (until the
interface statistics are cleared or the device is reloaded) watermarks are not
highly accurate.
|
|
output queue (blocks free curr/low)
|
The curr/low entry indicates the number of current and
all-time-lowest available slots on the interface's Transmit (output) descriptor
rings. These are updated by the main CPU, so the all-time-lowest (until the
interface statistics are cleared or the device is reloaded) watermarks are not
highly accurate.
|
|
Traffic Statistics:
|
The number of packets received, transmitted, or dropped.
|
|
Packets input
|
The number of packets received and the number of bytes.
|
|
Packets output
|
The number of packets transmitted and the number of bytes.
|
|
Packets dropped
|
The number of packets dropped. Typically this counter increments
for packets dropped on the accelerated security path (ASP), for example, if a
packet is dropped due to an access list deny.
See the
show
asp drop command for reasons for potential drops on an interface.
|
|
1 minute input rate
|
The number of packets received in packets/sec and bytes/sec over
the last minute.
|
|
1 minute output rate
|
The number of packets transmitted in packets/sec and bytes/sec
over the last minute.
|
|
1 minute drop rate
|
The number of packets dropped in packets/sec over the last
minute.
|
|
5 minute input rate
|
The number of packets received in packets/sec and bytes/sec over
the last 5 minutes.
|
|
5 minute output rate
|
The number of packets transmitted in packets/sec and bytes/sec
over the last 5 minutes.
|
|
5 minute drop rate
|
The number of packets dropped in packets/sec over the last 5
minutes.
|
|
Redundancy Information:
|
For redundant interfaces, shows the member physical interfaces.
The active interface has “(Active)” after the interface ID.
If you have not yet assigned members, you see the following
output:
Members unassigned
|
|
Last switchover
|
For redundant interfaces, shows the last time the active
interface failed over to the standby interface.
|
Note
|
The input and output rates in the show interface detail command result can be different from the input and output traffic rates that appear in the interface module of the management center user interface.
The interface module displays the traffic rates according to the values from Snort performance monitoring. Sampling intervals
of snort performance monitoring and the interface statistics are different. This difference in sampling intervals results
in different throughput values in the management center user interface and in the show interface detail command result.
|
The following is sample output from the
show interface
detail command. The following example shows detailed interface
statistics for all interfaces, including the internal interfaces (if present
for your platform) and asymmetrical routing statistics, if enabled:
> show interface detail
Interface GigabitEthernet0/0 "outside", is up, line protocol is up
Hardware is i82546GB rev03, BW 1000 Mbps, DLY 1000 usec
Auto-Duplex(Full-duplex), Auto-Speed(100 Mbps)
MAC address 000b.fcf8.c44e, MTU 1500
IP address 10.86.194.60, subnet mask 255.255.254.0
1330214 packets input, 124580214 bytes, 0 no buffer
Received 1216917 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
9 L2 decode drops
124863 packets output, 86956597 bytes, 0 underruns
0 output errors, 0 collisions
0 late collisions, 0 deferred
input queue (curr/max packets): hardware (0/7)
output queue (curr/max packets): hardware (0/13)
Traffic Statistics for "outside":
1330201 packets input, 99995120 bytes
124863 packets output, 84651382 bytes
525233 packets dropped
Queue Stats:
RX[00]: 6599382 packets, 697116251 bytes, 0 overrun
Blocks free curr/low: 512/432
RX[01]: 924929 packets, 258924873 bytes, 0 overrun
Blocks free curr/low: 512/483
RX[02]: 832587 packets, 245912949 bytes, 0 overrun
Blocks free curr/low: 512/479
RX[03]: 1581947 packets, 327352778 bytes, 0 overrun
Blocks free curr/low: 512/466
RX[04]: 1248125 packets, 304273571 bytes, 0 overrun
Blocks free curr/low: 512/491
RX[05]: 1040026 packets, 420338105 bytes, 0 overrun
Blocks free curr/low: 512/476
RX[06]: 995323 packets, 343474141 bytes, 0 overrun
Blocks free curr/low: 512/433
RX[07]: 73018771 packets, 46411510982 bytes, 0 overrun
Blocks free curr/low: 512/463
RX[08]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[09]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[10]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[11]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[12]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[13]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[14]: 94177 packets, 17778198 bytes, 0 overrun
Blocks free curr/low: 512/505
RX[256]: 6 packets, 96 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[257]: 180 packets, 3332 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[258]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[259]: 9 packets, 144 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[260]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[261]: 6 packets, 96 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[262]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[263]: 4 packets, 64 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[288]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[289]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[290]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[291]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[292]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[293]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[294]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
RX[295]: 0 packets, 0 bytes, 0 overrun
Blocks free curr/low: 512/512
TX[00]: 3258599 packets, 860813811 bytes, 0 underruns
Blocks free curr/low: 511/388
TX[01]: 891279 packets, 238071978 bytes, 0 underruns
Blocks free curr/low: 511/405
TX[02]: 787368 packets, 233492817 bytes, 0 underruns
Blocks free curr/low: 511/409
TX[03]: 1407442 packets, 294192127 bytes, 0 underruns
Blocks free curr/low: 511/423
TX[04]: 1143794 packets, 266269203 bytes, 0 underruns
Blocks free curr/low: 511/433
TX[05]: 1813341 packets, 1343723097 bytes, 0 underruns
Blocks free curr/low: 511/413
TX[06]: 745612 packets, 178752603 bytes, 0 underruns
Blocks free curr/low: 511/389
TX[07]: 498701 packets, 140487728 bytes, 0 underruns
Blocks free curr/low: 511/382
TX[08]: 107232 packets, 66899140 bytes, 0 underruns
Blocks free curr/low: 511/419
TX[09]: 108350 packets, 68658558 bytes, 0 underruns
Blocks free curr/low: 511/441
TX[10]: 98761 packets, 64801332 bytes, 0 underruns
Blocks free curr/low: 511/438
[...]
TX[254]: 0 packets, 0 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[255]: 0 packets, 0 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[256]: 123 packets, 3444 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[257]: 270048 packets, 2420741524 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[258]: 0 packets, 0 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[259]: 9 packets, 576 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[260]: 0 packets, 0 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[261]: 6 packets, 384 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[262]: 0 packets, 0 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[263]: 4 packets, 256 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[288]: 0 packets, 0 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[289]: 0 packets, 0 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[290]: 0 packets, 0 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[291]: 0 packets, 0 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[292]: 0 packets, 0 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[293]: 0 packets, 0 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[294]: 0 packets, 0 bytes, 0 underruns
Blocks free curr/low: 511/512
TX[295]: 0 packets, 0 bytes, 0 underruns
Blocks free curr/low: 511/512
Control Point Interface States:
Interface number is 1
Interface config status is active
Interface state is active
Interface Internal-Data0/0 "", is up, line protocol is up
Hardware is i82547GI rev00, BW 1000 Mbps, DLY 1000 usec
(Full-duplex), (1000 Mbps)
MAC address 0000.0001.0002, MTU not set
IP address unassigned
6 packets input, 1094 bytes, 0 no buffer
Received 6 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 L2 decode drops, 0 demux drops
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions
0 late collisions, 0 deferred
input queue (curr/max packets): hardware (0/2) software (0/0)
output queue (curr/max packets): hardware (0/0) software (0/0)
Control Point Interface States:
Interface number is unassigned
Interface Internal-Data0/1 "nlp_int_tap", is up, line protocol is up
Hardware is en_vtun rev00, BW Unknown Speed-Capability, DLY 1000 usec
(Full-duplex), (1000 Mbps)
Input flow control is unsupported, output flow control is unsupported
MAC address 0000.0100.0001, MTU 1500
IP address 169.254.1.1, subnet mask 255.255.255.248
37 packets input, 2822 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
0 L2 decode drops
5 packets output, 370 bytes, 0 underruns
0 pause output, 0 resume output
0 output errors, 0 collisions, 0 interface resets
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (blocks free curr/low): hardware (0/0)
output queue (blocks free curr/low): hardware (0/0)
Traffic Statistics for "nlp_int_tap":
37 packets input, 2304 bytes
5 packets output, 300 bytes
37 packets dropped
1 minute input rate 0 pkts/sec, 0 bytes/sec
1 minute output rate 0 pkts/sec, 0 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 0 pkts/sec, 0 bytes/sec
5 minute output rate 0 pkts/sec, 0 bytes/sec
5 minute drop rate, 0 pkts/sec
Control Point Interface States:
Interface number is 14
Interface config status is active
Interface state is active
[...]
The following table explains the additional fields shown by the
show interface
detail command.
Table 3. show interface detail Fields
|
Field
|
Description
|
|
Demux drops
|
(On Internal-Data interface only) The number of packets dropped because the threat
defense device was unable to demultiplex packets from other interfaces.
|
| Internal Data Interfaces |
The interfaces on the data plane (system support diagnostic-cli) are the Internal-Data0/0 and Internal-Data0/1.
Each of these interfaces have a buffer. One of the device threads read from the buffer and move packets into RX Rings. For
example, in the 4120 device, the total number of rings are 23 (From 00 to 22), where, RX Ring 16 and 17 are reserved for OSPF.
Similarly, based on the device models, some rings are reserved for failover and CCL packets.
These rings are packet stacks that ensure that packets from the same flow are in the same order; packets with the same 5 tuple
(based on source/destination IP) will always be on the same RX Ring.
|
|
Control Point Interface States:
|
|
|
Interface number
|
A number used for debugging that indicates in what order this
interface was created, starting with 0.
|
|
Interface config status
|
The administrative state, as follows:
|
|
Interface state
|
The actual state of the interface. In most cases, this state matches the config status above. If you configure high availability,
it is possible there can be a mismatch because the threat
defense device brings the interfaces up or down as needed.
|
|
Asymmetrical Routing Statistics:
|
|
|
Received X1 packets
|
Number of ASR packets received on this interface.
|
|
Transmitted X2 packets
|
Number of ASR packets sent on this interfaces.
|
|
Dropped X3 packets
|
Number of ASR packets dropped on this interface. The packets
might be dropped if the interface is down when trying to forward the packet.
|