- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Order of TCPIP logical TCPIP$INET_HOSTADDR & a...
Operating System - OpenVMS
1753843
Members
7793
Online
108806
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
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
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
11-04-2009 07:43 AM
11-04-2009 07:43 AM
Order of TCPIP logical TCPIP$INET_HOSTADDR & addr2
Somehow I've reconfigured HP TCPIP 5.1-3 in a way that's causing an application communication failure. Server has two DE500s, EWA0 is cabled to a 10Mb hub and has a 172.x.x.x address. EWB0 is cabled to a 100Mb switch and has a 199.x.x.x address.
Logicals show
"TCPIP$INET_HOSTADDR" = "172.a.b.c"
"TCPIP$INET_HOSTADDR2" = "199.d.e.f"
"UCX$INET_HOSTADDR" = "172.a.b.c"
A working system has the addresses reversed
"TCPIP$INET_HOSTADDR" = "199.d.e.f"
"TCPIP$INET_HOSTADDR2" = "172.a.b.c"
"UCX$INET_HOSTADDR" = "199.d.e.f"
How can I reconfig TCPIP in a manner that assign the logicals in the second manner?
Any help would be appreciated.
Logicals show
"TCPIP$INET_HOSTADDR" = "172.a.b.c"
"TCPIP$INET_HOSTADDR2" = "199.d.e.f"
"UCX$INET_HOSTADDR" = "172.a.b.c"
A working system has the addresses reversed
"TCPIP$INET_HOSTADDR" = "199.d.e.f"
"TCPIP$INET_HOSTADDR2" = "172.a.b.c"
"UCX$INET_HOSTADDR" = "199.d.e.f"
How can I reconfig TCPIP in a manner that assign the logicals in the second manner?
Any help would be appreciated.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2009 09:10 AM
11-04-2009 09:10 AM
Re: Order of TCPIP logical TCPIP$INET_HOSTADDR & addr2
First some background...
TCP/IP Services V5.1 is rather old; there are ECO kits and there are newer versions.
I'd not look at the order of the logical names here; this case looks to be bog-standard IP routing "fun." The lower-level settings establish the addresses.
But if you want to follow down this path, why not simply swap the Ethernet cables between the DE500 NICs within the box? Or use @SYS$MANAGER:TCPIP$CONFIG.COM to re-establish your network interface settings the way you want the addressing to work.
Or (more likely the solution) set up the default IP routes for whatever routing traffic you're tossing around. Getting this stuff to work with dual NICs means you have to have routing of some sort, either running as a full-on IP router, by ARP-based routing, or by establishing static routes.
TCP/IP Services V5.1 is rather old; there are ECO kits and there are newer versions.
I'd not look at the order of the logical names here; this case looks to be bog-standard IP routing "fun." The lower-level settings establish the addresses.
But if you want to follow down this path, why not simply swap the Ethernet cables between the DE500 NICs within the box? Or use @SYS$MANAGER:TCPIP$CONFIG.COM to re-establish your network interface settings the way you want the addressing to work.
Or (more likely the solution) set up the default IP routes for whatever routing traffic you're tossing around. Getting this stuff to work with dual NICs means you have to have routing of some sort, either running as a full-on IP router, by ARP-based routing, or by establishing static routes.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP