To review general interface statistics:
The screen displays by default in the right-hand pane.
| Name | Displays the name of the interface ge1, up 1, etc. |
| Interface MAC Address | Displays the MAC address of the interface. |
| IP Address | IP address of the interface. |
| IP Address Type | Displays the IP address type, either IPv4 or IPv6. |
| Secondary IPs | Displays a list of secondary IP resources assigned to this interface. |
| Hardware Type | Displays the networking technology. |
| Index | Displays the unique numerical identifier for the interface. |
| Access VLAN | Displays the tag assigned to the native VLAN. |
| Native VLAN | The native VLAN allows an Ethernet device to associate untagged frames to a VLAN when no 802.1Q frame is included in the frame. Additionally, the native VLAN is the VLAN untagged traffic is directed over when using a port in trunk mode. |
| Tagged Native VLAN | When a frame is tagged, the 12 bit frame VLAN ID is added to the 802.1Q header so upstream Ethernet devices know which VLAN ID the frame belongs to. The device reads the 12 bit VLAN ID and forwards the frame to the appropriate VLAN. When a frame is received with no 802.1Q header, the upstream device classifies the frame using the default or native VLAN assigned to the Trunk port. A native VLAN allows an Ethernet device to associate untagged frames to a VLAN when no 802.1Q frame is included in the frame. |
| Access Setting | Displays the VLAN mode as either Access or Trunk. |
| Allowed VLANs | Displays the list of allowed virtual interface(s) on this interface. |
| Administrative Status | Displays whether the interface is currently UP or DOWN. |
| Operational Status | Lists whether the selected interface is currently UP (operational) or DOWN. |
| IPv6 Mode | Lists the current IPv6 mode utilized. |
| IPv6 MTU | Lists the IPv6 formatted largest packet size that can be sent over this interface. |
| Media Type | Displays the physical connection type of
the interface. Medium types include:
|
| Protocol | Displays the routing protocol used by the interface. |
| MTU | Displays the maximum transmission unit (MTU) setting configured on the interface. The MTU value represents the largest packet size that can be sent over a link. 10/100 Ethernet ports have a maximum setting of 1500. |
| Mode | The mode can be either:
|
| Metric | Displays the metric associated with the interface's route. |
| Maximum Speed | Displays the maximum speed the interface uses to transmit or receive data. |
| Admin Speed | Displays the speed the port can transmit or receive. This value can be either 10, 100, 1000 or Auto. This value is the maximum port speed in Mbps. Auto indicates the speed is negotiated between connected devices. |
| Operator Speed | Displays the current speed of data transmitted and received over the interface. |
| Admin Duplex Setting | Displays the administrator's duplex setting. |
| Current Duplex Setting | Displays the interface as either half duplex, full duplex or unknown. |
| Good Octets Sent | Displays the number of octets (bytes) with no errors sent by the interface. |
| Good Octets Received | Displays the number of octets (bytes) with no errors received by the interface. |
| Good Packets Sent | Displays the number of good packets transmitted. |
| Good Packets Received | Displays the number of good packets received. |
| Mcast Pkts Sent | Displays the number of multicast packets sent through the interface. |
| Mcast Pkts Received | Displays the number of multicast packets received through the interface. |
| Ucast Pkts Sent | Displays the number of unicast packets sent through the interface. |
| Ucast Pkts Received | Displays the number of unicast packets received through the interface. |
| Bcast Pkts Sent | Displays the number of broadcast packets sent through the interface. |
| Bcast Pkts Received | Displays the number of broadcast packets received through the interface. |
| Packet Fragments | Displays the number of packet fragments transmitted or received through the interface. |
| Jabber Pkts | Displays the number of packets transmitted through the interface larger than the MTU. |
| Bad Pkts Received | Displays the number of bad packets received through the interface. |
| Collisions | Displays the number of collisions over the selected interface. |
| Late Collisions | Displays the number of late collisions. Late collisions occur after the first 64 octets of data has been sent. Late collisions are not normal, and usually the result of out of specification cabling or a malfunctioning device. |
| Excessive Collisions | Displays the number of excessive collisions. Excessive collisions occur when the traffic load increases to the point a single Ethernet network cannot handle it efficiently. |
| Drop Events | Displays the number of dropped packets transmitted or received through the interface. |
| Tx Undersize Pkts | Displays the number of undersized packets transmitted through the interface. |
| Oversize Pkts | Displays the number of oversized packets transmitted through the interface. |
| MAC Transmit Error | Displays the number of failed transmits due to an internal MAC sublayer error (that‘s not a late collision), due to excessive collisions or a carrier sense error. |
| MAC Receive Error | Displays the number of received packets that failed due to an internal MAC sublayer (that‘s not a late collision), an excessive number of collisions or a carrier sense error. |
| Bad CRC | Displays the CRC error. The CRC is the 4 byte field at the end of every frame. The receiving station uses it to interpret if the frame is valid. If the CRC value computed by the interface does not match the value at the end of frame, it is considered as a bad CRC. |
| Rx Frame Errors | Displays the number of frame errors received at the interface. A frame error occurs when data is received, but not in an expected format. |
| Rx Length Errors | Displays the number of length errors received at the interface. Length errors are generated when the received frame length was either less or over the Ethernet standard. |
| Rx FIFO Errors | Displays the number of First-in First-out (FIFO) errors received at the interface. FIFO queueing is an algorithm that involves buffering and forwarding of packets in the order of arrival. FIFO entails no priority. There is only one queue, and all packets are treated equally. An increase in FIFO errors indicates a probable hardware malfunction. |
| Rx Missed Errors | Displays the number of missed packets. Packets are missed when the hardware received FIFO has insufficient space to store an incoming packet. |
| Rx Over Errors | Displays the number of overflow errors received. Overflows occur when a packet size exceeds the allocated buffer size. |
| Tx Errors | Displays the number of packets with errors transmitted on the interface. |
| Tx Dropped | Displays the number of transmitted packets dropped from the interface. |
| Tx Aborted Errors | Displays the number of packets aborted on the interface because a clear-to-send request was not detected. |
| Tx Carrier Errors | Displays the number of carrier errors on the interface. This generally indicates bad Ethernet hardware or bad cabling. |
| Tx FIFO Errors | Displays the number of FIFO errors transmitted at the interface. FIFO queueing is an algorithm that involves the buffering and forwarding of packets in the order of arrival. FIFO uses no priority. There is only one queue, and all packets are treated equally. An increase in the number of FIFO errors indicates a probable hardware malfunction. |
| Tx Heartbeat Errors | Displays the number of heartbeat errors. This generally indicates a software crash, or packets stuck in an endless loop. |
| Tx Window Errors | Displays the number of window errors transmitted. TCP uses a sliding window flow control protocol. In each TCP segment, the receiver specifies the amount of additional received data (in bytes) the receiver is willing to buffer for the connection. The sending host can send only up to that amount. If the sending host transmits more data before receiving an acknowledgment, it constitutes a window error. |