| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3852.1 | It depends! :-) | DAVIDF::FOX | David B. Fox -- DTN 285-2091 | Thu Jan 30 1997 11:23 | 15 |
| If you're using DECdns for naming lookups then you don't need such a thing as
your node "database" will be up to date all the time. This is one of the
beauties of DECnet Plus!
If you're using the LOCAL namespace then you have a need for a similar
procedure. Is your node on the Easynet? Do you need the entire Easynet
database or just a handfull of nodes?
If you're on the Easynet all the time, it is best to use the DEC: namespace.
Since DECdns on the Easynet can be a problem at times, I use a populated LOCAL
namespace on my machine which mirrors the Easynet. I update every Sunday night.
The procedure is in this conference, note 2135.
David
|
| 3852.2 | | GRUFFY::ZAHORA | Rob Zahora | Thu Jan 30 1997 17:10 | 8 |
| I should have mentioned that right now I'm running with a LOCAL
namespace. I use a subset of about 200 nodes from the Easynet
database. I realize I could do an update with the entire network
database but I'd rather not take the space and time that this would
require if I don't have to.
As for DECdns, I'm not familiar with it and bypassed the capability
during the DECnet Plus install.
|
| 3852.3 | | PYRO::RON | Ron S. van Zuylen | Fri Jan 31 1997 03:01 | 10 |
| >Since DECdns on the Easynet can be a problem at times, I use a populated LOCAL
>namespace on my machine which mirrors the Easynet. I update every Sunday
>night. The procedure is in this conference, note 2135.
Hmmm... I haven't had any form of local database on my systems for 3 years.
And other than the corporate DECdns collapse when V1 was upgraded to V2
last year, we really don't have any name translation issues. I guess we're
just lucky...
--Ron
|
| 3852.4 | | DAVIDF::FOX | David B. Fox -- DTN 285-2091 | Fri Jan 31 1997 10:13 | 23 |
| Re: .3
Ron, we've had some difficulties, although not recently, here in NIO. I use
LOCAL as my backup just in case. I always go to the DEC namespace first.
Re: .2
I'll assume that your node is on the network regularly. What you can do is to
re-run NET$CONFIGURE and select option 2 to rename your node. It will ask you
to enter the director services you want. I use DECdns, DOMAIN, and LOCAL. If
we're talking about GRUFFY, your DECdns FULLNAME is DEC:.bxb.gruffy. Your LOCAL
FULLNAME can be what you desire. If you were to load it from Easynet data, your
nodename would be LOCAL:.bxb.gruffy. DOMAIN is only used if you have a TCP/IP
stack on your system and want the DECnet Over TCP/IP functionality. If so, that
name would be whatever your node name is for TCP/IP.
You don't have to have all three but DECdns OR LOCAL must be first in the list.
Once you've done that, you'll "never" have to worry about updating your node
database as you'll always, barring a DECdns problem, have the latest Easynet
information available to you. Makes management a little easier.
David
|
| 3852.5 | DECdns attempt | GRUFFY::ZAHORA | Rob Zahora | Fri Jan 31 1997 11:24 | 179 |
| Thanks for the suggestion on DECdns. Unfortunately, my attempt to make
the connection appears to have been unsuccessful. What follows is the
log of the session. Any thoughts as to what I did wrong?
* Enter the directory services to use on the system [LOCAL] : local,DECdns
* Enter the full name for directory service LOCAL [LOCAL:.GRUFFY] :
* Enter the full name for directory service DECDNS : DEC:.bxb.gruffy
* What is the synonym name for this node? [GRUFFY] :
sys$manager:net$dns_clerk_startup.ncl changed to use the new default
namespace.
Your default namespace nickname is DEC.
Your default namespace NSCTS is
AA-00-04-00-DE-11-A0-AA-F9-6F-56-DE-8E-00.
Node 0 DNS Clerk
at 1997-01-31-11:09:40.274-05:00I0.233
Node 0 DNS Clerk
at 1997-01-31-11:09:40.589-05:00I0.233
%NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries
Node 0
at 1997-01-31-11:09:44.129-05:00I0.233
%NET$CONFIGURE-I-NODERENAMED, node successfully renamed to
LOCAL:.GRUFFY
Node 0 Session Control
at 1997-01-31-11:09:44.920-05:00I0.234
Node 0 Session Control
at 1997-01-31-11:09:44.928-05:00I0.234
Node 0 Session Control
at 1997-01-31-11:09:44.931-05:00I0.234
Node 0 Session Control
at 1997-01-31-11:09:44.934-05:00I0.234
Node 0 Session Control
at 1997-01-31-11:09:45.000-05:00I0.234
Characteristics
Maintain Backward Soft Links = True
SHOW
DIRECTORY DEC:.bxb
AT 31-JAN-1997:11:09:45
dns$cts =
Error on entity: DEC:.bxb
%DNS-E-NOCOMMUNICATION, Unable to communicate with any DECdns server
**************************************************************************
WARNING
NET$CONFIGURE.COM cannot access the DEC: namespace, either because
the namespace is not available at the moment, your node does
not have proper access to the namespace, or because the namespace
you are using is new and the directories have not been created yet.
Therefore, the DECNET_REGISTER tool cannot attempt to look up or
register your node into the DEC: namespace.
When the problem is rectified, please use the DECNET_REGISTER import
file to register your node into the DEC: namespace.
***************************************************************************
Directory Service: Local name file
Node name: LOCAL:.GRUFFY
Phase IV synonym: GRUFFY
Address tower protocol and selector values:
Session: DNA_SessionControlV2 (SC2)
00 13
Transport: DNA_NSP (NSP)
(no selector value)
Routing: DNA_OSInetwork (CLNS)
49::00-1D:AA-00-04-00-56-74:20 (29.86)
Number of nodes reported on: 1
%NET$CONFIGURE-I-NODEISREG, node is already registered in the LOCAL
directory service
%RENAME-I-RENAMED,
SYS$SYSROOT:[SYSMGR]DECNET_REGISTER_IMPORT_FILE_GRUFFY.TXT;1
renamed to
SYS$SYSROOT:[SYSMGR]DECNET_REGISTER_IMPORT_FILE_GRUFFY.TXT-OLD;1
%NET$CONFIGURE-I-IMPORTFILECREATED, created the DECNET_REGISTER import
file
**********************************************************************
WARNING
This node could not be registered in one or more of the directory
services you have chosen. When this procedure completes you or
your network manager will have to manually register this node in the
directory service(s) for which the error occurred. See the
DECnet-Plus Installation and Configuration guide for more details,
or contact your network manager.
Once the problem has been rectified, you or your namespace manager
can use the following DECNET_REGISTER command(s) to register your node
in the appropriate directory service(s):
For the DECdns directory service:
DECNET_REGISTER IMPORT DIRECTORY DECDNS FILE -
SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_GRUFFY.TXT
Once the node has been successfully registered in the appropriate
directory service(s), invoke option 2 of NET$CONFIGURE.COM (Change
node name/namespace name) to complete the node's network configuration
and startup.
**********************************************************************
Summary of Configuration
Node Information:
Node Type: ENDNODE
Directory Services Chosen: LOCAL,DECDNS
Primary Directory Service: LOCAL
DECdns Full name: DEC:.bxb.gruffy
Local Full name: LOCAL:.GRUFFY
Node Synonym: GRUFFY
Phase IV Address: 29.86
Phase IV Prefix: 49::
Autoconfiguration of Network Addresses: Enabled
Session Control Address Update Interval: 10
Routing ESHello Timer: 600
Device Information:
Device: ESA (DESVA):
Data Link name: SVA-0
Routing Circuit Name: SVA-0
Transport Information:
NSP Transport: Configured
Maximum number of logical links: 200
Maximum Transmit and Receive Window: 20
Maximum Receive Buffers: 4000
OSI Transport: Configured
Maximum number of logical links: 200
Maximum Transmit and Receive Window: 20
Maximum Receive Buffers: 4000
Congestion Avoidance Disabled
Event Dispatcher Configuration:
Sinks: local_sink
Outbound Streams: local_stream
Phase IV Relay: Enabled
%NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts
modified by NET$CONFIGURE
%NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration
completed
|
| 3852.6 | Don't dispair... | DAVIDF::FOX | David B. Fox -- DTN 285-2091 | Mon Feb 03 1997 08:47 | 16 |
| Rob,
I think you're ok. Since GRUFFY is already registered in the DEC
namespace you're all set. I get errors like that a lot trying to get at the NIO
part of the namespace!
What you might want to consider doing is flip your namespace precedence
from LOCAL, DECdns to DECdns, LOCAL. In the later, the LOCAL namespace becomes
your backup namespace when DECdns is unavailable, OR you define nodes in your
LOCAL namespace that are not registered in the DEC namespace.
Another thing you should probably do if you haven't already is to reboot
GRUFFY to insure that the changes are active. There are some things that don't
take effect immediately. When doing something major like playing with your
naming services I like to reboot.
David
|