| 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 |
VMS 5.5
DECmcc T1.2.4
FDDI Ring Map FM T1.2.4
The DECmcc Autotopology option works fine ( see below files
MCC_FDDI_FM_FDDI_RING_MAP_AUTOREG.LOG and MCC_FDDI_FM_MESSAGES.LOG )
... until I try to use the new created FDDI entities.
Whatever entity selected ( DECconcentrator500, DECbridge500 or 600 ),
the SHOW directive displays the following error message :
"The MCC_COMMON:MCC_LAN_AUTOTOLOGY.DAT can not be accessed"
( it's not a mistake : AUTOTOLOGY is displayed instead of
AUTOTOPOLOGY !!! ).
Where does this file come from ? The only reference I found was in
the DEC ELM T1.2.4 release notes where it is mentionned that :
"Only one SMT gateway can be specified for a domain in the
MCC_LAN_AUTOTOPOLOGY.DAT file".
and later in the list of Error Messages (E) :
"Autotopology file MCC_LAN_AUTOTOPOLOGY.DAT does not exist
in MCC_COMMON".
Why can't I find this message in my MCC_FDDI_FM_MESSAGES.LOG file ?
Can I provide a MCC_LAN_AUTOTOPOLOGY.DAT by myself ? And if yes, what
kind of informations have I to supply ?
Guy.
------------------------------------------------------------------------------
$ type MCC_FDDI_FM_MESSAGES.LOG
KBANON>ty MCC_FDDI_FM_MESSAGES.LOG;4
*** STARTING FDDI AUTOMAP ***
(I) Domain=KBANON_NS:.fddi_ring_map, Autoreg=1, Reset=0, Gw=08-00-2B-19-85-4A (
M08002B19854A), Start=08-00-2B-19-85-4A (M08002B19854A)
(I) >autoregistration file: added node M08002B18A911
(I) >autoregistration file: added member M08002B18A911
(I) >autoregistration file: added node M08002B1E45C3
(I) >autoregistration file: added node M08002B14D691
(I) >autoregistration file: added node M08002B14D244
(I) >autoregistration file: added node M08002B19854A
(I) >autoregistration file: added node M08002B25CCD9
(I) >autoregistration file: added node M08002B198D45
(I)
(I) ---- Map ring is complete ----
(I) Spawning autoregistration process.
(W) Check status in the autoregistration log file
(I) FDDI ring Map completed successfully.
$
$
$
$ type MCC_FDDI_FM_FDDI_RING_MAP_AUTOREG.LOG
$ ON ERROR THEN CONTINUE
$ MANAGE/ENTERPRISE
DECmcc (T1.2.4)
REGISTER FDDI M08002B18A911 ADDRESS=08-00-2B-18-A9-11
FDDI KBANON_NS:.M08002B18A911
AT 12-MAR-1992 09:08:44
Registration Successful
CREATE DOMAIN KBANON_NS:.fddi_ring_map MEMBER M08002B18A911
Domain KBANON_NS:.fddi_ring_map Member KBANON_NS:.M08002B18A911
AT 12-MAR-1992 09:08:50
Create Successful
REGISTER FDDI M08002B1E45C3 ADDRESS=08-00-2B-1E-45-C3
FDDI KBANON_NS:.M08002B1E45C3
AT 12-MAR-1992 09:08:52
Registration Successful
CREATE DOMAIN KBANON_NS:.fddi_ring_map MEMBER M08002B1E45C3
Domain KBANON_NS:.fddi_ring_map Member KBANON_NS:.M08002B1E45C3
AT 12-MAR-1992 09:08:56
Create Successful
REGISTER FDDI M08002B14D691 ADDRESS=08-00-2B-14-D6-91
FDDI KBANON_NS:.M08002B14D691
AT 12-MAR-1992 09:08:57
Registration Successful
CREATE DOMAIN KBANON_NS:.fddi_ring_map MEMBER M08002B14D691
Domain KBANON_NS:.fddi_ring_map Member KBANON_NS:.M08002B14D691
AT 12-MAR-1992 09:09:01
Create Successful
REGISTER FDDI M08002B14D244 ADDRESS=08-00-2B-14-D2-44
FDDI KBANON_NS:.M08002B14D244
AT 12-MAR-1992 09:09:02
Registration Successful
CREATE DOMAIN KBANON_NS:.fddi_ring_map MEMBER M08002B14D244
Domain KBANON_NS:.fddi_ring_map Member KBANON_NS:.M08002B14D244
AT 12-MAR-1992 09:09:10
Create Successful
REGISTER FDDI M08002B19854A ADDRESS=08-00-2B-19-85-4A
FDDI KBANON_NS:.M08002B19854A
AT 12-MAR-1992 09:09:11
Registration Successful
CREATE DOMAIN KBANON_NS:.fddi_ring_map MEMBER M08002B19854A
Domain KBANON_NS:.fddi_ring_map Member KBANON_NS:.M08002B19854A
AT 12-MAR-1992 09:09:15
Create Successful
REGISTER FDDI M08002B25CCD9 ADDRESS=08-00-2B-25-CC-D9
FDDI KBANON_NS:.M08002B25CCD9
AT 12-MAR-1992 09:09:16
Registration Successful
CREATE DOMAIN KBANON_NS:.fddi_ring_map MEMBER M08002B25CCD9
Domain KBANON_NS:.fddi_ring_map Member KBANON_NS:.M08002B25CCD9
AT 12-MAR-1992 09:09:20
Create Successful
REGISTER FDDI M08002B198D45 ADDRESS=08-00-2B-19-8D-45
FDDI KBANON_NS:.M08002B198D45
AT 12-MAR-1992 09:09:22
Registration Successful
CREATE DOMAIN KBANON_NS:.fddi_ring_map MEMBER M08002B198D45
Domain KBANON_NS:.fddi_ring_map Member KBANON_NS:.M08002B198D45
AT 12-MAR-1992 09:09:26
Create Successful
EXIT
$
$
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2548.1 | QUIVER::CHILDS | Ed Childs | Thu Mar 12 1992 10:57 | 39 | |
| Whatever entity selected ( DECconcentrator500, DECbridge500 or 600 ),
| the SHOW directive displays the following error message :
| "The MCC_COMMON:MCC_LAN_AUTOTOLOGY.DAT can not be accessed"
| ( it's not a mistake : AUTOTOLOGY is displayed instead of
| AUTOTOPOLOGY !!! ).
The error message prints the wrong file name. It's really looking for
MCC_COMMON:MCC_AUTOTOPOLOGY.DAT.
| Where does this file come from ?
I believe the installation procedure should put one there. If not,
you'll need to create one.
| Can I provide a MCC_LAN_AUTOTOPOLOGY.DAT by myself ? And if yes, what
| kind of informations have I to supply ?
Yes, you need to create one for your FDDI environment. This file is a
text file containing two items on each line: a domain name, and a
gateway name. The gateway name can be the physical address of the SMT
gateway (i.e., 08-00-2B-11-22-33) or a name that has been registered as
an FDDI entity (register fddi bridge500 address 08-00-2B-11-23-33).
Example: You have a DECbridge 500 and a DECbridge 620 in your FDDI
environment. The 500 is on a ring which contains items in a domain
called FDDI_NORTH, the 600 is on a ring called FDDI_SOUTH. The correct
MCC_LAN_AUTOTOPOLOGY.DAT file would look like this:
--------------------------------------------------------------------------------
FDDI_NORTH BRIDGE500
FDDI_SOUTH BRIDGE620
--------------------------------------------------------------------------------
Note that BRIDGE500 and BRIDGE620 are registered FDDI entities.
You will then be able to issue commands like this:
MCC> show fddi bridge500 sif config all char, in domain fddi_north
/* Ed */
| |||||
| 2548.2 | PRSSOS::BONNAFE | Guy BONNAFE - CSC France | Fri Mar 13 1992 04:35 | 10 | |
Thanks Ed, it works fine now. Anyway, if customers have to create files for their FDDI environment, it would be interesting either supply a template in the ELM kit or insert a few comments in the release notes. Regards, Guy. | |||||
| 2548.3 | QUIVER::HAROKOPUS | Mon Mar 23 1992 10:13 | 7 | ||
Hi Guy, Thanks for your comments on the confusion over the FDDI file. We have since updated the FDDI FM and FDDI AM Use Guides to explain the need for and how to build this file more clearly. Bob | |||||
| 2548.4 | Can't find mcc_fddi_fm_hlo_<domain>_autoreg.com | CADSYS::LEMONS | And we thank you for your support. | Fri Aug 14 1992 12:57 | 52 |
I'm trying to use the FDDI Ring Map application. I have installed the
MCCELMFM012 savesets. The installation didn't produce any errors.
Yet, when I try to perform an autoregistration, I get:
MCC> AUTOREGISTER MCC 0 FDDI_FM ,IN DOMAIN=.hlo_fddi_test
*** STARTING FDDI AUTOREGISTER ***
autoregistration: : no such file or directory
(E) Error opening autoregistration script file mcc_fddi_fm_hlo_fddi_test_autor
eg.com.
MCC 0 FDDI_FM
AT 14-AUG-1992 11:57:18
Autoregistration Failed.
A manage/tool/diction show the following subclasses:
Subclass (2) : ALARMS 1
Subclass (2) : HISTORIAN_FM 4
Subclass (2) : DNA4_AM 5
Subclass (2) : BRIDGE_AM 6
Subclass (2) : ETHERNET_AM 7
Subclass (2) : SAMPLE_AM 8
Subclass (2) : DNA5_AM 10
Subclass (2) : REGISTRATION_FM 13
Subclass (2) : FCL 14
Subclass (2) : TERMSERVER_AM 15
Subclass (2) : TCPIP_AM 17
Subclass (2) : ICONICMAP 18
Subclass (2) : EXPORTER_FM 19
Subclass (2) : NOTIFICATION_FM 20
Subclass (2) : DOMAIN_FM 25
Subclass (2) : PA 33
Subclass (2) : CIRCUIT_AM 34
Subclass (2) : FDDI_AM 35
Subclass (2) : FDDI_FM 36
Subclass (2) : STM_FM 37
Subclass (2) : COLLECTION_AM 123
Subclass (2) : CONC_AM 302
Subclass (2) : REFERENCE_FM 893
I've read the appropriate sections in the Autotopology manual, and can't figure
out what's wrong.
Thanks,
tl
| |||||
| 2548.5 | Autoregister only works after automap is run for FDDI FM | QUIVER::HAROKOPUS | Fri Aug 14 1992 14:01 | 18 | |
For the FDDI FM (unlike the STM FM), the automap directive must be run prior to autoregister. In fact, you can build the ring map and register everything with just the automap command. The purpose of the autoregister directive is to execute the autoregistration script (generated by automap) if the user selected automap without autoregistration. This was implemeted this way because with FDDI you must walk the entire ring (and thus build the topology) to autodiscover all of the stations. So it doesn't make sense to have the autoregister directive do the same thing as automap. The STM FM has a listener for bridge autodiscovery so it is possible to register the bridges without building the topology. Bob | |||||