| 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 |
dear readers, i have a customer with thirty systems on an FDDI ring with a synoptics concentrator. twice now, he has lost all network communications on 10 of the 30 systems. rcinet restart did not get the network connection back, he had to reboot the systems. 9 of the 10 'network down' systems were running digital unix V3.2c with eisa fddi controlers (DEFEA-AA / rev 2.46). the /var/adm/messages file from one of the systems looks like this.. Nov 26 16:06:28 sap005 vmunix: fta0: Link transmit failure Nov 26 16:06:28 sap005 vmunix: fta0: PC Trace received Nov 26 16:06:28 sap005 vmunix: fta0: Ring beacon initiated Nov 26 16:06:28 sap005 vmunix: fta0: Elasticity buffer error Nov 26 16:06:28 sap005 vmunix: fta0: Link Unavailable. Nov 26 16:06:28 sap005 vmunix: fta0: Halted. Nov 26 16:06:28 sap005 vmunix: fta0: Halt Reason: PC Trace Nov 26 16:06:28 sap005 vmunix: fta0: Link Unavailable. Nov 26 16:06:28 sap005 vmunix: fta0: Link Available. Nov 26 16:06:28 sap005 vmunix: fta0: Link Unavailable. Nov 26 16:06:28 sap005 vmunix: fta0: Link Available. Nov 26 16:06:28 sap005 vmunix: NFS2 server chccl2 not responding still trying Nov 26 16:06:28 sap005 vmunix: NFS3 server sap001f not responding still trying has anyone heard of this problem? any clues on where to start looking?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1886.1 | NETCAD::STEFANI | Machines to humanize | Thu Nov 30 1995 10:17 | 6 | |
>>Nov 26 16:06:28 sap005 vmunix: fta0: PC Trace received
I'd get someone with (and who knows how to use) an FDDI network
analyzer. PC Trace events are indications of a "sick" ring.
/l
| |||||
| 1886.2 | one more time on your thoughts please.. | CSC32::J_WIELAND | Fri Dec 01 1995 08:36 | 12 | |
More Information,
Customer agrees that the ring was sick, they were doing some work on
it and the ring was 'taken down'. His concern is why when the ring
was brought back up, the digital unix systems did not recover from the
sick condition of the ring, and instead had to be rebooted to start
talking again on the fddi ring..?
Any input really appreciated...
john wieland
customer support center
colorado springs, colorado
| |||||