| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2016.1 | | QUIVER::CHILDS | Ed Childs | Thu Jan 02 1992 13:10 | 59 |
| Problem #2 sounds like the cause. (Maybe an out-of-date
MCC_DISPATCH_TABLE in MCC_SPECIFIC.) Please check it out.
We are including this sheet in the FT kits.
************************************************************
DECMCC ELM FIELD TEST
COMMON INSTALLATION PROBLEMS AND HOW TO AVOID THEM
************************************************************
There are two common setup problems which will prevent successful
installation of the DECmcc ELM T1.2 kit. Please take a moment to
verify that your MCC environment is setup correctly before attempting
the installation.
(1) NO MCC PROCESS LOGICAL NAMES SHOULD BE DEFINED
Type the following command to check if there are process logical names
defined that could adversely affect your installation:
$ SHOW LOGICAL MCC* /PROCESS
Any that are listed should be deassigned.
$ DEASSIGN MCC_ICONS
$ DEASSIGN MCC_SYSTEM
Verify that MCC system logical names are correctly defined. They
should point to valid disk and directory locations. Type this command
to verify them:
$ SHOW LOGICAL MCC* /SYSTEM
(2) DELETE OUT-OF-DATE FILES FROM MCC_SPECIFIC
The DECmcc ELM installation procedure does not place any files in the
MCC_SPECIFIC area. Since MCC_SPECIFIC is first on the search list of
the MCC_SYSTEM logical name, it is important that there are no
out-of-date files in that location. The DECmcc BMS Field Test files
are dated 8-DEC-1991. Check the date of all files in your MCC_SPECIFIC
area, and delete any that are older than 8-DEC-1991. You can verify
the dates with this command:
$ DIRECTORY /DATE MCC_SPECIFIC:
It is likely that there are no files at all in the MCC_SPECIFIC
directory. This is also normal.
Thank you for interest in DECmcc ELM.
LAN Software Development
Digital Equipment Corporation
2 January 1992
|
| 2016.2 | Aother failure installing ELM | WRK4ME::LUND | "Oh sure now it's working !" | Wed Jan 08 1992 12:27 | 219 |
|
I attached the vmsinstal listing. Was installed on a VS3100 M38, 16mb
VMS 5.4-3 DECmcc EFT 1.2.4
The following products will be processed:
MCCELMT V1.2
Beginning installation of MCCELMT V1.2 at 11:31
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.
************************************************************
* *
* DECmcc Extended LAN Manager *
* T1.2.4 *
* *
* Installation Procedure *
* *
************************************************************
NOTE: The Field Test Software for DECmcc ELM T1.2.4
requires that three (3) licenses be loaded on
your system:
DECMCC-BMS
DECMCC-ELM-AM-V
DECMCC-ELM-FM-V
* Do you presently have DECmcc BMS T1.2.4 installed [YES]?
Product: DECMCC-ELM-AM-V
Producer: DEC
Version: 1.2
Release Date: 16-FEB-1992
* Does this product have an authorization key registered and loaded? y
Product: DECMCC-ELM-FM-V
Producer: DEC
Version: 1.2
Release Date: 16-FEB-1992
* Does this product have an authorization key registered and loaded? y
* Do you want to run the DECMCC ELM IVP after the installation [YES]?
* Do you want to purge files replaced by this installation [YES]?
VMSINSTAL asks no additional questions.
%VMSINSTAL-I-RESTORE, Restoring product save set B ...
Following the copying of the files, the DECmcc ELM
start-up command procedure(s) will be invoked. Operational
tables will be created by this procedure.
To automatically set up DECmcc ELM on your system,
edit your local system start-up command procedure
SYS$MANAGER:SYSTARTUP_V5.COM
so that it invokes the DECmcc ELM start-up command
procedure. Add:
@SYS$STARTUP:MCC_STARTUP_ELM.COM
after the statement that invokes the DECmcc BMS start-up
command file (MCC_STARTUP_BMS.COM)
Following the DECmcc ELM start-up the DECmcc ELM
post install command procedure will be invoked.
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
Beginning DECmcc ELM Post Installation Procedure ...
Using dictionary file: USER1:[MCC]MCC_FDICTIONARY.DAT;2
DECmcc Dictionary Administrator Program Version T1.2.4
%DAP-I-CMD_FILE, Command file: mcc_bridge_am_svc_if.com
%DAP-I-CMD_FILE, Command file: mcc_bridge_am_mgt_if.com
%DAP-I-CMD_FILE, Command file: mcc_conc_am_svc_if.com
%DAP-I-CMD_FILE, Command file: mcc_conc_am_mgt_if.com
%DAP-I-CMD_FILE, Command file: mcc_fddi_am_svc_if.com
%DAP-I-CMD_FILE, Command file: mcc_fddi_am_mgt_if.com
%DAP-I-CMD_FILE, Command file: mcc_stm_fm_mgmt_if.com
%DAP-I-CMD_FILE, Command file: mcc_fddi_fm_mgmt_if.com
%DAP-I-CMD_FILE, Command file: mcc_lan_topology_mgt_if.com
%DAP-I-CMD_FILE, Command file: MCC_BRIDGE_LINE_STATISTICS.COM
Using parse table log file: USER1:[MCC]MCC_FDICTIONARY.LOG;1
Reading parse table file: USER1:[MCC]MCC_FDICTIONARY.BPT;2
lease wait while dictionary files are updated
Processing entity 9
Processing entity 9 11
Processing entity 9 11 44
Processing entity 9 11 45
Processing entity 9 11 46
Processing entity 9 12
Processing entity 9 21
Processing entity 9 21 37
Processing entity 9 21 48
Processing entity 9 21 49
Processing entity 9 47
Processing entity 7 6
Processing entity 7 302
Processing entity 7 1991
Processing entity 7 2364
Processing entity 7 2365
Processing entity 7 18 500 504
Processing entity 330
Processing entity 330 1
Processing entity 330 2
Processing entity 9815
Processing entity 9815 1
Processing entity 9815 2
Processing entity 9815 3
Writing parse table file: USER1:[MCC]MCC_FDICTIONARY.BPT;3
Parse table build complete.
DECmcc Help File Builder
Component Version: T1.2.4
Processing file USER1:[MCC]MCC_ALARMS_FM.HELP
Processing file USER1:[MCC]MCC_BRIDGE_AM.HELP
Processing file USER1:[MCC]MCC_CIRCUIT_AM.HELP
Processing file USER1:[MCC]MCC_COLLECTION_AM.HELP
Processing file USER1:[MCC]MCC_CONC_AM.HELP
Processing file USER1:[MCC]MCC_CONTROL_FM.HELP
Processing file USER1:[MCC]MCC_DNA4_AM.HELP
Processing file USER1:[MCC]MCC_DNA5AM_HELP.HELP
Processing file USER1:[MCC]MCC_DOMAIN_FM.HELP
Processing file USER1:[MCC]MCC_ENET_AM.HELP
Processing file USER1:[MCC]MCC_EXPORTER_HELP.HELP
Processing file USER1:[MCC]MCC_FDDI_AM.HELP
Processing file USER1:[MCC]MCC_FDDI_FM.HELP
Processing file USER1:[MCC]MCC_GENERAL_HELP.HELP
Warning - The first character in a line cannot contain a number.
The following line will not be processed:
75 percent of the y axis.
Processing file USER1:[MCC]MCC_HISTORIAN_HELP.HELP
Processing file USER1:[MCC]MCC_KERNEL_AM.HELP
Processing file USER1:[MCC]MCC_NOTIFICATION_FM.HELP
Processing file USER1:[MCC]MCC_PA_FM.HELP
Processing file USER1:[MCC]MCC_STM_FM.HELP
Processing file USER1:[MCC]MCC_TCPIP_AM.HELP
Processing file USER1:[MCC]MCC_TRANSLAN_AM.HELP
Sorting character cell help topics.
Sorting windows help topics.
Verifying hierarchy...
Verifying for character cell
Verifying for windows
Processing file(s)....
MCC help files updated.
MCC help files updated.
Cleaning up intermediate files.
The MCC_STARTUP_ELM startup procedure for DECmcc T1.2.4 is now running.
Note: The DECmcc Director and BMS, SMS or EMS Startup procecures
should be run prior to executing this procedure.
DECmcc (T1.2.4)
%MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced
%MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced
The MCC_STARTUP_ELM startup procedure for DECmcc T1.2.4 is now ending.
Completing DECmcc ELM Post Installation Procedure ...
Beginning DECmcc ELM Installation Verification Procedure
The IVP for DECmcc ELM will now be run.
DECmcc (T1.2.4)
%MCC-E-ATTRNOTALLOW, no attribute or argument allowed
The following command failed.
"MANAGE/ENTERPRISE TEST MCC 0 BRIDGE_AM, TO FILE = MCCELM$OUT.TXT"
DECmcc ELM T1.2.4 Installation Failed
%MCC-F-FAILED, fatal DECmcc error
*********************************************************
Fatal DECmcc ELM T1.2.4 event occurred during installation
*********************************************************
%VMSINSTAL-E-IVPFAIL, The IVP for MCCELMT V1.2 has failed.
VMSINSTAL procedure done at 13:51
|
| 2016.3 | ELM V1.2 installed after using MIB compiler | CSC32::WOESTEMEYER | Why??...Why not!!! | Wed Jan 08 1992 13:43 | 11 |
| I suppose I should have entered the solution to this problem eariler.
.1 gave enough info that I was able to get it working. First let me ask
you another question, before you installed ELM V1.2, did you use the
MIB compiler to add some of the private MIB extentions for the
TCPIP/SNMP AM? If you did it created a file in MCC_SPECIFIC,
mcc_fdictionary.bpt. This is the file that is causing the problem.
All I did was to rename the file, I dislike deleting until I'm sure,
then the IVP ran fine. You don't even have to reinstall.
Steve
|
| 2016.4 | | QUIVER::CHILDS | Ed Childs | Thu Jan 09 1992 10:45 | 20 |
| Some questions:
Were there any MCC process logical names defined at installation time?
Is there an MCC_INIT file being run when MCC starts?
Are there any files in MCC_SPECIFIC (especially
MCC_DISPATCH_TABLE.DAT)?
Can you type these commands and post the output here?
MCC> TEST MCC 0 BRIDGE_AM
MCC> TEST MCC 0 FDDI_AM
$ DIR/DATE MCC_SYSTEM:MCC_DISPATCH_TABLE
It looks like your dictionary and parse table were correctly updated,
so perhaps the dispatch table is incorrect.
/* Ed */
|
| 2016.5 | | QUIVER::CHILDS | Ed Childs | Fri Jan 10 1992 13:21 | 8 |
| | It looks like your dictionary and parse table were correctly updated,
| so perhaps the dispatch table is incorrect.
If that's the case you should be able to fix the dispatch table with
this command:
$ @SYS$STARTUP:MCC_STARTUP_ELM ENROLL
|
| 2016.6 | More info
| WRK4ME::LUND | "Oh sure now it's working !" | Fri Jan 10 1992 15:28 | 56 |
|
Were there any MCC process logical names defined at installation time?
>> None I'm aware of
Is there an MCC_INIT file being run when MCC starts?
>> No
Are there any files in MCC_SPECIFIC (especially
MCC_DISPATCH_TABLE.DAT)?
>>MCC_DNS_SETUP.DEF;2 MCC_FDICTIONARY.BPT;1
>>MCC_FDICTIONARY.LOG;1
Can you type these commands and post the output here?
MCC> TEST MCC 0 BRIDGE_AM
>>%MCC-E-ATTRNOTALLOW, no attribute or argument allowed
MCC> TEST MCC 0 FDDI_AM
>>%MCC-E-ATTRNOTALLOW, no attribute or argument allowed
$ DIR/DATE MCC_SYSTEM:MCC_DISPATCH_TABLE
>>MCC_DISPATCH_TABLE.DAT;1 450 16-DEC-1991 13:31:26.10 [SYSTEM]
I have not had a chance to do what was suggested in note .3 yet, but will
try it and post what happens. Also did @SYS$STARTUP:MCC_STARTUP_ELM ENROLL
The MCC_STARTUP_ELM startup procedure for DECmcc T1.2.4 is now running.
Note: The DECmcc Director and BMS, SMS or EMS Startup procecures
should be run prior to executing this procedure.
DECmcc (T1.2.4)
%MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced
%MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced
%MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced
%MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced
%MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced
%MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced
%MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced
%MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced
The MCC_STARTUP_ELM startup procedure for DECmcc T1.2.4 is now ending.
But I still get the above error message whe TEST MCC 0 BRIDGE_AM.
|
| 2016.7 | | QUIVER::CHILDS | Ed Childs | Mon Jan 13 1992 11:16 | 19 |
| | Are there any files in MCC_SPECIFIC (especially
| MCC_DISPATCH_TABLE.DAT)?
| >>MCC_DNS_SETUP.DEF;2 MCC_FDICTIONARY.BPT;1
| >>MCC_FDICTIONARY.LOG;1
I think this is the problem. The installation procedure updates the
dictionary in MCC_COMMON. When you run MCC, it uses the MCC_SYSTEM
logical which is a search list, checking MCC_SPECIFIC first. How are
your MCC_FDICTIONARY files in MCC_SPECIFIC different than the ones in
your MCC_COMMON area? Have you installed other MCC products onto your
DECmcc BMS T1.2.4 system?
In order to ensure a "clean" installation, I would clear out all the
files from MCC_SYSTEM, re-install BMS and then install ELM. It looks
like you have old files in your MCC area.
It looks like your dispatch tables are out of sync with your dictionary
files.
|
| 2016.8 | ELm installs fine | WRK4ME::LUND | "Oh sure now it's working !" | Tue Jan 14 1992 10:50 | 7 |
|
I've removed all file in mcc_system:, and reinstalled DECmcc and ELM
everything installed fine. Thanks for the suggestions
Alan
|
| 2016.9 | Which MCC_FDICTIONARY.BPT ? | MEO78B::BARNHOORN | here on Cactus Island | Tue Jan 28 1992 23:11 | 83 |
|
I had a working DECmcc T1.2.4 system and I installed the ELM-AM, the
ELM-AM installed ok until the IVP, re .0 and .2.
I had previously compiled in the ChipCom MIB and one for a Datability
terminal server. ( I could use the Chipcom MIB succesfully to a
Chipcom hub).
I took the suggestion of .3 and looked in MCC_SPECIFIC: and found two
versions of MCC_FDICTIONARY.BPT, the dates of those match the dates when
I complied in the MIBs.
$dir mcc_specific:MCC_FDICTIONARY.*/datE
Directory SYS$SPECIFIC:[MCC]
MCC_FDICTIONARY.BPT;2
21-JAN-1992 15:13:50.01
MCC_FDICTIONARY.BPT;1
30-DEC-1991 11:43:38.01
MCC_FDICTIONARY.LOG;2
21-JAN-1992 15:13:01.38
MCC_FDICTIONARY.LOG;1
30-DEC-1991 11:43:38.92
Total of 4 Files.
Looking at MCC_COMMON: I have THREE versions of MCC_FDICTIONARY
$dir mcc_common:MCC_FDICTIONARY.*/date
Directory DISK_NET:[MCC]
MCC_FDICTIONARY.BPT;3
28-JAN-1992 16:04:39.82
MCC_FDICTIONARY.BPT;2
28-JAN-1992 13:55:27.73
MCC_FDICTIONARY.BPT;1
8-DEC-1991 13:51:41.01
MCC_FDICTIONARY.DAT;1
8-DEC-1991 02:11:19.86
MCC_FDICTIONARY.LOG;2
28-JAN-1992 15:31:48.98
MCC_FDICTIONARY.LOG;1
28-JAN-1992 13:51:08.92
Total of 6 files.
I tried twice to install the ELM-AM that accounts for the same dates of
the BPT and LOGS in MCC_COMMON.
I renamed the MCC_FDICTIONARY.BPT files in MCC_SPECIFIC, and ran the
IVP for DECmcc ELM and it successfully completed.
But when I run DECmcc I donot see the MIBs I compiled, ChipCom or
Datability for the SNMP AM. Their definitions are in the
MCC_SPECIFIC:MCC_FDICTIONARY.BPT ( which does not contain the Bridge
AM).
So how do I get the MIBs back without re compiling them?
Also where will the MCC_FDICTIONARY.BPT go ?
regards
Mark Barnhoorn
|
| 2016.10 | rebuild parse tables | TOOK::CALLANDER | MCC = My Constant Companion | Fri Jan 31 1992 11:15 | 10 |
| they may actually still be in there, the .bpt might have been
the only pieces not correctly updated. save a copy of the .bpt
(rename it), and delete all other version of it. then from
dap (manage/tool/dict) do a rebuild command to force a new
copy of the parse tables to be built. If you want to check for
the mibs before doing the rebuild, do a SHOW CLASS SNMP from
the dap prompt and see if they are there.
jill
|