VESS R2000 Series Articles

Vess R2600: unable to SMB connect with Windows 11 24H2.

2025-10-24T17:20:05.4300000

Intro:

After updating to Windows 11 24H2 users find themseves unable to SMB mount a Vess R2600 share.

Discussion:

In Windows 11 24H2 Microsoft introduced SMB 3.1.1 and included many SMB security enhancements that broke older SMB implementations. This affects all older storage devices.

Many are searching for answers in the various forums and there are a lot of potential solutions, none of which have worked in practice.

We do not have a solution for this. The storage is working as designed but Microsoft has broken SMB.

Some work arounds...

Roll back to Windows 11 23H2.
Use NFS. The Windows NFS client will have to be installed.
Use FTP. Filezilla is an easy to use graphical interface FTP browser.

Other Promise Storage affected by the new Microsoft SMB:

Apollo SMB mount, cloud access is not affected.
SmartStor series.

VessRAID 2000 series: Minimum memory (2GB) may be insufficient.

2018-02-05T20:07:27.6100000

Vess R2600/R2000 Memory Requirements

Feb 05 2018

Background:

The base model Vess R2600 comes with 2GB of memory per controller. The Vess Pro comes with 32GB of memory per controller today, although the original Vess Pro shipped with 16GB of memory per controller.

The memory requirements of the Vess controller depend strongly on the use case, how the Vess is being used. The base model Vess comes with 2GB of memory per controller. This is adequate when the Vess is used as for iSCSI, but more memory may be needed with other use cases, such as...

When the Vess is used as a NAS or mixed NAS + iSCSI.
When the Vess NAS sharedisk was created with Service Release 1 firmware, now known as Type 1.
When the Vess is providing an iSCSI datastore to VMware ESXi servers.
When a Vess iSCSI LUN is being accessed by many servers through multiple portals.
When expanding a sharedisk.
When running a sharedisk check.
When the Vess is joined to a domain.
When sharedisks larger than 8TB are needed.

Recommendations:

For the use cases above it is recommended to upgrade the memory to 8GB per controller. When joined to a large domain, 16GB per controller may be more appropriate. The number of domain users/groups supported scales up with controller memory.

The maximum sharedisk size also scales with memory as follows:

Controller Memory	2GB	4GB	8GB	16GB	32GB
Maximum Sharedisk size	8TB	16TB	32TB	100TB	100TB

Updating Controller Memory:

With a dual controller Vess, both controllers need to have the same amount of memory.

For each controller, DIMMs of different sizes cannot be mixed. That is, if you buy an 8GB DIMM and the controller has a 2GB DIMM installed, you will have to remove the 2GB DIMM before adding the 8GB DIMM.

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 >

VessRAID R2000 series: NAS ACL is not available for OD and LDAP users.

2018-01-15T21:48:31.1530000

Vess Access Control

Introduction:

The Vess R2000 series supports two types of access control.

1) ACL (Access Control List)

2) Permissions.

When Permissions are used, users can be granted Read-Write, Read-Only or Deny-Acess permission to a sharedisk.

When ACLs are used, users can be granted Read-Write, Read-Only or Deny-Acess permission to folder(s) in a sharedisk. Different folders can have different ACLs. ACLs give more granular access control than Permissions.

Limitations on where ACLs can be used:

ACLs can be used with local users and Active Directory (AD) users only. If authentication is done with Open Directory (OD) or Lightweight Directory Access Protocol (LDAP), then ACLs cannot be used. Once OD or LDAP have been configured, the default access control will be Permissions with a default permission of Read-Write as seen in the image below. While any new user will have the default Read-Write permission, a users permissions can be changed to Deny-Access or Read-Only.

Limitations on Permissions:

Permissions can be used for local users and AD/LDAP/OD users. But for OD and LDAP users, Permissions is the only option and default permission (Read-Write) cannot be changed, although users Permissions can be changed at any time.

Best Practices for VMware for Vess R2600 Series

2018-01-10T20:42:56.0470000

The following is a best practice guide for the use of a Vess R2600 Series for VMware ESXi version 5 or higher.

Topics covered for this article are RAID Levels, Expansion Chassis, LUN Affinity, ALUA, VAAI Support and Thin Provisioning.

