cpqNicIfPhysAdapterAlignmentErrors

CPQNIC-MIB · .1.3.6.1.4.1.232.18.2.3.1.1.20

Object

column mandatory RFC1155-SMICounter
A count of frames received on a particular
interface that are not an integral number of
octets in length and do not pass the FCS check.
The alignment of a frame is checked by the
receiver after the packet has failed the
Cyclical Redundancy Check (CRC). Misaligned
packets do not end on an 8-bit boundary.
All packets contain a set number of bytes
and must end after a defined number of bytes.
Packets that do not end on a byte boundary
fail the alignment check.
              
Faulty components may be the cause of alignment
errors. Check the following:
              
Segment too long: Nodes at the far end of the
cabling system transmit, unaware that a station
at the other end has already gained control of
the medium by transmitting the first 64 bytes
of a frame.
              
Failing cable: Packet data traveling through
shorted or damaged cabling may become corrupt
before reaching the destination station.
              
Segment not grounded properly: Improper grounding
of a segment may allow ground-induced noise to
corrupt data flow.
              
Improper termination: If a cable segment is not
properly terminated, allowing the signal to be
absorbed upon reaching the end of the segment,
a partial signal will bounce back and collide
with existing signals.
              
Noisy cable: Interference or noise produced by
motors or other devices can distort the signals
and cause CRC/Alignment errors.
              
Deaf/partially deaf node: A faulty station that
cannot hear the activity is considered a deaf node.
If you suspect a deaf node, replace the NIC.
              
Failing repeater, transceiver, or controller:
Repeaters, transceivers, and controllers can
disrupt the network signal, transmit erroneous
signals on the wire, or ignore incoming packets.
Perform the following steps:
              
1.  If your NIC is continuously transmitting,
    it causes erroneous signals, or `jabber`.
    Replace a jabbering transmitter to ensure
    proper network performance.
              
2.  Check your hub or switch. This component
    may be at fault.  Use the diagnostics from
    the component manufacturer to help you
    determine if a problem exists.

Context

MIB
CPQNIC-MIB
OID
.1.3.6.1.4.1.232.18.2.3.1.1.20
Type
column
Access
readonly
Status
mandatory
Parent
cpqNicIfPhysAdapterEntry
Table
cpqNicIfPhysAdapterTable
Siblings
42

Syntax

Source
RFC1155-SMICounter
Base type
Unsigned32

Values & Constraints

Type Constraints
range: 0..4294967295

Related Objects

Sibling Objects