- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: DECnet address change leads to SET HOST proble...
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
тАО06-09-2005 02:34 AM
тАО06-09-2005 02:34 AM
There are three nodes involved, A, B, and G. Before yesterday they were all in area 19. Yesterday I moved G into Area 53. There is a Cisco router with DECnet in between these two areas. A, B, and G are all nonrouting Phase IV.
I had a good bit of difficulty getting SET HOST to work at all, going in our out of G. Even restarting DECnet didn't help. (And yes, I changed G's address in their DECnet permanent and volatile databases.)
Eventually I just rebooted all three. After that, SET HOST worked between all three in both directions EXCEPT from B to G.
Since SET HOST (CTERM) is the only DECnet application that is having problems, and only in one direction between just two nodes, I think we can rule out routing problems or DECnet on G having "SET NODE B ACCESS NONE".
Anything else come to mind?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2005 04:29 AM
тАО06-09-2005 04:29 AM
Re: DECnet address change leads to SET HOST problem
Of course, G really is accepting SET HOST connections from everyone but B (see o.p.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2005 07:26 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2005 07:34 AM
тАО06-09-2005 07:34 AM
Re: DECnet address change leads to SET HOST problem
I think i faced a similar situation few years back and i faintly remember ....
Probably i got around the situation like yours by deleting and then creating the defintions for the nodes having problem either side using the DECNET CONFIG MENU
regards
Mobeen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2005 11:11 PM
тАО06-09-2005 11:11 PM
Re: DECnet address change leads to SET HOST problem
Thanks for the reminder about checking NCP's settings on G for incoming access from B.
I may not have looked at it because copying a file over DECnet from B to G worked, and I assumed that ruled out having NODE B ACCESS NONE on G. Still, I should check just to be thorough. I'll e-mail that site and have them take a look. (I'll also be there myself on Monday.)
Mobeen,
I hadn't tried actually doing a purge and clear on the DECnet entries for the nodes involved. It's probably worth a shot, which I'll do on Monday unless the guys on site find something first.
Thanks,
Galen
(Points to follow when problem fixed.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2005 11:37 PM
тАО06-09-2005 11:37 PM
Re: DECnet address change leads to SET HOST problem
Just to give you a heads up, in our case i remember that when we delete and purge and create definitions for the nodes with problem on Decnet database, it used to just work fine the first time....
That is we would be able to "Set h" without any issues for the first time and any subsequent set h would fail. I hope it is not the same in your case :)
Will wait for you to give this a try and let us know how things fare
regards
Mobeen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-13-2005 06:45 AM
тАО06-13-2005 06:45 AM
Re: DECnet address change leads to SET HOST problem
If there is a router in say area 19, there should also be a router in area 53 and those routers should be handling cross-area stuff!
If there are NO ROUTERS at all, traffic will however work even across areas.
Even if there is just ONE router around, traffic may appear to work since your systems are end nodes and have endnode cache.
I would verify that each node correctly knows each other, i.e.
$ mcr ncp show node X
as well as routing stuff,
$ mcr ncp show known circuits
Obviously nodes in same area should see same router as the designated router and all involved nodes should see some routers
You say there is A CISCO ROUTER. I would read this as "there is a single router box" but the setup classically would require at least two router boxes (one for area 19, another for area 53).
Does the cisco box do some fancy NAT stuff?
_veli
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-13-2005 09:43 PM
тАО06-13-2005 09:43 PM
Re: DECnet address change leads to SET HOST problem
You wrote:
You say there is A CISCO ROUTER. I would read this as "there is a single router box" but the setup classically would require at least two router boxes (one for area 19, another for area 53).
It's been a very long time since I worked with Cisco routers myself--roughly since 1996. My memory is a bit foggy, but isn't it possible for a Cisco router to run one DECnet area on one interface, and another area on a different interface?
I will have to ask the site staff here if they know anything about this...
Also, you understand correctly that we have just one router.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-13-2005 11:05 PM
тАО06-13-2005 11:05 PM
Re: DECnet address change leads to SET HOST problem
On both B and G I did an NCP SHOW NODE other_node CHARACTERISTICS
On G I got back just the node name and address of B.
On B I got back G's node name and address, PLUS "Access = Incoming and Outgoing".
So I looked at the executor characteristics on G and found that its default access was set to NONE.
This told me that I needed to do the following on G:
NCP>SET NODE B ACCESS BOTH
and that fixed it.
I examined the node and executor access settings on these three nodes and found some apparent inconsistencies. I'll have to ask the guys here about that, since I don't know what reasons there may have been for this arrangement. Quite possibly it is just an accident.
If anything else interesting turns up within the next week or so, I'll follow up in this topic.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2005 09:51 PM
тАО06-19-2005 09:51 PM
Re: DECnet address change leads to SET HOST problem
NCP>SET NODE B ACCESS BOTH
on G.
It's a bit embarrassing that as longtime manager of DECnet I didn't spot this right off. :-}