Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Dealing with an inhomogeneous Management Cluster - Notes

&pagelevel(3)&pagelevel

Inhomogeneous Management Cluster means that a Management Cluster consists of servers with different software versions, of an SE server with all units (MU, HNC, SU x86) with one version – usually the current one – and another SE server with all units (MU, HNC, SU x86) with another version – an older one. 
This situation can occur, for example, if the servers of a Management Cluster are not upgraded at the same time but in steps. 

With V6.6, Management Clusters consisting of SE servers with versions V6.6/V6.5 and with V6.6/V6.4 are supported.

This chapter deals with some specific topics and limitations that must be considered in an inhomogeneous Management Cluster during normal operation - separately for the two steps from V6.5 to V6.6 and from V6.4 to V6.5.

General

Generally, the user is advised to do as follows:

  • Login on and use a V6.6 MU for administrating V6.6 units.
  • Login on and use a V6.5 MU for administrating V6.5 units.
  • Login on and use a V6.4 MU for administrating V6.4 units. 

V6.6/V6.5

BS2000 support

  • SERVICE-PACK and SYSID
    • SERVICE-PACK and SYSID of BS2000 systems are displayed as of SEM V6.6.
  • Modified IORSF file

    • The warnings regarding the modification of the active IORSF file are displayed only in SEM V6.6.
  • EMDISC files (SU x86, MU)
    • In SEM V6.6, the SEM window "EMDISC files" will be displayed also for V6.5 units, but the tables will remain empty.
    • If called for those units, the dialog "Update EMDISC filesystems" will fail.
  • BS2000 disks
    • As of V6.6, it is possible in SEM to create BS2000 disks based on EMDISC files on MU, which can be used by SU /390.
  • Restart all tape devices

    • In SEM V6.6, the window "Tape devices" will contain the dialog "Restart all tape devices" also for V6.5 SU x86.
    • If called for those units, the dialog will fail.

Roles and accounts 

  • The new roles Remote service administrator and Shell access are not supported in V6.5.

SEM display

  • SEM in main window <Unit x86> -> System -> Overview: 
    Boot times (system start) for units with the respective other version are not displayed.

V6.5/V6.4

Roles and accounts 

The role concept in V6.5 is not compatible with that in V6.4.

Therefore the following applies:

  • V6.4 accounts should only be used on V6.4 MUs, V6.5 accounts only on V6.5 MUs.
  • The service will advise you and help you find the right approach when moving to V6.5, so that you can use the acounts you want in the homogeneous V6.5 end state.

SE operation state

The SE operation state (including the maintenance state) can be edited only in V6.5 and it is not visible in V6.4.
The server information (predecessor of the SE operation state) can be edited only in V6.4 and it is not visible in V6.5.

New menu structure and the main windows

In V6.5 the structure of the Units and Service menus has been changed:

The submenus Hardware -> <MU|HNC|SUx86> -> Service (Update | CSR | Diagnostics | Remote Service) have been moved from the Hardware menu to the Service menu. 

When changing the MU in SEM (e.g. using the links in the header) from a MU with V6.5 to one with V6.4, with one of the above main windows open in SEM, this is not found and the browser displays "Not Found / The requested URL ... was not found on this server.".
With an analogous change from a MU with V6.4 to one with V6.5, the Service menu is changed correctly, whereas all calls of the FC menu are redirected to the Overview window.

Hardware properties

Call the "Hardware details for unit" dialog for a unit from a MU of the same server, otherwise it will fail.
Call the "Change scheduled power on/off" dailog for a unit from a MU of the same server, otherwise it will fail.

Add-ons

Version dependency
With V6.5 the add-ons had to adapt to this new version.
Please refer to the respective add-on-specific documentation for the recommended versions and recommended procedures.
This applies in particular to STORMAN, as from STORMAN 10.3 and M2000 V6.5 the STORMAN graphical interface is fully integrated into SEM.