[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

1946.0. "T1.2.4 VMS IP Autoconfig problem" by HAZARD::BAKER (Paul Baker, UK Product and Technology Group - 844 3311) Mon Dec 16 1991 10:15

The following is a log of an IP autoconfig run. Any ideas what went wrong?


* * * * * * * * * * *  Starting MCC IP Autoconfiguration * * * * * * * * * *

The autoconfiguration process consists of the following steps:

        1.  Automatic construction of the initial configuration file

        2.  Manual adjustment of the configuration file using an editor

        3.  Gathering of data using the adjusted configuration file

        4.  Inspection of the exceptions, if there were any

        5.  Generation of MCC Iconic Map files and MCC registration scripts

        6.  Execution of MCC registration scripts

Note that step 6 can be executed independently from 1-5 if the MCC
registration files for the current domain have already been generated.
To execute step 6 only, choose option 'R' from the main menu.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Enter any character to continue>


Environment variable MCC_AC_TOP_DIR not set.
Autoconfiguration will use current directory as the top directory.
Current directory is SYS$SYSDEVICE:[BAKER].
Please specify a domain> iptest1

Autoconfiguration will proceed with the domain "IPTEST1"
Enter Q to Quit
Is this the correct domain?[y]

Building configuration file: SYS$SYSDEVICE:[BAKER.IP.IPTEST1]IPTEST1.CF ...
%SEARCH-I-NOMATCHES, no strings matched
%RMS-E-EOF, end of file detected

Error has occurred.

Warning: Data files created may be corrupt.

Exiting...
Enter any character to exit>

System is VS3100 M48, 16Mb memory, VMS 5.4-3, T1.2.4

Paul.
T.RTitleUserPersonal
Name
DateLines
1946.1QAR #1897TOOK::MINTZErik MintzMon Dec 16 1991 10:512
Enterd as QAR 1897 in MCC_INTERNAL

1946.2It's problems with ROUTE in UCX, address 0.0.0.0 is missingOSLACT::BJORNOnce againTue Dec 17 1991 09:0444
1946.3Thanks, and question about your SNMP registration questionsTOOK::FIGWERTue Dec 17 1991 13:3123
1946.4Clarification - how to specify default gateway in UCXTOOK::FIGWERUlla Figwer LKG2-2/T2 x226-7858Tue Dec 17 1991 15:3022
1946.5IP AUTOCONFIG generates "invalid entity identifier" messagesOSLACT::BJORNOnce againWed Dec 18 1991 05:1751
Re .3

>>      About your questions regarding registration of the SNMP entity
>>      OSLXXX.  Is the command which you specified in your note
>>      one that was generated by IP Autoconfiguration?  

	Yes, the command is picked from the .COM files generated by IP 
 	AUTOCONFIGURATION. The register commands failed, and the .LOG file
	shows me the messages.

>>>	I believe that IP Autoconfiguration would have specified an internet
>>> 	name as the synonym for NWOMCC_NS:.mcc.ip.OSLXXX.  The SNMP 
>>>	registration command requires the synonym to be an internet name.

	The procedure generated the synonym as my UCX HOST NAME, which perhaps
	is the Internet name? Is it, or should it be OSLXXX.NWO.DEC.COM, which 
	is the BIND name? I didn't specify that I wanted to use BIND, when I 
	re-installed UCX. Should I have done so?

	I manually entered one of the commands and got this output;


*********
register SNMP NWOMCC_NS:.MCC.IP.OSLXXX SYNONYM OSLXXX
*********

%MCC-E-INVALIDIDENT, invalid entity identifier

*********
create domain .MCC.DOMAIN.16-0-0-0-hosts member NWOMCC_NS:.MCC.IP.OSLXXX
*********

Domain NWOMCC_NS:.MCC.DOMAIN.16-0-0-0-hosts Member NWOMCC_NS:.MCC.IP.OSLXXX
AT 18-DEC-1991 09:04:30

No such entity: Domain NWOMCC_NS:.MCC.DOMAIN.16-0-0-0-hosts Member
NWOMCC_NS:.MCC.IP.OSLXXX
                         Unknown Entity = Domain
                                          NWOMCC_NS:.MCC.DOMAIN.16-0-0-0-hosts
                                          Member NWOMCC_NS:.MCC.IP.OSLXXX
*********
$ ucx
UCX> show host
*********

     LOCAL database

Host address    Host name

127.0.0.1       LOCALHOST, localhost
16.181.192.3    OSLXXX
1946.6invalid entity identifier usually means bad fullnameDANZO::CARRWed Dec 18 1991 16:426
Can I join the party?

The "%MCC-E-INVALIDIDENT, invalid entity identifier" error message is issued
when an invalid fullname is specified.

Are you sure your fullname,  NWOMCC_NS:.MCC.IP.OSLXXX is valid?
1946.7What is a valid SNMP fullname?OSLACT::BJORNOnce againMon Dec 23 1991 09:0343
Re .6

>>> Are you sure your fullname,  NWOMCC_NS:.MCC.IP.OSLXXX is valid?

How can I be sure? I'm only a user.

NWOMCC_NS is the namespace name of my namspace, I'm sure!
.MCC.IP is a directory I've created in DNS, so I'm sure!
NWOMCC_NS:.MCC.IP is the default prefix for IP Autoconfig defined in the file
MCC_AUTOCONFIG_PREFIX.DAT, which I'm sure of.
OSLXXX is the host name defined in UCX, I'm sure!

I've manually tried to register the SNMP entity instance OSLXXX in many ways,

MCC> REGISTER SNMP OSLXXX

Unrecognized registration name. The namespace name must be a fullname, include
a leading ".".

MCC> REGISTER SNMP .OSLXXX

Unrecognized registration name. The namespace name must be a fullname, include
a leading ".".

MCC> REGISTER SNMP .mcc.ip.oslxxx

Unrecognized registration name. The namespace name must be a fullname, include
a leading ".".

MCC> REGISTER SNMP nwomcc_ns:.mcc.ip.oslxxx

%MCC-E-INVALIDIDENT, invalid entity identifier

MCC> SHOW MCC 0 TCPIP_AM ALL att

MCC 0 TCPIP_AM
AT 23-DEC-1991 12:27:43 All Attributes

               Component Identification = "DECmcc TCP/IP SNMP AM"
                      Component Version = T1.2.4
                            UDP Retries = 2
                            UDP Timeout = 5
MCC>
1946.8Seems to work for us. Pls try other things...BSYBEE::EGOLFJohn C. Egolf LKG2-2/T02 x226-7874Mon Dec 23 1991 10:4343
	It appears  to  work  here for us.  Can you ensure that you can
	register other things into DNS so that we understand whether it
	is an SNMP problem/issue  or  a DNS problem/issue (or something
	else).


Hawk2> MAN/ENT
DECmcc (T1.2.4)

MCC> REGISTER SNMP HAWK2

SNMP HAWK2_NS:.HAWK2
AT 23-DEC-1991 08:13:34

Partial registration success. Please retry later to complete the registration.
        Reason for Partial Registration = No internet name or internet address
                                          specified
MCC> REGISTER SNMP HAWK2 SYN HAWK2

SNMP HAWK2_NS:.HAWK2
AT 23-DEC-1991 08:13:57

Registration successful.
MCC> REGISTER SNMP .MCC_IP.HAWK2 SYN HAWK2

SNMP HAWK2_NS:.MCC_IP.HAWK2
AT 23-DEC-1991 08:14:15

Duplicate registration identifier, identifier already in use by another entity.
                                Address = 16.20.144.93
MCC> DEREGISTER SNMP HAWK2

SNMP HAWK2
AT 23-DEC-1991 08:14:30

Deregistration Successful
MCC> REGISTER SNMP .MCC_IP.HAWK2 SYN HAWK2

SNMP HAWK2_NS:.MCC_IP.HAWK2
AT 23-DEC-1991 08:14:36

Registration successful.
MCC>
1946.9REGISTER'ing other entities are O.K.OSLACT::BJORNOnce againMon Dec 23 1991 11:0423