Tuesday 28 February 2012

Demartek Storage Networking Interface Comparison


Demartek Storage Networking Interface Comparison

Updated 22 February 2012
By , Demartek President
Because of the number of storage interface types and related technologies that are used for storage devices, we have compiled this summary document providing some basic information for each of the interfaces. This document will be updated periodically. This document may become larger over time.Contact us if you’d like to see additional information in this document.
The interface types listed here are known as “block” interfaces, meaning that they provide an interface for “block” reads and writes. They simply provide a conduit for blocks of data to be read and written, without regard to file systems, file names or any other knowledge of the data in the blocks. The host requesting the block access provides a starting address and number of blocks to read or write.
We are producing deployment guides for some of the interfaces described in this document. The Demartek iSCSI Deployment Guide 2011 is now available. More Read here


Wednesday 22 February 2012

Netapp Filer Commands


  • sysconfig -a : shows hardware configuration with more verbose information
  • sysconfig -d : shows information of the disk attached to the filer
  • vol status : Shows the volume information
  • vol status -s : Displays the spare disks on the filer
  • vol status -f : Displays the failed disks on the filer
  • vol status -r : Shows the raid configuration, reconstruction information of the disks
  • df -h : Displays volume disk usage
  • df -i : Shows the inode counts of all the volumes
  • df -Ah : Shows "df" information of the aggregate
  • license : Displays/add/removes license on a netapp filer
  • maxfiles : Displays and adds more inodes to a volume
  • aggr create : Creates aggregate
  • vol create <volname> <aggrname> <size> : Creates volume in an aggregate
  • vol offline <volname> : Offlines a volume
  • vol online <volname> : Onlines a volume
  • vol destroy <volname> : Destroys and removes an volume
  • vol size <volname> [+|-]<size> : Resize a volume in netapp filer
  • vol options : Displays/Changes volume options in a netapp filer
  • qtree create <qtree-path> : Creates qtree
  • qtree status : Displays the status of qtrees
  • quota on : Enables quota on a netapp filer
  • quota off : Disables quota
  • quota resize : Resizes quota
  • quota report : Reports the quota and usage
  • snap list : Displays all snapshots on a volume
  • snap create <volname> <snapname> : Create snapshot
  • snap sched <volname> <schedule> : Schedule snapshot creation
  • snap reserve <volname> <percentage> : Display/set snapshot reserve space in volume
  • /etc/exports : File that manages the NFS exports
  • rdfile /etc/exports : Read the NFS exports file
  • wrfile /etc/exports : Write to NFS exports file
  • exportfs -a : Exports all the filesystems listed in /etc/exports
  • cifs setup : Setup cifs
  • cifs shares : Create/displays cifs shares
  • cifs access : Changes access of cifs shares
  • lun create : Creates iscsi or fcp luns on a netapp filer
  • lun map : Maps lun to an igroup
  • lun show : Show all the luns on a filer
  • igroup create : Creates netapp igroup
  • lun stats : Show lun I/O statistics
  • disk show : Shows all the disk on the filer
  • disk zero spares : Zeros the spare disks
  • disk_fw_update : Upgrades the disk firmware on all disks
  • options : Display/Set options on netapp filer
  • options nfs : Display/Set NFS options
  • options timed : Display/Set NTP options on netapp.
  • options autosupport : Display/Set autosupport options
  • options cifs : Display/Set cifs options
  • options tcp : Display/Set TCP options
  • options net : Display/Set network options
  • ndmpcopy <src-path> <dst-path> : Initiates ndmpcopy
  • ndmpd status : Displays status of ndmpd
  • ndmpd killall : Terminates all the ndmpd processes.
  • ifconfig : Displays/Sets IP address on a network/vif interface
  • vif create : Creates a VIF (bonding/trunking/teaming)
  • vif status : Displays status of a vif
  • netstat : Displays network statistics
  • sysstat -us 1 : begins a 1 second sample of the filer's current utilization (crtl - c to end)
  • nfsstat : Shows nfs statistics
  • nfsstat -l : Displays nfs stats per client
  • nfs_hist : Displays nfs historgram
  • statit : beings/ends a performance workload sampling [-b starts / -e ends]
  • stats : Displays stats for every counter on netapp. Read stats man page for more info
  • ifstat : Displays Network interface stats
  • qtree stats : displays I/O stats of qtree
  • environment : display environment status on shelves and chassis of the filer
  • storage show <disk|shelf|adapter> : Shows storage component details
  • snapmirror intialize : Initialize a snapmirror relation
  • snapmirror update : Manually Update snapmirror relation
  • snapmirror resync : Resyns a broken snapmirror
  • snapmirror quiesce : Quiesces a snapmirror bond
  • snapmirror break : Breakes a snapmirror relation
  • snapmirror abort : Abort a running snapmirror
  • snapmirror status : Shows snapmirror status
  • lock status -h : Displays locks held by filer
  • sm_mon : Manage the locks
  • storage download shelf : Installs the shelf firmware
  • software get : Download the Netapp OS software
  • software install : Installs OS
  • download : Updates the installed OS
  • cf status : Displays cluster status
  • cf takeover : Takes over the cluster partner
  • cf giveback : Gives back control to the cluster partner
  • cf disable : To turn of takeover alerts.
  • cf enable : To turn on takeover alerts
  • reboot : Reboots a filer
  • version : shows the netapp Ontap OS version.
  • uptime : shows the filer uptime
  • dns info : this shows the dns resolvers, the no of hits and misses and other info
  • nis info : this shows the nis domain name, yp servers etc.
  • rdfile : Like "cat" in Linux, used to read contents of text files/
  • wrfile : Creates/Overwrites a file. Similar to "cat > filename" in Linux
  • aggr status : Shows the aggregate status
  • aggr status -r : Shows the raid configuration, reconstruction information of the disks in filer
  • aggr show_space : Shows the disk usage of the aggreate, WAFL reserve, overheads etc.

