[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 |
1046.0. "FCA-0 Circuit bounce " by GIDDAY::CHONG (Andrew Chong - Sydney CSC ) Tue Aug 03 1993 06:31
Circuit FZA-0 intermittently experiencing circuit bounce and sometimes
circuit up event without a circuit down event.
These events (4.7 and 4.10) are almost always preceeded by an event 0.7
Message from user DECNET on PV05
DECnet event 0.7, aborted service request
From node 1.45 (PV05), 2-AUG-1993,19:35:02.39
Circuit FZA-0, Receive error
The reality is there were no service request at the time .
Although the circuit up event does not affect decnet traffic as such,
there are lots and lots of adjacency up events following the circuit up.
The node (PV05) is an MCC station and alarms are being fired and pagers being
send all over the place creating quite abit of nuisense
The other observation which may be relevant to the problem is that
the DECcontrator 500 physical port "LEM Link Errors" increment from 50 to 112
and "link error rate" changes from 12 to 8 at the time around the circuit
bounce.
Appreciate if anyone can offer some advise on isolating this problem.
The hardware associated with the FDDI (controller, concentrator) were replaced
by the hardware engineer to try and isolate the problem.
Driver and NCP line information
----------------------------
Image Identification Information
image name: "FCDRIVER"
image file identification: "X-7"
link date/time: 17-MAR-1993 12:25:46.13
linker identification: "05-13"
Image Identification Information
image name: "NETDRIVER"
image file identification: "X-39"
link date/time: 22-SEP-1992 11:13:06.41
linker identification: "05-13"
Image Identification Information
image name: "NETACP"
image file identification: "X-13A3"
link date/time: 8-JUL-1992 01:32:09.17
linker identification: "05-13"
Line = FZA-0
>65534 Seconds since last zeroed
8603946 Data blocks received
7471411 Multicast blocks received
0 Receive failure
1036863929 Bytes received
921604994 Multicast bytes received
0 Data overrun
1165576 Data blocks sent
82326 Multicast blocks sent
111282731 Bytes sent
15961165 Multicast bytes sent
0 Send failure
869 Unrecognized frame destination
0 System buffer unavailable
0 User buffer unavailable
>4294967294 MAC frame count
0 MAC error count
0 MAC lost count
1 Ring initializations initiated
2 Ring initializations received
1 Ring beacons initiated
0 Duplicate address test failures
0 Duplicate tokens detected
0 Ring purge errors
0 FCI strip errors
0 Traces initiated
0 Traces received
0 Directed beacons received
0 Elasticity buffer errors
0 LCT rejects
0 LEM rejects
0 Link errors
2 Connections completed
Line = FZA-0
Receive buffers = 10
Controller = normal
Protocol = FDDI
Service timer = 4000
Hardware address = 08-00-2B-32-68-58
Device buffer size = 1498
Requested TRT = 8000
Valid transmission time = 2620
Restricted token timeout = 1000
Ring purger enable = on
Echo data = 55
Echo length = 1
SYSGEN> SH LRPSIZE
Parameter Name Current Default Min. Max. Unit Dynamic
-------------- ------- ------- ------- ------- ---- -------
LRPSIZE 4542 1504 256 16384 Bytes
Large Packet (LRP) Lookaside List Packets Bytes Pages
Current Total Size 260 1272960 2487
Initial Size (LRPCOUNT) 260 1272960 2487
Maximum Size (LRPCOUNTV) 1040 5091840 9945
Free Space 204 998784
Space in Use 56 274176
Packet Size/Upper Bound (LRPSIZE + 354) 4896
Lower Bound on Allocation 1088
Andrew
**** Cross posted in BULEAN::DECNETVAX ***
T.R | Title | User | Personal Name | Date | Lines |
---|
1046.1 | | KONING::KONING | Paul Koning, A-13683 | Tue Aug 03 1993 12:00 | 9 |
| The LEM Link Errors indicates a problem with the signal from the workstation
to the concentrator. Did the "LEM rejects" counter increment? That indicates
that the direct cause of the circuit-down was the error rate.
You should check the entire signal path between the two points: not just the
adapter and concentrator ports but also (or especially) the cabling between
them.
paul
|