***18/02/2016***

* Three main requirement standards from SNIA are

1. Provisioning.
2. monitoring
3. reporting.
later they introduced CIM(common information module)(they communicated with CIM
to SNIA for approvals on their products)
HBA cards manugacturers
Emulex - uses HBA anywhere software
Qlogic - SAN surfur software
each port has two pins(wwpn is the port address in wwn node)
one pin is used as transmitter
another pin as receiver
SFP
This act as a mediator between cable and ports
How the data will be transferred?
- In SAN, data wil lbe transferred in blocks.
- data is saved in form of blocks in disc.
- 2146 bytes frame size.
SAN
- Local network of mutiple devices/disc blocks.
- user channel interfaces.
NAS
- NAS uses file system to access data.
- In data will be in form of packets(SAN uses frames).
- It is the single storage device.
- depends on TCP/IP connectivity.
- NAS uses NFS(unix), CIFS(windows), HTTP(Netapp) & FTP(Netapp).
Disc drives used in SAN/NAS.
- SATA(Serially attached technology attached)
- SAS(Serially attached storage).
- EFD(Enterprise flash disc).
- ATA(Advanced technology attached).
- IDE(Intigrated electronics)
- Fibre channel disc(73GB(10k RPM) to 600GB(15K RPM))(180 I/O per minute)
SATA
- Has multiple ports for single devices.
- paths will be active and passive.
- RPM is 7500.
- max size is 2TB.
- 90 I/O per minute.
sas
- Nowadays not in used.
EFD
- max size(200GB to 400GB).
- No RPM.

- 3500 I/O per minute.

What is Fibre channel?
- Its the Gigabit speed network technology.
- Primary it is used for SAN for serial data transfer.
- Transfer the data in form of frames.
Fibre channel Topologies:
- Point to point topologies.
- FCAL(Fibre channel arbitetary loop) topology.
- Switched fabric.
Point to point:
- No mediator between server and storage, directly connected to the storage.
FCAL:
- It follows ring technology.
- Uses hub.
- Hub sends request to all server including server who sent request, hence hub
is not intelligent device. All servers will access data of one server.
- 8 bit pattern for addressing.
- 127 device can only connected in FCAL.
- If one device failes, the others can access the data.
- FCAL is works with JBOD drives.
Switch
- For first time it sends request to all connected device as it doesnt have any
information regarding all devices.
- Than it save all info regarding devices in Naming Table, and next time onwards
it will refer to naming table to find out target devices. Hence switch is intel
ligent device.
- WWN is 128 bit addressing it is assigned to HBA.
- Each HBA has 2 ports. both will have unique WWPN number which is 64 bits(Hexad
ecimal).
- NAA(Name assigned authority), some authority will be there before releasing i
n market used to maintain data integrity for servers.
- For brocade switch has 3 octates. 0:00:00:60:69:50:60:02
- first '0' is named by NAA.
- Next '00' is assigned by Fibre channel standards.
- Next '00:60:69' is assigned by IEEE Standards.
- next '50:60:02' is assigned by vendors.
***23/02/2016***
FC Layers :
- FC-4
- FC-3
- FC-2
- FC-1
- FC-0
FC-0
- its the physical layer
- discussed complete about speed & feeds(1Gbps, 2Gbps, 4Gbps, 8 Gbps, 16Gbps, 20
Gbs)
- its deal with the cables, cables like multimode, single mode and dark cable.
- multimode means multiple lights can be transferred and it will be orange color
, it will be upto 250 metres.

core size will be 50 microns and 62.5 microns.

clad will 125 microns.
Single mode cable will be yellow in color and supports only 1 light at a time.
it will be upto 5kms and core will 9 microns and clad 125 microns.

FC-1
- 8/10 Encoding and decoding.
FC-2
- For framing and flow control.
- Frame(2148 bytes) structure: SOF(4bytes)-Header(24bytes)-Payload(2112bytes)-CR
C(4bytes)-EOF(4bytes).
- SOF wil l have name of frame
- Header will have complete data like sender and receiver details and index of a
ctual data.
- Payload is the actual data.
- CRC will be data to decode the data at receiver end.
- EOF will have the acknowledgement to sender.
- End to end credits and buffer to buffer credits are the flow controls.
FC-3
- This layer will have common services like internal services which we are not u
sing in SAN.
FC-4
- Upper layer transfer protocol. Sender and receiver should same protocols at FC
-4.
Well Known Addresses :
- Flogi, Plogi & PRlogi
- Flogi is used to allocating pids to the device by the fabric., is nothing but
Zoning (FFFFFE),
- Plogi is nothing but mapping(Lun allocation to server)
- PRlogi is nothing but masking(Authentication given to particular server so tha
t only that server can access particular lun).
BROCADE SWITCHES.
Hardware structure of the switch.
- Switch will have ports with naming e-port, f-port, n-port, g-port, u-port, flport, nl-port.
- nl port from from devices are connected to fl ports from switches.
- g-port is generic port, this g-ports can operate as e-port somtimes or f-port
sometime.
- u-port is universal port, this can port can be converted into e-port, f-port
or as g-port.
- e-port is nothing but expansion, it is used to connect to connect to another
switch.
- f-port is used to connect to the nodes(n-ports)
- n-port is direct attached device used to.
- ex-port is expansion is used to connect two fabrics.
FCID in zonning
- FCID is 24 bit addressing used to identify devices in zoning.
- 24 bits are divided into 3 parts of 8 bits.
- first 8 bits is for domain id, next 8 bits for port and last 8 bits is address
which is alpha.