What is DAS NAS SAN?


Difference between SAN - NAS - DAS



DAS:
Direct Attached Storage. Storage

(usually disk or tape) is directly attached
by a cable to the computer processor.
(The hard disk drive inside a PC or a
tape drive attached to a single server
are simple types of DAS.) I/O requests
(also called protocols or commands) access
devices directly.







NAS:
Network Attached
Storage. A NAS device
(“appliance”), usually an
integrated processor plus
disk storage, is attached to
a TCP/IP-based network
(LAN or WAN), and
accessed using specialized
file access/file sharing
protocols. File requests
received by a NAS are translated by the internal processor to device requests


SAN: 
Storage Area Network. Storage
resides on a dedicated network. Like DAS,
I/O requests access devices directly. Today,
most SANs use Fibre Channel media,
providing an any-to-any connection for
processors and storage on that network.
Ethernet media using an I/O protocol
called iSCSI is emerging in



NAS gateway:
A NAS
device without integrated
storage (i.e., just the
NAS processor). Instead,
the NAS device connects
externally to storage by
direct attachment or by SAN.

Brocade day to day use switch CLI commands


Brocade day to day use switch CLI commands 
=============================================

Zone Alias
aliAdd -Add a member to a zone alias.
aliCreate -Create a zone alias.
aliDelete -Delete a zone alias.
aliRemove -Remove a member from a zone alias.
aliShow -Show zone alias definition.

ZoningzoneAdd -Add a member to a zone.
zoneCreate -Create a zone.
zoneDelete -Delete a zone.
zoneRemove -Remove a member from a zone.
zoneShow -Show zone information.

QuickLoop ZoningqloopAdd -Add a member to a QuickLoop.
qloopCreate -Create a QuickLoop.
qloopDelete -Delete a QuickLoop.
qloopRemove -Remove a member from a QuickLoop.
qloopShow -Show QuickLoop information.

Zone ConfigurationcfgAdd -Add a zone to a zone configuration.
cfgCreate -Create a zone configuration.
cfgDelete -Delete a zone configuration.
cfgRemove -Remove a zone from a zone configuration.
cfgShow -Show zone configuration definition.

Configuration Management
cfgClear -Clear all zone configurations.
cfgDisable -Disable a zone configuration.
cfgEnable -Enable a zone configuration.
cfgSave -Save zone configurations in flash memory.
cfgShow -Show zone configuration definition.
cfgTransAbort -Abort the current zoning transaction.


Zoning (Cisco, Brocade and Mc Data)
======================================

