Skip to Content

Server IP Binding Check Alert for "Auto Assigned" APS services invalid

Running a 2.1.1 landscape report against a 4.2 SP4 multi-server cluster, I get alerts on each node where there is an Adaptive Processing Server (including WACS and Lumira) stating as follows:


Server IP Binding Check

One or more BI Servers were found to have a different hostname/ip binding configuration when compared to the other servers on the same node. All BI servers under a common SIA should use the same binding configuration.

This information can be found by comparing the server IOR and/or the '-port' and '-ipv6' command line arguments on each server. The IOR shows which name or ip the running BI server is currently bound to. The description in parenthesis shows whether this value was auto-assigned in the CMC > Servers properties page or if it was set set by the administrator. Please refer to the Landscape Analysis Report for more details.


I checked, and EVERY server under that node/SIA has the identical configuration for hostname/IP configuration (all are set to Auto assign under "Common Settings")

I can disable the alert, but it would be something to look at.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Apr 13, 2018 at 04:45 PM


    Could you save the landscape report as a .zip and shoot it off to

    I'll take a look.

    I took a quick look at the alert and it checks the Corba IOR Stub, pulls out the host: parameter and compares it to the rest of the servers in the cluster. Is this mismatched between the Java/non-Java servers?


    Add comment
    10|10000 characters needed characters exceeded

    • I don't think I need the files, since that's the info I wanted.

      I'll bring it up with the team, but in general, the purpose of the alert is to warn when BI servers are bound to different network addresses in Multi-NIC machines. I'll check whether or not we should update the alert to only consider the hostname - I think we should since it was primarily intended to check for IP address differences.

      Provided all machines in the environment can communicate to other machines by both FQDN and by hostname, I don't think it'd be an issue.

  • Apr 17, 2018 at 09:04 AM

    Hi Folks,

    I too am receiving the same alerts for what sounds like an identical system environment - would be interested to hear how this issue progresses and what the resolution is.

    Add comment
    10|10000 characters needed characters exceeded