The objects described here can be monitored with the IPHost Network Monitor.
You can start SNMP monitoring using free 30-day trial version of IPHost right now.
OID list for alignment errors
- rastotal Alignment Errors
- rastotalAlignmentErrors 1.3.6.1.4.1.311.1.1.3.1.1.16.10 (defined in WINDOWS-NT-PERFORMANCE)
The total number of Alignment Errors for this connection. Alignment Errors occur when a byte received is different from the byte expected. - rasport Alignment Errors
- rasportAlignmentErrors 1.3.6.1.4.1.311.1.1.3.1.1.31.1.12 (defined in WINDOWS-NT-PERFORMANCE)
The total number of Alignment Errors for this connection. Alignment Errors occur when a byte received is different from the byte expected. - dot3 Statistics Alignment Errors
- dot3StatsAlignmentErrors 1.3.6.1.2.1.10.7.2.1.2 (defined in EtherLike-MIB)
interface that are not an integral number of octets in length and do not pass the FCS check. The count represented by an instance of this object is incremented when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions pertain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC. This counter does not increment for group encoding schemes greater than 4 bits per group. For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsAlignmentErrors object for 10 Gb/s or faster interfaces. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. - dot3 HC Statistics Alignment Errors
- dot3HCStatsAlignmentErrors 1.3.6.1.2.1.10.7.11.1.1 (defined in EtherLike-MIB)
interface that are not an integral number of octets in length and do not pass the FCS check. The count represented by an instance of this object is incremented when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions pertain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC. This counter does not increment for group encoding schemes greater than 4 bits per group. This counter is a 64 bit version of dot3StatsAlignmentErrors. It should be used on interfaces operating at 10 Gb/s or faster. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. - dot3 Statistics Alignment Errors
- dot3StatsAlignmentErrors 1.3.6.1.2.1.10.7.2.1.2 (defined in rfc1398)
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 count represented by an instance of this object is incremented when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC. - Repeater Monitor Port Alignment Errors
- rptrMonitorPortAlignmentErrors 1.3.6.1.2.1.22.2.3.1.1.6 (defined in rfc1516)
This counter is incremented by one for each frame received on this port with the FCSError and FramingError signals asserted and CollisionEvent signal deasserted and whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: IEEE 802.3 Std, 4.4.2.1). If rptrMonitorPortAlignmentErrors is incremented then the rptrMonitorPortFCSErrors Counter shall not be incremented for the same frame. The approximate minimum time for rollover of this counter is 80 hours. - dot3 Statistics Alignment Errors
- dot3StatsAlignmentErrors 1.3.6.1.2.1.10.7.2.1.2 (defined in rfc1650)
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 count represented by an instance of this object is incremented when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC. - Compaq Network Interface Card If Physical Adapter Alignment Errors
- cpqNicIfPhysAdapterAlignmentErrors 1.3.6.1.4.1.232.18.2.3.1.1.20 (defined in CPQNIC)
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. - dot3 Statistics Alignment Errors
- dot3StatsAlignmentErrors 1.3.6.1.2.1.10.7.2.1.2 (defined in ETHER)
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 count represented by an instance of this object is incremented when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC. - perf Monitor Agent Alignment Errors
- perfMonAgentAlignmentErrors 1.3.6.1.4.1.52.259.10.3.3.1.2 (defined in elh100-mib)
The number of valid-length packets with alignment errors received on the agent's MAC port. - switch Port Alignment Errors
- switchPortAlignmentErrors 1.3.6.1.4.1.52.259.10.3.4.2.1.1.6 (defined in elh100-mib)
The number of valid-length frames received by the port that had alignment errors.
