Monthly Archives: August 2014


The typeperf command writes performance data to the command window or to a log file.

typeperf <counter [counter …]> [options]
typeperf -cf <filename> [options]
typeperf -q [object] [options]
typeperf -qx [object] [options]

typeperf “\Processor)_Total)\% Processor Time”
typeperf -cf counters.txt -si 5 -sc 50 -f TSV -o domain2.tsv
typeperf -qx PhysicalDisk -o counters.txt
typeperf “\memory\available bytes”


C:\>typeperf /?

Typeperf writes performance data to the command window or to a log file. To
stop Typeperf, press CTRL+C.

typeperf { <counter [counter …]> | -cf <filename> | -q [object]
| -qx [object] } [options]

<counter [counter …]>       Performance counters to monitor.

-?                            Displays context sensitive help.
-f <CSV|TSV|BIN|SQL>          Output file format. Default is CSV.
-cf <filename>                File containing performance counters to
monitor, one per line.
-si <[[hh:]mm:]ss>            Time between samples. Default is 1 second.
-o <filename>                 Path of output file or SQL database. Default
-q [object]                   List installed counters (no instances). To
list counters for one object, include the
object name, such as Processor.
-qx [object]                  List installed counters with instances. To
list counters for one object, include the
object name, such as Processor.
-sc <samples>                 Number of samples to collect. Default is to
sample until CTRL+C.
-config <filename>            Settings file containing command options.
-s <computer_name>            Server to monitor if no server is specified
in the counter path.
-y                            Answer yes to all questions without prompting.

Counter is the full name of a performance counter in
“\\<Computer>\<Object>(<Instance>)\<Counter>” format,
such as “\\Server1\Processor(0)\% User Time”.

typeperf “\Processor(_Total)\% Processor Time”
typeperf -cf counters.txt -si 5 -sc 50 -f TSV -o domain2.tsv
typeperf -qx PhysicalDisk -o counters.txt


Fsutil is a command-line utility that you can use to perform many FAT and NTFS file system related tasks, such as managing reparse points, managing sparse files, dismounting a volume, or extending a volume.

—- Commands Supported —-

8dot3name       8dot3name managment
behavior        Control file system behavior
dirty           Manage volume dirty bit
file            File specific commands
fsinfo          File system information
hardlink        Hardlink management
objectid        Object ID management
quota           Quota management
repair          Self healing management
reparsepoint    Reparse point management
resource        Transactional Resource Manager management
sparse          Sparse file control
transaction     Transaction management
usn             USN management
volume          Volume management

C:\windows\system32>fsutil fsinfo
—- FSINFO Commands Supported —-

drives          List all drives
drivetype       Query drive type for a drive
volumeinfo      Query volume information
ntfsinfo        Query NTFS specific volume information
statistics      Query file system statistics

Some examples
Create a new file of a specific size(Arbitrary Size)

FSUTIL file createnew filename

C:\>fsutil file createnew test.txt 100
File C:\test.txt is created

possibly very large, with this utility is very easy to create a 10GB file, use the following:

fsutil file createnew bigfile.out 10737418240

Create a hardlink

FSUTIL hardlink create new_filename existing_filename

fsutil hardlink create c:\foo.txt c:\bar.txt

Set the zero data for a file

FSUTIL file setzerodata offset=val length=val filename

fsutil file setzerodata offset=100 length=150 C:\Temp\sample.txt

C:\windows\system32>fsutil fsinfo drives

Drives: C:\

C:\windows\system32>fsutil fsinfo drivetype c:
c: – Fixed Drive

C:\windows\system32>fsutil fsinfo statistics c:
File System Type :     NTFS

UserFileReads :        322574
UserFileReadBytes :    5475978240
UserDiskReads :        316161
UserFileWrites :       87461
UserFileWriteBytes :   4716495608
UserDiskWrites :       92814
MetaDataReads :        37771
MetaDataReadBytes :    411365376
MetaDataDiskReads :    54770
MetaDataWrites :       37664
MetaDataWriteBytes :   190550016
MetaDataDiskWrites :   48367