***24/02/2016***
Switch
processor
ram
harddisk.
operating system
apps
Brocade swith
ASIC processor(Applicatin specificaton integrated circuit)
depending upon the model, processor models are stitch(512), loom(1gbps), bloom
(2gbps), bloom-2(4gbps), golden eye(4gbps), golden eye-2(8gbps), condour(8), con
dour-2(18).
will contain entire functional logic of switch.
below parameters will differentiate between processors:
Time taken to process frame,
speed of the switch,(1gbs, 2 gbs. etc....)
# of ports
RAM:
contains SD Ram, synchronous dymanic RAM.
Harddish :
FP ROM, Flash programmable readonly memory.
this compact flash it will hold OS and the apps(fabric os/small firmwares).
OS:
Realtime OS (RT OS).
Diffrent for unix and windows.
will never crash and files will be very thin in size.
Brocade switch modules
3200(bloom processor, 8 ports)
3800(bloom processor, 16 ports)
3900(bloom processor, 32 ports)(midrange)
3900(bloom processor, 64 ports)(higher lever)
200E(GE processor, 16 ports)(low)
4900(GE Processor, 32 ports)(mid)
4900(GE processor, 8X48 ports)(high)
4100(Condour processor, 16 ports)(low)
4100(Condour processor, 32 to 64 ports)(mid)
4100(Condour processor, Director switch)(high)
300E(GE-2, 16 ports)(low)
5911(ge-2, 64 ports)(mid)
5911(GE-2, DSS)(High)
5100(C-2, 32 ports(low))
5100(C-2, DS switch)(mid)
What are the operations we can do in switches:
- Health check of switch(2 types GUI, CLI)(CLI most common), through GUI we can
use web tools like fabric manager, basic command for Health checks are :
- Login to switch through putty by giving name or IP address.
- than we need to do version of the switch by giving command 'version' or 'firmw
areshow'.
- The result will show 7 points like OS, versions and all.
- Next we can do is licence show by giving command 'licenseshow'.
- after know the version, we need to know weather switch is online or offline ho

w devices are connected how many ports are active which device is conneceted to
wich port by giving 'switchshow' command.
- to check the power supply we need to give 'psshow'command.
- next is status of fan in switch by giving 'fanshow' command.
- next to know temperature of switch by giving 'tempshow'command.
- next to know sensor reading we need to give 'sensorshow' command.
- to know complete information we need to give 'switchstatusshow' command.
- command 'hashow' to know high availability of links in switch like standby is
there or not which is active link which is not, also to know two switches status
.
- command 'porterrshow'one of the most important command to know transmitting of
frames, to everything about frames, encryption status, crc status, anylink fa
ils, lost of sync, lost signature, loss of signal.
- command 'fabstatshow' whenever we execute this command we get complete descrip
tion of port, zoning information, whether ports are active or passive, any ove
rlapping.
- command 'statsclear' than will get the all clear all previous data loss.
- if I want to know about me in switch than give 'whoami' command, it will give
all id details.
- If I want to know SFP details, we need to give 'sfpshow' it will check status
of all SFP adapters.
- If I want to know IP of switch, need to give 'ipaddrshow' it will give ip of s
witch.
- 'slotstatclear'
Trunking :
- We will combine the ISL links for load balancing is call trunking.
- Fabric is nothing but collection switches, all are connected through ISL links
.
- e-port of one switch will connect to e-port of another switch.
- speed of switches will be vary for example first switch port will have 1gbps i
t will connect to 1gbps speed only not more than that.
***26/02/2016***
Initilization of new switch :
-Default IP would be '10.77.77.77'
-Default subnet mask would be '255.255.255.0'.
-in windows hipher terminals used to configure
-in unix tip hardware.
-for windows available for comport,
-for unix available in serialport.
-required addl serial cable to configure switch.
-connect laptop provided in box in DB9 port
-than enter command called 'ifmodeshow eth0', it will show link if link is ok th
an give 'ifmodeset eth0'.
-than it will ask do you really want this yes/no ; give yes
-Auto negotiate ; no
-full deplex/half duplex : no
-than give ip by command 'ipaddrset'.
-ehernet subnet mask there we need to give subnet mask.
-than fibre channel addresses come which we dont need to give.
-one more option will come bits per sec, than give 9600
-than data bits : 8
-parity : none.
-stop bits : 1
-flow control : none.
-installation is complete now, now disconnect cable from DB9 port.
-web tool and fabric manager is used in GUI to work with switch.

