Scenario one
The Network Deployment Manager token is used or locked.
To release the token, wait 30 minutes for the token to expire, or run
the following commands in wsadmin:
wsadmin>set a [$AdminControl
completeObjectName type=AdminOperations,process=dmgr,*]
Returns the following before the wsadmin prompt if successful:
WebSphere:platform=common,cell=chewiNetwork1,version=5.0,name=AdminOperations,mbeanIdentifier=AdminOperations,type=AdminOperations,node=chewiManager1,process=dmgr
wsadmin>$AdminControl invoke $a forceNodeFederationOrRemovalTokenReset
Returns back to the wsadmin prompt.
Scenario two
The dmgr process is stopped during the federation process.
Review the dmgr logs to determine if the process stopped, if the
process crashed, or if something else occurred during the federation
process. You must determine why it stopped and if it will stop again the
next time you try to federate the Base node.
One interesting case where the addNode script causes itself to fail
during the federation process is when the addNode script pings all
Application Servers on that installation through the
SOAP_CONNECTOR_ADDRESS. If a WebSphere process is listening, the addNode
script issues a stop command to stop the WebSphere process.
If the Base and ND nodes are on the same machine and the
SOAP_CONNECTOR_ADDRESS of one Application Server matches the
SOAP_CONNECTOR_ADDRESS port of the dmgr, the addnode script stops the
dmgr, causing the script to fail.
|