Compaq 108164-003 - ProLiant - 800 Guide de démarrage rapide

INTEGRATIONNOTE

ECG043/1097

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

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.

INTEGRATION NOTE (cont.)

ECG043/1097

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.

LAN Driver Statistics for Novell Drivers

First Edition (October, 1997)

043A/1097

INTEGRATION NOTE (cont.)

ECG043/1097

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.

INTEGRATION NOTE (cont.)

ECG043/1097

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.

INTEGRATION NOTE (cont.)

ECG043/1097

NETFLEX 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.

INTEGRATION NOTE (cont.)

ECG043/1097

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

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 de-

asserted during transmission of a packet without collision.

INTEGRATION NOTE (cont.)

ECG043/1097

The carrier sense signal is an ongoing activity of a data station to detect whether or not another

station is transmitting. Carrier sense errors are detected when a station transmits a frame and

does not detect its own signal on the wire.

If you receive carrier sense errors, check the following:

•Failing cable: Packet data traveling through shorted or damaged cabling may cause a signal

loss. Ensure that your cable is working and plugged in properly.

•Segment not grounded properly: Improper grounding of a segment may allow ground-

induced noise to interrupt the signal. Ensure that you have properly grounded all segments.

•Noisy cable: Interference or noise produced by motors or other devices can interrupt the

signals.

•Deaf/partially deaf node: A faulty station that cannot hear the activity is considered a deaf

node. If you suspect a deaf node, the network interface card or transceiver should be

replaced.

•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. Swap out the transceiver, transceiver cable, and transceiver attachment point, one at

a time. If you find a faulty component, replace it.

2. If none of the items listed above help you isolate the problem, you may need to

replace the Multi-Access Unit (MAU) or hub. Use a network analyzer to isolate the

problem area.

Send Abort from Excessive Deferral

The number of packets aborted due to excessive deferrals: This counter contains the number of

packets that, due to excessive deferrals, are not transmitted successfully. This counter is

incremented when the number of transmission attempts is greater than 16.

Receive Abort from Bad Frame Alignment

The number of packets received with alignment errors:

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.

If you are using a 100-Mbit adapter in your server and the Intel PRO/100 adapter in your clients,

you may see a large number of these errors. The problem can be alleviated by adding the

following line to the LINK DRIVER E100ODI section of your client’s NET.CFG files:

THRESHOLD 200

If your network continues to experience an increasing number of CRC/Alignment errors, check

for the problems listed under the bullet: Send Abort from Excess Collisions.

LOW/HIGH Counter Statistics

Total Send/Receive OK Byte Count:

These counts are defined as 8 byte values. The LOW count is the lower 4 bytes of the count. The

HIGH is the upper 4 bytes of the count. The HIGH will increment once every time the LOW

INTEGRATION NOTE (cont.)

ECG043/1097

reaches 4 billion. At that point, the LOW will start back at zero. Thus, in a normal situation, you

will see a very active and very high count for the LOW statistic. The HIGH count statistic will be

much smaller. An example of these types of counters is the Total Send OK Byte Count High and

Total Send OK Byte Count Low.

INTEGRATION NOTE (cont.)

ECG043/1097

PCNTNW.LAN CUSTOM STATISTICS

PCNTNW.LAN for the ProSignia Integrated NetFlex-L ENET and the Deskpro XL Integrated

NetFlex ENET/PCI has these additional custom statistics.

Heart Beat Error

This error indicates that the collision inputs to the AUI port failed to activate within 20 network

bit times after the chip terminated transmission.

Memory Time Out

This counter is incremented when the board does not get bus master resource to read or write to

memory in the system.

Tx Babbling Error

Babble is a transmitter time-out error. It indicates that the transmitter has been on the channel

longer that the time required to send the maximum length frame. BABL will be set if 1519 bytes

or greater are transmitted.

Tx Under Flow Error

This error indicates that a frame transmission was aborted because the board could not get the

data from memory in time.

Tx Buffer Error

This error indicates that the frame buffers which were queued for transmission were not set up

correctly by the software.

Rx ECB’s Over 16 Meg Count

This is a standard statistics counter which counts receive Event Control Blocks located above 16

Megabytes.

Tx ECB’s Over 16 Meg Count

This is a standard statistics counter which counts transmit Event Control Blocks located above 16

Megabytes.

Packets Used 2 ECBs

This is a statistic counter indicating that a packet used 2 Event Control Blocks.

INTEGRATION NOTE (cont.)

ECG043/1097

CPQNF3.LAN CUSTOM STATISTICS

CPQNF3.LAN has these additional custom statistics.

TLAN Device Revision (X.X)

This statistic will be a two-digit number that represents the version of ThunderLAN that is used

on your controller. For instance, if this value is 23, then that means that the TLAN version in use

is v2.3.

Adapter Check Count

This counts the number of adapter checks that occur and indicates a possible hardware problem.

