Searching: firmware - 177 Results Found

VTrak D5000 Best Practices for VMware for VTrak D5000 and Vess R3000
Babatunde Akinkuolie posted this 31 October 2024 - Last edited 31 October 2024

This guide provides best practices for utilizing D5000/R3000 with VMware ESXi version 5 or higher. The following topics will be covered in this article: RAID Levels, Expansion Chassis, LUN Affinity, ALUA and VAAI Support

RAID: RAID stands for Redundant Array of Independent Disks. When it comes to VMware usage, we recommend using one of the two RAID configurations mentioned below:

  • RAID 5 (Stripe with Parity): This configuration offers optimal read/write speeds with less overhead, resulting in superior performance.
  • RAID 6 (Stripe with Dual Parity): This configuration is ideal for Archival Storage, providing dual redundancy and superior fault tolerance.

RAID 0 (Stripe): It is not recommended to use a stripe volume as it offers little performance benefit and does not provide any fault tolerance for the volume.

J3000/J5000 Expansion Chassis: If you have an expansion chassis connected to your VTrak D5000 and Vess R3000 unit, you have the option to increase storage capacity for your VM configuration. However, it is not recommended to span enclosures and create a single large RAID array volume using the RAID Engine.

For optimal performance, it is recommended to have each enclosure contain separate disk arrays. RAID configurations spanning enclosures will require either RAID 50 or RAID 60.

LUN Affinity: To optimize performance, it is recommended to enable LUN Affinity for Dual controller in VTrak D5000 and Vess R3000 units. Enabling LUN Affinity improves write performance and enhances stability. While VMware has been certified with LUN Affinity disabled, Promise Technology recommends enabling it for the best performance.

ALUA: ALUA, which stands for Asynchronous Logical Unit Access, must be enabled for VMware optimization. VMware 5x and higher are ALUA aware, and it is recommended to have this feature enabled for improved overall performance on the unit.

VAAI (VMware API Array Integration): VAAI is a VMware special configuration API that allows offloading of certain storage tasks from the ESXi server to the storage array. It is also referred to as hardware acceleration.

The latest firmware versions for both VTrak/Vess storage units offer VAAI support, which can be enabled or disabled. Since VAAI is specific to VMware, only VMware systems make use of this feature.

To enable the VAAI feature on the VTrak D5000 and Vess R3000, you may use the WEBPAM PROe GUI or the Command Line Interface (CLI).

VTrak D5000 and Vess R3000 Configuration Details

1.1. Enable VTrak D5000 and Vess R3000 VAAI Function

      1.1.1 Use the CLI mode to enable VAAI function in D5000/R3000

 A. SSH/Console go to controller CLI and login(administrator/password)

 B. Check controller1 VAAI function status -> ctrl –v –i 1

      Check controller2 VAAI function status -> ctrl –v –i 2

  •  Check controller1 & controller2 -> ctrl -v

 C. Controller list information “VAAIsupport” default is disabled.

                  ->VAAIsupport=disabled  

 D. Enable controller1 VAAIsupport -> ctrl –a mod –s “vaaisupport=enable”

 E. Check controller1 VAAI function status -> ctrl –v –i 1.

      Check controller2 VAAI function status-> ctrl –v –i 2

1.1.2 Use the GUI to enable VAAI function in D5000/R3000

       A.  Login to Web-GUI (administrator/password)

       B.  In “HOME” page, click following step to go to the VAAI setup page:

  • Click “Device”
  • Click “Component List”.
  • In “Component List”, select the controller ID=1 (or ID=2).

                       Click the setup button and slect “Settings”.

    C. In “Controller Setting” page, click as following step to enable the VAAI function :

  • Select the “Enable VAAI” and enable the checkbox.
  • Click “SAVE” button

2.1 Disable VTrak D5000 and Vess R3000 VAAI

  • Note: If the datastore is using ATS-only locking, please refer to KB article to disable the ATS-only flag.

 https://kb.promise.com/thread/disable-vmware-ats-only-flag-in-d5000-r3000/

2.1.1 Use the CLI mode to enable VAAI function in D5000/R3000

  A. SSH/Console enter controller CLI and login (administrator/password)

  B. Check controller1 status -> ctrl –v –i 1

      Check controller2 status -> ctrl –v –i 2

       Check controller1 & controller2 -> ctrl -v

    C. Controller list information “VAAIsupport” is enabled.

  • VAAIsupport=enabled

    D. Disable controller1 VAAIsupport -> ctrl –a mod –s “vaaisupport=disable”

    E.  Check controller1 VAAI function status ->  ctrl –v –i 1

          Check controller2 VAAI function status -> ctrl –v –i 2

