| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1946.1 | QAR #1897 | TOOK::MINTZ | Erik Mintz | Mon Dec 16 1991 08:51 | 2 |
| Enterd as QAR 1897 in MCC_INTERNAL
|
| 1946.2 | It's problems with ROUTE in UCX, address 0.0.0.0 is missing | OSLACT::BJORN | Once again | Tue Dec 17 1991 07:04 | 44 |
| Hi,
I've been looking into this problem, and I've found the reason to what was
causing the problem.
The MCC_IP_AUTOCONFIG.COM is calling MCC_MAKECONFIG.COM to get info from UCX.
In MCC_MAKECONFIG.COM a UCX SHOW ROUT is done to get routing information.
In MCC_MAKECONFIG.COM a SEARCH is done in the outputfile from the UCX SHOW
command to look for an address 0.0.0.0. This address is not set up when
installing UCX, so the procedure exits due to the ON WARNING statement
at the top of the procedure.
A workaround is to do the following;
UCX SET ROUT 0.0.0.0 /gateway=your_ip_nodename_as_defined_in_HOST_TABLE
Then you can run the IP Autoconfig again, and generate the autoconfig scripts.
I've come a few steps further with the procedure, but now I run into syntax
problems when the registration files are executed. It seems that MCC is not
able to handle this format;
REGISTER SNMP NWOMCC_NS:.mcc.ip.OSLXXX SYNONYM OSLXXX
%MCC-E-INVALIDIDENT, invalid entity identifier
I've modified MCC_AUTOCONFIG_PREFIX.DAT to point to my namespace name, by
replacing LOCAL_NS: with NWOMCC_NS:
I've also created the .MCC.IP directory with MCC_DNS_SETUP.COM.
If I manually try to register an SNMP entity instance, with the ADDRESS
attribute specified, I get an error message saying
%MCC-E-ATTRNOTALLOW, no attribute or argument allowed.
I previously used to start MCC_TCPIP_STARTUP.COM after MCC_STARTUP_BMS.COM,
when the system was booted. Is this the correct way under T1.2? Another note
explains that TCPIP AM V1.1 or V1.0 should NOT be installed on top of T1.2, but
it doesn't say anything about ENROLL!
Any ideas of the problems with register SNMP command?
Bj�rn Olav Haugom
Oslo, Norway
|
| 1946.3 | Thanks, and question about your SNMP registration questions | TOOK::FIGWER | | Tue Dec 17 1991 11:31 | 23 |
|
Hello Bj�rn,
Thank you for helping us solve the problem of 1946.0!
We will add to the release notes the requirement that the
UCX command you specified be issued before IP Autoconfiguration is
run.
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? 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.
Are any of the registration commands generated by IP
Autoconfiguration causing the same error? If so, could you
post the text of such a registration command and the associated
error? (Send mail to TOOK::FIGWER if you prefer.)
Thank you,
Ulla Figwer
|
| 1946.4 | Clarification - how to specify default gateway in UCX | TOOK::FIGWER | Ulla Figwer LKG2-2/T2 x226-7858 | Tue Dec 17 1991 13:30 | 22 |
|
More clarification about the UCX command in 1946.2...
0.0.0.0 is UCX's way of showing the default route. Therefore, the
following command is a more standard way to do what Bj�rn suggested:
UCX SET ROUTE/DEFAULT/GATEWAY=your_local_ip_router/perm
A few things to note:
/DEFAULT specifies that the router to be set is 0.0.0.0, the default
router
/perm will insure that the modification to the database will stay
in tact if UCX goes down and comes back up
It is important to specify an ip *router* as the default gateway,
not necessarily the ip name of your local node.
Thanks Erik, for suggesting that we clarify this!
Ulla
|
| 1946.5 | IP AUTOCONFIG generates "invalid entity identifier" messages | OSLACT::BJORN | Once again | Wed Dec 18 1991 03:17 | 51 |
| 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.6 | invalid entity identifier usually means bad fullname | DANZO::CARR | | Wed Dec 18 1991 14:42 | 6 |
| 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.7 | What is a valid SNMP fullname? | OSLACT::BJORN | Once again | Mon Dec 23 1991 07:03 | 43 |
| 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.8 | Seems to work for us. Pls try other things... | BSYBEE::EGOLF | John C. Egolf LKG2-2/T02 x226-7874 | Mon Dec 23 1991 08:43 | 43 |
| 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.9 | REGISTER'ing other entities are O.K. | OSLACT::BJORN | Once again | Mon Dec 23 1991 09:04 | 23 |
| �'ve REGISTER'ed other entities, like NODE4 entities.
REGISTER NODE4 .NWO.NWOBOH syn NWOBOH
is working O.K.
I've only tried the autoconfig procedures, and not played around with
STATION, BRIDGE and so on.
The REGISTER function is working, so I gues it has something to do with
the upgrade from BMS V1.1 via BMS X1.2 and BMS T1.2.3 to BMS T1.2.4.
The X1.2 was the pre-pre-pre release of 1.2 I copied to Alcatel earlier.
When upgrading from BMS V1.1, I erroneously installed the TCP/IP SNMP AM V1.1
on top of BMS T1.2.3. After Upgrading to T1.2.4, I didn't re-install TCP/IP
SNMP AM on top. I also commented out the MCC_TCPIP_STARTUP.COM from my
SYSTARTUP_V5.COM file. Is this correct? I read in note 1886 that the SNMP AM
was included in the BMS kit, so I would presume that the BMS startup file
would enroll the SNMP AM. Correct?
Bj�rn Olav Haugom
|