| 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 |
Hello..
I had a problem on 1 vax cluster node where all the protocols except
TCP/IP stopped working on the fddi. (decnet,lat,lavc) stopped. There
were no apparent errors. The customer restarted lavc (now on the ethernet)
shutdown and restarted decnet on the FDDI ok. Lat and last wouldnt run
so the system was rebooted. No dump. Vms version is A5.5-1. I dont have
any driver versions yet, but has anything like this been seen? The odd
thing is that IP kept running on the fddi.
Thanks
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1281.1 | FDDI protocols stopped for me too! | CHEFS::MOAKESR | Fri Apr 18 1997 13:03 | 13 | |
I have just gone through the same experience on a trihost OpenVMS Alpha
V 6.1 cluster.
All protocols stopped, in fact TCP/IP stopped until the shutdown was
initiated, then only TCP/IP came back.
After the reboot, everything was just fine.
Any thoughts anyone?
Richard Moakes
Managed Services - Glaxo Wellcome
| |||||
| 1281.2 | STAR::STOCKDALE | Fri Apr 18 1997 14:17 | 11 | ||
>> Any thoughts anyone? Crash the system when it is in this state and look at the dump. You should be able to look at the LAN data for the device, via SHOW LAN/FULL and SHOW LAN/TIME to see what happened recently, whether any errors were detected, or timeouts, or ring events. The same thing can be done with the base note in spite of the two completely different hardware configurations, one Alpha and one VAX. - Dick | |||||