CPQNIC-MIB :: cpqNicIfPhysAdapterLateCollisions

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCPQNIC-MIBcpqNicIfPhysAdapterLateCollisions

cpqNicIfPhysAdapterLateCollisions

Module: CPQNIC-MIB

OID (symbolic): CPQNIC-MIB::cpqNicIfPhysAdapterLateCollisions

OID (numeric): 1.3.6.1.4.1.232.18.2.3.1.1.25

Node type: OBJECT-TYPE

Type: Counter

Access: read-only

Description: Late collisions may be a symptom of cabling problems. A late collision is one that occurred 64 bytes or more into the packet.

Late collisions may be an indication that a segment is longer than allowed by the wiring specifications.

A station will believe it has control of the cable segment if it has already transmitted 64 bytes. If another node at the far end of the segment has not yet seen the packet, and transmits, this packet will collide with the first transmission after the first 64 bytes have been sent. Ensure that your segment length does not exceed the maximum length allowed.

Because the location of cabling problems can be very difficult to detect on an Ethernet network, you may want to 'shorten' an Ethernet segment (remove portions of the network to isolate problems) until the problems are no longer seen, and then expand the network until the problem recurs.

If this counter increments quickly in a short period of time, it may mean that the network card is running in half duplex mode, but your hub or switch port is configured for full duplex mode. Compare your network card's configuration with the port's configuration.

Late collisions are also included in other collision-related statistics.

What is cpqNicIfPhysAdapterLateCollisions?

This read-only counter tallies late collisions, ones occurring 64 bytes or more into the packet, which the MIB flags as a symptom of cabling problems or a segment being longer than the wiring specification allows. An admin treats a rising late-collision count as a strong indicator of a physical cabling issue rather than a normal traffic-load collision. For example, late collisions appearing on a segment believed to be within spec would prompt an admin to re-measure cable length and check for damaged runs.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.232.18.2.3.1.1.25
snmpwalk -v2c -c public <target> CPQNIC-MIB::cpqNicIfPhysAdapterLateCollisions

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.232.18.2.3.1.1.25.1
snmpget -v2c -c public <target> CPQNIC-MIB::cpqNicIfPhysAdapterLateCollisions.1

Start monitoring Compaq/HP ProLiant server (network interface card) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CPQNIC-MIB::cpqNicIfPhysAdapterLateCollisions OID value, configure state conditions and alerts, and monitor any Compaq/HP ProLiant server (network interface card) from a single console.

OID Breakdown

Upper-level ancestors (7 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.232compaqCOMPAQ-ID-REC-MIB
Numeric OIDNameModule
1.3.6.1.4.1.232.18cpqNicCPQNIC-MIB
1.3.6.1.4.1.232.18.2cpqNicComponentCPQNIC-MIB
1.3.6.1.4.1.232.18.2.3cpqNicIfPhysAdapterCPQNIC-MIB
1.3.6.1.4.1.232.18.2.3.1cpqNicIfPhysAdapterTableCPQNIC-MIB
1.3.6.1.4.1.232.18.2.3.1.1cpqNicIfPhysAdapterEntryCPQNIC-MIB
1.3.6.1.4.1.232.18.2.3.1.1.25cpqNicIfPhysAdapterLateCollisionsCPQNIC-MIB