RAID: RAID is an acronym for Redundant Array Of Independent Disks.
For VMware usage, we recommend one of the following two RAID configurations to be used:

RAID 5 (Stripe With Parity): Optimal Read/write speeds with less overhead. Superior Performance.
RAID 6 (Stripe with Dual Parity): Good for Archival Storage that offers Dual Redundancy and superior fault tolerance.

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

J2600 Expansion Chassis: If you have an expansion chassis attached to your Vess 2600 unit, you can add more storage space to your VM configuration; however, it is not recommended to span enclosures under a single large RAID array volume using the Vess RAID Engine.

For best practice purposes, it is recommended to have each enclosure contain separate disk arrays (RAID configurations which span enclosures, will require either RAID 50 or RAID 60)

LUN Affinity: For optimization, LUN Affinity should be enabled for Dual controller Vess R2600 units. LUN Affinity will enable write performance to be faster, and increase stability. Although VMware has been certified with LUN Affinity disabled, Promise Technology recommends that LUN Affinity be enabled to provide the best performance.

ALUA: ALUA is an acronym for Asynchronous Logical Unit Access (ALUA) must be enabled for VMWare to be optimized. VMware 5x and higher is ALUA aware, and it is recommended to have this feature enabled for better overall performance on the unit.

Thin Provisioning: This VMware feature is to a VM that is available in the LUN to provide higher utilization by letting you dedicate more storage capacity than the actual purchased capacity. With VAAI enabled, the Vess 2600 series can provide hardware support to thin provisioned LUNs by allowing freed up space on the LUN to be reclaimed.

VAAI: VMware API Array Integration (VAAI) is a VMware special configuration API which offloads some storage tasks for the ESXi server. This is also known as hardware acceleration.

The latest Vess firmware versions offer VAAI support which can be either enabled or disabled as only VMware makes use of VAAI.

Note that if VAAI was in use prior to upgrading to VMware, it is important that VAAI be re-enabled after updating to continue to access the volume. If VAAI is not enabled after the upgrade of the VMware host, the LUN(s) will be seen but the datastore will not be accessible. This is due to the datastore being originally created with VAAI enabled.
With VAAI enabled, the datastore will have support use for AB file locking. Therefore, the datastore will only be seen if VAAI is enabled.

To enable the VAAI feature on the Vess 2600 series, you may use the WEBPAM PROe GUI or the Command Line Interface (CLI).

[Enabling VAAI via WEBPAM PROe]

To enable VAAI via WEBPAM PROe:

Go to Component List, select (click) on one of the controllers, and click Settings:
In the Setting menu, locate Enable VAAI Support and ✓ the checkbox. Then click Save.

Note 1 - Once you apply the VAAI module to one controller, the setting will automatically be applied to the second controller.

Note 2 - Make sure to reboot the subsystem after enabling VAAI.

[Enabling VAAI via CLI]

To access the CLI, you can use the serial console or via terminal thru SSH:

ssh administrator@Virtual_IP_Address

To enable VAAI in the CLI, type the following commands:

administrator@cli> ctrl -a mod -s "VAAIsupport=enable"

Note: The CLI does not prompt the end-user to reboot the Vess; however, the Vess 2600 needs to be rebooted.

After enabling the VAAI module, you will need to reboot the Vess and the ESXi server.

After you reboot the Vess 2600, run the following command to ensure that VAAI is enabled on both controllers:

administrator@cli> ctrl -v
 
-------------------------------------------------------------------------------
CtrlId: 1
Alias: Controller 1
OperationalStatus: OK                  PowerOnTime: 35 minutes
ControllerRole: Primary                ReadinessStatus: Active
LUNAffinity: Enabled                   LunmappingMethod: Name Based
CacheUsagePercentage: 0%               DirtyCachePercentage: 0%
 
PartNo: F29V2FD00000000                SerialNo: XXXXXXXXXXXXXXX
HWRev: A3.1                            WWN: XXXX-XXXX-XXXX-XXXX
CmdProtocol: SCSI-3
MemType: DDR3 SDRAM (Slot 1)           MemSize: 2 GB (Slot 1)
       : N/A (Slot 2)                  : N/A (Slot 2)