MftReads :             34323
MftReadBytes :         374571008
MftWrites :            24323
MftWriteBytes :        106967040
Mft2Writes :           0
Mft2WriteBytes :       0
RootIndexReads :       0
RootIndexReadBytes :   0
RootIndexWrites :      0
RootIndexWriteBytes :  0
BitmapReads :          23
BitmapReadBytes :      5316608
BitmapWrites :         10492
BitmapWriteBytes :     60985344
MftBitmapReads :       6
MftBitmapReadBytes :   24576
MftBitmapWrites :      1492
MftBitmapWriteBytes :  6963200
UserIndexReads :       19868
UserIndexReadBytes :   101777408
UserIndexWrites :      10613
UserIndexWriteBytes :  49397760
LogFileReads :         7
LogFileReadBytes :     28672
LogFileWrites :        46987
LogFileWriteBytes :    395644928
LogFileFull :          0



Install ESXi Interactively

You use the ESXi CD/DVD or a USB flash drive to install the ESXi software onto a SAS, SATA, SCSI hard drive, or USB drive.
ESXi Embedded must not be on the host. ESXi Installable and ESXi Embedded cannot exist on the same host.
■     You must have the ESXi ISO file on CD or DVD. If you do not have the installation CD/DVD, you can create one.
■     Verify that the server hardware clock is set to UTC. This setting is in the system BIOS.
■     Verify that a keyboard and monitor are attached to the machine on which the ESXi software will be installed.
■     Consider disconnecting your network storage. This action decreases the time it takes the installer to search for available disk drives. Note that when you disconnect network storage, any files on the disconnected disks are unavailable at installation.
Do not disconnect a LUN that contains an existing ESX or ESXi installation. Do not disconnect a VMFS datastore that contains the Service Console of an existing ESX installation. These actions can affect the outcome of the installation.
■     Gather the information required by the ESXi installation wizard.

1    Insert the ESXi CD/DVD into the CD/DVD-ROM drive and restart the machine.
2    Set the BIOS to boot from the CD-ROM device.
See your hardware vendor documentation for information on changing boot order.
3    On the Select a Disk page, select the drive on which to install ESXi and press Enter.
Press F1 for information about the selected disk.
Do not rely on the disk order in the list to select a disk. The disk order is determined by the BIOS and might be out of order. This might occur on systems where drives are continuously being added and removed.
If the disk you selected contains data, the Confirm Disk Selection page appears.
4    Select the keyboard type for the host.
You can change the keyboard type after installation in the direct console.
5    Enter the root password for the host.
You can leave the password blank, but to secure the system from the first boot, enter a password. You can change the password after installation in the direct console.
6    Press F11 to start the installation.
7    When the installation is complete, remove the installation CD or DVD.
8    Press Enter to reboot the host.
If you are performing a new installation, or you chose to overwrite an existing VMFS datastore, during the reboot operation, VFAT scratch and VMFS partitions are created on the host disk.
9    Set the first boot device to be the drive on which you installed ESXi in Step 3.

Install the vSphere Client

The vSphere Client enables you to connect to an ESXi host and to a vCenter Server system.
■     In a Web browser application, enter the IP address of a vCenter Server or an ESXi host, and click Download vSphere Client.
■     Verify that you are a member of the Administrators group on the system.
■     Verify that the system has an Internet connection.
1    Double-click the VMware-viclient<build number>.exe file to run the vSphere Client installer.
2    Follow the prompts in the wizard to complete the installation.

vCenter Server Installation

vCenter Server Prerequisites

Verify that you have a separate 64-bit physical server on which to install vCenter Server 5.0. You can also install ESXi 5.0 on that system and deploy vCenter Server in a virtual machine within the host. vCenter Server 5.0 cannot run as a virtual machine on an ESXi host that runs a vSphere Storage Appliance.
Verify that the physical server or virtual machine meets the hardware requirements for vCenter Server.

Verify that you have vSphere Storage Appliance 1.0 installation DVD, or download the vCenter Server 5.0 installer from the VMware product page

