solutions for Unix, Virtualization, Backup & Storage

Wednesday, 10 December 2014

Link Aggregation in Solaris 11

A link aggregation consists of several interfaces on a system that are configured together as a single, logical unit. Link aggregation

What do you mean by Link Aggregation?

Its the process of configuring more than one interfaces in a server together to a single logical unit for increased network performance, increased Bandwidth & Link Protection.

In other sense its also called as Trunking.

In this article i will explain on how to configure Link Aggregation on Solaris hosts where the uplink is coming from a LACP enabled switch.

Please see the below mentioned steps:

1) Identify the network cards to be created for the link aggregation

root@liael243:~# dladm show-link
LINK CLASS MTU STATE OVER
net0 phys 1500 up --
net3 phys 1500 unknown --
net5 phys 1500 unknown --
net2 phys 1500 unknown --
net1 phys 1500 unknown --

------------------------------------------------------------------------------------------------------------------------------------------------

2) Create a aggregate group aggr1 using the below caommand for net 5 and net 1

root@liael243:~# dladm create-aggr -i net1 -i net5 -P L3 -l active

root@liael243:~# dladm show-link
LINK CLASS MTU STATE OVER
net0 phys 1500 up --
net3 phys 1500 unknown --
net5 phys 1500 up --
net2 phys 1500 unknown --
net1 phys 1500 up --
aggr1 aggr 1500 up net5 net1

root@liael243:~# dladm show-aggr
LINK MODE POLICY ADDRPOLICY LACPACTIVITY LACPTIMER
aggr1 trunk L4 auto active short

------------------------------------------------------------------------------------------------------------------------------------------------

3) Assign Ip to the aggregate port

root@liael243:~# ipadm create-ip aggr1
root@liael243:~# ipadm create-addr -T static -a local=10.63.35.50/22 aggr1/v4
root@liael243:~# ipadm show-addr
ADDROBJ TYPE STATE ADDR
lo0/v4 static ok 127.0.0.1/8
net0/v4 static ok 10.63.16.243/22
aggr1/v4 static ok 10.63.35.50/22
lo0/v6 static ok ::1/128

net0/v6 addrconf ok fe80::214:4fff:fef8:3a92/10

Simple!!!!! Link Aggregation is configured in your Solaris host.

Wednesday, 9 January 2013

How to find HBA details in AIX, Solaris, Linux, HP-UX , ESX & Windows

For a person who works on Storage, its mandatory to know the HBA details of the host servers.And when you are working on many flavors of OS, its difficult to remember all the commands. This is making me to write & post such an article. I hope this will be helpful for people working on Storage as well as on Servers.

This article will help Storage admins as well as Sys Admins to find details like port speed, wwn no., vendor make and some important other details of HBA cards inserted in their servers installed with IBM AIX, Oracle SOLARIS, HP-UX, Red-hat LINUX and ESX.

The below mentioned commands should display FCOE card details too if its present in the server.

1) IBM AIX

* First find how many HBA adapters are there using the command "lscfg"

------------------------------------------------------------------------

bash-4.0# lscfg | grep "FC Adapter"

+ fcs1 U787A.001.DPM1VHX-P1-C6-T1 FC Adapter

+ fcs0 U787A.001.DPM1VHX-P1-C1-T1 FC Adapter

* Now we can find the wwn no. of each Adapter card using "lscfg" command (the wwn no. is highlighted in red color )

--------------------------------------------------------------------------------

bash-4.0# lscfg -vpl fcs0

fcs0 U787A.001.DPM1VHX-P1-C1-T1 FC Adapter

Part Number.................00P4295

EC Level....................A

Serial Number...............1D4150C817

Manufacturer................001D

Customer Card ID Number.....5704

FRU Number.................. 00P4297

Device Specific.(ZM)........3

Network Address.............10000000C93E2359

ROS Level and ID............02E01871

Device Specific.(Z0)........2003806D

Device Specific.(Z1)........00000000

Device Specific.(Z2)........00000000

Device Specific.(Z3)........03000909

Device Specific.(Z4)........FF601231

Device Specific.(Z5)........02E01871

Device Specific.(Z6)........06631871

Device Specific.(Z7)........07631871

Device Specific.(Z8)........20000000C93E2359

Device Specific.(Z9)........HS1.81X1

Device Specific.(ZA)........H1D1.81X1

Device Specific.(ZB)........H2D1.81X1

