- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: not working Advanced Server Pathwork after ope...
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
тАО06-03-2009 12:02 AM
тАО06-03-2009 12:02 AM
not working Advanced Server Pathwork after openVMS autogen and reboot
After a autogen with reboot on a three node cluster the Advanced Server (PathWork) is unable to startup on one of the cluster nodes.
In PWRK$LMMCP_NODENAME.LOG i found:
LISTER\listeninit: Unable to post the name on any networl: NODENAME
PCS_SetConnectionLevel: group name has not been declared
and after that
SYSTEM job terminated at ...
Is there a problem with the network or where can I look up next? Please help me, I am a "fresh" openVMS Admin.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2009 12:51 AM
тАО06-03-2009 12:51 AM
Re: not working Advanced Server Pathwork after openVMS autogen and reboot
It is likely that the pwrk$knbdaemon process is not starting up correctly. You may want to check if there are any errors in the log file PWRK$ROOT:[LOGS]PWRK$KNBDAEMON_
Regards,
Shilpa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2009 01:04 AM
тАО06-03-2009 01:04 AM
Re: not working Advanced Server Pathwork after openVMS autogen and reboot
In PWRK$KNBDAEMON_NODENAME.LOG I found:
get_ip_addr: gethostname error: 0
I looked in TCPIP show host, there is a entry
IP-Adress Nodename
I can do ping, telnet usw. looks like network is on...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2009 03:23 AM
тАО06-03-2009 03:23 AM
Re: not working Advanced Server Pathwork after openVMS autogen and reboot
I am assuming that you are using TCPIP services provided HP. If so, can you execute the following command and see if the inet logicals are defined correctly?
$ sh log *inet*
Regards,
Shilpa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2009 03:39 AM
тАО06-03-2009 03:39 AM
Re: not working Advanced Server Pathwork after openVMS autogen and reboot
I used your command to look up the logicals on both nodes from the cluster.
On the one where Advanced Server still working I found these logicals in LNM$SYSTEM_TABLE
"TCPIP$INET_DOMAIN" = "..."
"TCPIP$INET_HOST" = "..."
"TCPIP$INET_HOSTADDR" = "..."
"UCXIP$INET_DOMAIN" = "..."
"UCXIP$INET_HOST" = "..."
"UCXIP$INET_HOSTADDR" = "..."
On the node where Advanced Server isn't working the logicals are missing.
So please can You tell me, where and when these logicals are set up. Thanks a lot!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2009 03:52 AM
тАО06-03-2009 03:52 AM
Re: not working Advanced Server Pathwork after openVMS autogen and reboot
usually these would be defined after you have configured your tcpip setup with tcpip$config.com and started tcpip services.
fwiw
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2009 03:55 AM
тАО06-03-2009 03:55 AM
Re: not working Advanced Server Pathwork after openVMS autogen and reboot
Looks like TCPIP is not configured correctly. As mentioned by Mark Hunt, you can use tcpip$config to reconfigure TCPIP.
Regards,
Shilpa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2009 04:01 AM
тАО06-03-2009 04:01 AM
Re: not working Advanced Server Pathwork after openVMS autogen and reboot
Okay, so realy a problem with TCP/IP?
But when I say TCPIP show service I get Information. Also I can ping the node and connect to this via Telnet. Also TCPIP show interface gets the correct interface configuration...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2009 04:10 AM
тАО06-03-2009 04:10 AM
Re: not working Advanced Server Pathwork after openVMS autogen and reboot
can't remember if there can be case sensitivity issues with the host name with this, have you an upper and lower case nodename (alias) in the host table to tie in with the logicals ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2009 04:18 AM
тАО06-03-2009 04:18 AM
Re: not working Advanced Server Pathwork after openVMS autogen and reboot
IP NODENAME, nodename
and the logicals are once defined:
TCPIP$.... = "nodename"
UCX$... = "NODENAME"
I looked up the Processes running on both nodes an found an missing entry on the node where advanced server isn't running.
The missing process is TCPIP$PWIP_ACP, I looked up with TCPIP$CONFIG.COM and tried to stop and start but still missing... Is it possible this is the problem?