| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3713.1 | A bad DNS setup? | TRM::KWAK | | Thu Sep 10 1992 12:28 | 57 |
|
RE: .0
> DNS problems similar to those mentioned in 1528, 1661, and 1676 have
> occurred while running DECmcc V1.2.0 and DNS V1.1, all on VMS systems.
Do you see the same MCC DNS error messages?
How is DNS name space set up (Master and Read-only Replicas)?
> When registering an SNMP node, I got the DNS DANGLINGLINK message
> followed by the MCC message "unable to register node".
>
> Other problems surrounding missing objects, but soft-links still being
> present in the namespace have resulted in "unable to register entity,
> entity already exists" messages, yet there is nothing to deregister.
>
> I have had to manually use DNS$CONTROL to find the links and delete
> them.
Are you definitely using DECmcc V1.2?
Can you issue the following command in FCL:
MCC> show mcc 0 all char
What is you SNMP registration command?
In DECmcc V1.2, you do not have to remove softlink.
If DECmcc registration is unsuccessful, you can remove the DNS object
and leave the softlinks. The dangling softlinks will be re-used when
the same alternate identifiers are used (IP name and IP address for
SNMP).
> I am having trouble with 5 SNMP nodes. Deleting the
> .MCC_SNMP_Backtranslation.SNMPxx link will delete the associated
> hex value above it in the same DNS directory, but I'm not quite sure on
> some of these.
It seems that DNS is mis-behaving. Maybe, you can ask this question
in NOTED::DNS conference.
> How is the hex value in this directory determined? Which object or
> link attribute contains a target pointer to this value?
EX. An IP address of 16.20.144.140 has 32 bit hex value of 1014908c.
(16 = 0x10, 20 = 0x14, 144 = 0x90, 140 = 0x8c)
The corresponding IP address backtranslation would be:
.MCC_SNMP_Backtranslation.1014908C
> There is still DEFINITELY a problem with DNS and its use with DECmcc
> that the patches in 1267 did not fix.
????
This is the first report of such DNS problem with DECmcc V1.2.
We have to see if other people are having the same problem.
William
|
| 3713.2 | More info on DNS V1.1 / DECmcc V1.2 registration problem | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Tue Sep 15 1992 12:40 | 87 |
| William,
The customer's namespace consists of two clearinghouses, one on each
of two nameserver nodes. All master replica directories are on one
node, with read-only replica directories on the other node.
DNS Version 1.1, Protocol Version 1.0
VMS V5.4-3 on both nameserver nodes and DECmcc management nodes.
MCC> SHOW MCC 0 ALL CHAR
Component Version = V1.2.0
Component Identification = "DECmcc"
Default Namespace Root Directory = ""
MCC> SHOW MCC 0 TCPIP_AM ALL CHAR
Component Version = V1.2.0
Component Identification = "DECmcc TCP/IP SNMP AM"
UDP Timeout = 5
UDP Retries = 2
ICMP Timeout = 5
Other AMs: DECmcc Terminal Server AM V1.0.0
DECmcc DECnet DNA4 AM V1.2.0
DECmcc DECnet DNA5 AM V1.2.0
DECmcc Bridge AM V1.2.1
DECmcc FDDI AM V1.2.0
DECmcc Concentrator AM V1.2.0
=====================================================================
Registration commands and error messages:
MCC> DIR SNMP .ip.xyplex1 (also tried using SYNONYM xyplex1)
The entity SNMP .ip.xyplex1 is not registered
Not Registered Entity = SNMP .ip.xyplex1
MCC> REGISTER SNMP .ip.xyplex1 SYNONYM xyplex1
SNMP MY_NS:.ip.xyplex1
The requested operation cannot be completed
MCC Routine Error = %DNS-E-ENTRYEXISTS, Creation not
possible, entry already exists
*****> Using DNS$CONTROL:
DNS> show obj .ip.xyplex1 ! not found
DNS> show link .mcc_snmp_backtranslation.xyplex1 !not found
DNS> show link .mcc_snmp_backtranslation.81010101 !not found
I also looked for the object xyplex1 in EVERY directory in the
namespace. No luck.
Then I tried this:
MCC> REGISTER SNMP xyplex1 synonym xyplex1
.
.
.
Registration successful.
DNS showed the object xyplex1 in the root directory and both softlinks
were present in the backtranslation directory.
MCC> DEREGISTER SNMP xyplex1
.
.
.
Deregistration Successful
MCC> REGISTER SNMP .ip.xyplex1 SYNONYM xyplex1
.
.
.
entry already exists.
I have this same problem with 3 other ip nodes that I have found so
far. I do not have this problem with other node types.
-----------------------------------
Regarding the DANGLINGLINK problem, I tried to reproduce the problem
by re-registering the ip node in question (a Chipcom hub). This time,
the registration completed (though partially, since the node was down).
Any ideas?
-Dan
|
| 3713.3 | Try more DNS$Control commands | TRM::KWAK | | Tue Sep 15 1992 15:10 | 15 |
|
RE:. 2
Try some DNS commands:
DNS> show char dir .ip
DNS>! Check if a DNS entry name ".ip.xyplex1" is used.
DNS> show object .ip.xyplex1
DNS> show link .ip.xyplex1
DNS> show dir .ip.xyplex1
(%DNS-E-ENTREXISTS means a DNS entry (object, directory, or softlink)
already exists)
William
|
| 3713.4 | More on DNS and registration problem | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Wed Sep 16 1992 11:52 | 14 |
| William,
As mentioned in .2, I issued the appropriate DNS commands to
determine whether or not the links and object exist. They do not.
The links would be present in the .mcc_snmmp_backtranslation directory,
not the .ip directory, but I issued the commands mentioned in .3
anyway. Entities do not exist.
Last night, I turned off the clearinghouses one at a time and
issued the DNS commands mentioned in .3 (show link & show object) just
to be sure that one clearinghouse had the object/link and the other
didn't. Neither clearinghouse contains the entities.
-Dan
|
| 3713.5 | Solution: %DNS-E-ENTITYEXISTS, entity already exists | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Mon Sep 28 1992 03:28 | 16
|