FlashType: Flash Memory                FlashSize: 512 MB
NVRAMType: SRAM                        NVRAMSize: 256 KB
BootLoaderVersion: 1.00.0000.18        BootLoaderBuildDate: Apr 28, 2016
FirmwareVersion: 1.05.0000.84          FirmwareBuildDate: Nov 27, 2017
SoftwareVersion: 1.05.0000.84          SoftwareBuildDate: Nov 27, 2017
 
DiskArrayPresent: 2                    OverallRAIDStatus: OK
LogDrvPresent: 2                       LogDrvOnline: 2
LogDrvOffline: 0                       LogDrvCritical: 0
PhyDrvPresent: 16                      PhyDrvOnline: 16
PhyDrvOffline: 0                       PhyDrvPFA: 0
GlobalSparePresent: 0                  DedicatedSparePresent: 0
RevertibleGlobalSparePresent: 0        RevertibleDedicatedSparePresent: 0
RevertibleGlobalSpareUsed: 0           RevertibleDedicatedSpareUsed: 0
 
WriteThroughMode: No                   MaxSectorSize: 4 KB
PreferredCacheLineSize: 64 KB          CacheLineSize: 64 KB
Coercion: Enabled                      CoercionMethod: GBTruncate
SMART: Disabled                        SMARTPollingInterval: 10 minutes
MigrationStorage: DDF                  CacheFlushInterval: 3 second(s)
PollInterval: 15 second(s)             AdaptiveWBCache: Enabled
HostCacheFlushing: Disabled            ForcedReadAhead: Enabled
ALUA: Enabled                          PowerSavingIdleTime: Never
PowerSavingStandbyTime: Never          PowerSavingStoppedTime: Never
RestoreACMode: Last state
AdvancedBatteryFlashBackup: Enabled
BackupFlashStatus: Backup flash ready
BackupFlashSize: 7.54 GB
PerfectRebuildAvailable: 16
ApplianceMode: Generic
VAAIsupport: Enable
 
-------------------------------------------------------------------------------
CtrlId: 2
Alias: Controller 2
OperationalStatus: OK                  PowerOnTime: 35 minutes
ControllerRole: Secondary              ReadinessStatus: Active
LUNAffinity: Enabled                   LunmappingMethod: Name Based
CacheUsagePercentage: 0%               DirtyCachePercentage: 0%
 
PartNo: F29V2FD00000000                SerialNo: XXXXXXXXXXXXXXX
HWRev: A3.1                            WWN: XXXX-XXXX-XXXX-XXXX
CmdProtocol: SCSI-3
MemType: DDR3 SDRAM (Slot 1)           MemSize: 2 GB (Slot 1)
       : N/A (Slot 2)                  : N/A (Slot 2)
FlashType: Flash Memory                FlashSize: 512 MB
NVRAMType: SRAM                        NVRAMSize: 256 KB
BootLoaderVersion: 1.00.0000.18        BootLoaderBuildDate: Apr 28, 2016
FirmwareVersion: 1.05.0000.84          FirmwareBuildDate: Nov 27, 2017
SoftwareVersion: 1.05.0000.84          SoftwareBuildDate: Nov 27, 2017
 
DiskArrayPresent: 2                    OverallRAIDStatus: OK
LogDrvPresent: 2                       LogDrvOnline: 2
LogDrvOffline: 0                       LogDrvCritical: 0
PhyDrvPresent: 16                      PhyDrvOnline: 16
PhyDrvOffline: 0                       PhyDrvPFA: 0
GlobalSparePresent: 0                  DedicatedSparePresent: 0
RevertibleGlobalSparePresent: 0        RevertibleDedicatedSparePresent: 0
RevertibleGlobalSpareUsed: 0           RevertibleDedicatedSpareUsed: 0
 
WriteThroughMode: No                   MaxSectorSize: 4 KB
PreferredCacheLineSize: 64 KB          CacheLineSize: 64 KB
Coercion: Enabled                      CoercionMethod: GBTruncate
SMART: Disabled                        SMARTPollingInterval: 10 minutes
MigrationStorage: DDF                  CacheFlushInterval: 3 second(s)
PollInterval: 15 second(s)             AdaptiveWBCache: Enabled
HostCacheFlushing: Disabled            ForcedReadAhead: Enabled
ALUA: Enabled                          PowerSavingIdleTime: Never
PowerSavingStandbyTime: Never          PowerSavingStoppedTime: Never
RestoreACMode: Last state
AdvancedBatteryFlashBackup: Enabled
BackupFlashStatus: Backup flash ready
BackupFlashSize: 7.54 GB
PerfectRebuildAvailable: 16
ApplianceMode: Generic
VAAIsupport: Enable

