GitHubContribute in GitHub: Open doc issue|Edit online

From Preconfirmation queue to Input bridge

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
  • Input bridge
 DISCONNECTED N/A

This state is the start of the iteration, where the data is PULLED into the Input bridge. After the Input bridge pulls data, it updates the Conductor, which is the signal to disconnect the VLAN.

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 Pre to Input

This state remains until the Input bridge indicates to the Conductor when its Time-based security elapses, and is ready to proceed to PUSH data into the Backend.

State Pre to Input