Controller status
HPE VAN SDN Controller groups components into categories and those component groups are initialized in order as the startup sequencer moves through the stages in the startup sequence. During the operational phase, the OpenFlow port is opened. Core services are the first to be initialized and they are always active. System Information Service is part of the core services and thus the controller status cannot be determined or reported until the core services complete the initialization phase.
For more information, see Error log for team configuration , Team alias node, Failover behavior within a region, Failback behavior within a region.
The controller states are:
initializingThe sequencer completed the startup sequence through the team stage and the controller is part of the team quorum (connected to at least one other active controller in the team), but has not yet deployed and initialized the operational group services. At this point, the OpenFlow port is not open.
activeThe sequencer completed all stages of the startup sequence and the OpenFlow port is open. If the controller is a member of a team, it is part of the team quorum (connected to at least one other team member that has started its teaming services).
suspendedThe sequencer completed all stages in the suspend sequence. The sequencer initiates the suspend sequence when a monitored core service reports an unhealthy status or a teamed controller loses its membership in the team quorum. Core services are started. Teaming services are started but are waiting until the controller can become a member of a team quorum. The OpenFlow port is closed.
unreachableA controller sees a remote controller as
unreachableif the connection to the remote controller is broken. A controller never sees itself asunreachable.
If an application reports an unhealthy status,
an alert is generated but the controller remains in the active state.
If two controllers in a team fail, the third controller does not operate as a standalone controller. Instead, the third controller loses its membership in the team quorum, and the sequencer initiates the suspend sequence.
You can view your controller status from the top section of the Team screen in the UI, see Viewing team configuration and controller status.