HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: DecNet Phase V Issue on New Integrity Servers
Operating System - OpenVMS
1828983
Members
2327
Online
109986
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
01-31-2007 03:35 AM
01-31-2007 03:35 AM
DecNet Phase V Issue on New Integrity Servers
Forum-mates,
I've got a new 3-node Integrity cluster (VMS 8.3) I'm setting up to replace our Alpha Cluster. Am having issues with Decnet Phase V and I'm sure it's probably because I've either configured something wrong or didn't configure something that I should have during initial setup and NET$CONFIGURE runs. Anyway, here's what's happening and not happening. To test Decnet, I usually test the SET HOST capability and MONI CLUSTER.
Here are results of testing:
1. Cannot SET HOST out from one Integrity node to another in the new cluster
2. MONI CLUST does not run on any of the 3 Integrity server nodes
3. I CAN SET HOST out to the existing Alpha Cluster and I can also SET HOST into the Integritys from the Alpha Cluster.
Any clues as to what I may have done wrong or neglected to do?
Thx,
Warren
I've got a new 3-node Integrity cluster (VMS 8.3) I'm setting up to replace our Alpha Cluster. Am having issues with Decnet Phase V and I'm sure it's probably because I've either configured something wrong or didn't configure something that I should have during initial setup and NET$CONFIGURE runs. Anyway, here's what's happening and not happening. To test Decnet, I usually test the SET HOST capability and MONI CLUSTER.
Here are results of testing:
1. Cannot SET HOST out from one Integrity node to another in the new cluster
2. MONI CLUST does not run on any of the 3 Integrity server nodes
3. I CAN SET HOST out to the existing Alpha Cluster and I can also SET HOST into the Integritys from the Alpha Cluster.
Any clues as to what I may have done wrong or neglected to do?
Thx,
Warren
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2007 03:59 AM
01-31-2007 03:59 AM
Re: DecNet Phase V Issue on New Integrity Servers
HP Support actually got back to me in a timely manner on this and was able to solve problem for me.
For reference of anyone else who might have this type of deal, here's what needed to be done.
1) Run sys$system:decnet_register and define the other 2 cluster nodes via their Local Name and Decnet ID
2) MC NCl> FLUSH SESSION CONTROL NAMING CACHE ENTRY "*" tomake changes take effect immediately instead after the default of 8 hours for updating.
That's it.
Warren
For reference of anyone else who might have this type of deal, here's what needed to be done.
1) Run sys$system:decnet_register and define the other 2 cluster nodes via their Local Name and Decnet ID
2) MC NCl> FLUSH SESSION CONTROL NAMING CACHE ENTRY "*" tomake changes take effect immediately instead after the default of 8 hours for updating.
That's it.
Warren
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP