MustGather: Node Federation or addNode Problems for all Releases of V5.0 Base and Network Deployment
 Technote (troubleshooting)
 
Problem(Abstract)
Collecting data for problems with the IBM® WebSphere® Application Server V5.0 node federation or the addNode command. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.
 
Resolving the problem

Node Federation or addNode Problems for all Releases of Websphere Application Server V5.0 Base and Network Deployment

If you have already contacted support, continue on to the component-specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.

Node federation or addNode command specific MustGather:

To troubleshoot why the addNode command is not working following these steps, top down. Also, "$WAS_HOME" is the absolute path to the Application Server or Network Deployment installation.

  1. Stop all WebSphere Java™ processes.

  2. Backup (if needed) and then purge all logs in $WAS_HOME/logs directory on the WebSphere Application Server (Base) node.

  3. Start the WebSphere Deployment Manager by issuing the following command from the $WAS_HOME/bin directory:

    startManager.bat/sh

  4. On the Application Server (Base) node, verify that no Application Servers are running by issuing the following command from the $WAS_HOME/bin directory:

    serverStatus.bat/sh –all

  5. If any of the application servers are started, stop them by issuing the following command from the $WAS_HOME/bin directory:

    stopServer.bat/sh server1

    Note: Your server name may vary depending on your naming convention.

  6. On the Application Server (BASE) node issue the following command from $WAS_HOME/bin directory:

    addNode.bat/sh <dmgr host> <dmgr SOAP port>

    where dmgr host is the host name of the WebSphere Deployment Manager Node and dmgr SOAP port is the SOAP port for that node (default is 8879).

Notes:
If the above steps do not complete or if you have errors during the above process, gather the following information:
  1. To capture a trace of the addNode command, issue the following command from $WAS_HOME/bin directory:

    ./addNode.bat/sh <dmgr host> <dmgr SOAP port> -trace

    NOTE: The trace output is logged to the addNode.log file located in the $WAS_HOME/logs directory.

  2. Collect Network Interface Card (NIC) information by running the following command from both the Base and ND nodes:

    UNIX®:
    ifconfig –a > $WAS_HOME/logs/
    ifconfig.out

    Microsoft® Windows®:
    c:\ipconfig  /all > $WAS_HOME\logs\ipconfig.out

  3. Please collect netstat information from the Base and Network Deployment nodes:

    UNIX:
    netstat –an > $WAS_HOME/logs/netstat_Base.out
    netstat –an > $WAS_HOME/logs/netstat_ND.out

    Windows:
    C:\netstat –an > $WAS_HOME\logs\netstat_Base.out
    C:\netstat –an > $WAS_HOME>\logs\netstat-ND.out

    Start a telnet session from the Base node to the Network Deployment node and collect the output result from the following command:

    telnet < dmgr SOAP port >

    Collect the screen output to a file telnet.out

  4. Follow directions in MustGather: Readme First, open PMR and send data to IBM Support.

  5. Follow instructions to send diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to the component, search the WebSphere Application Server support site.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): Windows
Software version: 5.1
Software edition:
Reference #: 1141241
IBM Group: Software Group
Modified date: Feb 12, 2007