ACD-PORT-MIB: View SNMP OID List / Download MIB

The Port statistics for this Accedian Networks device.

Table of port configuration attributes

Port configuration.

The value of this object uniquely identifies this acdPortConfig entry.

This is a string to identify the port.

This is a string to give the port an alias.

The MAC address of the port.

This object identifies the connector ID of the port. This object shall identify the acdDescConnectorID object, defined in the ACD-DESC-MIB.

Enable or disable the port.

The configured MTU of the port. The value ranges from 1518 to 10240.

Enable or disable the auto negociation on the port.

The configured speed of the port in Mbps. The valid values are 10, 100, 1000 and 10000.

The configured duplex mode for this port. Enumeration: 'fullDuplex': 2, 'halfDuplex': 1.

The configured MDI mode for this port. Enumeration: 'autoMdi': 1, 'mdi': 2, 'mdix': 3.

The configured pause mode for this port. Enumeration: 'forward': 3, 'disable': 1, 'local': 2.

A value that identifies the set of port capabilities to advertise during auto-negociation. Each bit indicates whether or not the specific capability is valid on the system. Bits: 'bFullDuplex1Gbps': 5, 'bPauseAsymmetric': 7, 'bPauseSymmetric': 6, 'bHalfDuplex100Mbps': 2, 'bFullDuplex10Mbps': 1, 'bHalfDuplex1Gbps': 4, 'bFullDuplex100Mbps': 3, 'bHalfDuplex10Mbps': 0.

Table for port status

Port status.

The value of this object uniquely identifies this acdPortStatus entry.

The current speed of the port in Mbps. The valid values are 10, 100 1000 and 10000.

The current duplex mode of the port. Enumeration: 'fullDuplex': 2, 'halfDuplex': 1.

The current MDI mode of the port. Enumeration: 'mdi': 1, 'mdix': 2.

Indicates whether or not the port is transmitting pause frames.

Indicates whether or not the port is receiving pause frames.

A value that identifies the set of port capabilities advertised by the link partner. Each bit indicates whether or not the specific capability is valid on the link partner system. Bits: 'bFullDuplex1Gbps': 5, 'bPauseAsymmetric': 7, 'bPauseSymmetric': 6, 'bHalfDuplex100Mbps': 2, 'bFullDuplex10Mbps': 1, 'bHalfDuplex1Gbps': 4, 'bFullDuplex100Mbps': 3, 'bHalfDuplex10Mbps': 0.

Indicates if the port link is Up or Down. Down(FALSE), Up(TRUE)

A value that uniquely identifies the selected media type. Bits: 'b1000baseTHD': 29, 'bOther': 0, 'b1000baseLXFD': 24, 'b10broad36': 9, 'b10base2': 4, 'b1000baseCXHD': 27, 'b1000baseLXHD': 23, 'b10base5': 2, 'b10baseTFD': 11, 'b100baseTXHD': 15, 'bAUI': 1, 'b100baseT2HD': 19, 'b10baseTHD': 10, 'b1000baseCXFD': 28, 'b100baseTXFD': 16, 'b1000baseSXHD': 25, 'b100baseFXFD': 18, 'b100baseT4': 14, 'b1000baseXFD': 22, 'b1000baseTFD': 30, 'b100baseFXHD': 17, 'b100baseT2FD': 20, 'bFoirl': 3, 'b1000baseXHD': 21, 'b1000baseSXFD': 26, 'b10baseFB': 7, 'b10baseFL': 8, 'b10baseFP': 6, 'b10baseFLHD': 12, 'b10baseFLFD': 13, 'b10baseT': 5.

Indicates if the port is a monitor port. No(FALSE), Yes(TRUE)

Indicates if the port is a management port. No(FALSE), Yes(TRUE)

Indicates if the port has an SFP. No(FALSE), Yes(TRUE)

Indicates if the port is connected to fiber. No(FALSE), Yes(TRUE)

Table of port transmit statistics

port transmit statistics.

The value of this object uniquely identifies this acdPortTxStats entry.

