Popular Posts

Thursday, May 12, 2011

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.




Friday, May 6, 2011

Unable to Recognize New SAN LUNs After Rescan (Vmware ESX server)

After you scan the SAN for the currently presented LUNs, the service console needs to be made aware of the LUN changes.
If your ESX Server version is less than 2.5, you need to perform the following three steps. If your ESX Server version is 2.5 or greater, you need to perform only the third step.
The first step flushes the cache in the HBA (fiber host bus adapter). The second step scans the SAN for presented LUNs. The third step creates device nodes required to partition the available LUNS into VMFS volumes.
Note: The first step applies to QLogic HBAs only, not to Emulex HBAs.
  1. If you have Emulex HBAs, skip this step. Otherwise, for QLogic HBAs only, run wwpn.pl with the -s option for each HBA through which the LUN is accessed. For example:
    wwpn.pl -s vmhba1
  2. Run vmkfstools with the -s option for each HBA through which the LUN is accessed. For example:
    vmkfstools -s vmhba1
  3. Run cos-rescan.sh on the same HBA as in the step above. For example:
    cos-rescan.sh vmhba1

Thursday, May 5, 2011

Storage Provisioning( Clariion, DMX, Vmax, Netapp )

Storage Provisioning steps in EMC Clariion: (Manged by Navisphere Manager)

  • Zone the Server to the CX
  • Go to the connectivity status and register the server
  • Verify the Raid groups having required size of LUN or else create new Raid group
  • Right click on the Raid Group and Create the LUN
  • Create the Storage Group
  • Add the Server and LUN to storage Group
Storage Provisioning steps in EMC DMX: (Managed by ECC or SMC)
  • Identify which FA ports do you want to Map the LUNs to (Normally if its more than 256 LUNs already assigned try use a different FA port)
  • Zone the server to DMX
  • Select the unmapped LUNs , right click on LUN and go to SDR device mapping and map the LUN
  • Go to the Host tab and right cick on the server and select Modify masking configuration and mask the LUNs to the server.
  • Refresh the VCMDB
Storage Provisioning steps in EMC Vmax: (Managed by SMC)
  • Right click on the array and Create a device
  • Create a Storage group and add the devices  to Storage Group
  • Create a Port group and add Array FA ports to Port Group
  • Create a Initiator group and add Server HBA's to Initiator group
  • Create a Masking view and add Port group, Initiator group, Storage group to Masking view
  • Refresh the ACLX
Storage Provisioning steps in Netapp: (Managed by Filerview)
  • Create an Aggregate with Raid Group on it
  • Create a volume
  • Create a Q-Tree (optional)
  • Zone the Server to Array
  • Create the Initiator group and add Server HBA's(WWPN) to Initiator group
  • Create a LUN in the volume or inside the Q-tree 
  • Map the LUN to Initiator group

Wednesday, May 4, 2011

Zoning (Cisco, Brocade and Mc Data)

What are the basic steps we should follow while doing zoning?


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




Brocade Switch CLI Commands (Day to day use)

Comons CLI commands used to administer Brocade Zoning.

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.

Vmax SYMCLI Commands (Symaccess)


- symaccess -sid 1234 list - List all Initiator,Port and Storage Groups Created for Array 1234


- symaccess -sid 1234 list -v - List all Initiator,Port and Storage Groups Created for Array 1234 along with related Masking Views


- symaccess -sid 1234 list -type storage - List all Storage Groups Created for Array 1234


- symaccess -sid 1234 list -type initiator - List all Initiator Groups Created for Array 1234

- symaccess -sid 1234 list -type port - List all Port Groups Created for Array 1234

- symaccess -sid 1234 list view - List masking views Created for Array 1234 with related groups details

- symaccess -sid 1234 list assignment -dev 6A0:6AF - Shows the masking details of devices from 6A0 to 6AF

- symaccess -sid 1234 list no_assignments -dirport 16F:1 - Shows the devices are mapped to 16F:1 but not masked.

- symaccess -sid 1234 list -name MyGroup - List all groups named MyGroup

- symaccess -sid 1234 list -name MyGroup -v - List all groups named MyGroup and also shows the related Masking Views

- symaccess -sid 1234 list devinfo -ig MyInitiator - List the details of devices assigned to the initiatorgroup MyInitiator

- symaccess -sid 1234 show MyStorageGroup -type storage - Shows the contents of storage group MyStorageGroup Created on Array 1234