A console error message that details the problem will be generated. The adapter will be reset and

operation should continue. The Adapter Reset statistic will also increment.

At the next scheduled maintenance, bring down the server and run Compaq Diagnostics to

determine if the board should be replaced.

Transmit Timeout Errors

This counter is incremented when a frame does not transfer within the expected amount of time.

The adapter will be reset and operation should continue. The Adapter Reset statistic will also

increment.

If this counter increments rapidly in a short period of time, check to ensure that the cables are

properly connected. The Link Status LED should be lit if the driver is loaded and the adapter is

connected to a hub. If this statistic still increments, power off the system and check the following:

Check the module on the NetFlex-3 Controller to ensure that it is correctly installed.

Check the seating of the NetFlex-3 Controller into its slot.

If all of these elements appear to be in working order:

1. Swap out the adapter and adapter cable one at a time. If you find a faulty component, replace

it.

2. 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 Link Failures

This indicates how many transmitted packets have failed to transmit due to link failures.

Transmit Packets Copied

Indicates how many packets have been copied by the driver before transmission. This counter

enables you to monitor inefficient NLMs running on the server. NLMs that use up to 16

fragments transmitted per packet may cause this counter to be incremented.

A typical file server will never see this counter increment.

Oversized Receive Errors

If a packet is received that is larger than the maximum allowed on Ethernet, this counter will be

incremented. A high number of these errors indicates that a node has malfunctioned and is

Autres manuels pour 108164-003 - ProLiant - 800

Ce manuel convient aux modèles suivants

Table des matières

Autres manuels Compaq Serveur

Compaq

Compaq ProLiant 400 Guide de démarrage rapide

Compaq

Compaq ProLiant 8500 Manuel d'installation et d'exploitation

Compaq

Compaq BL10e - HP ProLiant - 512 MB RAM Manuel utilisateur

Compaq

Compaq AlphaServer 160 Manuel utilisateur

Compaq

Compaq BL10e - HP ProLiant - 512 MB RAM Manuel de référence

Compaq

Compaq ProLiant DL580 Instructions d'utilisation et de sécurité

Compaq

Compaq 108164-003 - ProLiant - 800 Guide de référence rapide

Compaq

Compaq 6400R - ProLiant - 1 GB RAM Manuel

Compaq

Compaq BL10e - HP ProLiant - 512 MB RAM Manuel de référence

Compaq

Compaq 108164-003 - ProLiant - 800 Guide de référence rapide

Compaq

Compaq TruCluster Server AA-RHGWB-TE Manuel utilisateur

Compaq

Compaq DL320 - ProLiant - G3 Manuel technique

Compaq

Compaq ML330e - ProLiant - 64 MB RAM Manuel

Compaq

Compaq 112726-001 - ProLiant - 6500 Manuel utilisateur

Compaq

Compaq 386746-001 - ProLiant - 1600 Guide de démarrage rapide

Compaq

Compaq ProLiant 5500 Instructions d'utilisation et de sécurité

Compaq

Compaq ML350 - ProLiant - G2 Instructions d'utilisation et de sécurité

Compaq

Compaq DL320 - ProLiant - G3 Manuel

Compaq

Compaq BL10e - HP ProLiant - 512 MB RAM Manuel utilisateur

Compaq

Compaq TruCluster Server AA-RHGWC-TE Manuel utilisateur

Compaq

Compaq ProSignia 500 Mode d’emploi

Compaq

Compaq ProLiant 1000 Guide de référence rapide

Compaq

Compaq ML350 - ProLiant - G2 Manuel utilisateur

Compaq

Compaq t1000 - Terminal Thin Client PC Manuel utilisateur

Manuels Serveur populaires d'autres marques

HP AlphaServer ES47 Manuel utilisateur

Dell

Dell PowerEdge R410 Manuel utilisateur

PowerNAS

PowerNAS CMA Manuel utilisateur

Supero

Supero FatTwin F617R3-FT Manuel utilisateur

MSI

MSI P1-109N-L70 Manuel utilisateur

Dell

Dell PowerEdge XE9640 Manuel

Dell

Dell PS4100 Instructions de montage

EtroVISION

EtroVISION EV3151 Manuel utilisateur

NEC

NEC Express5800/T110j Manuel utilisateur

HP ProLiant Gen9 Manuel utilisateur

Dell

Dell PowerEdge 3YPMN Manuel utilisateur

iRobo

iRobo IPC2U Manuel utilisateur

Nortel

Nortel 1000 Con?guration guide Manuel utilisateur

Asus

Asus AP7500 Manuel d'utilisation et d'entretien

Avid Technology

Avid Technology AirSpeed 5000 Manuel utilisateur

HP Integrity rx2600 Guide d'installation

Milestone

Milestone Husky IVO 350T Manuel utilisateur

Planet

Planet NAS-7410 Manuel utilisateur