A value that identifies the set of TX statistics supported by the device. Each bit indicates whether or not the specific statistic value is valid on the system. Bits: 'bMultipleCollisions': 11, 'bExcessiveCollisions': 12, 'bFifoErrors': 15, 'bPkts1024to1518': 21, 'bDeferred': 8, 'bPktsLarge': 26, 'bBroadcastPkts': 4, 'bPkts2048to4095': 23, 'bPkts64': 16, 'bNormalCollisions': 14, 'bPkts4096to8191': 24, 'bBytesGood': 0, 'bTaggedFrames': 6, 'bMulticastPkts': 3, 'bPkts1519to2047': 22, 'bPkts256to511': 19, 'bPkts512to1023': 20, 'bLateCollisions': 13, 'bBytesTotal': 1, 'bSingleCollisions': 10, 'bPauseFrames': 5, 'bExcessiveDeferrals': 9, 'bCRCErrors': 7, 'bUnicastPkts': 2, 'bPkts128to255': 18, 'bPkts65to127': 17, 'bPkts8192andMore': 25.

This is a count of the total number of bytes transmitted by the port in good packets. The count includes the 4 CRC bytes but does not include the preamble or SFD bytes. A good packet is one that has been transmitted successfully (not aborted) with a good CRC. It is assumed that all transmit packets are properly sized, 64 bytes (after any padding) to maxsize bytes long.

This is a count of the total number of bytes transmitted by the port in good and bad packets. The count includes the 4 CRC bytes but does not include the preamble or SFD bytes. Bad packets include normal collisions, late collisions, and FIFO underflows. For collisions, all bytes transmitted before the start of the collision as well as the colliding and jam bytes are counted. For FIFO underflows, all bytes actually transmitted are counted.

This is a count of the good unicast packets transmitted by this port. Good unicast packets are packets that are not dropped and have a good CRC. Unicast packets are identified by having a 0 in the least significant bit of the first byte of the destination address (i.e. the first bit transmitted is a 0).

This is a count of the good multicast packets transmitted by this port (good means not dropped and valid CRC). Multicast packets are identified by having a 1 in the least significant bit of the first byte of the destination address (i.e. the first bit transmitted is a 1). Broadcast packets are not included in this count.

This is a count of the good broadcast packets transmitted by this port (good means not dropped and valid CRC). Broadcast packets are identified by a destination address of all 1.

This is a count of the good flow control pause packets transmitted by this port (good means not dropped and valid CRC). Flow control pause packets are identified by a type of 0x8808 and an opcode field of 0x0001.

This is a count of the good VLAN packets transmitted by this port (good means not dropped and valid CRC). VLAN packets are identified by a type field equal to 0x8100 in the outer VLAN tag.

This is a count of the transmitted packets with a bad non-appended CRC field. This count doesn't include any packets with a bad CRC due to a FIFO underflow.

This is a count of the number of packets that were deferred on the first transmit attempt due to the medium being busy. Packets with subsequent deferrals (for instance, after a collision back off) are not counted. Whether the packet is eventually transmitted successfully or not is irrelevant to this counter. Packets dropped due to excess deferral that occur during the initial transmit attempt are not counted.

This is a count of the number of packets 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.

This is a count of the number of times a packet is successfully transmitted from this port after experiencing a single collision. This count does not include erroneous (dropped) packets.

This is a count of the number of times a packet is successfully transmitted from this port after experiencing multiple collisions. This count does not include erroneous (dropped) packets and also does not include packets dropped due to excess collisions.

This is a count of the number of packets dropped by this port due to excess collisions (number of collisions equals MaxRetry+1). This count does not include packets dropped due to FIFO underflow or late collisions (even if the late collision is also an excessive collision).

This is a count of the number of packets dropped by this port due to late collisions. A late collision is a collision that occurs after the collision window time (normally 512-bit times). This count does not include packets dropped due to FIFO underflow. Late collisions are not retried.

