Skip to main content
Cisco SD-WAN
Product Documentation
Viptela Documentation

show interface

show interface—Display information about IPv4 interfaces on a Viptela device.

Command Syntax

show interface [detail] [interface-name] [vpn vpn-id]


Display standard information about the interfaces on the Viptela device.
Detailed Interface Information
Display detailed information about the interfaces (available only on vEdge routers).
Specific Interface
Display information about a specific interface.
On vEdge routers, interface-name can be a physical interface (geslot/port), a subinterface or VLAN (geslot/port.vlan-number), the interface corresponding to the system IP address (system), the management interface (typically, eth0), or a GRE tunnel (grenumber).
On vSmart controllers, interface-name can be an interface (ethnumber) or the interface corresponding to the system IP address (system).
Specific VPN
vpn vpn-id
Display information about interfaces in a specific VPN.

Output Fields

The following are the fields in the show interface command output:

Whether the interface is operating in duplex or simplex mode. This field does not apply to virtual interfaces, such as GRE, IRB, loopback, and system interfaces.
Encapsulation Type
Encapsulation configured on the interface with the encapsulation command.
Hardware Address
MAC address of the interface.
If Admin Status
Administrative status of the interface; that is, its status as a result of the interface's configuration. The status can be either Up or Down. By default, interfaces are administratively down, and you must include the no shutdown command in the interface's configuration to bring the interface up. An interface that is both administratively and operationally up is able to transmit and receive traffic. To bring down an interface administratively, include the shutdown command in the interface's configuration.
If Oper Status
Operational status of the interface; that is, its status as a result of operational factors. The status can be either Up or Down. An interface can be operationally up if it is Interface is administratively up, the interface link layer state is up, and the interface initialization has completed. An interface that is both administratively and operationally up is able to transmit and receive traffic. If the operational status is down, the interface is functionally down and is not able to transmit or receive any traffic.
MTU size for packets being send over the interface.
Port Type
Describes the port's function from the point of view of the overlay network. It can be one of the following:
loopback—Loopback interface. The device's system IP address is listed as a loopback interface.
service—Interface for data traffic.
transport—Interface running a DTLS control session.
RX Packets and TX Packets
For GRE interfaces, these fields show counts of the data traffic received and transmitted on GRE tunnels. To display GRE keepalive traffic counts, use the show tunnel gre-keepalives command. To display all GRE tunnel statistics, use the show tunnel statistics gre command.
Speed of the interface, in megabits per second (Mbps). This field does not apply to virtual interfaces, such as GRE, IRB, loopback, and system interfaces.
TCP MSS Adjust
Maximum segment size (MSS) of TCP SYN packets on the interface. For more information see tcp-mss-adjust.
How long the interface has been up, in days, hours, minutes, and seconds.

The following are the additional fields included in the show interface detail command output:

  • addr-type—Type of address configured on the interface, either IPv4 or IPv6, and how the address is configured, either dynamic or static.
  • allow-service—Services allowed on the interface. For more information, see allow-service.
  • arp-add-fails—Packets for which an ARP entry in the forwarding plane could not be created.
  • bad-label—Packets dropped because of an invalid next-hop label record for a destination.
  • cpu-policer-drops—Packets destined to the control plane dropped because they exceeded the CPU policer limit.
  • dot1x-rx-pkts—802.1X packets received on the interface.
  • dot1x-tx-pkts—802.1X packets transmitted on the interface.
  • filter-drops—Packets dropped because of an implicit or explicit localized data policy (ACL) filter configuration.
  • icmp-redirect-rx-drops—
  • icmp-redirect-tx-drops—ICMP redirect packets dropped by the interface.
  • if-addr, ip-address/broadcast-addr/secondary—Interface's primary unicast and broadcast addresses, and interface's secondary address, if one is configured.
  • ifindex—Interface's SNMP index number.
  • if-tracker-status—Whether interface tracking is enabled. For more information, see tracker.
  • interface-disabled—Incoming packets dropped because the interface port is not enabled.
  • mirror-drops—Fragmented packets that are being mirrored to a destination.
  • route-lookup-fail—Packets that could not be forwarded because no route is present in the forwarding table (FIB).
  • rx-arp-non-local-drops—Received ARP packets that do not match the destination IP address of any local IP address.
  • rx-arp-replies—Received ARP replies
  • rx-arp-rate-limit-drops—Currently, the software does not increment this counter.
  • rx-arp-reply-drops—Currently, the software does not increment this counter.
  • rx-arp-request-fail—Packets that could not be received because there is not corresponding MAC address.
  • rx-arp-requests—Received ARP requests.
  • rx-broadcast-pkts—Received broadcast packets.
  • rx-drops—Received packets that were dropped.
  • rx-errors—Received packets that were errored.
  • rx-ip-ttl-expired—Received IP packets whose time-to-live value expired.
  • rx-multicast-pkts—Received multicast packets.
  • rx-non-ip-drops—Received packets other than IP or ARP packets that the interface dropped.
  • rx-oversize-errors—Currently, the software does not increment this counter.
  • rx-octets—Number of octets in received packets.
  • rx-packets—Received packets.
  • rx-policer-drops—Incoming packets dropped because of the rate exceeded the configured ingress policer rate.
  • rx-policer-remark—Received packets remarked as the result of a policer.
  • rx-pps—Receipt rate of packets, in packets per second.
  • rx-replay-integrity-drops—Received packets dropped because the IPsec packet arrive outside of the anti-replay window or because the integrity check performed by ESP or AH failed. To view the configured anti-replay window, use the show security-info command. To modify the anti-replay window size, use the security ipsec replay-window configuration command.
  • rx-undersize-errors—Currently, the software does not increment this counter.
  • rx-wred-drops—Incoming packets dropped because of a RED drop profile associated with an interface queue. To configure a RED drop profile, use the drops option when configuring a QoS scheduler.
  • shaping-rate—Traffic rate on the interface if rate is configured with the shaping-rate command to be less than the maximum rate.
  • split-horizon-drops—BGP packets dropped as a result of split-horizon determination that the router was advertising a route back on the same interface from which it was learned.
  • tx-arp-rate-limit-drops—Number of ARP packets generated by the forwarding plane that exceed the CPU rate limit, which is 16 ARP packets sent towards the CPU and 128 ARP packets send towards physical ports.
  • tx-broadcast-pkts—Transmission rate of broadcast packets, in packets per second.
  • tx-drops—Transmitted packets that were dropped.
  • tx-errors—Transmitted packets that were errored.
  • tx-icmp-mirrored-drops—ICMP redirect packets dropped by the system.
  • tx-icmp-policer-drops—ICMP packets generated by the system that were dropped because of ICMP policer limits.
  • tx-multicast-pkts—Transmitted multicast packets.
  • tx-no-arp-drops—Packets dropped in the forwarding plane because of a missing ARP entry for a destination IP address.
  • tx-octets—Number of octets in transmitted packets.

