1 - Luncreation On DMX Using Solution Enabler

LUN CREATION AND MAPPING
• Physical discs are not visible to hosts.
• Logical volumes can be created from physical discs and they are called
“hyper volume extension”.
• 256 hypers can be created on a physical disc.
• Every hyper has its own personality.
• Initially any hyper is known as a standard device.
• Minimum size of a hyper can be 8mb and maximum size is 32 GB (varies

according to the micro code).
• Standard device can be unprotected, two ways mirrored, three ways

mirrored, 4 way mirrored as well as raid 5 protected.
• Unprotected Standard device less than 5 cylinders are visible to the host
which can be configured as gate keeper device.
• Standard device is visible to host when it is mapped to front end director.
• Once the LUN is deleted it should be unmapped.
• Standard device can be configured to different personalities which may

not be visible to host unless it is protected.
• To set the personalities change the attributes.
• To convert standard device to BCV device it should be an unprotected

device.
• Once standard device is configured to BCV, the BCV can become two
ways mirrored.
• An unprotected standard device with less than 5 cylinders can be

configured as gate keeper device.
• If gate keeper device is not configured, any volume can become gate
keeper.
• Without gatekeeper EMC control center and solution enabler cannot be

operated by host on SYMM.
• SYMM cannot be managed through TCP/IP stack as it is a fiber channel

device.
• It requires FC adapter and HBA.
• Solution enabler installed in the host sends API calls through the HBA
across fiber channel to gate keeper device upon receiving the API’s gate
keeper allows the commands execute on SYMM.
• METAVOLUME: - The larger volumes created by concatenating or

striping the smaller hyper volumes.
• The size of a Meta volume depends on the micro code.
• 2 to 255 hyper volumes can be joined to a Meta volume.
• All hypers joined to a Meta volume should be of same size.
• They should follow same protection mechanism.
• Meta volume is identified by its Meta head i.e., the first volume of the
Meta volume.
• Volumes are mapped to the host through the front end director ports.
• The ports have some flags either disabled or enabled.
• The following flags should be enabled
1. C bit enabled for common serial number to volume
2. SCSI persistent reservations enabled for cluster environment
3. VCM enabled
• To change the status of port flags offline the ports of directors, once
Changed, enable the directors.
LAB SESSION:-
• Create six standard devices two way protected of size 450MB

• Create eight BCV devices of size 450MB
• Create a device unprotected of size five cylinders
• Map the devices
• Mask the devices
NOTE:-
For convenience, following device names are given through out the
programme.
i) primary host name SUN1
ii) backup host name SUN2
iii) SYMM IDs 277 & 694
iv) Fe directors 1c, 1d ,16c and 16d port No=0
STEPS TO CREATE STANDARD DEVICES WITH TWO WAY
PROTECTION
1. Verify the free space available in MBs

SUN1#symconfigure -sid 277 list -freespace –unit MB
• now the free space in SYMM 277 is displayed in MBs example
1278888 MB
2. verify any configuration sessions are running

SUN1#symconfigure -sid 277 verify
• it verifies if any configurations are running
3. verify if any locks have been enforced upon SYM

SUN1#symcfg -sid 277 list -lockn
• it displays the lock number if any lock has been enforced locks can
be from 0 to 15. (Example : configuration lock =15)
4. to release the lock (example 15)

SUN1#syncfg -sid 277 release -lockn 15
• lock released
5. now create a text file using vi editor to submit parameters to commit

the LUN configuration
SUN1#vi create_LUN
Create dev count =6 size=958 emulation=fba config=2-way-mir;
:wq
• Count denotes number of devices to be created
• Size mentioned in cylinders one cyl = 0.5x MB
• Emulation refers to fba(fixed block architecture 512 bytes)used in
open systems.
• Config refers to the protection enforced on device
6. Commit the configuration
SUN1#symconfigure -sid 277 -v -f create_LUN commit –nop
• configuration is saved and six LUNs are created

• phases of this command are preview, prepare and commit
• -v verbose mode
• -f file parameter create_LUN LUN specifications are enclosed
• Commit: to perform the activity
• -nop: non interactive session and no prompting
7. Discover the sym devices
SUN1#symcfg discover
• Solution enabler in host sends an API call through HBA to
sym
• Gate keeper devices receives the API call
• Downloads the configuration of sym in IMPL.bin file to host
• This configuration is stored in /var/sym_api/db directory of
host
8. scan for new devices IO level at host

SUN1#devfsadm -Cv
• it verifies for newly added devices and also the new device
drivers
9. To list the devices

