TroubleShooting: Node agent and Deployment Manager discovery problems
 Technote (troubleshooting)
 
Problem(Abstract)
TroubleShooting for problems with the WebSphere® Application Server Node agent and Deployment Manager discovery component. This should help address common issues with this component before calling IBM support and save you time.
 
Resolving the problem

1. Learning more 2. Troubleshooting 3. Collecting data 4. Analyzing data

Steps to help resolve Node agent and Deployment Manager discovery problems

  1. If you have multiple network interface cards (NIC) on the nodeagent or Deployment Manager node, and you do not want to use the primary NIC, you must apply Interim Fix PQ71669 or use Fix Pack 1 or higher for version V5.0.

  2. Are both processes running? (Message ADMD0004E may be seen in an FFDC log if either process is not running.)
    • Yes, continue to the next question.
    • No, start the process.

  3. Is there a firewall between the processes?
    • Yes, make sure the ports are open, help.
    • No, continue to next question.

  4. Is the discovery port listening?

What to do next?
If the preceding troubleshooting steps did not solve your problem, see the MustGather for Node agent and Deployment Manager Discovery problems to continue investigation.
 
Related information
Submitting information to IBM Support
Steps to getting support
Troubleshooting guide
 
 
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: 6.0
Software edition:
Reference #: 1201625
IBM Group: Software Group
Modified date: Jun 6, 2006