Device Specific.(ZC)........00000000

Hardware Location Code......U787A.001.DPM1VHX-P1-C1-T1

PLATFORM SPECIFIC

Name: fibre-channel

Model: LP9802

Node: fibre-channel@1

Device Type: fcp

Physical Location: U787A.001.DPM1VHX-P1-C1-T1

bash-4.0# lscfg -vpl fcs1

fcs1 U787A.001.DPM1VHX-P1-C6-T1 FC Adapter

Part Number.................00P4295

EC Level....................A

Serial Number...............1D4150C1D6

Manufacturer................001D

Customer Card ID Number.....5704

FRU Number.................. 00P4297

Device Specific.(ZM)........3

Network Address.............10000000C93E1D18

ROS Level and ID............02E01871

Device Specific.(Z0)........2003806D

Device Specific.(Z1)........00000000

Device Specific.(Z2)........00000000

Device Specific.(Z3)........03000909

Device Specific.(Z4)........FF601231

Device Specific.(Z5)........02E01871

Device Specific.(Z6)........06631871

Device Specific.(Z7)........07631871

Device Specific.(Z8)........20000000C93E1D18

Device Specific.(Z9)........HS1.81X1

Device Specific.(ZA)........H1D1.81X1

Device Specific.(ZB)........H2D1.81X1

Device Specific.(ZC)........00000000

Hardware Location Code......U787A.001.DPM1VHX-P1-C6-T1

PLATFORM SPECIFIC

Name: fibre-channel

Model: LP9802

Node: fibre-channel@1

Device Type: fcp

Physical Location: U787A.001.DPM1VHX-P1-C6-T1

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

2) ORACLE SOLARIS

* First check how many HBA ports are there and if they are connected or not using luxadm command

------------------------------------------------------------------------------------------------------

bash-3.00# luxadm -e port

/devices/pci@1d,700000/emlx@1/fp@0,0:devctl NOT CONNECTED

/devices/pci@1d,700000/emlx@1,1/fp@0,0:devctl CONNECTED

* Now using fcinfo command we can get the wwn no. of hba cards.(the wwn no. is highlighted in green color)

---------------------------------------------------------------------

bash-3.00# fcinfo hba-port

HBA Port WWN: 10000000c955dd7c

OS Device Name: /dev/cfg/c3

Manufacturer: Emulex

Model: LP11002-E

Firmware Version: 2.10a10 (B2F2.10A10)

FCode/BIOS Version: Boot:3.01a1 Fcode:3.01a1

Serial Number: BG62327522

Driver Name: emlxs

Driver Version: 2.31p (2008.12.11.10.30)

Type: unknown

State: offline

Supported Speeds: 1Gb 2Gb 4Gb

Current Speed: not established

Node WWN: 20000000c955dd7c

HBA Port WWN: 10000000c955dd7d

OS Device Name: /dev/cfg/c1

Manufacturer: Emulex

Model: LP11002-E

Firmware Version: 2.10a10 (B2F2.10A10)

FCode/BIOS Version: Boot:3.01a1 Fcode:3.01a1

Serial Number: BG62327522

Driver Name: emlxs

Driver Version: 2.31p (2008.12.11.10.30)

Type: N-port

State: online

Supported Speeds: 1Gb 2Gb 4Gb

Current Speed: 4Gb

Node WWN: 20000000c955dd7d

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

3) HP-UX

* first find how many hba cards are inserted in the host using ioscan command

-------------------------------------------------------------------------------

bash-4.2# ioscan -fnC fc

Class I H/W Path Driver S/W State H/W Type Description

================================================================

fc 0 0/5/1/0 fcd CLAIMED INTERFACE HP AB379-60101 4Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 1)

/dev/fcd0

fc 1 0/5/1/1 fcd CLAIMED INTERFACE HP AB379-60101 4Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 2)

/dev/fcd1

* Now for each card we can find the wwn detail using fcmsutil command

-----------------------------------------------------------------------

bash-4.2# fcmsutil /dev/fcd0

Vendor ID is = 0x1077

Device ID is = 0x2422

PCI Sub-system Vendor ID is = 0x103C

PCI Sub-system ID is = 0x12D7

PCI Mode = PCI-X 266 MHz

ISP Code version = 5.4.0

ISP Chip version = 3

Topology = PTTOPT_FABRIC

Link Speed = 4Gb

