VTrak Ex30 Articles

Visual comparison of AAMUX adapter and SAS-to-SATA adapter for VTrak X30 series

2015-10-05T16:13:37.0000000

When using a SATA or SSD drivein a VTrak Ex30 or Jx30 system, an adapter is required.

Most systems with SATA or SSD drives installed will use the SAS-to-SATA adapter.

Some early systems have the AAMUX adapter installed.

They can be easily identified by visual inspection.

Note - The SAS-to-SATA adapter may be referred to by its development code name; the Blackjack adapter.

VTrak Ex30 Series Single Controller - LED Activity for Empty Drive Bay

2015-03-24T15:53:52.0000000

Promise has identified a cosmetic facet in our VTrak Ex30 series if deployed with single controllers and partially populated bays. If any of the drive bays are left unpopulated, the indicator LEDs for these bays will blink intermittently. These indicators are supposed to be off (unlit) if there are no drives in the associated bays. The issue is completely cosmetic and is not associated with any functionality or stability problems.

Note that this ONLY happens when running with a single controller in our E- Class RAID head system (does not impact expansion chassis).

Event logging, snmp and email notification are fully functional.

Promise recommends to monitor and manage the enclosure via WebPam Pro or CLI (Command Line Interface).

VTrak Ex30 LDAP User Management – Active Directory

2014-01-09T16:35:50.0000000

This document will explain how to set up user access management for a VTrak Ex30 subsystem.

It is assumed that you have a functional MS Active Directory domain configured and administrative access to the domain controller.

Begin by logging in to the Vtrak's management interface GUI as administrator.
Select the Administration tab at the top-right, and select the User Management option.
Click the LDAP Settings button.

Here is an example using a domain called dixdomain.local.
Set the Base DN appropriately for your domain.
Set the Server Type for Windows Active Directory, and enter the LDAP server IP address.
You can use the Anonymous Bind option, but if your server does not support that you will have to create a dummy domain user for access.

Dummy Domain User

From the Server Manager, go to the Active Directory Users and Computers panel.
Add a New User and name it appropriately – this example uses VTrak LDAP.
Make it a member of Domain Users.

Use the Test button on the VTrak LDAP Settings page to verify the connection.

LDAP Role Mapping

Creating Security Groups and Adding Members

If your domain contains many users, and you want to easily control who has access to the VTrak and what privileges they have, you can create some security groups, then selectively edits users, giving them membership in the appropriate group.

For example, our domain has two users name 'dick' and 'dickey', and we want the first to have administrative – or Super – privileges, and the second to have only maintenance privileges.

From the Active Directory Users and Computers panel, create two new Security Groups – VTrakAdmin and VTrakMaint. They do not have to be members of any domain groups.

Now you can edit the two users, making them a member of the appropriate group.

'dick' is now a member of Group 'VTrakAdmin' and 'dickey' is now a member of Group 'VTrakMaint'.

Creating the LDAP Roles

From the LDAP Settings page click the Role Mapping button, and then the Add Role Mapping button.
Click the LDAP Role drop-down menu and scroll to the bottom. If you have configured the LDAP settings correctly – and the Test succeeded – you will see that the two new Security Groups we added are now visible. Select VTrakAdmin.

From the Subsystem Privilege drop-down, select the Super option.

Click the Submit button.
Repeat the process for the VTrakMaint role, giving it Maintenance privileges, then Submit.
Now they should be added to the LDAP-Role to Subsystem-Privilege Mapping table.

Test User Access

Now you can test the VTrak subsystem privileges each user has.

First, log in to the VTrak management GUI as the user 'dick'.
Click on the Administration tab and note that all of the options are available to this user.

Log out and log back in as the user 'dickey'.

Click on the Administration tab.
Note that not all of the Administration options are available for this user’s privilege level.

MPIO Configuration for VMware ESXi

2013-12-13T13:33:04.0000000

In ESXi, the MPIO driver sets the default "Active/Optimized" to storage controller 1 and "Standy" to storage controller 2 when ALUA/LunAffinity are enabled on the controllers.

The above settings can easily be changed so that the "Active/Optimized" is default to storage controller 2 and "Standby" default to storage controller 1 for any individual LUN. The objective is to balance the access to the LUNs across both controllers for better performance.

For example, in a case where the "Active/Optimized" is set to storage controller 2, and "Standby" is set to storage controller 1 for LUN A, only I/Os accessing LUN A are passing through storage controller 2. Vise versa is also true for say LUN B..