Four logins
user
admin
factory
root.
-user can only monitor and read the data in switch.
-admin will some rights, he will some change rights, he will create, edit, del
ete user ids.
-factory will have more rights than user and admin, he can able work, monitor,
edit.
-root means complete rights, read, write & execute.
-first we need to check lisense by 'lisenseshow' command, than it will give list
of lisense. lisense is important for zoning.
-'lisenseadd name' to add lisense in switch for zoning.
-This lisense are valid for several levels like zoning lisense, fabric lisense,
switch lisenses.
-all switches will have their domain Ids, zoning will take place in domain id or
port id, only domain or only port.
-use the command 'fabricshow', it will gives the ip, names, wwn# and domains an
d it will have greater than symbol '>' to principal switch.
-to give name to the switch use command 'switchname xyz'.
-to manually changing the principal switch give command 'fabricprinciple -f6'
-'switchcfgspeed 2' to assign speed to switch.
-trunking command 'portcfgtrunkport'
-'portcfgshow' to know the speed of the port, show port setting, speed, trunking
, distance, l port, b2b credit.
-'portcfgspeed port#,%16' and we use the command 'portcfgshow' to cross check.
-'portdisable port#'/ 'portenable port#' to disable enable any port.
-'uptime' or 'switchuptime' to check since how many days it in up state.
-'switchshow' will give complete details of switch, how many devices connected
to it, if we have multiple vendors switch than our switch mode will be interrup
t mode, native mode in case of single vendor switches. becon: green is ok, oran
ge warning, red already faulted, distance of switch, all the ports #m ids, onli
ne, no light, no sync(sync is not taking place.), in sync(everything is fine), n
o cord, no module(no sfp). if its online than it will have wwpn of node.
-firmware upgration.
***29/02/2016***
Zoning
-Zoning is for security purpose in fabric.
-its the limiting scope of initiator with respect to target box(storage)
-or creating virtual bus within the physical SAN network.
-process to implement zoning we need prepare, define, we need to analyze, enable
the zone configuration, verify there is a accessibility between zone members.
Types of zoning:
-soft zoning.
-hard zoning.
-mixed zoning.
Soft zoning:
-its based on wwn numbers of initiator and target with port numbers of the fabri
c.
Hard zoning:
-Hard zoning is done by domain ids and port ids of the switch.

Mixed zoning:
-Combination of both zonings soft and hard zoning.
-main disadvantage of if zone configuration is needs to be changed whenever HBA
or port fails, if single port also fails we need to change zone details.
Soft Zoning:
-most prefable method is CLI, we use the command 'aliascreate' we create the ali
as, 'alidelete' to delete the alias, to add onemore alias give 'aliadd', 'alirem
ove' to remove it.
-'Alishow' to know the current status of what we have created.
-'zonecreate' to create, 'zonedelete' to delete zone, 'zoneadd' to add zone, 'zo
neremove' to remove, 'zoneshow *name' to show details of particular zone.
-'cfgcreate' creating the configuration, 'cfgdelete' to delete that particular z
one configuration, 'cfgadd' to add, 'cfgremove' to remove that particular zone c
onfiguration, 'cfgshow *name' to show details of that particular zone configurat
ion.
-'cfgsave *name' to save configuration, 'cfgenable *name' than it will be active
, 'cfgactvshow' will automatically enable the configurationa nd shows the detail
s of it.
Preparing soft zone.
-first we collect wwpn of initiator and targets.
-than we need to create alias for server, 'alicreate "S1","222"'
-'alicreate "B1","666"'
-to check alias details, execute 'alishow' it will shows both alias details.
-to create zone 'zonecreate "SB1","S1:B1"'.
-now create configuration by 'cfgcreate "CFG1","SB1"'.
-now we can check zone configuration, we can check by 'cfgshow CFG1', to check z
one 'zoneshow SB1'.
-to active configuration give command 'cfgenable CFG1'.
-'alicreate "S2","444"'
-'alicreate "B2","888"'
-'zonecreate "SB2","S2:B2"'
-than we can add SB2 zone in 'CFG1' effective configuration by 'cfgadd CFG1,SB2'
.
-than again we need to execute 'cfgenable CFG1' to changes to take place in 'CFG
1'
Redundancy.
-'alicreate "S1","111;222"'
-'alicreate "B1","333;444"'
-'zonecreate "SB1","S1;B1"'
-'cfgadd CFG1,SB1'
-'cfgenable CFG1'
-if HBA fails, 'aliremove "S1","111"'
-new one wee need to add 'aliadd "S1","111a"'
-'cfgenable "CFG1","S1;B1"'