Cisco MDS switch (Managed by Cisco Fabric Manager):
- Create Alias (Optional)
- Create a Zone name
- Add the Alias or WWN's to Zone
- Add the Zone to zoneset
- Activate the Zoneset


Brocade Silkworm switch (Manged by Brocade Fabric Manger):

- Create Alias (Optional)

- Create a Zone name
- Add the Alias or WWN's to Zone
- Add the Zone to Configuration
- Enable the Configuration.

Mcdata Switch (Managed by Connectrix manager):
- Create Alias (Optional)


- Create a Zone name
- Add the Alias or WWN's to Zone
- Add the Zone to zoneset
- Activate the Zoneset

**********************************************************************




1. Create alias (this step is optional)

An alias is a name assigned to a device or group of devices. By creating an alias you can assign
a familiar name to a device, or you can group multiple devices into a single name.

An alias must be a unique alpha-numeric string beginning with an alpha character. The
underscore character ( _ ) is allowed and alias names are case sensitive

Aliases can greatly simplify the administrative process; however, they are not required to
define zones.

i.e alicreate "a_host1_hba0","50:06:0b:00:00:bc:be:22"

or alicreate "a_host1_hba1","1,2"

2. Create zone

A zone is a group of devices that can communicate with each other. Zone membership can
include ports, WWNs, or aliases, or any combination of these. And, a device can be included in
more than one zone.

To define a zone, specify the list of members to be included and assign a unique zone name;
the zone name must be a unique alpha-numeric string beginning with an alpha character.

i.e. zonecreate “z_aixhosts","a_aix01;a_aix02;a_aix03;10:00:00:60:69:00:00:8a;1,2"

3. Create a Zoneset or Zone Configuration (We should add the Zone to Zoneset/Configuration)

A zone configuration is a group of zones that are enforced whenever that zone configuration is
enabled. And, a zone can be included in more than one zone configuration.

To define a zone configuration, specify the list of zones to be included and assign a zone
configuration name; the zone configuration name must be a unique alpha-numeric string
beginning with an alpha character.

i.e cfgadd "production1","z_aixhosts"

4. Enable zone configuration

To enable a zone configuration, select the zone configuration to be enabled. The configuration
is downloaded to the switch hardware.

i.e cfgenable production1

note: use cfgsave to save the modified zone configuration. i.e. cfgsave

Tuesday 21 February 2012

SCSI 101 Q&A


·         Q. 11. What is HVD SCSI?
Answer: This is the "old" differential SCSI using TTL voltage levels that was originally defined in SCSI-2, offering 25 meter (82 ft) cable length. It was functionally replaced by LVD (Low Voltage Differential) SCSI in the SPI-2 document of SCSI-3 and obsoleted in the SPI-3 document of SCSI-3. HVD and LVD SCSI are not directly compatible but can be interconnected by the use of a SCSI expander called an LVD to HVD Converter.
·         Q. 12. What is Wide Ultra SCSI?
Answer: Ultra SCSI, defined in the SPI-2 document of SCSI-3 offers a maximum data throughput of 20 Mbytes/sec for Narrow (8-bit) SCSI. Ultra Wide SCSI is the 16-bit version that offers 40 Mbytes/sec data transfers. Ultra Wide single-ended SCSI has a maximum cable length of 1.5 m (5 ft) with more than 4 active IDs and 3 m (10 ft) with 4 or fewer active IDs. Ultra Wide differential SCSI has a maximum cable length of 25 m (82 ft).
·         Q. 13. What is LVD SCSI?
Answer: LVD, which stands for Low Voltage Differential, was introduced in the SPI-2 document of SCSI-3. It is also called Ultra 2 or Fast-40 SCSI. It uses 3 volt instead of 5 volt logic level and is not directly compatible with the "old" differential (HVD) SCSI. LVD again doubles SCSI data throughput to 40 Megatransfers/sec. Cable lengths are 12 m (40 ft). Single initiator-single target applications may use up to 25 m (82 ft) of cable. The "multimode" implementation of LVD is backward compatible with single-ended SCSI. However, connecting one single-ended peripheral to a multimode LVD bus will cause the entire bus to switch to the single-ended mode with the single-ended limitations on data throughput and cable length. LVD can be interconnected with HVD by the use of a SCSI expander called an LVD to HVD Converter.
·         Q. 14. What is "multimode LVD" or LVD/MSE SCSI?
Answer: Multimode LVD and LVD/MSE (Multimode Single-Ended) are terms for the same interface. It is an implementation of SCSI that automatically switches between the LVD and the single-ended mode. When a single-ended device is connected to a multimode LVD/MSE bus, the entire bus switches to the single-ended mode. Otherwise LVD/MSE devices operate in the LVD mode.
·         Q. 15. What are the benefits of LVD SCSI?
Answer: In addition to the obvious benefits of longer maximum cable length than single-ended and a doubling of data throughput, there are a number of other benefits. LVD/MSE and single-ended offer some compatibility. The lower operating voltage of the LVD bus means lower power dissipation, so the differential drivers can be included on the LVD ASIC rather than having to mount them external to the chip. This results in smaller boards, less heat dissipation, higher reliability and lower cost. Also, manufacturers will no longer have to design and build devices with both single-ended and differential interfaces. This results in lower costs.


