| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4919.1 | working correctly | TOOK::PURRETTA | | Wed Apr 21 1993 09:39 | 12 |
| The Name and Address attributes are always set to what the
entity responded with. Everything here is working correctly;
you asked for a Directory of node MN1 which was the synonym you
gave at registration time, and we returned the actual data that
node identified itself as at the time of registration.
Actually you're lucky that your local database is wrong (1.111 mapping
to MN1 instead of MNN1) otherwise the registration wouldn't have found
the node and you would have gotten a partial registration.
This is a good example of how you can detect anomalies in your local
database against reality on the net.
|
| 4919.2 | It's not an anomaly, it's designed that way. | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Wed Apr 21 1993 13:07 | 16 |
| John,
The local database is set up to use a 3-letter node name to support a
customer-required convention. The node's actual name has 4 characters
in it.
I want to be able to use **ANY** synonym I choose. I am able to
register other nodes using the synonym of my choice. I checked two
end-nodes to verify this.
I will go back and experiment more.
What I really need is the ability to refer to a remote node by any name
that is set for that address in the NCP database.
-Dan
|
| 4919.3 | | TOOK::PURRETTA | time for a cool change... | Wed Apr 21 1993 14:16 | 10 |
| Dan, I don't see the problem. look back at your .0 entry. You specified
the Directory command using the synonym and MCC responded. If your
local database has the node in it as the synonym name then if you
do a show, you'll get there. However, the Registration information
will *always* reflect reality; i.e. what the NODE told us. This is
goodness.
Are you saying that if you do a Show using the synonym, you can't get
to the node, even though it's in the local net database as the synonym
name?
|
| 4919.4 | Entry in NCP database must match Synonym | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Thu Apr 22 1993 01:29 | 19 |
| John,
It seems that a couple of system managers changed node names on two
nodes after I registered them, hence my comment regarding how synonyms
are displayed for certain nodes.
The behavior is the same for all NODE4's, regardless of type.
The synonym must match the entry in the NCP database, otherwise, you
will get "not known to local node" error messages.
The nodes actual name will be displayed on the Map, not the synonym. I
wanted the synonym on the map.
I'm now in the process of finding out how this will impact my customer.
It is, as you say, a good idea to find out what the node is really
named. It makes sense. But we need the flexibility to do things that
sometimes don't seem to make sense.
-Dan
|