| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
From a friend of mine:
We were/are using Polycenter Extended LAN Manager (AM&FM) V1.3
in our three DSSI node VAX4500/VMS V5.5-2H4 cluster for a longer
period of time.
Recently I installed a FDDI interface (DEFQA) in all three VAXes
to connectem directly into the FDDI ring. Everything works fine.
Extended LAN Manager(AM&FM) can see FFDI bridge, concentrator etc.
Then I switched DECNET traffic from the ethernet interface (DEFTA)
ovet to the FDDI interface DEFQA. Everything runs faster as it
should be.
Only Extended LAN Manager (AM&FM) does not run any more i.e. when-
ever I try to see the FDDI bridge I get the following error :
%MCC-F-STRTDEVERROR, start Ethernet device failed
%SYSTEM-F-TIMEOUT, device timeout
I think, correct me if I am wrong, that Extended LAN Manager can NOT
use DECNET over an FDDI circuit i.e. it can use DECNET only over
the Ethernet device. Hence the error message. ?
We want to keep DECNET on FDDI circuit. So, how can we run Extended
LAN Manager in this situation ? Is there anything I can do to make
ELMS run over FDDI ?
Any help?
Thanks
Guenther
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 6401.1 | use the via port qualifier | CSC32::KEANE | Scott Keane - MCI MCT - 592-7310 | Thu Nov 09 1995 20:38 | 8 |
Try the command with something like the following... mcc> show bridge 08-00-2b-xx-xx-xx all status, via port fqa0: Your fddi controller may have a different designation. The : is necessary. Scott | |||||
| 6401.2 | AZUR::DURIF | Fri Nov 10 1995 10:45 | 12 | ||
Hi Guenther, I do not know much about DECnet over FDDI but you may check if some FDDI entity may be managed unser the NODE global class (= phase V node). if your request is to be managed by the Phase V agent, the NODE class is to be used at MCC level. Hope this helps, Benoit | |||||
| 6401.3 | this rings a bell .. | CSC32::PRICE | Thu Nov 16 1995 22:48 | 14 | |
Is this not the same as the Ultrix Bridge access module problem on a
dual interface machine. The access module uses the first network
controller it can find, which sometimes is not the correct one, so in a
dual controller configuration you *have* to specify which interface
you wish to use with the "via port" qualifier. I believe there is
already a note about this, as I've encountered it myself. But not on
VMS yet. If this is the same, note that you cannot set the "via port"
information permanently.
Regards, Conrad
| |||||