HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Upgrade V7.2 Vax 4300
Operating System - OpenVMS
1829404
Members
1700
Online
109991
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
Go to solution
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
06-11-2006 04:39 AM
06-11-2006 04:39 AM
I finished upgrading our VAx 4300. When I ram autogen I found the following warning. CAn someone tell me if this is anything to worry about?
** WARNING ** Conflicting definitions in MODPARAMS.DAT:
RECNXINTERVAL is defined to be 60
This overrides MIN_RECNXINTERVAL value of 60
Override Information - parameter calculation has been overridden.
The calculated value was 20. The new value is 60.
RECNXINTERVAL has been set to the hard-coded value of 60.
RECNXINTERVAL is not allowed to be less than 60.
Thanks!
** WARNING ** Conflicting definitions in MODPARAMS.DAT:
RECNXINTERVAL is defined to be 60
This overrides MIN_RECNXINTERVAL value of 60
Override Information - parameter calculation has been overridden.
The calculated value was 20. The new value is 60.
RECNXINTERVAL has been set to the hard-coded value of 60.
RECNXINTERVAL is not allowed to be less than 60.
Thanks!
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2006 07:59 AM
06-11-2006 07:59 AM
Solution
Apparently, you have both a
RECNXINTERVAL = 60
and a
MIN_RECNXINTERVAL = 60
in your MODPARAMS.DAT.
You don't need both, but as the "new value
is 60", the biggest problem would appear to
be the warning itself.
I'd remove the line you like less, and then
re-AUTOGEN.
RECNXINTERVAL = 60
and a
MIN_RECNXINTERVAL = 60
in your MODPARAMS.DAT.
You don't need both, but as the "new value
is 60", the biggest problem would appear to
be the warning itself.
I'd remove the line you like less, and then
re-AUTOGEN.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2006 08:22 AM
06-11-2006 08:22 AM
Re: Upgrade V7.2 Vax 4300
If the node is not a cluster member, I'd eliminate both entries.
If it is a cluster member, I'd try to find out *who* made the addition(s) and ask him or her why it was felt that the default of 20 seconds was not long enough.
There can be valid reasons for using a higher-than-normal value for RECNXINTERVAL (like a less-than-reliable cluster interconnect).
-- Rob
If it is a cluster member, I'd try to find out *who* made the addition(s) and ask him or her why it was felt that the default of 20 seconds was not long enough.
There can be valid reasons for using a higher-than-normal value for RECNXINTERVAL (like a less-than-reliable cluster interconnect).
-- Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2006 03:31 AM
06-12-2006 03:31 AM
Re: Upgrade V7.2 Vax 4300
recnxinterval = 20 works well for very good networks, 60 is a better number for an average network. If you have a busy network, set it to 120 cluster-wide to avoid spurious CLUEXITS when your interconnect is exclusively Ethernet and your segment is busy. The other important part is setting it consistently on every node.
Remove it from Modparams, except as a comment for documentation purposes. Autogen/Feedback won't reset it.
Regards, /jeff
Remove it from Modparams, except as a comment for documentation purposes. Autogen/Feedback won't reset it.
Regards, /jeff
le plus ca change...
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