- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- TCPIP issues on an Alpha ES45 running OPVM V7.3-2
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
тАО11-24-2008 06:00 AM
тАО11-24-2008 06:00 AM
The main reason for this is because I have three nodes in a cluster, the first and second nodes are on the same vlan 10.1.1.nn while the third node is on a different vlan 10.128.8.nn.
The tcpip$configuration logical is pointing to a common file. When I configured TCPIP (tcpip$config) on the third node, the gateway changed for all three nodes. (I.e. the first node ip: 10.1.1.12 using the 10.1.1.1 gateway, the second node ip; 10.1.1.10 using the 10.1.1.1 gateway.) The third node ip is 10.128.8.26 using the 10.128.8.101 gateway.
This caused an issue when the cluster was rebooted. I attempted to redefine the tcpip$configuration logical on the third node and reconfigured tcpip but each time a reconfigured the gateway it would change on the first and second nodes. I've even attempted a reboot of the third node but to no avail same issue.
$ @sys$startup:tcpip$shutdown
%TCPIP-I-INFO, TCP/IP Services shutdown beginning at 24-NOV-2008 08:37:54.24
%TCPIP-E-INETERROR, internet interface error
-TCPIP-E-NOINET, the internet driver is not loaded
The following Internet devices are still active on
Your system:.....
$ tcpip show ver
HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 6
on a AlphaServer ES45 Model 2 running OpenVMS V7.3-2
BG10000:
$ show system/proc=tcpip*
OpenVMS V7.3-2 on node HMES04 24-NOV-2008 08:42:31.57 Uptime 0 21:37:50
Pid Process Name State Pri I/O CPU Page flts Pages
2080048D TCPIP$INETACP HIB 8 175 0 00:00:00.01 169 90
$ show dev bg/full
Device BG0:, device type unknown, is online, mounted, record-oriented device,
network device, mailbox device, device is a template only.
Error count 0 Operations completed 0
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:RWPL,W:RWPL
Reference count 0 Default buffer size 256
Device BG10000:, device type unknown, is online, mounted, record-oriented
device, network device, mailbox device.
Error count 0 Operations completed 10
Owner process "TCPIP$INETACP" Owner UIC [SYSTEM]
Owner process ID 2080048D Dev Prot S:RWPL,O:RWPL,G:RWPL,W:RWPL
Reference count 1 Default buffer size 256
Any help in this area would be greatly appreciated.
Thank you,
Ronald J. Russik
Sr. Systems Engineer - OpenVMS
YRCW Technologies, Inc.
10990 Roe Avenue
Overland Park, KS 66211-1213
Desk: 913-344-5502
Cell: 913-568-1851
Text: 9135681851@vtext.com
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2008 06:32 AM
тАО11-24-2008 06:32 AM
Solutionthe default route information seems to be stored in the file pointed to by the TCPIP$ROUTE system logical and would typically be SYS$COMMON:[SYSEXE]TCPIP$ROUTE.DAT;1
On a common system disk, this file would be used by all nodes in the cluster booting from that disk. And changing the default gateway on one of the nodes will also change it on the other nodes, as there is only ONE file to store this information.
You may get around this problem by putting a TCPIP$ROUTE.DAT file into the specific directory of the 3rd node and defining a TCPIP$ROUTE logical - before starting TCPIP - to point to that file on that node.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2008 06:39 AM
тАО11-24-2008 06:39 AM
Re: TCPIP issues on an Alpha ES45 running OPVM V7.3-2
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2008 11:08 AM
тАО11-24-2008 11:08 AM
Re: TCPIP issues on an Alpha ES45 running OPVM V7.3-2
Thank you for all your help,
Ron Russik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-07-2009 04:48 AM
тАО05-07-2009 04:48 AM