Local N_Port_id is = 0x65000e

Previous N_Port_id is = None

N_Port Node World Wide Name = 0x5001438001328edd

N_Port Port World Wide Name = 0x5001438001328edc

Switch Port World Wide Name = 0x20c4000dec8224c0

Switch Node World Wide Name = 0x100008008804fc9e

N_Port Symbolic Port Name = hostname_fcd0

N_Port Symbolic Node Name = hostname_HP-UX_B.11.31

Driver state = ONLINE

Hardware Path is = 0/5/1/0

Maximum Frame Size = 2048

Driver-Firmware Dump Available = NO

Driver-Firmware Dump Timestamp = N/A

TYPE = PFC

NPIV Supported = YES

Driver Version = @(#) fcd B.11.31.1103 Dec 6 2010

bash-4.2# fcmsutil /dev/fcd1

Vendor ID is = 0x1077

Device ID is = 0x2422

PCI Sub-system Vendor ID is = 0x103C

PCI Sub-system ID is = 0x12D7

PCI Mode = PCI-X 266 MHz

ISP Code version = 5.4.0

ISP Chip version = 3

Topology = PTTOPT_FABRIC

Link Speed = 4Gb

Local N_Port_id is = 0x65000f

Previous N_Port_id is = None

N_Port Node World Wide Name = 0x5001438001328edf

N_Port Port World Wide Name = 0x5001438001328ede

Switch Port World Wide Name = 0x20c6000dec8224c0

Switch Node World Wide Name = 0x100008008804fc9e

N_Port Symbolic Port Name = hostname_fcd1

N_Port Symbolic Node Name = lhostname_HP-UX_B.11.31

Driver state = ONLINE

Hardware Path is = 0/5/1/1

Maximum Frame Size = 2048

Driver-Firmware Dump Available = NO

Driver-Firmware Dump Timestamp = N/A

TYPE = PFC

NPIV Supported = YES

Driver Version = @(#) fcd B.11.31.1103 Dec 6 2010

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

4) Red-hat LINUX

* First identify the no. of HBA cards and their types by lspci command

-----------------------------------------------------------------------

bash# lspci |grep -i fibre

0a:00.0 Fibre Channel: Emulex Corporation Zephyr-X LightPulse Fibre Channel Host Adapter (rev 02)

0a:00.1 Fibre Channel: Emulex Corporation Zephyr-X LightPulse Fibre Channel Host Adapter (rev 02)

0e:00.0 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 02)

0e:00.1 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 02)

* We can find the wwn no. from the respective files

---------------------------------------------------

bash# more /sys/class/fc_host/host0/port_name

0x210000e08b871816

bash# more /sys/class/fc_host/host1/port_name

0x210100e08ba71816

bash# more /sys/class/fc_host/host7/port_name

0x10000000c9893356

bash# more /sys/class/fc_host/host8/port_name

0x10000000c9893357

There is another method to find the hba wwn details by installing a package called sysfutils

rpm -ivh libsysfs-2.1.0-6.1.el6.x86_64.rpm

rpm -ivh sysfsutils-2.1.0-6.1.el6.x86_64.rpm

yum install sysfsutils

bash# systool -c fc_host -v -d host0

0x210000e08b871816

bash# systool -c fc_host -v -d host1

0x210100e08ba71816

bash# systool -c fc_host -v -d host7

0x10000000c9893356

bash# systool -c fc_host -v -d host8

0x10000000c9893357

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

5) ESX- VMware

We can find the wwn no.s of the hba from the file "/proc/scsi/qla2xxx/X" where X is the no. of card

~ # more /proc/scsi/qla2xxx/7

QLogic PCI to Fibre Channel Host Adapter for QLE2562:

FC Firmware version 5.03.15 (d5), Driver version 901.k1.1-14vmw

Host Device Name vmhba4

BIOS version 2.02

FCODE version 2.00

EFI version 2.00

Flash FW version 4.03.01

ISP: ISP2532

Request Queue = 0x81810000, Response Queue = 0x81851000

Request Queue count = 2048, Response Queue count = 512

Number of response queues for multi-queue operation: 0

Total number of interrupts = 72

Device queue depth = 0x40

Number of free request entries = 2048

Total number of outstanding commands: 0

Number of mailbox timeouts = 0

Number of ISP aborts = 0

Number of loop resyncs = 1

Host adapter:Loop State = <DEAD>, flags = 0x1a268

