PQ74969: IN A MULTI-HOME TCP/IP SETUP SERVER FAILS TO START WITH A MESSAGE INDICATING THE NODE AGENT IS NOT ACTIVE | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description In a multi-home TCP/IP setup with VIPA, in an ND configuration after attempting to start a server from the admin console, receiving message: "The node agent on node xxxx is not active. The server can not be started." The node agent is running as well as the DMGR and the Daemon. . The server is started from the admin console. After refresh of the status the displayed status in "unavailable". Then if the server is started from the admin console you see: "The node agent on node xxxx is not active. The server can not be started." Trace shows that node agent comes back with the IP of primary home interface. The IP going out from the DMGR is a VIPA from the same system. Multi home IPs are used for that system. This failure shows for the DiscoveryService. . The following ports will be affected by the multi-homed host setup: soap, drs, node discovery, node multicast discovery, and cell discovery.Local fix Change the IP address of the server to the first one in the TCPIP Home List (to the one the Nodeagent tried to use).Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: In a multi-home TCP/IP setup in an * * Network Deployment configuration, * * starting a server from the * * administrative console resulted in the * * following message: * * * * "The node agent on node xxxx is not * * active. The server can not be started." * **************************************************************** * RECOMMENDATION: * **************************************************************** The daemon, deployment manager and node agent were started. A server was started from the console. On refreshing, the status of the server on the administrative console appeared as "unavailable". Starting the server from the admin console results in the following message: "The node agent on node xxxx is not active. The server can not be started." In the multi-home TCP/IP setup, the ip addresses being used by the node agent to discover the deployment manager was different from the IP used by the Deployment Manager to identify itself and hence the processes could not discover each other.Problem conclusion Support was added for multi-home systems, accomodating the discovery protocol and following ports SOAP, Node Discovery, Node Multicast Discovery, and Cell Discovery. By default, the behaviour will assume multi-homed behaviour for the above ports. APAR PQ74969 is associated with SERVICE LEVEL W500103 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ74969.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ74969
IBM Group: Software Group
Modified date: Aug 8, 2003
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.