Verify that the fully qualified domain name (FQDN) of the system where you will install vCenter Server is resolvable. To check that the FQDN is resolvable,
type nslookupyour_vCenter_Server_fqdn at a command line prompt.
If the FQDN is resolvable, the nslookup command returns the IP and name of the domain controller machine.
Verify that the host name of the machine that you are installing vCenter Server on complies with RFC 952 guidelines.
Verify that DNS reverse lookup returns a fully qualified domain name when queried with the IP address of the vCenter Server. When you install vCenter Server, the installation of the web server component that supports the vSphere Client fails if the installer cannot look up the fully qualified domain name of the vCenter Server from its IP address. Reverse lookup is implemented using PTR records. To create a PTR record, see the documentation for your vCenter Server host operating system.
Verify that no Network Address Translation (NAT) exists between the vCenter Server system and the hosts it will manage.
For small-scale deployments, VMware recommends installing the bundled SQL Server 2008 R2 Express database on one of the supported operating systems.
If the system that you use for your vCenter Server installation belongs to a workgroup rather than a domain, not all functionality is available to vCenter Server. If assigned to a workgroup, the vCenter Server system is not able to discover all domains and systems available on the network when using some features. To determine whether the system belongs to a workgroup or a domain, right-click My Computer. Click Properties and click the Computer Name tab. The Computer Name tab displays either a Workgroup label or a Domain label.
During the installation, verify that the connection between the machine and the domain controller is working.
Verify that the computer name is no more than 15 characters.
The NETWORK SERVICE account is required on the folder in which vCenter Server is installed and on the HKLM registry.
Verify that the DNS name of the machine matches the actual computer name.
Make sure the system on which you are installing vCenter Server is not an Active Directory domain controller.
On each system that is running vCenter Server, make sure that the domain user account has the following permissions:
■     Member of the Administrators group
■     Act as part of the operating system
■     Log on as a service

Install vCenter Server, like any other network server, on a machine with a fixed IP address and well-known DNS name, so that clients can reliably access the service. Assign a static IP address and host name to the Windows server that will host the vCenter Server system. This IP address must have a valid (internal) domain name system (DNS) registration. Ensure that the ESXi host management interface has a valid DNS resolution from the vCenter Server and all vSphere Clients. Ensure that the vCenter Server has a valid DNS resolution from all ESXi hosts and all vSphere Clients. If you use DHCP instead of a static IP address for vCenter Server, make sure that the vCenter Server computer name is updated in the domain name service (DNS). Ping the computer name to test this connection. For example, if the computer name is, run the following command in the Windows command prompt:
If you can ping the computer name, the name is updated in DNS.

Install vCenter Server

vCenter Server allows you to centrally manage hosts from either a physical or virtual Windows machine, and enables the management of a VSA cluster as well as the use of advanced features such as vSphere High Availability (HA), vSphere vMotion, and vSphere Storage vMotion.
A vCenter Server instance can manage only one instance of a VSA cluster.

See vCenter Server Prerequisites.
vCenter Server requires the Microsoft .NET 3.5 SP1 Framework. If your system does not have it installed, the vCenter Server installer installs it. The .NET 3.5 SP1 installation might require Internet connectivity to download more files.

1    In the software installer directory, double-click the autorun.exe file to start the installer.
2    Select vCenter Server™.
3    Follow the prompts in the installation wizard to choose the installer language, agree to the end user patent and license agreements, enter your user name, organization name, and license key.
If you omit the license key, vCenter Server will be in evaluation mode, which allows you to use the full feature set for a 60-day evaluation period. After installation, you can enter the license key to convert vCenter Server to licensed mode.
4    Click Install SQL Server 2008 Express instance (for small-scale deployments).
This database is suitable for small deployments of up to 5 hosts and 50 virtual machines.
5    Select Use SYSTEM Account and click Next.
The Fully Qualified Domain Name field displays the FQDN of the system that you are installing vCenter Server on. The vCenter Server installer checks that the FQDN is resolvable. If not, a warning message is displayed when you click Next. Change the entry to a resolvable FQDN. You must enter the FQDN, not the IP address.
6    Accept the default destination folders and click Next.
7    Select Create a standalone VMware vCenter Server instance and click Next.
8    For each component that you install, accept the default port numbers and click Next.

Note: Do not change the default vCenter Server ports, as it might lead to VSA upgrade failures.

Select the size of your vCenter Server inventory to allocate memory for several Java services that are used by vCenter Server.
This setting determines the maximum JVM heap settings for VMware VirtualCenter Management Webservices (Tomcat), Inventory Service, and Profile-Driven Storage Service. You can adjust this setting after installation if the number of hosts in your environment changes. See the recommendations in the vCenter Server Hardware Requirements topic in System Requirements.
Click Install.
Installation might take several minutes. Multiple progress bars appear during the installation of the selected components and finish installation.