Link speed = <Unknown>

Dpc flags = 0x100c0

Link down Timeout = 045

Port down retry = 005

Execution throttle = 2048

ZIO mode = 0x6, ZIO timer = 1

Commands retried with dropped frame(s) = 0

Product ID = 4953 5020 2532 0002

NPIV Supported : Yes

Max Virtual Ports = 254

SCSI Device Information:

scsi-qla0-adapter-node=20000024ff282188:000000:0;

scsi-qla0-adapter-port=21000024ff282188:000000:0;

FC Target-Port List:

~ # more /proc/scsi/qla2xxx/8

QLogic PCI to Fibre Channel Host Adapter for QLE2562:

FC Firmware version 5.03.15 (d5), Driver version 901.k1.1-14vmw

Host Device Name vmhba5

BIOS version 2.02

FCODE version 2.00

EFI version 2.00

Flash FW version 4.03.01

ISP: ISP2532

Request Queue = 0x8188e000, Response Queue = 0x818cf000

Request Queue count = 2048, Response Queue count = 512

Number of response queues for multi-queue operation: 0

Total number of interrupts = 72

Device queue depth = 0x40

Number of free request entries = 2048

Total number of outstanding commands: 0

Number of mailbox timeouts = 0

Number of ISP aborts = 0

Number of loop resyncs = 1

Host adapter:Loop State = <DEAD>, flags = 0xa268

Link speed = <Unknown>

Dpc flags = 0x100c0

Link down Timeout = 045

Port down retry = 005

Execution throttle = 2048

ZIO mode = 0x6, ZIO timer = 1

Commands retried with dropped frame(s) = 0

Product ID = 4953 5020 2532 0002

NPIV Supported : Yes

Max Virtual Ports = 254

SCSI Device Information:

scsi-qla1-adapter-node=20000024ff282189:000000:0;

scsi-qla1-adapter-port=21000024ff282189:000000:0;

FC Target-Port List:

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

5) Windows

Windows Server 2012 R2:
From Power Shell:
Get-WmiObject -class MSFC_FCAdapterHBAAttributes -namespace "root\WMI" | ForEach-Object {(($_.NodeWWN) | ForEach-Object {"{0:x}" -f $_}) -join ":"}

Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
PS C:\Users\Administrator.DS1> Get-WmiObject -class MSFC_FCAdapterHBAAttributes -namespace "root\WMI" | ForEach-Object {
(($_.NodeWWN) | ForEach-Object {"{0:x}" -f $_}) -join ":"}
20:0:0:24:ff:54:91:60
20:0:0:24:ff:54:91:61

Wednesday, 3 October 2012

Host Power-On issue in Oracle T4-1 server from ILOM prompt : Solved

It is the first time i am facing such an issue with Oracle T-series servers. Starting from T1000, i have worked on different T-series SPARC machines like T2000, T3-1, T3-2, T4-1.... and they are all like my pets. It is something more than a normal pleasure that i feel when i work on T-series and M-series SPARC servers. Unfortunate that M-series servers are no more into market except its support and that too, EOSL is almost reached

While working on these servers, I came to know that if any small hardware issue is there, ILOM prompt doesn't allow the host to run the POST itself and it will stay in the same prompt.

There is an easy way to solve this issue which i have already done and got a positive output. Its just like "Cheating the server". Everything is mentioned in detail below with the commands and outputs

When you try to start the Server, the issue appears like the below mentioned

-> start /SYS
Are you sure you want to start /SYS (y/n)? y
start: System faults or hardware configuration prevents power on.

What you need to do is:

1) Go to the Fault management shell to use the fmadm utility, so that we can find if any hardware issues are

there

-> start /SP/faultmgmt/shell

Are you sure you want to start /SP/faultmgmt/shell (y/n)? y

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

2) You can see the hardware issues after entering the command fmadm faulty and its the same that you can

see from run level3

faultmgmtsp> fmadm faulty

------------------- ------------------------------------ -------------- --------

Time UUID msgid Severity

------------------- ------------------------------------ -------------- --------

2012-09-26/07:24:59 dc873a7b-f661-ca2f-ae23-f59753bff70c SPT-8000-DH Critical

Fault class : fault.chassis.voltage.fail

FRU : /SYS/MB

(Part Number: 7015924)

(Serial Number: 465769T+1220BW09L3)

Description : A chassis voltage supply is operating outside of the