how to change password of switch userids.

-'passwd'
-it will ask for old password than give old password
-than it will ask for new password than give new password
-again it will ask new password.
***06/03
/2016***

- we have automated to to show healthcheck.

'Supportsave' command
-when we run 'supportsave' it will take complete details of the switch.
-'statsclear' and 'slotstatsclear' run before executing 'supportsave'.
it will give :
- it will transfer existing tracedump files first than automatically generate an
d send latest files.
it will ask for ip for other system to transfer all details,
than it will ask for your username.
than it will ask for ftp or scp. than give ftp.
than it will ask remote directory name than give name as 'root'
than inside root, give folder name with resptive switch name and zip it, for ou
r convenience where all details will be saved.
- than it will save RAS logs, trace, supportshow, corefile, FFDC data.
***09/03
/2016***
Switch Topology :
-there are 3 types of topologies.
-full mesh, half mesh, core edge technology.
Firmware Upgration:
-there will be already existing firware of old version.
-first we need to take backup of current firmware.
-'firmwareshow' to check firmware.
-'configupload' to take backup, it will take complete configuration backup incl
uding firmware.
-than it will ask manager server ip, than give ip of server where you want to
save configuraton,
-than it will ask domain username and password.
-than it will ask protocol, ftp or http.
-than give filname by switch by '.ext'
-than it will save in root directory your configuration file.
-download new version from IBM link.
-when u click it will again ask for management server.
-it will ask same things.
-than 'firmwaredownload' give in switch
-than it will ask us the server name/ip than same username and password and loca
tion of file and file name.
-than it will download from that server.
-than we need to check lisense by 'lisenseshow'
-than 'nsallshow' it will gives the server which is connected to switch, NL-node
loop,
-after that give 'portcfgshow' than it will give all port capabilities
-'configupload' protocol ftp and ip adress username and password
-it will ask pathname and filename after giving credentials
-'firmwaredownloadstatus' to check status of firmware, it will take minimum 30 m
ins.than it will give all details regarding new firmware.
-in director switch tha firmware upgrade will automatically reflect in second pa
rt(we updated in first part).
-'downloadstatusshow' will also give all details.
-now give 'firmwareshow' to crosscheck whether new upgraded version applied or n
ot.
-if after upgrade services is not working properly than we need to roll by to ol

der version of firmware by again giving 'configupload' in switch and give backup
server ip, username, password, and filepath to download old version.

***10/03
/2016***
STORAGE DEVICE
-DS4K
-DS4100
-DS4300
-DS4500
DS4100
-Dec8 2006 onwards these 4100 has came in market.
-compact 3U rack mountable.
-Controller has 2Gbps raid controller.
-It supports Raid0, Raid1,Raid3, Raid5, & Raid10.
-Cache memory is of controller is 512MB(BtoB credit)
-it has hot swappable power supply.
-one 1 expansion port per controller.
-Exp100, Exp710, Exp810 ports only DS4100 supports.
-consist of 4 host ports.
-Exp100 cannot be attached to single controller model.
-Each controller having one ethernet port.
-each will have one powersupply.
-each part will have one fan.
-each side have one expansion port.
-on/off switch on each controller.
-DS4100 consist 14DDMs (diskdrivemodules).
-These 14DDms supports Raid0,1,3,5,10.
DS4300
-It is also having Compact 3U rack mountable.
-its 2Gbps Raid controller.
-hot swappable powersuppy.
-Support raid0,1,3,5,10
-each expansion port for one controller.
-Exp100, Exp710 & Exp810.
-These are all SATA disk
-4 host ports(2 per controller).
-Exp100 model cannot to attached to single controller model.
-it supports 14DDMS.
-1GB cache memory(B2B credit).
DS4500
-4U Rack mountable enclosure.
-Intel P3 in each raid controller.
-dual redunce 2Gbps raid controllers.
-raid0,1,3,5,10.
-it support 4 host sides mini hubs.
-it support 4 drive side mini hubs.
-upto 16 expansion drives it supports.
-Exp100 & Exp710.
-Exp 100 cannot be connected to single controller model.
-it will have alarm switch, for any hardware issues it will give alarm call/mail
.
-Cache memory is 1Gbps per controller.
-it consist of controller blades.

-controller status, heartbeats, indicators.