·         Q. 16. Is LVD SCSI backward compatible?
Answer: LVD is backward compatible through the single-ended interface if it is multimode LVD. It is doubtful that anyone will build LVD devices that are not multimode. Remember that connecting a single-ended device to a LVD/MSE bus will cause the entire bus to switch to the single-ended mode with its data throughput and cable length limitations. To add a single-ended peripheral to an LVD bus and preserve the data throughput and cable length of LVD, you can use a SCSI expander called an LVD to SE or LVD/MSE to LVD/MSE converter. This converter divides the SCSI domain into two bus segments - one segment will operate at the LVD data throughput and cable length and the other bus segment will operate at the single-ended data throughput and cable length.
·         Q. 17. What is Ultra160 or U160 SCSI?
Answer: Ultra 160 is defined in SPI-3. It offers data throughput of 80 Megatransfers/sec or 160 Mbytes/sec for Wide (16-bit) SCSI which is the only defined bus width. For this speed, clocking on both the rising and falling edges of the REQ and ACK clock is required. This is called Double Transition (DT) clocking. Also called Fast-80 or Ultra 3 SCSI.


·         Q. 18. I have heard of U160/m SCSI. What is it?
Answer: The SPI-3 document defines 5 new features for SCSI: Double Transition Clocking, CRC, Domain Validation, Quick Arbitration and Select (QAS), and Information Units (Packetization). In order to be compliant with the SPI-3 U160 specification, at least one of these features must be implemented. A group of industry leaders agreed to incorporate three of these features in order to speed up introduction of U160 products. These three features are Double Transition Clocking, CRC and Domain Validation. U160 devices with these three features are called U160/m.
·         Q. 19. Is Ultra160 SCSI backward compatible?
Answer: Ultra 160, also called Ultra 3 is backward compatible through the single-ended interface, if it is multimode Ultra 160. It is doubtful that anyone will build Ultra 160 devices that are not multimode. Remember that if a single-ended device is placed directly on a multimode Ultra 160 bus the entire bus will switch to the single-ended mode with its limitations on data throughput and cable length.


·         Q. 20. Is Ultra 160 SCSI better than fibre channel?
Answer: This is a discussion that will go on for some time and there is no simple answer. It depends on the application. At least until now, fibre channel (FC) implementations of SCSI have been FC-AL or FC-Arbitrated Loop, so I will limit my comments to FC-AL. At the time of writing this FAQ, SCSI is beginning to ship devices that are capable of 160 Mbytes/sec data transfer rate while fibre channel (FC) is stalled at a maximum of 100 Mbytes/sec and the only peripherals with true FC interface are disk drives -- and only one manufacturer makes them. Mark up the data throughput advantage to SCSI.
§         FC proponents say that connectivity is more important than data throughput and that FC can have up to 126 nodes. If that were true why would every increase in SCSI data throughput be immediately adopted? Data throughput rules in nearly every serious application we have encountered. Anyway, on a practical basis, FC is limited to only a couple dozen nodes which is very similar to what SCSI can handle. Call the connectivity issue a draw.
§         Well then, FC can have up to 10 kilometers of fiber. Well, there are a number of manufacturers of SCSI Extenders that offer the same or longer fiber cable lengths. Call this one a draw.