allowable range.

Response : The system will be powered off. The chassis-wide service

required LED will be illuminated.

Impact : The system is not usable until repaired. ILOM will not allow

the system to be powered on until repaired.

Action : The administrator should review the ILOM event log for

additional information pertaining to this diagnosis. Please

refer to the Details section of the Knowledge Article for

additional information.

------------------- ------------------------------------ -------------- --------

Time UUID msgid Severity

------------------- ------------------------------------ -------------- --------

2012-10-03/04:47:56 47f0af46-19ce-c28d-ae6e-a01e19522e79 SPT-8000-5X Major

Fault class : fault.chassis.env.power.loss

FRU : /SYS/PS0

(Part Number: 300-2235)

(Serial Number: B70386)

Description : A power supply AC input voltage failure has occurred.

Response : The service-required LED on the affected power supply and

chassis will be illuminated.

Impact : Server will be powered down when there are insufficient

operational power supplies.

Action : The administrator should review the ILOM event log for

additional information pertaining to this diagnosis. Please

refer to the Details section of the Knowledge Article for

additional information.

------------------- ------------------------------------ -------------- --------

Time UUID msgid Severity

------------------- ------------------------------------ -------------- --------

2012-07-17/10:03:18 01877670-70dc-667e-928b-c13be3cac7da SPT-8000-MJ Critical

Fault class : fault.chassis.power.fail

FRU : /SYS/PS1

(Part Number: 300-2235)

(Serial Number: B70387)

Description : A Power Supply has failed and is not providing power to the

server.

Response : The service required LED on the chassis and on the affected

Power Supply may be illuminated.

Impact : Server will be powered down when there are insufficient

operational power supplies

Action : The administrator should review the ILOM event log for

additional information pertaining to this diagnosis. Please

refer to the Details section of the Knowledge Article for

additional information.

faultmgmtsp>

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

3) After getting the outputs, please note the faulty FRU's and set the property "clear_fault_action=true" for

all these faulty ones going back to the ILOM prompt

faultmgmtsp> exit

-> set /SYS/MB clear_fault_action=true

Are you sure you want to clear /SYS/MB (y/n)? y

Set 'clear_fault_action' to 'true'

-> set /SYS/PS0 clear_fault_action=true

Are you sure you want to clear /SYS/PS0 (y/n)? y

Set 'clear_fault_action' to 'true'

-> set /SYS/PS1 clear_fault_action=true

Are you sure you want to clear /SYS/PS1 (y/n)? y

Set 'clear_fault_action' to 'true'

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

4) Once this property is set to true, we need to go back to fault management shell and repair the FRU's using

the below mentioned command

-> start /SP/faultmgmt/shell

Are you sure you want to start /SP/faultmgmt/shell (y/n)? y

faultmgmtsp> fmadm repair /SYS/MB

faultmgmtsp> fmadm repair /SYS/PS0

faultmgmtsp> fmadm repair /SYS/PS1

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

5) Check for any more faults are there in the server

faultmgmtsp> fmadm faulty

faultmgmtsp>

faultmgmtsp> exit

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

6) Try startin the System, you can find the error is resolved and the server is up and running

-> start /SYS

Are you sure you want to start /SYS (y/n)? y

Starting /SYS

-> start /HOST/console

Are you sure you want to start /HOST/console (y/n)? y

Serial console started. To stop, type #.

[CPU 0:0:0] NOTICE: Initializing TOD: 2012/10/03 05:44:10

[CPU 0:0:0] NOTICE: Loaded ASR status DB data. Ver. 3.

[CPU 0:0:0] NOTICE: Initializing TPM with:

tpm_enable = false

tpm_activate = false

tpm_forceclear = false

[CPU 0:0:0] NOTICE: TPM found: Ver 1.2, Rev 1.2, SpecLevel 2, errataRev 0, VendorId 'IFX'

[CPU 0:0:0] NOTICE: TPM initialized successfully. Current state is: disabled

[CPU 0:0:0] NOTICE: Serial#: 000000000000002a.015948c07cda22a6

[CPU 0:0:0] NOTICE: Version: 003e003012030607

[CPU 0:0:0] NOTICE: T4 Revision: 1.2

..............................................................

bash-3.2# prtdiag -v |more

System Configuration: Oracle Corporation sun4v SPARC T4-1

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

That's it.. Very simple....huh.... :P

Friday, 31 August 2012