DS4200
-3U rack mountable.
-supports only Sata disk.
-support 4Gbps raid controllers.
-1GB cache per controller with BBU(Battery backup unit).
-It is hot swabbable power supply.
-Raid0,1,3,5,10.
-it supports 2 expansion ports per controller.
-it will have total 4 host ports.
-support maximum 6disk EXP420s.
-It consist of 16DDMs
-LED lights to check health status of each hardware part.
DS4700
DS4800
DS4700
-Supports FC and SATA disk solution.
-it is an 3U rack mountable.
-it consist of 4Gbps Raid controller.
-4GB cache per controller with BBU.
-redundant hot swappable power supply.
-supports raid0,1,3,5,6,10.
-2 expansion ports per controller.
-supports EXP710 & EXP810.
-total 4 host ports.
-it is having 16DDMs
-LED lights to check health status of each hardware part.
-These divided into 70A model & 72A model.
-in 70A we have 4 host ports, 2GB cache, 4 expansion ports.
-in 72A we have 8 host ports, 4GB cache, 8 expansion ports.
-sata means 84.3TB for all 16DDMs, FC means 36.4TB for all 16DDMs.
DS4800
-supports FC and SATA disk solution.
-it is an 3U rack mountable.
-4Gbps raid controllers.
-4GB cache per controller with BBU.
-redundant hot swappable power supply.
-supports raid0,1,3,5,10
-have 8 expansion ports.
-supports 16 expansion drives.
-support EXP100, EXP710 & EXP810.
-max support 6 expansions.
-total it have 8 host ports.
-it has support 16DDMs.
-if using exp100 than 16DDMs, if using exp710 than 14DDMs.
-sata means 84.3TB for all 16DDMs, FC means 36.4TB for all 16DDMs.
-Exp100, Exp710, Exp810 will support FC & Sata disks.
-Exp420 will support only sata disks.
***29/03/2016***
DS8K Model Base Frame.
BASE FRAME

- Base frame consist of cooling finum,

- disc enclosures(total 8), each disc enclosure consist of 16DDMs so totally 128
DDMs in basic frames.
- It consist of HMC, Hardware management console, Call home has been configured
in this HMCs, comes with inbuild laptop to configure.
- comes with 2 ethernet switches, each switch has 8 port.
- Out of 8, 2 are connector to processors, each to one processors. CEC.
- 2 ports for HMCs.
- 2 ports for FSP., Flexible service processor.
- rest 2 ports are free.
- It consist of 2 processors, P5(Power 570) processors, CEC0, CEC1.
- 1.5Gbits per processor Cache memory.
- It has remote input output group.
- It consist of 4 IO enclosures, each IO enclosure consist of 6 slots,
- Slot 1,2,4,5 are Host adaptors,
- Slot 3,6 are Disc adaptors.
- Each slot consist of 4 ports.
- so total HA ports are 64 ports
- Total DA ports are 32 ports.
- Port speed is 4Gbps.
- It consist of Rack power control(RPC), its mainly used to nagate power fluctua
tion
- 2 PPS(Primary power suppy).
- Consist of 2 BBUs, Batter backup units. It provides the battery backup wheneve
r there is powerfailure.
- It suppots Raid5,6,10 model.
- Max size of LUN could be 2TB in DS8K Series.
DS8100
- It conist of one base frame and one expansion frame.
- That expansion frame consist of 1RPC, 2 PPS, 2 BBUs, and cooling pinum.
- It also will have 4 IO Encslosure.
- Expansion frame will consist of 16 Disc Enclosures and 16 DDMs per enclosure,
so total 256DDMs.
- This expansion model is 92E.
- Internally each Disc enclosure will have two switch.
- Swith will have 20 ports, 16 ports for 16 DDMs.
- 2 are for internal connectivity.
- 2 are free.
- This connectivity is called Daisy chain
- Between CEcs we will have Remote Input Output Group.
DS8300
- It will have 4 Expansion frames apart from base frame.
- First 3 expansion frames will have 16 Disc Enclosures and each will have 16DDM
s per enclosure.
- 4TH expansion frame will have 8 Disc Enclosures and each will have 16DDMs.
- The cache memory is 256 GB in Base frame.
DS8700
- It will have P6 processcor which is 4.7 Ghrtz.
- Cache memory will be 384GB.
- It will have 4 Expansion frames apart from base frame.
- First 3 expansion frames will have 16 Disc Enclosures and each will have 16DDM
s per enclosure.
- 4TH expansion frame will have 8 Disc Enclosures and each will have 16DDMs.
***30/03
/2016***

