Arbitrated services

The following table lists the states that are published only for arbitrated services.

The same message is published with the specific computer name (for example, "ls1pdcrt1"), as well as the computer definition within the service (primary or secondary). This enables you to subscribe to either the specific computer name, or alternatively, to the definition you desire. The options abstract your subscription to deal with any computer that may be configured as this member of the service pair.

• Primary computer: <system>.<service>.arb.primary.states.<stateType>

• Secondary computer: <system>.<service>.arb.secondary.states.<stateType>

• Computer Name: <system>.<service>.arb.<computer>.< stateType>

  Where <stateType> can be any of the options in the table below:

  State Type	Description
  fresh	The following values are published to indicate if the state reported for the service is current: True False
  hostname	The name of the host for the given service on the computer.
  state	The following values are published to identify the state of the given service on the specified computer: FAIL PENDING INIT STANDBY HOT SWITCH DO_SWITCH
  syncstate	The following values are published to identify the state of the given service on the specified computer: STALE SYNCHRONIZING SYNCHRONIZED
  flag.packqual	The quality information associated with this service and computer. This can be used to identify which color should be used in displaying the current state, as shown in the states.state topic.
  lastMsgContainedTimestamp	The time inside of the last state update message. This is a timestring in the following format: mm/dd/yyyy/ hh:mm:ss
  lastMsgReceivedTimestamp	The time of the last state update received. This is a timestring in the following format: mm/dd/yyyy/ hh:mm:ss