Searching: firmware - 177 Results Found

VTrak A-Class A-Class Access Control Settings Expected Behavior
Ken Chou posted this 05 March 2014

WindowsDefault UID and GID of the userUID and GID used by VTrak File System based on options set in the export entry of the file system (squashroot is the default)
 Example UserFCS Firmware v1.01.0000.00PR1 Firmware v1.05.0000.00SR1 Firmware v1.08.0000.00
NameUIDGIDsquashrootsquashallsquashnorootsquashrootsquashallsquashnorootsquashrootsquashallsquashnoroot
UIDGIDUIDGIDUIDGIDUIDGIDUIDGIDUIDGIDUIDGIDUIDGIDUIDGID
Rules for the default exports created after formatting the filesystemWindows Administrator1000100010001000N/AN/AN/AN/A10001000N/AN/AN/AN/A10001000N/AN/AN/AN/A
Windows Limited1000100010001000N/AN/AN/AN/A10001000N/AN/AN/AN/A10001000N/AN/AN/AN/A





















Rules for the default exports that were modified or new export createdWindows Administrator10001000100010000010001000100010001000100010001000100010001000100010001000
Windows Limited10001000100010000010001000100010001000100010001000100010001000100010001000






















Note: To make a Windows client have root privilege, please perform the following steps:
  1. Pre-condition: squash = noroot in export setting.
  2. Enable LDAP from A-Class GUI, and then setup according to Windows AD server.
  3. Create a Windows AD user and assign uid/gid as 0.
  4. Login Windows client using the Windows AD user with uid/gid 0.
  5. Input username/password of the Windows AD user with uid/gid 0.
  6. Mount the A-Class volume.
After the steps above, the Windows client can get root privilege.



Mac OSDefault UID and GID of the userUID and GID used by VTrak File System based on options set in the export entry of the file system (squashroot is the default)
 Example UserFCS Firmware v1.01.0000.00PR1 Firmware v1.05.0000.00SR1 Firmware v1.08.0000.00
NameUIDGIDsquashrootsquashallsquashnorootsquashrootsquashallsquashnorootsquashrootsquashallsquashnoroot
UIDGIDUIDGIDUIDGIDUIDGIDUIDGIDUIDGIDUIDGIDUIDGIDUIDGID
Rules for the default exports created after formatting the filesystemroot0000N/AN/AN/AN/A00N/AN/AN/AN/A10001000N/AN/AN/AN/A
Admin (of Mac OSX)5012050120N/AN/AN/AN/A50120N/AN/AN/AN/A50120N/AN/AN/AN/A
JohnDoe38383838N/AN/AN/AN/A3838N/AN/AN/AN/A3838N/AN/AN/AN/A
Rules for the default exports that were modified or new export createdroot00000000100010001000100000100010001000100000
Admin (of Mac OSX)50120501200050120501201000100050120501201000100050120
JohnDoe3838383800383838381000100038383838100010003838

Note:
  1. N/A (not applicable) because when default of squashroot is modified, then it follows the rules of the second row
  2. The values shown in red are wrong and have been fixed in SR1
As you can see from the above chart, access setting implementation is not the same across the first two releases. 
Please reference the following KB for detailed access control definitions:

http://kb.promise.com/thread/what-do-each-of-the-vtrak-a-class-access-control-list-acl-squash-settings-actually-do

Depending on the code are running or may have previously been running, you mayneed to make some access setting modifications via the A-Class GUI.

If you are having access control problems with files or folders please leave the settings intact and contact Promise technical support.

After proper access control setting configuration has been conducted on A-Class, the existing file or folder permissions may need to be modified manually using chmod, chown and chgrp.

See the following:

http://en.wikipedia.org/wiki/Chmod
http://en.wikipedia.org/wiki/Chown
http://en.wikipedia.org/wiki/Chgrp



VTrak A-Class How to replace controller(s) on VTrak AClass system
Ken Chou posted this 23 January 2014

Note - The following document is valid only for firmware v1.01.0000.00 (FCS) and v1.05.0000.00 (PR1)

This document is to guide how to replace A‐Class controller in the field, but does not cover how to replace the whole unit (both chassis and all controllers).

For instructions to replace the whole AClass system, please see "File System Recovery after RMA".

Connecting to the CLI prompt via serial connection on both controllers will allow monitoring of the replacement process. However it is not required.

  1. Please get a subsystem report before replacing the controller.

  2. Pull out the first controller from A‐Class.
    The first controller is the one on left side from back view of the unit.

  3. Note:
    1. Don’t disconnect network cable before pulling out the controller!!!
    2. If the first controller is the primary controller, a fail over will be started
      (CLI command ctrl can show which controller is the primary one)

  4. Unplug all remaining cables from the controller that is removed.

  5. Install the replacement controller.

  6. Note:
    1. Before plugging in the new controller into the chassis, please make sure that the network cable is connected!!!
    2. If there is a Firmware mismatch, firmware will be automatically synced to this controller.
    3. The new installed controller will be rebooted automatically after sync.

  7. Plug in all remaining cables

  8. Using CLI, verify using “ctrl” command that both the controllers are show OK Status and in Active mode.

  9. If replacing both the controllers, please continue to the steps below. If this is a single controller VTrak AClass, please  skip to Step 12.

  10. Pull out the second controller

  11. Note:
    1. Don’t disconnect network cable before pulling out the controller!!!
    2. The second controller is primary controller, a fail over will be started.
      (CLI command ctrl can show which controller is the primary one)

  12. Unplug all remaining cables from the controller that is removed.

  13. Install the other replacement controller.

  14. Note:
    1. Before plugging in the new controller into the chassis, please make sure that the network cable is connected!!!
    2. If there is a Firmware mismatch, firmware will be automatically synced to this controller.
    3. The new installed controller will be rebooted automatically after sync.

  15. Plug in all remaining cables.

  16. Login to A‐Class GUI.

    1. Go through first time Setup Wizard.
      All steps in this first time Step Wizard can be skipped, because of these settings are kept during the controller replacement.

    2. Setup LDAP Setting.
      Because of system limitations, LDAP setting has to be re‐configured manually after both controllers are replaced.

  17. After controller(s) are replaced, please save a new subsystem report for your records.

Close