- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: decnet_register Question
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2008 09:34 AM
тАО10-09-2008 09:34 AM
My question is this, do I HAVE to register (using DECNET_REGISTER) every node which might be using DECnet communication, given that all of my decnet connectivity is via IP addresses and DNS Host names, and not Phase IV address or nodenames?
Within my configuration, can I get away with just registering myself, i.e. the 'local' node.
thanks \
Dave.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2008 01:12 PM
тАО10-09-2008 01:12 PM
Re: decnet_register Question
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2008 11:08 PM
тАО10-09-2008 11:08 PM
Re: decnet_register Question
$ mc ncl show session control naming search path
$ mc cdi$trace ! do this and then get another session going and set host to a remote node. You will see the process of nodename resolution unfold.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-10-2008 12:45 AM
тАО10-10-2008 12:45 AM
SolutionFrom here on I'll assume that you're using LOCAL naming for DECnet and DOMAIN naming for DECnet over IP.
I'll also assume you're using DECnet on the LAN and DECnet over IP across the WAN, or between LANS / VLANS where you only have IP routing as a means to communicate.
With DECnet over IP you've jumped sideways into the IP stack for name resolution using BIND.
So, use DECNET_REGISTER to set up a clean DECnet name to DECnet address lookup for all your nodes that will use DECnet, export that to a file and import it on all the others. That gets you a consistent DECnet naming scheme.
Set your DOMAIN DNS server to be "127.0.0.1" (equates to "localhost") when you set up naming using NET$CONFIGURE in ADVANCED mode. That will cause the DECnet over IP name lookup to use the local BIND resolver, which will first try the HOSTS file, then use the list of DNS name servers you've set up in your IP stack's name resolution nameserver list. Means you don't have to go back to your DECnet configuration if you ever change your IP name servers.
You should make consistent naming changes everywhere. In practice a destination node will accept inbound DECnet-over-IP connections without having all the naming in place, but you'll see "back translate" failures from the naming service until you have the naming consistent.
All you then do is delete the 'old' DECnet style name from the local naming service (using DECNET_REGISTER) and insert the new name into the local HOSTS database, then move it out to your DNS if you ever need to.
You'll also need to flush the naming caches everywhere too. NCL> FLUSH SESSION CONTROL NAMING CACHE ENTRY "*" is what you need.
Don't forget to enable the PWIP driver and allow ports 102 and 399 through the firewalls. You can also control which IP subnets you accept inbound connections from if you're on a recent version (look at the NCL help for the rfc 1006 and rfc 1006-plus (aka rfc 1869) OSI transport templates.
You might find the article I wrote some time ago for the VMS technical journal useful (V5 I think it was) plus some of the slide sets available at www.xdelta.co.uk/seminars
Don't forget that you can test the connectivity without relying on the naming by using things like set host ip$
Also use Martin's recommendation to view the whole name resolution process unfolding.
Cheers, Colin (http://www.xdelta.co.uk).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-10-2008 03:27 AM
тАО10-10-2008 03:27 AM
Re: decnet_register Question
$ CREATE NET$SESSION_STARTUP.NCL
!% Custom Created
!% NCL Script SYS$SPECIFIC:[SYSMGR]NET$SESSION_STARTUP.NCL;
!% 10-Oct-2008
!%
SET NODE 0 SESSION CONTROL MAINTAIN BACKWARD SOFT LINKS TRUE
SET NODE 0 SESSION CONTROL TRANSPORT PRECEDENCE (TP4,NSP)
^Z
$ CREATE NET$SEARCHPATH_STARTUP.NCL
!% Custom Created
!% NCL Script SYS$SPECIFIC:[SYSMGR]NET$SEARCHPATH_STARTUP.NCL;
!% 10-Oct-2008
!%
SET NODE 0 SESSION CONTROL NAMING SEARCH PATH -
([DIRECTORY SERVICE = DOMAIN, TEMPLATE = "*"], -
[DIRECTORY SERVICE = DOMAIN, TEMPLATE = "*.myplace.com"], -
[DIRECTORY SERVICE = LOCAL, TEMPLATE = "*"], -
[DIRECTORY SERVICE = LOCAL, TEMPLATE = "local:*"], -
[DIRECTORY SERVICE = LOCAL, TEMPLATE = "LOCAL:.*"])
SET NODE 0 SESSION CONTROL BACK SEARCH PATH -
([DIRECTORY SERVICE = DOMAIN, TEMPLATE = ""], -
[DIRECTORY SERVICE = LOCAL, TEMPLATE = ""])
SET NODE 0 SESSION CONTROL NAMING CACHE TIMEOUT 30-00:00:00
SET NODE 0 SESSION CONTROL NAMING CACHE CHECKPOINT INTERVAL 08:00:00
^Z
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2009 05:46 AM
тАО08-20-2009 05:46 AM