DS8800
- Now in Base frame we will have 10 Disc enclosures
- In IO Enclosure, 2 slots for HA and 2 for DA.
- HA slots will have 8 ports with 8Gbps speed and DA slot 4 ports with 8Gbps spe
ed.
- It will have Power6 processor with 5.2 Gigahertz.
- It will have 3 expansion frames.
- First expansion will have 14 DE.
- Second & third expansion will have 20 DEs.
- If rack size is 2.5 inches than enclosure will have 24DDMs per enclosure.
- If rack size is 3.5 inches than enclosure will have 12DDMs per enclosure.
- First will have RPC, Cooling pinum
DS8870
- It will have P7 processor.
- First xpansion 14, 2nd xpansion 20 DEs, & 3rd xpansion 20 DEs.
- It will hae DC UPS Direct current uninruupteable power supply.
- There it consumes 20% less power than other models.
- Cache Memory will be 1024GB.
- PCIE Connectivity(RIOG is looping connectivty where PCIE is point to point con
nectivity)
- Main advantage of PCIE there is no single point of failure.
VIRTULIZATION :- It is the abstraction process from actual physical disc to logical volume pres
ented to host.
VIRTULIZATION STEPS :- Frome DDMs first we need to create Array site.
- From there we need to create Array.
- From array we need to create rancs.
- From rancs we need to create extend pool.
- From extand pool we need to create volume.
- In DS8K volume will rotate volume or rotate extend.
- Frome volumes we need to create volume groups.
- Than map to host.

- rancs could ve ckd(count key data .94GB) or fb(fixed block of 1GB).

- than we create extand poool from ranc which is nothing but collection of exten
ds.
- in extend pool it consist of 16 address groups, each group consist of 16 lss(
logical storage subsystem) which are lun ids, means 256(0-255) lun ids in one ex
tend pool.
- than we create volume and group them into volume group.
Command line for virtulization.
- 'dscli -hmc1 "ip of storage array" -username "username" -pwd "password"'.
//To login into storage array.
- 'lsarraysite -l'
//To check arraysite.
- 'mkarray -raidtype 5 -arsite "arsitename"'
//To create array from array site.
- 'lsarray -l'
//To check arrays.

- 'mkranc -stgtype "ckd or fb" -array "arrayname".

//To create ranc from array.
- 'lsranc -l'
//To check rancs.
- 'mkextpool -rancgrp "0/1" -stgtype "ckd/fb" -extpool "extpool name"'
//To create extend pool from ranc.
- 'lsextpool -l'
//To check volume groups.
- 'mkfbvol -extpool "extpool id" -cap size units -volname'
//To create volume from extend pool.
- 'mkvolgrp -name "volgrp name" -vol "lss id:lun id"'
//To create volume grp from volume.
- 'mkhostconnect -wwpn "hostwwpn" -volgrp "volgrp name"'
//To map voume grp to host.
REPLICATIONS.
- Flash copy.
- Metro mirror.
- Global copy.
- Global mirror.
Flash copy.
- Point in copy of image.
-Types : persistance flash copy, incremental flash copy, multiple relationship f
lash copy, dataset flash copy, consistency group flash copy.
Metro mirror
- Repliating the data from one storage box to another storage box, it wills sup
port upto 300Kms.
- Synchronus mirror service
Global Copy
- Full copy of a volume with background copy.
Globar Mirror
- Replicating from DCs, supports long distance, asyncronus copy service.
Commands
- 'mkflash -dev -device "source volume: target volume"'
//To create flash
- 'mkpprcpath -dev "device id" -src "lss" -tglss "lss id" -remoteserver "wwpn of
remote server" "srclssid:trglssid"'
//To create path from source to target.
- 'mkpprc -dev "device id" -remotedev "remote dev id" -type "mmrr sourcevolid:ta
rgetvolid"'
//To create metro mirror copy.
- 'mkpprc -dev "device id" -remotedev "remote dev id" -type "gcp sourcelssid:tar
getvolid"'
//To create global copy.
- 'mkgmr -dev "device id" -type "gmr sourcelssid:targetlssid" -remote "remote ww
pn"'
//To create global mirror.***
***01/04/2016***
IBM XIV :- This is the fast growing in Market
- 2810 and 2812 are the two models.
- there are 2 generations are there
- nd gen 2810 is A140 Model -A140 for 2812
- This two works based on switches.
- Gen 3 models are 2810-114 and 2812-114

Works on infiny band switches.

Infiny band swiches conduct data and meta data traffic at same time.
It supports iSCSI and FC connectivity.
Mulitple host access almost 1024 host.
Fast rebuild time in case of disc failure
It supports thin provissing.
Synchronous and Asynchronous in replication volumes.
Consistency group to a remote syste,
Volume cloning nothing but full copy of volume.
It can perform 16000 Snapshots and 500 snaps for master.
It will send the notification events, through email, sms, snmp.
It support flash copy and management software through CLI and GUI.
It provides data models and interface models,
Physical processing, data....................
contain total 15 modules in XIV RACK, 9 will be data modules, remaining 6 will
be the interface module.
- 1,2,3,10,11,12,13,14,15 this are the data modules in rack
- 4,5,6,7,8,9 this are the interface modules.
- Each module contains 12 disc drive those are SAS drives, Size of each drive wi
ll be 2TB and 3TB.
- Each module will contain intel I7 quadcore processor, and 48 GB cache for tota
l 8 models.
- Purpose for interface modules are equaling to data modules in all aspects in a
ddition to disc cache, processing resources.
- Process is I7 quad core, each modules contains 12 SAS drive, 48GB cache.&
- It is connected to the host, 4 FC ports for host connectivity, 4 iSCSI ports,
so total 24 FC ports and 22 iSCSI ports(module 4 have only 2 iSCSI ports).
- It consist of 3 UPS, under that UPS we have ATS(Automic Transfer Switch), this
switches we call as infiny band switches.
- Each switch has 36 ports, 1 to 15 are internal module connectios and 16 & 17 a
re interswitch connectivity, 18 will be free, rest all ports are in active mode.
- Traffic will follow interface to interface, data modules,
- There is no raid concept in XIV.(In build it comes with 10 model)

