locked
SOA and Network Topology RRS feed

  • Question

  • All of our SOA service calls are failing because the endpoints "private.{ComputeNode}" cannot be resolved via DNS. Our HPC cluster has been configured as an "Enterprise Network" without any private network component. Can SOA work with this topology or do we need to change the topology to one that includes an HPC private network?

    Thanks.
    Monday, January 4, 2010 1:34 PM

Answers

  • In fact, the WCF_NETWORKPREFIX should be Enterprise. (Please make sure you have Enterprise.{CN} in your hosts file.)

    Normally the value should be automatically updated after you set the network topology but sometime it'll go out-of-sync. Manually set it should fix the problem.
    • Marked as answer by Simon Place Tuesday, January 5, 2010 10:30 AM
    Tuesday, January 5, 2010 6:45 AM

All replies

  • Hi Simon,

    "Enterprise Only" - Topology 5 is supported for SOA. In your case, can you do 2 things?

    1. Go to your borker node and compute node, take a look at the %windir%\System32\drivers\etc\hosts file. And see if they get those private.{CN} entry?

    2. Do a "cluscfg listenvs -scheduler:<Headnode>" and paste the result here? Specifically, what's the value of WCF_NETWORKPREFIX?

    Thanks
    Yiding

    Monday, January 4, 2010 2:19 PM
  • Hi Yiding

    Thanks for your reply.

    The hosts files do not contain the private.{CN} entries unles we add them manually.

    Also WCF_NETWORKPREFIX=Private.

    So I guess that is the key. Do we want to look at changing that value?

    Thanks
    Simon
    Monday, January 4, 2010 3:22 PM
  • Yiding

    This solves our problem:

    cluscfg setenvs -scheduler:{HN} "WCF_NETWORKPREFIX="

    Thanks for your help.

    Simon

    • Marked as answer by Simon Place Monday, January 4, 2010 3:42 PM
    • Unmarked as answer by Simon Place Tuesday, January 5, 2010 10:31 AM
    Monday, January 4, 2010 3:42 PM
  • In fact, the WCF_NETWORKPREFIX should be Enterprise. (Please make sure you have Enterprise.{CN} in your hosts file.)

    Normally the value should be automatically updated after you set the network topology but sometime it'll go out-of-sync. Manually set it should fix the problem.
    • Marked as answer by Simon Place Tuesday, January 5, 2010 10:30 AM
    Tuesday, January 5, 2010 6:45 AM
  • Hi Yiding

    Yes, we do have the "Enterprise.{CN} entries. Thanks for the pointer.

    Cheers

    Simon

     

    Tuesday, January 5, 2010 10:30 AM