SUN1#symdev list
• displays the newly added devices
• the LUN number is given in hexa decimal code (0000 – ffff)
• As the devices are not mapped the directors field
displays ???:???
• In our session let us suppose the addresses of 6LUNs are 0001
– 0006
10. To display the LUNs which have not been mapped
SUN1#symdev list – noport
• Displays the sym devices which have not been mapped to
any of the frontend directors and its ports
11. To display the available front end ports
SUN1#symcfg –sid 277 list -connections
• It displays the front end directors and their ports to which
the hosts are connected
12. To check the available address in sym
SUN1#symcfg -sid 277 list -available -addresses -dir 1c –p 0
SUN1#symcfg -sid 277 list -available -addresses -dir 1d –p 0
• It shows the available logical unit address to which the sym
devices in host can be mapped
• The available logical address to map is seen in the last field
which is preceded by status field where it shows available
example :
* - AVAILABLE- 001
• The logical unit address is in hexadecimal number.
13 create a file to Map the devices and the specifications
SUN1# vi map_LUN
Map dev 0001:0006 to dir1c:0, Lun=001;
Map dev 0001:0006 to dir1d:0, Lun=001;
:wq
• Map the sym devices with the Lun address 001 in sym box
through the front end directors port 0
14 Commit the activity
SUN1#symconfigure –sid 277 –v –f map_LUN commit –nop
• Configuration is saved and six LUNs are Mapped
• -v verbose mode
• -f file parameter map_LUN LUN specifications are enclosed
15 Scan the devices once again at host level
SUN1#devfsadm –Cv
• Scans the changes in hosts
16 Check the controller
SUN1# fcinfo
• Displays controller number and its wwpn address
17 configure the controller

SUN#cfgadm –c configure C3
• Configure the host controller c3 to map the symdevs with
LUN address
17 Discover the sym devices
18 To list the devices
SUN1#symdev list
• Displays the newly added & mapped sym devices
• As the devices are mapped the directors field displays director
number and port
If the devices are not mapped properly reboot the host once Not
Recommended
STEPS TO CREATE BCV DEVICES
1 Verify the free space available in MBs

• Now the free space in SYMM 277 is displayed in MBs example
1278888 MB
2 Verify any configuration sessions are running
• It verifies if any configurations are running
3 Verify if any locks have been enforced upon SYM

• It displays the lock number if any lock has been enforced locks can
4 To release the lock (example 15)

• Lock released
5 Now create a text file using vi editor to submit parameters to commit

the unprotected LUN configuration
SUN1#vi create_BCV
Create dev count =8 size=958 emulation=fba config=unprotected;
:wq
• Count denotes number of devices to be created
open systems.
6 Commit the configuration
SUN1#symconfigure -sid 277 -v -f create_LUN commit –nop
• Configuration is saved and eight LUNs are created

• Phases of this command are preview, prepare and commit
• -v verbose mode
• -f file parameter create_LUN LUN specifications are enclosed
sym
host
8 Scan for new devices IO level at host

SUN1#devfsadm -Cv
• It verifies for newly added devices and also the new device
drivers

SUN1#symdev list
• Displays the newly added devices
• The LUN number is given in hexa decimal code (0000 – ffff)
• As the devices are not mapped the directors field
displays ???:???
• in our session let us suppose the addresses of 8LUNs are 0009
– 0010
• 0000 lun is for VCM ,0001- 0006 for protected and in most of
the cases 0007 and 0008 are automatically assigned by symm
to sfs luns
10 To convert the devices to BCV devices create a configuration file
SUN1#convert_BCV
Convert dev 0009:0010 to BCV;
Wq
• The unprotected standard devices more than 5 cylinders cannot
be mapped by front end directors, unless it is converted to BCV
device, hence the devices 0009 to 0010 total 8 devices are being
converted to BCV devices.
SUN1#symconfigure -sid 277 -v -f convert_BCV commit –nop
• configuration is saved and eight LUNs are converted

• -v verbose mode
• -f file parameter create_LUN, here LUN specifications are
enclosed
12 To display the LUNs which have not been mapped
• Displays the sym devices which have not been mapped to
any of the front-end directors and its ports
13. To display the available front end ports
• It displays the front end directors and their ports to which
14. To check the available address in sym
• It shows the available logical unit address to which the sym devices in
host can be mapped
example :
* - AVAILABLE- 002
• The logical unit address is in hexadecimal number.
15 Create a file to Map the devices and the specifications
SUN1# vi map_BCV
:wq
SUN1#symconfigure –sid 277 –v –f map_BCV commit –nop
• Configuration is saved and eight LUNs are Mapped
• -v verbose mode
SUN1#devfsadm –Cv
SUN1# fcinfo
19 configure the controller
LUN address
SUN1#symdev list
• As the devices are mapped the directors field displays ***:**
Recommended
STEPS TO CREATE UNPROTECTED STANDARD DEVICES
1 Verify the free space available in MBs