- 'mstsc' than we will get command prompt than it will go to remote desktop conn
ection
- there we need to give ip and than click connect.
- It will as username and password,
- There in command prompt I need to type 'dscli', there hmc ip username and pass
word.
- For GUI we have link, double click and it will open box directly, There is co
nnects to XIV storage management.
- There like speakers are drives and under that we have monitor and under that w
e have volumes and under that we have LUN and after that we have host connectivi
ty.
- Next we have replications
- There is limit in read and write operations like for example if it goes above
14k to 15k than its critical.
- Need to allocate storage to the host, for that we need to create host from tha
t we need to create storage pools, to do all we have options on tops like file,
edit, view, etc.
- We need to connect view, than it will displays all system, pools, volumes, hos
t, & luns, there select pools.
- it will display storage poolm, if we right click than it will give option for
add pool, now pool has been created based on requiredment.
- Select the newly created pool than there it will have number of volumes to add
, select numbers of volumes, size of volume and name of volumes.

- hen select create, in XIV we can create 17GB of volume at a time.

- now we need to add this volume to pool.
- Next Adding the host to the volume, select view, than select 'hosts&luns' it w
ill open hosts and host connectivity for luns it iwll open luns and luns mapping
.
- right click on host than select add host, host has veen added now
- Now we need to add host ports to host defination, right click on newly added
host and select add port and than give port address.
- Goto the view select host&luns than select host and after that select map volu
mes to this host.
- We need to give host name, FC or iSCSI, next port name, than host HBA WWPN tha
n select add and its complete.
- to map volues goto view select host&luns than select lun mapping than it give
you the luns name and volumes name.
- Whatever lun you want to map select that lun and respective host name than it
will map them.
Replications
- we have local replications and remote replications.
- snapshots and volume copy in local replications.
- remote mirroring in remote replication.
SNAPSHOTS
- Goto 'view' than select 'volumes' than it will give options like volumes snaps
hot, consistency group etc., select 'volumes&snapshots'
- There we need to select particulate volume, than right click on it, than it w
ill give 'create snapshot', 'create snapshot advance', 'map selected volumes'.
- Than select 'create snapshot'
VOLUME COPY
- Goto 'view' than select 'volumes' than right click n select 'copy of this volu
me', also it will have 'resize', 'delete' and all.
REMOTE MIRRORING
- Goto 'views' than select 'remote connectivity', than select 'configure' than w
e need to configure the port names.
- than give initiator address than and in raid option give auto.
- Right click on the system than select 'create target', than we need to give ta
rget type also target name and target protocol(FC/iSCSI) than select define.
- than go to 'views' than select 'remote' than select 'mirroring'
- Goto 'view' than 'host&luns' than it will ask you asynchronous or synchronous
mode than it will start mirroring.

***08/04/2016***
svc : SAN VOLUME CONTROLLER :
- The SVC is an storage virtulization device by IBM.
- It is used to virtulize the back-end storage space and to present it as a logi
cal volumes to the server.
- Its just a device does not contain any storage or controllers.
- Gives us a centralized management of the storage.
- Common replication service for all difference boxes using SVC.
ARCHITECTURE OF SVC :
- It is an eight node cluster.
- It considers as 4 pair cluster, one pair is having 2 nodes.
- Each node has processor Intel Zeon 5600 Quadcore processor.
- Each node will have own cache of 24GB.
- 4 FC ports and 2 iSCSI port for each node.

- Each port speed will be 8Gbps.

- All backend storage assigned to SVC work as mdisk, unmanaged mode disk.
- Total we can 128 mdisk groups, and each mdisk group can have 128 mdisks.
- This mdisk spaces is divided to extents.
- So total max 4 million mdisk possible in SVC.
- The minimum extent size start from 16MB which comes to 64TB max sixe, if selec
t 32MB than it will have 128TB
- In SVC we have to corum disk, to maintain the SVC information corum disk is us
ed.
- The first 3 mdisk reserved as a corum disk, out of these 3 disk only 1 corum d
isk is active.
- It contains all configuration data.
- Shrinking and expansion of vdisk is possible, but shrkingking is not recommend
ed.
STEPS :
- First need to detect mdisk.
- Second make mdisk group.
- Third add mdisk to mdisk group.
- Fourth make a vdisk from mdisk.
- Fifth Make host.
- Sixth Make vdisk host map.
MIGRATION
- Between
- Between
- Between
-