Example Output

vEdge# show interface
                                        IF      IF                                                                TCP                                   
                AF                      ADMIN   OPER    ENCAP                                      SPEED          MSS                 RX       TX       
0    ge0/0      ipv4     Up      Up      null   transport  1500  00:0c:29:7d:1e:fe  1000   full    1420    0:19:51:22  795641   857981   
0    ge0/1      ipv4     Up      Up      null   service    1500  00:0c:29:7d:1e:08  1000   full    1420    0:19:42:43  5754     10       
0    ge0/2      ipv4  -                 Down    Up      null   service    1500  00:0c:29:7d:1e:12  1000   full    1420    0:19:51:27  5752     0        
0    ge0/3      ipv4     Up      Up      null   service    1500  00:0c:29:7d:1e:1c  1000   full    1420    0:19:42:43  5763     9        
0    ge0/6      ipv4      Up      Up      null   service    1500  00:0c:29:7d:1e:3a  1000   full    1420    0:19:42:43  5750     10       
0    ge0/7      ipv4    Up      Up      null   service    1500  00:0c:29:7d:1e:44  1000   full    1420    0:19:48:22  7469     1346     
0    system     ipv4  Up      Up      null   loopback   1500  00:00:00:00:00:00  0      full    1420    0:19:42:19  0        0        
1    ge0/4      ipv4    Up      Up      null   service    1500  00:0c:29:7d:1e:26  1000   full    1420    0:19:42:40  13263    7653     
1    ge0/5      ipv4      Up      Up      null   service    1500  00:0c:29:7d:1e:30  1000   full    1420    0:19:42:40  5730     8        
512  eth0       ipv4      Up      Up      null   service    1500  00:50:56:00:01:0f  0      full    0       0:19:51:22  47033    31894
vEdge# show interface detail ge0/0
interface vpn 0 interface ge0/0 af-type ipv4
 if-admin-status         Up
 if-oper-status          Up
  secondary      false
 encap-type              null
 port-type               transport
 ifindex                 1
 mtu                     1500
 hwaddr                  00:0c:29:7d:1e:fe
 speed-mbps              1000
 duplex                  full
 auto-neg                false
 pause-type              ""
 tcp-mss-adjust          1420
 uptime                  0:19:51:44
 allow-service           dhcp,dns,icmp
 rx-packets              795901
 rx-octets               146499972
 rx-errors               0
 rx-drops                2920
 tx-packets              858263
 tx-octets               147918066
 tx-errors               0
 tx-drops                0
 rx-pps                  11
 rx-kbps                 16
 tx-pps                  12
 tx-kbps                 17
 rx-arp-requests         44
 tx-arp-replies          52
 tx-arp-requests         2139
 rx-arp-replies          2085
 arp-add-fails           2
 rx-arp-reply-drops      0
 rx-arp-rate-limit-drops 0
 tx-arp-rate-limit-drops 0
 rx-arp-non-local-drops  13
 tx-arp-request-fail     0
 tx-no-arp-drops         0
 rx-ip-ttl-expired       0
 interface-disabled      0
 rx-policer-drops        0
 rx-non-ip-drops         0
 filter-drops            0
 mirror-drops            0
 cpu-policer-drops       0
 tx-icmp-policer-drops   0
 tx-icmp-mirrored-drops  0
 split-horizon-drops     0
 route-lookup-fail       0
 bad-label               0
 rx-multicast-pkts       7511
 rx-broadcast-pkts       2997
 tx-multicast-pkts       7437
 tx-broadcast-pkts       88
 num-flaps               1
 shaping-rate            0
 dot1x-tx-pkts           0
 dot1x-rx-pkts           0
 rx-policer-remark       0

Release Information

Command introduced in Viptela Software Release 14.1.

  • Was this article helpful?