"The SE code is running as a guest of the HMC. The two SE code instances are clustered for high availability. One SE code runs the Primary SE the other Alternative SE. These SEs perform data mirroring and their role can be switched for maintenance purposes."
"Switching the Primary and Alternative SE roles is important because HMC microcode maintenance can be performed only on the server that runs the Alternative SE as a guest." Page 411 https://mail.google.com/mail/u/0/#inbox/WhctKKXpSbvmbcppNmHrLvBqKDqnsVDKbdgLnvvjbLHRsMVSDDpXqJSQzgCJgwfrGMGnqGv joe On Sat, Jan 14, 2023 at 4:24 PM Radoslaw Skorupka < [email protected]> wrote: > As it is documented, z16 supports virtual HMC appliance only. In other > words, no more standalone PC working as HMC > So, inside z16 cabinet there are two pizza box PC servers, both hosting > SE and HMC. > So, SE and HMC run virtualized on same hardware. > Q: what is the setup of virtual machines? > I can imagine the following: > a) SE runs on bare metal and hosts HMC virtual machine. > b) HMC runs on bare metal and hosts SE virtual machine. > c) Both SE and HMC run as virtual machines, under some other hypervisor. > > I heard the option b) is in effect, but it doesn't seem optimal > solution, because HMC restart implies SE temporary unavailability as well. > > Any clue? > > -- > Radoslaw Skorupka > Lodz, Poland > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
