Sample Output
You can display cluster
membership information for WildFire appliance cluster node members
(controller and worker nodes) and standalone WildFire appliances
to check whether they belong to a cluster, their application status,
and other local host information. The output differs slightly depending
on the WildFire appliance’s role. The differences are:
The
prompt indicates the active (primary) controller node and the passive
(backup) controller node, but does not indicate a worker node or
standalone role.
The
Node mode
indicates if the
WildFire appliance is a
controller node
,
a
worker node
, or a
stand_alone
WildFire
appliance.
HA priority
displays
primary
for
the active controller node,
secondary
for
the passive (backup) controller node, and the field is blank for
worker nodes and standalone WildFire appliances.
Application status
fields display
different values in some fields. For
global-db-service
and
global-queue-service
,
cluster members display
ReadyLeader
or
JoinedCluster
,
and standalone appliances display
ReadyStandalone
.
For
siggen-db
,
the primary controller node of the WildFire appliance cluster displays
ReadyMaster
,
the secondary controller node of the WildFire appliance cluster
displays
ReadySlave
, WildFire appliance
cluster work nodes display
Ready
, and
standalone WildFire appliances display
ReadyMaster
.
The
last four digits of each WildFire appliance serial number is changed
to “xxxx” in the displays to avoid revealing real serial numbers.
Output
on the primary controller node in a WildFire appliance cluster:
admin@thing1(active-controller)>
show cluster membership
Service Summary: wfpc signature
Cluster name: satriani1
Address: 10.10.10.14
Host name: thing1
Node name: wfpc-00970100xxxx-internal
Serial number: 00970100xxxx
Node mode: controller
Server role: True
HA priority: primary
Last changed: Wed, 15 Feb 2017 09:12:01 -0800
Services: wfcore signature wfpc infra
Monitor status:
Serf Health Status: passing
Agent alive and reachable
Application status:
wildfire-apps-service: Ready
global-db-service: JoinedCluster
global-queue-service: JoinedCluster
siggen-db: ReadyMaster
Output on the
controller backup node in a WildFire appliance cluster:
admin@thing2(passive-controller)>
show cluster membership
Service Summary: wfpc signature
Cluster name: satriani1
Address: 10.10.10.112
Host name: thing2
Node name: wfpc-00970700xxxx-internal
Serial number: 009707000xxxx
Node mode: controller
Server role: True
HA priority: secondary
Last changed: Wed, 15 Feb 2017 09:13:10 -0800
Services: wfcore signature wfpc infra
Monitor status:
Serf Health Status: passing
Agent alive and reachable
Application status:
wildfire-apps-service: Ready
global-db-service: ReadyLeader
global-queue-service: ReadyLeader
siggen-db: ReadySlave
Output on a
worker node in a WildFire appliance cluster:
admin@grinch>
show cluster membership
Service Summary: wfpc
Cluster name: satriani1
Address: 10.10.10.19
Host name: grinch
Node name: wfpc-00970100xxxx-internal
Serial number: 00970100xxxx
Node mode: worker
Server role: True
HA priority:
Last changed: Thu, 09 Feb 2017 15:55:55 -0800
Services: wfcore wfpc infra
Monitor status:
Serf Health Status: passing
Agent alive and reachable
Application status:
wildfire-apps-service: Ready
global-db-service: JoinedCluster
global-queue-service: JoinedCluster
siggen-db: Ready
Output on a standalone
WildFire appliance (not a WildFire appliance cluster member):
admin@max>
show cluster membership
Service Summary: wfpc signature
Cluster name:
Address: 10.10.10.90
Host name: max
Node name: wfpc-00970700xxxx-internal
Serial number: 00970700xxxx
Node mode: stand_alone
Server role: True
HA priority:
Last changed: Mon, 13 Feb 2017 02:54:52 -0800
Services: wfcore signature wfpc infra
Monitor status:
Serf Health Status: passing
Agent alive and reachable
Application status:
wildfire-apps-service: Ready
global-db-service: ReadyStandalone
global-queue-service: ReadyStandalone
siggen-db: ReadyMaster