Lun Allocation from VMAX Storage

Today i got a chance to allocate some storage luns from VMAX Symmetrix storage Array to a Solaris SPARC host. VMAX storage systems are the best Enterprise level storages and the most popular flagships products of EMC. These Storage Systems replaced the DMX arrays which once ruled the world of storage, another old EMC product. They are fast, reliable and gives a better performance

Allocating Luns from VMAX has a different method and its not like that in DMX. Here comes something new called Port-group, storage-group, initiator-group and a masking view

Initiator Group : Its a group which consists of
  Host HBA wwn
Port Group : Its a group which consists of
  front end ports of the array
Storage Group : Its a group which consists of all the luns that need to be assigned to   host
Masking view : Its a view created with a port-group, Initiator group and storage group
  When we want to allocate luns to host, we create a masking view for it..
  Entire host-storage communication takes place through this masking view

Below i have mentioned on creation and deletion of Port Group,Storage Group, Initiator Group & Masking view.

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

INITIATOR GROUP CREATION
***************************
The initiator group name i am going to create is ig_libg162 which consists of 2 HBA wwn no.

1) Check if the host WWN no. is visible in the Symmetrix at the ports that is zoned from the
switch end. Here i have zoned it to ports 7e:1 and 8g:1

bash-3.2# symaccess list logins -dirport 7e:1 -sid 016

Symmetrix ID : 000194901016

Director Identification : FA-7E
Director Port : 1

User-generated Logged On
Identifier Type Node Name Port Name FCID In Fabric
---------------- ----- --------------------------------- ------ ------ ------
50000972081a3519 Fibre NULL NULL 6f1b00 No Yes
50000972c00fe19d Fibre NULL NULL 6e0600 No Yes
2100001b320f5448 Fibre NULL NULL 612a13 Yes Yes
210000e08b9472a0 Fibre 210000e08b9472a0 210000e08b9472a0 6d0500 Yes Yes
2101001b322f5448 Fibre NULL NULL 612813 Yes Yes
210100e08bb472a0 Fibre NULL NULL 6d0400 Yes Yes
21fd006069e21a14 Fibre NULL NULL fffc6e No Yes

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

2) Select the particular WWN no. required and create the initiator Groups with the command given
below. Check if the initiator group is created and the required wwn no. got added or not.

bash-3.2# symaccess -sid 016 create -name ig_libj162 -type initiator -wwn 210000e08b9472a0
bash-3.2# symaccess -sid 016 show ig_libj162 -type initiator

Symmetrix ID : 000194901016

Initiator Group Name : ig_libj162
Last updated at : 02:11:07 PM on Fri Aug 31,2012

Host Initiators
{
WWN : 210000e08b9472a0 [alias: 210000e08b9472a0/210000e08b9472a0]
}

Masking View Names
{
None
}

Parent Initiator Groups
{
None
}

***************************************************
3) Add the next wwn no. of the host using the command given below and check if it got added or
not.

bash-3.2# symaccess -sid 016 -name ig_libj162 -type initiator -wwn 210100e08bb472a0 add
bash-3.2# symaccess -sid 016 show ig_libj162 -type initiator

Symmetrix ID : 000194901016

Initiator Group Name : ig_libj162
Last updated at : 02:13:12 PM on Fri Aug 31,2012

Host Initiators
{
WWN : 210000e08b9472a0 [alias: 210000e08b9472a0/210000e08b9472a0]
WWN : 210100e08bb472a0 [alias: 210100e08bb472a0/210100e08bb472a0]
}

Masking View Names
{
None
}

Parent Initiator Groups
{
None
}
*********************************************************************************
DELETING INITIATOR GROUP
*****************************
We should first remove the HBA wwn no. first one by one and then we should delete the entire Initiator Group

bash-3.2# symaccess -sid 016 -name ig_libj162 -wwn 210000e08b9472a0 remove -type initiator

bash-3.2# symaccess -sid 016 show ig_libj162 -type initiator

Symmetrix ID : 000194901016

Initiator Group Name : ig_libj162
Last updated at : 01:11:40 PM on Fri Aug 31,2012

Host Initiators
{
None
}

Masking View Names
{
None
}

Parent Initiator Groups
{
None
}

bash-3.2# symaccess -sid 016 delete -name ig_libj162 -type initiator

Delete Initiator group 'ig_libj162' (y/[n])? y

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

