Hp COMPAQ PROLIANT 6500, COMPAQ PROLIANT 2500, COMPAQ PROSIGNIA 200, COMPAQ PROSIGNIA 720, COMPAQ PROLIANT 1500 LAN Driver Statistics for Novell Drivers
...
INTEGRATION NOTE
.
.
October, 1997
Prepared By
Novell Integration
Business Unit, Compaq
Computer Corporation
CONTENTS
Executive Summary........ 3
Introduction ................... 4
PCNTNW.LAN
Custom Statistics ........... 9
CPQNF3.LAN
CUSTOM
STATISTICS ................... 10
LAN DRIVER
TOKEN RING
STATISTICS ................... 13
ECG043/1097
.
.
.
LAN Driver Statistics for Novell Drivers
.
.
.
.
.
.
.
.
.
.
.
.
.
.
This integration note describes the statistics to diagnose network problems via the Novell
.
.
.
MONITOR modules. The statistics supplement the diagnostic information that would
.
.
.
normally be obtained with a protocol analyzer or network monitor and gives an estimate
.
.
.
of network and controller activity.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
ECG043/1097
.
.
INTEGRATION NOTE (cont.)
.
NOTICE
.
.
.
.
.
The information in this publication is subject to change without notice.
.
.
.
.
.
.
.
COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR TECHNICAL
.
.
OR EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN, NOR FOR
.
.
.
INCIDENTAL OR CONSEQUENTIAL DAMAGES RESULTING FROM THE
.
.
.
FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL.
.
.
.
.
This publication does not constitute an endorsement of the product or products that were tested.
.
.
.
The configuration or configurations tested or described may or may not be the only available
.
.
.
solution. This test is not a determination of product quality or correctness, nor does it ensure
.
.
.
compliance with any federal, state or local requirements. Compaq does not warrant products other
.
.
.
than its own strictly as stated in Compaq product warranties.
.
.
.
.
Product names mentioned herein may be trademarks and/or registered trademarks of their
.
.
.
respective companies.
.
.
.
.
.
Compaq, Compaq Insight Manager, ProLiant, SmartStart, NetFlex, registered United States
.
.
.
Patent and Trademark Office.
.
.
.
.
Netelligent is a trademark and/or service mark of Compaq Computer Corporation.
.
.
.
.
.
intraNetWare, NetWare 3, NetWare 4, NetWare Loadable Module, NetWare Storage
.
.
Management Services, NetWare SMS, Novell, Novell Directory Services, and NDS and are
.
.
.
trademarks of Novell, Inc.
.
.
.
.
.
Other product names mentioned herein may be trademarks and/or registered trademarks of their
.
.
.
respective companies.
.
.
.
.
©1997 Compaq Computer Corporation. All rights reserved. Printed in the U.S.A.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
LAN Driver Statistics for Novell Drivers
.
.
.
First Edition (October, 1997)
.
.
.
043A/1097
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
ECG043/1097
.
.
INTEGRATION NOTE (cont.)
.
.
.
.
EXECUTIVE SUMMARY
.
.
.
.
.
The Compaq network interface controller (NIC) drivers provide a number of statistics to aid in
.
.
.
the diagnosis of network problems. These statistics can be viewed with MONITOR.NLM. Each
.
.
.
statistic is listed in this document includes a description of its purpose as well as provides
.
.
suggestions to counter problems and reduce the number errors reported.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
ECG043/1097
.
.
INTEGRATION NOTE (cont.)
.
.
.
.
INTRODUCTION
.
.
.
.
.
The Compaq network interface controller (NIC) drivers provide a number of statistics to aid in
.
.
.
the diagnosis of network problems. These statistics can be viewed with MONITOR.NLM.
.
.
.
Information such as Packets Received and Packets Sent are common to every protocol and are
.
.
reported for every controller. Others like Collisions or Beacons are particular to one protocol or
.
.
.
another (Ethernet and Token Ring, respectively). The statistics supplement the diagnostic
.
.
.
information that would normally be obtained with a protocol analyzer or network monitor and
.
.
.
give an estimate of network and controller activity. Most of these statistics will increase during
.
.
.
normal operation. Occasional errors do not necessarily indicate a problem.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
ECG043/1097
.
.
INTEGRATION NOTE (cont.)
.
.
.
.
NET FLEX AND DUALSPEED CONTROLLER STATISTICS
.
.
.
.
.
.
.
Send OK Single Collision Count
.
.
.
.
The number of single collision packets: This counter contains the number of packets that are
.
.
.
involved in a single collision and are subsequently transmitted successfully.
.
.
.
.
These errors show that the network has light to moderate traffic. If single collisions become more
.
.
.
frequent, the count for multiple collisions escalates.
.
.
.
.
.
.
.
Send OK Multiple Collision Count
.
.
.
.
The number of multiple collision packets: This counter contains the number of packets that are
.
.
.
involved in multiple collisions and are subsequently transmitted successfully.
.
.
.
.
These errors mean that the network is experiencing moderate to heavy traffic. If multiple
.
.
.
collisions become more frequent, the count for excessive collisions escalates.
.
.
.
.
.
.
.
Send OK But Deferred
.
.
.
.
The number of packets deferred before transmission: This counter contains the number of packets
.
.
.
whose transmission was delayed on its first attempt because the medium was busy. Packets
.
.
.
involved in any collisions are not counted. Frames that wait before transmission are counted.
.
.
.
This statistic will be incremented often during normal operation on a busy network.
.
.
.
.
Deferred transmissions occur when the network is extremely busy; so busy that the NIC did not
.
.
.
try to transmit. High counts of multiple collisions and excessive collisions also occur.
.
.
.
.
.
Deferred transmissions indicate that this segment of the LAN is overcrowded. Reduce the traffic
.
.
.
by reorganizing the LAN. For example, if you have 100 stations on one Ethernet bus, break it
.
.
.
into two Ethernet segments by adding a NIC to your server. In this way you can balance the load
.
.
.
by putting 50 stations on one segment and 50 on the other. If a few isolated stations create the
.
.
traffic, put them on a separate segment.
.
.
.
.
.
.
.
Send Abort from Late Collision
.
.
.
.
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. For example, if you are using 10BASE-2 wiring, also known as Thinnet, the
.
.
maximum segment length is 185 meters.
.
.
.
.
.
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 port is configured for full duplex mode. Compare your
.
.
.
network card’s configuration with the hub port’s configuration.
.
.
.
.
.
5
ECG043/1097
.
.
INTEGRATION NOTE (cont.)
Send Abort from Excess Collisions
.
.
.
.
.
The number of packets aborted during transmission due to excessive collisions: This counter
.
.
.
contains the number of packets that, due to excessive collisions, are not transmitted successfully.
.
.
.
A station may attempt to transmit up to 16 times before it must abort the attempt. Once the abort
.
.
.
occurs, this counter increments.
.
.
.
.
If you see an increase in deferred transmissions as well as excessive collisions, the network is
.
.
.
extremely busy and this segment of the LAN is overcrowded. Reduce the traffic by reorganizing
.
.
.
your LAN or adding a NIC to the server. For example, if you have 100 stations on one Ethernet
.
.
.
bus, break it into two Ethernet buses by adding a NIC to your server. In this way you can balance
.
.
.
the load by putting 50 stations on one bus and 50 on the other. If there are a few isolated stations
.
.
.
creating the traffic, try placing them on a separate bus.
.
.
.
.
Faulty components may be the cause of excessive collisions. Check the following:
.
.
.
.
.
• This counter will increment with each transmit frame if you are using coaxial cabling (on the
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
10B2 connector) and the cable is disconnected.
• 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.
• Taps too close: Follow the minimum recommended spacing between cable taps to ensure
minimal reflection build-up and data distortion.
• 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 or transceiver.
• 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. Swap out the transceiver, transceiver cable, and transceiver attachment point, one at
a time. If you find a faulty component, replace it.
3. Check your hub. This component may be at fault. Use the diagnostics from the hub
manufacturer to help you determine if a problem exists.
Send Abort from Carrier Sense
The number of packets transmitted with carrier sense errors: This counter contains the number of
times that the carrier sense signal from the physical layer interface was not asserted or was deasserted during transmission of a packet without collision.
Loading...