How to save a system Service Report on the Vess R2000 Series

2017-01-10T22:34:11.8670000

How to save a system Service Report on the Vess R2000 Series

To Save a system Service Report on a VR2000 series:

Log in to the web-based management GUI.
Click on the Save Service Report link at the top of the management window.
The Vess will generate a system Service Report, and depending on your browser's configuration you may either be prompted to select where to save the file, or the file may be automatically saved to your downloads folder.

This links to a Promise KB article on how to attach files to a web support case:

http://kb.promise.com/thread/how-to-attach-files-to-your-web-case/

Vess R2600 PRO Performance and Configuration

2015-05-27T15:10:27.0000000

1. Scope

This document summarizes current performance test data of Promise Vess R2600, as references for Product Marketing. This document will highlight real world video performance, Configurations, Topologies and also real world applications.

2. Executive Summary

Vess R2600performance data is summarized in the following tables:

Table 1 – Single Controllervs. Dual Controller Playback Test Results (OSX 10.10.2)
Playback
Data Rate
MBs
Single Controller
Dual Controller
App
Load
FCPX 10.1.3
PreRes4444 10bit QuadHD 3840x2160 @59.94fps.mov
304.9
1
1
PreRes4444 10bit QuadHD 3840x2160 @50fps.mov
254.4
1
2
PreRes4444 10bit QuadHD 3840x2160 @29.97fps.mov
152.5
2
3
PreRes4444 10bit QuadHD 3840x2160 @23.98fps.mov
122.1
3
6
Uncompressed 10bit 1920x1080@29.97fps.mov
165.9
2
3
Uncompressed 10bit 1920x1080@23.97fps.mov
132.6
3
6
ProRes 422 HQ (1080 @29.97fps).mov
27.8
11
22
DVCPro HD 1280x1080 @29.97fps.mov
14.6
21
42
Notes:

- : Vess R2600 Version: 1.04.0000.01 Build Date: Mar 5, 2015

3. Test Purpose and Requirements

The purpose is to test the performance of Promise Vess R2600 single controller vs dual controller using A/V streaming loads.

3.1 General Test Configuration and Applications

Platform
Mac OSX 10.10.2
File System
XFS
Topology
Four 10Gbit NAS clients
Storage
Vess R2600tiD Version: 1.04.0000.01 Build Date: Mar 5, 2015
Software
Apple Final Cut Pro X –10.1.3
Video Formats
PreRes4444 10bit QuadHD 3840x2160 @59.94fps QuickTime media
PreRes4444 10bit QuadHD 3840x2160 @50fps QuickTime media
PreRes4444 10bit QuadHD 3840x2160 @29.97fps QuickTime media
PreRes4444 10bit QuadHD 3840x2160 @23.98fps QuickTime media
Uncompressed 10bit 1920x1080@29.97fpsQuickTime media
Uncompressed 10bit 1920x1080@23.97fpsQuickTime media
ProRes422 HQ (1080 @29.97fps)QuickTime media
DVCPro HD 1280x1080 @29.97fps
Media Workload
Playback
Ingest*
Ingest*& playback mixed

* : Use Terminal “dd” command to simulate ingesting.

4. Test Environment & Topology

There are two 10Gbit Ethernet interfaces on each controller of Vess R2600tiD. We need to setup all the Mac clients and Vess R2600tiD in the same switch and give them some IP addresses. For example: give Vess R2600tiD IP address of 10.0.10.1 and 10.0.10.2. And set the IP address of Mac clients be 10.0.10.5, 10.0.10.6… and so on. After that, the Mac clients can access the storage of Vess R2600tiD via Samba by “Connect to Server” with smb://10.0.10.1 or smb://10.0.10.2.

Figure1 – 10Gbit NAS Test Topology – Single Controller

