Skip to Content
1

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

Apr 13 at 04:14 PM

59

avatar image

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.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Leslie Mui
Apr 13 at 04:45 PM
0

Hi,

Could you save the landscape report as a .zip and shoot it off to leslie.mui@sap.com?

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?


Thanks,
Leslie

Show 4 Share
10 |10000 characters needed characters left characters exceeded

Leslie,
I sent you the landscape report as requested.

Not knowing where to find the CORBA IOR Stub, I cannot answer that, however the settings were consistent when looking at the properties section of each server within the CMC.

Please let me know if you need further information.

Garrick.

0

Hi Garrick,

I think the spam filter caught the email, I can't find it.

The easiest way to get the IOR values is via the communications analyzer (Tool -> Landscape Tools -> Communications Analyzer).

Execute it against your landscape, export the results to excel, and in the excel document, check the "Decoded IOR" column.

One of the values in that should be host:

If you can, try shooting the email with the xlsx attachment - hopefully that makes it through.

Regards,
Leslie

0

Leslie,

I checked this, and here is what I found (I don't think we need the .xlsx file for this, since I think we may have found the issue).

On the servers that generate the alert, each one of them has the ipv4 address that shows in each of the other servers, but also has a dummy ip6 value. eg: 172.1.1.1,0:0:0:0:0:0:0:1.

In addition, each of the alerting servers shows the "server name" in the Host: value, and the "FQDN" in the alternate host profile. (I changed our platform-specitic data so nothing is "exposed". eg;

Java based server:

byteorder: little endian type_id: IDL:img.seagatesoftware.com/ImplServ/OSCAFactoryEx:3.1 IIOP profile #1: iiop_version: 1.2 host: servername port: 12345 object_key: (53) Native char codeset: "ISO 8859-1:1987; Latin Alphabet No. 1" Char conversion codesets: "ISO 646:1991 IRV (International Reference Version)" "ISO/IEC 10646-1:1993; UTF-16, UCS Transformation Format 16-bit form" "ISO/IEC 10646-1:1993; UCS-2, Level 1" Native wchar codeset: "ISO/IEC 10646-1:1993; UTF-16, UCS Transformation Format 16-bit form" Wchar conversion codesets: "ISO/IEC 10646-1:1993; UCS-2, Level 1" Alternate IIOP address #1: host: servername.domain.com port: 12345


Non-Java based server:

byteorder: little endian
type_id: IDL: img.seagatesoftware.com/ImplServ/OSCAFactory:3.1
IIOP profile #1:
iiop_version: 1.1
host: servername.domain.com
port: 65307
object_key: (32)
Native char codeset:
"ISO 8859-1:1987; Latin Alphabet No. 1"
Native wchar codeset:
"ISO/IEC 10646-1:1993; UCS-2, Level 1"


So the issue could be related to one of two things: First, the Java.exe services seem to want to look at local name instead of FQDN, and also are trying to listen on ip6, even though we have that disabled on the server (windows 12r2)

...

I also checked my Linux system, and it's a little different, but with the same result.

The Java based processes all show the FQDN in the Decoded IOR field under Host:, but the other servers show just the name

Non-Java based server:

"byteorder: little endian type_id: IDL:img.seagatesoftware.com/ImplServ/OSCAFactory:3.1 IIOP profile #1: iiop_version: 1.1 host: servername port: 41935 object_key: (32) Native char codeset: ""ISO 8859-1:1987; Latin Alphabet No. 1"" Native wchar codeset: ""ISO/IEC 10646-1:1993; UCS-2, Level 1"" "

Java based server

"byteorder: little endian type_id: IDL:img.seagatesoftware.com/ImplServ/OSCAFactoryEx:3.1 IIOP profile #1: iiop_version: 1.2 host: servername.domain.com port: 35080 object_key: (53) Native char codeset: ""ISO 8859-1:1987; Latin Alphabet No. 1"" Char conversion codesets: ""ISO 646:1991 IRV (International Reference Version)"" ""ISO/IEC 10646-1:1993; UTF-16, UCS Transformation Format 16-bit form"" ""ISO/IEC 10646-1:1993; UCS-2, Level 1"" Native wchar codeset: ""ISO/IEC 10646-1:1993; UTF-16, UCS Transformation Format 16-bit form"" Wchar conversion codesets: ""ISO/IEC 10646-1:1993; UCS-2, Level 1"" "


Let me know if you would still like the files, I suspect if the filter stopped the landscape report, it would stop these also.

Thanks,

Garrick.

0

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.

0
avatar image
Former Member Apr 17 at 09:04 AM
0

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.

Share
10 |10000 characters needed characters left characters exceeded