PI93298: PORT CONFLICT AFTER MIGRATING FROM V7 TO V855X ON THE SAME SERVER INTO THE SAME DIRECTORY

9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• Migration process seems to have changed ports 11007 and 11008
  into 11005  and 11006 on the new Dmgr for
  OVERLAY_UDP_LISTENER_ADDRESS and  OVERLAY_TCP_LISTENER_ADDRESS
  respectively
  
  Here are the pre and post upgrade commands:
  
  Save the old deployment manager profile configuration using
  the preUpgrade command:
  
  /tmp/bin/WASPreUpgrade.sh
  /staging/websphere_migration/training4/v7tov85dmgr
  /usr/IBM/WebSphere/AppServer -oldProfile Dmgr01 -machineChange
  true
  
  Save the old AppSrv configuration for the upgrade:
  
  /tmp/bin/WASPreUpgrade.sh
  /staging/websphere_migration/training4/v7tov85AppSrv1
  /usr/IBM/WebSphere/AppServer -oldProfile AppSrv01
  -machineChange true
  
  Restore 7.0 Dmgr profile to 8.5:
  
  /usr/IBM/WebSphere/AppServer/bin/WASPostUpgrade.sh
  /staging/websphere_migration/training4/v7tov85dmgr
  -profileName Dmgr01 -oldProfile Dmgr01 -replacePorts TRUE
  -backupConfig  FALSE -includeApps SCRIPT -scriptCompatibility
  TRUE -keepDmgrEnabled  TRUE -username xxxx -password xxxx
  
  Run the WASPostUpgrade command against the AppSrv profile:
  
  /usr/IBM/WebSphere/AppServer/bin/WASPostUpgrade.sh
  /staging/websphere_migration/training4/v7tov85AppSrv1
  -profileName AppSrv01 -oldProfile AppSrv01 -replacePorts TRUE
  -backupConfig
  FALSE -scriptCompatibility TRUE -username xxxx -password xxxx
  

Local fix

• Change the port after migration process
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Migration Scripts                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Cell migration results in port          *
  *                      conflicts for new Endpoints.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The ports of any new endpoints introduced since the release
  from which the migration occurs are defaulted to the ports
  found in the template and are not being check to see if they
  are already in use.
  

Problem conclusion

• The ports of any new endpoints are checked against the
  current set of ports being used by the cell.  If a conflict is
  detected the port is adjusted accordingly.  The fix for this
  APAR is currently targeted for inclusion in
  fix pack 8.5.5.14 and 9.0.0.8.  Please refer to the
  Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP