show interface

Syntax

show interface <INTERFACE-NAME> [queues] [vsx-peer]

Description

Shows interface-level configuration, including any QoS settings that may override the global settings on the switch.

NOTE:

For every layer 3 packet transmitted on a switch queue, an extra three bytes are added to the value of Tx Bytes (due to the inclusion of an internal routing packet header). To show layer 3 statistics without this addition, enable layer 3 counters on an interface, and execute the command show interface. For example: 

switch(config)# interface 1/1/1
switch(config-if)# l3-counters
switch(config-if)# exit
switch# show interface 1/1/1

Command context

Operator (>) or Manager (#)

Parameters

<INTERFACE-NAME>

Specifies the name of an interface on the switch. Some switches (such as the Aruba 8400 Switch Series), use the format member/slot/port (for example, 1/1/1). Other switches use slot/port (for example, 1/1).

queues

Show queue statistics.

[vsx-peer]

Shows the output from the VSX peer switch. If the switches do not have the VSX configuration or the ISL is down, the output from the VSX peer switch is not displayed.

Authority

Operators or Administrators. Users without administrator authority can execute this command from the operator context (>) only.

Usage

Statistics include:

  • Tx Bytes: Total bytes transmitted. The byte count may include packet headers and internal metadata that are removed before the packet is transmitted. Packet headers added when the packet is transmitted may not be included.
  • Tx Packets: Total packets transmitted.
  • Tx Errors: Shows the amount of traffic dropped on an egress interface before being sent. When traffic cannot be forwarded out an egress interface, it backs up on ingress. The more servicing assigned to a queue by a schedule profile, the less likely traffic destined for that queue will back up and be dropped. Tx Errors shows the sum of packets that were dropped across all line modules (due to insufficient capacity) by the ingress Virtual Output Queues (VOQs) destined for the egress port. As the counts are read separately from each line module, the sum is not an instantaneous snapshot.
  • Tx Byte Depth: Largest byte depth (or high watermark) found on any ingress line module Virtual Output Queue (VOQ) destined for the egress port.

Examples

Showing settings for interface 1/1/5: 

switch# show interface 5
Interface 5 is down (Administratively down)
 Admin state is down
 State information: admin_down
 Hardware: Ethernet, MAC Address: aa:55:aa:55:00:29
 MTU 1500
 Full-duplex
 qos trust cos
 qos schedule-profile default
 qos dscp override 46
 Speed 0 Mb/s
 Auto-Negotiation is turned on
 Input flow-control is off, output flow-control is off

Showing queue statistics for interface 1/1/5: 

switch# show interface 1/1/5 queues
Interface 1/1/5 is up
 Admin state is up
               Tx Bytes      Tx Packets       Tx Errors         Tx Byte Depth
 Q0        157113373520      1890863919               0                  1362
 Q1        233312143017      2808451320              18                 65550
 Q2        156814056423      1887257650               0                  1392
 Q3        157441358980      1894815504               0                  1374
 Q4        157700809294      1897941370               0                  1362
 Q5        157872849381      1900014146               0                  1392
 Q6        183486049854      2208268429               0                  4398
 Q7        231607534141      2787913734               0                 65544