Steps to assign "Active/Optimized" and "Standby" for any LUN.

NOTE: You need to know the respective WWPN of the host HBA ports and Storage WWNN.. These can be looked up through Promise CLI or Promise WebPam GUI.

Open vCenter Sever and select the appropriate HBA as indicated below:
Select a LUN as indicated above by right click on it and select "Manage Paths" as indicated below.
Then select which prefered path the to set this LUN to (storage controller 1 or storage controller 2) Note: Make sure that the LUN policy is set to "Fixed (VMware)" as indicated below.

CLI output of Logdrv -v before making changes:

-------------------------------------------------------------------------------

LdId: 66

ArrayId: 4 SYNCed: Yes

OperationalStatus: OK

Alias:

SerialNo: 495345200000000000000000E2BE857E74045600

WWN: 22b3-0001-55f2-763b PreferredCtrlId: 1

RAIDLevel: RAID0 StripeSize: 64 KB

Capacity: 249.49 GB PhysicalCapacity: 249.49 GB

ReadPolicy: ReadAhead WritePolicy: WriteBack

CurrentWritePolicy: WriteThru

NumOfUsedPD: 1 NumOfAxles: 1

SectorSize: 512 Bytes RAID5&6Algorithm: N/A

TolerableNumOfDeadDrivesPerAxle: 0 ParityPace: N/A

Raid6Scheme: N/A

HostAccessibility: Normal

ALUAAccessStateForCtrl1: Active/optimized

ALUAAccessStateForCtrl2: Standby

AssociationState: no association on this logical drive

StorageServiceStatus: no storage service running

-------------------------------------------------------------------------------

LdId: 67

ArrayId: 4 SYNCed: Yes

OperationalStatus: OK

Alias:

SerialNo: 4953452000000000000000000A987EF44E93A434

WWN: 2284-0001-55f3-b451 PreferredCtrlId: 2

RAIDLevel: RAID0 StripeSize: 64 KB

Capacity: 249.49 GB PhysicalCapacity: 249.49 GB

ReadPolicy: ReadAhead WritePolicy: WriteBack

CurrentWritePolicy: WriteThru

NumOfUsedPD: 1 NumOfAxles: 1

SectorSize: 512 Bytes RAID5&6Algorithm: N/A

TolerableNumOfDeadDrivesPerAxle: 0 ParityPace: N/A

Raid6Scheme: N/A

HostAccessibility: Normal

ALUAAccessStateForCtrl1: Active/optimized

ALUAAccessStateForCtrl2: Standby

AssociationState: no association on this logical drive

StorageServiceStatus: no storage service running

CLI output of Logdrv -v after balancing the LUNs:

-----------------------------------------------------------------------------

LdId: 66

ArrayId: 4 SYNCed: Yes

OperationalStatus: OK

Alias:

SerialNo: 495345200000000000000000E2BE857E74045600

WWN: 22b3-0001-55f2-763b PreferredCtrlId: 1

RAIDLevel: RAID0 StripeSize: 64 KB

Capacity: 249.49 GB PhysicalCapacity: 249.49 GB

ReadPolicy: ReadAhead WritePolicy: WriteBack

CurrentWritePolicy: WriteThru

NumOfUsedPD: 1 NumOfAxles: 1

SectorSize: 512 Bytes RAID5&6Algorithm: N/A

TolerableNumOfDeadDrivesPerAxle: 0 ParityPace: N/A

Raid6Scheme: N/A

HostAccessibility: Normal

ALUAAccessStateForCtrl1: Standby

ALUAAccessStateForCtrl2: Active/optimized

AssociationState: no association on this logical drive

StorageServiceStatus: no storage service running

-------------------------------------------------------------------------------

LdId: 67

ArrayId: 4 SYNCed: Yes

OperationalStatus: OK

Alias:

SerialNo: 4953452000000000000000000A987EF44E93A434

WWN: 2284-0001-55f3-b451 PreferredCtrlId: 2

RAIDLevel: RAID0 StripeSize: 64 KB

Capacity: 249.49 GB PhysicalCapacity: 249.49 GB

ReadPolicy: ReadAhead WritePolicy: WriteBack

CurrentWritePolicy: WriteThru

NumOfUsedPD: 1 NumOfAxles: 1

