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.
- 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.
- Tracing the discovery process on the nodeagent and dmgr:
- Stop all WebSphere Application Server processes (no java.exe).
- Modify the server.xml files for both nodeagent and dmgr:
- Enable discovery tracing on the dmgr:
- Edit the server.xml file for the dmgr located in
WAS_ND/config/cells/cellname/nodes/nodename/servers/dmgr
directory.
- Find the TraceService xml tag section.
- Modify the startupTraceSpecification entry to look like the following:
com.ibm.ws.management.*=all=enabled
- Make sure enable is set to true.
- Enable discovery tracing on the nodeagent:
- Edit the server.xml file for the nodeagent located in
WAS_BASE/config/cells/I/nodes/I/servers/nodeagent directory.
- Find the TraceService xml tag section.
- Modify the startupTraceSpecification entry to look like the following:
com.ibm.ws.management.*=all=enabled
- Make sure enable is set to true.
- Clear all the files in the WAS_BASE/logs and WAS_ND/logs
directory.
- Issue a netstat -an > before.txt.
- Start the nodeagent and dmgr.
- Open a console and look at System administration >
Nodes to see if the node is still status Unknown.
- Issue a netstat -an > after.txt.
- Stop nodeagent and dmgr.
- Run the collector tool on both Network Deployment and BASE.
- Open a PMR with IBM
- 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
- 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.
|