Port CSV File Description (and KPI if applicable)
Col. No. | Field Name | Field Description | Units/Values | Examples |
|---|---|---|---|---|
1 | PORT Data Type | Data type | This value is always PORT. | PORT |
2 | Date | Date and time at the beginning of the period | YYYY-MM-DD HH:MM:SS±hh:mm YYYY-MM-DD: Date HH:MM:SS: Local Time hh:mm: UTC Offset + DST | 2014-09-15 10:31:00-04:00 |
3 | System | System name, as defined by DNS name in the unit | By default, this value is the serial number. | G274-0010 |
4 | Firmware Version | Current firmware version | PFID_A.B.C.D_build PFID: Product Family ID (AEN, AMO_10GE, etc.) A.B.C.D: Release number build: build number | AMT_6.4.1.2_35204 |
5 | Hardware Version | Hardware assembly version of unit | 500-032-01 | |
6 | Serial Number | Serial number of unit. Unique identifier assigned by the manufacturer. | Format: ANNN-NNNN | G274-0010 |
7 | Model | For more information, please refer to Product Model Information. | ||
8 | Connector Name | The port’s connector name | Platform-dependent. Examples: RJ45-A, SFP-B, SFP-1, etc. | SFP-1 |
9 | Port Name | The name that identifies the port | Default port names are platform-dependent. May also be user-defined (up to 17 alphanumeric characters). | PORT-1 |
10 | MAC Address | MAC address of the port | 00:15:AD:xx:yy:zz | 00:15:AD:11:A5:F9 |
11 | State | State of the port | enabled, disabled | enabled |
12 | Configured Speed | Configured port speed | 10Mbps, 100Mbps, 1Gbps or 10Gbps (depending on the platform) | 1Gbps |
13 | MTU | Configured Maximum Transmit Unit | 64 to 10240 | 2000 |
14 | MDI Mode | Media Dependent Interface mode | Auto, MDI, MDIX | Auto |
15 | Link Status | Link status | up, down | up |
16 | Link Speed | Actual link speed | 10Mbps, 100Mbps, 1Gbps or 10Gbps (depending on the platform) | 1Gbps |
17 | Interval | Configured reference period | 1 to 60 minutes | 1 |
18 | Duration | Actual duration of the period | 60 to 3600 seconds | 60 |
19 | Period | Period number (sequential) | 1207 | |
20 | TX Packets (KPI) | Count of the total number of frames/packets (both good and bad) transmitted by the port. Bad frames include normal collisions, late collisions and FIFO underflows. | packets (frames) | 1413380 |
21 | TX Errors (KPI) | Number of transmission errors | 0 | |
22 | TX Bytes Good (KPI) | Count of the total number of bytes transmitted by the port in good frames. The count includes the four FCS bytes, but does not include the preamble or SFD bytes. A good frame is one that has been transmitted successfully (not aborted) with a valid FCS. It is assumed that all transmitted frames are properly sized: from 64 bytes (after any padding) up to the maximum size | bytes | 1104251214 |
23 | TX Bytes Total (KPI) | Count of the total number of frames/packets (both good and bad) transmitted by the port. Bad frames include normal collisions, late collisions and FIFO underflows. | bytes | 1104251214 |
24 | TX Unicast Packets (KPI) | Count of the good (not dropped and having a valid FCS) unicast frames transmitted by this port. Unicast frames are identified by having a 0 in the least significant bit of the first byte of the destination address (the first bit transmitted is a 0). | packets (frames) | 1413318 |
25 | TX Multicast Packets (KPI) | Count of the good (not dropped and having a valid FCS) multicast frames transmitted by this port. Multicast frames are identified by having a 1 in the least significant bit of the first byte of the destination address (the first bit transmitted is a 1). Broadcast frames are not included in this count. | packets (frames) | 62 |
26 | TX Broadcast Packets (KPI) | Count of the good (not dropped and having a valid FCS) broadcast frames transmitted by this port. Broadcast frames are identified by a destination address of all 1s. | packets (frames) | 0 |
27 | TX Pause Frames (KPI) | Count of the good (not dropped and having a valid FCS) flow control pause frames transmitted by this port. Flow control pause frames are identified by an Ethertype of 8808h and an OpCode of 00-01. | packets (frames) | 0 |
28 | TX Tagged Frames (KPI) | Count of the good (not dropped and having a valid FCS) VLAN frames transmitted by this port. VLAN frames are identified by a type field equal to 8100h, 88A8h or 9100h, set in the outer VLAN tag. | packets (frames) | 1403908 |
29 | TX CRC Errors (KPI) | Count of the transmitted frames with a bad non-appended FCS field. This count does not include frames with a bad FCS due to a FIFO underflow. | packets (frames) | 0 |
30 | TX Deferred (KPI) | Count of the number of frames that were deferred on the first transmit attempt due to the medium being busy. Frames with subsequent deferrals (for instance, after a collision backoff) are not counted. Whether or not the frame is eventually transmitted successfully is irrelevant to this counter. Frames dropped due to excess deferral during the initial transmit attempt are not counted. | packets (frames) | 0 |
31 | TX Excessive Deferrals (KPI) | Count of the number of frames dropped by this port due to excessive deferral. The deferral time starts at the beginning of each transmission attempt and ends when the transmission starts (regardless of collisions). The deferral is excessive if more than 3036 byte times have passed without the transmission starting. | packets (frames) | 0 |
32 | TX Single Collisions (KPI) | Count of the number of times a frame is successfully transmitted from this port after experiencing a single collision. This count does not include erroneous (dropped) frames. | packets (frames) | 0 |
33 | TX Multiple Collisions (KPI) | Count of the number of times a frame is successfully transmitted from this port after experiencing multiple collisions. This count does not include erroneous (dropped) frames or frames dropped due to excess collisions. | packets (frames) | 0 |
34 | TX Excessive Collisions (KPI) | Count of the number of frames dropped by this port due to excess collisions (number of collisions equals MaxRetry+1). This count does not include frames dropped due to FIFO underflow or late collisions (even if the late collision is also an excessive collision). | packets (frames) | 0 |
35 | TX Late Collisions (KPI) | Count of the number of frames dropped by this port due to late collisions. A late collision is a collision that occurs after the collision window delay (normally 512-bit times). The collision window time is measured from the rising edge of TX_EN to COL asserted at the MII interface. This count does not include frames dropped due to FIFO underflow. Late collisions are not retried. | packets (frames) | 0 |
36 | TX Normal Collisions (KPI) | Count of the total number of normal collisions that occurred on this port during all transmission attempts. FIFO underflows, late collisions and collisions that occur while this port is not attempting to transmit are not counted. This count does not include collisions during half-duplex back pressure. | packets (frames) | 0 |
37 | TX FIFO Errors (KPI) | Count of the number of packets dropped by this port due to an underflow in the transmit FIFO. When an underflow is detected, transmission is immediately aborted after sending a known bad (inverted) FCS sequence. The FIFO underflow error takes precedence over all other errors if this counter is incremented; consequently, none of the other frame type counters is incremented. | packets (frames) | 0 |
38 | TX Packets 64 (KPI) | The total number of frames (good and bad) transmitted by this port that were exactly 64 bytes in length (excluding the preamble and SFD, but including the FCS). | packets (frames) | 702 |
39 | TX Packets 65-127 (KPI) | The total number of frames (good and bad) transmitted by this port in the range of 65-127 bytes. This frame length value excludes the preamble and SFD, but includes the FCS. | packets (frames) | 44446 |
40 | TX Packets 128-255 (KPI) | The total number of frames (good and bad) transmitted by this port in the range of 128-255 bytes. This frame length value excludes the preamble and SFD, but includes the FCS. | packets (frames) | 112160 |
41 | TX Packets 256-511 (KPI) | The total number of frames (good and bad) transmitted by this port in the range of 256-511 bytes. This frame length value excludes the preamble and SFD, but includes the FCS. | packets (frames) | 262309 |
42 | TX Packets 512-1023 (KPI) | The total number of frames (good and bad) transmitted by this port in the range of 512-1023 bytes. This frame length value excludes the preamble and SFD, but includes the FCS. | packets (frames) | 534424 |
43 | TX Packets 1024-1518 (KPI) | The total number of frames (good and bad) transmitted by this port in the range of 1024-1518 bytes. This frame length value excludes the preamble and SFD, but includes the FCS. | packets (frames) | 459339 |
44 | TX Packets 1519-2047 (KPI) | The total number of frames (good and bad) transmitted by this port in the range of 1519-2047 bytes. This frame length value excludes the preamble and SFD, but includes the FCS. | packets (frames) | 0 |
45 | TX Packets 2048-4095 (KPI) | The total number of frames (good and bad) transmitted by this port in the range of 2048-4095 bytes. This frame length value excludes the preamble and SFD, but includes the FCS. | packets (frames) | 0 |
46 | TX Packets 4096-8191 (KPI) | The total number of frames (good and bad) transmitted by this port in the range of 4096-8191 bytes. This frame length value excludes the preamble and SFD, but includes the FCS. | packets (frames) | 0 |
47 | TX Packets 8192 and More (KPI) | The total number of frames (good and bad) transmitted by this port in the range of 8192 bytes or more. This frame length value excludes the preamble and SFD, but includes the FCS. | packets (frames) | 0 |
48 | TX Large Packets (KPI) | The total number of large frames transmitted by this port. The size of large frames is defined via the Large Packet Threshold parameter. | packets (frames) | 0 |
49 | TX L1 Bandwidth Utilization (%) (KPI) | The bandwidth currently used for the transmission of outgoing traffic on the selected port, expressed as a percentage of the line rate. Notes: Bandwidth utilization statistics are provided with one-second granularity for both Layer 1 and Layer 2. However, the value expressed as a percentage of the line rate is available for Layer 1 only. Statistics will be accurate to ±1% at data rates above 100 Mbps. | % | 15.1 |
50 | TX L1 Rate (Mbps) (KPI) | The rate at which outgoing traffic is currently circulating in Layer 1 for the selected port, expressed in Mbps. | Mbps | 151 |
51 | TX L2 Rate (Mbps) (KPI) | The rate at which outgoing traffic is currently circulating in Layer 2 for the selected port, expressed in Mbps. | Mbps | 147.23 |
52 | RX Packets (KPI) | Count of the total number of frames/packets (both good and bad) received by the port. Bad frames include short frames (less than 64 bytes), long frames (greater than the port's configured MTU), frames with bad FCS, frames with PHY errors and frames with received FIFO errors. | packets (frames) | 1873470 |
53 | RX Errors (KPI) | Number of errors received | packets (frames) | 0 |
54 | RX Bytes Good (KPI) | Count of the total number of bytes received by the port in good frames. The count includes the four FCS bytes but does not include the preamble or SFD bytes. A good frame is one that has been received successfully (not aborted) with a valid FCS. It is assumed that all received frames are properly sized: from 64 bytes (after any padding) up to the maximum size. | bytes | 1462549010 |
55 | RX Bytes Total (KPI) | Count of the total number of frames/packets (both good and bad) received by the port. Bad frames include short frames (less than 64 bytes), long frames (greater than the port's configured MTU), frames with bad FCS, frames with PHY errors and frames with receive FIFO errors. | bytes | 1462549010 |
56 | RX Short Ok (KPI) | Count of error-free frames shorter than 64 bytes that were received on this port. A frame is considered error-free if it has a valid FCS, no PHY errors and no FIFO errors. | packets (frames) | 0 |
57 | RX Short Bad (KPI) | Count of frames received on this port that were shorter than 64 bytes and have a bad FCS. Frames with PHY or FIFO errors are not counted. | packets (frames) | 0 |
58 | RX Long Ok (KPI) | Count of error-free frames received that are longer than the MTU configured on the port. A frame is considered error-free if it has a valid FCS, no PHY errors and no FIFO errors. | packets (frames) | 0 |
59 | RX Long Bad (KPI) | Count of frames received that are longer than the MTU configured on the port and have a bad FCS. Frames with PHY or FIFO errors are not counted. | packets (frames) | 0 |
60 | RX Unicast Packets (KPI) | Count of the good unicast frames received by this port. A good unicast frame is a normally-sized frame (from 64 bytes to the MTU configured on the port) that is not dropped and has a good FCS. Unicast frames are identified by having a 0 in the least significant bit of the first byte of the destination address (the first bit received is a 0). | packets (frames) | 1873468 |
61 | RX Multicast Packets (KPI) | Count of the good multicast frames received by this port. A good multicast frame is a normally-sized frame (from 64 bytes to the MTU configured on the port) that is not dropped and has a good FCS. Multicast frames are identified by having a 1 in the least significant bit of the first byte of the destination address (the first bit received is a 1). Broadcast frames are not included in this count. | packets (frames) | 2 |
62 | RX Broadcast Packets (KPI) | Count of the good broadcast frames received by this port. A good broadcast frame is a normal-sized frame (from 64 bytes to the MTU configured on the port) that is not dropped and has a good FCS. Broadcast frames are identified by a destination address of all 1s. | packets (frames) | 0 |
63 | RX Pause Frames (KPI) | Count of the good flow control pause frames received by this port (good FCS, no PHY or FIFO errors, normal size). Flow control pause frames are identified by an Ethertype of 8808h and an OpCode of 00-01. | packets (frames) | 0 |
64 | RX Tagged Frames (KPI) | Count of the good VLAN frames received by this port (good FCS, no PHY or FIFO errors, normally sized). VLAN frames are identified by a type field equal to 8100h set in the outer VLAN tag. | packets (frames) | 1873468 |
65 | RX CRC Errors (KPI) | Count of normally-sized frames (from 64 bytes to the MTU configured on the port) received by this port with an FCS error but not a dribbling nibble (frame length is an integral number of bytes). Frames with FIFO or PHY errors are not counted. | packets (frames) | 0 |
66 | RX Aligned Errors (KPI) | Count of normally-sized frames (from 64 bytes to the MTU configured on the port) received by this port with an FCS error and a dribbling nibble (frame length is not an integral number of bytes). Frames with PHY or FIFO errors are not counted. | packets (frames) | 0 |
67 | RX Runt Frames (KPI) | Count of the number of received frames (or events) detected by this port without SFD detection but with carrier assertion. Frames with valid SFD but no data bytes are also counted as runts. After detecting a runt frame, the update of the Rx Runt counter is suspended until the next valid frame is received. If multiple runt frames occur between valid frames, the Rx Runt counter is incremented only once. | packets (frames) | 0 |
68 | RX Length Errors (KPI) | Count of the number of good frames received by this port with an error in the length field. A length error occurs when the value in the length field is within the valid range for data length (46-1500 bytes) but does not match the actual data length of the frame. Field lengths less than 46 bytes (less than the minimum legal frame size of 64 bytes) are not checked, due to padding. | packets (frames) | 0 |
69 | RX False CRS (KPI) | Count of the number of received frames (or events) detected by this port with a false carrier (SSD1 not followed by SSD2). After detecting a false carrier, updating the RxFalseCRS counter is suspended until the next valid frame is received. If multiple false carrier events occur between valid frames, the RxFalseCRS counter is incremented only once. | packets (frames) | 0 |
70 | RX PHY Errors (KPI) | Count of the number of frames received by this port with RX_ER asserted during reception (while RX_DV is asserted). Frames with a FIFO error are not counted. | packets (frames) | 0 |
71 | RX FIFO Errors (KPI) | Count of the number of received frames dropped or aborted due to receiving a FIFO overflow. The FIFO overflow error takes precedence over all other errors. If this counter is incremented, then none of the other frame counters are incremented. | packets (frames) | 0 |
72 | RX Ignored (KPI) | Count of the number of received frames that have been ignored by this port. A frame is ignored if it violates the programmed preamble rules or if it violates the minimum data gap. The preamble rules include long preamble enforcement (greater than 23 nibbles) and pure preamble enforcement (only 55 hex bytes). The minimum data gap is the time between frame data transfers and is measured from immediately after the last FCS byte of the previous frame to the SFD field of the current frame. The normal data gap is 20 bytes long (12 bytes of IFG and 8 bytes of preamble/SFD). The enforcement limit is set to 10 bytes (half the normal gap length). | packets (frames) | 0 |
73 | RX Bad Opcode (KPI) | Count of the good control frames received by this port (good FCS, no PHY or FIFO errors, normally sized) with an unknown OpCode. Unknown control frames are identified by an Ethertype of 8808h and an OpCode not equal to 00-01. | packets (frames) | 0 |
74 | RX Packets 64 (KPI) | The total number of frames received by this port (both good and bad) that were exactly 64 bytes in length (excluding preamble and SFD but including FCS). | packets (frames) | 824 |
75 | RX Packets 65-127 (KPI) | The total number of frames received by this port (both good and bad) that were in the range of 65-127 bytes. This frame length value excludes the preamble and SFD but includes the FCS. | packets (frames) | 57917 |
76 | RX Packets 128-255 (KPI) | The total number of frames received by this port (both good and bad) that were in the range of 128-255 bytes. This frame length value excludes the preamble and SFD but includes the FCS. | packets (frames) | 148067 |
77 | RX Packets 256-511 (KPI) | The total number of frames received by this port (both good and bad) that were in the range of 256-511 bytes. This frame length value excludes the preamble and SFD but includes the FCS. | packets (frames) | 349562 |
78 | RX Packets 512-1023 (KPI) | The total number of frames received by this port (both good and bad) that were in the range of 512-1023 bytes. This frame length value excludes the preamble and SFD but includes the FCS. | packets (frames) | 711375 |
79 | RX Packets 1024-1518 (KPI) | The total number of frames received by this port (both good and bad) that were in the range of 1024-1518 bytes. This frame length value excludes the preamble and SFD but includes the FCS. | packets (frames) | 605725 |
80 | RX Packets 1519-2047 (KPI) | The total number of frames received by this port (both good and bad) that were in the range of 1519-2047 bytes. This frame length value excludes the preamble and SFD but includes the FCS. | packets (frames) | 0 |
81 | RX Packets 2048-4095 (KPI) | The total number of frames received by this port (both good and bad) that were in the range of 2048-4095 bytes. This frame length value excludes the preamble and SFD but includes the FCS. | packets (frames) | 0 |
82 | RX Packets 4096-8191 (KPI) | The total number of frames received by this port (both good and bad) that were in the range of 4096-8191 bytes. This frame length value excludes the preamble and SFD but includes the FCS. | packets (frames) | 0 |
83 | RX Packets 8192 and More (KPI) | The total number of frames received by this port (both good and bad) that were in the range of 8192 bytes and more. This frame length value excludes the preamble and SFD but includes the FCS. | packets (frames) | 0 |
84 | RX Large Packets (KPI) | The total number of large frames received by this port. The size of large frames is defined via the Large Packet Threshold parameter. | packets (frames) | 0 |
85 | RX L1 Bandwidth Utilization (%) (KPI) | The bandwidth currently used for the reception of incoming traffic on the selected port, expressed as a percentage of the line rate. Note: Bandwidth utilization statistics are provided with one-second granularity for both Layer 1 and Layer 2; however, the value expressed as a percentage of the line rate is available for Layer 1 only. Note: Statistics will be accurate to ±1% at data rates above 100 Mbps. | % | 20 |
86 | RX L1 Rate (Mbps) (KPI) | The rate at which incoming traffic is currently circulating at Layer 1 for the selected port, expressed in Mbps. | Mbps | 200 |
87 | RX L2 Rate (Mbps) (KPI) | The rate at which incoming traffic is currently circulating at Layer 2 for the selected port, expressed in Mbps. | Mbps | 195 |
© 2025 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and trademarks
