Using the SC//Reliant Local Status Indicator (RLSI)
The SC//Reliant™ Local Status Indicator (RLSI) is a web console that runs on each node in your SC//Reliant platform environment. It reports the node's current status and offers a small set of local actions — restarting a virtual machine, taking a backup, running a network diagnostic — without needing the SC//Reliant Platform Manager or a remote session.
Each node serves its own console, so everything RLSI shows you describes the node you connected to and nothing else. To check the other node at a site, open RLSI on that node.
Reaching the console
RLSI is served by the node on your own network rather than published to the internet, so all you need is a computer that can route to the node, and the node's hostname or IP address. You can find both in the SC//Reliant Platform Manager at https://platform.reliant.io/. Node hostnames follow the pattern sit0001red0, where 0001 is the site number.
You do not need shell access to the node, and you do not need to open an SSH session first.
-
In a browser, navigate to the node over HTTPS.
https://<node_hostname_or_ip_address>For example,
https://sit0001red0orhttps://172.20.40.161. Use the IP address if the hostname does not resolve on your network. -
Accept the certificate warning. RLSI presents a certificate issued per customer rather than by a public authority, so browsers do not trust it. The warning is expected.
-
If the tab you need is password protected, log in. See Logging in.
RLSI listens on port 443. If a node has been configured to serve on a different port, append it: https://<node_hostname_or_ip_address>:<port>. See Setting the listen port.
Logging in
Which tabs appear, and which require a login, depends on how RLSI is configured for the node. Some tabs open without one.
The login page displays a sequence number. That number identifies which password to use, from the credential database configured for your company. The number changes each time a login page is loaded, so read it and enter the matching password in one pass.
The session expires after 30 minutes of inactivity, after which you log in again.
For more information, see Credentials for password-protected tabs.
The header bar
The bar across the top of every tab tells you where you are and what state the node is in.
| Item | What it tells you |
|---|---|
STORE NUMBER | Which store you are connected to. |
Primary or Secondary | The node's role in its cluster. The store's virtual machines run on the primary. |
Last checked at | When RLSI last refreshed the cluster status, in UTC. A timestamp that stops advancing means the status is stale. |
Selecting the role indicator expands the cluster status for the node.
Before you act
Every action in RLSI applies to the node you are connected to. Before using anything on the VMS, BACKUPS, or ADMIN tabs, confirm three things.
-
You are on the right node. Check the store number and role in the header bar. The
Hostnamerow on the STATUS tab identifies the individual node, which matters if you have more than one console open. -
The cluster is in a state where it is safe to act. Expand the role indicator and read the three fields. For a healthy cluster, all three answers are No.
Field Healthy What "Yes" means Is this cluster in Maintenance Mode? No Planned work is in progress. Leave the node alone unless you are part of it. Is this node in Stand by? No The node was taken out of service, so its VMs are running on the other node. Is this cluster Unclean? No A hard stop. Escalate, and do not attempt any action. -
The action is the scope you intend. Reboot on the ADMIN tab restarts the whole node; the VMS tab restarts a single virtual machine.
These three fields tell you whether it is safe to act, not whether the cluster is fully healthy. For quorum, fencing, and replication state, none of which RLSI reports, see Verifying cluster health.
The tabs
Which tabs a node shows depends on how RLSI is configured for it, so the set is not the same everywhere. See Configuring RLSI.
| Tab | What it is for | Read more |
|---|---|---|
| STATUS | The home page. Reports checks describing the node's connectivity, addresses, and disk usage. Read-only, and cannot be hidden. | Reading the Status tab in RLSI |
| VMS | Lists the node's virtual machines and their power controls. | Managing virtual machines in RLSI |
| BACKUPS | Backs up and restores virtual machines. | Managing virtual machines in RLSI |
| LOGS | Shows logs from the node. | — |
| ADMIN | Node-level maintenance and diagnostics, including rebooting the node. | Using the Admin tab in RLSI |
The VMS and BACKUPS tabs cannot be password protected, so where they are enabled they are open to anyone who can reach the console. See Configuring RLSI.
In this section
- Configuring RLSI: the properties that install RLSI and control which tabs and checks appear.
- Reading the Status tab in RLSI: the checks, what each reports, and how to read the indicators.
- Managing virtual machines in RLSI: viewing, rebooting, backing up, and restoring virtual machines.
- Using the Admin tab in RLSI: rebooting the node, running Puppet, and the network diagnostics.
- Troubleshooting RLSI issues: what to do when the console will not load or an action does not behave as expected.
Related documentation
- SC//Reliant Local Status Indicator (RLSI): where RLSI fits in the platform.
- Choosing between Platform Manager, REdge, and RLSI: which interface to use for a given task.
- Verifying cluster health: the cluster checks RLSI does not cover.