2.1.2 Use the GUI to disable VAAI function in D5000/R3000

  A. Login to Web-GUI (administrator/password)

  B. In “HOME” page, click following step to go to the VAAI setup page:

  • Click “Device”
  • Click “Component List”.
  • In “Component List”, select the controller ID=1 (or ID=2).

                       Click the setup button and slect “Settings”.

 

    C. In “Controller Setting” page, click as following step to enable the VAAI function :

  1. Select the “Enable VAAI” and enable the checkbox.
  2. Click “SAVE” button.

Thunderbolt™ Pegasus Family Guide to using legacy and modern Pegasus storage.
Babatunde Akinkuolie posted this 30 October 2024 - Last edited 30 October 2024

IMPORTANT NOTE: The M1 macOS does not include a Pegasus Driver, a Pegasus driver must be installed on all M1 Macs, preferably the DEXT (user space) driver.

The Pegasus line has been evolving for over a decade.

Model Year Macos
Pegasus 1  2011 Lion
  2012 Mountain Lion
  2013 Mavericks
Pegasus 2 2014 Yosemite
  2015 El Capitan
Pegasus 3 2016 Sierra
  2017 High Sierra
  2018 Mojave
  2019 Catalina
Pegasus 32 2020 Big Sur
  2021 Monterey
Promise M4 (SSD)   2022 Ventura
  2023 Sonoma
  2024 Sequoia


During this time macOS has evolved from OS X Lion to macOS Ventura and soon Sonoma.

Windows 7 was primarily used in 2011 but many still used XP. Windows 11 is the current Windows version and support for Windows 10 will be ending in 2025.

Thinderbolt has evolved from Thunderbolt 1 to Thunderbolt 4.

Hard drives were from 1TB to 2TB in 2011, today drives of over 20TB are available with 30TB drives announced for the future.

In 2011 SSDs were a curiosity, slow with low capacity. Today SSDs are reliable, fast and have taken over as boot disks.

Much has changed over the decade. And using a device from 2011 like the Pegasus 1 is complicated by all these changes.

Here are some basic rules.

  • For any legacy Pegasus device, please update to the last firmware released for that Pegasus. Firmware from other generations of Pegasus cannot not be used.
  • Drivers and the Promise Utility from the shipping Promise Pegasus should be used, today that means the Pegasus32. Drivers written for macOS High Sierra won't work in M1 Ventura. Promise drivers are backwards compatible. The Pegasus32 Promise Utility is backwards compatible. The Promise Utility Pro has limited backwards compatibility.
  • Drivers and the Promise Utility are backwards compatible, but they are not forward compatible. When an older macOS like Mojave is used, the latest Pegasus32 driver and Promise Utility probably will not work due to changes in macOS. The suggestion is to use the drivers and Promise Utility that were released in the same timeframe as the macOS. The article beginning shows the timeframes of macOS and the Pegasus line.

----

For a Pegasus 1 with a modern macOS.

Use the latest Pegasus 1 firmware v5.04.000061

There is a KB on updating firmware on the Pegasus 1 and Pegasus 2

Use the latest Pegasus32 driver. For Intel macOS, the driver is builtin. For M1 macOS use the DEXT driver v21.1.0-2

Do not use the latest Promise Utility, use a slightly older version v4.06.0000.01

----

For a Pegasus 2 with a modern macOS.

Use the latest Pegasus 2 firmware v5.04.0000.64

There is a KB on updating firmware on the Pegasus 1 and Pegasus 2

Use the latest Pegasus32 driver. For Intel macOS, the driver is builtin. For M1 macOS use the DEXT driver v21.1.0-2

Do not use the latest Promise Utility, use a slightly older version v4.06.0000.01

----

For a Pegasus 3 with a modern macOS.

Use the latest Pegasus 3 firmware v6.06.0000.45

Use the latest Pegasus32 driver. For Intel macOS, the driver is builtin. For M1 macOS use the DEXT driver v21.1.0-2

Use the latest Promise Utility, v4.06.0000.04

----

For the Pegasus 32 and Pegasus M4 with a modern macOS.

Use the latest Pegasus 32 firmware v6.06.0000.45

Use the latest Pegasus32 driver. For Intel macOS, the driver is builtin. For M1 macOS use the DEXT driver v21.1.0-2

Use the latest Promise Utility, v4.06.0000.04

----

Note: M1 is an architecture (actually ARM architechure), M2 and M3 are the next generations of Apple Silicon, but they use the same M1 architechure, an M1 driver will work with an M2 or M3.

Close