Configurations
TheA S1typical StorONE (S1) system consists of a highly available (HA) 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 the configurations that werehave setbeen attempted and completed on your server,system, use the configurations list command. The list is ordered by configuration starting time, with the most recent configuration isat the lastend configuration onof 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,configurations, runconfigurations 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 usersusers, and one of the users configures the S1 system, thenthe configuration won'tdoes not immediately appear in the other session. To makesynchronize all sessions synchronized with the S1 configurations,sessions, run:
configurations session async_completion