• Now the free space in SYMM 277 is displayed in MBs example
1278888 MB
2 Verify any configuration sessions are running

• It verifies if any configurations are running
3 Verify if any locks have been enforced upon SYM

• It displays the lock number if any lock has been enforced locks can
4 To release the lock (example 15)

• Lock released
5 Now create a text file using vi editor to submit parameters to commit

the LUN configuration
SUN1#vi create_GK
Create dev count =1 size=5 emulation=fba config=unprotected;
:wq
• count denotes number of devices to be created

open systems.
SUN1#symconfigure -sid 277 -v -f create_GK commit –nop
• configuration is saved and six LUNs are created

• -v verbose mode
• -f file parameter create_GK LUN specifications are enclosed
sym
host
8 Scan for new devices IO level at host
SUN1#devfsadm -Cv
• It verifies for newly added devices and also the new device
drivers

SUN1#symdev list
• displays the newly added devices
• the LUN number is given in hexa decimal code (0000 – ffff)
• as the devices are not mapped the directors field
displays ???:???
• in our session let us suppose the address of LUN 0011
10 To display the LUNs, which have not been mapped
• displays the sym devices which have not been mapped to any
of the front-end directors and its ports
11 To display the available front end ports
• it displays the front end directors and their ports to which
12 Check the available address in sym
• It shows the available logical unit address to which the sym
devices in host can be mapped
example :
* - AVAILABLE- 003
• The logical unit address is in hexadecimal number .
13 Create a file to Map the devices and the specifications
SUN1# vi map_GK
Map dev 0011 to dir1c:0, Lun=003;
Map dev 0011 to dir1d:0, Lun=003;
Map dev 0011 to dir16c:0, Lun=003;
Map dev 0011 to dir16d:0, Lun=003;
:wq
SUN1#symconfigure –sid 277 –v –f map_GK commit –nop
• Configuration is saved and LUN is Mapped
• -v verbose mode
SUN1#devfsadm –Cv
SUN1# fcinfo
17 Configure the controller

LUN address
SUN1#symdev list
• As the devices are mapped the directors field displays director
number and port
Recommended

1 - Luncreation On DMX Using Solution Enabler

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1 - Luncreation On DMX Using Solution Enabler

Uploaded by

Copyright:

Available Formats

LUN CREATION AND MAPPING

• Physical discs are not visible to hosts.

• 256 hypers can be created on a physical disc.

• Every hyper has its own personality.

• Initially any hyper is known as a standard device.

• Minimum size of a hyper can be 8mb and maximum size is 32 GB (varies

• Standard device can be unprotected, two ways mirrored, three ways

• Standard device is visible to host when it is mapped to front end director.

• Once the LUN is deleted it should be unmapped.

• Standard device can be configured to different personalities which may

• To set the personalities change the attributes.

• To convert standard device to BCV device it should be an unprotected

• An unprotected standard device with less than 5 cylinders can be

• Without gatekeeper EMC control center and solution enabler cannot be

• SYMM cannot be managed through TCP/IP stack as it is a fiber channel

• It requires FC adapter and HBA.

• METAVOLUME: - The larger volumes created by concatenating or

• Create six standard devices two way protected of size 450MB

1. Verify the free space available in MBs

2. verify any configuration sessions are running

3. verify if any locks have been enforced upon SYM

4. to release the lock (example 15)

5. now create a text file using vi editor to submit parameters to commit

• configuration is saved and six LUNs are created

8. scan for new devices IO level at host

9. To list the devices

17 configure the controller

1 Verify the free space available in MBs

3 Verify if any locks have been enforced upon SYM

4 To release the lock (example 15)

5 Now create a text file using vi editor to submit parameters to commit

• Configuration is saved and eight LUNs are created

8 Scan for new devices IO level at host

9 To list the devices

• configuration is saved and eight LUNs are converted

1 Verify the free space available in MBs

2 Verify any configuration sessions are running

3 Verify if any locks have been enforced upon SYM

4 To release the lock (example 15)

5 Now create a text file using vi editor to submit parameters to commit

• count denotes number of devices to be created

• configuration is saved and six LUNs are created

9 To list the devices

17 Configure the controller

You might also like