diff --git a/content/CORE/CORETutorials/Sharing/iSCSI/AddingiSCSIShare.md b/content/CORE/CORETutorials/Sharing/iSCSI/AddingiSCSIShare.md index 51bdfb166e..4ac9fbb72d 100644 --- a/content/CORE/CORETutorials/Sharing/iSCSI/AddingiSCSIShare.md +++ b/content/CORE/CORETutorials/Sharing/iSCSI/AddingiSCSIShare.md @@ -6,6 +6,7 @@ aliases: /core/sharing/iscsi/iscsishare/ tags: - coreiscsi - corefibrechannel +- tciscsi --- {{< toc >}} diff --git a/content/CORE/CORETutorials/Sharing/iSCSI/UsingiSCSIShare.md b/content/CORE/CORETutorials/Sharing/iSCSI/UsingiSCSIShare.md index 905706dd64..37f6a58975 100644 --- a/content/CORE/CORETutorials/Sharing/iSCSI/UsingiSCSIShare.md +++ b/content/CORE/CORETutorials/Sharing/iSCSI/UsingiSCSIShare.md @@ -5,6 +5,7 @@ weight: 10 tags: - coreiscsi - corefibrechannel +- tciscsi --- {{< toc >}} diff --git a/content/SCALE/SCALETutorials/Shares/iSCSI/AddingISCSIShares.md b/content/SCALE/SCALETutorials/Shares/iSCSI/AddingISCSIShares.md index 4c7f327370..9be2e374a2 100644 --- a/content/SCALE/SCALETutorials/Shares/iSCSI/AddingISCSIShares.md +++ b/content/SCALE/SCALETutorials/Shares/iSCSI/AddingISCSIShares.md @@ -3,8 +3,9 @@ title: "Adding iSCSI Block Shares" description: "This article provides instructions on setting up iSCSI block shares manually or using the wizard and starting the service." weight: 30 tags: - - scaleiSCSI - - scaleshares +- scaleiscsi +- scaleshares +- tciscsi --- {{< toc >}} diff --git a/content/SCALE/SCALETutorials/Shares/iSCSI/IncreaseISCSIStorage.md b/content/SCALE/SCALETutorials/Shares/iSCSI/IncreaseISCSIStorage.md index 0366e212dd..bf57f35b04 100644 --- a/content/SCALE/SCALETutorials/Shares/iSCSI/IncreaseISCSIStorage.md +++ b/content/SCALE/SCALETutorials/Shares/iSCSI/IncreaseISCSIStorage.md @@ -3,8 +3,9 @@ title: "Increasing iSCSI Available Storage" description: "This article provides information on increasing available storage in zvols and file LUNs for iSCSI block shares." weight: 50 tags: - - scaleiSCSI - - scaleshares +- scaleiscsi +- scaleshares +- tciscsi --- {{< toc >}} diff --git a/content/SCALE/SCALETutorials/Shares/iSCSI/UsingISCSIShares.md b/content/SCALE/SCALETutorials/Shares/iSCSI/UsingISCSIShares.md index e760fa8277..4b0efd64a9 100644 --- a/content/SCALE/SCALETutorials/Shares/iSCSI/UsingISCSIShares.md +++ b/content/SCALE/SCALETutorials/Shares/iSCSI/UsingISCSIShares.md @@ -3,8 +3,9 @@ title: "Using an iSCSI Share" description: "This article provides information on setting up a Linux or Windows system to use a TrueNAS-configured iSCSI block share." weight: 40 tags: - - scaleiSCSI - - scaleshares +- scaleiscsi +- scaleshares +- tciscsi --- {{< toc >}} diff --git a/content/SCALE/SCALEUIReference/Shares/iSCSI/iSCSISharesScreens.md b/content/SCALE/SCALEUIReference/Shares/iSCSI/iSCSISharesScreens.md index 29dd9cac5e..7a59ae45f8 100644 --- a/content/SCALE/SCALEUIReference/Shares/iSCSI/iSCSISharesScreens.md +++ b/content/SCALE/SCALEUIReference/Shares/iSCSI/iSCSISharesScreens.md @@ -3,8 +3,9 @@ title: "Block (iSCSI) Share Target Screens" description: "This article provides information on Block (iSCSI) Share Targets screens and settings." weight: 30 tags: - - scaleiSCSI - - scaleshares +- scaleiscsi +- scaleshares +- tciscsi --- {{< toc >}} diff --git a/content/TrueCommand/Administration/Admin/LDAPServers.md b/content/TrueCommand/Administration/Admin/LDAPServers.md index 9254d0948d..8b6c818d22 100644 --- a/content/TrueCommand/Administration/Admin/LDAPServers.md +++ b/content/TrueCommand/Administration/Admin/LDAPServers.md @@ -19,7 +19,7 @@ Click the gear icon in the upper toolbar and select **Administration**. Scroll d ![AddLDAPServer](/images/TrueCommand/AddLDAPServer.png "Add LDAP Servers") -| Field | Description | +| Setting | Description | |---------|-------------| | **Hostname** | Host name of LDAP/AD server, with optional port. e.g. example.com:636. | | **Domain** | LDAP base domain. e.g. dc=example,dc=com. | diff --git a/content/TrueCommand/Administration/SystemLog.md b/content/TrueCommand/Administration/SystemLog.md index d879edd6c9..557c73426c 100644 --- a/content/TrueCommand/Administration/SystemLog.md +++ b/content/TrueCommand/Administration/SystemLog.md @@ -1,6 +1,10 @@ --- title: "System Log" +description: "This article provides information on system logs." weight: 30 +aliases: +tags: +- tcsystems --- {{< toc >}} diff --git a/content/TrueCommand/Administration/Systems.md b/content/TrueCommand/Administration/Systems.md index 5aa96d6f45..6cb46c82df 100644 --- a/content/TrueCommand/Administration/Systems.md +++ b/content/TrueCommand/Administration/Systems.md @@ -1,6 +1,10 @@ --- title: "Systems" +description: "This article provides information on the System screens, settings, and options." weight: 10 +aliases: +tags: +- tcsystems --- {{< toc >}} @@ -47,9 +51,12 @@ Click }} -If the system has **Available** in the **Updates** column, it has system updates ready to apply. -Click **Update** on the options menu to open a dialog window with information on the update. -Check the **Confirm** box, then click **OK** to update the system. +If the system has updates ready to apply, a green **Update** displays on the system information screen. + +![SystenUpdateAvailable](/images/TrueCommand/2.3.2/SystenUpdateAvailable.png "System Update Available") + +Click on the green arrow_circle_up icon to open the **Update** dialog with information on the update. +Select **Confirm**, then click **OK** to update the system. Click **CANCEL** to close the window without updating. ![Systems Update](/images/TrueCommand/2.1/SystemsUpdateNAS.png "Systems Update") diff --git a/content/TrueCommand/Administration/Users.md b/content/TrueCommand/Administration/Users.md index f45627db54..5c576ac1ce 100644 --- a/content/TrueCommand/Administration/Users.md +++ b/content/TrueCommand/Administration/Users.md @@ -1,6 +1,10 @@ --- title: "Users" +description: "This article provides information on the User screens and settings, and tutorials on how to create or manage user accounts." weight: 20 +aliases: +tags: +- tcusers --- {{< toc >}} diff --git a/content/TrueCommand/Administration/_index.md b/content/TrueCommand/Administration/_index.md index 4fbca054ae..080fd276eb 100644 --- a/content/TrueCommand/Administration/_index.md +++ b/content/TrueCommand/Administration/_index.md @@ -22,3 +22,6 @@ Access to some of these areas may require a TrueCommand administrator account. {{< include file="static/includes/General/MenuNav.md.part" markdown="true" >}} +## Article Summaries + +{{< children depth="2" description="true" >}} \ No newline at end of file diff --git a/content/TrueCommand/Alerts/AlertManage.md b/content/TrueCommand/Alerts/AlertManage.md index 6342a05c90..d8dba2b67c 100644 --- a/content/TrueCommand/Alerts/AlertManage.md +++ b/content/TrueCommand/Alerts/AlertManage.md @@ -1,6 +1,6 @@ --- title: "Alert Management" -description: "This article provides general information on the alert screens and functions in TrueCommand. It also provides basic instructions on managing alerts, and on configuring alert rules, or services in TrueCommand including SMTP and user email, or PagerDuty." +description: "This article provides information on the alert screens and functions in TrueCommand. It also provides instructions on managing alerts, configuring alert rules, or setting up alert services for SMTP and user email, or PagerDuty in TrueCommand." weight: 10 aliases: - /truecommand/alerts/alertmanage/ @@ -152,7 +152,7 @@ To configure SMTP service: 1. Enter values in all fields on the **SMTP Email** screen and then click **SAVE**: - ![AlertServicesSMTPEmailptions](/images/TrueCommand/2.0/AlertServicesSMTPEmailptions.png "Alert Services: SMTP Email options") + ![AlertServiceSMTPEmailScreen](/images/TrueCommand/2.3.2/AlertServiceSMTPEmailScreen.png "Alert Services: SMTP Email options") * **Mailserver** (*smtp.gmail.com* for example) * **Mailserver port** number the mail service uses @@ -160,6 +160,7 @@ To configure SMTP service: * **Auth pass** password for the plain authentication; for a *No-Auth* SMTP configuration, leave the password field blank If configuring smtp.gmail.com, create an **App Password** in the gmail account for the gmail account. Enter this passcode here to configure gmail SMTP service authentication, * **From** is what sends the email (i.e., no-reply@TrueCommand.io) or allows you to customize the sender field of the email + * **Tls** initiates a connection with TLS, and uses system settings. Click **Test** on the **SMTP Email** configuration screen to verify that the configuration is correct. If you did not receive a test alert email, check the values entered for accuracy. diff --git a/content/TrueCommand/SystemManagement/SingleSystem/TrueCommandSnapshots.md b/content/TrueCommand/SystemManagement/SingleSystem/TrueCommandSnapshots.md index 37c1dbdfee..0fa030bd07 100644 --- a/content/TrueCommand/SystemManagement/SingleSystem/TrueCommandSnapshots.md +++ b/content/TrueCommand/SystemManagement/SingleSystem/TrueCommandSnapshots.md @@ -1,42 +1,99 @@ --- title: "TrueCommand Snapshots" +description: "This article provides instructions on setting up and running snapshots in TrueCommand." weight: 40 +aliases: +tags: +- tcsnapshots +- scalesnapshots +- coresnapshots --- {{< toc >}} -## View Snapshots -To view a system's already existing snapshots, click *EXPLORE* in that system's window and select a storage pool. Once the pool loads, select the *Snapshots* tab. +## Viewing Snapshots -![TrueCommandSelectPool](/images/TrueCommand/2.0/TC20TrueCommandSelectPool.png "Select a Pool") +To view a list of snapshots for a system, click **EXPLORE** on the system widget (information card), then select the pool. -![TrueCommandViewSnapshots](/images/TrueCommand/2.0/TC20TrueCommandViewSnapshots.png "View Snapshots") +![ExploreSystemSelectPool](/images/TrueCommand/2.3.2/ExploreSystemSelectPool.png "Select a Pool") -## Create Single Snapshots +Click **Snapshots** to see a list of snapshots for the root or pool-level dataset. +To see a list of snapshots for any other dataset, click on the dataset, then on **Snapshots**. -To create single snapshots, select a pool in the system's *EXPLORE* menu and click *CREATE SNAPSHOTS*, then select *Create One-Time Snapshot*. -![TrueCommandCreateOneTimeSnapshot](/images/TrueCommand/2.0/TC20TrueCommandCreateOneTimeSnapshot.png "Create One-time Snapshot") +![ExploreSystemDatasetSnapshotList](/images/TrueCommand/2.3.2/ExploreSystemDatasetSnapshotList.png "Dataset Snapshot list") -Name the snapshot and click *CONFIRM*. +The header displays the breadcrumb for the system, pool, and dataset. To return to the pool, click the down arrow beside the system name, then select the pool on the dropdown list. -## Create Recurring Snapshot Tasks +## Taking Snapshots +If the dataset does not have existing snapshots, a blue **CREATE SNAPSHOTS** button displays instead of a list of snapshots. -To create recurring snapshot tasks, select a pool in the system's *EXPLORE* menu and click *CREATE SNAPSHOTS*, then select *Create Snapshot Task*. +![CreateSnapshotButtons](/images/TrueCommand/2.3.2/CreateSnapshotButtons.png "Create Snapshot Buttons") -![TrueCommandCreateSnapshotTask](/images/TrueCommand/2.0/TC20TrueCommandCreateSnapshotTask.png "Create Snapshot Task") +You can use this or the white **CREATE SNAPSHOTS** button under the *pool/dataset* path on the left-side panel. +**CREATE SNAPSHOTS** displays two options: -Set the task's schedule and determine the snapshot lifetime, then click *CONFIRM*. +* **Create One-time Snapshot** to take a single snapshot +* **Create Snapshot Task** to create a snapshot task that runs on a schedule + + +### Creating a Single Snapshot + +To create single snapshots: + +Click **EXPLORE** on the system card found on the dashboard, then select a pool on that system. + +Next, click on a dataset you want to snapshot, then click **CREATE SNAPSHOTS**. + + +![CreateSnapshotsOptions](/images/TrueCommand/2.3.2/CreateSnapshotsOptions.png "Create One-time Snapshot") + +Select **Create One-Time Snapshot** to open the snapshot dialog. + +![CreateSnapshotDialog](/images/TrueCommand/2.3.2/CreateSnapshotDialog.png "Create Snapshot Dialog") + +Enter a name for the snapshot. +Select **Recursive** if the dataset selected has other datasets nested under it and you want to include those in the snapshot. + +Click **OK**. + +## Creating a Snapshot Task + +To create snapshot tasks that occurs on a schedule: + +Find the system card on the dashboard and click **EXPLORE**, then select a pool. + +Next, click on a dataset you want to snapshot, then click **CREATE SNAPSHOTS**. + + +![CreateSnapshotsOptions](/images/TrueCommand/2.3.2/CreateSnapshotsOptions.png "Create Snapshot Task") + +Select **Create Snapshot Task** to open the **Create Snapshot Task** configuration screen. +If you did not select a dataset in the pool, you can select one from the dropdown list in the **Dataset** section. Otherwise, this area is not editable. + + +![CreateSnapshotTaskDataset](/images/TrueCommand/2.3.2/CreateSnapshotTaskDataset.png "Create Snapshot Task Dataset Path") + +Set the schedule for the task. Select the frequency from the **Period** dropdown, the day of the week, the hour, and the minute you want to run the task. + + +![CreateSnapshotTaskScheduleAndLifetime](/images/TrueCommand/2.3.2/CreateSnapshotTaskScheduleAndLifetime.png "Add Snapshot Task Schedule and Lifetime") + +Select the task lifetime. Enter a number in **Lifetime Value**, then select the unit from the **Lifetime Unit** dropdown list. Options are **Hour**, **Day**, **Week**, **Month**, and **Year**. + + +Click **OK** to save the task. ## Timezones -When you create snapshot tasks, TrueCommand uses the system the dataset is mounted in to determine what timezone it will use. +When you create snapshot tasks, TrueCommand uses the system the dataset is mounted in to determine what timezone it uses. + +For example, if you are in New York and the dataset is mounted to a system with a Los Angeles timezone, a snapshot task set to run at 12:00 P.M. runs at 3:00 P.M. your time. + -For example, if you are in New York and the dataset is mounted to a system with a Los Angeles timezone, a snapshot task set to occur at 12:00 P.M. will actually occur at 3:00 P.M. your time. +To see what timezone a system is in, go to that TrueNAS system UI and navigate to **System > General** for CORE or **System Settings > General** in SCALE, then find the **Localization** widget or section. -To see what timezone a system is in, go to that system's UI and navigate to **System > General** (**System Settings > General** in SCALE). -That system's timezone information is in the *Localization* section. Administrators can change the system's timezone using the drop-down menu. +{{< taglist tag="tcsnapshots" limit="10" >}} -![TrueCommandTimezone](/images/TrueCommand/2.0/TC20TrueCommandTimezone.png "Timezones") diff --git a/content/TrueCommand/SystemManagement/SingleSystem/_index.md b/content/TrueCommand/SystemManagement/SingleSystem/_index.md index 1125626c15..228eaa338c 100644 --- a/content/TrueCommand/SystemManagement/SingleSystem/_index.md +++ b/content/TrueCommand/SystemManagement/SingleSystem/_index.md @@ -1,24 +1,30 @@ --- title: Single System Management +description: "" weight: 20 geekdocCollapseSection: true +aliases: +tags: --- -While TrueCommand allows users to manage all of their systems on a single dashboard, it also lets users view single systems at a time. -To manage a single system, click on the system name in its card or click on the dashboard drop-down menu, and hover over **Ungrouped** to see the systems list. +TrueCommand allows users to manage all of their systems on a single dashboard that also lets users view single systems at a time. + +To manage a single system, either click on the name on a System card or click on the **All** dropdown arrow_drop_down on the left side of the system header at the top of main dashboard. Select or hover over **Ungrouped** to see the list of systems. Select the system you want to manage. -![TrueCommandSelectSingleSystem](/images/TrueCommand/2.1/DashboardSelectSingleSystem.png "Select Single System") +![MainDashboardSelectUngroupedSystem](/images/TrueCommand/2.3.2/MainDashboardSelectUngroupedSystem.png "Selecting a System") -While viewing a single system, users can see various statistics like CPU, memory, disk, network, and storage usage, as well as existing datasets and [alerts]({{< relref "AlertManage.md" >}}). +Single system cards display various statistics like CPU, memory, disk, network, and storage usage, as well as existing datasets and [alerts]({{< relref "AlertManage.md" >}}). -Users can create and manage storage, snapshots, and shares using the **File Explorer**. +Users can create and manage storage, replication, snapshots, and shares using the **Explore** button. -Users can view expanded TrueNAS information details by clicking on the double arrows located at the lower right corner of the system card. Information includes the system manufacturer, serial numbers, support tier, support expiration date, hostname, CPU, CPU cores, physical memory, OS, and uptime. +Users can view expanded TrueNAS information details by clicking on the double arrows keyboard_double_arrow_down at the lower right corner of the system card. +Information includes the system manufacturer, serial numbers, support tier, support expiration date, host name, CPU, CPU cores, physical memory, OS, and uptime. -![TrueCommandSingleSystemhardware](/images/TrueCommand/2.0/TCHardwareDash.png "Single System Hardware Information") +![SystemInformationCardDetails](/images/TrueCommand/2.3.2/SystemInformationCardDetails.png "Single System Hardware Details") Users with adequate permissions can update the system, [configure backups]({{< relref "TrueNASConfigManage.md" >}}), and generate system audits and [reports]({{< relref "Creation.md" >}}). If a system update is available, the **Update** label and icon turn green. You can also see which systems have updates pending on the **Systems** screen. -![TrueCommandSingleSystemDashboard](/images/TrueCommand/2.0/TC20TrueCommandSingleSystemDashboard.png "Single System Dashboard") +![SystemUpdateAvailable](/images/TrueCommand/2.3.2/SystemUpdateAvailable.png "Single System Dashboard") + diff --git a/content/TrueCommand/TCGettingStarted/InitialConfig.md b/content/TrueCommand/TCGettingStarted/InitialConfig.md index 5f3e4720b3..e1232c406d 100644 --- a/content/TrueCommand/TCGettingStarted/InitialConfig.md +++ b/content/TrueCommand/TCGettingStarted/InitialConfig.md @@ -12,74 +12,98 @@ tags: - coretoptoolbar --- {{< toc >}} + + TrueCommand allows you to manage all your TrueNAS systems from one location. This multi-system management increases efficiency and simplifes operations -To get started with the initial configuration of TrueCommand, complete these steps: +## Getting Started + +To get started with the initial configuration of TrueCommand, you: + +1. [Create the administrator account]({{< relref "/TrueCommand/TCGettingStarted/AdminAccounts.md" >}}). +2. [Create user accounts]({{< relref "/TrueCommand/TCGettingStarted/UserAccounts.md" >}}). +3. Become familiar with the interface toolbars and icons. Review the [Interface Overview]({{< relref "/TrueCommand/TCGettingStarted/InterfaceOverview.md" >}}) article. +4. [Connect your first TrueNAS system]({{< relref "/TrueCommand/TCGettingStarted/ConnectingTrueNAS.md" >}}). -1. Create the administrator account. See [Creating the Admin Account]({{< relref "/TrueCommand/TCGettingStarted/AdminAccounts.md" >}}) for more information. -2. Create the necessary user accounts. See [Creating User Accounts]({{< relref "/TrueCommand/TCGettingStarted/UserAccounts.md" >}}). -3. Become familiar with the interface toolbars and icons. Review them here [Interface Overview]({{< relref "/TrueCommand/TCGettingStarted/InterfaceOverview.md" >}}). -4. Connect your first TrueNAS system. See [Connecting Your First TrueNAS System]({{< relref "/TrueCommand/TCGettingStarted/ConnectingTrueNAS.md" >}}) for more information. +## TrueCommand Administration Overview + +The **Administration** screen, available to users with administrator permissions, displays additional system details and offers a variety of TrueCommand configuration options through the system widgets or information cards. -The **Administration** page, available to users with administrator permissions, displays additional system details and offers a variety of TrueCommand configuration options. -Click the **Configure** icon and select **Administration** to access the **Administration** screen. It is organized into **About**, **Certificates**, and **Configuration** widgets (functional and information cards). +To access the **Administration** screen, click the **Configure** icon and select **Administration**. ![TrueCommand231AdminSystemInfo](/images/TrueCommand/2.3.1/TrueCommand231AdminSystemInfo.png "Administration Configuration") -## TrueCommand Administration Overview +The screen has seven widgets: +* **[About](#about-widget)** that covers TrueCommand system information, iXsystems Support Contact information, and TrueCommand licenses. +* **[Certificates](#certificates-widget)** where you can access system certificates and upload or reset certificates. +* **[Certificate Authorities](#certificate-authorities-widget)** where you can access or import certificate authorities. +* **[Configuration](#configuration-widget)** where you configure general, SSL, and alert options, LDAP and SAML service, and Telemetry. +* **[LDAP Servers](#ldap-servers-widget)** where you configure LDAP server settings. +* **[LDAP Teams](#ldap-teams-widget)** where you can join LDAP teams. +* **[Alert Recipients](#alert-recipients-widget)** where you configure users and their email addresses that receive system alerts. -### About +## About Widget -The **About** widget displays the current TrueCommand system ID and version, contact information for iXsystems, and license details. +The **About** widget displays the current TrueCommand system ID and version information, iXsystems Support contact information, and license details. +Click **Get a License** to open a browser file for your system where you can obtain a license and **Upload License** to add it to TrueCommand. -#### Updating the License +### Updating Licenses You can expand TrueCommand to monitor more disks by upgrading or purchasing a license from iXsystems. Click **GET A LICENSE** to open a new browser tab to purchase a TrueCommand license. You can also contact iXsystems to upgrade the current license. -After you upgrade or purchase a new license, you must upload it to TrueCommand. -Click **Browse…** to open a file browser on your local system. +After you upgrade or purchase a new license, upload it to TrueCommand. +Click **Browse** to open a file browser on your local system. Select the new license file to upload and click **UPLOAD LICENSE** to apply the new license to TrueCommand. -### Certificates Widget +## Certificates Widget + +The **Certificates** widget shows the certificates TrueCommand uses and has options to reset or upload a certificate. -The **Certificates** widget shows the certificates and Certificate Authorities (CAs) TrueCommand uses and has options to upload or import a certificate or CA. +![AdministrationCertificatesWidget](/images/TrueCommand/2.3.2/AdministrationCertificatesWidget.png "Administration: Certificates Widget") + +Click **Upload Certificate** to open the **Upload Certificate** screen, where you can either browse to or drag and drop a certificate and a private key file into TrueCommand. ![AdministrationCertificates](/images/TrueCommand/2.2/AdministrationCertificates.png "Administration: Certificates") -Click **Browse...** to upload a file from the local system. Selecting **Plain text** allows you to copy and paste the raw text instead of uploading a file. -### Certificate Authorities +## Certificate Authorities Widget Click **IMPORT** in the **Certificate Authorities** screen to add certificate authorities (CAs) to TrueCommand. -![AdministrationCAs](/images/TrueCommand/2.2/AdministrationCAs.png "Administration: Certificates") +![AdministrationCertificateAuthoritiesWidget](/images/TrueCommand/2.3.2/AdministrationCertificateAuthoritiesWidget.png "Administration: Certificates Authorities Widget") -The **CA Import** screen allows name the CA and to select changing it to plain text before you upload it. +Click **Import** to open the **Add Certificate Authority** screen, where you enter the name for the CA and either browse to or drag and drop the CA file into TrueCommand. + +![AdministrationCAs](/images/TrueCommand/2.2/AdministrationCAs.png "Administration: Certificates") -### Configuration +Selecting **Plain Text** allows you to copy and paste the raw text before you upload it. -The **Configuration** widget contains options to configure various TrueCommand features. Configuration options are: +## Configuration Widget -* General Options -* SSL Options -* Alert Options -* LDAP -* SAML -* Telemetry +The **Configuration** widget displays current general, SSL, alert options, LDAP, SAML, and telemetry service settings. It provides access to a configuration screen to add or make changes to these settings: -Click **CONFIGURE** to change feature settings. +* **General Options** +* **[SSL Options](#ssl-options)** +* **[Alert Options](#alert-options)** +* **[LDAP](#ldap)** +* **[SAML](#saml)** +* **[Telemetry](#telemetry)** -![AdministrationConfiguration](/images/TrueCommand/2.2/AdministrationConfiguration.png "Administration: Configuration1") +![AdministrationConfigurationWidget](/images/TrueCommand/2.3.2/AdministrationConfigurationWidget.png "Administration Configuration Widget") -After changing any options, click **SAVE** at the bottom of the window to save the new system configuration. -To reset fields back to their previous values, click **CANCEL**. +Click **CONFIGURE** to open the **Configuration** screen where you can manage feature settings. After changing any options, click **Save** or **Cancel** to reset fields back to their previous values. +### General Options General options include how long TrueCommand stores system statistics and the number of database backups from an iXsystems NAS to store. -#### SSL options +![ConfigurationScreenGeneralSSLAlertOptions](/images/TrueCommand/2.3.2/ConfigurationScreenGeneralSSLAlertOptions.png "Configuration General SSL and Alert Options") + +Enter numeric values in the **Months** and **Backups** fields. + +### SSL options {{< hint info >}} This feature is only available for local installations or containerized TrueCommand deployments. @@ -87,55 +111,59 @@ This feature is only available for local installations or containerized TrueComm {{< include file="static/includes/TrueCommand/2.0/TrueCommandSSL.md.part" markdown="true" >}} -#### Alert Options +### Alert Options -You can adjust the alert levels that TrueCommand shows from a connected NAS to tune the system messages displayed according to your use case. -Choose an alert category to ignore. -You can select multiple categories. +You can adjust the alert levels that TrueCommand shows from a connected TrueNAS system to tune the system messages displayed according to your use case. +Select an alert category to ignore. Options are **None**, **Information**, **Warning** and **Critical**. Alerts generated by TrueCommand rules are unaffected. -#### LDAP +### LDAP -The **Allow LDAP user creation** checkbox is not selected (disabled) by default. If disabled, you can use LDAP to log in with existing users. +The **Allow LDAP user creation** checkbox is not selected (disabled) by default. When disabled, you can use LDAP to log in with existing users. -#### SAML +### SAML -The SAML service feature allows users to configure TrueCommand SAML for [Active Directory]({{< relref "SAMLAD.md" >}}) or [Google Admin]({{< relref "SAMLGA.md" >}}) +The SAML service is an experimental feature that allows users to configure TrueCommand SAML for [Active Directory]({{< relref "SAMLAD.md" >}}) or [Google Admin]({{< relref "SAMLGA.md" >}}). -#### Telemetry +### Telemetry -TrueCommand reports some (completely anonymous) basic usage telemetry back to iXsystems for product improvement analysis. +TrueCommand reports some anonymous basic usage telemetry to iXsystems for product improvement analysis. Click the **PREVIEW** button to see what your system is sending. Select **Disable Telemetry** to disable the disable telemetry and click **SAVE**. -## LDAP Servers +## LDAP Servers Widget Users can configure TrueCommand to use [LDAP servers]({{< relref "LDAPServers.md" >}}) for security and authentication management among connected TruNAS systems. -{{< include file="static/includes/TrueCommand/2.0/TrueCommandLDAP.md.part" markdown="true" >}} +{{< include file="/_includes/TrueCommandLDAP.md" type="page" >}} -## LDAP Teams +## LDAP Teams Widget The **LDAP Teams** widget allows you to add TrueCommand teams to your LDAP server by clicking **JOIN** and selecting a team from the list. -## Alert Recipients +## Alert Recipients Widget + +The **Alert Recipients** widget allows you to add recipient email addresses and configure mail list settings. + +![AdministrationAlertRecipientsWidget](/images/TrueCommand/2.3.2/AdministrationAlertRecipientsWidget.png "Administration Screen Alert Recipients Widget") -The **Alert Recipients** widget allows you to add email addresses to your LDAP server by clicking **ADD** and entering a valid address. +Click **Add** to open an add an email address screen. This adds the email address to your LDAP server. -![TrueCommand231AdminAlertRecipientsNone](/images/TrueCommand/2.3.1/TrueCommand231AdminAlertRecipientsNone.png "Administration: Alert Recipients Widget") +![AddRecipientScreene](/images/TrueCommand/2.3.2/AddRecipientScreen.png "Add Recipients Screen") -Clicking the **Configure** button displays the following fields: +Click **Configure** to open the **Mailing List Configure** screen. -![TrueCommand231AdminAlertRecipientsConfigure](/images/TrueCommand/2.3.1/TrueCommand231AdminAlertRecipientsConfigure.png "Administration: Mailing List Configuration") +![MailingListConfigureScreen](/images/TrueCommand/2.3.2/MailingListConfigureScreen.png "Mailing List Configuration Screen") -| Field | Value | -| ----- | ------------- | -| **Mailserver** | Address for the SMTP server. | -| **Mailserver port** | Port number the SMTP server listens to. | -| **Auth user** | User name for plain authentication. | -| **Auth pass** | Password for plain authentication. Leave blank for no-auth. | -| **From** | The email address of the sender. | +| Setting | Description | +|---------|-------------| +| **Mailserver** | Enter the address for the SMTP server. | +| **Mailserver port** | Enter the port number the SMTP server listens to. | +| **Auth user** | Enter the user name for plain authentication. | +| **Auth pass** | Enter the password for plain authentication. Leave blank for no-auth. | +| **From** | Enter the email address of the sender. | +| **Tls** | Initiates a connection with TLS. Uses system settings. | {{< taglist tag="tcinstall" limit="10" >}} {{< taglist tag="tcconfig" limit="10" title="Related Articles" >}} diff --git a/content/TrueCommand/TCGettingStarted/InterfaceOverview.md b/content/TrueCommand/TCGettingStarted/InterfaceOverview.md index 1f67f45abe..15cba9692d 100644 --- a/content/TrueCommand/TCGettingStarted/InterfaceOverview.md +++ b/content/TrueCommand/TCGettingStarted/InterfaceOverview.md @@ -1,6 +1,6 @@ --- title: "Interface Overview" -description: "This article defines the icons, links and alerts on the TrueCommand interface." +description: "This article defines the icons, provides links to articles for each function, and where to access alerts on the TrueCommand interface." weight: 20 tags: - tcinterface @@ -11,27 +11,30 @@ tags: {{< toc >}} -## Top Bar + +## Top Toolbar ![TopBar](/images/TrueCommand/2.1/TopBar.png "Top Bar") The top toolbar has various quick links, configuration options, alerts, and menus. -+ Clicking opens the [**Cluster Volume**]({{< relref "/TrueCommand/Clusters.md" >}}) page. -+ Clicking opens the [**iSCSI Manager**]({{< relref "/TrueCommand/iSCSIManagement.md" >}}) page. -+ Clicking opens the [**Reports**]({{< relref "/TrueCommand/Reports/Creation.md" >}}) page. -+ Clicking toggles documentation tooltips. -+ Clicking opens the **Theme Settings** menu dropdown. See information listed below. -+ Clicking opens a dialog window with a TrueCommand releases and maintenance news feed. -+ Clicking opens the [**Alert Notifications**]({{< relref "/TrueCommand/Alerts/AlertManage.md" >}}) page. -+ Clicking opens the **Settings** menu dropdown. See information listed below. -+ Clicking the user avatar displays the user **Profile** option where you can set a custom avatar to change the default user gravtar. It also provides access to the **API Interface**, the **EULA** and the **Log Out** options. See information listed below. +| Icon | Description | +|------|-------------| +| | Opens the [**Cluster Volume**]({{< relref "/TrueCommand/Clusters.md" >}}) page. | +| | Opens the [**iSCSI Manager**]({{< relref "/TrueCommand/iSCSIManagement.md" >}}) page. | +| | Opens the [**Reports**]({{< relref "/TrueCommand/Reports/Creation.md" >}}) page. | +| | Toggles documentation tooltips. | +| | Opens the **[Theme Setting](#creating-themes-using-the-theme-settings-pallet)** menu dropdown. | +| | Opens a dialog window with a TrueCommand releases and maintenance news feed. | +| | Opens the [**Alert Notifications**]({{< relref "/TrueCommand/Alerts/AlertManage.md" >}}) page. | +| | Opens the **[Settings](#settings-menu)** menu dropdown. | +| User avatar | Opens the user **[Profile](#user-menu)** option where you can set a custom avatar to change the default user gravtar. It also provides access to the **API Interface**, the **EULA** and the **Log Out** options. | -### Creating Themes using the Theme Settings Pallet -{{< expand "Theme Settings menu dropdown" >}} +### TrueCommand Theme Settings TrueCommand includes the ability to customize the alert colors to user preferences. The **Theme settings** pallet is located in the top banner on the right. +{{< expand "Changing Theme Settings" >}} To open the theme configuration menu, click the icon. ![ThemeSelect](/images/TrueCommand/2.0/ThemePallete.png "Theme Select") @@ -45,34 +48,38 @@ To reset all colors to the application defaults, click **DEFAULTS**. {{< /expand >}} ### Settings Menu -{{< expand "Settings menu dropdown" >}} - +The settings dropdown menu provides the main navigation to functional areas in TrueCommand, some of which you can also access from the top toolbar, main Dashboard, and System information screens through **Explore** or the more_vert icon. +{{< expand "Settings Menu Options" >}} The **Settings** menu has the following options: -+ Clicking opens the main TrueCommand Dashboard. -+ Clicking opens the [**System Inventory**]({{< relref "/TrueCommand/systemmanagement/multisystems.md" >}}) page. -+ Clicking opens the [Cluster Volume]({{< relref "/TrueCommand/Clusters.md" >}}) page. -+ Clicking opens the [iSCSI Manager]({{< relref "/TrueCommand/iSCSIManagement.md" >}}) page. -+ Clicking opens the [**Reports**]({{< relref "/TrueCommand/Reports/Creation.md" >}}) page. -+ Clicking opens the [All Alerts]({{< relref "/TrueCommand/Alerts/AlertManage.md" >}}) page. -+ Clicking opens the [Alert Rules]({{< relref "/TrueCommand/Alerts/AlertManage.md" >}}) page. -+ Clicking opens the [Alert Services]({{< relref "/TrueCommand/Alerts/AlertManage.md" >}}) page. -+ Clicking opens the [Systems]({{< relref "/TrueCommand/Administration/Systems.md" >}}) page. -+ Clicking opens the [Users]({{< relref "/TrueCommand/Administration/Users.md" >}}) page. -+ Clicking opens the [Teams]({{< relref "/TrueCommand/Administration/Users.md" >}}) page. -+ Clicking opens the [Logs]({{< relref "/TrueCommand/Administration/SystemLog.md" >}}) page. -+ Clicking opens the [Administration]({{< relref "/TrueCommand/Administration/Admin/_index.md" >}}) page. +| Icon | Description | +|------|-------------| +| | Opens the main TrueCommand Dashboard. | +| | Opens the [**System Inventory**]({{< relref "/TrueCommand/systemmanagement/multisystems.md" >}}) screen. | +| | Opens the [Clusters]({{< relref "/TrueCommand/Clusters.md" >}}) screen. | +| | Opens the [iSCSI Manager]({{< relref "/TrueCommand/iSCSIManagement.md" >}}) screen. | +| | Opens the [**Reports**]({{< relref "/TrueCommand/Reports/Creation.md" >}}) screen. | +| | Opens the [All Alerts]({{< relref "/TrueCommand/Alerts/AlertManage.md" >}}) screen. | +| | Opens the [Alert Rules]({{< relref "/TrueCommand/Alerts/AlertManage.md" >}}) screen. | +| | Opens the [Alert Services]({{< relref "/TrueCommand/Alerts/AlertManage.md" >}}) screen. | +| | Opens the [Systems]({{< relref "/TrueCommand/Administration/Systems.md" >}}) screen. | +| | Opens the [Users]({{< relref "/TrueCommand/Administration/Users.md" >}}) screen. | +| | Opens the [Teams]({{< relref "/TrueCommand/Administration/Users.md" >}}) screen. | +| | Opens the [Administration]({{< relref "/TrueCommand/Administration/Admin/_index.md" >}}) screen. | +| |Opens the [Logs]({{< relref "/TrueCommand/Administration/SystemLog.md" >}}) screen. | + {{< /expand >}} -### User Menu -{{< expand "User (avatar) menu dropdown" >}} - -The user menu (avatar) has the following options: +### User Avatar Menu +The user avatar provides access to the logged-in user profile, API Interface, user license (EULA), and the log out option. +{{< expand "User (avatar) Options" >}} +| Icon | Description | +|------|-------------| +| | Opens the **[Profile]({{< relref "/TrueCommand/Administration/Users.md" >}})** screen for the logged-in user. | +| | Opens the **[API Interface]({{< relref "/TrueCommand/API/_index.md" >}})** testing screen. | +| | Opens the [TrueCommand EULA]({{< relref "/TrueCommand/Notices/TCTermsOfService.md" >}}) window. | +| | Logs the user out of TrueCommand. | -+ Clicking opens the [**Users**]({{< relref "/TrueCommand/Administration/Users.md" >}}) page. -+ Clicking opens the [**API Interface**]({{< relref "/TrueCommand/API/_index.md" >}}) testing page. -+ Clicking opens the [TrueCommand EULA]({{< relref "/TrueCommand/Notices/TCTermsOfService.md" >}}). -+ Clicking logs the user out of TrueCommand. {{< /expand >}} {{< taglist tag="tcinstall" limit="10" >}} diff --git a/content/TrueCommand/TCReleaseNotes.md b/content/TrueCommand/TCReleaseNotes.md index 2386d64c6e..04b83b9980 100644 --- a/content/TrueCommand/TCReleaseNotes.md +++ b/content/TrueCommand/TCReleaseNotes.md @@ -1,5 +1,5 @@ --- -title: TrueCommand 2.3.1 Release Notes +title: TrueCommand 2.3.2 Release Notes weight: 5 aliases: - /truecommand/tcreleasenotes/2.2 @@ -19,27 +19,61 @@ aliases: | Version | Checkpoint | Scheduled Date | |---------|------------|----------------| -| 2.3.2 | Code-freeze | 23 March 2023 | -| 2.3.2 | Internal Testing Sprints | 27 March 2023 - 07 April 2023 | -| 2.3.2 | Tag | 10 April 2023 | -| 2.3.2 | Release | 11 April 2023 | | 2.3.3 | Code-freeze | 17 May 2023 | -| 2.3.3 | Internal Testing Sprints | 18 May - 2 June 2023 | -| 2.3.3 | Tag | 4 June 2023 | -| 2.3.3 | Release | 5 June 2023 | +| 2.3.3 | Internal Testing Sprints | 18 May - 02 June 2023 | +| 2.3.3 | Tag | 04 June 2023 | +| 2.3.3 | Release | 05 June 2023 | -## 2.3.1 +## 2.3.2 + +April 18, 2023 + +iXsystems is pleased to release TrueCommand 2.3.2! +This release is a maintenance release that fixes issues identified in earlier releases, improves validation, and adds new functions and improvements to existing functions. Changes include: + +* Adds TLS for email and SMTP +* Adds new Order property for Systems and Groups +* Adds support for IDP-initiated SAML +* Improves creating new volumes in the UI +* Improves UI cluster creation and adds warning +* Improves NAS connection validation +* Improves main Dashboard information widgets +* Changes NAS SSL connections for on-site instances +* Removes iSCSI cache +* Fixes disk license issues by sending new server and limit limit events when license limit is exceeded + +### 2.3.2 Change Log + +### New Feature + +* [TC-2533](https://ixsystems.atlassian.net/browse/TC-2533) Hook in new servers/limit event sent when license limit has been exceeded +* [TC-2633](https://ixsystems.atlassian.net/browse/TC-2633) Hook in new TLS field for email settings + +### Improvement -February 16, 2023 +* [TC-2566](https://ixsystems.atlassian.net/browse/TC-2566) Customer needs TLS for SMTP added back in. +* [TC-2574](https://ixsystems.atlassian.net/browse/TC-2574) Icon for CORE system on dashboard old icon +* [TC-2580](https://ixsystems.atlassian.net/browse/TC-2580) Do not force NAS SSL for on-site instances +* [TC-2581](https://ixsystems.atlassian.net/browse/TC-2581) Populate the Lifetime Unit field with the valid choices +* [TC-2582](https://ixsystems.atlassian.net/browse/TC-2582) Add \`order\` property in system and groups +* [TC-2583](https://ixsystems.atlassian.net/browse/TC-2583) Use cached base images instead of single repo container file +* [TC-2586](https://ixsystems.atlassian.net/browse/TC-2586) Support IDP-initiated SAML +* [TC-2598](https://ixsystems.atlassian.net/browse/TC-2598) after volume creation, redirect users directly to share panel +* [TC-2599](https://ixsystems.atlassian.net/browse/TC-2599) expose nas configs from the cluster cards +* [TC-2628](https://ixsystems.atlassian.net/browse/TC-2628) add update NAS dialog to the multisystem dash +* [TC-2630](https://ixsystems.atlassian.net/browse/TC-2630) Warning when creating cluster +* [TC-2637](https://ixsystems.atlassian.net/browse/TC-2637) Remove iSCSI cache +* [TC-2645](https://ixsystems.atlassian.net/browse/TC-2645) Add a cluster indicator to dash card +* [TC-2672](https://ixsystems.atlassian.net/browse/TC-2672) Relaxed NAS Connection Validation +* [TC-2686](https://ixsystems.atlassian.net/browse/TC-2686) Sanitize data source inputs -iXsystems is pleased to release TrueCommand 2.3.1! -This release is a maintenance release that fixes issues identified in the 2.3.0 release and adds a few new improvements. Changes include: +### Bug -* Refresh option no longer logs users out of TrueCommand -* Unlimited disk count license no longer enforced -* Upgrade available indication added to system dashboard cards -* Port option added to the Servers Add screen -* Code field now sends SMTP Configuration Validation +* [TC-2561](https://ixsystems.atlassian.net/browse/TC-2561) Theme adjustments not sticking after log in / log out +* [TC-2636](https://ixsystems.atlassian.net/browse/TC-2636) short domains are not allowed during configure cluster + +## 2.3.1 +{{< expand "2.3.1" "v" >}} ### 2.3.1 Change Log @@ -57,6 +91,7 @@ This release is a maintenance release that fixes issues identified in the 2.3.0 * [TC-2553](https://ixsystems.atlassian.net/browse/TC-2553) Disable strict SNI host matching in Caddyfile * [TC-2559](https://ixsystems.atlassian.net/browse/TC-2559) Panic when adding certificate * [TC-2560](https://ixsystems.atlassian.net/browse/TC-2560) fix marshaling error for cpu temperature stats +{{< /expand >}} ## 2.3 {{< expand "2.3.0" "v" >}} @@ -523,17 +558,44 @@ TrueCommand 2.1 is the single pane of glass for: {{< /expand >}} -## Known Issues - -| Seen In | Key | Summary | Workaround | Resolved In | -|---------|-----|---------|------------|-------------| -| TC 2.3.0 | TC-2609 | Unable to recreate a cluster after removing the cluster | After removing a cluster, unable to create a new cluster as not all settings with dropdown lists populate the options preventing configuring required settings. Recommend you not delete your cluster until this is fixed. Underlying issue is identified and will be included in the next release. | Targeted 2.3.2 | -| TC 2.3.0 | TC-2533 | Hook in new servers/limit event sent when license limit is exceeded | This event replaces an error on servers/add, which instead sends max_disks and license_count if the license is executed, but not error. Any time a check fails the servers/limit event is sent as well, for asynchronous occurrences. | Targeted 2.3.2 | -| TC 2.3.0 | TC-2528 | Cannot enable team alert creation | Enabling team alert creation on new teams does not stick as the only way to submit is to update the name, which resets the checkbox after the team object is reloaded. | Unknown | -| TC 2.3.0 | TC-2524 | Notices WebSocket test results are unstable | Most tests pass but some are failing but never on the same test. Possible middleware issue. | Targeted 2.3.2 | -| TC 2.3.0 | TC-2508 | Teams, systems and groups missing in User after migration from 2.2.2 to 2.3.0 | After migrating from 2.2.2. to 2.3.0, users no longer had Teams, Systems or system Groups assigned. The Teams are and system groups are listed in the Systems/System Groups and Teams areas but no longer assigned under the User. | Fixed in 2.3.0 | -|TC 2.2.2 | TC-2339 | Dashboard System card values for SCALE 22.12 do not populate. | The TrueCommand Dashboard System card values for SCALE 22.12 Bluefin are missing. | Fixed in 2.2.3 | +## Known Issues +Known issues are those found during internal testing or reported by the community and are listed in two tables: +* Issues from a release that will be resolved in a future targeted release(s). +* Issues resolved in a particular version. + + +### Known Issues with a Future Resolution + +| Seen In | Key | Summary | Details / Workaround | Resolution Target | +|---------|-----|---------|----------------------|-------------------| +| 2.3.2 | TC-2733 | License has expired but no message in the UI | N/A | 2.3.3 | +| 2.3.2 | TC-2732 | NAS HTTPS connection backed by certificates created with brainpool curves fail TLS handshakes | NAS supports nine types of elliptical curves for certificate keys. Four of these are brainpool curves, which is the SCALE default curve. CORE and SCALE have the same set of curves but each has different default curve type. Golang and Github limit support for the nine curves. TrueCommand has two ways to handle this by either avoiding HTTPS or injecting the curve definitions in during the TrueCommand build. | 2.3.3 | +| 2.3.2 | TC-2731 | Explore: The Periodic Snapshot test and the snapshot doesn't list for zvols | Using the TrueCommand Explore option for a pool with a zvol and Periodic Snapshot or Snapshot options. After selecting either Periodic Snapshots or Snapshots should see the zvol but it is not listed under either. | 2.3.3 | +| 2.3.2 | TC-2730 | Add "License has" in front of the message about License expiring message | UI improvement to the current license expiring message. | 2.3.3 | +| 2.3.2 | TC-2729 | Cluster issues after updating individual notes to 22.12.2 | A cluster, created in TrueCommand 2.3.2, using four nodes with 22.12.1 and an SMB share, and that upgrades to 22.12.2 results in the SMB share being inaccessible. | 2.3.3
22.12.3 | +| 2.3.2 | TC-2723 | R30 System Card System Image and Information Display Issues | The expanded System Card does not show the image of the R30 and the information text displays outside of the card frame. | 2.3.3, 3.0 | +| 2.3.2 | TC-2715 | Home Directory field cursor location is misleading when creating a user in TrueCommand | After adding a system and selecting Users and Groups from the action list, and then entering a value in Home Directory, the cursor is positioned after /mnt// in the path and not at the beginning of the field, leading the user to think they should edit from that point. The entire path value can be overridden with a new pool and dataset path. | 2.3.3 | +| 2.3.1 | TC-2677 | Cannot Administer Cluster in TC after creation | After creating a cluster and registering nodes as gluster peers, the TrueCommand instance does not display the cluster in the UI and API calls do not recognize the cluster. Reinstalling from the 22.12.2 iso file or using 22.12.1 UI does result in a successful cluster creation. | 2.3.3 | +| 2.3.2 | TC-2711 | No error encountered when creating a user on a system without any pools, with a Home Directory path that doesn't exist on a system in TrueCommand | After logging into TrueCommand and adding a system without any pools, and then trying to add a user and Home Directory, TrueCommand does not show an error or alert to indicate the user is not created. The user is created on the TrueNAS system but not in TrueCommand. | 3.0 | +| 2.3.0 | TC-2528 | Cannot enable team alert creation | Enabling team alert creation on new teams does not stick. The only way to submit the change is to update the name, but this resets the checkbox after the team object reloads. | 3.0 | +| 2.3.2 | TC-2734 | Creating an iSCSI volume doesn't set Start Automatically for the iSCSI service | When creating an iSCSI volume through TrueCommand should automatically select the Start Automatically option for the iSCSI service on the TrueNAS system but does not. Administrator must manually selected in the TrueNAS system. | TBD | +| 2.3.2 | TC-2727 | Uploading or resetting certificates closes UI WS connection | Uploading or resetting certificates tries to write to a file and closes the UI websocket connection and generates an error code. The system tries but fails to add an error to the UI logs as the connection closes. The connection should not close during this event but should reconnect immediately. | TBD | +| 2.3.2 | TC-2726 | Renamed Groups appear as old name and not loading properly when editing | The Groups names do not load properly or show name changes. Clear the browser cache to update the screen and show changes. | TBD | +| 2.3.2 | TC-2706 | API error displays after Updating a NAS System with TrueCommand | An API error displays after logging into TrueCommand and using it to update a NAS system. | TBD | +| 2.3.2 | TC-2705 | Deleting a volume with the TC iSCSI Manager does not delete iSCSI Initiators Group | After deleting an iSCSI volume using TC iSCSI Manager does not delete the Initiator Group but does delete the rest of the iSCSI block share. | TBD | +| 2.3.0 | TC-2609 | Unable to recreate a cluster after removing the cluster | After removing a cluster, cannot to create a new cluster because the dropdown list does not populate all settings. This prevents configuring required settings. We recommend that you not delete your cluster until this is fixed. Underlying issue is identified and scheduled for the next release. | TBD | +| 2.3.0 | TC-2524 | Notices WebSocket test results are unstable | Most tests pass while some fail, but fails don't occur on the same test. Possible middleware issue. | Backlog | + +### Resolved Known Issues +{{< expand "Resolved Known Issues List" "v">}} +| Seen In | Resolved In | Key | Summary | Workaround | +|---------|-------------|-----|---------|------------| +| 2.3.2 | 2.3.1, 3.0 | TC-2719 | Launch TrueNAS Interface option on the System action list does not work | The Launch TrueNAS Interface on a system widget action list in TrueCommand, displays "This page is not working" instead of launching the connection to the TrueNAS UI. | +| 2.3.2 | 2.3.1, 3.0 | TC-2718 | After adding a system that is down, the UI doesn't show a system until an F5 Refresh | If adding an offline or down system to TrueCommand, the system does not show in the TrueCommand UI until you refresh the cache using F5. At that point the server displays on the list flagged as Offline. | +| 2.3.0 | 2.3.2 | TC-2533 | Hook in new servers/limit event sent when license limit is exceeded | This event replaces an error on servers/add, which instead sends max_disks and license_count if the license is executed, but not error. Any time a check fails the servers/limit event is sent as well, for asynchronous occurrences. | +| 2.3.0 | 2.3.0 | TC-2508 | Teams, systems and groups missing in User after migration from 2.2.2 to 2.3.0 | After migrating from 2.2.2. to 2.3.0, users no longer had Teams, Systems or system Groups assigned. The Teams and system groups are listed in the Systems/System Groups and Teams areas and no longer assigned under the User. | +{{< /expand >}} ## To Download this Release Login to the [TrueCommand Account Portal](https://portal.ixsystems.com) for downloads, documentation links, and licensing options. @@ -558,12 +620,9 @@ As a best practice, TrueCommand admins should backup their instance's data direc {{< hint warning >}} **Important Note for Upgrading from v1.3** -Updating from TrueCommand v1.3 to v2.0 or higher involves a database migration process. This preserves all configuration data, but does not preserve old performance statistics. +Updating from TrueCommand v1.3 to v2.0 or newer involves a database migration process. This preserves all configuration data, but does not preserve old performance statistics. Additionally, it is not possible to roll back to TrueCommand v1.3 from v2.1. Please use caution when upgrading production TrueCommand systems. If necessary, run TrueCommand 1.3 and TrueCommand 2.1 in parallel for a transition period. Simply use the "ixsystems/truecommand:1.3.2" docker image to continue using that specific version of TrueCommand. {{< /hint >}} **Docker:** Re-run `docker pull ixsystems/truecommand` to fetch the latest version of TrueCommand, and then restart your docker instance. - -**VM Image:** Either reboot the VM or run `systemctl restart truecommand.service`. -This will automatically fetch and start the latest Docker image of TrueCommand within your VM. - +**Cloud Deployments:** iXsystems coordinates a time when cloud based deployments update to the latest version. diff --git a/content/TrueCommand/iSCSIManagement.md b/content/TrueCommand/iSCSIManagement.md index 5c6b335ee2..d1bf5b7636 100644 --- a/content/TrueCommand/iSCSIManagement.md +++ b/content/TrueCommand/iSCSIManagement.md @@ -1,73 +1,105 @@ --- title: iSCSI Volume Management +description: "This article provide information on managing iSCSI block shares, iSCSI volumes in TrueCommand." weight: 70 +aliases: +tags: +- tciscsi +- coreiscsi +- scaleiscsi --- +{{< toc >}} + + {{< hint danger >}} -iSCSI management is a brand new feature in TrueCommand 2.0. Always back up any data intended for storage or sharing! {{< /hint >}} -Open the **iSCSI Manager** page by clicking the icon on the top bar. +{{< hint info >}} +TrueCommand 2.3.2 introduces changes to how iSCSI objects are cached. We no longer cache all objects which fixes timing issues between sync. +{{< /hint >}} + +Use the icon on the top toolbar to open the **iSCSI Manager** screen. ![iSCSIManagerPage](/images/TrueCommand/2.1/iSCSIManagerPage.png "iSCSI Manager Page") -Begin creating an iSCSI volume by clicking **+ Volume**. -After the **iSCSI Manager** page opens, click **+ Add System Pool** and select a pool or multiple pools. +## Adding an iSCSI Volume +You can create in iSCSI block share for a TrueNAS system and have that new volume display both in TrueCommand iSCSI Manager and on the TrueNAS system screen listing iSCSI block shares. + +To add a new iSCSI volume in TrueCommand from the **iSCSI Manager** screen: + +Click **+ Volume** to begin creating an iSCSI volume. +After the **iSCSI Manager** wizard opens on the **Systems/Portals** screen. -![iSCSISelect Pools](/images/TrueCommand/2.1/iSCSISelectPools.png "iSCSI Select Pools") +![iSCSICreateScreenSystemPortals](/images/TrueCommand/2.3.2/iSCSICreateScreenSystemPortals.png "Add Portal Screen") -Click **Next**. +Click on **Add System Pool**, then select a pool or multiple pools from the dropdown list. -Click **+ Block Devices** to add block devices. -The **Count** field creates a batch of ISCSI datastores with identical settings in the number specified. +![iSCSIWizardAddVolumeSelectPool](/images/TrueCommand/2.3.2/iSCSIWizardAddVolumeSelectPool.png "iSCSI Add Volume Portal Select Pools") -![iSCSICreateBlockDevice](/images/TrueCommand/2.1/iSCSICreateBlockDevice.png "iSCSI Create Block Device") +Click away from the list to close it. -Click **SAVE** when finished, and then click **NEXT**. +On the system field for the selected pool, select the IP address the portal the volume listens to from the **Port Bindings** dropdown list. +**0.0.0.0** listens on all IPv4 addresses, **::** listens on all IPV6 addresses, or select the IP address for the system to listen to only this address. -Click **+ Target** and name the target. +Select **CHAP Auth** to use this discovery authentication method and display the **CHAP User** and **CHAP Secret** fields. +If using this authentication, enter the required information. -![iSCSICreateTarget](/images/TrueCommand/2.1/iSCSICreateTarget.png "iSCSI Create Target") +Click **Next** to advance to the **Block Devices** screen, then click **+ Block Devices** to open the **Block Device Group** dialog. -Click **SAVE** when finished and then click **NEXT**. +![iSCSIWizardAddBlockDeviceGroup](/images/TrueCommand/2.3.2/iSCSIWizardAddBlockDeviceGroup.png "iSCSI Add Block Device Group") -Click the checkbox to assign the target to the block device. +To add a block device, enter a name, specify the number of iSCSI datastores you want to create, the size, zvol and logical block sizes for each. +Enter a number in **Count** to tell TrueCommand to create a batch of ISCSI datastores with identical settings for the number specified. -![iSCSIMapBlocks](/images/TrueCommand/2.1/iSCSIMapBlocks.png "iSCSI Map Blocks") +Select **Xen Support** if using Xen, a VM platform, as an initiator. +Select **xcopy Support** to enable allowing an initiator to bypass normal access control and access any scannable target when the TrueNAS system is running CORE, SCALE does not use this function. This allows xcopy operations otherwise blocked by access control. + +Click **SAVE**, then click **NEXT** to advance to the **Targets** screen. + +Click **+ Target** to open the **Target** dialog. + +![iSCSIWizardAddTargetDialog](/images/TrueCommand/2.3.2/iSCSIWizardAddTargetDialog.png "iSCSI Create Target") + +Enter a name for the target, then click **Save**. +Select the checkbox for the new target to to assign it to the block device listed above the target row and to +activate **Next**. + +![iSCSIWizardAddTargetSelectCheckbox](/images/TrueCommand/2.3.2/iSCSIWizardAddTargetSelectCheckbox.png "Map Target To Block") Click **NEXT**. -By default, TrueCommand grants target access to all initiators. -To change this, click **+ Initiator**. +By default, TrueCommand grants target access to all initiators. You can skip over creating an initiator or click **+ Initiator** to add one. Name the new initiator and click the checkbox to assign it to the target. -![iSCSICreateInitiator](/images/TrueCommand/2.1/iSCSICreateInitiator.png "iSCSICreateInitiator") +![iSCSIWizardAddInitiatorDialog](/images/TrueCommand/2.3.2/iSCSIWizardAddInitiatorDialog.png "iSCSI Create Initiator") Click **NEXT**. Review the configuration and click **Create**. -![iSCSIReview](/images/TrueCommand/2.1/iSCSIReview.png "iSCSIReview") +![iSCSIWizardReviewAndCreate](/images/TrueCommand/2.3.2/iSCSIWizardReviewAndCreate.png "iSCSI Review") -TrueCommand creates the iSCSI volume on the TrueNAS system and adds it to the iSCSI Manager. +TrueCommand creates the iSCSI volume on the TrueNAS system and adds it to the **iSCSI Manager**. -![iSCSIVolumeList](/images/TrueCommand/2.1/iSCSIVolumeList.png "iSCSIVolumeList") +![iSCSIManagerWithAddedVolume](/images/TrueCommand/2.3.2/iSCSIManagerWithAddedVolume.png "iSCSI Volume List") Using the TrueNAS web interface to update iSCSI settings takes approximately five minutes to resync with TrueCommand. #### Deleting a Share -To delete a block device, click the icon to open the options, select **Edit**, then click the icon in the pop-out panel. +To delete a block device, click the icon for the volume, then select **Block Devices** to open the list of block devices for the selected volume. -![iSCSIEdit](/images/TrueCommand/2.1/iSCSIEdit.png "iSCSIEdit") +Click the icon for the block device to open the action list. -![iSCSIDeleteBlockDeviceandzvol](/images/TrueCommand/2.0/iSCSIDeleteBlockDeviceandzvol.png "iSCSI Delete Block Device and zvol") +Click **Delete Block Device** to delete the block device and target or **Delete Block Device and zvol** to delete the block device, target, and associated zvol, which is a full clean-up in TrueCommand and the TrueNAS system. -To delete the target click the icon and select **Delete Target**. -To delete everything click the icon and select **Deleting Target and zvols** which is the full cleanup. +![DeleteBlockVolumeOptions](/images/TrueCommand/2.3.2/DeleteBlockVolumeOptions.png "Delete iSCSI Options") -![iSCSIDeleteTarget](/images/TrueCommand/2.1/iSCSIDeleteTarget.png "iSCSIDeleteTarget") +Select **Confirm** then **OK**. -TrueCommand cannot delete initiators and init groups because they might be tied to multiple targets. +TrueCommand cannot delete initiators and initiator groups because they might be tied to multiple targets. To remove these settings, delete them from each TrueNAS system. + +{{< taglist tag="tciscsi" limit="10" title="Related iSCSI Articles" >}} diff --git a/content/_includes/TrueCommandLDAP.md b/content/_includes/TrueCommandLDAP.md new file mode 100644 index 0000000000..21ca55050d --- /dev/null +++ b/content/_includes/TrueCommandLDAP.md @@ -0,0 +1,71 @@ +TrueCommand supports using [LDAP](https://tools.ietf.org/html/rfc4511) to better integrate within an established network environment. +*LDAP/AD* allows using single sign-on credentials from the [Lightweight Directory Access Protocol (LDAP)](https://tools.ietf.org/html/rfc4511) or [Active Directory (AD)](https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/active-directory-domain-services). +Users can log in with an LDAP or AD account without creating a separate TrueCommand login. + +LDAP and AD require the server IP address or DNS hostname and domain to use. +The LDAP or AD Username (optional) is required when the TrueCommand user name does not match the LDAP or AD credentials. + +Click on the **  (Gear) > Administration**. +Click **Add** on the **LDAP Servers** widget to open the **Add LDAP Server** configuration screen. + +![AdministrationLDAPServersWidget](/images/TrueCommand/2.3.2/AdministrationLDAPServersWidget.png "Administration Screen LDAP Servers Widget") + +To configure LDAP, type the LDAP server IP address or DNS host name into the **LDAP Server URL** field, type the domain name in the **Domain** field, and click **ADD SERVER**. +You can add multiple LDAP servers and domains. + +The **Test LDAP Config** icon opens a window that allows you to test your connection to the LDAP server. The **Remove LDAP Server** icon removes the selected LDAP server. + +![AddLDAPServerScreen](/images/TrueCommand/2.3.2/AddLDAPServerScreen.png "Add LDAP Server") + +| Setting | Description | +|---------|-------------| +| **Hostname** | (Required) Enter the host name, IP or DNS name, of the LDAP server, with port number on the end. For example: *ldap.mycorp.com:636* (SSL port is typically 636 for AD/LDAP). | +| **Domain** | (Required) Base domain settings of the user. For example: dc=mycorp,dc=com for a typical `username@mycorp.com` user account. | +| **Group Domain** | Enter the alternative domain setting to use when searching for groups. The default value is the same as **Domain**. | +| **Verify SSL** | Select to require strict SSL certificate verification. The default value is false. Disable this option if the system host name is not the one on the SSL certificate, the system uses an IP to connect instead of the DNS host name, or the LDAP server uses a self-signed certificate. | +| **User ID Field** | Enter the user ID for the user that logs in (this is class-matched to the login username). Enter **Domain** name to use for user-matching. The default value is **uid** (user ID). Another commonly-used field is **cn** (common name). | +| **Group ID Field** | Enter the class for finding groups associated with a user. The default is cn (common name). Enter the **Domain** name to use when searching for a group name. | +| **BIND User Domain** | Enter the full domain setting for a pre-authenticated bind to the server. For example: uid=binduser,cn=read-only-bind,dc=mycorp,dc=com. For an unauthenticated bind, enter just a name (example: truecommand-bin). This is sometimes used for logging purposes on the LDAP but otherwise is not validated. | +| **Realm** | Enter the realm that performs authentication against the LDAP server. | +| **BIND Password** | Enter the password to use for the bind user. For an unauthenticated bind, leave blank while setting the **BIND User Domain** to a non-empty value. | +| **KDC** | Enter the key distribution center (KDC) that supplies session tickets and temporary session keys to users and computers within the LDAP server. | + +### LDAP connection options + +TrueCommand supports two methods of validating LDAP user credentials: + +#### Direct Bind +The direct BIND method uses the **Domain** and **User ID Field** values to create a static domain string for user authentication. + +Example: + +* Domain: *dc=mycorp,dc=com* +* User ID Field: *uid* + +When *bobby.singer* attempts to log in, TrueCommand establishes an SSL-secure connection to the LDAP server and attempts to bind with the static domain *uid=bobby.singer,dc=mycorp,dc=com* and the user-provided password. If successful, the user authentication verifies, and Bobby Singer may access TrueCommand. + +#### Indirect Bind +The indirect BIND authentication method is more dynamic and searches for the proper user domain settings rather than making format assumptions. +With TrueCommand, indirect BIND configures a *bind user* (typically a read-only, minimal-permissions user account) with a known domain/password to perform the initial bind to the LDAP server. +After logging in, TrueCommand searches for the user domain requesting to log in. It then attempts a second bind with the user domain and provided password. + +Example: + +* Domain: *dc=mycorp,dc=com* +* User ID Field: *uid* +* BIND User Domain: *uid=binduser,cn=read-only-bind,dc=mycorp,dc=com* +* BIND Password: *pre-shared-key* + +When *bobby.singer* attempts to log in, TrueCommand establishes an SSL-secure connection to the LDAP server. TrueCommand uses the **BIND User Domain** and **BIND Password** settings to perform an initial bind using pre-known settings from your LDAP provider. Once bound, TrueCommand searches for the user matching *uid=bobby.singer*, but only within the subdomains that include the domain setting (*dc=mycorp,dc=com* in this example). If TrueCommand finds a user, it uses the entire user domain string from the search result to initialize a second bind along with the user-provided password. If successful, TrueCommand verifies the user authentication, and Bobby Singer is allowed access to TrueCommand. + +### SSL/TLS Connection Info + +**WARNING:** AD/LDAP authentication *requires* SSL connections. + +If the LDAP server uses an SSL certificate generated by a custom certificate authority (CA), then one of two things must occur before TrueCommand can use the LDAP server: + +* (Option 1) Users must register the custom certificate authority with TrueCommand via the **Certificates** tab on the **Administration** screen. +* (Option 2) Users can disable the **Verify SSL** option to accept whatever SSL certificate the server provides. Users might need to choose Option 2 if the LDAP server hostname differs from the one listed on the certificate or if the server uses a self-signed SSL certificate. + +Selecting **Allow LDAP user creation** means TrueCommand creates user accounts when someone logs in to the User Interface with their LDAP credentials. +**JOIN TEAM** automatically adds LDAP users to specific TrueCommand teams. \ No newline at end of file diff --git a/static/images/TrueCommand/2.3.2/AddLDAPServerScreen.png b/static/images/TrueCommand/2.3.2/AddLDAPServerScreen.png new file mode 100644 index 0000000000..d5729a80b2 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/AddLDAPServerScreen.png differ diff --git a/static/images/TrueCommand/2.3.2/AddRecipientScreen.png b/static/images/TrueCommand/2.3.2/AddRecipientScreen.png new file mode 100644 index 0000000000..e582e10383 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/AddRecipientScreen.png differ diff --git a/static/images/TrueCommand/2.3.2/AdministrationAlertRecipientsWidget.png b/static/images/TrueCommand/2.3.2/AdministrationAlertRecipientsWidget.png new file mode 100644 index 0000000000..d8c352b66e Binary files /dev/null and b/static/images/TrueCommand/2.3.2/AdministrationAlertRecipientsWidget.png differ diff --git a/static/images/TrueCommand/2.3.2/AdministrationCertificateAuthoritiesWidget.png b/static/images/TrueCommand/2.3.2/AdministrationCertificateAuthoritiesWidget.png new file mode 100644 index 0000000000..b6b64a0d02 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/AdministrationCertificateAuthoritiesWidget.png differ diff --git a/static/images/TrueCommand/2.3.2/AdministrationCertificatesWidget.png b/static/images/TrueCommand/2.3.2/AdministrationCertificatesWidget.png new file mode 100644 index 0000000000..ba0c56fb65 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/AdministrationCertificatesWidget.png differ diff --git a/static/images/TrueCommand/2.3.2/AdministrationConfigurationWidget.png b/static/images/TrueCommand/2.3.2/AdministrationConfigurationWidget.png new file mode 100644 index 0000000000..8afee08a3b Binary files /dev/null and b/static/images/TrueCommand/2.3.2/AdministrationConfigurationWidget.png differ diff --git a/static/images/TrueCommand/2.3.2/AdministrationLDAPServersWidget.png b/static/images/TrueCommand/2.3.2/AdministrationLDAPServersWidget.png new file mode 100644 index 0000000000..4524c9177a Binary files /dev/null and b/static/images/TrueCommand/2.3.2/AdministrationLDAPServersWidget.png differ diff --git a/static/images/TrueCommand/2.3.2/AlertServiceSMTPEmailScreen.png b/static/images/TrueCommand/2.3.2/AlertServiceSMTPEmailScreen.png new file mode 100644 index 0000000000..3f0ff38e5e Binary files /dev/null and b/static/images/TrueCommand/2.3.2/AlertServiceSMTPEmailScreen.png differ diff --git a/static/images/TrueCommand/2.3.2/ConfigurationScreenGeneralSSLAlertOptions.png b/static/images/TrueCommand/2.3.2/ConfigurationScreenGeneralSSLAlertOptions.png new file mode 100644 index 0000000000..701d9905e3 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/ConfigurationScreenGeneralSSLAlertOptions.png differ diff --git a/static/images/TrueCommand/2.3.2/ConfigurationScreenSSLOptions.png b/static/images/TrueCommand/2.3.2/ConfigurationScreenSSLOptions.png new file mode 100644 index 0000000000..f8d60738b9 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/ConfigurationScreenSSLOptions.png differ diff --git a/static/images/TrueCommand/2.3.2/CreateSnapshotButtons.png b/static/images/TrueCommand/2.3.2/CreateSnapshotButtons.png new file mode 100644 index 0000000000..5b57fcae9f Binary files /dev/null and b/static/images/TrueCommand/2.3.2/CreateSnapshotButtons.png differ diff --git a/static/images/TrueCommand/2.3.2/CreateSnapshotDialog.png b/static/images/TrueCommand/2.3.2/CreateSnapshotDialog.png new file mode 100644 index 0000000000..446850d643 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/CreateSnapshotDialog.png differ diff --git a/static/images/TrueCommand/2.3.2/CreateSnapshotTaskDataset.png b/static/images/TrueCommand/2.3.2/CreateSnapshotTaskDataset.png new file mode 100644 index 0000000000..66594ed24a Binary files /dev/null and b/static/images/TrueCommand/2.3.2/CreateSnapshotTaskDataset.png differ diff --git a/static/images/TrueCommand/2.3.2/CreateSnapshotTaskScheduleAndLifetime.png b/static/images/TrueCommand/2.3.2/CreateSnapshotTaskScheduleAndLifetime.png new file mode 100644 index 0000000000..2f34bcb3ce Binary files /dev/null and b/static/images/TrueCommand/2.3.2/CreateSnapshotTaskScheduleAndLifetime.png differ diff --git a/static/images/TrueCommand/2.3.2/CreateSnapshotsOptions.png b/static/images/TrueCommand/2.3.2/CreateSnapshotsOptions.png new file mode 100644 index 0000000000..a8638a15d0 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/CreateSnapshotsOptions.png differ diff --git a/static/images/TrueCommand/2.3.2/DeleteBlockVolumeOptions.png b/static/images/TrueCommand/2.3.2/DeleteBlockVolumeOptions.png new file mode 100644 index 0000000000..df7b31e541 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/DeleteBlockVolumeOptions.png differ diff --git a/static/images/TrueCommand/2.3.2/ExploreSystemDatasetSnapshotList.png b/static/images/TrueCommand/2.3.2/ExploreSystemDatasetSnapshotList.png new file mode 100644 index 0000000000..827af48db0 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/ExploreSystemDatasetSnapshotList.png differ diff --git a/static/images/TrueCommand/2.3.2/ExploreSystemSelectPool.png b/static/images/TrueCommand/2.3.2/ExploreSystemSelectPool.png new file mode 100644 index 0000000000..226def9e6b Binary files /dev/null and b/static/images/TrueCommand/2.3.2/ExploreSystemSelectPool.png differ diff --git a/static/images/TrueCommand/2.3.2/MailingListConfigureScreen.png b/static/images/TrueCommand/2.3.2/MailingListConfigureScreen.png new file mode 100644 index 0000000000..396855a804 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/MailingListConfigureScreen.png differ diff --git a/static/images/TrueCommand/2.3.2/MainDashboardSelectUngroupedSystem.png b/static/images/TrueCommand/2.3.2/MainDashboardSelectUngroupedSystem.png new file mode 100644 index 0000000000..77c0762482 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/MainDashboardSelectUngroupedSystem.png differ diff --git a/static/images/TrueCommand/2.3.2/SystemInformationCardDetails.png b/static/images/TrueCommand/2.3.2/SystemInformationCardDetails.png new file mode 100644 index 0000000000..f4ab225caa Binary files /dev/null and b/static/images/TrueCommand/2.3.2/SystemInformationCardDetails.png differ diff --git a/static/images/TrueCommand/2.3.2/SystemUpdateAvailable.png b/static/images/TrueCommand/2.3.2/SystemUpdateAvailable.png new file mode 100644 index 0000000000..b318978411 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/SystemUpdateAvailable.png differ diff --git a/static/images/TrueCommand/2.3.2/iSCSICreateScreenSystemPortals.png b/static/images/TrueCommand/2.3.2/iSCSICreateScreenSystemPortals.png new file mode 100644 index 0000000000..a656cf7a3e Binary files /dev/null and b/static/images/TrueCommand/2.3.2/iSCSICreateScreenSystemPortals.png differ diff --git a/static/images/TrueCommand/2.3.2/iSCSIManagerWithAddedVolume.png b/static/images/TrueCommand/2.3.2/iSCSIManagerWithAddedVolume.png new file mode 100644 index 0000000000..11922ea242 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/iSCSIManagerWithAddedVolume.png differ diff --git a/static/images/TrueCommand/2.3.2/iSCSIWizardAddBlockDeviceGroup.png b/static/images/TrueCommand/2.3.2/iSCSIWizardAddBlockDeviceGroup.png new file mode 100644 index 0000000000..64d5062624 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/iSCSIWizardAddBlockDeviceGroup.png differ diff --git a/static/images/TrueCommand/2.3.2/iSCSIWizardAddInitiatorDialog.png b/static/images/TrueCommand/2.3.2/iSCSIWizardAddInitiatorDialog.png new file mode 100644 index 0000000000..f8ff002227 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/iSCSIWizardAddInitiatorDialog.png differ diff --git a/static/images/TrueCommand/2.3.2/iSCSIWizardAddTargetDialog.png b/static/images/TrueCommand/2.3.2/iSCSIWizardAddTargetDialog.png new file mode 100644 index 0000000000..c7b50e40af Binary files /dev/null and b/static/images/TrueCommand/2.3.2/iSCSIWizardAddTargetDialog.png differ diff --git a/static/images/TrueCommand/2.3.2/iSCSIWizardAddTargetSelectCheckbox.png b/static/images/TrueCommand/2.3.2/iSCSIWizardAddTargetSelectCheckbox.png new file mode 100644 index 0000000000..5897683ae7 Binary files /dev/null and b/static/images/TrueCommand/2.3.2/iSCSIWizardAddTargetSelectCheckbox.png differ diff --git a/static/images/TrueCommand/2.3.2/iSCSIWizardAddVolumeSelectPool.png b/static/images/TrueCommand/2.3.2/iSCSIWizardAddVolumeSelectPool.png new file mode 100644 index 0000000000..e0a453824f Binary files /dev/null and b/static/images/TrueCommand/2.3.2/iSCSIWizardAddVolumeSelectPool.png differ diff --git a/static/images/TrueCommand/2.3.2/iSCSIWizardReviewAndCreate.png b/static/images/TrueCommand/2.3.2/iSCSIWizardReviewAndCreate.png new file mode 100644 index 0000000000..00e525666b Binary files /dev/null and b/static/images/TrueCommand/2.3.2/iSCSIWizardReviewAndCreate.png differ diff --git a/static/includes/TrueCommand/2.0/TrueCommandSSL.md.part b/static/includes/TrueCommand/2.0/TrueCommandSSL.md.part index cd621fb92a..73543a3f4d 100644 --- a/static/includes/TrueCommand/2.0/TrueCommandSSL.md.part +++ b/static/includes/TrueCommand/2.0/TrueCommandSSL.md.part @@ -3,7 +3,7 @@ By default, TrueCommand attempts an SSL connection, then a non-SSL connection if You can disable non-SSL connection attempts by setting **Require SSL for all connections**, which is useful when a monitored system uses a custom port or does not allow SSL-secured access. There are additional options to configure how TrueCommand handles certificates. -By default, TrueCommand accepts self-signed certificates and certificate hostname mismatches. -Self-signed certificates enable the first-time login to TrueCommand. Certificate hostname mismatches let TrueCommand accept certificates from systems that use a hostname, even though it registered them with an IP address (or vice-versa). +By default, TrueCommand accepts self-signed certificates and certificate host name mismatches. +Self-signed certificates enable the first-time login to TrueCommand. **Accept certificate even if there is a hostname mismatch** allows TrueCommand to accept certificates from systems that use a host name, even though it registered them with an IP address (or vice-versa). -![Configure SSL](/images/TrueCommand/2.0/AdministrationConfigurationSSL.png "Configure SSL") \ No newline at end of file +![ConfigurationScreenSSLOptions](/images/TrueCommand/2.3.2/ConfigurationScreenSSLOptions.png "Configuration Screen SSL Options") \ No newline at end of file diff --git a/words-to-ignore.txt b/words-to-ignore.txt index 176be38d23..5579d3d5e9 100644 --- a/words-to-ignore.txt +++ b/words-to-ignore.txt @@ -1169,6 +1169,27 @@ Gbs Gbps GBs GBps +IDP-initiated +IDP +repo +multisystem +brainpool +Golang +uid +cn +pre-authenticated +binduser +pre-shared-key +mycorp +pre-known +ldap +Xen +scannable +tciscsi +coreiscsi +scaleiscsi +xcopy +blocksize corezfs scalezfs pre-failover