The RDP protocol component X.224 detected an error

Problem Description :

You may experince problems if you try to connect to a Windows Server 2008 R2 via RDP.

Sympthoms :
– RDP Session may freeze.
– Black screen inside RDP window.
– Slow connection.
– You may also be disconnected.

Error Messages :

Log Name: System
Source: TermDD
Date: 28.02.2012 08:49:40
Event ID: 56
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: XXXXX
The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. Client IP:

Log Name: System
Source: TermDD
Date: 25.02.2012 23:00:59
Event ID: 50
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: XXXXX
The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.

Solution :

The following actions solved the problem in our case.

1) Configure TCP Chimney Offload in the operating system
• To disable TCP Chimney Offload, follow these steps:
a. Use administrative credentials to open a command prompt.
b. At the command prompt, type the following command, and then press ENTER:
netsh int tcp set global chimney=disabled

2) Configure TCP Chimney Offload on the network adapter
• To determine the current status of TCP Chimney Offload, follow these steps:
a. Use administrative credentials to open a command prompt.
b. At the command prompt, type the following command, and then press ENTER:
netsh int tcp show global

• To determine the current status of TCP Chimney Offload, follow these steps:
a. Use administrative credentials to open a command prompt.
b. At the command prompt, type the following command, and then press ENTER:
netsh int tcp show global

3) Disable RSS in Windows Server 2008 R2
• To disable RSS, follow these steps:
1. Use administrative credentials to open a command prompt.
2. At the command prompt, type the following command, and then press ENTER:
netsh int tcp set global rss=disabled

• To determine the current status of RSS, follow these steps:
a. Use administrative credentials to open a command prompt.
b. At the command prompt, type the following command, and then press ENTER:
netsh int tcp show global

4) Disable NetDMA in Windows Server 2008 R2
• To disable NetDMA, follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate the following registry subkey, and then click it:
3. Double-click the EnableTCPA registry entry.
Note If this registry entry does not exist, right-click Parameters, point to New, click DWORD Value, type EnableTCPA, and then press ENTER.
4. To enable NetDMA, type 1 in the Value data box, and then click OK.
5. To disable NetDMA, type 0 in the Value data box, and then click OK.
6. If the EnableTCPA registry entry does not exist, enable the NetDMA functionality.

Information about the TCP Chimney Offload, Receive Side Scaling, and Network Direct Memory Access features in Windows Server 2008
Source :

Mount and Unmount a SAN drive from within Windows 2003

As LUN is to be treated as a single disk in Disk manager on windows Serve 2003, to unmount a drive (LUN from SAN) on Windows Server 2003

you can use mountvol.exe commands in the cmd window or script (.cmd / batch files)

Mountvol (without parameters) will list all Volume GUIDs, example:


in this case the volume with GUID 6e900029-ebef-11dd-8b53-806d6172696f

is mounted under D:\

to unmount, type

mountvol D:\ /D

to mount, type
mountvol D:\ \\?\Volume{6e900029-ebef-11dd-8b53-806d6172696f}\

for help, type

mountvol /?

Creates, deletes, or lists a volume mount point.

MOUNTVOL [drive:]path VolumeName
MOUNTVOL [drive:]path /D
MOUNTVOL [drive:]path /L

path        Specifies the existing NTFS directory where the mount
point will reside.
VolumeName  Specifies the volume name that is the target of the mount
/D          Removes the volume mount point from the specified directory.
/L          Lists the mounted volume name for the specified directory.

Possible values for VolumeName along with current mount points are:





Logical Unit Number masking

Logical Unit Number Masking or LUN masking is an authorization process that makes a Logical Unit Number available to some hosts and unavailable to other hosts.

LUN masking is mainly implemented at HBA level. The security benefits of LUN masking implemented at HBAs are limited, since with many HBAs it is possible to forge source addresses (WWNs/MACs/IPs) and compromise the access. Many storage controllers also support LUN masking. When LUN masking is implemented at the storage controller level, the controller itself enforces the access policies to the device and as a result it is more secure. However, it is mainly implemented not as a security measure per se, but rather as a protection against misbehaving servers which may corrupt disks belonging to other servers. For example, Windows servers attached to a SAN will, under some conditions, corrupt non-Windows (Unix, Linux, NetWare) volumes on the SAN by attempting to write Windows volume labels to them. By hiding the other LUNs from the Windows server, this can be prevented, since the Windows server does not even realize the other LUNs exist.