§         Again, at the time of this writing, an issue that FC proponents do not raise is interconnectivity. There are great problems in getting FC devices from different manufacturers to work together. Sometimes this is true with products from the same manufacturer. SCSI went through these problems many years ago. There are now very few problems with SCSI interconnectivity. Of course, these FC interconnectivity problems will eventually be solved, but for now, score this one for SCSI.
§         Cost is always a factor. FC is more expensive. As FC gets wider application its cost will go down, but for now there is no contest. Score this one for SCSI.
§         Overall, at this time, FC has a place in large scale storage and backup systems but there is almost no reason for the home user and very little reason for the small business to consider FC.

·         Q. 21. Is Ultra 160 SCSI better than EIDE?
Answer: Again, the answer depends on the application. SCSI is an intelligent interface that can perform data transfers with no intervention from the host CPU. SCSI is multi-tasking. An initiator can issue a command to a target. The target can then disconnect from the bus to perform the task and free the bus up for another task. Ultra 160 SCSI can have up to 16 devices connected to the bus and they can be any of a large variety of peripherals, including hard drives, floppy drives, tapes, CDs, scanners, printers, etc. The number of devices can be substantially increased through the use of LUNs. EIDE can have two internal drives connected. Your PC probably has two EIDE buses, so it may have up to four peripherals. Ultra 160 SCSI allows up to 12 m (40 ft) of cabling, which may be internal or external to the computer. For point to point applications you may have up to 25 m (82 ft) of cable. EIDE is for internal cabling only and the maximum cable length is only 18 inches. And, don't forget that 160 Mbytes/sec is much faster than any EIDE bus.

For a home user with a single hard drive, EIDE is probably better as it is less expensive and almost as fast as Ultra SCSI. In a compute-intensive or storage-intensive application, however, SCSI is the clear choice.


·         Q. 22. What is Fast-20 [or Fast-40 or Fast-80] SCSI?
Answer: The term "Fast-xx" refers to the maximum data throughput that a particular version of SCSI is capable of, expressed in Megatransfers/sec. For example, Fast-20 is 20 Megatransfers/sec which is 20 Mbytes/sec for 8-bit (Narrow) SCSI and 40 Mbytes/sec for 16-bit (Wide) SCSI.

§         Fast-10 is the same as Fast SCSI
§         Fast-20 is the same as Ultra SCSI
§         Fast-40 is the same as Ultra 2 (uses LVD transmissions)
§         Fast-80 is the same as Ultra 3 or Ultra 160 SCSI (uses LVD transmissions)

·         Q. 23. Can I connect an Ultra 2 Wide (LVD) disk to an Ultra Wide adapter?
Answer: The answer is definitely yes. However, exactly how you do it depends on the type of Ultra Wide host adapter you have. If it is single-ended SCSI and the LVD disk is multimode LVD, you can connect the disk directly to the host adapter. The multimode LVD interface on the disk will switch to the single-ended mode.

If the Ultra Wide adapter is differential (HVD), they can still be connected, however, you will have to use a SCSI expander called an HVD to SE or an HVD to LVD Converter.
·         Q. 24. What is Double Transition clocking?
Answer: Double Transition (DT) clocking is used to double the data transfer rate from Ultra 2 (Fast-40) to Ultra 3 (Ultra 160 or Fast-80) SCSI without having to increase the clock speed. That means that both edges of the REQ and ACK signals are used to clock data. The REQ and ACK signals run at 40 MHz on Ultra SCSI, so double clocking increases the rate at which data is clocked to 80 MHz. This provides data throughput of 160 Mbytes/sec for Wide SCSI.
·         Q. 25. What is "Domain Validation"?
Answer: Domain Validation is a method used in Ultra 160 (Fast-80 or Ultra 3) to test for the optimum rate for data exchange. Once the host adapter (initiator) has located a peripheral and negotiated a data transfer rate, the initiator sends a Write Buffer command to the target at that negotiated data transfer rate and then reads it back to determine if what it reads is what it wrote. If not, it will resend the Write Buffer command at the next lower data transfer rate. This will continue until a speed is reached where the test is successful. This is all accomplished automatically. (Cntd...)