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.
- Stop all WebSphere Java™ processes.
- Backup (if needed) and then purge all logs in $WAS_HOME/logs directory
on the WebSphere Application Server (Base) node.
- Start the WebSphere Deployment Manager by issuing the following
command from the $WAS_HOME/bin directory:
startManager.bat/sh
- 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
- 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.
- 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:
- 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.
- 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
- 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
- Follow directions in MustGather: Readme First, open PMR and send data to
IBM Support.
- 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. |