Search Results

This chapter covers the customer-configurable system and session settings: how capacity numbers are displayed, how CLI output is formatted, and where to find the anomaly detection settings. Capacity display units Every capacity value StorONE displays — drive s...

StorONE supports non-disruptive updates (NDU) — installing a new software version on a node without taking your storage offline. The customer-facing update flow has two steps: upload the update package to the node you want to update, then install it. Each node...

A system is a StorONE-managed cluster — a single controller or an HA controller pair, along with everything it manages (applications, volumes, pools, and so on). A single CLI or web session can be connected to more than one system at once: one system is always...

When you replicate NAS or object volumes to a remote StorONE system, clients need a stable address to reach whichever side is currently primary. Pairing a local floating IP with a remote one is how you set that up: the two floating IPs are linked, and only one...

A floating IP is a virtual IP address that isn't permanently tied to one node — StorONE moves it between nodes as needed, so clients keep using the same address regardless of which physical node is actually serving it. This is what lets a client connection sur...

On a high-availability (HA) pair, both nodes are normally active, each owning a share of the system's volumes. These commands change that ownership — moving every volume onto one node (takeover), restoring the normal split afterward (giveback) — and let you re...

A StorONE cluster is made up of one or more physical (or virtual) nodes — the servers that run the StorONE software and serve I/O to your hosts. This chapter covers the node-level administration and network settings that are available to you as a customer; mos...

This page covers two unrelated but customer-facing groups of node commands: giving StorONE support secure remote access when you need help, and the iSCSI-related network settings (CHAP authentication and iSNS discovery) that apply to your nodes' iSCSI targets....

The three basic permission roles ( Read, ReadWrite, Admin) are all-or-nothing across the whole system. A permission policy lets you build something more targeted — for example, a user who can create and edit volumes but never delete them, or a user who can o...

StorONE user accounts control who can log in to the system — through the web interface, the CLI, or the REST API — and what they're allowed to do once they're in. Every account is either a local user (username and password stored in S1 itself) or an LDAP user ...

StorONE S1 Platform 4.0 VERSION 4.0 · GENERALLY AVAILABLE S1 Platform 4.0 is officially GA. This release adds file-level snapshot insight, Auto-Tiering v3, striped object stores, directory-based authentication with granular permissions, and a redesigned GUI wi...

The StorONE REST API lets you do over HTTPS what you do in the web interface and the CLI: provision storage, manage snapshots and replication, read monitoring data, configure notifications, and so on. It's the right tool when another system needs to drive Stor...