GitHubContribute in GitHub: Open doc issue|Edit online

From Output bridge to Postconfirmation queue

In this state, the HiperSockets states and components that are created on the LPARs are listed in the following table.

Components CREATED on LPAR_1 LPAR_1 and LPAR_2 HiperSockets state Components CREATED on LPAR_2 LPAR_2 and LPAR_3 HiperSockets state Components CREATED on LPAR_3
  • (Conditional) Frontend
  • (Conditional) Frontend plug-in
  • Preconfirmation queue
  • Postconfirmation queue
  • Admin controller
  • UI Server
CONNECTED
  • Conductor
  • Output bridge
DISCONNECTED N/A

Note: In the figures, the blocks that are filled with a blurred pattern are in a DESTROYED state, where the virtual machine instance does not exist on the LPAR.

State Output to Post

Then, the Output bridge PUSH data into the Postconfirmation queue.

State Output to Post

Which is a signal to destroy the output bridge.

State Output to Post