Logical unit number

In computer storage, a logical unit number, or LUN, is a number used to identify a logical unit, which is a device addressed by the SCSI protocol or protocols which encapsulate SCSI, such as Fibre Channel or iSCSI. A LUN may be used with any device which supports read/write operations, such as a tape drive, but is most often used to refer to a logical disk as created on a SAN. Though not technically correct, the term “LUN” is often also used to refer to the logical disk itself.


To provide a practical example, a typical disk array has multiple physical SCSI ports, each with one SCSI target address assigned. An administrator may format the disk array as a RAID and then partition this RAID into several separate storage-volumes. To represent each volume, a SCSI target is configured to provide a logical unit. Each SCSI target may provide multiple logical units and thus represent multiple volumes, but this does not mean that those volumes are concatenated. The computer that accesses a volume on the disk array identifies which volume to read or write with the LUN of the associated logical unit.

In another example: a single disk-drive has one physical SCSI port. It usually provides just a single target, which in turn usually provides just a single logical unit whose LUN is zero. This logical unit represents the entire storage of the disk drive.


How to select a LUN: In the early versions of SCSI, an initiator delivers a Command Descriptor Block (CDB) to a target (physical unit) and within the CDB is a 3-bit LUN field to identify the logical unit within the target. In current SCSI, the initiator delivers the CDB to a particular logical unit, so the LUN appears in the transport layer data structures and not in the CDB.

LUN vs. SCSI Device ID: The LUN is not the only way to identify a logical unit. There is also the SCSI Device ID, which identifies a logical unit uniquely in the world. Labels or serial numbers stored in a logical unit’s storage volume often serve to identify the logical unit. However, the LUN is the only way for an initiator to address a command to a particular logical unit, so initiators often create, via a discovery process, a mapping table of LUN to other identifiers.

Context sensitive: The LUN identifies a logical unit only within the context of a particular initiator. So two computers that access the same disk volume may know it by different LUNs.

LUN 0: There is one LUN which is required to exist in every target: zero. The logical unit with LUN zero is special in that it must implement a few specific commands, most notably Report LUNs, which is how an initiator can find out all the other LUNs in the target. But LUN zero need not provide any other services, such as a storage volume.

Many SCSI targets contain only one logical unit (so its LUN is necessarily zero). Others have a small number of logical units that correspond to separate physical devices and have fixed LUNs. A large storage system may have up to thousands of logical units, defined logically, by administrative command, and the administrator may choose the LUN or the system may choose it.

cXtXdXsX nomenclature in Unix

From the computer perspective, SCSI LUN is only a part of the full SCSI address. The full device’s address is made from the:

c-part: controller ID of the host bus adapter,
t-part: target ID identifying the SCSI target on that bus,
d-part: disk ID identifying a LUN on that target,
s-part: slice ID identifying a specific slice on that disk.

In the Unix family of operating systems, these IDs are often combined into a single “name”. For example, /dev/dsk/c1t2d3s4 would refer to controller 1, target 2, disk 3, slice 4. Presently Solaris, HP-UX, NCR, and others continue to use “cXtXdXsX” nomenclature, while AIX has abandoned it in favor of more familiar names.
Other uses

The term logical unit number also applies to an input/output access channel within certain programming languages.
Fortran I/O

For example, in FORTRAN, some input/output statements such as the READ or WRITE statements contain an ordered pair of numbers which identifies the LUN of the file or other data source or destination, and (usually) also, the FORMAT of the data to be read or written, as in this example:

WRITE (5,32)

where 5 is the LUN of the target file or device, and 32 is the label of the FORMAT statement for the write.

World Wide Name

A World Wide Name (WWN) or World Wide Identifier (WWID) is a unique identifier used in storage technologies including Fibre Channel, Advanced Technology Attachment (ATA) or Serial Attached SCSI (SAS).

