Accessing the UI

To connect to the legacy Admin Console, enter one of the following URLs in a browser's address or location field:

CSN Platform Server

No Platform Server

For example, if the Swarm node IP address is 10.20.30.101, enter:

Navigating the UI

The legacy Admin Console displays two separate views of the cluster: cluster-level and node-level status.

Cluster Status Page

The Cluster Status page appears when initially logging in to the legacy Admin Console.

Open

The Cluster Status page allow viewing cluster-wide information such as number of nodes, cluster status, number of errors, number of streams (data components that comprise objects), and capacity data. If the cluster is configured with subclusters, you must expand a subcluster node name to display the associated IP addresses and then click an IP address to display node information.

Node Status Page

When clicking an IP address in the Node IP column, the Node Status page appears for the selected node, as shown below.

Open

The Node Status page allows viewing information specific to your cluster node, such as hardware status, health processor status, uptime, and Swarm software version.

See Managing Chassis and Drives.

The Node Status page also includes the following sections:

• Node Info. Provides general information about the hardware installed on the node, as well as time server information and current uptime.

• Node Configuration. Provides the cluster and network configuration settings assigned to the node. Use this status information to verify your system configuration quickly, without using SNMP commands.

• Node Operations. Describes the state of the node. If you encounter a problem in your storage cluster, a Swarm Support representative can use the information in this page to help determine if the node is communicating effectively with other nodes and resources in the cluster.

• Hardware Status. Provides status and operational reporting (if available) for various hardware components installed on the node. Use this status information to retrieve node system data, such as the serial number and BIOS version.

Printing the Legacy Admin Console

Click Print at the top of the page to display a printer-friendly version of the legacy Admin Console.

To include a portion of the console in an email, copy the text and paste it to an HTML-formatted email.

If you are not using HTML-formatted email, you can paste a portion of the printed formatted page into an application (such as Microsoft® Excel® or Word®) and then copy it to another location.

Viewing License Information

Your cluster license appears when you click the Licensed to link at the top of the legacy Admin Console. This window displays your registration status, contact information, and the configuration settings in the license file.

If your cluster license is invalid, Unregistered appears in the Company field and as a watermark in the legacy Admin Console. Contact your Swarm representative to purchase a valid license.

Branding the Admin Console

You can override the baseline style sheets in the legacy Admin Console using a centralized configuration.

The legacy Admin Console ships with a set of default styles. These styles are persisted in these files:

• console.css. Provides a set of baseline styles.

• console_print.css. Provides a small set of overrides for the printed page.

• console_print_preview.css. Provides the styles for the on-screen print view.

These files are loaded at boot time from a USB or centralized configuration caringo.console directory. If the files are not available in this location, Swarm uses internal file versions.

The styles defined in the standard files can be overwritten with custom styles on a style-by-style basis. Any styles not overwritten revert to the baseline styles provided in the default style sheets.

If a centralized configuration server is not available for your cluster, you can update the console styles by modifying the default styles in console.css, console_print.css, and console_print_preview.css on the USB flash drive for each node.

Overriding Styles on a Centralized Server

To override the baseline styles using a centralized configuration server:

1. Create new style sheet files, clearly named to distinguish them from the originals. The new style sheets define one or more styles from console.css, console_print.css, or console_print_preview.css to override. At minimum, paste specific styles from the default style sheets into your new one and then change those style definitions.

2. Install your new styles and place them on any web server that the storage cluster can access.

3. Configure the cluster to reference your new styles with the consoleStyleURL and consoleReportStyleURL node configuration parameters (Managing Configuration Settings). 
   When you override the styles, the consoleReportStyleURL parameter is used for both the console_print.css and console_print_preview.css style sheets.