- symaccess -sid 1234 show MyInitiatorGroup -type initiator - Shows the contents of initiator group MyInitiatorGroup Created on Array 1234

- symaccess -sid 1234 show MyPortGroup -type port - Shows the contents of port group MyPortGroup Createdon Array 1234

- symaccess -sid 1234 show view MyView - Shows the contents of view MyView Created on Array 1234

- symaccess -sid 1234 -f MyBackup.txt backup - Creates a file MyBackup containing all the group and view information currently on the Symmetrix array 1234

- symaccess -sid 1234 -f MyBackup.txt restore - Restores all the group, view and security information from the specified backupup file

- symaccess -sid 1234 -type initiator -name Host1 create -wwn 1000000000000001 - Creates and initiator group called Host1 by adding the specified wwn

- symaccess -sid 1234 -type initiator -name Host1 add -wwn 1000000000000002 - Add the specified wwn in to the existing initiator group Host1


- symaccess -sid 1234 -type port -name 3E0_4E0_13E0_14E0 -dirport 3e:0,4e:0,13e:0,10e:0 create - Create the portgroup E0_4E0_13E0_14E0 with specified ports

- symaccess -sid 1234 -type storage -name Host1 create devs AAA:AAB - Create the storage group Host1 with specified range of devices

- symaccess -sid 1234 -type storage -name Host1 add devs AAA:AAB - Create the storage group Host1 with specified range of devices

- symaccess -sid 1234 create view -name Host1_Allocation -sg Host1 -pg 3E0_4E0_13E0_14E0 -ig Host1 - Create a masking view combined with specified groupsymaccess

- symaccess -sid 1234 list - List all Initiator,Port and Storage Groups Created for Array 1234

- symaccess -sid 1234 list -v - List all Initiator,Port and Storage Groups Created for Array 1234 along with related Masking Views

- symaccess -sid 1234 list -type storage - List all Storage Groups Created for Array 1234

-symaccess -sid 1234 list -type initiator - List all Storage Groups Created for Array 1234

- symaccess -sid 1234 list -type port - List all Storage Groups Created for Array 1234

- symaccess -sid 1234 list view - List masking views Created for Array 1234 with related groups details

- symaccess -sid 1234 list assignment -dev 9A0:9AF - Shows the masking details of devices from 9A0 to 9AF

- symaccess -sid 1234 list no_assignments -dirport 12f:1 - Shows the devices are mapped to 12f:1 but not masked.

- symaccess -sid 1234 list -name MyGroup - List all groups named MyGroup

- symaccess -sid 1234 list -name MyGroup -v - List all groups named MyGroup and also shows the related Masking Views


- symaccess -sid 1234 list devinfo -ig MyInitiator - List the details of devices assigned to the initiatorgroup MyInitiator

- symaccess -sid 1234 show MyStorageGroup -type storage - Shows the contents of storage group MyStorageGroup Created on Array 1234

- symaccess -sid 1234 show MyInitiatorGroup -type initiator - Shows the contents of initiator group MyInitiatorGroup Created on Array 1234

- symaccess -sid 1234 show MyPortGroup -type port - Shows the contents of port group MyPortGroup Createdon Array 1234

- symaccess -sid 1234 show view MyView - Shows the contents of view MyView Created on Array 1234

- symaccess -sid 1234 -f MyBackup.txt backup - Creates a file MyBackup containing all the group and view information currently on the Symmetrix array 1234

- symaccess -sid 1234 -f MyBackup.txt restore - Restores all the group, view and security information from the specified backupup file

- symaccess -sid 1234 -type initiator -name Host1 create -wwn 1000000000000001 - Creates and initiator group called Host1 by adding the specified wwn

- symaccess -sid 1234 -type initiator -name Host1 add -wwn 1000000000000002 - Add the specified wwn in to the existing initiator group Host1

- symaccess -sid 1234 -type port -name 3E0_4E0_13E0_14E0 -dirport 3e:0,4e:0,13e:0,10e:0 create - Create the portgroup E0_4E0_13E0_14E0 with specified ports

- symaccess -sid 1234 -type storage -name Host1 create devs AAA:AAB - Create the storage group Host1 with specified range of devices

- symaccess -sid 1234 -type storage -name Host1 add devs AAA:AAB - Create the storage group Host1 with specified range of devices

- symaccess -sid 1234 create view -name Host1_Allocation -sg Host1 -pg 3E0_4E0_13E0_14E0 -ig Host1 - Create a masking view combined with specified group