Hi All


When i execute addnode command its connected to dmgr after completing some operation dmgr system not look up appserver node system hostname.....

 
8:08:20:750 IST 0000000a AdminTool A ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.AdminExcept ion: ADMU0036E: The Deployment Manager cannot lookup by name host T61O.in.ibm.com at address 9.124.98.83


please help me...   its urgent.......


i added hostname in both systems host files .. no solution.....


Thanks
Chinna

Hi Chinna,

Do you have more than IP address on this node server, if so it looks like a DNS resolve issue so try to use IP address in adding this node instead.

//Ahmed

Hi Ahmed,

Thanks for ur reply....


I checked today......... SOAP port is not listening from one system to another sytem.

When i execute "telnet Dmgrhostname SOAP" from Appserver system SOAP port is not listening..... same scenario from Dmgr machine to appserver machine........

Please  suggest this is problem ....... i think this port should listen from one to one....

Please correct if i am wrong.....

Thanks

Chinna

Hi,

well said, SOAP port should be opened on dmgr server so please make sure that dmgr is started correctly by accessing its admin console and check on its systemout.log as well.

//Ahmed

I'd suggest you do the following to troubleshoot:
1. Verify that your DMGR is up and acessible as Ahmed indicated
2. Verify whether you can ping the alias you defined in the host file from each server
3. Verify the DMGR SOAP port via the admin console


Here's a link to an old technote you might want to look at:
publib.boulder.ibm.com/infocenter/wasinf...

Erik  

Hi china,

I agree with Erik and Ahmed inputs,


Also i request you to check "is there any firewall blocking the ports" take support from OS and Network team to resolve the issue earliest.


Thanks&Regards,
Rajkumar N

Hi Chinna

I agree with Ahmed, Erik, and Rajkumar about making sure the DMGR is up and running with no errors in the logs during startup related to ports. If that is good try federating the node from the admin console at System administration > Nodes.

This has worked for me in the past when I had problem federating a node using the addnode command.