Searching: firmware - 177 Results Found

VTrak G-Class (NAS Gateway) Internal LDAP Server Configuration
PROMISE Technology Inc. posted this 27 October 2017 - Last edited 27 October 2017

Table of Contents
A. Enable Internal LDAP
B. Create Internal LDAP Users and Groups
C. Add the Internal LDAP User to the Samba User List
D. Default Folder Anonymous Permissions
E. Adding Permissions to the NAS Gateway SMB Share

Scope

The purpose of this article is to provide an A-Class SAN administrator the appropriate instructions on using the Promise Internal LDAP server module.

Internal and External LDAP servers cannot be enabled at same time. There are three LDAP statuses:

  1. Internal LDAP enabled while External LDAP is disabled
  2. Internal LDAP disabled while External LDAP is enabled
  3. Internal and External LDAP servers are both disabled

 A. Enable Internal LDAP

  1. Go to the Administration tab and go to LDAP Settings.
  2. Select Enable Internal LDAP Server


B. Create Internal LDAP Users and Groups
In the A-Class GUI, if the internal LDAP is enabled, the administrator can create LDAP users and groups under tab "User Management" and "Group Management" respectively.

Create Internal LDAP Group

  1. Click "Add LDAP Group" under the gear icon in tab "Group Management"
  2. Input the Group Name in popup window.
  3. Click the Save button.




Create Internal LDAP User

  1. Click "Add New User" under the gear icon in tab "User Management"
  2. Select Internal LDAP
  3. Input the user’s name 
    (This will automatically update the Display Name and Surname)
  4. Enter the user’s password.
  5. Click the Save button.




C. Add the Internal LDAP User to the Samba User List

  1. Using your web browser, enter the Virtual IP Address of the NAS Gateway Cluster to access the Promise NAS Gateway Samba Login Tool.
  2. You can retrieve the Virtual IP Address of the cluster by going to NAS Gateway > Detail.


  3. Enter the user's credentials that you will be authenticating and Login:
    If you don’t execute this step, your Internal LDAP users will not be able to access the SMB share. 

  4. You will receive a message stating that the user has been successfully authenticated.

D. Default Folder Anonymous Permissions

  1. Go to the NAS Gateway tab and go the Detail
  2. Ensure that the Default Folder Anonymous Permissions is set to: No Anonymous User
  3. Click the pencil edit icon set the No Anonymous User permission and click Save:



E. Adding Permissions to the NAS Gateway SMB Share

  1. Go to NAS Gateway > Mount Point.
  2. Click the gear and select Folder Share:

  3. You can set permissions by User or Group.
    A. User = Read-Write Example:

    B. Group = Read-Write Permission Example
  4. Click Submit to save the changes and you will receive the following notification message:

Related Articles:
Disable SMB Signing on OS X (10.11.5 > 10.12.x)
Unable to Save File on the NASGW from a File Created by a FC Client - Internal/External LDAP Configurations
VTrak G-Class NAS Gateway Firmware Release Notes

Contact Promise Technology Support
Need more help? Save time by starting your support request online and a technical support agent will be assigned to your case.

Promise Technology Technical Support >

VTrak E5000 Promise VTrak: Configuring for Optimal Performance (E5000 Series)
P B posted this 18 October 2016 - Last edited 30 June 2017

Promise VTrak: Configuring for Optimal Performance (E5000 Series)

Configure Promise VTrak RAIDs for best performance using the guidelines in this article.

These scripts are inteded to be used for  Xsan and Quantum StorNext Deployments

- For the Promise VTrak E5000 series, the scripted options below are currently not built into the Promise Admin interface. At this juncture, it is necessary to create and import the configuration scripts. In the next service release of the firmware, these scripts will be embedded in the GUI.

- For the Promise VTrak E5000 & J5000 Series, create and import the desired script, as described below.

- Some of the configuration scripts configure Global or Dedicated Revertible Spare Drives. In the event that a drive is replaced, data will be migrated from the Spare Drive to the replacement drive. Performance may be impacted for the duration of the migration procedure.

Note: All these scripts have ALUA (Asymmetric Logical Unit Access) enabled by default. If all your host's operating systems are ALUA compliant; you may leave ALUA enabled.

In the case that you need to disable ALUA due to your operating system's non-compliancy, following the instructions below.

Locate alua=enable :
 
ctrl -a mod -s "lunaffinity=enable, alua=enable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"

Modify the alua variable in the script before importing:

ctrl -a mod -s "lunaffinity=enable, alua=disable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"

Configure via Script

Create the script file
 
Determine which script you should use from the following list, then click the linked article to get the text of the script. Follow the instructions in the linked article to save the script, then return to this article.
 
 
Configures a RAID Controller that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, two data LUNs, and two spares. Each Xsan or StorNext volume must contain one metadata LUN.
 

RAID Controller: Xsan (Metadata and Data) - E5600f

Configures a RAID Controller that will be used as an Xsan or StorNext Volume. Configures arrays to be used as a metadata LUN, two data LUNs, and two spares. Each Xsan or StorNext volume must contain one metadata LUN.


RAID Controller and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5600f + J5600s

Configures a RAID Controller and SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, four data LUNs, one scratch LUN, and three spares. Each Xsan or StorNext volume must contain one metadata LUN.


RAID Controller and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5600f + (3) J5600s

Configures a RAID Controller and (3) SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, eight data LUNs, three scratch LUNs, and five spares. Each Xsan or StorNext volume must contain one metadata LUN.

RAID Controller: Xsan (Metadata and Data) - E5800f
 
Configures a RAID Controller that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, two data LUNs, one scratch LUN, and two spares. Each Xsan or StorNext volume must contain one metadata LUN.


RAID Controller and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5800f + J5600s
 
Configures a RAID Controller and a SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, four data LUNs, one scratch LUN, and two spares. Each Xsan or StorNext volume must contain one metadata LUN.

RAID Controller and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5800f + (3) J5600s
 
Configures a RAID Controller and (3) SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, eight data LUNs, one scratch LUN, and two spares. Each Xsan or StorNext volume must contain one metadata LUN.

RAID Controller: Xsan (Metadata and Data) - E5320f
 
Configures a RAID Controller that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, two data LUNs, and two spares. Each Xsan or StorNext volume must contain one metadata LUN.


 
Configures a RAID Controller and a SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, four data LUNs, and six spares. Each Xsan or StorNext volume must contain one metadata LUN.


 
Configures a RAID Controller and a SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, four data LUNs, and four spares. Each Xsan or StorNext volume must contain one metadata LUN.

RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5320f + (2) J5600s

Configures a RAID Controller and (2) SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, six data LUNs, and six spares. Each Xsan or StorNext volume must contain one metadata LUN.


 

Search
Popular Tags
Categories
Close