An inhomogeneous Management Cluster is a Management Cluster consisting of servers with different SW versions, e.g. of an SE server with all units (MU, HNC, SU x86) with version V6.4 and another SE server with all units (MU, HNC, SU x86) with version V6.3. This situation can occur if the servers of a Management Cluster are not upgraded at the same time but in steps.
In general, it can be said that in such a situation functions should be used only within the same server resp. version, even if in SEM there seem to be no differences.
This chapter deals with specific topics and limitations that must be considered in an inhomogeneous management cluster.
Server information
The server information can be edited only in V6.4 and it is not visible in V6.3.
Certificates
In V6.4 the certificate functionality has been enhanced with the support of the customer's CA certificate and allowing the non-administrators to access it.
Due to the necessary changes, the user is strongly advised to administrate the certificates from V6.4 MUs using SEM from V6.4 MUs and the certificates from V6.3 MUs using SEM from V6.3 MUs. This means not only the SEM dialog boxes but also the main windows.
Terminal functions – notes and restrictions
- With V6.4, a new terminal called SEMVT (SEM virtual terminal) with extended functionality has replaced the Shellinabox-based terminal.
- The commands supported by administrator accounts have been extended in the new version.
Note:
- The terminal you get depends on the MU on which you call SEM.
- The supported commands (cli_info output) you get depends on the MU that you address with SEM.
New menu structure and the main windows
In V6.4 the structure of the following systems and devices menus has been changed:
- Systems -> <SU>
- Systems -> <SU> -> <VM>
- Systems -> <AU>
- Systems -> <AU> -> <VM>
- Devices -> <SU>
If one changes the MU (e.g. via the header functionality) from a V6.4 to a V6.3 MU (or vice versa) with one of these windows open, the corresponding window will not be found and "Not Found / The requested URL … was not found on this server." will be displayed by the browser.
IP-based access rights
In V6.4 the IP-based access rights functionality has been enhanced with new functions.
The behavior in an inhomogeneous Management Cluster is as follows:
- All functions available in V6.3 - Allow IP address, Remove IP address, Change description - work correctly across all servers.
- When called for V6.3, the new functions in V6.4 - Set configuration status and Remove all IP addresses - will be apparently successful, but will have no effect at all.
- Display of the status:
In V6.3 the status of the V6.4 configuration is not visible.
In V6.4 the status of the V6.3 configuration can apparently be set to Inactive, but in fact it is always Active.
Remote service - Delete AIS Connect proxy configuration
Due to internal changes, the user is strongly advised to use a V6.3 MU for deleting the AIS Connect proxy configuration on a V6.3 MU and use a V6.4 MU for this action regarding a V6.4 MU!
Add-ons
- Status INITIALIZING
As of V6.4 the value INITIALIZING is supported for the status of add-ons.
If set, it will not be properly displayed in V6.3. - Version dependency
With V6.4 the add-ons had to adapt to this new version.
Please take the recommended versions that support both V6.4 and V6.3 from the documentation for the specific add-ons.
Add-on administrator roles
At creation of an add-on administrator account in V6.4, the general behavior will be misleading, irritating and error-prone.
As conclusion, the following restriction results:
- The customer is strongly advised not to use add-on administrator accounts in an inhomogeneous management cluster.
- The add-on administrator accounts shall not be introduced until a homogeneous management cluster has been established.
Configuration and usage of LDAP
The user is strongly advised to
- use a V6.3 MU for administrating the LDAP configuration on a V6.3 server and to
- use a V6.4 MU for administrating the LDAP configuration on a V6.4 server!
AIS notification and remote service access
- In V6.3, this functionality is MU-local and it doesn’t affect at all any other MUs.
- In V6.4, events with component RemSrv are created, and are forwarded also to V6.3 MUs, where they become visible.
One cannot register in V6.3 for alarm mails regarding RemSrv, because this component is unknown there. - The V6.3 and V6.4 functionalities are completely independent from each other.
There are no restrictions whatsoever that must be observed in the regard of this functionality, neither in V6.3, nor in V6.4.