This is a count of the total number of normal collisions that have occurred on this port during all transmission attempts. FIFO underflows, late collisions and collisions that occur while this port is not trying to transmit are not counted. This count does not include collisions during half-duplex back pressure.

This is a 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) CRC sequence. The FIFO underflow error takes precedence over all other errors if this counter is incremented, then none of the other packet type counters are incremented.

The total number of packets, good or bad, transmitted by this port that were exactly 64 bytes in length (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, transmitted by this port that were 65 to 127 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, transmitted by this port that were 128 to 255 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, transmitted by this port that were 256 to 511 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, transmitted by this port that were 512 to 1023 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, transmitted by this port that were 1024 to 1518 bytes in length (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, transmitted by this port that were 1519 to 2047 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, transmitted by this port that were 2048 to 4095 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, transmitted by this port that were 4096 to 8191 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, transmitted by this port that were greater than 8192 bytes in length (excluding preamble and SFD but including CRC).

The total number of large packets transmitted by this port. Define the size of large packets on the Port configuration.

Table of port receive statistics

port receive statistics.

The value of this object uniquely identifies this acdPortRxStats entry.

A value that identifies the set of RX statistics supported by the device. Each bit indicates whether or not the specific statistic value is valid on the system. Bits: 'bFalseCRS': 15, 'bFifoErrors': 17, 'bPkts1024to1518': 25, 'bPktsLarge': 30, 'bBroadcastPkts': 8, 'bPkts64': 20, 'bPhyErrors': 16, 'bRuntFrames': 13, 'bPkts4096to8191': 28, 'bAlignErrors': 12, 'bBytesGood': 0, 'bTaggedFrames': 10, 'bMulticastPkts': 7, 'bPkts1519to2047': 26, 'bPkts256to511': 23, 'bPkts512to1023': 24, 'bRxStatsLongBad': 5, 'bRxStatsShortOk': 2, 'bRxStatsShortBad': 3, 'bBytesTotal': 1, 'bPkts2048to4095': 27, 'bCRCErrors': 11, 'bIgnored': 18, 'bLengthErrors': 14, 'bRxStatsLongOk': 4, 'bPauseFrames': 9, 'bBadOpcode': 19, 'bUnicastPkts': 6, 'bPkts128to255': 22, 'bPkts65to127': 21, 'bPkts8192andMore': 29.

This is a count of the total number of bytes received by the port in good packets. The count includes the 4 CRC bytes but does not include the preamble or SFD bytes. A good packet is a well-formed normally sized packet (64 to maxsize bytes) with good CRC and no PHY or FIFO errors.

This is a count of the total number of bytes received by the port in good and bad packets. The count includes the 4 CRC bytes (if present) but does not include the preamble or SFD bytes. Good packets are described above. Bad packets include short packets (less than 64 bytes), long packets (greater than maxsize bytes), packets with bad CRC, packets with PHY errors, and packets with receive FIFO errors. Bytes in bad packets resulting from a collision are counted if the SFD is detected.

This is a count of error-free packets received on this port that are shorter than 64 bytes. A packet is error-free if it has a valid CRC, no PHY errorsand no FIFO errors.

This is a count of packets received on this port that are shorter than 64 bytes and have a bad CRC. Packets with PHY or FIFO errors are not counted.

This is a count of error-free packets received on this port that are longer than maxsize bytes. A packet is error-free if it has a valid CRC, no PHY errors and no FIFO errors.

This is a count of packets received on this port that are longer than 64 bytes and have a bad CRC. Packets with PHY or FIFO errors are not counted.

This is a count of the good unicast packets received by this port. A good unicast packet is a normally sized packet (64 to maxsize bytes) that is received without error a good CRC, no PHY or FIFO errors. Unicast packets are identified by having a 0 in the least significant bit of the first byte of the destination address (i.e. the first bit received is a 0).

This is a count of the good multicast packets received by this port. A good multicast packet is a normally sized packet (64 to maxsize bytes) that is received without error, a good CRC, no PHY or FIFO errors. Multicast packets are identified by having a 1 in the least significant bit of the first byte of the destination address (i.e. the first bit received is a 1). Broadcast packets are not included in this count.

This is a count of the good broadcast packets received by this port. A good broadcast packet is a normally sized packet (64 to maxsize bytes) that is received without error, a good CRC, no PHY or FIFO errors. Broadcast packets are identified by a destination address of all 1's.

This is a count of the good flow control pause packets received by this port (good CRC, no PHY or FIFO errors, normally sized). Flow control pause packets are identified by a type of 0x8808, and an opcode field of 0x0001.

This is a count of the good VLAN packets receive by this port (good CRC, no PHY or FIFO errors, normally sized). VLAN packets are identified by a type field equal to 0x8100 in the outer VLAN tag.

This is a count of normally sized packets (64 to maxsize bytes) received by this port with a CRC error but not a dribbling nibble (packet is an integral number of bytes long). Packets with FIFO or PHY errors are not counted.

This is a count of normally sized packets (64 to maxsize bytes) received by this port with a CRC error and a dribbling nibble (packet is not an integral number of bytes long). Packets with PHY or FIFO errors are not counted.

This is a count of the number of receive packets (or events) detected by this port without SDF detection but with carrier assertion. Packets with valid SFD but no data bytes are also counted as runts. After detecting a runt packet, the update of the RxRunts counter is held off until the next valid packet is received. If multiple runt packets occur between valid packets, the RxRunts counter is incremented only once.

This is a count of the number of good packets received by this port with a length field check error. A length check error occurs when the value in the length field is within the valid range for data length (3-1500 bytes) but does not match the actual data length of the packet. Length field values less than 46 bytes (which corresponds to the minimum legal packet size of 64 bytes) are not checked due to padding.

This is a count of the number of receive packets (or events) detected by this port with a false carrier (SSD1 not followed by SSD2). After detecting a false carrier, update of the RxFalseCRS counter is held off until the next valid packet is received. If multiple false carrier events occur between valid packets, the RxFalseCRS counter is incremented only once.

This is a count of the number of packets received by this port with RX_ER asserted during reception (while RX_DV asserted). Packets with a FIFO error are not counted.

This is a count of the number of receive packets dropped or aborted due to receive FIFO overflow. The FIFO overflow error takes precedence over all other errors - if this counter is incremented, then none of the other packet type counters is incremented.

This is a count of the number of received packets that have been ignored by this port. A packet is ignored if it violates the programmed preamble rules or it violates the minimum data gap. The preamble rules include long preamble enforcement (greater than 23 nibbles) and pure preamble enforcement (only 55h bytes). The minimum data gap is the time between packet data transfers and is measured from immediately after the last CRC byte of the previous packet through the SFD field of the current packet. The normal data gap is 20 bytes long (12 bytes of IPG and 8 bytes of preamble/SFD). The enforcement limit is set to 10 bytes (half the normal gap length).

This is a count of the good control packets received by this port (good CRC, no PHY or FIFO errors, normally sized) with an unknown opcode. Unknown control packets are identified by a type field of 88-08 and an opcode field not equal to 00-01.

The total number of packets, good or bad, received by this port that were exactly 64 bytes in length (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, received by this port that were 65 to 127 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, received by this port that were 128 to 255 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, received by this port that were 256 to 511 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, received by this port that were 512 to 1023 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, received by this port that were 1024 to 1518 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, received by this port that were 1519 to 2047 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, received by this port that were 2048 to 4095 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, received by this port that were 4096 to 8191 bytes in length inclusive (excluding preamble and SFD but including CRC).

The total number of packets, good or bad, received by this port that were greater than 8192 bytes in length (excluding preamble and SFD but including CRC).

The total number of large packets received by this port. Define the size of large packets on the Port configuration page.

This is the transaction ID of the last change of the acdPortConfigTable table. If this value is different since the last read this is indicate a table change.

The compliance statement for support of the ACD-PORT-MIB module.

.

.

.

.

List of scalars to monitior changes in tables.