Central operation and administration of the SE server is continued after an MU has failed if there is MU redundancy, i.e. if the SE server has a second MU.
Redundancy of the SKP functionality
On an SE server with SU /390, two MUs mean that the SKP functionality is also provided with redundancy. As a result, when one MU fails the SU /390 can still be operated via the SVP.
With respect to the SKP functionality, one MU is always "active" and the other is "passive". Only the active MU can access the SVP of the SU /390. SVP accesses of the passive MU take place by means of automatic redirection via the active MU.
On the SVP console tab of the SU /390 you see the current status of the MUs with respect to the SKP functionality. There you can also switch over the passive MU, i.e. the two MUs change status (see Systems -> [<se server>(SE<model>) ->] <unit> (SU</390>), "Switching active Management Unit").
The SE Manager displays the current status of the SVP network and of the MU connections in the IP configuration of the SU /390 (see Hardware -> Units -> [<se server> (SE<model>) ->] <unit> (SU</390>) -> Management, "Managing the IP configuration").
Operating redundant MUs
When two MUs are available, in other words MU redundancy exists, you can log into the SE Manager on either of the two MUs. Operation and administration of the SE server is possible without restriction on either of the two MUs.
In the title bar, the SE Manager displays the existing MUs and permits a "change" to the SE Manager of the other MU via a link. You do not need to log in again, because, in the default case, a session on the SE Manager is global. For this, the following requirements must be met:
The MUs are registered at an external DNS domain.
The connection to the SE Manager was made via the DNS name of the MU (entering the DNS name of the MU as address in the browser).
The MU on whose SE Manager the user is currently logged in is the local MU in this session, and the redundant MU is the remote MU.