The following table explains the information that is displayed in the Partner Fileshare Table:
Title | Description |
---|---|
Node | The order of the nodes as listed in the ES_HA_VSAM environment variable. The current node is always displayed first, and then the other group nodes, in order. |
Name | The name of the node. |
Connection Status | Connection status in relation to the group; this is either acquired (in the group) or released (not in the group). |
Role | The role that the current node is assigned within the group. This can be one of primary, standby, or disabled. |
Host | The host-name of the machine on which the node is located. For example, this can be an IP address, localhost, or a server name, depending on how the ES_HA_VSAM environment variable is configured. |
Port | The ISC-port of the current node. This is the port on which to host the dynamically generated ISC listener for node. |
DBREF | An indicator to signify that the dbase.ref file on the current node is fully synchronized with the version on the primary server. |
Checked | An indicator to signify that the ES_HA_VSAM environment variable is consistent with the version on the primary server. |
Prim_ok | An indicator to signify that the node is connected to the primary server. |
ISCTrace | An indicator to signify if ISC tracing is enabled. ISC tracing is enabled using option T when setting the ES_HA_VSAM environment variable. |
Rep Seq | The latest sequence number assigned to a replication request. This is one of the metrics used to determine the next suitable candidate for primary server in the event of a failover. |
Upd Count | Internal metrics. |
Start Seq | Internal metrics. |
Response Time | The average time (in ms) that a node took to respond to a commit acknowledgment request. Another metric used to determine the next suitable candidate for primary server in the event of a failover. |
Takeover | An indicator to signify the eligibility of the current node to become the primary server in the event of a failover. |