2564209 - SYSTEM MANAGER: instance list does not contain SUM central instance

Following error occurs during SUM run in step PREP_PRE_CHECK INSTANCELIST_INIT:

Directory: /usr/sap/<SID>/SUM/abap/log
Name: SAPup.log
   ...
CURRENTPHASE PREP_PRE_CHECK/INSTANCELIST_INIT
...started at 20171115120525
# Using phase log file 'INSTANCELIST_INIT.LOG'.
...finished at 20171115120531 with status ABORTED.
# Error message set: 'SYSTEM MANAGER: instance list does not contain SUM central instance.'
...begin dialog at 20171115120532
 
Directory: /usr/sap/<SID>/SUM/abap/log
Name: INSTANCELIST_INIT.LOG
   ...
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO DIAG_YES.
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO DIAG_YES.
1EETQ399 SYSTEM MANAGER: initialize instance list has failed.
1EETQ399 SYSTEM MANAGER: instance list does not contain SUM central instance.
1EETQ399 Last error code set is: SYSTEM MANAGER: instance list does not contain SUM central instance.

• The SAP system consists of several instances on different servers.

Case 1

• sapcontrol -nr <instance number> -function GetSystemInstanceList returns the instance list only partly, some of the are missing.

For example,
in SM51 following three instances appear (instance numbers may differ):

<host1>_<SID>_00 <host1> Dialog Batch Update Upd2 Spool ICM Active
<host2>_<SID>_00 <host2> Dialog Batch Update Upd2 Spool ICM Active
<host3>_<SID>_00 <host3> Dialog Batch Update Upd2 Spool ICM VMC Active

GetSystemInstanceList webmethod returns only two of them, the third one is missing:

sapcontrol -nr 0 -function GetSystemInstanceList

15.11.2017 14:06:09
GetSystemInstanceList
OK
hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus
<host1>, 0, 50013, 50014, 3, ABAP GATEWAY ICMAN IGS, GREEN
<host2>, 0, 50013, 50014, 3, ABAP GATEWAY ICMAN IGS, GREEN

Case 2

It can also happen that all the available instances are recognized by SUM but none of them is handled as 'central instance'.

For example,

INSTANCELIST_INIT.LOG displays:

1 ETQ399 SYSTEM MANAGER: enhance instance list for Instance Number: 22, Instance Host: <virtualhost2>
1 ETQ399 SYSTEM MANAGER: enhance instance list for Instance Number: 05, Instance Host: <anotherhost4>
1 ETQ399 SYSTEM MANAGER: enhance instance list for Instance Number: 21, Instance Host: <virtualhost1>
1 ETQ399 SYSTEM MANAGER: enhance instance list for Instance Number: 12, Instance Host: <anotherhost5>
1 ETQ399 SYSTEM MANAGER: enhance instance list for Instance Number: 01, Instance Host: <virtualhost3>
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO DIAG_YES.
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO ENQREP.
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO DIAG_YES.
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO DIAG_YES.
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO DIAG_NO.

INSTANCELIST.DAT displays:

<virtualhost2>,22,52213,0,3,ABAP GATEWAY ICMAN IGS,GREEN,,,CI_NO DIAG_YES,STOP BOOTSTRAP,,,NO_INFO,NO_INFO,0,NO_INFO,SINGLE_ABAP
<anotherhost4>,05,50513,0,0.5,ENQREP,GREEN,,,CI_NO ENQREP,START STOP BOOTSTRAP,,,NO_INFO,NO_INFO,0,NO_INFO,
<virtualhost1>,21,52113,0,3,ABAP GATEWAY ICMAN IGS,GREEN,,,CI_NO DIAG_YES,STOP BOOTSTRAP,,,NO_INFO,NO_INFO,0,NO_INFO,SINGLE_ABAP
<anotherhost5>,12,51213,0,3,ABAP GATEWAY ICMAN IGS,GREEN,,,CI_NO DIAG_YES,STOP BOOTSTRAP,,,NO_INFO,NO_INFO,0,NO_INFO,SINGLE_ABAP
<virtualhost3>,01,50113,0,1,MESSAGESERVER ENQUE,GREEN,,,CI_NO DIAG_NO,STOP MANDATORY,,,NO_INFO,NO_INFO,0,NO_INFO,

In SM51 following three ABAP instances appear (instance number may differ):

<virtualhost1>_<SID>_21 <virtualhost1> Dialog Batch Update Upd2 Spool ICM Active
<virtualhost2>_<SID>_22 <virtualhost2> Dialog Batch Update Upd2 Spool ICM Active
<virtualhost3>_<SID>_12 <virtualhost3> Dialog Batch Update Upd2 Spool ICM Active

and they match.

However, SUM recognized the host differently, and uses the physical name instead of virtual one, like (in SAPup_troubleticket.log):

Summary of host system details 

SID:###<SID>
Host:###<physicalhost>
MS Host:##
GW Host:##
Start Path:###
Kernel Path:##

<physicalhost> does not match any of the virtual host names in SM51 or instancelist.

UID GID, nslookup, loopback, /etc/hosts, 127.0.0.2 , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-CST-STS , Startup Service , Problem