CREATING PORT GROUP
************************
Here i am going to create a port group with Symmetrix Front End ports 7e:1 and 8g:1

1) first check which all ports are used and what all are the port names given

bash-3.2# symcfg -sid 016 list -fa all

Symmetrix ID: 000194901016

S Y M M E T R I X F I B R E D I R E C T O R S

Dir Port WWN ACLX Volume Set Pnt to Pnt
Enabled Addressing

FA-7E 0 50000972C00FE118 Yes No Yes
FA-7E 1 50000972C00FE119 Yes No Yes
FA-8E 0 50000972C00FE11C Yes No Yes
FA-8E 1 50000972C00FE11D Yes No Yes
FA-7F 0 50000972C00FE158 Yes No Yes
FA-7F 1 50000972C00FE159 Yes No Yes
FA-8F 0 50000972C00FE15C Yes No Yes
FA-8F 1 50000972C00FE15D Yes No Yes
FA-8G 0 50000972C00FE19C Yes No Yes
FA-8G 1 50000972C00FE19D Yes No Yes

******************************************
2) Create port group using the command mentioned below and check if the port got added or not.

bash-3.2# symaccess -sid 016 create -name pg_7e1_8g1 -type port -dirport 7e:1
bash-3.2# symaccess list -sid 016 -type port

Symmetrix ID : 000194901016

Port Group Name
--------------------------------
pg_7e0_8e0
pg_7e1_8g1

bash-3.2# symaccess -sid 016 show pg_7e1_8g1 -type port

Symmetrix ID : 000194901016

Port Group Name : pg_7e1_8g1
Last updated at : 02:40:21 PM on Fri Aug 31,2012

Director Identification
{
FA-7E:1
}

Masking View Names
{
None
}

********************************************
3) Add the required ports to this port group depending upon the reliability u need using the
below command.

bash-3.2# symaccess -sid 016 -name pg_7e1_8g1 -type port -dirport 8g:1 add
bash-3.2# symaccess -sid 016 show pg_7e1_8g1 -type port

Symmetrix ID : 000194901016

Port Group Name : pg_7e1_8g1
Last updated at : 02:44:02 PM on Fri Aug 31,2012

Director Identification
{
FA-7E:1
FA-8G:1
}

Masking View Names
{
None
}

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

DELETING PORT GROUP

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

We should first remove the front end ports one by one and then we should delete the entire Port Group.

bash-3.2# symaccess -sid 016 -name pg_7e1_8g1 -type port -dirport 7E:1 remove
bash-3.2# symaccess -sid 016 show pg_7e1_8g1 -type port

Symmetrix ID : 000194901016

Port Group Name : pg_7e1_8g1
Last updated at : 02:45:19 PM on Fri Aug 31,2012

Director Identification
{
FA-8G:1
}

Masking View Names
{
None
}

bash-3.2# symaccess -sid 016 -name pg_7e1_8g1 -type port -dirport 8g:1 remove
bash-3.2# symaccess -sid 016 show pg_7e1_8g1 -type port

Symmetrix ID : 000194901016

Port Group Name : pg_7e1_8g1
Last updated at : 02:47:12 PM on Fri Aug 31,2012

Director Identification
{
None
}

Masking View Names
{
None
}
bash-3.2# symaccess -sid 016 delete -name pg_7e1_8g1 -type port -nop

Delete Port group 'pg_7e1_8g1' (y/[n])? y

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

CREATING STORAGE GROUP

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

Here i am creating a storage group with 25 Luns of 5 Gb size each.

1) Add a storage group using a device as shown with the below command and check if the devices

are visible in the storage group

bash-3.2# symaccess -sid 016 create -name sg_libj162 -type storage dev 0087

bash-3.2# symaccess -sid 016 show sg_libj162 -type storage

Symmetrix ID : 000194901016

Storage Group Name : sg_libj162

Last updated at : 02:54:22 PM on Fri Aug 31,2012

Number of Storage Groups : 0

Storage Group Names : None

Devices : 0087

Masking View Names

{

None

}

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

2) After this u can keep on adding devices to the storage group depending on the requirement using the below command

bash-3.2# symaccess -sid 016 add devs 0088:009F -name sg_libj162 -type storage

bash-3.2# symaccess -sid 016 show sg_libj162 -type storage

Symmetrix ID : 000194901016

Storage Group Name : sg_libj162

