Configurations
The S1 system consists of a two-node cluster. The nodes are servers with high availability (HA) connection. S1 is a complete operating system that manages the node servers and their peripherals. Each node has its own internal storage where the S1 operating system resides.
Both nodes connect to an external disk enclosure where the physical storage can be found. Nodes are responsible for managing and running the disk enclosure. Users who interact with the S1 system may either use the CLI or the GUI. Using the configuration command, you can view server configuration, list connection status, and perform server synchronization.
View server configuration
To list configurations that were set on your server, use the configurations list command. The list is ordered by configuration starting time, the most recent configuration is the last configuration on the list.
Usage:
configurations list [--inProgress | --success | --failure] [--top=<n>] [--descendingOrder]
Options:
| Options and arguments | Description |
|---|---|
--pending |
To list only the pending configurations. |
--inProgress |
To list only the in-progress configurations. |
--success |
To list only the successful configurations. |
--failure |
To list only the failed server configurations. |
--top=<n> |
To list only the first <n> configurations display, replace <n> by the number of lines to display. |
--descendingOrder |
To sort the configurations list by descending order, most recent configurations appear first. |
Examples:
- To output the last 3 successful server configurations, run
configurations list --top 3 --success --descendingOrder - To output all servers activities, run
configurations list - To output all failed server configurations in descending order (most recent configurations listed
first), run
configurations list --failure --descendingOrder
Synchronizing all sessions with S1 configuration
If the S1 system is accessed simultaneously by multiple S1 CLI users and of the users configures the S1 system, then configuration won't appear in the other session. To make all sessions synchronized with the S1 configurations, run:
configurations session async_completion