The following example demonstrates using unityadmin to verify a successful Unity installation.
Viewing Status Information
Run STATUS to view system details.
unityadmin> status; Sequencer: region1_seq-fastcop1(active), Repository: prod1(active) Sequencer: region2_seq-bltorcop1(standby-synchronized), Repository: prod2(standby - synced) Endpoint region1_ept: 10.25.1.4(not listening):1025, 22.214.171.124(listening):1025, 10.25.1.9(not listening):1025, 126.96.36.199(not listening):1025 Endpoint region2_ept: any(listening):1025 System prod1(unrecoverable) Tables: OOS 0, standby 0, unrecoverable 0, interrupted 0, restore 0, read-only 0, active 0 Dispatcher status: region2_dsp_prod1(standby) - down, region1_dsp_prod1(active) – up Gateway status: flash - prod1cop1(up) System blaze(active) Tables: OOS 0, standby 0, unrecoverable 0, interrupted 0, restore 0, read-only 0, active 0 Dispatcher status: region2_dsp_prod2(active) - up, region1_dsp_prod2(standby) – up Gateway status: prod2 - prod2cop1(up) Alerts: 0 critical, 1 warning, 1 normal
This table explains the output.
||When Unity is functioning properly, one Sequencer (region1_seq-fastcop1) and its Repository (flash) should be in the Active state. The second Sequencer (region2_seq-bltorcop1) and its Repository (blaze) should be in the standby state (the sub-state can be synchronizing, syncing, synced or synchronized). For more information, see SEQUENCER STATUS or REPOSITORY INFO.|
||All Endpoints (region1_ept, region2_ept) should be connected. Each IP address should be in the proper listening/not listening state (10.25.1.4(not listening)). Endpoints listen on all default IP addresses, and not listen on standby IP addresses (unless requested to do so specifically by the Sequencer). If an Endpoint is not connected, "not connected" appears instead of a list of associated IP addresses.|
The first list shows the flash system, which is in the unrecoverable state. There are currently no objects in the Unity dictionary, so that count of tables in each state is 0. There are two dispatchers defined. Dispatcher (region2_dsp_flash) is in Standby state, and is not connected to the Sequencer (state: down). Dispatcher (region1_dsp_flash) is the Active dispatcher, and is connected to the Sequencer (state: up).
For detailed information on the system, associated gateways and dispatchers, see the SYSTEM DESCRIBE command.
There should be no critical alerts, but warning alerts can show up as part of normal system operation and don't need to be cleared. Normal alerts can appear during system startup.
To see all open alerts in a system, use the ALERT LIST OPEN command.