IY97983: AGENT FAILS TO CONNECT TO HUB WITH UNDOCUMENTED ERROR CODE 78

APAR status

• Closed as program error.

Error description

• ENVIRONMENT:
  ITM 6.1 + FP02 on all component
  New Firewall gatewy Proxy feauture implemented.
  .
  PROBLEM DCESCRIPTION:
  Customer has following configuration:
  1) 10.12.xx.yy: A windows machine running a hubtems and
  warehouse proxy.
  2) 10.12.nn.mm (host1): An AIX 5.3 machine running a UNIX OS
  agent with the firewall gateway feature configured as a relay
  connect /client proxy
  3) 192.168.xx.zzz (host2): An AIX 5.3 machine running a UNIX
  OS agent with the firewall gateway feature configured as a relay
  listen / server proxy
  
  
  The machines 10.12.xx.yy and 10.12.nn.mm are in the same network
  zone.
  The machine 192.168.xx.zzz is in the DMZ.
  .
  The agent in DMZ fails to connect to HUB and logs show:
  2) The logs from hostname1 in the DMZ shows:
  ----------------- 41408.211.788-hostname1.log
  ------------------- ....
  
  44C0E9D8.0000-4:kdebgrc.c,44,"KDEBG_RelayConnect") Interface
  uprelay.dmz.poraai01 connection active: 10.12.nn.mm:10021
  (44C0EA20.0000-5:kdebbcn.c,35,"KDEB_BaseConnect") connect
  failed, errno
  78
  ....
  ----------------------------------------------------------------
  .
  Problem was solved by:
  1) reconfigured the UNIX OS agent on the DMZ (hostname2 -
  192.168.xx.zzz ) with the location of the TEMS as being
  127.0.0.1 instead of 10.12.xx.yy.
  2) The agent is using the tunnel to connect to the HTEMS.
  .
  The error code 78 is not documented anywhere and should be
  
  
  DETAILE RECREATION PROCEDURE:
  NA
  
  RELATED FILES AND OUTPUT:
  available on request
  
  APPROVER:
  NA
  

Local fix

• 1) reconfigured the UNIX OS agent on the DMZ (poraai01 -
  192.168.0.213) with the location of the TEMS as being 127.0.0.1
  instead of 10.12.69.90.
  2) The agent is using the tunnel to connect to the HTEMS.
  

Problem summary

• Agent fails to connect to the HUB with an
  undocumented ERROR CODE 78; message in RAS1 log is:
  "connect failed, errno 78".  This error code is not
  documented.
  

Problem conclusion

• Code changed to provide platform-specific ERRNOs for
  error conditions detected and reported in the RAS1
  log. Message "connect failed, errno 78" is now
  "Status 1DE00045=KDE1_STC_CONNECTIONFAILURE=10061:
  No connection could be made because the target
  machine actively refused it." The fix for this APAR is
  included in the following maintenance vehicle(s):
  fix pack 6.1.0-TIV-ITM-FP0005.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IY89183

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TEMA

• Fixed component ID

  5724C04TE

Applicable component levels

• R610 PSY

     UP