SectorSize: 512 Bytes RAID5&6Algorithm: N/A

TolerableNumOfDeadDrivesPerAxle: 0 ParityPace: N/A

Raid6Scheme: N/A

HostAccessibility: Normal

ALUAAccessStateForCtrl1: Active/optimized

ALUAAccessStateForCtrl2: Standby

AssociationState: no association on this logical drive

StorageServiceStatus: no storage service running

-------------------------------------------------------------------------------

Firmware Update for VTrak x30 series for enhanced compatiblity for Intel 320 series SSD drives

2012-08-29T17:09:17.0000000

The VTrak X30 family products require an updated firmware for use with some models from the Intel 320 SSD series of drives.

These models require an updated firmware:

Intel 320 SSD Series
Model	Capacity
SSDSA2CW600G3 SSDSA2CW160G3 SSDSA2CW120G3 SSDSA2CW080G3	600GB 160GB 120GB 80GB

This model does not require the update:

Intel 320 SSD Series
Model	Capacity
SSDSA2CW300G3	300GB

For the VTrak X30 for Mac, please use this firmware update: X30_Mac_Intel_SSD_SR3.zip

For the VTrak X30 standard channel release, please use this firmware update: X30_Channel_Intel_SSD_SR3.zip

Please make note of your VTrak model. Loading the incorrect firmware will put the VTrak controllers offline and will require flashing with the correct firmware to bring the VTrak controllers back online.

How do I save a system Service Report on the VTrak Ex30?

2012-08-13T14:09:47.0000000

If there is ever an issue with your VTrak Ex30 family product, if possible, please save a system Service Report before restarting your VTrak.

To Save the system Service Report:

1. Please log into WebPAM PROe.

2. Click on the Save Service Report link at the top of the VTrak's WebPAM PROe management window.

3. The VTrak will generate the system Service Report. Depending on your browser's configuration, you may be prompted where to save the file, or the file may be automatically saved to your downloads folder.

3. If the report is saved in your downloads folder, please navigate to your download folder to find the ServiceRerport file. Please note this file is password protected for security. Be sure to provide the full .zip archive file to support for any service.

Max number of events supported NVRAM and RunTime Vtrak Ex30 series

2012-01-27T16:27:01.0000000

For run-time events: 1023 events
For NVRAM events: 1024 events

How many hard disk drives or expansion chassis can the Ex30 support?

2011-05-25T14:12:04.0000000

The Promise VTrak Ex30 series with firmware v4.02.0000.00 and newer can support up to 7 additional VTrak Jx30 series expansion chassis.

With one 4U, 24 bay VTrak Ex30 RAID head, and 7 of the 4U, 24 bay VTrak Jx30 expansion chassis installed, you can support up to 192 physical hard disk drives.

example: (One Ex30 + Seven Jx30) x 24 drives per chassis = 192 drives

Firmware updates for the VTrak Ex30 series can be found in the Promise Technology Download Center. Always keep firmware up to date. Please update to the latest firmware whenever available.

- Note - Only hard disk drives qualified by Promise Technology are supported with the VTrak subsystem family. Other hard disk drives may be unreliable and are not supported.

Please go to the Promise Technology Download Center to find the latest supported hard drive compatibility lists for all Promise Technology products.

What is Video Playback QoS?

2011-05-24T10:28:48.0000000

Introduction

QoS is the abbreviation for Quality of Service, which does not refer to the level of performance achieved but rather the guarantee of a certain level of performance to data flow.

Promise uses the term Guaranteed Latency to refer to the maximum response time that a disk-drive will be allowed to reply to a command from the RAID controller before the data for that disk-drive is regenerated using the parity function - if that disk-drive is a member of a redundant Logical Drive array.

In order for a RAID Logical Drive array to achieve a guaranteed response time for a read command from the host system it has to resiliently handle disk-drive errors and return the requested data, but most errors on a disk-drive result in its response time exceeding a maximum allowable threshold. When this occurs the data from the disk-drive with the error is regenerated using a parity operation on the data from the other disk-drives in the Logical Drive, if that data was not in the RAID controller's read cache.

Guaranteed Latency provides users a mechanism for achieving a predictable response time for any read commands to a redundant Logical Drive in an environment that is primarily dictated by the behavior of the disk-drives - video ingesting, editing, and playback. This predictable response time provides a known level of Quality of Service - QoS.

