- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- tcpip route could not be fixed
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
тАО07-06-2015 11:31 PM
тАО07-06-2015 11:31 PM
tcpip route could not be fixed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2015 06:18 PM
тАО07-07-2015 06:18 PM
Re: tcpip route could not be fixed
OK, so you have a cluster or two running comparatively old OpenVMS and TCP/IP software, one of which is not maintaining the default route across servers within the cluster, and another cluster which apparently is maintaining the routing.
What TCP/IP Services version and patch levels are in use for the various servers involved here? (You do mention duplicates, but are those hosts in the second cluster manually created copies, or are they copies imaged from the problematic configuration? Identical hardware for both clusters, or are there different models or types of Itanium servers in use?)
What command(s) are you using to change the default route on the working and not-working configurations?
What command(s) are you using to show that the default route has been lost?
What are the differences between the working and the not-working cluster configurations?
Are BGP or other routing protocols in use?
Any reason that you're not running OpenVMS V8.4 with TCP/IP V5.7; something a little more recent than V8.3-1H1?
I'd probably look to use the blade inboard NAT тАФ HP has a fancy marketeering name for this NAT тАФ to avoid having to reset the network, too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2015 06:42 PM
тАО07-13-2015 06:42 PM
Re: tcpip route could not be fixed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-15-2015 10:44 AM
тАО07-15-2015 10:44 AM
Re: tcpip route could not be fixed
(This and your first post are pretty unreadable. It would be nice if you could use Post Options > Edit Reply to add some paragraphs and newlines.)