Last updated at : 02:57:37 PM on Fri Aug 31,2012

Number of Storage Groups : 0

Storage Group Names : None

Devices : 0087:009F

Masking View Names

{

None

}

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

DELETING STORAGE GROUP

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

In Similar way like what we did for port group and initiator group, remove the luns first from the storage group and then delete the storage group

1) bash-3.2# symaccess -sid 016 remove devs 0087:009F -name sg_libj162 -type storage

bash-3.2# symaccess -sid 016 show sg_libj162 -type storage

Symmetrix ID : 000194901016

Storage Group Name : sg_libj162

Last updated at : 02:59:55 PM on Fri Aug 31,2012

Number of Storage Groups : 0

Storage Group Names : None

Devices : None

Masking View Names

{

None

}

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

2) Delete the storage group as shown with the below command

bash-3.2# symaccess -sid 016 delete -name sg_libj162 -type storage

Delete Storage group 'sg_libj162' (y/[n])? y

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

CREATING MASKING VIEW

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

1) Create the masking view with the proper storage group in which all the luns are added, with

the port group where all the ports are added and with the initiato group where all the HBA wwn

no.s of the hosts are added. as shown in the below command

bash-3.2# symaccess -sid 016 create view -name mv_libj162 -storgrp sg_libj162 -portgrp

pg_7e1_8g1 -initgrp ig_libj162

bash-3.2# symaccess -sid 016 show view mv_libj162

Symmetrix ID : 000194901016

Masking View Name : mv_libj162

Last updated at : 03:05:17 PM on Fri Aug 31,2012

Initiator Group Name : ig_libj162

Host Initiators

{

WWN : 210000e08b9472a0 [alias: 210000e08b9472a0/210000e08b9472a0]

WWN : 210100e08bb472a0 [alias: 210100e08bb472a0/210100e08bb472a0]

}

Port Group Name : pg_7e1_8g1

Director Identification

{

FA-7E:1

FA-8G:1

}

Storage Group Name : sg_libj162

Number of Storage Groups : 0

Storage Group Names : None

Sym Host

Dev Dir:P Physical Device Name Lun Attr Cap(MB)

------ ----- ----------------------- ---- ---- -------

0087 07E:1 Not Visible 0 20481

08G:1 Not Visible 0

0088 07E:1 Not Visible 1 20481

08G:1 Not Visible 1

0089 07E:1 Not Visible 2 20481

08G:1 Not Visible 2

008A 07E:1 Not Visible 3 20481

08G:1 Not Visible 3

008B 07E:1 Not Visible 4 20481

08G:1 Not Visible 4

008C 07E:1 Not Visible 5 20481

08G:1 Not Visible 5

008D 07E:1 Not Visible 6 20481

08G:1 Not Visible 6

008E 07E:1 Not Visible 7 20481

08G:1 Not Visible 7

008F 07E:1 Not Visible 8 20481

08G:1 Not Visible 8

0090 07E:1 Not Visible 9 20481

08G:1 Not Visible 9

0091 07E:1 Not Visible a 20481

08G:1 Not Visible a

0092 07E:1 Not Visible b 20481

08G:1 Not Visible b

0093 07E:1 Not Visible c 20481

08G:1 Not Visible c

0094 07E:1 Not Visible d 20481

08G:1 Not Visible d

0095 07E:1 Not Visible e 20481

08G:1 Not Visible e

0096 07E:1 Not Visible f 20481

08G:1 Not Visible f

0097 07E:1 Not Visible 10 20481

08G:1 Not Visible 10

0098 07E:1 Not Visible 11 20481

08G:1 Not Visible 11

0099 07E:1 Not Visible 12 20481

08G:1 Not Visible 12

009A 07E:1 Not Visible 13 20481

08G:1 Not Visible 13

009B 07E:1 Not Visible 14 20481

08G:1 Not Visible 14

009C 07E:1 Not Visible 15 20481

08G:1 Not Visible 15

009D 07E:1 Not Visible 16 20481

08G:1 Not Visible 16

009E 07E:1 Not Visible 17 20481

08G:1 Not Visible 17

009F 07E:1 Not Visible 18 20481

08G:1 Not Visible 18

-------

Total Capacity 512025

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

DELETING MASKING VIEW

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

bash-3.2# symaccess -sid 016 delete view -name mv_libj162

Delete masking view 'mv_libj162' from symmetrix 000194901016 (y/[n])? y