The Guaranteed Latency feature provides users with a means of configuring a maximum allowable response time for read commands to the disk-drives, and if one of the disk-drives exceed the defined response time the RAID controller will regenerate the data segment for this disk-drive using the data segments from the other disk-drives of the Logical Drive array they belong to.

Note: This feature is only available on the Promise VTrak for Mac Ex30 - and is disabled by default.

Usage

To use the Guaranteed Latency feature you must enable and configure it, which can be accomplished using the Promise WebPAM browser (GUI), Command Line Interface (CLI), or Command Line Menu (CLU).

Entering a non-zero value for this parameter that is within the allowable range enables this feature, and entering 0 disables this feature.

It has a minimum value of 100ms, a maximum value of 29000ms (29 seconds), a resolution of 10ms.

Note that an example value of 155 would actually round down to 150 due to the 10ms resolution of this paramter.

These rules appy to all three management methods.

Note:
You must exercise caution and choose the minimum value very carefully as this could actually result in unnecessary latency for read commands.
For example, if the Guaranteed Latency is set to 10ms and a disk-drive takes 15ms to respond to a command, the actual time it takes to complete a host command could be more than 15ms because the parity regeneration process to recover the data has been triggered. Also, the additional reads to the other disk-drives for the parity operation could delay other host reads as well.
The recommended minimum value for this field is approximately the average response time for the set disk-drives that comprise the Logical Drive.

Configuring with the GUI

The Guaranteed Latency feature can be found on the Global Physical Drive Settings page, as demonstrated by the following illustration.

Configuring with the CLI

The Guaranteed Latency feature is a hidden command option in the CLI.

To enable or disable Guaranteed Latency use the following command:

administrator@cli> phydrv -a mod -s "glatency=n"

Where n = 0 (disable) or n = 100 to 29000

Configuring with the CLU

Invoke the CLU from the CLI:

administrator@cli> menu

The Guaranteed Latency feature can be found on the Global Physical Drives Settings page, as demonstrated by the following illustration.

Again, n = 0 (disable) or n = 100 to 29000

I am having a problem connecting my MacPro to my VTrak Ex30 using a Brocade DCX switch...

2011-05-03T13:01:26.0000000

Question:

I am having a problem connecting my MacPro to the VTrak Ex30using a Brocade DCX-4S Director switch. How do I connect my MacPro to the VTrak Ex30?

Notes:

• TheBrocade DCX switch will only work in “N Port” topology setting with the VTrakEx30 and Ex10 Fibre Channel front end.

• MACOS X Leopard and Snow Leopard do not support ALUA which offer “Port Aliasing”support for seamless VTrak Ex30 or Ex10 controller failover / failback.

• NLPort Topology supports “Port Aliasing - N Port does not.

• LUNAffinity is enabled on the VTrak Ex30 and Ex10 using NL topology to ensureseamless controller failover / failback in a MAC OS environment.

• AnNL topology supported Fibre Channel switch needs to used in between the MAC andthe DCX switch for seamless VTrak controller failover / failback to work.

• Linuxand Windows system support N Port Topology

Solution:

To ensure proper connectivityusing a Brocade DCX switch, please see diagram below:

Tech Support Contact Information:

https://www.promise.com/ContactUS/

I forgot my password on my Promise VTrak Ex30...

2011-05-03T10:30:02.0000000

Question:

I forgot my password on my Promise VTrak Ex30. How do I reset the password?

Solution:

1. The Ex30 has a password reset button located beside the mini-db9 connector for UPS monitoring.

2. Using a small pin or paper clip, momentarily depress the button.

3. Connect via serial, ssh, telnet or WebPAM Pro-e to the VTrak and login with the default username/password (administrator/password)

Tech Support Contact Information:

https://www.promise.com/ContactUS/

x30 Power Consumption and Thermal Output

2011-05-02T16:33:48.0000000

These numbers are derived from fully populated x30 chassis utilizing SAS drives under full load:

E830

Power Consumption - 701W

Thermal Output - 2393 BTU/Hr

J830

Power Consumption - 458W

Thermal Output - 1563 BTU/Hr

E630

Power Consumption - 508W

Thermal Output - 1734 BTU/Hr

J630

Power Consumption - 326W

Thermal Output - 1113 BTU/Hr

J930 - 60 SAS drives

Power Consumption - 950W

Thermal Output - 2900 BTU/Hr