In dual controller case, we also could put them all in the same sub-net. For example: give Vess R2600tiD controller1 IP address of 10.0.10.1 and 10.0.10.2 and controller2 IP address of 10.0.10.3 and 10.0.10.4. And set the IP address of Mac clients be 10.0.10.5, 10.0.10.6… and so on. After that, the Mac clients can access the storage of Vess R2600tiD controller1 via Samba by “Connect to Server” with smb://10.0.10.1 or smb://10.0.10.2 and controller2 with smb://10.0.10.3 or smb://10.0.10.4.
Figure
2 – 10Gbit NAS Test Topology – Dual Controller

5. Storage Configuration

Vess R2600tiD: Dual controller, 16GB memory per controller, Redundancy Type:Active-Active.

Controller: Adaptive Writeback Cache enabled, LUNAffinity disabled,

ALUA disabled and ForcedReadAhead disabled.

Disk Pool: RAID Level: RAID5 and Stripe Size: 1MB.

Drives: Controller1: 16 HGSTHUS724030ALS640 3TB drives for

Disk Pool (DP1) with RAID5 and Share Disk (SD1)

Controller2: 16 HGST HUS724020ALS640 2TB drives for

Disk Pool (DP2) with RAID5 and Share Disk (SD2)

Storage subsystem configuration

DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2

5.1
A/V Streaming Passing Criteria

No frame drop for ~1 hour streaming.

6. For OS-X 10.9.X

OS-X version 10.9.X will not support as many video streams as OS-X 10.10.X as it does not support SMB v3.0. Also for best performance a change is required to the TCP/IP stack.

For runtime, enter the following command.

sudo sysctl -w net.inet.tcp.delayed_ack=0

This change will not survive a reboot. To make the change persistent, create a file named /etc/sysctl.conf, in the file place the command

net.inet.tcp.delayed_ack=0

This change is not necessary in OS-X 10.10.X.

Vess R2600 PRO configuration scripts

2015-04-24T09:33:50.0000000

# CONFIGURATION SCRIPT BEGIN
#
# Script Date:    Jun 5, 2015 09:08:10
#
# Script Summary: The configuration script is used to save the current RAID
#                 configuration, which can be later used for various purpose like
#                 - Propagating the saved configuration to other subsystems
#                 - Restoring a system configuration, lost due to some failure
#                 - The script can serve as summary of the system configuration
#                    if needed to troubleshoot a failure condition.
#
# Source Subsystem Configuration Overview:
#       Subsystem Model:               Vess R2600ti
#       Reduancy Type:                 1
#       Controllers Count:             2
#            Controller ID:            1
#                Firmware Version:     1.04.0000.07
#                Software Version:     1.04.0000.07
#                Controller Mode:      0
#            Controller ID:            2
#                Firmware Version:     1.04.0000.07
#                Software Version:     1.04.0000.07
#                Controller Mode:      0
#       Physical Drives Count:         32
#            PD ID    Physical Capacity    Type
#            ~~~~~    ~~~~~~~~~~~~~~~~~    ~~~~
#               1        1.81 TB           SAS HDD
#               2        1.81 TB           SAS HDD
#               3        1.81 TB           SAS HDD
#               4        1.81 TB           SAS HDD
#               5        1.81 TB           SAS HDD
#               6        1.81 TB           SAS HDD
#               7        1.81 TB           SAS HDD
#               8        1.81 TB           SAS HDD
#               9        1.81 TB           SAS HDD
#              10        1.81 TB           SAS HDD
#              11        1.81 TB           SAS HDD
#              12        1.81 TB           SAS HDD
#              13        1.81 TB           SAS HDD
#              14        1.81 TB           SAS HDD
#              15        1.81 TB           SAS HDD
#              16        1.81 TB           SAS HDD
#              17        1.81 TB           SAS HDD
#              18        1.81 TB           SAS HDD
#              19        1.81 TB           SAS HDD
#              20        1.81 TB           SAS HDD
#              21        1.81 TB           SAS HDD
#              22        1.81 TB           SAS HDD
#              23        1.81 TB           SAS HDD
#              24        1.81 TB           SAS HDD
#              25        1.81 TB           SAS HDD
#              26        1.81 TB           SAS HDD
#              27        1.81 TB           SAS HDD
#              28        1.81 TB           SAS HDD
#              29        1.81 TB           SAS HDD
#              30        1.81 TB           SAS HDD
#              31        1.81 TB           SAS HDD
#              32        1.81 TB           SAS HDD
#
# Script Prerequisites for the Target Subsystem:
#       - Target Subsystem must have similar configuration as Source Subsystem
#       - Any exsiting configuration must be deleted from the Target Subsystem for
#         the script to run without errors
#
#
# ADVISORY NOTE :
#
#     PLEASE USE EXTREME CAUTION WHILE EDITING THIS FILE.
#     MODIFICATION RELATED TO STORAGE CONFIGURATION MAY POTENTIALLY PRODUCE
#     UNPREDICTABLE RESULTS OR DATA LOSS ON PRODUCTION SYSTEMS.
#
#     PROMISE STRONGLY RECOMMENDS TESTING ALL USER MODIFIED SCRIPTS ON
#     NON-PRODUCTION SYSTEM, BEFORE USING IT ON PRODUCTION SYSTEMS.
#
# ******************************************************************************

