show gateway-peering-status
This command shows the gateway peering status.
Syntax
show gateway-peering-status
Guidelines
The show gateway-peering-status command shows the list of gateway peering configuration, for each gateway peering configuration. The command shows the following information.
- The IP address that identifies a peer member.
- The configuration name of the gateway peering engine.
- Number of outstanding commands on this member.
- The replication offset of a member. The offset of a member matches the offset of the primary when they share the same data replication. Data is replicated asynchronously as a constant stream of updates, so small deltas are expected between each of the members in the peer group.
- Healthiness of the network connection from this member to the primary.
- Whether this member is primary in this peer group.
To view status information about peer-based gateway peering members, use the show gateway-peering-cluster-status command.
The following output show 3 healthy peer group
members.
Address Configuration name Pending updates Replication offset Link status Primary
------------- ------------------ --------------- ------------------ ----------- -------
172.16.52.71 gwd 0 5172227903 ok no
172.16.52.71 tms 0 530258237 ok no
172.16.53.39 gwd 0 5172229359 ok yes
172.16.53.39 tms 0 530258384 ok yes
172.16.54.108 gwd 0 5172228339 ok no
172.16.54.108 tms 0 530258237 ok no
The following output show 2 peer groups each with too many unhealthy members for a valid quorum.
For a valid quorum, the following requirements apply.
- The primary peer must be up.
- At least (n/2)+1 members must be active.
Address Configuration name Pending updates Replication offset Link status Primary
------------- ------------------ --------------- ------------------ ----------- -------
172.16.52.28 gwd 2 100 down no
172.16.52.28 tms 2 100 down no
172.16.52.71 gwd 0 5153656987 ok no
172.16.52.71 tms 0 528269932 ok no
172.16.53.39 gwd 0 5153658295 ok yes
172.16.53.39 tms 0 528270079 ok yes
172.16.54.4 gwd 0 5153656987 ok no
172.16.54.4 tms 0 528269932 ok no
172.16.54.108 gwd 100 13 down no
172.16.54.108 tms 15 13 down no
172.16.54.121 gwd 9 13 down no
172.16.54.121 tms 102 13 down no
Example
Validate the health
of gateway peering members to verify that the primary peer is still
up and that there are at least (n/2)+1 members still active. Both
of these conditions are required to ensure that the cluster maintains
the quorum.
# show gateway-peering
The
following output indicates stale members and a lost quorum.
Address Configuration name Pending updates Replication offset Link status Primary
------------- ------------------ --------------- ------------------ ----------- -------
172.16.52.28 gwd 2 100 down no
172.16.52.28 tms 2 100 down no
172.16.52.71 gwd 0 5153656987 ok no
172.16.52.71 tms 0 528269932 ok no
172.16.53.39 gwd 0 5153658295 ok yes
172.16.53.39 tms 0 528270079 ok yes
172.16.54.4 gwd 0 5153656987 ok no
172.16.54.4 tms 0 528269932 ok no
172.16.54.108 gwd 100 13 down no
172.16.54.108 tms 15 13 down no
172.16.54.121 gwd 9 13 down no
172.16.54.121 tms 102 13 down no
Recover from this situation by removing stale members.
# gateway-peering-remove-stale-peers gwd
# gateway-peering-remove-stale-peers tms
Verify
the removal.
# show gateway-peering
The
following output indicates removal, which indicates a valid quorum.
Address Configuration name Pending updates Replication offset Link status Primary
------------- ------------------ --------------- ------------------ ----------- -------
172.16.52.71 gwd 0 5153656987 ok no
172.16.52.71 tms 0 528269932 ok no
172.16.53.39 gwd 0 5153658295 ok yes
172.16.53.39 tms 0 528270079 ok yes
172.16.54.4 gwd 0 5153656987 ok no
172.16.54.4 tms 0 528269932 ok no