Apologies for shortage of info in original question.
1> netstat -k is undocumented.
2> the first_collision field appears to only be present for
the hme interfaces and under 2.5.1.
What I needed:
I have about 60 Ultra E3/4/5/6000s. The Ultra's ship without
le0, just the hme0. Plus each machine has an additional 3 hme's.
The site is an ISP so with HA running, the networking gets a
little scary. We felt that a register of second collisions
vs. the total would better gauge the load on the various
segements, an option which is available under HP-UX and AIX.
All I could find was this first_collision field reported
by netstat -k, but was unaware what the number represented
and/or if there was a command I didn't know of to extract
the needed info.
Thanks to;
t0152180@et.swissbank.com (perl script to compute %)
qwe0ht.eimb.rssi.ru
irac@nis.comdata.com
twhite@bear.com
casper@holland.sun.com for;
the le interface will only report one collision, then retry 16 times,
and then report another
the qe interface reports all
only hme reports "first-collissions" but that count can be 0 even
if collisions aren't. So I have no idea what they are.
Here is a small sample of what we get;
# ifconfig -a
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 172.19.60.122 netmask ffffff00 broadcast 172.19.60.255
ether 8:0:20:79:a0:be
<delete others>
# netstat -i
Name Mtu Net/Dest Address Ipkts Ierrs Opkts Oerrs Collis Queue
lo0 8232 loopback localhost 131439258 0 131439258 0 0 0
hme0 1500 172.19.60.0 lztpac02-prov 5692490 0 6824886 0 243838 0
<delete>
# netstat -k
<lots deleted>
hme0:
ipackets 5693557 ierrors 0 opackets 6826211 oerrors 0 collisions 243868
0 framing 0 crc 0 sqe 0 code_violations 0 len_errors 0
0 buff 0 oflo 0 uflo 0 missed 0 tx_late_collisions 0
retry_error 0 first_collisions 256 nocarrier 0 inits 7 nocanput 1451
allocbfail 0 runt 0 jabber 1 babble 0 tmd_error 0 tx_late_error 0
rx_late_error 0 slv_parity_error 0 tx_parity_error 0 rx_parity_error 0
slv_error_ack 0 tx_error_ack 0 rx_error_ack 0 tx_tag_error 0
rx_tag_error 0 eop_error 0 no_tmds 0 no_tbufs 0 no_rbufs 0
rx_late_collisions 0
So if you read this far, yes, I still dont know.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:16 CDT