:
storage we can migrate.
IO groups we can migrate.
storage pools.

First imange to manage mode.

Second manage to image mode.
Third image to image mode.
Fourth manage to manage.

- Manage group is nothing but mdisk added mdisk group.

- Image is nothing but mdisk contains the data.
- Collection of mdisk group is called storage pool.
IMAGE TO MANAGE :
- Data from actual mdisk will going to be migrated to managed mdisk.
MANAGE TO IMAGE :
- Data from managed mdisk will goint to be migrated to mdisk who is already havi
ng data.
IMAGE TO IMAGE :
- Data will be migrated from one data disk to the another data disk.
MANAGE TO MANAGE :
- Data from one manage mdisk group to migrate another mdisk group.
- If migrating with "image to manage" and "manage to manage' than we can create
migrate Vdisk.
- If migrating with "manage to image" and "image to image" than it is migrate to
image.
STEPS:
- First detect mdisk with command 'detectmdisk'
- SECOND create mdisk group with command 'mkmdiskgroup -"name" -"ext" -"mdisk" "#mdisk"'.
- Third to create vdisk with command 'mkvdisk -"name" -"mdiskgroup" -"vtype" -"s

ize" -"IOgroup#"'.
- Fourth create host with command 'mkhost -"hbawwpn" -"name"'.
- Fifth map vdisk to host with command "mkvdiskhostmap -"host" -"vdiskname"'.
- we use '-force' in command when we want vdisk to be mapped to multiple host,
"mkvdiskhostmap -force -"host" -"vdiskname"'.
- We can max 8192 vdisk(extent 16MB)
COPY SERVICES.
- Flash copy.
- Metro mirror.
- Global mirror.
FLASH COPY : Snapshot, clone, cascade, backup.
- command to map is 'mkfcmap "sourcevidsk":"targetvdisk" "fcmapname"'.
- to start service 'stratfcmap "fcmapname"'.
METRO MIRROR :
- 'mkpartnership -"bandwidth" "remoteclusterid"'
- 'mkrcrelationship -"master" -"aurid" -"clusterid" -"rccopyname"'.
- 'startrcrelationship -"rccopyname"'.
GLOBAL MIRROR :
- Same as metro mirroring.
- 'mkrcrelationship -"master" -"aurid" -"consistgroup#" -"clusterid" -"globalcop
yname"
- 'startrcrelationship -"primary":"auxilary" -"globalcopyname"'.
multipathing software in linux is sddpcxm(sub device driver path control module)
sdddsm(sussystem device driver data storage management) for windows
migrate extents take place between storage pool
migrate images take plase between storage pool
migrate vdisk take place between storage pool
map host to IO groups give ndvm(non distructive volume move) means without any d
own time and data loss we need to move data between controllers.
- 'movevdisk'
- 'addvdiskaccess'
- 'rmvdiskaccess'
BASIC HEALTHCHECKs PERFORMED IN SVC :
- 'lshbaportcandidate'
//Will display
he devices connected to that SVC
- 'lshost'
//will display
ion connected to SVC.
- 'lshostvdiskmap'
//will display
ormation.
- 'lsddm -usage -unconfigured -stgid'
//will display
sk in that controller
- 'lssi'
//will display
ans logical sub system. one lss have 0 to 255 luns.
- each address group has 16 lss(each lss have 0 to 255 luns)
- 'lsda stgid'
//will display
Trublishooting steps.
- first check lun id of that lun.
- second check lun is online or not.

you the wwpn of t

all host informat
all the vdisk inf
all the failed di
storageid, lss me
storageids.

- third check the status of that host.

- fourth rescan the system/services.
- 'cfgmgr' AIX command to detect.
basic healthcheck commands ds8k
- 'lsddm -usage -unconfigured -"storageid"'.
ailed ddms
- 'lsioport'
nput output ports
- 'lsfbvol'
isting of fb volumes.
- 'lsserver'
ll servers details.
IN SVC
- 'lsnode'
ll nodes connected svc.
- 'lsiogrp'
ll i/o groups details
- 'lsmdiskgrp'
ll mdisk groups information.
- 'lsdrive'
ll drives information.
XIV BASIC HEALTHCHECK
- 'eventlist'
ll the events.
- 'module_list'
ll modules info.
- 'service_list'
ll services info.
- 'fc_connectivity_list'
ll flash copy connectivities info.
- 'host_connectivity_list'
ll host details connected to XIV box.

//list f
//list i
//will l
//list a

//list a
//list a
//list a
//list a

//list a
//list a
//list a
//list a
//list a

- ARCHITECTURE is main, interviewer firt focus on architecture knowledge.