[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | FDDI - The Next Generation |
|
| Moderator: | NETCAD::STEFANI |
|
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
1096.0. "Collision Detect Check Failures" by WRKSYS::GKELLY (Proverbs 9) Mon Sep 27 1993 12:52
Hi,
We're debugging system and/or network hesitations and delays in our
LAN. One of the observations we'd like to clear up or correct is on
and Ultrix/fddi system getting Collision Detect Check Failures. The
following is data compiled from the last reboot Friday evening.
This system utilizes DECnet and IP heavily, as both general user and
for software deveolopment. Along with heavy use of mail, nfs, and
user applications.
Any insight on underatanding these collisions is welcome.
Thanks, Gk
# ncp show known line counters | more
Known Line Volatile Counters as of Mon Sep 27 08:34:25 EDT 1993
Line = FZA-0
31477 Seconds since last zeroed
>4294967294 Bytes received
0 Bytes sent
209707292 Multicast bytes received
0 Data blocks received
133912519 Data blocks sent
1003272 Multicast blocks received
1359705 Blocks sent, initially deferred
25152176 Blocks sent, single collision
178503 Blocks sent, multiple collisions
25 Send failure, including:
Excessive collisions
Open circuit
Remote failure to defer
22813 Collision detect check failure
0 Receive re
0 Unrecognized frame destination
0 Data overrun
0 System buffer unavailable
System Info:
-----------
SYSTEM ID x82040230 HW REV: x30
FW REV: x2
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN03
MESSAGE ULTRIX V4.3 (Rev. 44) System #2: Tue
_Feb 2 16:15:29 EST 1993
DECsystem 5000 Model 240
KN03 Processor - system rev 48
64K Instruction Cache, 64K Data Cache
cpu0 ( version 3.0, implementation 2 )
fpu0 ( version 4.0, implementation 3 )
FDDI info: DEFZA-AA Hardware Rev E05
------------------------------------
fza0 at ibus1
fza0: DEC DEFZA FDDI Interface,
_hardware address 08:00:2b:1d:66:22
_ROM rev 1.0 Firmware rev 1.2
ln0 is terminated:
-----------------
ln0 at ibus3
ln0: DEC LANCE Ethernet Interface,
_hardware address: 08:00:2b:2e:76:2a
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1096.1 | | KONING::KONING | Paul Koning, A-13683 | Mon Sep 27 1993 15:10 | 4 |
| Since FDDI is not Ethernet, those counters are obviously nonsense. I can't
understand why Ultrix would report them.
paul
|
| 1096.2 | | UPSAR::THOMAS | The Code Warrior | Mon Sep 27 1993 17:39 | 5 |
| ULTRIX Phase IV barely supports FDDI (it allows you to turn on the
circuit and that's it).
The counters are bogus. To get the real counters, use
netstat -I fza0 -s
|
| 1096.3 | that looks better | WRKSYS::GKELLY | Proverbs 9 | Tue Sep 28 1993 10:33 | 79 |
| RE: The counters are bogus. To get the real counters, use
netstat -I fza0 -s
Must have missed README #209485.
Thanks, Gk
fza0 FDDI counters at Tue Sep 28 07:21:57 1993
47993 seconds since last zeroed
4294967295 ANSI MAC frames count
0 ANSI MAC frame errors
0 ANSI MAC frames lost
1202516158 bytes received
973354966 bytes sent
3677803 data blocks received
3921987 data blocks sent
36731218 multicast bytes received
270723 multicast blocks received
2243648 multicast bytes sent
31018 multicast blocks sent
0 transmit underrun errors
0 send failures
0 FCS check failures
0 frame status errors
0 frame alignment errors
0 frame length errors
0 unrecognized frames
0 unrecognized multicast frames
0 receive data overruns
0 system buffers unavailable
0 user buffers unavailable
0 ring reinitialization received
0 ring reinitialization initiated
0 ring beacon process initiated
0 duplicate tokens detected
0 duplicate address test failures
0 ring purge errors
0 bridge strip errors
0 traces initiated
0 traces received
0 LEM reject count
0 LEM events count
0 LCT reject count
0 TNE expired reject count
1 Completed Connection count
0 Elasticity Buffer Errors
fza0 FDDI status
Adapter State: Running State
LED State: Green
Link State: On Ring Running
Duplicate Address Condition: Absent
Ring Purger: Purger off
Negotiated TRT: 7.987 ms
Upstream Neighbor Address: 08-00-2B-2B-84-99
UNA Timed Out: False
Claim Token Yield: False
Frame Strip Mode: Bridge Strip
Ring Error Reason: No Reason
Last Direct Beacon SA: 00-00-00-00-00-00
Physical Port State: In Use
Neighbor Physical Port Type: Master
Reject Reason: No Reason
Physical Link Error Estimate: 15
fza0 FDDI characteristics
Link Address: 08-00-2B-1D-66-22
Firmware Revision: 1.2
ROM Revision: 1.0
SMT Version ID: 1
Requested TRT: 8.000 ms
Maximum TRT: 173.015 ms
Valid Transmission Time: 2.621 ms
LEM Threshold: 8
PMD Type Multimode
|