Hello Folks @ 3000-l,

Re: linkcontrol @;status=all - Are these stats okay?

linkcontrol @;status=all
Linkname: LANLINK   Linktype: IEEE8023  Linkstate: CONNECTED
Physical Path:              56/56
Current Station Address:    00-60-B0-56-36-B6
Default Station Address:    00-60-B0-56-36-B6
Current Receive Filter:     broad(1) any(0) k_pckts(1) x_pckts(0)
Current Multicast Addresses:
 09-00-09-00-00-01  09-00-09-00-00-03  09-00-09-00-00-04
 09-00-09-00-00-06
Transmits no error     13166361  Receives no error     15086523
Transmit byte count  1016436068  Receive byte count  2518317170
Transmits error               1  Receives error          153058
Transmits deferred         5936  Carrier losses               1
Transmits 1 retry           581  CRC errors              153058
Transmits >1 retry          217  Frame losses                 0
Trans 16 collisions           0  Whole byte errors       138925
Trans late collision          0  Size range errors            0
802 chip restarts             0  Receives dropped             0
Heartbeat losses              1  Receives broadcast     2124099
                                 Receives multicast           0

Well, the answer is it depends... truthfully the statistics are really
of little value unless you are able to define "time".  Specifically
what is the time frame since the statistics have been collected.
Secondly what out of 'normal' operation has taken place on the physical
link segment during the collection period.

Concerns:

Transmits error               1
Heartbeat losses              1

Receives error          153058
Carrier losses               1
CRC errors              153058
Whole byte errors       138925

All of these statistics indicate a physical cable/wire problem.  In a
controlled environment over a defined time period I would be concerned.

Heartbeat losses & Carrier losses indicate to me a physical cable/wire
problem - i.e. a loss of electrical signal, electrical open condition or
significant variation from expected electrical current levels.

Transmits error, Receives error, CRC errors, Whole byte errors indicate
to me data corruption is detected at the physical cable/link level.

Why is it important to view these statistics in a controlled environment
over a defined time period ?   These statistics are "NOT" unexpected if
you are adding, removing or doing hardware maintenance to any devices
physically attached to the physical cable/wire segment the HP-e3K is
connected to.  Secondly it is important to evaluate these statistics in
relationship (ratio) to the number of "Transmits no error" and
"Receives no error".

One of the tools I use to monitor these statistics when I begin trouble
shooting a possible link problem is to setup a monitor job which records
the link data and defines "time".

notes:

This tool writes the link output to a file nwmono.net.sys

Modify line #1 to include your passwords

Modify lines #17 thru #20 to include the names of your links.
Note: you can get the names of your links by performing a
:linkcontrol @;status=all

Modify line #22 to define your "time".  The pause value is in
seconds... I have specified 3600 seconds = 60 minutes.

/t nwmon.net.sys
FILE UNNUMBERED
/l all
    1     !job nwmon,manager/pass.sys/pass,net;outclass=,1
    2     !comment
************************************************************
    3     !comment * This job nwmon.net.sys collects linkcontrol & resource
    4     !comment * data which is stored to nwmonO.net.sys
    5     !comment
************************************************************
    6     !continue
    7     !purge nwmono.net.sys
    8     !continue
    9     !build nwmono.net.sys;dev=disc;rec=-78,1,f,ascii;disc=1000000
   10     !file nwmono=nwmono.net.sys,old
   11     !showtime > *nwmono
   12     !setvar test true
   13     !while test
   14     !echo --------------------------- >> *nwmono
   15     !showtime >> *nwmono
   16     !echo --------------------------- >> *nwmono
   17     !linkcontrol syslink;status=diag >> *nwmono
   18     !linkcontrol syslink;status=reset
   19     !linkcontrol bt100lnk;status=diag >> *nwmono
   20     !linkcontrol bt100lnk;status=reset
   21     !run nettool.net.sys;info="res;di;quit" >> *nwmono
   22     !pause 3600
   23     !endwhile
   24     !eoj

The output "nwmono.net.sys" now gives you the statistic data and the time
which supports your further sleuthing to identify "root cause" of a problem
or if a problem really exist.

I hope this helps

Regards,

James Hofmeister
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *