MustGather: Node agent and Deployment Manager discovery problems for all releases and editions of V5.0 and V5.1
 Technote (FAQ)
 
Question
MustGather for problems with the IBM® WebSphere® Application Server node agent and Deployment Manager discovery process. Gathering this information before calling IBM support helps familiarize you with the troubleshooting process and saves you time.
 
Answer

Node agent and Deployment Manager discovery problems for all releases and editions of V5.0 and V5.1

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.


Component specific MustGather:


In the administrative console under System Administration > Nodes, the node in question has a Status of Unknown, or it is using wsadmin and is not able to get the $AdminControl MBean object for the nodeagent. However, the nodeagent and the Deployment Manager are running.

The nodeagent and Deployment Manager must discover each other to have synchronization and administrative commands work properly on the BASE node. There are multiple reasons why the nodeagent and the Deployment Manager might not be able to talk to each other correctly.

  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 PQ71669 efix or use Fix Pack 1 or higher for version V5.0.

  2. Tracing the discovery process on the nodeagent and dmgr:

    1. Stop all WebSphere Application Server processes (no java.exe).
    2. Modify the server.xml files for both nodeagent and dmgr:
      1. Enable discovery tracing on the dmgr:
        1. Edit the server.xml file for the dmgr located in WAS_ND/config/cells/cellname/nodes/nodename/servers/dmgr directory.
        2. Find the TraceService xml tag section.
        3. Modify the startupTraceSpecification entry to look like the following:

          com.ibm.ws.management.*=all=enabled

        4. Make sure enable is set to true.
      2. Enable discovery tracing on the nodeagent:
        1. Edit the server.xml file for the nodeagent located in WAS_BASE/config/cells/I/nodes/I/servers/nodeagent directory.
        2. Find the TraceService xml tag section.
        3. Modify the startupTraceSpecification entry to look like the following:

          com.ibm.ws.management.*=all=enabled

        4. Make sure enable is set to true.
    3. Clear all the files in the WAS_BASE/logs and WAS_ND/logs directory.
    4. Issue a netstat -an > before.txt.
    5. Start the nodeagent and dmgr.
    6. Open a console and look at System administration > Nodes to see if the node is still status Unknown.
    7. Issue a netstat -an > after.txt.
    8. Stop nodeagent and dmgr.
    9. Run the collector tool on both Network Deployment and BASE.

  3. Open a PMR with IBM

    1. Use the Service Request (SR) tool:

      http://www-3.ibm.com/software/support/sr/

      Use the Attach Relevant File button to attach log files and other diagnostic information.

      OR

    2. Call 1-800-IBM-SERV and follow the instructions to send diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to theWebSphere Application Server node agent and Deployment Manager component, search the WebSphere Application Server support site.

 
 
 


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.1.2
Software edition:
Reference #: 1140942
IBM Group: Software Group
Modified date: Dec 8, 2004