For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

jkrumenacher_13's avatar
jkrumenacher_13
Icon for Nimbostratus rankNimbostratus
May 08, 2014

Error adding AD servers in iAPP

Error:

 

Configuration error: Pool member node /serverSUP/100.1.2.x and existing node /Common/BIL-USDC-106 cannot use the same IP Address 100.1.2.x

 

This is how I tested the Exchange in the test deployment and it didn't error out

 

iApp:

 

Which Active Directory servers in your domain can this BIG-IP system contact?

 

FQDN BIL-USDC-106.test.com IP 100.1.2.x

 

Any ideas?

 

Thanks, jkrum

 

4 Replies

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account

    Hi jrkum, I don't quite understand. In your test environment, the iApp didn't throw this error, but in production it did?

     

    It looks like you are trying to deploy the same node IP on two different partitions, is that correct?

     

    Mike

     

  • Yes, that is exactly right. I did execute the iAPP in the common partition in test. Good catch. There is a different support team that manage each partition so ultimately I want the Exchange environment in serversup partition. Thoughts? Ideas?

     

    Thanks, jkrum

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account

    It seems like it could be a bug, I'll have to do some testing to know if it's expected behavior. For now, is it possible to choose a different domain controller for your Exchange deployment?

     

  • To get around it I entered a bogus AD and after the iAPP completed I went and edited the exchange_aaa_pool with the correct controllers. I am looking at this more from a hand off/support perspective. Thanks, jkrum