#
# Array Configuration
#

diskpool -a add -n "DP2" -r 6 -p 17,18,19,20,21,22,23,24,25,26,27,28,29,30,31 -s"ctrlid=2,stripe=1024KB"
sharedisk -a add -n "SD2" -d "DP2" -t sd -c 100tb -p smb|webdav|nfs|ftp|afp -u enable -r rw

spare -a add -i 0 -p 32 -r y -t g -s "mediapatrol=enable"

#
#
# CONFIGURATION SCRIPT END
# ******************************************************************************

Playback		Data Rate MBs	Single Controller	Dual Controller
App	Load	Data Rate MBs	Single Controller	Dual Controller
FCPX 10.1.3	PreRes4444 10bit QuadHD 3840x2160 @59.94fps.mov	304.9	1	1
	PreRes4444 10bit QuadHD 3840x2160 @50fps.mov	254.4	1	2
	PreRes4444 10bit QuadHD 3840x2160 @29.97fps.mov	152.5	2	3
	PreRes4444 10bit QuadHD 3840x2160 @23.98fps.mov	122.1	3	6
	Uncompressed 10bit 1920x1080@29.97fps.mov	165.9	2	3
	Uncompressed 10bit 1920x1080@23.97fps.mov	132.6	3	6
	ProRes 422 HQ (1080 @29.97fps).mov	27.8	11	22
	DVCPro HD 1280x1080 @29.97fps.mov	14.6	21	42

Platform	Mac OSX 10.10.2
File System	XFS
Topology	Four 10Gbit NAS clients
Storage	Vess R2600tiD Version: 1.04.0000.01 Build Date: Mar 5, 2015
Software	Apple Final Cut Pro X –10.1.3
Video Formats	PreRes4444 10bit QuadHD 3840x2160 @59.94fps QuickTime media PreRes4444 10bit QuadHD 3840x2160 @50fps QuickTime media PreRes4444 10bit QuadHD 3840x2160 @29.97fps QuickTime media PreRes4444 10bit QuadHD 3840x2160 @23.98fps QuickTime media Uncompressed 10bit 1920x1080@29.97fpsQuickTime media Uncompressed 10bit 1920x1080@23.97fpsQuickTime media ProRes422 HQ (1080 @29.97fps)QuickTime media DVCPro HD 1280x1080 @29.97fps
Media Workload	Playback Ingest* Ingest*& playback mixed

DP1(R5)-SD1	DP1(R5)-SD1	DP1(R5)-SD1	DP1(R5)-SD1
DP1(R5)-SD1	DP1(R5)-SD1	DP1(R5)-SD1	DP1(R5)-SD1
DP1(R5)-SD1	DP1(R5)-SD1	DP1(R5)-SD1	DP1(R5)-SD1
DP1(R5)-SD1	DP1(R5)-SD1	DP1(R5)-SD1	DP1(R5)-SD1

DP2(R5)-SD2	DP2(R5)-SD2	DP2(R5)-SD2	DP2(R5)-SD2
DP2(R5)-SD2	DP2(R5)-SD2	DP2(R5)-SD2	DP2(R5)-SD2
DP2(R5)-SD2	DP2(R5)-SD2	DP2(R5)-SD2	DP2(R5)-SD2
DP2(R5)-SD2	DP2(R5)-SD2	DP2(R5)-SD2	DP2(R5)-SD2