A WWN may be employed in a variety of roles, such as a serial number or for addressability; for example, in Fibre Channel networks, a WWN may be used as a WWNN (World Wide Node Name) to identify a switch, or a WWPN (World Wide Port Name) to identify an individual port on a switch. Two WWNs which do not refer to the same thing should always be different even if the two are used in different roles, i.e. a role such as WWPN or WWNN does not define a separate WWN space. The use of burned-in addresses and specification compliance by vendors is relied upon to enforce uniqueness.


Each WWN is an 8 or 16 byte number, the length and format of which is determined by the most significant four bits, which are referred to as an NAA (Network Address Authority.) The remainder of the value is derived from an IEEE OUI (often the term “Company Identifier” is used as a synonym for OUI) and vendor-supplied information. Each format defines a different way to arrange and/or interpret these components. OUIs are used with the U/L and multicast bits zeroed, or sometimes even omitted (and assumed zero.)

The WWN formats include:[1]

“Original” IEEE formats are essentially a two-byte header followed by an embedded MAC-48/EUI-48 address (which contains the OUI.) The first 2 bytes are either hex 10:00 or 2x:xx (where the x’s are vendor-specified) followed by the 3-byte OUI and 3 bytes for a vendor-specified serial number. Thus, the difference between NAA 1 format and NAA 2 format is merely the presence of either a zero pad or an extra 3 nibbles of vendor information.
“Registered” IEEE formats dispense with padding and place the OUI immediately after the NAA. The OUI is no longer considered to be part of a MAC-48/EUI-48 address. For NAA 5 format, this leaves 9 contiguous nibbles for a vendor-defined value. This is the same format used by the companion NAA 6 format, the only difference being a 16-byte number space is assumed, rather than an 8-byte number space. This leaves a total of 25 contiguous nibbles for vendor-defined values.
“Mapped EUI-64” formats manage to fit an EUI-64 address into an 8-byte WWN. Since the NAA is mandatory, and takes up a nibble, this represents a four-bit deficit. These four bits are recouped through the following tricks: First, two bits are stolen from the NAA by allocating NAAs 12, 13, 14, and 15 to all refer to the same format. Second, the remaining two bits are recouped by omitting the U/L and multicast bits from the EUI-64’s OUI. When reconstructing the embedded EUI-64 value, the U/L and multicast bits are assumed to have carried zero values.


WWN addresses are predominantly represented as colon separated hexadecimal octets, MSB-first, with leading zeros — similar to Ethernet’s MAC address. However, there is much variance between vendors.[2]
List of OUIs commonly seen as WWN Company Identifiers

00:50:76 IBM
00:17:38 IBM, formerly XIV.
00:A0:98 NetApp
00:01:55 Promise Technology
00:60:69 Brocade Communications Systems
00:05:1E Brocade Communications Systems, acquired in purchase of Rhapsody Networks
00:60:DF Brocade Communications Systems, formerly CNT Technologies Corporation
00:05:30 Cisco
00:05:73 Cisco
00:05:9b Cisco
00:E0:8B QLogic HBAs, original identifier space
00:1B:32 QLogic HBAs. new identifier space starting to be used in 2007
00:C0:DD QLogic FC switches
00:90:66 QLogic formerly Troika Networks
00:11:75 QLogic formerly PathScale, Inc
08:00:88 Brocade Communications Systems, formerly McDATA Corporation. WWIDs begin with 1000.080
00:60:B0 Hewlett-Packard – Integrity and HP9000 servers. WWIDs begin with 5006.0b0
00:11:0A Hewlett-Packard – ProLiant servers. Formerly Compaq. WWIDs begin with 5001.10a
00:01:FE Hewlett-Packard – EVA disk arrays. Formerly Digital Equipment Corporation. WWIDs begin with 5000.1fe1 or 6000.1fe1
00:17:A4 Hewlett-Packard – MSL tape libraries. Formerly Global Data Services. WWIDs begin with 200x.0017.a4
00:60:48 EMC Corporation, for Symmetrix DMX
00:00:97 EMC Corporation, for Symmetrix VMAX
00:60:16 EMC Corporation, for CLARiiON/VNX
00:60:E8 Hitachi Data Systems
00:10:86 ATTO Technology
00:23:29 DDRdrive LLC, for DDRdrive X1
00:A0:B8 Symbios Logic Inc.
00:0C:50 Seagate Technology
00:00:C9 Emulex
00:14:EE Western Digital


%d bloggers like this: