| 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 |
First a little background, 2 - clustered 6510, running VMS T5.4-3, both CPUs have DEMFA FDDI controllers, DECmcc and MAKO FT software as well as ELMS V1.1. On one system he can start the ELMS listener, on the other he cannot, gets a 'failed to start listener'. Investigation shows that on the system that fails he has 18 - EX devices. using 'sho lan' in SDA 9 of the EX devices are using MOP-RC, the same protocol that the listener is trying to use. There are supposedly no other processes (TSM, Ethernim, etc) running that would use MOP-RC. The question in this case being, is there any way to trace back the existing EX devices to a process that would have started MOP-RC, and if the process is gone is there a way to make the EX device disappear gracefully? Also any ideas as to why they would stick around in the first place? On the system where he can start the listener there are no EX devices using MOP-RC until he does start the listener. Steve Woestemeyer CSC/CS - NSU/LAT
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 293.1 | Owner field in UCB | MARVIN::DAVISON | Eric Davison | Thu Jul 04 1991 09:16 | 10 |
These mysterious EXA devices presumably have a non-zero owner PID field in the UCB ? (SHOW DEVICE/FULL EXA from DCL or SHOW DEV EX in SDA). This field should indicate the process that started the MOP-RC protocol. If the field is zero then either the process has succesfully deallocated the device but the driver hasn't deleted the UCB (presumably because some resource is still outstanding - normally IO queued to the device which you might get some information on from SDA SHOW DEV) or the device is owned by non-process code. Eric | |||||
| 293.2 | Some help maybe | STAR::SALKEWICZ | It missed... therefore, I am | Mon Jul 08 1991 15:43 | 22 |
Something very similar to this is in one of my QARs right now.
I'd appreciate your creating a dump and filing it with another
QAR.
In the meantime,.. we have a couple new SDA commands with 5.4-3
that you folks might be interested in,... like:
SDA> SHOW LAN
SDA> SHOW LAN/DEV=[ES,ET,EX,EZ,FX,XE,XQ]
SDA> SHOW LAN /FULL
SDA> SHOW LAN /TIME
SDA> SHOW LAN /COUNT
Various combos of qualifiers will and will not work. You will find
that these commands provide a much better picture of the Ethernet/FDDI
stuff at the datalink layer than the old SDA> SHOW DECNET/DATALINK did.
And whats more,.. they actually work.
Your milage may vary,.. Unsupported etc. etc.
/Bill
| |||||